I find it interesting that there is no exit button for the in-built browser in Android (at least in 3.2 on my Samsung Epic). What could be the reasoning behind leaving it out? The browser uses a lot of RAM, and if I want to exit out of it, I have to either keep going back to the starting page of the browsing session, or close it from Task Manager. I am perplexed. Could someone comment on this?
Sent from my SPH-D700 using XDA App
incisivekeith said:
I find it interesting that there is no exit button for the in-built browser in Android (at least in 3.2 on my Samsung Epic). What could be the reasoning behind leaving it out? The browser uses a lot of RAM, and if I want to exit out of it, I have to either keep going back to the starting page of the browsing session, or close it from Task Manager. I am perplexed. Could someone comment on this?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
They probably feel strongly enough that Android is capable of handling RAM on its own. Which is why they look so down upon task managers. It's better to just press the home button, let the OS do what it will with free RAM and when you open it again, it'll either snap right back or load up the page you were on again.
This isn't Windows. There aren't exit buttons in apps for a reason. People more qualified than both you and me discourage task killers because they know how Android works.
Android is built to manage ram on its own, so let it do its job. Don't worry about what's using ram, spend that time enjoying your device. I promise that if you need the ram for something else then it'll be there.
Supersonic Evo 4G | MIUI | Tapatalk
In a perfect world I would agree but who knows if someones crappy code (apps aside from internet) has a leak and keeps loading itself and draining the battery. I have read many args against task killers but when I use one my phone lasts longer. Placebo effect maybe but hell it's free and makes me think I'm in control ;-)
If you read my post again, you will notice I never mentioned task killers; instead, I was referring to the in-built Task Manager (hence "T" and "M" are capital), which I use to kill the in-built browser.
From experience, the method of shuffling ROM when needed, causes battery drain, and the more RAM that is occupied (with apps not closed completely) the more battery it takes to refresh the RAM. So, it is much better to have more empty RAM, from what I understand.
I use Dolphin HD and my battery is fine, but I just can't seem to make peace with the fact that the browser occupies 70 MB in the RAM and there is no exit button. I hope my question is clear now.
Sent from my SPH-D700 using XDA App
incisivekeith said:
If you read my post again, you will notice I never mentioned task killers; instead, I was referring to the in-built Task Manager (hence "T" and "M" are capital), which I use to kill the in-built browser.
From experience, the method of shuffling ROM when needed, causes battery drain, and the more RAM that is occupied (with apps not closed completely) the more battery it takes to refresh the RAM. So, it is much better to have more empty RAM, from what I understand.
I use Dolphin HD but I just can't seem to make peace with the fact that the browser occupies 70 MB in the RAM and there is no exit button.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Unused RAM is wasted RAM so no free RAM is not better.
You can exit dolphin by pressing menu and then exit...
---------------------------------
Sent from my LG Optimus V using Tapatalk
Again, my posts are only about the native browser, not any other browser. I mentioned Dolphin merely to convey I don't use the native browser but just wondering about the exit button for the native browser.
Sent from my SPH-D700 using XDA App
It's more easy to newbies like to having such an exit button for every applications installed in my android. Hoping there is some developemnet on this issue later.
Related
I don't know what the deal is but this is continually happening to me and across different roms. I am using the built in "Task Manager" feature of touchwiz to monitor what processes are using my cpu. I am finding that some things are sitting there using between 15-45% cpu at all times even when in the background. For example:
Today right before my lunch I checked the task manager, I stared at it for 2 minutes to make sure there was no cpu activity, when I saw that everything looked to me normal I clocked out for my lunch and left work. By the time I was done eating (my phone had been in my pocket the entire time by the way) I checked my phone to see what time it was and noticed that I had lost about 12% battery life in 30 minutes. I immediately opened task manager and found that Browser was in the red and running at a constant 45% cpu usage. I immediately exited the browser. I find that this is happening with other apps as well.
What could be causing this? And more importantly will ICS fix it?
Interesting. Browsers are always killing it for me.
For example I use Dolphin Browser. The ad-dons like Google services and tab switcher kill battery like a mother and also put a ton of CPU stress on the processor.
Only thing I can say is make sure to close out all apps because apps running in a background may run rampant.
Yeah that shouldn't be happening.
I do hope a feature is implemented into android to have a 'do not run list' unless opened by user.
Sent from my SAMSUNG-SGH-I777 using XDA App
kevonomics said:
Interesting. Browsers are always killing it for me.
For example I use Dolphin Browser. The ad-dons like Google services and tab switcher kill battery like a mother and also put a ton of CPU stress on the processor.
Only thing I can say is make sure to close out all apps because apps running in a background may run rampant.
Click to expand...
Click to collapse
What I've resorted to is closing all web pages when im done and backing out of apps that I know have started to run out of control sometimes. There has to be an easier way though.
What about times like today when im researching something and have to run out for lunch and just throw my phone in my pocket with 8 browser windows open? I have to go back and find all the pages because I had to close them all out in fear that my battery would drain?
There has to be a better way. I switched to android bevaseu of the horrible memory management apple has. I would hate to leave android beacuse it couldnt control backgournd processes and let my battery be destroyed.
Memory management is good on these phones. Bad memory management causes slow downs.
What you're looking for is app management. I know some may jump on the me for saying anything about a task manager, but you might want to try one out.
Though I'd only recommend using it for the programs you're having issues with. Set it to 'only' kill the problem apps. Not any other apps or system processes.
What browser are you using? If it's happened across multiple roms, it may be an issue with that browser. Better to treat the problem (the app) than the symptom (battery getting drained)
Sent from my SAMSUNG-SGH-I777 using XDA App
gr8hairy1 said:
Memory management is good on these phones. Bad memory management causes slow downs.
What you're looking for is app management. I know some may jump on the me for saying anything about a task manager, but you might want to try one out.
Though I'd only recommend using it for the programs you're having issues with. Set it to 'only' kill the problem apps. Not any other apps or system processes.
What browser are you using? If it's happened across multiple roms, it may be an issue with that browser. Better to treat the problem (the app) than the symptom (battery getting drained)
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Well see its happening with the same apps across different roms so I know its either an android problem or a touchwiz problem. Can you reccomend any apps that will auto close apps if they start using too much CPU or an app that would allow auto kill on exit? Thank you.
There's not any apps like that, at least yet. Task killers kill whether the app is using alot of cpu or not.
What apps are causing you issues? Have you compared what apps you have on your phone to entropy512's thread about known battery drainers?
Sent from my SAMSUNG-SGH-I777 using XDA App
gr8hairy1 said:
There's not any apps like that, at least yet. Task killers kill whether the app is using alot of cpu or not.
What apps are causing you issues? Have you compared what apps you have on your phone to entropy512's thread about known battery drainers?
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
I remember seeing that thread somewhere before but don't know how to find it again.
Can you reccomend any task killer apps?
Sent from my SAMSUNG-SGH-I777 using XDA App
My favorite with my captivate was auto task manger. When you first open it, it tries to get you to update but the update is garbage.
https://market.android.com/details?id=com.mizusoft.autotaskmanager&hl=en
I haven't used one with my sgs II. Hasn't needed one so far.
Here's a link to the thread:
http://forum.xda-developers.com/showthread.php?t=1308030
Sent from my SAMSUNG-SGH-I777 using XDA App
gr8hairy1 said:
My favorite with my captivate was auto task manger. When you first open it, it tries to get you to update but the update is garbage.
https://market.android.com/details?id=com.mizusoft.autotaskmanager&hl=en
I haven't used one with my sgs II. Hasn't needed one so far.
Here's a link to the thread:
http://forum.xda-developers.com/showthread.php?t=1308030
Sent from my SAMSUNG-SGH-I777 using XDA App
Click to expand...
Click to collapse
Thank you, I will read through this.
Sent from my SAMSUNG-SGH-I777 using XDA App
Is there a possible way to completely terminate app on home button press? Because everytime my friends use my phone they didn't realize there is a back button.. So they just presses the home button like they were using idevices.. This would hog the memory with the running apps and i have to constantly close them everytime they finish playing..
ICS does have this feature but im running GB atm..
Sent from my GT-I9100 using xda premium
Doesn't matter. Android automatically manages those tasks when they're sent to the background. You're supposed to use the home button like that. Gingerbread is very efficient at handling tasks and RAM. Hence no need for any task killers/manual killing of apps. It's unnecessary. They'll automatically be purged from memory when a freshly opened app needs to take their place in memory to run. I know it feels satisfying to always kill every running app (coming from Symbian S60) and think that you have all the RAM free, but its pointless and of no use.
RAM is supposed to be full. Unused/empty RAM is considered to be wasted RAM. The RAM will be managed completely by the Android system without user intervention. The only time you'll ever need to manually kill an app is if it's misbehaving and causing stability issues.
So continue using the home button like that, there's nothing wrong.
Take a look at this excellent article to get a clear idea -
http://www.androidcentral.com/ram-what-it-how-its-used-and-why-you-shouldnt-care
Sent from my Desire HD using xda premium
So it's best to left the apps running?
But these apps are different to services right? I mean, when it's running in the background it's counted as inactive? Because my friend's SGS2 had plethora of active services running and it drains battery like crazy..
Sent from my GT-I9100 using xda premium
Only concern I can see is if an app isnt killed and is still active in the background, it could use cpu/battery power, but if it's Instantly killed it won't anymore.
sent from my legend, currently using extream legend fuse™
Gorjess said:
So it's best to left the apps running?
But these apps are different to services right? I mean, when it's running in the background it's counted as inactive? Because my friend's SGS2 had plethora of active services running and it drains battery like crazy..
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
They will only drain power if the apps are requesting CPU which any good app shouldn't. RAM needs power but I believe its being powered the same whether full or partially full and I imagine RAM requires little power. There are some that will drain battery if left running, and those are the ones that you may have to kill but it shouldn't be the norm.
Advanced task killer is a very good app but i found that when i put it to kill tasks when screen off, it sometimes doesn't work??? It happened with my galaxy s and now with my xperia s
I know this is not really answering your question, but you should consider not using an automatic task killer.
Three reasons are:
* A task that does nothing but is only started doesn't suck battery life or processor power, killing it however does.
* A task that is started automatically because it does work in the background should be disabled another way if possible, because killing it will make it restart, again sucking battery life.
* If your concern is free memory you should know that memory that is used doesn't take more power than memory that is free. But again, freeing it uses power.
Pezo said:
I know this is not really answering your question, but you should consider not using an automatic task killer.
Three reasons are:
* A task that does nothing but is only started doesn't suck battery life or processor power, killing it however does.
* A task that is started automatically because it does work in the background should be disabled another way if possible, because killing it will make it restart, again sucking battery life.
* If your concern is free memory you should know that memory that is used doesn't take more power than memory that is free. But again, freeing it uses power.
Click to expand...
Click to collapse
well i tell you why i want to use it. Its only when screen off anyways so minimum killing when necessary. But for example sometimes i start dolphin app and just go back to the main screen but dolphin is still running and using cpu, my phone gets hot, it seems sometimes apps get stuck in cpu. Then when i turn off the phone it will kill it cos of the task killer. If i turn off the phone and i dont kill it, dolphin will continue to use up 40% continuously making the phone hot and use up massive battery. Im sure some of you know this it happens with other apps too maybe its a problem with android gingerbread. Note dolphin doesn't always do this, only sometimes.
Use provided browser is best.
Also dolphin have big security issuse, try and google it
Sent from my LT26i using XDA
opera mini is also great browser imo..stock one is also ok I guess.. dolphin a bit laggy..at least for me
I can recommend Boat Browser. Very lightweight and supports tabbed browsing. At least I am very pleasantly surprised of how good it really is.
https://play.google.com/store/apps/details?id=com.boatbrowser.free
unrealboot1 said:
well i tell you why i want to use it. Its only when screen off anyways so minimum killing when necessary. But for example sometimes i start dolphin app and just go back to the main screen but dolphin is still running and using cpu, my phone gets hot, it seems sometimes apps get stuck in cpu. Then when i turn off the phone it will kill it cos of the task killer. If i turn off the phone and i dont kill it, dolphin will continue to use up 40% continuously making the phone hot and use up massive battery. Im sure some of you know this it happens with other apps too maybe its a problem with android gingerbread. Note dolphin doesn't always do this, only sometimes.
Click to expand...
Click to collapse
Have you considered using Watchdog if apps are hanging or freezing? It monitors them better an alerts you if an app is misbehaving. It's just an idea as opposed to using an auto task killer which is, quite bluntly, screwing with your current apps and OS.
Is it possible to make Android NEVER automatically kills running apps, to have true multitasking like on Maemo and webOS?
I am really sick of it killing apps that I use.
I tried V6 supercharger, but that didn't help... I looked everywhere for an answer, but I never found one.
Surely there is a way to make Android multitask like a proper PC, where it's the user who manages apps?
(And please don't tell me that I should leave it to Android, that it knows better, and etc.)
Now, before you start defending Android:
Ever had your browser refresh the page by itself after switching to it?
Ever lost something you were writing when you switched to another app?
Ever had a video pause because you switched from the player?
That shows that Android does NOT have true multitasking.
Now, I see why Google did that - battery life. However there is a new class of devices, where battery life is not such a problem. Tablets.
And yet they still suffer from same issues.
Now, here's an example: the browser. Very often I'd come back to my browser, only to find that it is reloading the page I was on, wasting traffic, and losing whatever text I typed.
That's stupid, right?
I can even track back to what device did this first - the iPhone.
iPhone 1 had 8 times less RAM than your average high end device, yet they still have a similar problem.
So yeah. Not true multitasking. Even in the app switcher, notice that it never says "running apps", only "recent apps" - because it isn't a true multitasking app switcher, just a history of all recent apps you launched.
Go on, scroll to the very top, launch the oldest app on the list. I'm 99% sure that it has restarted. This would've never happened if Android had TRUE multitasking.
Now, there has to be a way to get that. Desktop Linux does it, so Android probably can too.
If you ever notice that the app restarts, it's the app that is badly implemented. All apps must be able to handle a restart by Android transparently to the user by saving its state. If not, tell the app developer to fix it.
Chrome, Dolphin, Boat, Maxthon, AOSP, ICS Browser+, Opera, Firefox.
That's a list of browsers that have this problem.
Do you really think that they all implemented multitasking wrong?
Again, it's a problem with Android - I don't want apps to save their state so that Android can kill them - I want them to never leave RAM at all.
SilverHedgehog said:
Now, here's an example: the browser. Very often I'd come back to my browser, only to find that it is reloading the page I was on, wasting traffic, and losing whatever text I typed.
Click to expand...
Click to collapse
Maybe dont answer all ur questions:
http://stackoverflow.com/questions/...lication-is-that-frowned-upon/2034238#2034238
Apps who properly implement onSaveInstanceState() can come back, in case of web browsers is more complex to use it properly, texts or images are simple to imagine how to OS save on "disk" to retrieve later, what about sockets or open files (can be deleted while in background).
Android keep on background until the resources are needed for another task (and maybe a time limit, but dunno for sure), if happen very often w/ u means ur OS r using more resources than what need to keep on background.
Android has true multitasking, but... eh here's a link. Read yourself.
http://android-developers.blogspot.com/2010/04/multitasking-android-way.html?m=1
Sent from my MB508 using xda premium
But is it possible to make it so that apps do not get killed at all, just like in Maemo or a normal PC?
What you showed me is exactly why Android does not have true multitasking: it uses stuff like services to actually have less things running - and I don't want that. I want all apps to truly stay in the background - so a YouTube video would continue playing, just like when I minimize the browser on my PC, and etc.
I understand why that isn't the default behavior on phones, but it could be really useful on a tablet.
I don't want to be at mercy of app developers - since even Google messes up: every time I switch out of Google Talk, I lose what I was typing.
I'd much rather have a limited amount of apps that I can launch at a time, and be able to manage what I want to keep open myself.
What you are asking for is basically to completely change core Android behavior.
Sorry, but its just not possible
Sent from my DROID2 using xda premium
It is possible, because it's been done. There was a guy who did it over on the V6 supercharger thread, but I don't think the how he did it was ever released. Instead it was developed into a "kill apps only when ram is REALLY needed" method, which could run up to 20 apps at a time on some phones apparently
Sent from my Galaxy Nexus using Tapatalk 2
I get what you are talking about but I'd say is what device your using. My eVo 4g lte's was written screwed up by HTC. Maybe yours is like that too. My rom maker and other devs have done many fixes for it. It has got better but my eVo and eVo 3d still multitask better, and it is true multitasking. It doesn't work like I'm talking about on all devices, but for u to say it's all of Android.......... It's not.
Swyped from my eVo
The mulittasking in Android has some limits which are quite annoying. On my Droid 3 apps that I haven't used will start in the background and waste RAM so there isn't enough RAM to multitask and the device is laggy. I tried rooting and freezing bloatware, but other apps have just filled the void by automatically running in the background. I really wish the user had more control over multitasking. Unless I open an app I don't want it to start in the background, even if there is enough free RAM. But Motorola makes some pretty bad software so this could be the issue.
On my Touchpad with CM9 multitasking is quite a bit better. Not sure if its having 1GB of RAM, improvements in ICS, or just CM but you can actually run several programs at once without them closing, so my browser pages stay loaded.
gagdude said:
Android has true multitasking, but... eh here's a link. Read yourself.
http://android-developers.blogspot.com/2010/04/multitasking-android-way.html?m=1
Sent from my MB508 using xda premium
Click to expand...
Click to collapse
gagdude said:
What you are asking for is basically to completely change core Android behavior.
Sorry, but its just not possible
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
Then how come this was possible on iOS?
My iPad 1 was a multitasking beast with just 2 tweaks - Swap and Backgrounder.
Everything was smooth. And yet I can't get the same on devices with 4 times more RAM?
gagdude said:
What you are asking for is basically to completely change core Android behavior.
Sorry, but its just not possible
Sent from my DROID2 using xda premium
Click to expand...
Click to collapse
Did it weeks ago. Maximum Overdrive to bypass Maximum hidden app limit.
Just grab the Ultimate Jar PowerTools script or the windows exe version.
http://goo.gl/1JPl8
Also read Post 2 of the thread for a link to the windows.exe
Currently hacking Sense 4+ which seems to be working well.
http://forum.xda-developers.com/showthread.php?t=1900626
Tried V6 - but apps I bulletproofed still get killed.
So yeah. Looks like the only thing I can do is wait until webOS gets ported to my tablet...
SilverHedgehog said:
Tried V6 - but apps I bulletproofed still get killed.
So yeah. Looks like the only thing I can do is wait until webOS gets ported to my tablet...
Click to expand...
Click to collapse
Did you patch services.jar with the multitasking mods?
Yes, with "Jelly ISCream Automatic Patcher".
V6 script showed me that I'm 100% supercharged.
well...I didn't experienced these kind of problem before. android indeed has good multitasking stuff. the number of app running on background depend on the ram size. you can't expect to run such heavy app with huge ram consumption on such device with low ram. anyway, you can try to play with minfree stuff. try to minimilize the value
The Note 10.1 can have side by side applications, is this what you kinda mean?
Sent from my XT862 using Tapatalk 2
SilverHedgehog said:
Yes, with "Jelly ISCream Automatic Patcher".
V6 script showed me that I'm 100% supercharged.
Click to expand...
Click to collapse
Well the latest one is actually called Ultimate Jar Power Tools so if you ran that, and enable Maximum Multitasking Mods, then you should be getting better multitasking/app reloads.
The windows exe would do the same thing of course and is up to date.... well until I update it later cause I'm adding the Sense 4 mod.
Any idea about how many apps you can run before vs after?
oops... double post
Hi, I have a 4.2 and my RAM always gets used up. I try my best to close background programs, but yet I still have barely any left. I always have to force restart the player. This problem started happening out of nowhere. I didn't install any apps or anything either... I've been using ADW Launcher EX and ics keyboard for a while. Any help?
Sent from my YP-GI1 using xda app-developers app
You could try Go launcher EX. That seems to manage my RAM better. Also, if you are not already doing so, turn off your Wi-Fi when you are not using it or it is not around. Also once you turn off your Wi-Fi, try rebooting, that usually will stop any apps that stay open and require Wi-Fi in various ways that somehow are still active. You could also try a custom kernel, I use Terrasilent and my 64 emulator run smoother and I seem to have more RAM. On top of that to you could try a custom governor, which controls your RAM. Just stay away from task manager apps, they add to the problem instead of solving it.
Sent from my YP-G1 using xda app-developers app
actually, its not bad that your ram is filled up.
Consider this -- Jerry did/said/thought something that made his wife mad (yes, she can read my thoughts), so he bought flowers from the 7-Eleven and wants to make a mix CD of her favorite Rod Stewart songs to give to her and get his ass out of the doghouse. It could happen. Consider which is more efficient:
Burn 20 songs to a CD, give to wife, and smile while she plays it.
Burn one song to a CD, let her listen, then erase it and burn the next song.
That's what your phone (or tablet) has to consider. Loading Google Talk to RAM once, and having it there to open almost instantly is far better than loading it each and every time you want to use it. So why kill it off? It's not like you'll never use it again, and nothing else is going to use that RAM while it's sitting empty -- at that point, it's wasted space. You will also use a lot more battery power re-opening Talk every time you get a message than you will by having the zeros held as ones on your RAM. The folks who built Android really did know what they were doing when it comes to memory management. After the parameters are set, and the amount the OS can use to "swap" for it's normal operations, the rest is simply wasted if we're not using it. What is cached in RAM is just sitting there, not using any CPU cycles, but ready to get pushed to the front and appear on the screen as fast as it can, and not use the extra battery needed to start it up from disk again.
Click to expand...
Click to collapse
http://www.androidcentral.com/ram-what-it-how-its-used-and-why-you-shouldnt-care
Thanks! I'm just waiting for software to be developed so I can get a faster device.
Sent from my YP-GI1 using xda app-developers app