Sophie_1983
Lurker
Well, before I answer that question I'll give some updated information, too.
Note the images above mention use of the autokiller set to my ROM's default values. I also repeated the same experiment, but used the "Aggressive" autokiller preset. Much to my surprise, when I ran the same trials all the way through, the ending configuration looked very much like the 2nd figure above - about 5.4 Mb of "free memory" (as reported by /proc/meminfo)
That sort of shocked me - I thought that maybe the autokiller wasn't working! So, I dug into the source code and discovered that there was a way to turn up the amount of information that the Android LMK logs to kernel messages (found in /proc/kmsg)
Code:adb shell echo '6' > /sys/module/lowmemorykiller/parameters/debug_level
Then, I ran the same experiment twice (clean up apps, start e-mail app, open up an individual e-mail) - using the default and the aggressive Autokiller presets once each.
What I found out was that indeed the autokiller was working: in the default (Autokiller) preset case, it killed off YouTube; but in the aggressive preset case, it killed off 18 different apps over a 30-second period.
So, that's good news - the autokiller works the way you would expect; what it optimizes for, though, is apparently not the same thing as "free memory for file cache". It seems a bit more subtle than that.
In any event, I was using the Conap/Decadenc3 "CFSv9" kernel - it is in pretty wide use now in the Eris Froyo ROMs. So, no - this was not a stock ROM. The stock ROMs do have the Android LMK built in to them, but they might be started with different threshold values than what CFSv9 uses. Additionally, I looks like the source tree for CFSv9 has some back-porting of changes in the LMK that are derived from the 2.6.34 Android kernel, so I can't guarantee that the stock kernels would behave identically with the same parametrization.
No, I have a few "junk" e-mail accounts for message boards and so forth, and I just handle them using the Android "mail" application. It was configured for those accounts, not my gmail account. However, I don't think it makes any difference whatsoever what mail account is involved - it's gonna happen if you click on any email with that particular app
There is a sort of workaround, if someone finds this "e-mail app autostarts a bunch of junk" behavior objectionable: log on to Gmail on a real computer, and set it up to pull mail from other accounts that you have - and then set up a Gmail filter to automatically "label" them with a label that is unique to that account. That way, all your mail could be managed through the Gmail app - even mail from different accounts. (You might need to check if the mobile Gmail app honors the settings that you can configure in the web Gmail client: it allows you to specify your sender e-mail address automatically depending on which account the e-mail arrived in. I think it does this, but you should check).
As for K9 vs. the Android e-mail app, I'm not sure - I don't know if two different apps can produce the same broadcast event. The claim that "in principle, any subsystem in Android can be replaced" suggests that K9 might produce the same broadcasts.
There's an easy way to find out though - use a Task Manager, FC most of the non-critical ones, and read an e-mail in K9. Then go back and see if a whole bunch of new apps have started.
The bottom line though, in all of this, is that Android "did the right thing" in every case: judiciously choosing to terminate applications when I tried to load too many of them simultaneously.
eu1
Thanks for your detailed analysis of the problem, However your Final Bottom line seems to contradict what you and everyone else is claiming about Android
It is NOT Android that is performing as intended it is the app "Autokiller", Android as you proved Does not kill the useless programs as needed.
Autokiller may work for you on this matter, but to me it is just another program running in the background sucking down memory and resources. System info shows it fluctuating from 8 to 17 MB of memory on my eris.
Besides the whole argument with Android die hards is that you dont need any type of task killer with it
