I was thinking on the same lines. Maybe have a "Gaming Mode" where the user knowingly chooses to turn the device into a games machine for better performance.
Pd. Markus Junginger wrote: > I strongly agree with the idea that foreground processes should be > preferred. Currently I develop a game, which - like most games - > relies on a constant high frame rate. At first, the game pretty sloppy > until I realized some background app was draining CPU resources. So I > uninstalled some of them until it ran smoothly. Clearly, this is > nothing you want to tell a user to do. > > So, my first thought on how to solve this is a guaranteed CPU slice > for the foreground app. Let the foreground task constantly get 90-95% > of the CPU time if it needs it, no matter what's running in the > background. The remaining 5-10% should be enough for background tasks. > I think that's perfectly fine if, for example, emails are received a > little slower when the user plays a game. Of course, if the foreground > task does not use the CPU entirely, background tasks should be able to > get a bigger slice. > > Oh, and by the way, what about a JIT or a hotspot compiler? If Android > apps would be running a factor ~10 the problem would be smaller by the > same factor. :) > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
