Somebody knows what this option means?What if i check this "no background process"?
Tnx
Sent from my GT-N7100 using xda app-developers app
Usually the advice is to leave most developer options alone, except usb debugging and show touches, or something like that.
This will cut out any background process like it says... for you it will cut data traffic counters, alarms (maybe), e-mail, any IM clients that you might have and anything that works in the background pretty much.
The positive side is that it will save you LOTS of battery.
BrokenPixel said:
This will cut out any background process like it says... for you it will cut data traffic counters, alarms (maybe), e-mail, any IM clients that you might have and anything that works in the background pretty much.
The positive side is that it will save you LOTS of battery.
Click to expand...
Click to collapse
since it's positive what can i do for makin' it ticked permenantly??
This option was great for older phones that had 512MB ram, but with 2GB of ram, probably best if it is left alone.
BrokenPixel said:
This will cut out any background process like it says... for you it will cut data traffic counters, alarms (maybe), e-mail, any IM clients that you might have and anything that works in the background pretty much.
The positive side is that it will save you LOTS of battery.
Click to expand...
Click to collapse
R U sure it will save battery? From what i know, when d program get kill, and later need to on back when the user want to use it, it will consume more power compare to program that running at background and once u want to on it, it will simply on n not consume much power to restart etc..
Sent from my GT-N7100 using xda app-developers app
its up to you which option you want to choose, i have found it very useful. if you run a lot of apps, after quiting the apps it will stay in the memory as a background process. if the 'standard' limit is set your ram can even fall below 200mb. having standard limit will keep the ram and systm busy as well. hence i always go for ' 4 background process', i can easily get up to 1200mb free ram on average and it doesn't affect multitasking..
sent from: designed for humans
sohebq said:
i can easily get up to 1200mb free ram on average and it doesn't affect multitasking.
Click to expand...
Click to collapse
I can't see the point of this myself - free memory like that is just wasted memory in my experience.
On my Note 1, I'd often find a process had been killed when I switched away for a while and had to wait for it to be reloaded. No such problem on the Note 2 where the process can stay in memory almost indefinitely. I find the Note 2 far more efficient productivity wise because of this.
Yes, it will use slightly more battery, but given the already epic battery life of the Note 2, it's a no brainer in my opinion.
Regards,
Dave
Tnx guys .
Sent from my GT-N7100 using xda app-developers app
del
sent from: designed for humans
Related
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.
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
I found some articles on net talking about harmful influences when using task killers apps.
I'm using SlimICS at the moment and I want to know if when I use the killing button that I've added on my navigation buttons harms my phone as the task killers do..
Sent from my Galaxy Nexus while relaxing..
Don't kill apps unless you have a misbehaving one that's adversely affecting your phone.
The OS can manage apps and memory so much better than you ever could.
martonikaj said:
Don't kill apps unless you have a misbehaving one that's adversely affecting your phone.
The OS can manage apps and memory so much better than you ever could.
Click to expand...
Click to collapse
Just to add: If you have a misbehaving app, don't bother killing it. Just uninstall it. It's not worth the trouble.
These task killers and memory optimizers are really good for lower end devices that have little memory. I used them on a phone that only had 356MB of RAM and only run at about 30-40MB free. A better way to address these issues is to run the V6 Supercharger script on a rooted device.
As for the GNex, why do you need to run task killers? You're not having memory performance issues, are you?
netbuzz said:
These task killers and memory optimizers are really good for lower end devices that have little memory. I used them on a phone that only had 356MB of RAM and only run at about 30-40MB free. A better way to address these issues is to run the V6 Supercharger script on a rooted device.
As for the GNex, why do you need to run task killers? You're not having memory performance issues, are you?
Click to expand...
Click to collapse
Yep. On my old ZTE Blade I really did feel a significant difference in smoothness after killing off some apps, so I don't entirely agree with the notion that you should never ever even consider doing it (which seems to be what some people advocate), but on the GNex there doesn't seem to be a need for it unless a specific app is misbehaving. I don't know if that's just because of the more powerful hardware or if it's also because of the much improved OS (I imagine it's both), but there you go.
JaiaV said:
Just to add: If you have a misbehaving app, don't bother killing it. Just uninstall it. It's not worth the trouble.
Click to expand...
Click to collapse
This. I use watchdog to monitor rogue apps. Engadget was s repeat offender so it had to go.
As mentioned the OS does a great job on its own.
Sent from my Galaxy Nexus using Tapatalk 2
You need nothing more than to swipe apps away when you're done with them in the multitasking window, which doubles as a task manager of sorts.
Sent from my Galaxy Nexus
MikeyMike01 said:
You need nothing more than to swipe apps away when you're done with them in the multitasking window, which doubles as a task manager of sorts.
Click to expand...
Click to collapse
Again, why even bother? The OS handles this just fine.
Although, that doesn't necessarily "kill" background apps. There is a box in "developer settings" that, if you check it, will kill any application after using it. I haven't tried it out but it may just work.
Sent from my GummyNex!
LocoTSX said:
Although, that doesn't necessarily "kill" background apps. There is a box in "developer settings" that, if you check it, will kill any application after using it. I haven't tried it out but it may just work.
Sent from my GummyNex!
Click to expand...
Click to collapse
I'm pretty sure that's as bad as using a task killer.
Sent from my Galaxy Nexus using Tapatalk 2
Ntavelis said:
I found some articles on net talking about harmful influences when using task killers apps.
I'm using SlimICS at the moment and I want to know if when I use the killing button that I've added on my navigation buttons harms my phone as the task killers do..
Sent from my Galaxy Nexus while relaxing..
Click to expand...
Click to collapse
even cyanogenmod has a kill app button, i dont think it does anything to your phone.
IMO the only useful reasons to kill a background app are if it's wasting your battery, bandwidth, or it's some kind of logger. In those cases you're better off just uninstalling it. Android is designed to keep things in memory to save start-up time and related battery drain, and so you have the benefit of the task-selector button. It knows when to clear enough memory to keep your foreground app and you happy. Task killers are holdovers from the days when they were useful.
galaxy nexus (gsm) / cm9 / trinity @ 1.4GHz
I learned a long time ago that in Android/Linux free RAM is wasted RAM.
Sent from my Galaxy Nexus using xda premium
Ics/jb does not need app killers if you press the recent app key and swype it left or right the app gets killed
Sent from my GT-N7000 using xda premium
martonikaj said:
Again, why even bother? The OS handles this just fine.
Click to expand...
Click to collapse
No, not really. And if it were "bad" they wouldn't put it into Android. You should swipe them away when you're done with them.
I Am Marino said:
I'm pretty sure that's as bad as using a task killer.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
There's nothing bad about closing apps you're done with.
What's bad is the auto task killers.
Sent from my Galaxy Nexus
MikeyMike01 said:
No, not really. And if it were "bad" they wouldn't put it into Android. You should swipe them away when you're done with them.
Click to expand...
Click to collapse
No it really does nothing positive to swipe apps away when you're done with them. As the poster a couple above me said, free RAM is wasted RAM. The OS will keep everything in order. You're unnecessarily micromanaging your apps when you swipe them away. Your phone just works harder and for longer re-opening apps over and over again when you kill them manually.
Your RAM is powered and draining battery whether its full of apps or not. It's in your best interest to let the OS fill up your RAM (all the way up to about 90% full) and let it kill things as necessary when you load an app that needs more than is available. The OS will handle it. I know everyone has it engrained in their minds from using Windows for so long to keep as much RAM free as possible, but its just not the case in Android anymore.
martonikaj said:
No it really does nothing positive to swipe apps away when you're done with them. As the poster a couple above me said, free RAM is wasted RAM. The OS will keep everything in order. You're unnecessarily micromanaging your apps when you swipe them away. Your phone just works harder and for longer re-opening apps over and over again when you kill them manually.
Your RAM is powered and draining battery whether its full of apps or not. It's in your best interest to let the OS fill up your RAM (all the way up to about 90% full) and let it kill things as necessary when you load an app that needs more than is available. The OS will handle it. I know everyone has it engrained in their minds from using Windows for so long to keep as much RAM free as possible, but its just not the case in Android anymore.
Click to expand...
Click to collapse
Whatever you want to believe. I'm not going to waste my time on convincing you.
Sent from my Galaxy Nexus
MikeyMike01 said:
Whatever you want to believe. I'm not going to waste my time on convincing you.
Click to expand...
Click to collapse
Hah alright.
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 )
Looking for a App that does as above without taking up much memory in the background whilst doing so. I trialed Smart Booster app and it allowed me too disable auto start for apps I don't need and hibernate others etc but sorta felt like the app itself drain my battery just as much as the apps that were auto starting. Thanks in advance
It's not free, $1.49. But it's worked for me in the past. Personally don't think it will be very useful on this device.
https://play.google.com/store/apps/details?id=com.elsdoerfer.android.autostarts
illmatters said:
Looking for a App that does as above without taking up much memory in the background whilst doing so. I trialed Smart Booster app and it allowed me too disable auto start for apps I don't need and hibernate others etc but sorta felt like the app itself drain my battery just as much as the apps that were auto starting. Thanks in advance
Click to expand...
Click to collapse
Why do you want free RAM? Free RAM is wasted RAM. Android doesn't need you to constantly clear the RAM. It's actually bad to do that because you need to use more CPU power to recompile the whole app when you open it again until we fully switch to ART which pre-compiles all apps.
Also Android by design will dynamically close apps to make room if it needs more RAM than you have available. Plus not clearing it will safe battery because the CPU will run less cycles when you use apps.
That's just my opinion, however I'm sure you have a reason as to why you wan to clear the RAM. I just thought it was with mentioning the above in case you didn't know.
Pilz said:
Why do you want free RAM? Free RAM is wasted RAM. Android doesn't need you to constantly clear the RAM. It's actually bad to do that because you need to use more CPU power to recompile the whole app when you open it again until we fully switch to ART which pre-compiles all apps.
Also Android by design will dynamically close apps to make room if it needs more RAM than you have available. Plus not clearing it will safe battery because the CPU will run less cycles when you use apps.
That's just my opinion, however I'm sure you have a reason as to why you wan to clear the RAM. I just thought it was with mentioning the above in case you didn't know.
Click to expand...
Click to collapse
Reason = Battery Drain. I don't use the Radio, EVER. So why is it showing in android os in the battery settings? Just like quite a few other processes sitting in that long ass list. That's why I ask.
illmatters said:
Reason = Battery Drain. I don't use the Radio, EVER. So why is it showing in android os in the battery settings? Just like quite a few other processes sitting in that long ass list. That's why I ask.
Click to expand...
Click to collapse
Why don't your freeze them with titanium backup if you are rooted?
Pilz said:
Why don't your freeze them with titanium backup if you are rooted?
Click to expand...
Click to collapse
Might just do that, thanks. I see LG Suite is using a lot. I dunno why though, that's fine If I freeze also? Requires $5.99. Gonna have to deal with it for a while, ive donated over $30 just today..
illmatters said:
Might just do that, thanks. I see LG Suite is using a lot. I dunno why though, that's fine If I freeze also? Requires $5.99. Gonna have to deal with it for a while, ive donated over $30 just today..
Click to expand...
Click to collapse
There's a free version if the app that allows you to freeze apps still, but it won't let you do batch operations if I remember correctly.