Database Users

Browser reloading pages by ifself bug

Ever since I have my HTC Magic on Vodafone UK, I have that utterly annoying issue of Magic's internal browser reloading webpages that were previously loaded and switched into background. Simple example: I load a webpage, making sure it's fully loaded. Then I go back to home screen, play around with icons or other apps etc., or open new browser window and load another page. After short while, when I go back to that first loaded page (already fully loaded and sitting in the background) - I get blank browser window, and page gets reloaded from the scratch. Uber-annoying, especially when I try to get few pages pre-loaded for later reading while in the Tube.
There is a bug floating around Android's bugtrack: http://code.google.com/p/android/issues/detail?id=2171 - however I was wondering whether other Magic users are experiencing same thing and if there's any workaround for this?

eva_d said:
Ever since I have my HTC Magic on Vodafone UK, I have that utterly annoying issue of Magic's internal browser reloading webpages that were previously loaded and switched into background. Simple example: I load a webpage, making sure it's fully loaded. Then I go back to home screen, play around with icons or other apps etc., or open new browser window and load another page. After short while, when I go back to that first loaded page (already fully loaded and sitting in the background) - I get blank browser window, and page gets reloaded from the scratch. Uber-annoying, especially when I try to get few pages pre-loaded for later reading while in the Tube.
There is a bug floating around Android's bugtrack: http://code.google.com/p/android/issues/detail?id=2171 - however I was wondering whether other Magic users are experiencing same thing and if there's any workaround for this?
Click to expand...
Click to collapse
Is it a bug or is it just that the web browser has been moved off RAM to make space for another application so that when its re-opened, it has to reload everything again.
If you load a website that is just text only without any graphics or javascript and then go to another application and come back, it will not be reloaded, because the footprint is small.

dwang said:
Is it a bug or is it just that the web browser has been moved off RAM to make space for another application so that when its re-opened, it has to reload everything again.
If you load a website that is just text only without any graphics or javascript and then go to another application and come back, it will not be reloaded, because the footprint is small.
Click to expand...
Click to collapse
Yes, I can understand this point of view, however I'd still regard this as a bug, or at least as a feature that massively undermines user experience as for internet-centric mobile device...
In fact, this is the very first device I've had in my hand that has such 'feature', in every other phone or internet tablet (like Nokia N810) that has multi-window browser, I am able to load many webpages simultaneously and keep them persistent in the background. The new and shiny, internet-centric HTC Magic suddenly offers that 'magic' feature of saving RAM at a cost of utterly horrendous user experience...

dwang said:
Is it a bug or is it just that the web browser has been moved off RAM to make space for another application so that when its re-opened, it has to reload everything again.
Click to expand...
Click to collapse
Anyway, content should then have been cached on sdcard (or internal memory).

have you tried swapper?
http://forum.xda-developers.com/showthread.php?t=483110
that extends the internal ram out to flash so maybe that will help.
Seems to work fairly well. I can have imeem streaming and other stuff and the browser pages still stay in "memory" and aren't reloaded.

dwang said:
have you tried swapper?
http://forum.xda-developers.com/showthread.php?t=483110
that extends the internal ram out to flash so maybe that will help.
Seems to work fairly well. I can have imeem streaming and other stuff and the browser pages still stay in "memory" and aren't reloaded.
Click to expand...
Click to collapse
Good idea, but I'd need to root my phone first, which is actually quite good excuse to do it.
Thanks for a tip!

eva_d said:
Good idea, but I'd need to root my phone first, which is actually quite good excuse to do it.
Thanks for a tip!
Click to expand...
Click to collapse
yeah, i've been using it for a few hours and once everything is loaded into memory and swap, and its not bad and I haven't encoutered a browser page reload yet.
Of course when a swap from flash to memory occurs, there's a pretty significant pause, but thats to be expected.

Just a quick update, I've finally managed to install swapper and set the swap space to 32MB. It helps to the issue, however when many other windows are opened, there is still that reloading issue...
I guess it's not a bug, but just a feature of Android and its 'clever' memory management. Fingers crossed that they would improve it in future versions...

Hero "multitasking"

It started driving me mad. If I minimize browser, I can't be sure it won't close. Not only minimizing for longer periods, but short ones as well - wanted to reply an sms when a page was loading, but when I got back to it, it started over. And all the loaded tabs were gone! Saving states my ass, it takes time to load a page from zero and only the active browsing window remains. How to make this "multitasker" multitask?

does this also happen if you return to the browser by holding home?

