I understand that Android memory management cannot be compared with Windows memory management. CHECK
I therefore don't care that my SGN always shows about 100 MB free RAM (according to Quick System Info Pro) because you know, it's only a number. CHECK
I dont't have any lag when starting and switching (most) apps on my SGN. CHECK
I have installed only the most important apps (for me). Counting only those running as a service/widget and therefore needing some RAM permanently: Live wallpaper, Light Flow, Calendar Widget. CHECK
BUT:
Pressing "recent tasks" while BROWSING (e.g. opera mobile) and switching to another app like "google reader" causes opera mobile to close in background. And every restart takes about 2 sec and a reload of every web page tab.
So 100 MB free RAM is not just a number - it's a major problem for me. My previous device: HTC Desire on CM7.1 and I could not remember that a simple task switch closing opera in over 1 year!!!
Android 4.0.1 always seems to close the app that uses most RAM - and that's Opera. The task manager shows at least 4 other unused apps (settings, google mail - no widgets used) that use 120 MB in total that DO NOT get killed!! Even if they are unused for quite a while. Don't you think too that Android should priorize the foreground app and the last used foreground app instead of apps that have not been shown for minutes? Isn't switching between too apps the most common use case? SGN's "1 GB RAM" is pure deception to me. It's what Samsung has built into the device but not what you really get.
How do you cope?
[Sorry for my bad English but it just flowed out of my angry fingers]
I haven't had any problems with this whatsoever. Try closing tasks yourself so the system isn't forced to close one for you? Worth a shot.
Sent from my Galaxy Nexus using xda premium
Closing tasks before surfing is not what I want to do on a high-end device with 1 GB RAM. I want to use at least 2 apps concurrently and I think that this is not much to expect...
I typically have 275-300+ MB free at any given time (according to the settings page).
Not sure how your managing to use so much. I've yet to have android have to close a app for me.
Solution: Use a different browser.
Sent from my Galaxy Nexus using xda premium
Get a low end phone?
Sent from my Galaxy Nexus using xda premium
Same problem here, and I didn't cope I created my own mod of Opera Mobile where I added a service which increases the OOM priority of the app. Android then don't close it anymore.
Link to my Opera Mobile "keep-in-memory" mod: http://www.reddit.com/r/Android/comments/n7p48/app_mod_by_requests_latest_opera_mobile1153_with
That's the issue. The value of Opera is set too low where the Android system will close it first over other processes. It doesn't care that it is Opera, just what the value is. You can check all that with Auto killer memory optimizer.
Sent from my DROID RAZR using XDA App
sluflyer06 said:
I typically have 275-300+ MB free at any given time (according to the settings page).
Not sure how your managing to use so much. I've yet to have android have to close a app for me.
Click to expand...
Click to collapse
Settings page seems to calculate the free RAM differently ("wrong"?)
Oh and changing my browser is not a solution - happens too on stock browser.
Melhouse said:
Same problem here, and I didn't cope I created my own mod of Opera Mobile where I added a service which increases the OOM priority of the app. Android then don't close it anymore.
Click to expand...
Click to collapse
Could not add link before I spam the forum with a few more posts (stupid 8 post before link posting rule..) . Search for "lock in memory" on Reddit to find it.
kangxi said:
That's the issue. The value of Opera is set too low where the Android system will close it first over other processes. It doesn't care that it is Opera, just what the value is. You can check all that with Auto killer memory optimizer.
Sent from my DROID RAZR using XDA App
Click to expand...
Click to collapse
Auto Killer shows that Opera will be the process most likely to get killed, that's true.
But why is it that killing is needed so often?
onyxogen said:
Settings page seems to calculate the free RAM differently ("wrong"?)
Oh and changing my browser is not a solution - happens too on stock browser.
Click to expand...
Click to collapse
Already asked but nobody answered.Settings in my phone shows above 300mb and with elixir2,autokiller memory optimizer and few other apps shows below 200mb.Dont know which one is correct.
And one more question. My sgs2 has all the time free ram +450mb.Why GN has below or around 300mb (if settings correctly report the ram) with almost same apps installed?
afilopou said:
Already asked but nobody answered.Settings in my phone shows above 300mb and with elixir2,autokiller memory optimizer and few other apps shows below 200mb.Dont know which one is correct.
And one more question. My sgs2 has all the time free ram +450mb.Why GN has below or around 300mb (if settings correctly report the ram) with almost same apps installed?
Click to expand...
Click to collapse
You're lucky!
For me it's always about 100 mb left memory in Autokiller memory optimizer, in quick system info pro, ...
Anyone with the same low values?
onyxogen said:
You're lucky!
For me it's always about 100 mb left memory in Autokiller memory optimizer, in quick system info pro, ...
Anyone with the same low values?
Click to expand...
Click to collapse
restart the phone and tell us the memory value as soon as you restart without opening any apps
I don't think Android sets the values. It the app itself. So they programmed it whereas they wanted it closed more often than not. Like someone said, you can reconfigure the app the raise the value.
Sent from my DROID RAZR using XDA App
I did a reboot (first one since 3 days when I unboxed the device, it's so damn stable :-D ) and know I've got ~ 200 MB free too. Maybe I had a leaking process which led to this problem??
onyxogen said:
I did a reboot (first one since 3 days when I received the device, it's so damn stable :-D ) and know I've got ~ 200 MB free too. Maybe I had a leaking process which led to this problem??
Click to expand...
Click to collapse
more than likely. its probably an app that really isnt made for ICS.
or it could've been an app with a high value for keeping in memory that was using quite a bit and would never close (games are usually set that way)
And Android works on thresholds, I'm sure you are aware. So once your device gets to a certain memory level, it starts to kill processes with low priority. So maybe you have too many things running in the background or Widgets. Get rid of things you really don't use because they could be using resources.
I'm using a Droid RAZR, which is bogged down wth Motorola stuff, but auto killer still reports 315 MB of ram. I've frozen much of the bloat though.
Sent from my DROID RAZR using XDA App
I usually have Free/Total memory around 200M/630M
SGS2 420M/837M
kangxi said:
I don't think Android sets the values. It the app itself. So they programmed it whereas they wanted it closed more often than not. Like someone said, you can reconfigure the app the raise the value.
Sent from my DROID RAZR using XDA App
Click to expand...
Click to collapse
You don't set the value, Android does that based on requrements of the application, what type of application it is, and what state it is in.
What I did with my Opera Mobile mod, was to add a dummy service with high priority that don't do anything. This sets the OOM value to 2 when Opera is not visible in the foreground, this is just slightly below the priority of the keyboard.
Related
I've been wondering why my browser tabs get kicked out of memory after so long. Usually if I take a phone call or switch into a large app and return to the browser, I have to reload all my pages. I normally have 3-5 tabs open at once. With VZW's slow 3G it's a pain to reload and lose my place. Doesn't this phone have 1GB of RAM? I wouldn't think a phone call would cause the browser to be removed from memory would it? This has been plaguing me for years just wondering if there was anything I could do to prevent it.
Sent from my Galaxy Nexus using XDA App
Yes its just something to do with the latest ICS version, memory management is more aggressive with the browser or something. It drives me mad too. Sometimes ill switch to the homescreen for one second without loading a single thing, go right back to the broeser and it was kicked from memory.
Is the behaviour the same in the new Chrome Beta?
Yup, I find this a bit annoying, too.
DirkGently said:
Is the behaviour the same in the new Chrome Beta?
Click to expand...
Click to collapse
It doesn't seem to be. I've just had a test and it seems to keep all pages open.
Open browser -> load page -> menu -> save for offline reading
lilirose said:
Open browser -> load page -> menu -> save for offline reading
Click to expand...
Click to collapse
But wouldn't you then have to do this for each tab?
Because Android doesn't offer true multitasking. It closes apps you are actively using and caches apps you don't ever use... Poor memory management and aggressive task closing makes for a poor user experience.
EP2008 said:
Because Android doesn't offer true multitasking. It closes apps you are actively using and caches apps you don't ever use... Poor memory management and aggressive task closing makes for a poor user experience.
Click to expand...
Click to collapse
Yep. It's a little too aggressive. It's most annoying when i'm using Spotify or something. I might pause the music for a little while for whatever reason, run a couple apps. When I go back to Spotify I have to restart the whole app.
It should intelligently monitor usage and cache apps based off that...
tweak your VM settings, as well as min free settings.
My pages has always stayed in memory
s2d4 said:
tweak your VM settings, as well as min free settings.
My pages has always stayed in memory
Click to expand...
Click to collapse
Mind providing some examples and/or guidance on how to accomplish this?
s2d4 said:
tweak your VM settings, as well as min free settings.
My pages has always stayed in memory
Click to expand...
Click to collapse
Yeah this is what i want to try and tweak the oom numbers but i just been too lazy...
Hmm. I have never used Spotify before, but that sounds way too aggressive. I use slacker.com and if i pause it there does not seem to ever be a problem going back and having the song pick up right where i left off. Google listen seems to do the same. Now don't get me started on the one or two times per day slacker causes my galaxy nexus to reboot ......
rudolphe said:
Mind providing some examples and/or guidance on how to accomplish this?
Click to expand...
Click to collapse
Need it too...
I never experienced this. I have chrome and chrome beta with bunch of tabs in each of them open and they always stay there. I am on stock 4.1.1 and i have stock android browser disabled.
Sent from my Galaxy Nexus using xda app-developers app
So do you guys find it necessary to have a ram manager to free memory or no ?
No, ics have a good system to manage ram.
No. Creates more issues than it solves.
+1 for no. Watchdog has always been a must have for me, but it hasn't yet had to call out an app on my SGN.
No. Don't use automated tools to kill tasks and free up memory... in Android, free memory is wasted memory. You make your phone work harder when you interfere with its built-in memory management.
I kill running services that shouldn't be running... That allows for more RAM to be used by active applications.
EP2008 said:
I kill running services that shouldn't be running... That allows for more RAM to be used by active applications.
Click to expand...
Click to collapse
Users always feel they are smarter than the OS when it comes to killing processes. They are usually wrong.
adrynalyne said:
Users always feel they are smarter than the OS when it comes to killing processes. They are usually wrong.
Click to expand...
Click to collapse
Funniest thing I read all day and its true
adrynalyne said:
Users always feel they are smarter than the OS when it comes to killing processes. They are usually wrong.
Click to expand...
Click to collapse
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
EP2008 said:
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
You have no idea how android works and deserve to have your nexus confiscated.
Sent from my SGH-T989 using XDA App
EP2008 said:
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Android does not operate like windows. Apps listed as "Running" are actually only loaded in ram and are not using cpu cycles or battery power. Android loads them in ram in order for them to start/be available more quickly to the user. If Android needs more ram for a task, it will remove any thing it needs to in order to free up more ram. You are wasting battery power and cpu cycles by "killing" those apps/service. If you think of ram as a memory stick you will realize that once something is loaded there, it doesn't take any power to keep it there.
Good luck
Good luck
jordanishere said:
You have no idea how android works and deserve to have your nexus confiscated.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
System services should obviously not be messed with, but disabling autostarting services that you don't use is generally not a problem. It may take more power/time to start up apps that use those services (since they will have to be manually started), but if it's an app that you use infrequently it may be worth doing.
Intelligently tuning what services are allowed to autostart themselves is NOT the same as indiscriminately killing apps chasing after "free memory".
Personally, I wouldn't terminate services, but only modify which ones are allowed to automatically start up with the OS.
codesplice said:
if it's an app that you use infrequently it may be worth doing.
Click to expand...
Click to collapse
Is it worth doing when Android does this automatically?
Sent from my SGH-T989 using XDA App
EP2008 said:
Yes,I feel that having running SERVICES that I'm not using is a huge waste of memory and battery resources. Android is not smart in this regard.
For example, I use the amazon app store to check for free apps of the day ONCE a day. No need to have it run as a service all day, using up ram and CPU. Another example is pulse news reader. I want to go in the app, refresh the feeds, read them and exit, but the app remains running as a service for no reason. I also use a document scanner app which runs as a service when I'm not using it for no good reason. So, I kill the service.
To suggest that I'm wrong in doing this shows a lack of understanding of the issue at hand.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
you basically proved what he said was true
I agree with using "Autostarts", it's one of my fav apps and cuts down on startup time and certain apps like to be triggered for all kinds of rediculous things. Once again though I think it is counterproductive to use automated task killers. Watchdog will alert you of apps running away with your ram and battery, but does not just auto kill all random apps. As far as the Amazon AppStore, I agree that it can be very malicious with RAM if it wants to be even when just checking the FAOTD in the mornings, on my Atrix I would get constant alerts from Watchdog for Amazon AppStore. On my SGN however I have yet to recieve ANY alerts for ANY app yet from Watchdog, this leads me to think there is better optimization going on with ICS or the Nexus than I had with Gingerbread and Atrix.
Is there any reason not to use AutoStarts or WatchDog? They are not auto killing apps at all. And I am requesting a "real" technical explanation not just you opinion or a "think of it like.." story, those are useless to me and offer no explanation.
jordanishere said:
Is it worth doing when Android does this automatically?
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Eh, usually there's not much benefit to be had - but preventing a service from auto starting when you might not use its app for the entire time Android is booted won't cause any problems. You're essentially "freezing" the service while still allowing it to be used on demand .
WiredPirate said:
I agree with using "Autostarts", it's one of my fav apps and cuts down on startup time and certain apps like to be triggered for all kinds of rediculous things. Once again though I think it is counterproductive to use automated task killers. Watchdog will alert you of apps running away with your ram and battery, but does not just auto kill all random apps. As far as the Amazon AppStore, I agree that it can be very malicious with RAM if it wants to be even when just checking the FAOTD in the mornings, on my Atrix I would get constant alerts from Watchdog for Amazon AppStore. On my SGN however I have yet to recieve ANY alerts for ANY app yet from Watchdog, this leads me to think there is better optimization going on with ICS or the Nexus than I had with Gingerbread and Atrix.
Is there any reason not to use AutoStarts or WatchDog? They are not auto killing apps at all. And I am requesting a "real" technical explanation not just you opinion or a "think of it like.." story, those are useless to me and offer no explanation.
Click to expand...
Click to collapse
I relied upon autostart tuning and Watchdog on my N1, but haven't experienced a real need for either on the SGN. Not necessarily a technical response, but just my experience.
Wow, the ignorance on XDA is staggering.
A RUNNING SERVICE is not the same as a cached app or background process.
Why the heck would anyone want 3 or 4 running services in the background when they don't need them running?
Right now, I have the logmein service using 26mb, Amazon app store using 38mb, pulse taking up 43mb and I'm NOT using these apps. They are running as services and using ram, battery and cpu.
Continue to defend Android and all its flaws. The user doesn't always have to accept how poorly some things function.
Sent from my Galaxy Nexus using Tapatalk
EP2008 said:
Right now, I have the logmein service using 26mb, Amazon app store using 38mb, pulse taking up 43mb and I'm NOT using these apps. They are running as services and using ram, battery and cpu.
Continue to defend Android and all its flaws. The user doesn't always have to accept how poorly some things function.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Less an Android flaw and more related to how developers wrote those apps. Otherwise I think we are in agreement though.
codesplice said:
I relied upon autostart tuning and Watchdog on my N1, but haven't experienced a real need for either on the SGN.
Click to expand...
Click to collapse
why?
10char
Hi Guys,
I've noticed that when i "remove" (flick upwards) an app from Recent Apps, it does not really kills/closes that app. I know i can go to Task Manager and kill that app. My question is that is there any way (settings) that enables "Kill" of the app when i remove it (using upward flick) from the Recent Apps.
I tried looking up for this but was not successful hence a new thread (i was somewhat sure someone must have ask for it already).
Thanks
veerm said:
Hi Guys,
I've noticed that when i "remove" (flick upwards) an app from Recent Apps, it does not really kills/closes that app. I know i can go to Task Manager and kill that app. My question is that is there any way (settings) that enables "Kill" of the app when i remove it (using upward flick) from the Recent Apps.
I tried looking up for this but was not successful hence a new thread (i was somewhat sure someone must have ask for it already).
Thanks
Click to expand...
Click to collapse
I dont believe that there is a setting where you can change that. If you want to kill an individual app, use the task manager but in general, there is really no need to be killing all of your apps - the Android OS is designed to have apps sitting there not closed (and the HOX has 1gig of RAM so your shouldnt see any slow down anyway!).
Some custom ROMS for other devices do have a setting where you can set longpress backbutton to kill the app that you are in. Havent seen this in any One X roms yet but im sure it will come
It has been written many times before but can't be said enough, task killers isnt helping the system at all! Android OS itself controls the ram memory and closes the apps that isnt used in case of running out of memory
Skickat från min HTC One X via Tapatalk 2
App killers are phone killers!!1
Even if you force close the app, it may reopen immediately. some apps do this on their own. you dont need to worry about it.
the phone will prioritise the currently running app over cached or paused apps when it needs to. this is an autonomous feature (you don't have any control over it)
I stopped using App Killers and found performance/battery-life/usability to be exactly the same.
remember, Android has your back.
Megabunny said:
Even if you force close the app, it may reopen immediately. some apps do this on their own. you dont need to worry about it.
the phone will prioritise the currently running app over cached or paused apps when it needs to. this is an autonomous feature (you don't have any control over it)
I stopped using App Killers and found performance/battery-life/usability to be exactly the same.
remember, Android has your back.
Click to expand...
Click to collapse
Yeah but those apps are open and fill up almost whole 1GB RAM and when somone wants play game it is laggy cos not enough ram ..
Even when am broqsing internet is so laggy ..
But when u not doing with mobile it doesnt drain battery cos cpu is idle 99%
gifton1 said:
the HOX has 1gig of RAM so your shouldnt see any slow down anyway!).
Click to expand...
Click to collapse
well you will see slow down because it's an HTC One X..somehow HTC have managed to reduce the performance of a quad core processor to something that resembles a dual core device...juttering and slowing down..hogging all the RAM and re-drawing the launcher constantly
well done HTC. This the last time you're getting my money.
Megabunny said:
...
the phone will prioritise the currently running app over cached or paused apps when it needs to. this is an autonomous feature (you don't have any control over it)
...
Click to expand...
Click to collapse
True, however, the priorization is all wrong. When I send my browser to the background just to open an email for an address, most of the times the browser gets closed.
So, when I revert to the browser it has to start all over.
When I look in taskmanager, I see many programs that should be closed before closing the browser, because the browser was the lastest used application.
I would love to have more control over the dumb task closer of the HOX! For instance:
- really close applications that have been in the background for at least a certain amount of time (so games can have more memory without stutter!)
- close applications in reverse order of latest used instead of used most memory
- try to leave at least a certain amount of memory free (and let ME choose this amount)
So, when many tell that task killers are not needed they are only right for non-HOX devices. In other words, the HOX task killer that works automagically has serious issues preventing us to multi-task!
Bright.Light said:
- try to leave at least a certain amount of memory free (and let ME choose this amount)
!
Click to expand...
Click to collapse
linux caches stuff in memory to make it quicker when you do want it. unused ram is wasted ram. it is not like windows.
I came from the t-mobile galaxy s2 and it ran all my tasks in the background. For example, I'd load up a page and then check my email and I'd come back to see it fully loaded.
Whereas, on my Galaxy Nexus if I try to do that it'll have to reload the page.
I know this was a problem on the HTC one X and S, but has this always been something going on in the Nexus or was it after the update to jellybean?
Is there a way to enable apps running in the background?
Thank you in advanced.
jlim0512 said:
I came from the t-mobile galaxy s2 and it ran all my tasks in the background. For example, I'd load up a page and then check my email and I'd come back to see it fully loaded.
Whereas, on my Galaxy Nexus if I try to do that it'll have to reload the page.
I know this was a problem on the HTC one X and S, but has this always been something going on in the Nexus or was it after the update to jellybean?
Is there a way to enable apps running in the background?
Thank you in advanced.
Click to expand...
Click to collapse
Mine does it fine Idk what's going on with yours :3 i multitask all the time
Sent from my Galaxy Nexus using Tapatalk 2
you prolly got too many stuff running in the background at all time thats eating up your RAM
cant blame you seems like a gig of RAM isnt enough anymore
I'll agree with the others. Mine usually works the way you have described but sometimes it doesn't, especially with Chrome. If you wait too long the OS will also kill the app no matter if there's enough free ram or not iirc. I'd think if you just switched to email or sms or the alike, then switched back to the browser within a couple of minutes it should work just fine. 2gb of ram would definitely help though!
Do you have the setting to kill apps after exiting enabled in Developers Settings?
Turn that off if it's on.
Sent from my Galaxy Nexus using Tapatalk 2
I Am Marino said:
Do you have the setting to kill apps after exiting enabled in Developers Settings?
Turn that off if it's on.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No I don't and I have the "background process limit" to standard limit. What is the standard limit?
I have to agree with the OP. On my SGS2 i9100, apps stay alive much longer in the background buttons on the GNex they have to reload even if it's the 3rd apply on hold.
But then again the I9100 had 835mb free ram and the GNex only has 695mb free ram.
Sent from my Galaxy Nexus using Tapatalk 2
Where's all of our ram being allocated to? GPU? It was like that on my Droid X2, was so annoying that the original Droid X had more free ram than it did
Toroplus
What I find surprising is that any somewhat-experienced developer can tell you that RAM is so important on Android, much more than processing power, yet phones are released QUAD-CORE, which makes no sense. Android is a semi-multitasking operating system, it would benefit more from a really good dual-core rather than an average quad-core processor.
RAM is important, because when you switch applications on Android, your app's are 'hybernated' in memory until they are called back again. It is also possible for developer to hybernate the application better (such as store the state on internal memory), but most applications do not use it.
What this means is that if you have a lot of applications running and some applications 'ping' in your background frequently, then you will have very little RAM available on your phone. So when new application is run, the old hybernated ones are killed off.
Where does this take us?
It takes us back to 2010 when released phones had very little internal memory. Applications were growing in size and functionality back then, but most could not be moved to SD card and some parts of the application stayed on internal memory anyway. This meant that after a while, you really could not install all the apps you found useful because you kept running out of internal memory.
This is similar to 2012, where most phones have just 1GB of RAM and only very few new phones have realized this as a problem and have upgraded to 2GB. It is similar because again, apps grow in size and functionality and require more RAM. And in time this means that you can only have very few applications running at the same time without being killed off. Right now, if you happen to run a game like Shadowgun, be prepared to have most of your background apps killed off the moment you start the game.
On the 1GB version of Galaxy S3 that was released in EU there are even problems where the launcher itself is killed off because applications require RAM.
So it's similar in that in a years time, 1GB of RAM will be a real nuisance on the phone because it almost entirely kills off multitasking capability of the phone.
Developers know it, yet marketers and people who 'make the decisions' do not seem to care. They can advertise better processor much more efficiently than more RAM, since people can notice speed, but rarely notice RAM. Most people don't even know that their phone could work better if it had more RAM.
Jesus, I hope you didn't type all that from a phone!
Sent from my Galaxy Nexus using xda premium
Yeah I observe what OP is encountering..
On my SGS2, app tends to stay alive in background than nexus.... not sure why. probably because of HD display.?
IMO, I've played with my friends' iphone, iphone does it somewhat better, frozen app resume very quick..
nonione said:
you prolly got too many stuff running in the background at all time thats eating up your RAM
cant blame you seems like a gig of RAM isnt enough anymore
Click to expand...
Click to collapse
You don't have a gig of ram, you have less
Sent from my Jelly Beaned GNexus
I have found that on all my phones, the stock browser and dolphin browser will get killed and force me to reload. But the chrome browser doesn't appear to do this.
Jubomime said:
Jesus, I hope you didn't type all that from a phone!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Made me LOL
Sent from my Galaxy Nexus using xda premium
What I've found is that, on JB, clicking back on an app until you get out will bring you to the home screen instead of the application you were using before opening the last one.
Pretty annoying if you ask me! Anyone knows how to change this behavior?
The stock browser behavior is not changed much from ics, though. It often reloads, but I'm not sure it's been killed, it might just be that the page is "expired" in some way.
elban said:
What I've found is that, on JB, clicking back on an app until you get out will bring you to the home screen instead of the application you were using before opening the last one.
Pretty annoying if you ask me! Anyone knows how to change this behavior?
The stock browser behavior is not changed much from ics, though. It often reloads, but I'm not sure it's been killed, it might just be that the page is "expired" in some way.
Click to expand...
Click to collapse
That's what "recents" is for. Why would you press the back button ten times, even if that worked?
Sent from my Galaxy Nexus using xda premium
Jubomime said:
That's what "recents" is for. Why would you press the back button ten times, even if that worked?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The application state wil be different if you change app by history or by hitting back.
I often leave an app by hitting back because I want it to start from the main screen (not where it was) when I get to it (eventually) later.
It's like iconifying a window on a pc and it shows the desktop instead of the underlying window(s): doesn't make sense to me.
And anyway it's been different on all previous android versions (tested from cupcake on )
Android is praised for having 'real' multitasking. But why does it have to 'suck' on a phone with 1GB memory?
Chrome starts to reload 3-4 tabs only if it's the only app 'opened' (of course there are other background services. but I don't have much running services, map, google messaging service, keyboard, )
I think it could also be problem with app. app not releasing memory resource when goes to background.
But it's really annoying to see that apps activity needs to be created again from scratch after opening a few apps.
Please discuss your opinion here.
Bayint Naung said:
Android is praised for having 'real' multitasking. But why does it have to 'suck' on a phone with 1GB memory?
Chrome starts to reload 3-4 tabs only if it's the only app 'opened' (of course there are other background services. but I don't have much running services, map, google messaging service, keyboard, )
I think it could also be problem with app. app not releasing memory resource when goes to background.
But it's really annoying to see that apps activity needs to be created again from scratch after opening a few apps.
Please discuss your opinion here.
Click to expand...
Click to collapse
No problems here..
try to avoid apps with high memory usage, one being the Facebook app
crixley said:
No problems here..
try to avoid apps with high memory usage, one being the Facebook app
Click to expand...
Click to collapse
I don't have facebook running as I've said earlier. I don't even have it installed.
But I"m still not convinced that it's the BEST android multitasking could have. it's too aggressively killing background activity..
Bayint Naung said:
I don't have facebook running as I've said earlier. I don't even have it installed.
But I"m still not convinced that it's the BEST android multitasking could have. it's too aggressively killing background activity..
Click to expand...
Click to collapse
Get autokiller from the market and adjust the settings then. You want lower numbers in the app to allow more applications to stay active. Note that some apps might just kill background memory use, there's nothing you can do about that one.
Doing this might make your phone more laggy. You need to decide for yourself what the best trade-off is for you.
When exactly does it do it? I have 5 tabs open and I'm good! Is it after a while of inactivity?
Sent from my iPad using Tapatalk HD
I have never noticed this issue.
Sent from my other android devive using Tapatalk 2
z06mike said:
When exactly does it do it? I have 5 tabs open and I'm good! Is it after a while of inactivity?
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
It's not a refresh (like refresh web page), I think it's just re-rendered from the cache..
even though I'm android fan, I'm jealous how iOS manage to run pretty well for daily use with 512MB... probably dalvik JIT is culprit here?
I personally think this is a problem with chrome and this is the reason I don't like chrome because it runs a constant large service at 70+ mb at all times which takes away from general multitasking of the phone. My guess is this is related to your problem. Persistent services on android are rather powerful and when one is too large it has detrimental effects. Maybe others don't experience this with chrome, but I did, and that's why I stopped using it.
Yes, chrome is worse than stock browser.
Stock can maintain usually 4-5 tabs easily without reloading.
Hopefully Google could do something with both chrome and improve OS multitasking capability.