> So you are saying the user doesn't want to know who is playing sounds in the > background and have a clear way to get to the app to stop it?
A service doesn't need foreground to play noises in the background. If it IS foreground, the notification doesn't help to 'get to it' or stop it. If my app is foreground all the time, whenever the bells play the users think it must be my notification bar app. > Or what is > the situation you are using this for where it is an annoyance? My app needs a permanent background service for monitoring. That means, it needs foreground in order to be reliable. Unreliable monitoring is useless. I get constant queries asking me about 'turning off the notification'. A notification that is there all the time is just taking up space. We can't even change the icon dynamically to give it some informational use, as I recall. > > I really don't think that that change was an improvement, especially > > since > > the service/battery stats arenow easily available via the Settings > > app. > > Apps had started to seriously abuse this facility to get themselves stuck > consuming memory with no way for a normal user to know what is going on. It > was necessary. But now (don't know since when) there is another way, the running services list. They can't stop the service via the notification. They can via the services list. If things aren't going to change in this respect, how about a setting under Manage Apps to turn off the notification on a general or per-app basis ? Pent -- 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
