Robert Green wrote: > The whole issue is that the Sync and IM services are specifically what > cause lag in games. If a user wants a smooth gaming experience, > something's gotta go - or it's gotta be squashed way down so that it > can't use much of the CPU.
That's what the background process scheduling class was supposed to do, or so I thought. Another way to help skin the cat is to provide frameworks for intelligent background processing. Think of it as providing an iPhone-style multi-tasking layer. Apps written to use those can be "guaranteed" (-ish) to behave well. Apps that ignore the frameworks and roll their own background processing can cause problems, and sufficient "blame APIs" can help users identify the problematic stuff and get rid of the apps, just as they get rid of apps that consume too much storage or use too much battery. That won't help where the OS itself is the one chewing up the CPU cycles, of course. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy _Beginning Android 2_ from Apress Now Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
