Quote:
Originally Posted by FalconFour
Now, what about some misbehaving app? Something that demands too much OS attention, more attention than I want to give it (personally)? Something I just one-off launched, didn't like, now "go away"? It keeps running. It'll keep running, too, if it wants to keep polling a network resource for updates. Or wants to keep monitoring for input. So, say I started running some Twitter app, and signed in. Bleh, I don't like twitter, I go back home. It keeps running. Facebook.
|
Dont use improperly coded applications, your right they are out there, but that isnt androids fault, they have throughly documented how to write applications that conform to the lifecyle.
As for applications like Twitter and Facebook, well first let me just say, if you run a task killer and see apps "running" that doesnt mean they are in the Foreground or Service lifecyle. Applications that are suspended will also show in this list, that DOESNT mean they are eating up resources. Anyway, applications like twitter and facebook are written correctly so they are suspended when not in use, they will come alive to sync if they are in the background, but you can easily turn this off.
And I answered you dalvik concerns a few times.
As much as I would like to continue this class, I am done feeding this fire and have much more productive things to be doing. Im sorry you are confused and dont understand how things work. I tried to help you but you obviously have formed your own concepts and ideas of how these things work.