So it is ok for us to see that an app is screwing up, but all we can do about it is flag the product in market, assuming it came from there, hope someone fixes it soon, uninstall and reset the phone. Way to treat all owners of the device like kids. Even my old Sony Ericsson phone lets me force quit things. I don't see that it is necessary or even desirable to include official system services, but 3rd party apps and services should be killable.
On Fri, Nov 7, 2008 at 9:18 PM, hackbod <[EMAIL PROTECTED]> wrote: > > On Nov 5, 2:34 pm, originalman20 <[EMAIL PROTECTED]> wrote: > > I see. But then the problem with applications ending when you don't want > > them to arises. > > Applications should be written to not have themselves end while still > running. This is done by writing the persistent part as a Service so > the system knows when it is needed. Many of the apps built into the > system use this facility for doing background things, so it should > work well. > > > Like my aim logs out all the time and its really annoying I > > don't even use it at all now. > > Is this the AIM client that comes with the system? I am not aware of > this issue, though maybe it has it, or it is maybe the intended > design. If it is some other AIM client, it is probably an issue with > that implementation. > > > So how do we address that? My Blackberry > > didn't have a task manager but I also never had the unwanted ending of > apps. > > Were talking different platforms I understand that but how can this be > > addressed in Android terms? > > Well first we need to figure out what the problem is. If you know the > app, you can use the dumpsys debugging command (in particular "dumpsys > activity" and "dumpsys services") to see what is going on in the > activity manager and "logcat -b events" to see how processing are > coming and going. If processes running services are indeed getting > killed when they shouldn't be, we should look into what is wrong with > the system... but as far as I know, this is working as intended, and > will only kill such processes when needed because the foreground > processes requires so much memory (very very rare) or there are so > many applications trying to do things in the background that there > just isn't enough memory to do everything needed. The latter can be > just because you are doing too much or, unfortunately, there seem to > be many applications that leave services running when they really > shouldn't. > > So... a task manager? Probably not what you want. It -would- be > useful to have a UI to see all of the services that are running and > stop and start them and such, and there is an APIs in the current SDK > to at least let you find out about the running services: > > > http://code.google.com/android/reference/android/app/ActivityManager.html#getRunningServices(int)<http://code.google.com/android/reference/android/app/ActivityManager.html#getRunningServices%28int%29> > > Unfortunately we don't yet have APIs to let applications manually > start and stop them, though. > > As a general rule of thumb, I really think that most applications that > leave something running indefinitely in the background should have > some UI somewhere for the user to know it is doing this and stop it. > See, for example, the media player and its background music service. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