kendong2 said:
does this also happen if you return to the browser by holding home?
Click to expand...
Click to collapse
Yes, that's the only way I switch betwen apps.

Have you installed the 'system-based' taskiller mod by any chance (you know, the one that was announced here that automatically keeps memory free by modifying the default thresholds for killing apps)?
If so, I reckon that's the issue! Either that, or you have too much running, so popping the browser into the background makes it a background task and it gets killed cos you're really short of RAM.
Let us know if you have used the tweak though...

@kengdong...
it doesn't matter how you change the apps.
For android it's the same, whether you tap an icon on a homescreen/list or whether you select it from the "task switch" thing... all that does is listing the last recently used applications but still tapping them results in the same internal action.
Source: Android SDK Documentation

I've had pretty much the same issue since I got the phone back in November (I guess I've just gotten used to it by now). I'm never really sure when I switch back to the browser if it will retain the page loaded and any other windows, or if it will reset, close the other windows, and have to reload the active page. I'm on the stock Telus ROM, no custom ROM, not rooted, no tweaks, nothing extra (I've been waiting patiently for 2.1 to come out before messing with custom ROMS).

olafos said:
Source: Android SDK Documentation
Click to expand...
Click to collapse
thx for the heads up, i wasn't sure about this, actually i was asking to maybe get an answer to this worked

anon2122 said:
Have you installed the 'system-based' taskiller mod by any chance (you know, the one that was announced here that automatically keeps memory free by modifying the default thresholds for killing apps)?
If so, I reckon that's the issue! Either that, or you have too much running, so popping the browser into the background makes it a background task and it gets killed cos you're really short of RAM.
Let us know if you have used the tweak though...
Click to expand...
Click to collapse
No, I have stock rom and I have never used any task killer or related app / tweak.
And I don't run too much stuff.. only music player, messaging and sense's facebook perhaps. If music player is paused, why can't it quit it instead... I prefer multitasking of my past htc s730 which had like 7 megs of free ram after booting.

Even after a hard reset, this behavior remains.

i dont know.. it works fine for me....
1.. maybe there is a setting in the browser.. to always refresh.
2.. you have a repair issue.. Need to take it in to your local service provider repair center. Let them see your issue.

Dan330 said:
i dont know.. it works fine for me....
1.. maybe there is a setting in the browser.. to always refresh.
2.. you have a repair issue.. Need to take it in to your local service provider repair center. Let them see your issue.
Click to expand...
Click to collapse
Come on, it's no hardware issue. Most of the time the browser stays, but u just can't be sure about that because it sometimes just closes. I think that it's an issue with Android's STUPID memory management, which also has a scheduled "quit all" script.
Yesterday I opened up a few articles on the browser and decided to read them later. This morning they all remained and I was pleasantly surprised I could read them. This very moment, though, they are gone by now even though I haven't quit the browser - probably that 'quit all' script kicked in.
There could be something in settings, where you could chose apps which would not close ever unless quit..
I would love if Android apps were quitable without any automatic mem management.

Suggest to grab AutoKiller or MinFreeManager, which are just frontends to Android's memory management (also they reapply settings at boot time, as the system file that's being modified is reset every boot.)
See what your current settings are, and lower them (e.g. use "moderate" preset). Just search XDA for autokiller or minfreemanager for more info.

Pressing home should only move that application to the background (pressing back should close it).
If you are pressing home and applications are still closing then there must be a task killer of some sort in place closing it for you.

Lennyuk said:
Pressing home should only move that application to the background (pressing back should close it).
If you are pressing home and applications are still closing then there must be a task killer of some sort in place closing it for you.
Click to expand...
Click to collapse
You obviously have not read the topic.
No task killers, tasks dont neceaarily close, its juast that u cant be sure they will remain in memory.

Lennyuk said:
If you are pressing home and applications are still closing then there must be a task killer of some sort in place closing it for you.
Click to expand...
Click to collapse
Yes - it's the standard Android process management rather than a 3rd party task killer.
I guess the browser is given a low priority and is one of the first apps to be killed.
Regards,
Dave

[Q] Lack of RAM - any solutions? HTC DZ

