On Wed, Aug 11, 2010 at 10:43 AM, Pent <[email protected]> wrote: > For numerous reasons, a primary one being I can't figure out when a > new > app launches within a reasonable time and resource usage otherwise.
This should be a hint that what you're doing isn't really supported by the platform. >> > We can't even change the icon dynamically to give it some >> > informational >> > use, as I recall. >> >> Sure you can. > > Have you tried ? Have I tried updating a Notification? Sure. Just raise the Notification with the same ID. Though for startForeground(), you will probably have to stopForeground() the existing one and create a new one with the new icon, calling startForeground() again. > However you turn it, however, a sizeable proportion of users don't > like > it and making them able to turn it off would be nice to them. IMHO, a much more sizable proportion of users get pissed off at developers creating everlasting services. IMHO, a much more sizable proportion of users get pissed off at running services that they can't control. Evidence for these can be found in the popularity of task killers and uncountable poorly-written rants on various blog posts and accompanying comments. I agree that it'd be nice for a user to be able to "bless" a service, such that it wouldn't need startForeground(), or perhaps so its icon just wouldn't show up even if startForeground() is called. However, I can't fault the current implementation's objectives. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android 2.2 Programming Books: http://commonsware.com/books -- 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
