This is a problem that the Google engineers have acknowledged. As you probably know, the issue is that the Android OS does delayed garbage collection of - and possibly reuses - "dead" porcesses, however the process name remains that of the last app it hosted, as reported via DDMS or via phone's running processes.
Forcefully killing the process may seem to placate your users, but as you know is frowned upon by the Android engineers. Could you instead explain that what they see is not a running process, but a process ready to run in case they need the service soon. It's really a lot like a hybrid car at a stop sign. The ignition is on, but the engine isn't running, but can start up instantly if you press on the gas. -- 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