I'm getting quite annoyed at my phone's lack of RAM.
I browse the internet and constantly open new windows (up to the max 4 allowed by the HTC browser, but that's another story) so that I can quickly go back a page when I need to.
If for some reason I go and use a couple of other apps on the phone, and then come back to the browser I constantly find that the oldest 3 pages have dropped completely out of RAM, and the 4th one has as well, and that last one alone loads up again.
This is annoying, time-consuming and messes up my browsing session. Is there some way I can prioritise the browser so that most other apps get killed off before it does?

setspeed said:
I'm getting quite annoyed at my phone's lack of RAM.
I browse the internet and constantly open new windows (up to the max 4 allowed by the HTC browser, but that's another story) so that I can quickly go back a page when I need to.
If for some reason I go and use a couple of other apps on the phone, and then come back to the browser I constantly find that the oldest 3 pages have dropped completely out of RAM, and the 4th one has as well, and that last one alone loads up again.
This is annoying, time-consuming and messes up my browsing session. Is there some way I can prioritise the browser so that most other apps get killed off before it does?
Click to expand...
Click to collapse
Try using firefox instead on the defualt browser .its not perfect yet but its getting
better and better with every beta release .

I don't think an alternate browser will help with Android unwantedly killing off processes.
Incidentally, I tried Firefox a couple of months ago and found it to be completely unusable - I take it it's worth checking out again now then?

Another possibility is to set the Android memory manager to be less aggressive in removing things from memory (you can use an app like AutoKiller to change the settings easily---try tweaking the settings to see if helps with your usage model).
I know AutoKiller will also allow you to lower the oom value for the process (the lower the oom, the less likely the memory manager will kill it in the background), but I don't think this will help for the browser (since the OS will dynamically change its oom each time you bring it to the foreground and send it to the background again). If someone knows a way to make the oom value permanently lower, that sounds like exactly what you want.
Maybe someone else has some ideas. I know often times launchers will have the option to keep themselves in memory, and CM6 has the option to keep messaging in memory (more like your situation), so it should be doable.

setspeed said:
I don't think an alternate browser will help with Android unwantedly killing off processes.
Incidentally, I tried Firefox a couple of months ago and found it to be completely unusable - I take it it's worth checking out again now then?
Click to expand...
Click to collapse
defo ,its much better now i figured since you were annoyed by 4 tab limit
you might find firefox helpful. because it doesnt have limit or if it does its more than 4 for sure also it has an aption called (your tabs from last time) which again i think
you will find it usefull ,you can also sync it with you pcs firefox too .
EDIT: I just tried it to make sure, even if you reboot your phone
and open firefox again you can just press on (your tabs from last time)
and it will restore them all.

The way I see it there are a few things you can do...
Firstly, you could try a renice script. It does what other people have suggested and changes the oomph value to what you like. It was commonly used on the g1 for the dialer so that you wouldn't miss phone calls lol. Its easy to do if you know the syntax, I would make you one myself if I was near a computer lol.
Another thing you could do is try an aosp/CM based rom, as those generally have much, much lower ram usage compared to sense.
Lastly you could try a different browser. There are so many to choose from I'm sure one will fit your needs.
Sent from my HTC Vision using XDA App

I use autokiller on my DZ, you have to have root to use this tho... quite satisfied about it, almost all the time 90+ free ram even when doing heavy stuff... quits the unused shizzle...
cheers

I HIGHLY recommend Dolphin Browser HD.
It is significantly faster than the stock Browser and I have had no issues with Android closing it down. One feature I like is that there is actually an 'Exit' button in the menu for those individuals who have OCD like me and don't like the Browser running in the background when not wanted.
Thus far, this is the best mobile Browser I have used. That being said, I have not tried Firefox and have been a regular user of Opera Mini in the past on other devices.

You should try miren browser once, i'm using it now instead of dolphin hd, and there is a exit button in the menu to. I think its better styled, it has got all the features of dolphin HD without all the bloating around... no gestures tho
cheers

I think its more of poorly optimized software because im pretty sure that google devs don't even utilize the full 512mb of RAM in 2.2. Chances are its the HTC sense limiting you.
Sent from my T-Mobile G2 using XDA App

Yeah I don't think this issue is anything to do with a lack of RAM.

I may try another ROM, however I'm just not up for flashing all the time like I used to with my old Desire or G1 before that. I want a 100% working ROM, preferably something that allows overclocking with a kernel that doesn't break stuff.
And I also want my HTC phone dialler/contacts as well, not vanilla or a cheap copy from the Market. Oh, and I hate the vanilla lockscreen - it's just hard to operate compared to the Sense one. I don't know why it's so hard to unlock side to side on Android - the iPhone takes a little flick and it's unlocked - vanilla Android is like a mission to ensure I've dragged it far enough across to unlock.
And I don't want my keyboard or capacitive keys or quick keys mullered up (I am running a Euro DZ).
If these issues can be dealt with easily when setting up the ROM/phone then I'm prepared to devote a little time to doing it.
So - any suggestions, please?

dont use htc sense roms.

I'm running the virtuous sense rom with his advanced kernel, ive ran the normal rom about 2 weeks, and ive yet to see differences other then a huuuuuuuge speed increase... i would just try it once if i were you its such a relieve...

I played with the latest over the weekend. I ended up uninstalling it. I'd hit a page with scripting and then firefox would lock up and crash.
Web2Go isn't perfect, but at least it doesn't crash as often.

This has nothing to do with RAM. This phone handles RAM just fine. Use Miren and thank me later. It's the best browser by far!

mr.boonet said:
You should try miren browser once, i'm using it now instead of dolphin hd, and there is a exit button in the menu to. I think its better styled, it has got all the features of dolphin HD without all the bloating around... no gestures tho
cheers
Click to expand...
Click to collapse
No text reflow = showstopper.
Unless I'm just being blind, I can't find any way to enable this in the settings for Miren.

It's sense. Sense roms use way more RAM than vanilla roms do. Also check out dolphin HD or dolphin mini browser.

Another issue I'm having which points to lack of RAM (whether this is due to Sense sucking it all up or not) is that programs do not stay in in RAM for that long, ie I go away from an app then return after using a few other apps (not massive games or anything) and when I return the first app's UI has been kicked out of memory and has to load up again, causing anything between a momentary (dialler, mesaging) to an annoyingly long (browser, maps, market) white screen, as data is downloaded again.
People talk a lot of sh*t about the iPhone, but cacheing (caching? sp?) a copy of the last screen for each app before it's closed so you instantly get a visual image of the UI of the app following the opening animation is a pretty good idea IMO.
Has anyone here used the Desire HD? I would think with the 768MB of RAM on that badboy this would be less of a problem.

setspeed said:
Another issue I'm having which points to lack of RAM (whether this is due to Sense sucking it all up or not) is that programs do not stay in in RAM for that long, ie I go away from an app then return after using a few other apps (not massive games or anything) and when I return the first app's UI has been kicked out of memory and has to load up again, causing anything between a momentary (dialler, mesaging) to an annoyingly long (browser, maps, market) white screen, as data is downloaded again.
People talk a lot of sh*t about the iPhone, but cacheing (caching? sp?) a copy of the last screen for each app before it's closed so you instantly get a visual image of the UI of the app following the opening animation is a pretty good idea IMO.
Has anyone here used the Desire HD? I would think with the 768MB of RAM on that badboy this would be less of a problem.
Click to expand...
Click to collapse
I've now installed Enomther's Official rom - what a difference to the speed of the phone! It absolutely flies, even when clocked at a lower CPU speed, and it appears to retain stuff in memory a lot better than the standard Sense rom. Also, there's over 100MB more of free RAM afte a fresh boot.
I'm definitely sold on the efficiency of stock Android, but I'm now missing some of my HTC goodies... I don't think anyone can deny that the HTC dialler is a different level to the rudimentary Android one. And I am missing my HTC browser - that seems a bit smoother, and the text reflow is more reliable, the stock browser seems a bit temperamental on that front.
Other than that, I can live without all the other Sense stuff. So my next question is, can the dialler and browser be installed on my new rom? Do they have any dependencies which would prevent me using them? How would I go about ripping the apps from the HTC rom? I'm an ADB noob so I need some kind expert to tell me how

[Q] browser auto-refresh

I cant find any xoom/honeycomb Information on this problem so i wanted to see if i am the only one frustrated by this....
If i have multiple tabs open in the browser and go do something else, then come back to the browser later, it will automatically and annoyingly refresh all the tabs at once. This seems so unneccesary and slows down the zoom.
Anyone have this/hate this problem?

This is happening to me as well on my Samsung Vibrant since I updated to Froyo. I posted this a while ago, but nobody seems to be bothered about it.
http://forum.xda-developers.com/showthread.php?t=958494
This is very annoying and time consuming as well as it is a battery and data eater.
I've look around with no luck.

LeoLopezDO said:
I cant find any xoom/honeycomb Information on this problem so i wanted to see if i am the only one frustrated by this....
If i have multiple tabs open in the browser and go do something else, then come back to the browser later, it will automatically and annoyingly refresh all the tabs at once. This seems so unneccesary and slows down the zoom.
Anyone have this/hate this problem?
Click to expand...
Click to collapse
Mobile devices simply dont have the RAM/cache to keep the pages in memory. If you leave the browser and do a bunch of things it must release the page so you CAN do those other things.
Its nothing XOOM specific. Just remember, even though the xoom is very powerful its not a PC.

El Daddy said:
Mobile devices simply dont have the RAM/cache to keep the pages in memory. If you leave the browser and do a bunch of things it must release the page so you CAN do those other things.
Its nothing XOOM specific. Just remember, even though the xoom is very powerful its not a PC.
Click to expand...
Click to collapse
A gig of ram... shouldn't that be enough to keep a few pages open?

bogatyr said:
A gig of ram... shouldn't that be enough to keep a few pages open?
Click to expand...
Click to collapse
Yeah it will keep a few tab open if they are low resource pages and you haven't accessed 20 apps before you go back to the browser.
Like I said this isn't a pc.

El Daddy said:
Yeah it will keep a few tab open if they are low resource pages and you haven't accessed 20 apps before you go back to the browser.
Like I said this isn't a pc.
Click to expand...
Click to collapse
Yep people don't realize that on your PC when you run out of RAM you can page to disk. On Android unless you have some special stuff going on when you run out of RAM there isn't anything to do but pull the app that was active longest ago and remove it from memory.

Any chance the Atrix is exempt from this Android "feature"?

My single biggest gripe with the Android OS is the way it closes backgrounded applications without the user's permission, unrelated to available memory but rather amount of time the app is left idle. I can be editing a Word document in QuickOffice or Docs-to-Go, then get an incoming call, answer it and talk for ten minutes, only to find my Office application has been closed and all my changes have been lost.
I am wondering if perhaps by some small miracle, the Atrix has been programmed differently from other Android devices NOT to do this, because of its intended function as a desktop substitute via the Webtop environment. No one ever wants their desktop/laptop computer shutting down applications because they left to grab a coffee for ten minutes, so I'm hoping maybe the Moto devs took this into account and somehow turned off the "auto close backgrounded apps if left idle for X minutes" functionality of Android.
It's only a slim hope I'm holding out regarding this, but maybe someone can answer definitively one way or the other.. anyone know for sure?

No, it's still the same operating system. The Webtop is completely separate from Android.

Nope. I'm slightly annoyed every time adw ex is background killed just because I was reading my email, and it has to completely reload.
Not only that, but gingerbread took away the option to keep the launcher persistent
Sent from my MB860 using Tapatalk

If your app doesn't restore the previous state on restart, then the app developer is to blame, not android. Just saying

turl1 said:
If your app doesn't restore the previous state on restart, then the app developer is to blame, not android. Just saying
Click to expand...
Click to collapse
Sorry, but Motorola's responsible for any killing of webtop. X isn't designed to be magically killed the way that Android kills things.

It is worth pointing out this is less of an issue on Atrix given the 1Gb of RAM... but yes, this is still Android and as such the memory management is ultimately the same.
I have had cases on the Atrix where I am playing Angry Birds, get distracted and browse the web, forget I was playing the game... then return to the game 1 hour later to find it's still running as I left it. This certainly would NOT have happened on my Galaxy S!

Sogarth said:
Sorry, but Motorola's responsible for any killing of webtop. X isn't designed to be magically killed the way that Android kills things.
Click to expand...
Click to collapse
We were talking about android apps though

turl1 said:
If your app doesn't restore the previous state on restart, then the app developer is to blame, not android. Just saying
Click to expand...
Click to collapse
Most apps do restore previous state.
They also take a while to do so.
On the other hand, my biggest gripe is resolved: cm7 has an built in option under he performance setting to keep the launcher persistant, so I don't really care anymore
Sent from my NookColor using Tapatalk

From my understanding of Android programming, it only closes Background tasks automatically, all apps are started as Background tasks by default, it's up to the app to tell Android that it's a Foreground app, and it can't be closed automatically.

Hmm, I've used QuickOffice and left it alone for a while (got distracted, went on the internet, checked emails, turned off the screen, etc) and it was still all there when I came back. Does it happen to you frequently?
As a test I just made a new word document and typed some random stuff into it. I'll leave it alone for a day in the background and see if it's still there tomorrow...

Restoring to previous state works for some types of apps, but for others it's not a viable solution. For example streaming radio applications or chat programs like eBuddy, Fring, Skype etc. These need to be left running constantly in the background, not just restored to where they left off, because otherwise you're not available to be contacted through them while they're closed/offline. Some of those apps use the workaround of an ongoing notification to avoid being shut down, but that is really just a trick that developers shouldn't have to resort to.
I find that both QuickOffice and Documents-To-Go get shut down constantly when left idle in the background, even with nothing else running or using memory, and after only ten minutes or so of idle time. And I always lose all unsaved changes - the previous state is never restored.
What seems to happen is this: I can leave a document in the background for hours, and then come back to it okay, IF I don't do anything else in between. But if before returning to the open document, I launch ANY other app first, even a very small footprint one like a notepad, THAT is when the previously backgrounded apps like QuickOffice get closed by Android. It seems that Android's auto-close-after-idle activity is triggered by the next time the user launches something else. That's when the check is done and idle apps get shut down.
There are free app-switching utilities like AltTabApps and Smart Taskbar which allow you to easily see which windowed apps/tasks are still currently running. Using these I have tested and confirmed that I can actually leave quite a few things running idle in the background for a full day, and every time I keep checking, they are all still there and open, waiting to be switched back to. But then as soon as I open a new small app, and all those others have been sitting there idle and backgrounded for long enough, *POOF*, they all get closed instananeously the moment the new app is opened.
And like I said it's not related to memory, because I can see how much is free, and the app I end up opening is very small as well.
So if you're going to test, don't just leave it for a day and then try to come back to it. Before you go back to it, open something else that ISN'T already running (such as email or text messaging which are always quietly open already).. choose a brand new app to open and then try to go back to your Quickoffice document. On the three or four Android 2.2 devices on which I have tried this, I have never, ever been able to return to a document without losing all changes.
Sorry for the long message.. just important to point out the mechanism at work so as to avoid a false positive result, since there are cases when you can return to documents when you haven't opened anything else new in between.

Ok, I see what you mean now. Tried it the way you said and left it for a good while and it did indeed lose the stuff I had typed. I can see how that would get frustrating...
Have you tried using a task manager and telling it to keep QuickOffice alive (i.e. for the system to never kill it)? Although this will probably eat your battery, so I guess only do this if you really need it. I doubt there's a way to turn the functionality off entirely, as it's a pretty core part of making multi-tasking work on low power consumption devices.

Even with my devices rooted, no task manager I have ever seen or tried has successfully been able to override the core Android system to keep-alive any app that I've specified. These utilities seem only to be able to affect their OWN task-closing habits or aggressiveness levels, but not to prevent the OS from doing its own thing separate from their internal settings.
Not to get side-tracked into an OS comparison, but I have an HTC Leo HD2 running Windows Mobile 6.5, and it is able to keep a dozen applications open in the background indefinitely, without ever slowing down or draining the battery. I can leave Word Mobile, Coreplayer, Internet Explorer, Opera Mobile, Windows Messenger, and a large handful of others all open and still get a strong couple of days out of the battery. Surely if an older OS like WinMo (and even WebOS and Symbian) can do this, Android should be capable of it too. For this very reason unfortunately, I have had to stick to Android 2.1 or WM devices as I need my apps to stay open until I decide to close them. I am always hoping though that a new 2.3 or 2.4 device will come along that allows disabling of this functionality by the user.

paleozord said:
Even with my devices rooted, no task manager I have ever seen or tried has successfully been able to override the core Android system to keep-alive any app that I've specified. These utilities seem only to be able to affect their OWN task-closing habits or aggressiveness levels, but not to prevent the OS from doing its own thing separate from their internal settings.
Not to get side-tracked into an OS comparison, but I have an HTC Leo HD2 running Windows Mobile 6.5, and it is able to keep a dozen applications open in the background indefinitely, without ever slowing down or draining the battery. I can leave Word Mobile, Coreplayer, Internet Explorer, Opera Mobile, Windows Messenger, and a large handful of others all open and still get a strong couple of days out of the battery. Surely if an older OS like WinMo (and even WebOS and Symbian) can do this, Android should be capable of it too. For this very reason unfortunately, I have had to stick to Android 2.1 or WM devices as I need my apps to stay open until I decide to close them. I am always hoping though that a new 2.3 or 2.4 device will come along that allows disabling of this functionality by the user.
Click to expand...
Click to collapse
The keep persitant value was depreciated from android alltogether in 2.3. However, if cm7 can be set to keep alive the launcher and the messenger app, then it stands to say there is still a way around this.
Sent from my NookColor using Tapatalk