Problem with multitasking : everytime I'm using the browser and switch to some other app and switch back to browser, browser restarts it self
I'm using nik_v4
use a different browser like opera,boat browser,firefox etc.
it depends, the system might be aggressively freeing up memory once you switch the application (that is if you are low on free memory) or another thing, it depends how you switch the application. in this case, a browser, you usually click Home and start another app (that send the current application in pause mode, in the background), but if you clicked Back to get back to the homescreen, the system will interpret this as a kill application sign, it will not keep it in the background. i'm not giving alternatives just trying to explain how stuff works. check if you are low on memory, try it with different browsers (i recommend Dolphin browser).
facing similar problem with firefox
andrei.je said:
it depends, the system might be aggressively freeing up memory once you switch the application (that is if you are low on free memory) or another thing, it depends how you switch the application. in this case, a browser, you usually click Home and start another app (that send the current application in pause mode, in the background), but if you clicked Back to get back to the homescreen, the system will interpret this as a kill application sign, it will not keep it in the background. i'm not giving alternatives just trying to explain how stuff works. check if you are low on memory, try it with different browsers (i recommend Dolphin browser).
Click to expand...
Click to collapse
i switch between apps using long press of home button still browser keeps closing and restarting i always have atleast 150 mb memory free
suggest a few memory hogging apps i'll remove them if i have
at least 150mb free means you don't have a memory problem. but this behavior is a bit odd. it might be from the current kernel you are using and it might be implementing a very aggressive memory freeing task manager (killing any application as soon as it is sent in the background). if you have installed a market task manager or any memory freeing app i suggest you uninstall them. you might also wanna try flashing a new kernel and see if it changes anything (make sure new kernel is compatible with your current ROM). i'm using niks 4.0 ROM with RCMIX-Vivo kernel and i don't have this problem.
Related
Hi, I'm looking for some advice on how to force my Dream to keep certain apps in memory, no matter what.
I'm currently running Dwang's rom 1.13, and the apps that I use all day long are Chompsms, Gmail and Dolphin browser.
I believe my rom uses compcache as standard, however time and again I'll go to open up my mail or sms, and i get a blank screen for 1-2 sec, as the app loads into memory. I don't even generally use other memory-hogging apps (like camera, maps) at all, so I can't understand why my most used apps are not always in memory? I only have 1 or 2 webpages open in Dolphin as well, and when I go back to that, generally it has to reload one or other of the pages.
Advanced Task Manager shows that I currently have 21mb free memory.
Can anyone suggest a way to keep the apps I want in memory permanently?
Thanks!
im reading that advanced task killer is good and bad, so is it bad to install or does it really work? im running CM7 Stable.
EverythingNook said:
im reading that advanced task killer is good and bad, so is it bad to install or does it really work? im running CM7 Stable.
Click to expand...
Click to collapse
Everything I've read says you don't need it with Android 2.2 and above.
I use it, nice quick and easy way to close things (like emulators that normally won't shut themselves off.)
dsf3g said:
Everything I've read says you don't need it with Android 2.2 and above.
Click to expand...
Click to collapse
me too but my friends have 2.3 and they use it.
I use it if videos start to stutter (ie youtube etc). It seems to help.
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Product F(RED) said:
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Click to expand...
Click to collapse
alright ill stay away from it thanks!
That about sums it up. The only time an app should be killed is if a bug causes it to hang or slow down severely. Otherwise, let the Android system handle things itself.
In my experience it's nice to have for when you need to kill off a specific game or resource intensive app that seems to be slowing things down.
Product F(RED) said:
It's bad if you set it to Auto-Kill. The reason is because from 2.2 onward, if you kill (not Force Close) and app, it'll just restart itself. That being said, Linux is not like Windows. With Linux, the OS will fill up memory (RAM) with whatever it can, in this case applications, even if you're not using them. HOWEVER, it will only dedicate the CPU to whatever you're actually using, so whatever is in memory and isn't being used won't affect you (aside from poorly-coded apps). You can use ATK to kill an app if it's just one or two, but not everything.
If you set ATK to auto-kill everything or if you hit Kill Everything, you'll have a ton of apps restarting at the same time, slowing down your phone for a while and eating battery.
Click to expand...
Click to collapse
so would you recommended going into the app itself and picking the apps i want to be closed? or could i also use the widget to close all of them?
I would only recommend going into the app itself, long-pressing on the app you want to kill, and then pressing kill. Closing all of them just forces a large number of apps to restart. I really only use it to kill certain apps that are more difficult to close.
Hi. I tried a few of ICS roms available for i9000 out there, and all of them are pretty fast, much better than I expected. The only issue I have with any ICS rom I've recently tried is that they close apps in background quite often. For example, I might open my Opera Mobile, switch to SMS app, send a message, and then when I return Opera has to start over and load all the pages again. Does it happen to You as well? As a comparison, I tested it with a 2.3.4 MIUI rom I had as a Nandroid backup, and it's much better - most apps stay open in background for a longer time.
Is it possible that ICS has that bigger of a memory footprint over Gingerbread? What are your opinions on that? Experienced similar issues? Any workarounds?
warnec said:
Hi. I tried a few of ICS roms available for i9000 out there, and all of them are pretty fast, much better than I expected. The only issue I have with any ICS rom I've recently tried is that they close apps in background quite often. For example, I might open my Opera Mobile, switch to SMS app, send a message, and then when I return Opera has to start over and load all the pages again. Does it happen to You as well? As a comparison, I tested it with a 2.3.4 MIUI rom I had as a Nandroid backup, and it's much better - most apps stay open in background for a longer time.
Is it possible that ICS has that bigger of a memory footprint over Gingerbread? What are your opinions on that? Experienced similar issues? Any workarounds?
Click to expand...
Click to collapse
Try using less widgets. Don't use apps like Facebook. Check push notification services of some apps.
Also, i seem to remember that Opera Mobile tends to "forget" loaded pages very quickly, if you don't come back to the app quite fast...
You can also try and check under settings > developer options > see if you have checked "don't keep activities" and under "background process limit" choose "standard limit"
Since I'm only getting advice, I take it I'm the only one having this problem? Strange. The only widget I have on my desktop is the stock ICS analog clock widget, and there is no such thing as "Developer options" in my Opera Mobile.
Right now I'm using AOKP rom b27, there is an option called "Free memory - Amount of RAM the minfree taskkiller will keep". I tried to change it to max possible - 100MB, didn't change anything.
Is you are using ICS roms, you never had such issues? Which roms do you use?
PS Could a different kernel make it better?
Opera uses alot of memory and the phones memory is very limited. Doesn't matter the ROM it will often get closed when you leave it to do other things.
BTW increasing the memory the OS keeps free makes it worse, how do you think it frees memory? By closing things. You actually want to decrease the memory it keeps free to try and help with this. The downside is that the phone will probably lag more and I have found it doesn't help much.
I'll try to use the stock browser. As to that task manager setting:
The description says:"Amount of RAM the taskkiller will keep", so I have no idea if it means keeping some RAM available at all times or is it the amount of RAM that can't be cleared.
warnec said:
I'll try to use the stock browser. As to that task manager setting:
The description says:"Amount of RAM the taskkiller will keep", so I have no idea if it means keeping some RAM available at all times or is it the amount of RAM that can't be cleared.
Click to expand...
Click to collapse
It is never the amount of RAM that can not be cleared it is the amount of RAM to keep free. ie if you set 64MB Ram to be kept free Taskkiller will keep that amount of memory free by killing the oldest non active task/process
I know that android is very good at handling background processes and ram but I have so many apps that I don't use at all. They consume big amount of ram and for instance, sometimes browser loads pages again when I get back to it from another app. I assume this is because of ram. So I guess, if I can shut down some running apps in the background, available ram would be more.
I can see them at settings-apps-running(or cached processes).
For example, right now in "running" section I have 9 processes and 3 of them are poweramp, awesome beats, accuweather.com and in "cached processes" I have 10 processes and 6 of them are beautiful widgets,calendar storage,google account manager, google search, calendar, google play store. Other processes are system services that I have no problem with. When I go to developer settings-background process limit and block them, there are no cached processes anymore but that probably has a side effect. I wish I could choose which apps I want in the background.
I can shut down these apps manually but every time I restart the phone, they are there again. How can I stop them?
if you rooted, you can use Autostarts or ROM toolbox from the playstore. it can change the receivers of the apps not to start at boot
CooLasFcuK said:
I know that android is very good at handling background processes and ram but I have so many apps that I don't use at all. They consume big amount of ram and for instance, sometimes browser loads pages again when I get back to it from another app. I assume this is because of ram. So I guess, if I can shut down some running apps in the background, available ram would be more.
I can see them at settings-apps-running(or cached processes).
For example, right now in "running" section I have 9 processes and 3 of them are poweramp, awesome beats, accuweather.com and in "cached processes" I have 10 processes and 6 of them are beautiful widgets,calendar storage,google account manager, google search, calendar, google play store. Other processes are system services that I have no problem with. When I go to developer settings-background process limit and block them, there are no cached processes anymore but that probably has a side effect. I wish I could choose which apps I want in the background.
I can shut down these apps manually but every time I restart the phone, they are there again. How can I stop them?
Click to expand...
Click to collapse
The simple answer is that you don't need to stop them!
As you say, Android is already very good at keeping track of background processes, to the extent that if a new program needs more RAM, Android itself will kill a background process that hasn't been used for a while to free up RAM for the new program.
The Cached processes screen SHOULD be full of recently used programs; it shows that Android is doing what it is supposed to do and is shifting inactive processes out of active RAM in case you want to load it again, without completely dumping the process memory.
Now, as for the side effect you mentioned, that would be a significant hit on battery life. By holding programs in RAM as it is supposed to do, the OS can load the program quickly and cleanly and more efficiently by simply reading the RAM rather than reading flash, writing to RAM, then reading from RAM. The general mantra for UNIX based systems is that unused RAM is wasted RAM.
Another thing to note is that if you do not close tabs when switching active programs (including going to homescreen) then the Browser is designed to hold that tab in memory. Even if you close the Browser (excluding closing the tab specifically with the "little x"). Even if you reboot the damn phone, it will still load the tabs/pages you had open last. The pages are not held in memory as such, just what was open and what tab order, so if you do open the browser after a while, it will load the last page from scratch.
TL;DR version: The running and the cached processes will remain exactly where they are until a new program needs more RAM than is available, at which point Android will kill something to make room. You do not need to do this manually. It will cause more power drain by making very inefficient use of RAM/Flash memory. Empty RAM is wasted RAM.
whilst Chaos is right, I notice severe performance drops when ram is filled, despite Androids theoretical advantage. It doesnt work...
Best to prevent from loading altogheter.
Root, lose warranty, backup apps, uninstall or freeze apps so the bloatware is removed.
For others, change autostart settings in Romtoolbox. So they wont start on boot.
Search for safe stuff to delete. There are lists for that
Sent from my GT-N7000 using Tapatalk 2
Or just dont install the apps that you dont really need.
Via GtN7000
LoVeRice said:
Or just dont install the apps that you dont really need.
Via GtN7000
Click to expand...
Click to collapse
Lol, even then you might still need to remove bloatware lol
Sent from my GT-N7000 using Tapatalk 2
Thanks so much for detailed answers.
Whenever I use chrome on my nook hd plus (running the nook stock software) and press the home button the home screen has to reload it takes like 5 seconds load. It happens with some other apps to but mostly just chrome. Running nova launcher fixes this but I would like to use the stock launcher. I get the nook isn't the most powerful device on the market but
With 1.5ghz dual core proccesor with 1gb of ram it shouldn't have to do that. I've tried task managers on auto kill and even ram managers and apps that modify the built in android task manager (although I dont have root) I tried dolphin browser which seemed to work fine but would rather use chrome. Any way to fix this?
its memory.
BrandonB1312 said:
Whenever I use chrome on my nook hd plus (running the nook stock software) and press the home button the home screen has to reload it takes like 5 seconds load.
Click to expand...
Click to collapse
Most likely its ram.
Android will unload/suspend background apps when running out of memory. As we all know browsers are memory intensive applications.
in fact the more capable your browser the more memory it will need for pages, images, plugins, additional processes such as flash, js, etc.. .
from the android dev site. application life cycle page , stopped section.
Stopped
The activity is completely obscured by another activity (the activity is now in the "background"). A stopped activity is also still alive (the Activity object is retained in memory, it maintains all state and member information, but is not attached to the window manager). However, it is no longer visible to the user and it can be killed by the system when memory is needed elsewhere.
Click to expand...
Click to collapse
Thanks gonna use nova launcher since it dosent take as much ram.