View Single Post
Posts: 702 | Thanked: 2,059 times | Joined on Feb 2011 @ UK
#41
Originally Posted by mscion View Post
Android seems to do multitasking better than it used to. Used to be when Android killed an app, like a document editor, I would lose the changes I made. Now if the same app is killed it looks like the changes are saved. Whether that is due to an improvement in the app or android itself, I can't say for certain.
It might be both. The app gets an onStop() message saying it's being stopped. The app can then decide what it needs to do.

If it doesn't do anything, the OS will still save the state of text in edit fields (for example) in a bundle. When you navigate back to the same instance, those are restored to the view.

Originally Posted by mscion View Post
Regardless, I wish it was me that decided whether the app is killed and not android. I would prefer, if the situation arises that there is no enough free memory to run an app, that the system tell me that I need to close some given set of apps or risk getting them killed. I would also prefer having a better swapping capability, even at the expense of performance, as the phones are pretty fast anyways. Regardless this may be a moot point once the phones have 6 to 8 gb.
IME it's moot with 2GB mostly and I'm not sure of the utility of manually managing resources when the computer can do that for you better most of the time for most of the people.

I think this discussion is clouded by years of Nokia phones with not enough RAM in them be they Symbian, Maemo, Meego or following on, Jolla and Sailfish who seem to have inherited that daft notion that they can squeeze a quart out of a pint pot.
 

The Following 4 Users Say Thank You to aegis For This Useful Post: