Related
Can't see why this is the case (but it obviously is) as long as I have lots of free disk space and not many apps running at the same time. Any logic in this?
I've been experiencing the same issue and wondering the same thing...
Sent from my Samsung Galaxy S GT-I9000 using Tapatalk Pro
There seems to be several things causing this, but the two key issues are:
The moviNAND (the internal flash drive/"SSD") firmware seems to have an issue with fsync() taking extremely long. E.g., it slows down whenever a file is written/updated on the internal storage.
RFS, the file system used by Samsung is buggy as hell and corrupts data after a while.
There are several topics on these issues in the Android Development forum. There are also several "lag fixes" trying their best to overcome these issues. Go check them out
Einride said:
There seems to be several things causing this, but the two key issues are:
RFS, the file system used by Samsung is buggy as hell and corrupts data after a while.
Click to expand...
Click to collapse
We have no idea if that is ACTUALLY true.. Just because fsck picked some things up on 1 phone, doesn't mean it happens everywhere.. Furthermore, it doesn't mean the problems detected affect operations
that has no truth at all about more apps slowing down the phone, my phone is the prove
Before jpk i didn't noticed slowdowns with aprox 100 apps, now i do on jpk =/
Prolly that all pictures/links/info stays in his workmemory?
probably cause some of them run in the system memory or run at startup
KaliKot said:
probably cause some of them run in the system memory or run at startup
Click to expand...
Click to collapse
Bingo!
and that is what most people does not realize
they need to Optimize the phone, most people take it for granted
the phone is not a phone, the phone is a mini computer that fits in your hands
just like your big desktop PC it can go crazy if you don't take care of it
AllGamer said:
Bingo!
and that is what most people does not realize
they need to Optimize the phone, most people take it for granted
the phone is not a phone, the phone is a mini computer that fits in your hands
just like your big desktop PC it can go crazy if you don't take care of it
Click to expand...
Click to collapse
Can you tell me why with the same apps installed on the Nexus it doesn't lag like the SGS?
Can you stop blaming users when is the phone which doesn't work as expected?
Oletros said:
Can you tell me why with the same apps installed on the Nexus it doesn't lag like the SGS?
Can you stop blaming users when is the phone which doesn't work as expected?
Click to expand...
Click to collapse
utter ****e -i have well over 100 apps on my sgs and experience NO lag whatsoever!
bonehooch said:
utter ****e -i have well over 100 apps on my sgs and experience NO lag whatsoever!
Click to expand...
Click to collapse
Utter ****e? Why?
it was mentioned many many times
just install autorunkiller and a good task manager then all the problems will be gone
stock ROM is very fast when you maintain the phone
AllGamer said:
it was mentioned many many times
just install autorunkiller and a good task manager then all the problems will be gone
stock ROM is very fast when you maintain the phone
Click to expand...
Click to collapse
With autokiller the phone is still laggy.
And please, stop thinking I'm stupid or I don't know a **** about smartphones, ROM's changing, firmware or knowing how a phone must run.
AFAIK this topic and its responses are for the OP
I have about 190 Apps installed and do not experience any diferene in overall speed of the phone. But only because i know that a lot of the programms start on boot and stay in background.
I have more than 15 apps turned off with the full version of autorun killer to prevent the auto restart of the apps. Otherwise the phone would definetaly slow down.
It´s really incredible what apps start on the boot!
TMReuffurth said:
I have about 190 Apps installed and do not experience any diferene in overall speed of the phone. But only because i know that a lot of the programms start on boot and stay in background.
I have more than 15 apps turned off with the full version of autorun killer to prevent the auto restart of the apps. Otherwise the phone would definetaly slow down.
It´s really incredible what apps start on the boot!
Click to expand...
Click to collapse
Do you need to be rooted ti use all of the functions in autorun killer? I am not rooted.
Can you compile a breif list of the "biggest culprits" to stop with this utility to gain back the most speed and efficiency? I am a bit nervous that I will stop the wrong items and somehow damage my phone...
Autokiller and task killers are not the solution here! Quick lesson on Android, and why having even A SINGLE BAD APP is going to ruin your whole phone!
Android has something called an 'Intent'. In order to start an app, an intent is made by your launcher or a button you press, and the Android system reads this intent and works out what app it needs to start up.
There is a second type of intent though, called a 'Broadcast Intent'. This is an intent that is sent out to anything that is registered to listen to it. This means that an app can register to listen to all sorts of events, such as battery level changed, application start, or a tons of other things. Even if the application is closed, if it is registered as a listener, Android will start it right back up so it can deal with the intent. If the intent comes every 5 seconds, Android will run this app every 5 seconds even if you have a taskkiller killing the app.
The only real solution is to not install apps which are bad! Finding bad apps is a real mission, too. Hopefully in the future, utilities will be available to let us track down these terrible apps, but till then, you'll have to work it out yourself.
yiannisthegreek said:
Do you need to be rooted ti use all of the functions in autorun killer? I am not rooted.
Can you compile a breif list of the "biggest culprits" to stop with this utility to gain back the most speed and efficiency? I am a bit nervous that I will stop the wrong items and somehow damage my phone...
Click to expand...
Click to collapse
No need for Root to use all features of Autorun Killer. I would disable only the apps you know and which you do not need at startup and running in background, such as (in my case) Paypal, App Center from Androidpit, Daily Briefing, Photoshop Express, Word Press, TweetCaster, etc.
Every of these apps works normal, even when deactivatet on startup.
So unless you do not disable system apps (must be previously set enabled in settings) you are safe.
RyanZA said:
(...)There is a second type of intent though, called a 'Broadcast Intent'. This is an intent that is sent out to anything that is registered to listen to it.(...)
Click to expand...
Click to collapse
Is there any possibility/app to show what is registered for which app?
watching the apps
Samga said:
Is there any possibility/app to show what is registered for which app?
Click to expand...
Click to collapse
There is an app called Autostarts at 0.95$.
It shows what is launched au startup, when you enable/disable wifi etc.
It think it gives insight on how apps seems launching out of nowhere.
I also reccomend Watchdog Task Manager Lite, the free version.
It does not kill anything, but notifies and logs the bad apps that consumes over a certain CPU percentage.
I am running auto nooter on my nc (lovin it) but i have noticed that the available memory is slowly leaking. On reboot, i usually have around 300 available and that number slowly but surely decreases until its so low that it reboots automatically.
I have advanced task killer installed and periodically kill all the tasks to make sure nothing is running in the background.
Any idea what might be causing this?
Advanced Task Killer is not helping you. Google has come right out and said Task Killers will do more harm than good on your Android device. Here is a good read:
http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
The fact that you can see an application's process "running" does not mean the application is running or doing anything. It may simply be there because Android needed it at some point, and has decided that it would be best to keep it around in case it needs it again.
...
Once Android determines that it needs to remove a process, it does this brutally, simply force-killing it. The kernel can then immediately reclaim all resources needed by the process, without relying on that application being well written and responsive to a polite request to exit. Allowing the kernel to immediately reclaim application resources makes it a lot easier to avoid serious out of memory situations.
Click to expand...
Click to collapse
czarjohn said:
I am running auto nooter on my nc (lovin it) but i have noticed that the available memory is slowly leaking. On reboot, i usually have around 300 available and that number slowly but surely decreases until its so low that it reboots automatically.
I have advanced task killer installed and periodically kill all the tasks to make sure nothing is running in the background.
Any idea what might be causing this?
Click to expand...
Click to collapse
It will not reboot when it runs out of ram. My suspicion is you're seeing the 'random reboot' problem that happens on the stock B&N ROM. See here for a workaround: http://nookdevs.com/NookColor_Issues
mrapollinax said:
Advanced Task Killer is not helping you. Google has come right out and said Task Killers will do more harm than good on your Android device. Here is a good read:
Click to expand...
Click to collapse
I totally agree with this on 2.2 upwards... Unfortunately 2.1 is a little more lax about memory handling, and can sometimes get quite slow and jumpy and can benefit from a flush. I use System Panel and exclude all of my important tasks and widget, and if I see my NC getting jumpy or such, I'll kill all (which excludes those already excluded apps of course). But auto task killers are always a bad idea.
mrapollinax said:
Advanced Task Killer is not helping you. Google has come right out and said Task Killers will do more harm than good on your Android device. Here is a good read:
http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
Click to expand...
Click to collapse
Thanks for the post, that was a great read and I am uninstalling my task killer now.
Mike
Regarding task killing, I recommend something like Watchdog to monitor apps as opposed to an auto-task killer. Watchdog has a really nice widget for monitoring system resources and in the rare occasion that an app starts misbehaving, it will give you a notification and the option to kill it. Otherwise letting the OS handle things itself is the best option. I've been using computers for a very long time and idea of leaving apps running seems counter-intuitive, but in my experience there is no reason to not trust what Google says about the issue.
czarjohn said:
I am running auto nooter on my nc (lovin it) but i have noticed that the available memory is slowly leaking. On reboot, i usually have around 300 available and that number slowly but surely decreases until its so low that it reboots automatically.
I have advanced task killer installed and periodically kill all the tasks to make sure nothing is running in the background.
Any idea what might be causing this?
Click to expand...
Click to collapse
i am also having these problems but im on honeycomb
i dont have any task killer installed but i installed one last week to check if my memory was leaking or if the rom was just rebooting
Great stuff here. Thanks for all the info. I think it was the random reboot since it did seem to happen most often when i was putting the nc in to standby.
Lots of good stuff here. Gonna miss the little green widget on my home screen, but i guess google knows best...
czarjohn said:
Great stuff here. Thanks for all the info. I think it was the random reboot since it did seem to happen most often when i was putting the nc in to standby.
Lots of good stuff here. Gonna miss the little green widget on my home screen, but i guess google knows best...
Click to expand...
Click to collapse
well i installed honeycomb preview v2 on my eemc from samuallhaff and it seems to remove this problem
i suggest you switch to his rom if you want the memory leaks to stop
luigi90210 said:
well i installed honeycomb preview v2 on my eemc from samuallhaff and it seems to remove this problem
i suggest you switch to his rom if you want the memory leaks to stop
Click to expand...
Click to collapse
Don't confuse "memory leaks" with "weird wifi sleep reboot bug".
You don’t need to change your ROM to get the best from your 2x, just a rooted stock ROM and a couple of apps that will change things dramatically. One thing I’ve noticed on the 2x is its memory management is too lenient and gets consumed quickly by background tasks etc. In no time I was down to 40-30Mb free memory and then my phone would run like a dog resulting in a reboot as the only solution.
Installing task and app killers are not the way, as they’ll only give you a short respite before the apps and background tasks you killed relaunch.
However, there is a solution.
1)Root your phone using SuperOneClick (piece of cake, instruction already on this forum)
2)Install “AutoKiller Memory Optimizer” by AndRS Studio free from the market
Optional
3) Install “Watchdog Task Manager” by Zolmut LLC (There’s a free or Paid version) I paid!
4) Install “Root App Remover” by Best of Best Android app
AutoKiller is not a task killer/manager it reconfigures Androids inbuilt memory manager to kill or suppress memory usage by applications and tasks. I now always have about 140-170MB free RAM at all times regardless of what I’m doing (but I do close my apps with the back button rather than click home)
AutoKiller Memory Optimizer Settings
I’ve used the ‘Extreme’ settings to ensure I have around 150MB free, and this makes a huge difference in everything I do with the phone.
----------Optional things you may want to consider-----------
Watchdog
Yeah, I know this is a task killer but Watchdog is different from other task mangers as it monitors CPU usage rather than free RAM, 3D Gallery for example is a CPU hog on my 2X, so I configured it to be killed if it consumes more than 30% CPU whilst running in the background, you’d be surprised what saps your battery!
Root App Remover
Uninstall the tosh supplied on the ROM, I removed the following, AndroidBackup (I use Titanium Backup), CarHome, F-Secure_Mobile_Security, SNS (If you’re not using the built in Facebook and Twitter app).
I also use LauncherPro with Beautiful Widgets to give my phone an almost HTC Sense look and feel and uninstalled LG Home using Root App Remover afterwards.
Hope it makes a difference for you, it did for me, vote if you like
What do you think having 140-170MB RAM free at all times actually does?
Guess what? Nothing.
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
We want to see some bench marks.
Thanks for sharing! My phone does become much more responsive
Sent from my LG-P990 using XDA App
I tried the app too and i can say that it works, I also did some of the advanced tweaks.
phone seems more responsive now.
Yes, me too. It's more responsive now. Also when I open app manager, the app list is a lot faster.I know it's more related to file read/write but still it's nice to finally able to browse with less waiting time.
Sent from my LG-P990 using XDA App
thx
good one and simple, thx
cann someone please post some benchmarks?
Here are some screenshots, tested with AnTuTu Benchmark
The first one is v10c stock, some apps like f-secure, carapp etc frozen, second one is with using autokiller memory with preset extreme, third one is to compare, this was while using cm7.1 rc
now we'll see if autokiller works stable ^^
edit: realized that with cm7 something seemed to be wrong with the sd-card, so don't forget to compare the single-scores
spadb said:
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
Click to expand...
Click to collapse
I'm sure Rusty knows what he is talking about. Thing is, this talk about "the more free ram the better" has been repeated so many times, and at the end of the day, it seems to be more about user preference.
The default LG ROM seems to allow tasks to run in the background until it reaches around 50MB free RAM, then it starts to close tasks one by one. For multi-taskers like me, this is fine, I love how I can switch between facebook, tweetdeck, miren browser, google+, gmail, and messaging without seeing the apps reload.
For some, they'd want to open a task, close it, and move on to another without looking back. I guess that is where the 100MB of RAM is good for.
If you guys will be looking at benchmarks, I can guarantee that you will have higher scores with RAM optimizers. As benchmarks do not test multitasking, they simply check the performance of your phone at that point in time. (Which is also why some modders pump up their CPU freq to insane values before doing their bench then posting it.)
I have nothing against AKMO, and I find it very effective for Froyo builds. But I would recommend that each user try it out themselves. It's not a "1 fix for all" thing.
spadb said:
I disagree, my phone runs way better now, maybe due to the fact that in part it’s killing more background tasks and enforcing better garbage collection. I want a phone that when I go to it, it responds immediately, I don’t want my phone to chug along whilst a new app is launched and android then decides to kill lower priority background tasks resulting in a choppy experience. These are my findings, and I wanted to share them. As a result using this particular application I now have a phone I can enjoy, rather than being frustrated by pausing, choppiness etc.
I would welcome your reasoning to why my post is useless, or explain why my phone is now running so well? Are you saying I’m suffering a placebo effect? Remember, this app is not a task killer, it reconfigures Androids internal memory management, see here:
http://andrs.w3pla.net/autokiller/details
and
http://androidforums.com/eris-all-things-root/158846-autokiller-vs-setcpu.html#post1452069
Finally, I’m very happy with the results.
Spadb (HTC G1, HTC HD2[CM7], LG Optimus x2
Click to expand...
Click to collapse
I'll just say this once: Free RAM is wasted RAM. If you feel´your phone is slow try adding some swap space
kiljacken said:
I'll just say this once: Free RAM is wasted RAM. If you feel´your phone is slow try adding some swap space
Click to expand...
Click to collapse
Does O2X already support swap space in EXT? (Or are your referring to VM heap?)
Doesn't play well with Fr19 at all (2 reboots in 2 minutes). Maybe I touched some settings that I shouldn't though.
akyp said:
Doesn't play well with Fr19 at all (2 reboots in 2 minutes). Maybe I touched some settings that I shouldn't though.
Click to expand...
Click to collapse
Yeah, FR19 is one of the more stable ROMs out there. Try full wipe then reflash maybe.
So, i've tried many different roms out there on my SGS. Never got any major issue with flashing or setting them up. Supposedly a custom rom has something improved but there was one think i kept thinking they all fail and i was wondering if anyone else feels the same.
I see random posts all the time telling how great multitasking in android is. But all these roms i keep using try their very best to close just about everything i have running. As far as i can tell, a few seconds after i switch to anything else, my first app gets closed. For example, everytime i'd leave browsing to manage what im listening to or sort out files on some file manager i'd find i needed to open my browser again instead of being there opened and waiting for me to return.
After searching for a while, the best explanation i could find out is to prevent battery drain from opened apps and to keep things smooth by having free ram, which kind of makes sense. Goes against what i read in a paper from google about android multitasking but fair enough.
Except the other day i happened to returned to a froyo stock rom (JS8 with darkcore 1.4) on my SGS and found out this does not happen. Apps stay open for the most part, except when i run something really heavy (like a game). And i dont really notice any performance decrease or extra battery drain from my usual usage.
Granted, i could be just told something along the lines "well dude, just use whatever works for you" and i totally plan on doing so, hence me experimenting, but thats not really my point. What i'm going for is, are custom roms being overzealous? because this really spoils any attempt at multitasking...
Again, this is not a rant of any sort, i was just wondering what are other people's thoughts about it
I'm suffering same problem
i want to have the browser and messenger at the same time
it close one after swetching to the other
i have 80mb free ram
I had the same problems, although lack of multitasking appeared on my stock rom, not a custom... sgs couldn't handle faceboom messager, viber, and a browser at the same time, everytime I switch from my browser to something else - it gets killed, which is frustrating
at the same time I saw how nexus s work, and how much free memory it has, compared to mine, the difference was huge!
I tried cyanogen at first, which was very close to stock nexus s, but it doesn't work good with sgs's camera and crashes once in a while
so eventually I installed JVT with voodoo and uninstalled different samsung stock apps, which gave me about 50mb of additional RAM compared to stock, and there doesn't seem to be any aggressive memory cleaners working, so I can now finally switch between all the apps I need
If you want the best roms for multitasking, go for the final builds of Froyo 2.2.1. They have plenty of free ram and are very smooth. I'd recommend Froyo ZSJPK. You can download it from XDA.
I think it depends on the ram settings in your ROM. The way android works is there are a bunch of system settings on how much ram to keep clear, and if it drops beneath certain values they start killing apps.
It's highly possible these values were tweaked in the custom roms, to improve the perceived smoothness and so on, but at the same time reducing multitasking. There's a trade off between performance and multitasking (guess why apple was so reluctant to add multitasking?)
I'm not really an expert on it, but I'm sure some quick searches around will find out where those values are and how to change them.. some rom/app probably even allows you to tweak them to your liking.
All Gingerbread roms do the same, closing apps after moving away from this, don't know why, but froyo didn't do this and ginger does.
I used to be like TS, clearing RAM because it might let the phone run smoother. After getting more exposed to Android, I realised that it could be logical to keep your apps in RAM instead of doing a cold boot again, meaning to close an app, open, close and open again, making it taxing on the phone.
So I tried to use up as much RAM as possible and it works just fine, it feels good. I believe the problem you have stated is that in your ROM, the task manager has instructions to clear the RAM once it hits a certain threshold. When it does, it starts to clear apps in different category, starting from what is known as empty apps, which are generally just apps you use and are not important to the android OS or rather independent from the OS.
In the new Samsung ROM, the threshold is set to 40MB, and it is working great for me. You can go to the android market and download "Galaxy Tuner" to set the threshold to a value you feel comfortable with. To multitask better, set the threshold as low as possible.
MaoJie said:
I used to be like TS, clearing RAM because it might let the phone run smoother. After getting more exposed to Android, I realised that it could be logical to keep your apps in RAM instead of doing a cold boot again, meaning to close an app, open, close and open again, making it taxing on the phone.
So I tried to use up as much RAM as possible and it works just fine, it feels good. I believe the problem you have stated is that in your ROM, the task manager has instructions to clear the RAM once it hits a certain threshold. When it does, it starts to clear apps in different category, starting from what is known as empty apps, which are generally just apps you use and are not important to the android OS or rather independent from the OS.
In the new Samsung ROM, the threshold is set to 40MB, and it is working great for me. You can go to the android market and download "Galaxy Tuner" to set the threshold to a value you feel comfortable with. To multitask better, set the threshold as low as possible.
Click to expand...
Click to collapse
ok i downloaded galaxy tuner but idk how to change threshold
Am running PA 3.60 which is great. I've now run some additional script that culls out and slims down the ROM and gapps. Again, everything runs great. I probably have a lot more memory free now than before. But I'm not sure what good that is.
Traditionally, we want to free up memory so we can install more apps - a2d and other methods help to keep things clear.
I don't want to do that - I want to be able to run more than one or two apps at the same time. But I don't know which memory types to clear up to do that.
The ROM is in, well, ROM, so making it smaller may not help free up memory if there's fixed 512MB used for it.
I know Android is actually running a lot of processes at once. What I mean is that if I load an app, say Candy Crush, then run another app, say Grindr, I can switch back and forth pretty much ok and each app resumes where it left off without any noticable reloading/refreshing. But if I then run another app, say Scruff, then as soon as I try to switch back to one of the others, it has to reload/refresh/restart. So clearly, there wasn't enough memory available to keep all 3 resident and it swapped some out or simply released it.
Logically, if I have more of a certain type of memory free, this will not happen as often. I know it depends on how much memory and other resources an app requires, but I don't need to get into that level of analysis yet. First and foremost, what sort of memory should I try to make as much of as possible to let me swtich between apps without so much reloading?
douginoz said:
Am running PA 3.60 which is great. I've now run some additional script that culls out and slims down the ROM and gapps. Again, everything runs great. I probably have a lot more memory free now than before. But I'm not sure what good that is.
Traditionally, we want to free up memory so we can install more apps - a2d and other methods help to keep things clear.
I don't want to do that - I want to be able to run more than one or two apps at the same time. But I don't know which memory types to clear up to do that.
The ROM is in, well, ROM, so making it smaller may not help free up memory if there's fixed 512MB used for it.
I know Android is actually running a lot of processes at once. What I mean is that if I load an app, say Candy Crush, then run another app, say Grindr, I can switch back and forth pretty much ok and each app resumes where it left off without any noticable reloading/refreshing. But if I then run another app, say Scruff, then as soon as I try to switch back to one of the others, it has to reload/refresh/restart. So clearly, there wasn't enough memory available to keep all 3 resident and it swapped some out or simply released it.
Logically, if I have more of a certain type of memory free, this will not happen as often. I know it depends on how much memory and other resources an app requires, but I don't need to get into that level of analysis yet. First and foremost, what sort of memory should I try to make as much of as possible to let me swtich between apps without so much reloading?
Click to expand...
Click to collapse
Try enabling zram, I haven't tried it personally but its supposed to allow for more multitasking.
Sent from my Nexus One using xda app-developers app
Moved To Q&A
You may of considered it dev based, but its a question so belongs in the Q&A section.
I've tried ZRAM now for a couple of days but makes no difference. I also have the problem on another Android device. I'm convinced its some sort of design limitation of the opsys or something. When I start up Grindr, it takes a long time to load all the images, make connections, etc. Then I start of Gruff, and it does the same. As long as I don't try to go to another app, I can flip between the two of them without them restarting/reloading/reinitialising themselves. That is clearly because their pages didn't get swapped out of memory or flagged for deletion and deleted.
But if I do something else, or even try to use additional functions within either app, its too much and the next time I try to flip to the other app, it has to reload and reestablish connections etc.
Its not just those apps either. The same with a game like Candy Crush. Or many many apps.
So either my devices don't have enough memory of some form to allow many concurrent apps to run without being swapped out, or Android can't handle it and unnecessarily swaps out or deletes a process's memory pages to make room for the next process, >>> even if the device has plenty of memory<<<.
I don't know which type of memory the opsys needs if this is the case. I'd like to know so that i can make sure there's ample available so that this constant restarting doesn't keep happening. It seems stupid to me that Android does this if the device has got "heaps" of available memory (no pun intended). Newer devices will continually have more and more built in memory, so if Android is doing this arbitrarily and not because of space issues then its, well, stupid.
I have to assume its my devices that are the problem. They're both old (Nook Color, Nexus One). But with the NC, I'd assume we can partition some of that 5GB for use as main memory to run lots of processes concurrently, without this annoying swapping/page deletion/forcing re-inits all the time.
I'm also having problems figuring out where in XDA to post this question - its not NC specific, or dev specific, but I need answers from people that know the Android architecture so I can work out if its possible to stop this from happening.