Related
I notice the phone start lagging when there are less than 100Meg of available RAM on both 2.1 or 2.2 SGS.
Questions....
1. How do i make sure there will always be min 130 available when not in use?
I'm currently using Froyo Task Manager, ATK and SystemPanel together to make that happen manually. A better suggestion or use of them will be appreciated.
I also tried MemoryPlus and Taskkiller (The red android logo)
2. There are so many background service running some of them start with com.samsung.... (what are these?) do we need them?
3. Why some Apps always run without us telling them to run, or ask us to give them to permission to run on background at will?
ATK
In ATK in settings you have auto kill level, which is disabled on default.
jakaka said:
In ATK in settings you have auto kill level, which is disabled on default.
Click to expand...
Click to collapse
I'm using JPC, ATK autokill will not able to kill at a system level like SystemPanel, so after a day of active use, the memory will still continue to reduce as some of the background service start consuming more and more memory or run more background process. E.g. Touchwiz from 17 Meg to 25 Meg.
So at the start with ATK, i will have 130Meg, after a day of active use i left with 80Meg. With Apps killed.
I use autokiller set to aggressive. memory left 152mb
ivanchin99 said:
I use autokiller set to aggressive. memory left 152mb
Click to expand...
Click to collapse
Cool, does that remain for few days? How often do you restart your phone?
free memory is bad memory!
why don't let android do it's job?! this ist linux with a clever memory management, not windows 95!!! deinstall all auto task killer android is handling the memory very well. it uses all it can get and if it's not enough it kills old uses apps from it. why have free memory, there is absolutely no reson for that! ram is fast, let the often used apps be there not on slow sd or nand!
Mykron said:
free memory is bad memory!
why don't let android do it's job?! this ist linux with a clever memory management, not windows 95!!! deinstall all auto task killer android is handling the memory very well. it uses all it can get and if it's not enough it kills old uses apps from it. why have free memory, there is absolutely no reson for that! ram is fast, let the often used apps be there not on slow sd or nand!
Click to expand...
Click to collapse
QFT!
What is the point of having memory if it is constantly empty?
Think about it this way...If you had five friends at your house and you have five chairs, do you make 2 or 3 of your friends stand so there is always empty space or do you let everyone sit down and worry about something worthwhile?
Finguz said:
QFT!
What is the point of having memory if it is constantly empty?
Think about it this way...If you had five friends at your house and you have five chairs, do you make 2 or 3 of your friends stand so there is always empty space or do you let everyone sit down and worry about something worthwhile?
Click to expand...
Click to collapse
True, upto a certain point... I don't think you need to have at least 100 or 150 mb free but it DOES seem to help to not let it get down to like 30mb...
For me:
-JM7
-animations off
-voodoo lag fix
-minfree manager set to preset agressive.
minfree manager customizes the android memory management system.
I love it this way, No lags when starting the Phone (DIALER) or anything else. The dialer annoys me the must, this must be lag free, if i want to dial i want to dial right away.
Btw, I think you have made some wrong assumptions about the Android memory management system, as mentioned, unused ram is wasted ram.
dagrim1 said:
True, upto a certain point... I don't think you need to have at least 100 or 150 mb free but it DOES seem to help to not let it get down to like 30mb...
Click to expand...
Click to collapse
Agreed but I have never seen my Galaxy with free memory that low and I don't use a task killer. Of course I don't often have more than 3 or 4 apps running at the same time
This is not about letting ram do nothing.you surely don't wasn't your ram get used up by programs you don't want while you had no hand in this.All those services running I don't want.badly written programs that are hanging out in memory instead of closing.at least in symbian an app closed when you exited.
Why would you have 100MB free ? Do you have any application that needs 100MB to run ?! The android system already has enough memory to run so even if you could have 200MB of free memory you phone wouldn't run any faster you would just be able to lauch around 20 apps at the same time.
Read this:
http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/
Linux however isn’t generally affected by this. While I admit that I don’t know the architecture and reason for this… linux will run the same regardless of if you have 20mb free memory or 200mb.
Click to expand...
Click to collapse
Finguz said:
Agreed but I have never seen my Galaxy with free memory that low and I don't use a task killer. Of course I don't often have more than 3 or 4 apps running at the same time
Click to expand...
Click to collapse
Dunno, I just noticed that one time my phone was VERY sluggish and memory free was around 20mb or so. Cleaning it up did seem to help (unless one of the programs killed was causing the lag of course).
Ah well... Whatever people choose right?
You guys can argue all you want that free RAM is a waste of RAM....
But it is a fact that the SGS runs much slower when the free RAM is low. This is the experience of all the SGS'es I have tried and my own as well. At least this is the case when running 2.1. I have not tested anyone with 2.2 yet.
It s starts to lag when memory is below 40 mb. So when it s low and you start an application it starts to lag. I set it to 50-55-60 and got hardly any lag. No need to keep so much free ram
Sent from my GT-I9000 using XDA App
matty___ said:
It s starts to lag when memory is below 40 mb. So when it s low and you start an application it starts to lag. I set it to 50-55-60 and got hardly any lag. No need to keep so much free ram
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Which ROM are you using? as the low memory killer level for background apps is set at 40M which means you should have 40M free all the time or it will start killing background apps. This is also why task killers are useless, free ram is wasted ram for android.
I never had the experience that more free RAM is faster, perhaps with the stock rom but JC and upwards are all good by default. Animations off + Oneclick lagfix (or another) and the phone stays totally lag free.
Being an android user for 1,5 years now i'm very confident Taskkillers are useless except when an app is stuck. I've had periods where I used them allot but the phone only gets slower as the killed apps have to be loaded into the memory again.
Finguz said:
QFT!
What is the point of having memory if it is constantly empty?
Think about it this way...If you had five friends at your house and you have five chairs, do you make 2 or 3 of your friends stand so there is always empty space or do you let everyone sit down and worry about something worthwhile?
Click to expand...
Click to collapse
Provided you are not expecting anymore friends. The problem happens if all your 5 friends are happily seated and along comes 2 more friends a-visiting. So you have to now move 2 inactive (for want of a better word) friends out of the seats so that you can accommodate the 2 new ones. This takes time. So why not move these friends out as soon as they become inactive so that the space is readily available when someone comes calling?
Try to have a read about garbage collector before argueing about free memory.
The more you try to have a large amount of memory, the more you will need major GC (and during major GC all activity is frozen).
If you let the system manage memory, it does minor GC as needed when it reaches min memory waterline (seems to be 50Mo on SGS).
Let the system do its job.
Get rid of task killer.
Mykron said:
free memory is bad memory!
why don't let android do it's job?! this ist linux with a clever memory management, not windows 95!!! deinstall all auto task killer android is handling the memory very well. it uses all it can get and if it's not enough it kills old uses apps from it. why have free memory, there is absolutely no reason for that! ram is fast, let the often used apps be there not on slow sd or nand!
Click to expand...
Click to collapse
I completely disagree. OK, it is better to use memory, but the android memory management is extremely inefficient since it does not know which foreground and background processes are important to the user and which are not, even though it tries to figure that out. Since the Galaxy S does not allow the system to use the full 512MB of memory, this can be a critical factor. And the Galaxy S definitely lags massively when less then 70 or so MB of free RAM is available this is definitely a fact.
The biggest problem is that you cannot manually close apps and only have multitasking access to the last 6 apps used. If you use 7 apps simultaneously, the 1st app still consumes memory but you cannot even switch back to it. And there are so many useless background processes, starting up over and over again and consuming hundreds of MB memory if they are not killed in regular fashion.
Who needs gesture search, amazon mp3, layar, and all the samsung crap running in the background all the time. If you only have 10 such applications and each of them only consumes 15MB of ram, 150MB are wasted for nothing.
Every second market application registers itself as autostart on every boot, so to use a autostart manager is also mandatory.
Since everybody can easily develop for Android the application quality and resource efficiency is not always perfect. So in my opinion Android needs a task manager, this is why even Samsung integrates such a application.
Using a well configured ATK (set to ignore system applications, widgets and apps frequently used for multitasking and killing every else on screen off) and autokiller (strict setting) in addition to Autostart Manager (had to remove 40!!! useless apps from automatic startup) and lagfix, the SGS runs perfectly smooth.
Is there a particular rom which offers better ram management to allow for apps to stay in the memory longer, and cached apps get less priority?
I'm getting annoyed of apps that are suppose to be running all the time in the notification bar, but they are constantly restarting because the ram gets too low, but in fact, there is enough ram, but it's being taken up by cached apps instead!
Maybe I'm asking too much. Are there ROMS which:
1) offer more ram by being "trim"
2) manage memory better for multitasking
I really wanted to keep this phone stock, but this is pathetic! I feel that my old phone, with a "huge" 256mb ram chip was able to run more software in the background than my GN is! I've stripped all the useful apps off this phone and memory management is still an issue.
isn't the kernel responsible for that and not the rom?
zephiK said:
isn't the kernel responsible for that and not the rom?
Click to expand...
Click to collapse
Good question. I figured some roms are made lighter by removing stuff on it you don't need, and when it's done on a system level, I assumed that less ram would be needed for the os to operate.
Maybe someone can explain this?
Sent from my Galaxy Nexus using Tapatalk
I mean yeah, to a extent.. I'd believe that ROM and Kernel both contributes to it but kernel is the bigger player when it comes to optimizing "RAM."
I use AOKP + Franco Kernel if that helps. No lag problems, never even had it when it came to stock ICS. You'd might want to check your apps and see if there's a bad app causing memory leaks.
EP2008 said:
Is there a particular rom which offers better ram management to allow for apps to stay in the memory longer, and cached apps get less priority?
I'm getting annoyed of apps that are suppose to be running all the time in the notification bar, but they are constantly restarting because the ram gets too low, but in fact, there is enough ram, but it's being taken up by cached apps instead!
Maybe I'm asking too much. Are there ROMS which:
1) offer more ram by being "trim"
2) manage memory better for multitasking
I really wanted to keep this phone stock, but this is pathetic! I feel that my old phone, with a "huge" 256mb ram chip was able to run more software in the background than my GN is! I've stripped all the useful apps off this phone and memory management is still an issue.
Click to expand...
Click to collapse
AOKP and a few other roms have the option to change the minimum ram before android os starts killing background apps. The default is about 80MB I believe. You can decrease it (do not forget to check set on boot), but I do not think it is recommended to go too low.
If you are having low memory issues its probably because of a rogue app. Install System Tuner and check for background apps that use more than ~10-20MB of memory.
The title is basically the question, im fed up of alot of programs auto opening on my android phone, it takes battery and is slightly annoying receiving notifications off apps i dont really care about such as the NFL game tells me about small things in the NFL, im in the UK, i dont care.
If you argue that it doesnt take alot of battery currently have 117mb free ram, (2 secs later) killed all my selected apps now have 201mb free so im using 80mb of ram on apps im not using. Ive made 2 or 3 phone calls today no more than 30 mins long altogether and ive lost 55% of my battery since about midday, which is when i unplugged the phone.
And I think all these apps are the problem so how can I stop them from auto opening, please help
Search the market for startup cleaner
Sent from my A101IT using xda premium
yusuo said:
If you argue that it doesnt take alot of battery currently have 117mb free ram
Click to expand...
Click to collapse
More free RAM doesn't really equate to longer battery life or lower power consumption.
Better search for auto starts, this asp shows you the conditions an asp can turn back on and you can bin it off, Facebook for example had like 8 conditions, from full to medium battery life, on charge and change in network....... Use it
Sent from my HTC Desire using xda premium
rootSU said:
More free RAM doesn't really equate to longer battery life or lower power consumption.
Click to expand...
Click to collapse
There's still no reason for most of this apps to use RAM. Apps like facebook and skype shouldn't be actice without user permission. Without login they are complete useless.
I'll try Startup Cleaner, thx.
It's how android works and what RAM is for. There is always a reason.
Sure if someone doesn't use Facebook, it should be uninstallable, but its not and its not causing any harm
Sent from my HTC Desire using Tapatalk
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
rootSU said:
RAM doesn't use more power, the more its used, no.
You don't need a task killer. You do not need to obsess about RAM. Forget about RAM and enjoy your phone
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Thanks for you reply but its not really an answer its more of a contradiction, what I was asking is how to I stop apps from auto starting and eating up RAM, regardless of how long the phones been on
...and I'm telling you its a pointless, unecessary waste of time. Also it is not possible. Autostarts as already mentioned is the closest you'll get
Sent from my HTC Desire using Tapatalk
I also turned off the autorun permissions of a lot of apps, for 2 reasons: 1) a device that is smooth sooner after booting, using less cpu cycles/power. 2) preventing Sense from reloading due to RAM shortage and have smooth multitasking.
1) Android loads a bunch of apps to the RAM that have the autorun permission, until it thinks it is "enough" and useful to you. No matter how many apps you have installed, the amount of free RAM is always about the same, just the number of "unwanted" apps in the RAM differs. Removing the autorun on boot permissions prevents the loading of unnecessary apps that will immediately be removed from the RAM the moment you start the browser/a game, saving cpu cycles=power. So for me there is no point in loading them in the first place, because I am never going to use them (right away). I want the apps that don't to any syncing loaded on demand.
2) I hate slow multitasking and I hate it even more when Sense reloads because it got kicked out of the RAM after each time I press HOME.
I use 3G Watchdog (~12MB RAM), Unlock with Wifi (~8MB), Whatsapp (~15MB), Handcent SMS (~18MB), Droidstats (~13MB), Extended Controls (~12MB), Battery Monitor Widget Pro (~13MB). Okay, I maybe could delete some of them, but these app are "OK" to me, because I use them actively or just need a background service to operate normally.
With Gemini I disabled apps like Facebook, a screenshot tool (just load when I want to make a screenshot..), various public transport planning tools, etc from autostarting.
No joy moment: after using the Facebook app (market version), it may take up 50+ MB and it will not be closed when I start another RAM intensive app, because it is a high priority service. Result: Sense gets kicked out of the RAM. Or, when the situation is somewhat less critical: multitasking is as good as unusable: switching between apps makes them load over and over again, because app2 kicks app1 out of the RAM and vice versa, causing unnecessary lag. Therefore: when I am done with facebook, I close it, then STAY the hell closed It may only autostart when it receives a push message. In that case it is nice to have FB already in RAM when I tap the notification.
Why do even some games have background services, or the Engadget app, or .. , or... all eating precious RAM. And yes, I know, once IN the RAM they eat no battery, but they DO eat battery when the app loads itself back in the RAM when it thinks it needs to, after it got kicked the moment I decided to so something else.
Hmm, spent way too much time to try to explain my frustration Oh and by the way, I have a Legend, but the basics are the same of course.
Dwnload an app called internet commander from the market. It shuts off the internet when your screen turns off but still let's you get calls and texts. I've got my phone , rooted of course, clocked to 710 and my battery will last for days.
Sent from my Eris using xda premium
I just re read your post, that won't help with apps but it will help save battery. And when you turn your screen on the internet kicks right on instantly. Good luck
Sent from my Eris using xda premium
yusuo said:
The problem isn't that apps start when I turn on the phone its that even after i use task manager to close they keep reopening and use over 100mb of ram, earlier I checked and only had 78mb ram available.
This must have an effect on battery to some degree i want to kinda ban certain apps from running in the background unless i specifically tell them to
Click to expand...
Click to collapse
The guys here have already suggested you use a certain program from the Market. Have you tried it?
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
TVTV said:
Regarding the whole RAM consumption issue, Android has its own built-in memory management system that ensures that there's always enough RAM for an app whenever it needs it, even if the memory manager shows like 40 MB free. Basically it "ejects" all background, unused apps, from memory making room for the foreground app which needs it most. If for some reason you need to fiddle with that, you can try using the V6 Supercharger script. I find it suitable for my needs but YMMV. It's completely reversible, so if you don't like it you can uninstall it just like that.
P.S. - I agree with rootSU, the ammount of free RAM has nothing to do with battery consumption. If you suspect that an app is draining your battery, check Android's battery statistics to find the culprit.
Click to expand...
Click to collapse
I respectfuly disagree. Android built in ram management is just silly. If I open xda app for example (it could actually be any app for that matter), reply to a few posts, read a few more and close it, why does it need to stay in ram? It reloads anyway when I run it again after I've closed it (using the back button or the actual exit command in the app itself). Why does the camera app need to stay in the background after I just shot a few photos and closed it? Because I may or may not use it again in some time? It's rediculous. And the whole theory that ram management doesn't require any power/cpu usage, how do you guys think all those apps get killed? Android will power?! No, kernel scans all running apps and kills the ones based on built in heuristics so it also reads them first. So that doesn't require any power/battery? Awesome if it's true! Although I wouldn't bet on that. And all this fuss just because you may or may not launch the same app sometime during the next day/week/month/year or it'll eventually get killed? Now that's just plain stupid. I get apps that need services like widgets, push notifications etc. but random apps like root explorer, xda app, titanium, youtube etc. which are opened specificly by the user shouldn't be in ram just for the sake of it after they're closed. I closed it, meaning I don't need it anymore. And I don't need the kernel to scan all apps and running services every time I launch an app so it could provide the free ram that app needs. Consumes cpu time, battery, i/o ... every piece of hardware actually just to free some ram that shouldn't be occupied in the first place. Every app that I ever opened on my phone got loaded almost instantly and that's just after phone had been booted. So after that it should stay in ram so I could open it in a blink of an eye instead of instantly? That's just funny.
Anyway, I'm just thinking out loud so don't flame me immediately. There probably are apsects of it that I didn't mention here or am not aware of. And I'm not saying that I'm right and you guys are wrong, I'm just saying what I know and think about this subject.
-. typewrited .-
PlayPetepp, while it might be true that the OS allocates (thus use) some resources to memory maintenance, the impact on battery life is negligible. In the Android OS, apps in memory are ordered according to priority and state, so the OS always knows which apps to kill first if it needs to make room in RAM, without much of a hassle. The only bad consequence of this system seems to be the fact that once the memory fills up, the launcher may lag or even be evacuated from memory. But, as i've mentioned in my previous post, there are ways to prevent that, either via scripts or, if you know what you're doing, via editing system files.
So the OS doesn't need to scan anything as it keeps everything in memory again? Seems like an endless loop. Open, sort, kill if needed, reopen, sort again, kill ... to what end, constant unneccessary multitasking that user is unaware of? I really don't see any benefit of that system and am only seeing the downsides. I mean, who needs every app they ever run remain in ram even if they close them after using? And then opening another app and "waiting" for whatever needs to be closed to get it running. Sure you can mess with the scripts (init.d, init.rc, etc.) but the underlined conditions stay the same. I hope I'm making sense here. Or am I fighting against windmills.
I just figured out that I strayed from the topic of this thread so won't be continuing this discussion if it's considered offtopic.
-. typewrited .-
Stop looking for excuses for poor multitasking in Sense 3+ roms
erklat said:
Stop looking for excuses for poor multitasking in Sense 3+ roms
Click to expand...
Click to collapse
Hello again nice to see you here
Here's an interesting article on what I was talking about. Sense 3.5 doesn't need that many mbs of ram to work smoothly. After booting and setting everything up I have 150+ mb free. That should be enough for decent multitasking but all those apps not getting killed when you close them are eating too much. Can anyone explain in detail what hidden app, perceptible app, backup app and heavy_weight app means? I've been googling this for a week and can't find any decent explanation.
@PlayPetepp - I think i have already said (in my previous post) that the OS does indeed use some resources for managing the memory, but they are negligible in terms of their impact on battery life. IMHO, the only thing a 3'rd party memory manager (task killer) WILL do is improve lanuncher responsiveness (lag) as the lag does increase when free RAM drops under a certain limit. Thus used wisely, a task killer can improve responsiveness, but battery life... very little, in rare cases (it does the opposite, most of the time).
Regarding the so called "memory slots", here's an excerpt from this article:
FOREGROUND_APP: This is the application currently on the screen, and running
VISIBLE_APP: This is an application that is open, and running in the background because it's still doing something
SECONDARY_SERVER: This is a process (a service that an application needs) that is alive and ready in case it's needed to do something
HIDDEN_APP: This again is a process, that sits idle (but still alive) in case it's needed by an app that's alive and running
CONTENT_PROVIDER: This is apps that provide data (content) to the system. HTC Facebook Sync? That's a CONTENT_PROVIDER. So are things like the Android Market, or Fring. If they are alive, they can refresh and provide the content they are supposed to at the set interval. If you kill them, they can't of course.
EMPTY_APP: I call these "ghosts." They are apps that you have opened, but are done with them. Android uses a unique style of handling memory management. When an activity is ended, instead of killing it off Android keeps the application in memory so that opening them again is a faster process. Theses "ghost" apps use no battery or CPU time, they just fill RAM that would be otherwise empty. When this memory is needed by a different application or process, the RAM is flushed and made available for the new app. To satisfy the geekier people (like myself) Android does this by keeping a list of recently used apps, with the oldest apps in the list given the lowest priority -- they are killed first if RAM is needed elsewhere. This is a perfect way to handle 'ghost' processes, so there's no need to touch this part
Click to expand...
Click to collapse
Hi Folks,
I've got the ZE551ML 2.3Ghz/4GB RAM/ 64GB ROM/ USA Version.
I picked up this phone mainly because of the 4GB RAM- I'm sure many of you did the same.
I multitask a lot and would rather not have to quit/close apps and let the memory management handle that.
I've noticed that the default RAM use by the phone (immediately after bootup), is TOO high (about 2GB used), with no background apps but a few background processes running (your FB/ Messenger/ Whatsapp/ Twitter - not too many, just these).
Have noticed that opening several 'light' apps (non- CPU/GPU/RAM intensive apps, fills up the RAM usage significantly). Last night, with less than 50MB free RAM left, the phone froze up and re-booted. This is a sign of very bad coding. Shouldn't the OS be able to kill tasks that have not been recently run to free up RAM?
Do any of you face similar issues? What are your workarounds? I'm aware that ZenUI is extremely RAM intensive itself.
P.S I am aware of 'Memory Leaking Issues'
I get the same. It starts using around 2GB. I had also noticed some apps, like WhatsApp/Snapchat growing to consume 4-500MB over time. That said, it has never froze up on me. I didn't notice Zen UI taking up a lot of RAM at any point, but I started using Nova pretty early on and have frozen most of the ASUS/Zen stuff through Titanium. I'd suggest you root it, if you haven't already, and start freezing out apps you don't use/prevent apps from auto-starting. That helps a lot.
Even leaving 2GB to start with, that's a ton of RAM for multi-tasking, unless you're using especially RAM-intensive apps (aside from the leaking issue). As for a fix, I'm not aware of any yet. We're all pretty much waiting for a new update so we get 5.1.x, where the leak is fixed. Even better, waiting for an AOSP/CM ROM to be released so we can be done with this ASUS stuff to begin with. IIRC there is an Xposed module for the memory leak issue, but last I read it wasn't working (for this device at least).
There must have been some optimizations made with the most recent two updates because the apps I noticed issues with before aren't consuming anywhere near as much RAM as before. WhatsApp/Snapchat are currently using ~220MB combined, whereas before it could get close to 1GB.
Thanks for the Reply.
I'd love to Root the device but unfortunately with corporate email and Mobile-Iron, this is an impossibility. (Consequently even Mobile Iron hogs a portion of the RAM).
Considering that a lot of devices even being released at the moment have 2GB RAM and this is allocated to System resources as well as back-grounded apps. How do those companies manage the memory in half the RAM as the ZF2 (considering they would also face similar memory leak issues)
If you are thinking of RAM usage from a Windows user's perspective, you might be feeling this way. There is no harm in RAM being used. In fact Linux or Android loves caches so much that they fill it up most of the time. And since we have 4GB, why not fill up about 3GB? If a device has lower memory altogether, say 1GB, it will only fill up about 700MB. But of course the memory leaks in 5.0 cause major irregularities.
Bottom line is RAM hogging isn't really an "issue" as far as i am concerned. The issue would be if the RAM does not get released for important tasks and the device starts to lag. But I don't see this happening, so why complain right? However this is just my opinion.
after updating to 2.19.40 my phone also started to consume a lot of ram .....even goes to 645 mb free sometimes
That's perfectly fine. Free RAM is wasted RAM. The OS wants to keep about 500MB or more free because beyond that you do experience slowdown. Above that, it's all gravy.
The system generously allocates that much RAM to itself because it can and to ensure core processes and ZenUI don't slow down. Android caches aggressively so switching between apps will be faster.
Auto-start Manager and Clean Master app, can help free up RAM
Sincerely,
ASUS_USA
I can live with the Nexus 5X' relative sluggishness when compared to the Nexus 5, but what really stops me from doing my work is the phone killing apps when I switch between them.
Example: I may be filling out a form on a website in Firefox for Android. I need to look up a word in the dictionary, so I switch over to the dictionary and look up the word. When I switch back to Firefox, the application has obviously been killed, as it reloads the page.
Example2: I'm listening to the Audio version of the Economist via the Economist app. The speaker mentions a certain placename and I open the Google Maps app in order too find where it is on the map. Suddenly the audio will stop playing - the app has been killed.
The above gets considerably worse when switching between more than two apps and is really hindering my work and productivity.
Now this almost never happened on the Nexus 5, which also only had 2 GB of RAM. So is it the power saving feature of the Nexus 5X kicking in? Is there a way to stop it from happening?
Marshmallow simply has very bad RAM management from what I've seen. I used to have the Nexus 5 too and as you said, multitasking was a very good experience on it (especially on Kitkat). Google's OS takes more of the phone's resources after each update (with no major new features or improvements). Marshmallow looks exactly the same as Lollipop, except for the tiny feature of apps permissions, and the Now on tap that I barely use (same for Android pay which I'm sure most of Nexus 5x owners won't even be able to use it outside the US). So I still don't understand why they had to jump so fast to a new version of Android while Lollipop still had a ****load of bugs that need fixing, they could've worked more on Lollipop to perfect it first then give us Marshmallow after 2 years maybe, we're not in a hurry.. I just hope they don't stop again at Marshmallow 6.1/6.2 or something and introduce Android N *sigh*
Sounds like you have more user installed apps with constantly running background services installed that the phone can comfortably handle with 2GB memory.
Check the memory stats in Settings - if the average over all the time options is 1.6GB or above used then your phone is going to struggle and cached apps are going to be getting cleared out when switching regularly. Look down the list particulary for apps running close to 100% of the time with a big RAM fingerprint. Also check running services in developer settings to get an idea of what is running a service all of the time.
Once you've identified the worst offenders make that difficult decision - is the apps utility worth it for the impact on performance. Consider reporting the memory use to the developer, particularly if it's much lower after a reboot and increases over time. Plenty of playstore apps ship with clear memory leak issues.
Other than that the other option is reasonably regular reboots to keep the system fresh and clear out any memory leaks.
thanks for the suggestion. Well here's the top 5:
Android operating system 524 MB
Wechat 156 MB
Firefox 117 MB
System UI 105 MB
Android system 99 MB
Clearly it's mostly the system using all resources. Firefox and Wechat, sure, I find them rather essential to my life, but together they don't even use as much as the OS.
Thing is, I can't remember this happening on the Nexus 5.
Sounds like you may have some apps using up a lot of your memory. I haven't been seeing any redraws with my apps, even 24+ hours of sitting in the background. The other day I was switching between gaming, streaming a live sporting even, and text messaging and the phone didn't drop a beat despite the game alone using 600MB of RAM.
Are those the average RAM or peak?
that's what shows up when I get the details of the RAM usage through settings
still this never happened on the Nexus 5, at least I can't remember
Yeah, I have a hard time believing it's the apps. I never had this issue come up in my Moto X 2013 (also 2 GB of RAM) using the same apps. We're seriously talking about one app open, switching to another app. No reason switching back to the first app should have everything reload.
Unless by "some apps," you mean that they have somehow not been optimized for Marshmallow in some way or other. But the apps simply running a process? A smartly-made OS (Lollipop, KitKat) will know "Hey, we have to kill something to free up RAM? Why don't we kill an app that hasn't been used in a while?" and a less-smartly-made OS (perhaps Marshmallow...?) will think "Hey, we have to kill something to free up RAM... why don't we kill the app the user just used?"
And there are two figures there - average and peak - which are those?
If there are the averages rather than peak then both Firefox and Wechat have got a problem.
---------- Post added at 06:42 AM ---------- Previous post was at 06:34 AM ----------
Marshmallow and Lollipop low RAM behaviour is pretty much identical and quite aggressive (the OS tries to preserve quite a chunk of free memory which is uses on the sly as a display buffer), KitKat was less aggressive.
I don't have any problem multitasking on my Nexus5x, but then again for the apps I've got when I check the memory tab I'm normally averaging 1.2-1.4GB used and 400-600MB average memory free so there is plenty of space for the OS to gracefully cache and uncache processes. If the phone is normally running at 1.5GB-1.6GB used and 200-300MB then the LMK is going to be kicking in frequently. It kicks in at around 250MB free on a Nexus5x.
It was the default setting, i.e. average. HM ok good to know. It's happening quite often when listening to the Economist too. Which is really bull****, it should treat it as audio playing. Why would Android kill your music.
I agree music players don't get the priority they should, although that particular 'bug' at least gives a clear symptom that lack of free RAM is an issue, if not the cause of the issue e.g. the OS, to many running services from user apps, or a particular user app with memory leak issues.
I came to the Nexus5x from a 1GB Moto G where it was almost impossible to keep background music running in combination with navigation after Lollipop without uninstalling pretty much everything else user installed and have got used to monitoring the RAM footprint and behaviour of apps as a result.
I've suffered the problem once since I've had the Nexus5x and that was due to the music player (Soundcloud) being a memory hog (120MB+) with it's background music player service coupled with a memory leak in the driving app I was testing at the time - Automate - it was peaking at 460MB use.
I'm not so precious about what is installed now but anything that wants to run a constant service either has to be tiny when running that service or absolutely fundamental to my use of the device.
I find this to be the worst problem .We want to kill our apps like we are use to.Switching between email and chrome is horrible especially when you have to start your application all-over again (submission request) Hopefully some XDA member will figure out how to solve this issue. For now I am testing DEVELOPER OPTIONS allow running
apps in background ? Anyone know what the default value is??