Hi, I recently added functionality to my app that does a simple state check on a boolean when the connectivity state changes. In order to do this i register a broadcast receiver that is invoked as soon as the phones connectivity state changes. This is all fine and works just as intended. However, a side effect of this is that the application context is launched every time there is a change in the connection. As a developer I know that this is ok, because the system can just kill the context whenever it wants. But users that use any kind of app-killer sees that the app is regularly reoccurring on the list of running app, and therefore thinks that the app does unnecessary background work and takes up resources. So how do i 'solve' this 'issue'. I cant expect the users to understand the underlying functionality of the OS...and people are uninstalling the app because they dont like that it is reoccuring on the app-killer list...
Any thoughts? :) Cheers -- 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
