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??
Related
Hello Android Gurus
I have bought Galaxy S (My first Android phone) 2 weeks ago and i have been experimenting with it since. I have noticed one thing regarding how android manages memory and its quite alarming.
When i start my phone I typically have around 160 Mb of RAM. As i load an application that requires 10 MB for example, the available RAM evidently drops to 150 MB but when I kill the application the RAM goes up but not to the previous level (e.g. goes up to 157).
little RAM is always lost as applications are opened and closed. This means that after a couple of hours of using the phone, the RAM goes down to 40 MB and the phone becomes REALLY laggy and you have to restart
The above behavior is typical of windows mobile, and that is exactly why i shifted to Android thinking it is better.
My questions to the android experts out there are the following:
1- Why is memory leaking like this. Such a behavior results in a phone with very bad user experience
2- Is this typical behavior of Android, if yes then i'd better sell my Galaxy S and look for an alternative OS
3- Is this due to TouchWiz by Samsung, if yes then i will wait for subsequent updates to see if this problem could be resolved by Samsung
4- Will the 2.2 Froyo update resolve this issue ?
I used to have an iphone 3gs before this one, and no matter how much you open or close applications, the UI is always smooth and responsive. The thing that made me really hate Apple and its products is their "Closed OS" that does not enable you to do much with your phone. That is why i moved to Galaxy S thinking it would give me a better experience
Thanks for your thoughts.
FREE RAM IS A WASTED RAM, golden rule of android.
Some time ago I did even a video so you can check what i'm talking about... http://www.youtube.com/watch?v=Ewxuy12KuUA
Dexter666 said:
FREE RAM IS A WASTED RAM, golden rule of android.
Some time ago I did even a video so you can check what i'm talking about...
Click to expand...
Click to collapse
That's an awesome video! I never knew the games looked so nice. I'm on a download spree because of that video now
Strange
Dexter666 said:
FREE RAM IS A WASTED RAM, golden rule of android.
Some time ago I did even a video so you can check what i'm talking about... http://www.youtube.com/watch?v=Ewxuy12KuUA
Click to expand...
Click to collapse
This is quite strange, the less RAM you have the more non-responsive the phone is and laggy.
Enough RAM has to be maintained to guarantee a smooth user experience.
If the phone requires 100Mb of RAM to run smoothly, then this much has to be maintained.
from my experience with the Galaxy S, there has to be atleaset 80 to 100 MB to maintain a somewhat smmoth interface.
Edit:
I also understand from your input that this is a Samsung problem, not an android problem, and that no matter how low the RAM is, the interface will always be smooth ??????
Mate, just one word - google.
There are about a billion articles online on android memory management, how to impoove it etc.
Dexter666 said:
FREE RAM IS A WASTED RAM, golden rule of android.
Some time ago I did even a video so you can check what i'm talking about... http://www.youtube.com/watch?v=Ewxuy12KuUA
Click to expand...
Click to collapse
i dont understand how this shows anything? You are manually exiting each one of the games, forcing it to quit anyways. A better test is just to hit the home button, and continually load up the next game.
andy2na said:
i dont understand how this shows anything? You are manually exiting each one of the games, forcing it to quit anyways. A better test is just to hit the home button, and continually load up the next game.
Click to expand...
Click to collapse
This means that after a couple of hours of using the phone, the RAM goes down to 40 MB
Click to expand...
Click to collapse
+red baloon on vid which says phone was used for >day, so "free" ram was <50MB, becouse browser etc. reserve some MBs for quick comming back.
And still was no problem to run anything I choose.
Dont quite understand..care to explain more? I'm getting puzzled abt this shortage of ram thingy. Some suggest to use task killer to free up rams while you say dont. But looking at your videos its fast..please explain. Thanks
Sent from my GT-I9000
Android handles the memory management itself. The moment it runs below certain amount of free memory it will start the kill apps. There is no need to run an app killer. Altho the default settings are not enough to provide a smooth experience. Check out the freememmanager app in the market to change the settings. As long as min 45 mb is free everything will run smooth.
Sent from my GT-I9000 using XDA App
RADLOUNI said:
2- Is this typical behavior of Android, if yes then i'd better sell my Galaxy S and look for an alternative OS.
Click to expand...
Click to collapse
This is typical Android behavior. See ya later.
Really though, if you're killing tasks, then you're already taking horrible advice from people who haven't an inkling of an idea on how Android manages memory.
Keep in mind that your phone is only using 256MB of its total 512MB of memory. Once a newer kernel is released with himem the phone will use all 512MB.
Android's garbage collection can be set to be more aggressive which would sort of fix your issue by killing more background applications. However, you might as well wait for the newer kernel which will fix your problem anyway.
Though it was more 320 out of 512
Sent from my GT-I9000 using XDA App
RADLOUNI said:
The above behavior is typical of windows mobile, and that is exactly why i shifted to Android thinking it is better.
My questions to the android experts out there are the following:
1- Why is memory leaking like this. Such a behavior results in a phone with very bad user experience
2- Is this typical behavior of Android, if yes then i'd better sell my Galaxy S and look for an alternative OS
3- Is this due to TouchWiz by Samsung, if yes then i will wait for subsequent updates to see if this problem could be resolved by Samsung
4- Will the 2.2 Froyo update resolve this issue ?
Thanks for your thoughts.
Click to expand...
Click to collapse
This has to do a lot with Android's garbage collector. The reason task-killers are not the best way to go, is because when you kill tasks a lot of the memory is not recovered (garbage collector does not work as it should). Android by default won't start killing apps until you get between 20-30MB of memory. For some reason, in the SGS, as you said, when ram drops below 70MB, the phone starts to feel pretty laggy; the best way to remedy this is to use applications like autokiller or minfreemanager, which require you to be rooted.
For a more in-depth explanation of how android kills processes see this http://andrs.w3pla.net/autokiller/details (from the developer of Autokiller).
I would like to know why the phone feels so laggy when ram drops below 70MB, from what I understand, this shouldn't be the case...
2- Is this typical behavior of Android, if yes then i'd better sell my Galaxy S and look for an alternative OS
--> No, this is not typical behavior of Android, i use my HTC Magic before Galaxy S, no lagging problem even the memory is lower than 15MB.
The galaxy S defaults are too low for when it starts removing apps from RAM, you need to root it and then install minfree manager or autokiller (which is not a task killer don't be deceived by the name)
Brantyr said:
The galaxy S defaults are too low for when it starts removing apps from RAM, you need to root it and then install minfree manager or autokiller (which is not a task killer don't be deceived by the name)
Click to expand...
Click to collapse
doesn't solve the mystery because this is a non-issue on other android phones.
why do i need to keep 50-70mb free to get a smooth running phone where others can handle 30mb free without problems.
Goshh..thanks for simplified. Now ive removed the task killer..and stand firm by the android golden rules...cheers..
Sent from my GT-I9000
I noticed this same low ram behavior on my galaxy s. After boot the phone shows like 180 mb of ram free after a couple days the phone will drop down to 30 mb of ram all the while I'm killing apps running in the background with task killer.
The phone slows down significantly even after I kill everything.i thought android was supposed to circumvent these kind of low ram Issues.
inurb said:
I noticed this same low ram behavior on my galaxy s. After boot the phone shows like 180 mb of ram free after a couple days the phone will drop down to 30 mb of ram all the while I'm killing apps running in the background with task killer.
The phone slows down significantly even after I kill everything.i thought android was supposed to circumvent these kind of low ram Issues.
Click to expand...
Click to collapse
It is.
And you're supposed to not be messing with how Android manages things cuz taskkilling screws it up.
reuthermonkey said:
It is.
And you're supposed to not be messing with how Android manages things cuz taskkilling screws it up.
Click to expand...
Click to collapse
So you suggest that I not force close any apps using taskkiller and just let android 2.1 do it's thing with memory management?
When I had the phone for the first week without taskkiller installed, the device ran very slow after the first couple days of use. Your saying that the slowness will go away as android dishes out memory effectively?
I'll uninstall taskkiller and let the device run longer than a week and see if it ever speeds up. thanks
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
I'm still pretty new to Android so I don't know what is normal, but why does the system use so much RAM when it is supposedly doing nothing? On my 2GB model, after a reboot it says that 1.2GB are free, but this soon drops to 900MB and continues to drop to 500 or 600MB, even if all apps are closed. Is this something I should just ignore and trust that tge Android system knows best and uses RAM appropriately?
kanagawaben said:
I'm still pretty new to Android so I don't know what is normal, but why does the system use so much RAM when it is supposedly doing nothing? On my 2GB model, after a reboot it says that 1.2GB are free, but this soon drops to 900MB and continues to drop to 500 or 600MB, even if all apps are closed. Is this something I should just ignore and trust that tge Android system knows best and uses RAM appropriately?
Click to expand...
Click to collapse
This must be the well-publicised Android 5.0.x memory leak.
DanielKennethRego said:
This must be the well-publicised Android 5.0.x memory leak.
Click to expand...
Click to collapse
Possibly, but my Memo Pad 7 seems much the same, and that's still on 4.4.2
If there is free memory then Android will let the apps sit in memory invisibly even after you have closed them - this way they will load faster next time you launch them. If the amount of free memory gets low Android will close some of those invisible apps. So that is normal, unless the amount of free RAM keeps decreasing while you do nothing with it - in that case there must be some bad memory leak.
In android, unused memory is kind of waste so system will allocate usage in a high percentage for efficiency.
DanielKennethRego said:
This must be the well-publicised Android 5.0.x memory leak.
Click to expand...
Click to collapse
graphO said:
If there is free memory then Android will let the apps sit in memory invisibly even after you have closed them - this way they will load faster next time you launch them. If the amount of free memory gets low Android will close some of those invisible apps. So that is normal, unless the amount of free RAM keeps decreasing while you do nothing with it - in that case there must be some bad memory leak.
Click to expand...
Click to collapse
xda_husky said:
In android, unused memory is kind of waste so system will allocate usage in a high percentage for efficiency.
Click to expand...
Click to collapse
kanagawaben said:
Possibly, but my Memo Pad 7 seems much the same, and that's still on 4.4.2
Click to expand...
Click to collapse
It is not a memory leak. All devices which are on papers 2GB are actually less than that. Take memory for example. My Nexus says 32GB but I get around 27GB. Same goes on with USB flash drivers/ pen drives.
Secondly, On Windows, you want to keep as much RAM available as you can so that programs have enough room to operate. When RAM fills up, Windows is forced to start using hard drive space as virtual RAM and hard drives are much slower than physical RAM.
This is not true for Android.
Android’s operating system has its own native handler for assigning RAM to apps and making sure that all of it is being used in the most optimal way. In fact, Android purposely tries to keep apps loaded into RAM for better performance. RAM is fast, remember? On mobile devices, every bit of speed is critical for a good user experience, so keeping apps in RAM is actually a good thing. So regardless how much your RAM is shown, it wouldn't affect your user experience unless the apps installed in your phone are more than RAM can handle at a time which means either update your phone with more RAM or uninstall your apps that you do not use!
Hnk1 said:
It is not a memory leak. All devices which are on papers 2GB are actually less than that. Take memory for example. My Nexus says 32GB but I get around 27GB. Same goes on with USB flash drivers/ pen drives.
Click to expand...
Click to collapse
That is not what OP is saying, at all.
DanielKennethRego said:
That is not what OP is saying, at all.
Click to expand...
Click to collapse
The OP says that the memory decreases over time. If you read my post again, i simply said as you more applications are loaded over time, the memory starts to decrease! This is what causes the memory to decrease and if you could use a bit of logic, you could have easily come to the conclusion
Hnk1 said:
The OP says that the memory decreases over time. If you read my post again, i simply said as you more applications are loaded over time, the memory starts to decrease! This is what causes the memory to decrease and if you could use a bit of logic, you could have easily come to the conclusion
Click to expand...
Click to collapse
...And that is not what I quoted in my reply, is it?
DanielKennethRego said:
...And that is not what I quoted in my reply, is it?
Click to expand...
Click to collapse
Sometimes it's good to swallow some pride and in that there's more dignity. I explained everything from bits and pieces and I'm sure OP can conclude it unlike you.
Do not hesitate to quote me for any query. Always welcomed
Hnk1 said:
It is not a memory leak. All devices which are on papers 2GB are actually less than that. Take memory for example. My Nexus says 32GB but I get around 27GB. Same goes on with USB flash drivers/ pen drives.
Secondly, On Windows, you want to keep as much RAM available as you can so that programs have enough room to operate. When RAM fills up, Windows is forced to start using hard drive space as virtual RAM and hard drives are much slower than physical RAM.
This is not true for Android.
Android’s operating system has its own native handler for assigning RAM to apps and making sure that all of it is being used in the most optimal way. In fact, Android purposely tries to keep apps loaded into RAM for better performance. RAM is fast, remember? On mobile devices, every bit of speed is critical for a good user experience, so keeping apps in RAM is actually a good thing. So regardless how much your RAM is shown, it wouldn't affect your user experience unless the apps installed in your phone are more than RAM can handle at a time which means either update your phone with more RAM or uninstall your apps that you do not use!
Click to expand...
Click to collapse
I must say, although most of what you say is true, having less free ram absolutely does have a negative effect on user experience. My browser tends to crash, non-intensive games face lag spikes and the general UI stutters. Is this due to Android or Asus' tweaks to Android doing a poor job at managing ram? I don't doubt that in a perfect scenario with a perfect OS, what you said holds true.
I've not had good experience with the RAM so far. My browser tabs fall out of memory more than my cheap 1GB phone. It's rather disappointing. Even just switching between 2 or 3 tabs and going back to a tab after a few seconds and it's already fallen out.
aloy99 said:
I must say, although most of what you say is true, having less free ram absolutely does have a negative effect on user experience. My browser tends to crash, non-intensive games face lag spikes and the general UI stutters. Is this due to Android or Asus' tweaks to Android doing a poor job at managing ram? I don't doubt that in a perfect scenario with a perfect OS, what you said holds true.
Click to expand...
Click to collapse
damian5000 said:
I've not had good experience with the RAM so far. My browser tabs fall out of memory more than my cheap 1GB phone. It's rather disappointing. Even just switching between 2 or 3 tabs and going back to a tab after a few seconds and it's already fallen out.
Click to expand...
Click to collapse
Yes as I mentioned before, if the apps which are preloaded are more than RAM can handle, you'd surely see a lag but killing background apps wouldn't be of much help either unless your RAM memory has too many preloaded apps already which is affecting performance of your phone. If you are rooted, apps like greenify / titanium can hibernate / freeze apps which take up memory and usually this helps in better user interface but again many other argue the opposite.
Are you using Asus Browser ? If yes, I'd suggest to use chrome as your default browser because Asus Browser is not only slow but also it drains a lot of battery. This has been proven extensively and even reviewed on different websites including gsmarena.
Basically Nexus provides pure Android interface which every manufacturer tweaks a bit according to their own needs. Usually this tweaking means more memory usage(Ram) by system UI. This is one reason that Samsung's touch wiz lags a lot on lower end phones but the same hardware runs smooth without touchwiz. The reason is Samsung has lots of tweaks in system UI .
Some browsers conserve memory by only keeping the tab used in memory and rest are loaded when you switch them. They aren't preloaded but usually this option is available in settings to preload pages which would use more memory.
I have preordered the device with 4gb so I'm afraid I can't compare your device with mine in this regard.
Kindly tell me which browsers are you using so I can comment further
Hnk1 said:
Yes as I mentioned before, if the apps which are preloaded are more than RAM can handle, you'd surely see a lag but killing background apps wouldn't be of much help either unless your RAM memory has too many preloaded apps already which is affecting performance of your phone. If you are rooted, apps like greenify / titanium can hibernate / freeze apps which take up memory and usually this helps in better user interface but again many other argue the opposite.
Are you using Asus Browser ? If yes, I'd suggest to use chrome as your default browser because Asus Browser is not only slow but also it drains a lot of battery. This has been proven extensively and even reviewed on different websites including gsmarena.
Basically Nexus provides pure Android interface which every manufacturer tweaks a bit according to their own needs. Usually this tweaking means more memory usage(Ram) by system UI. This is one reason that Samsung's touch wiz lags a lot on lower end phones but the same hardware runs smooth without touchwiz. The reason is Samsung has lots of tweaks in system UI .
Some browsers conserve memory by only keeping the tab used in memory and rest are loaded when you switch them. They aren't preloaded but usually this option is available in settings to preload pages which would use more memory.
I have preordered the device with 4gb so I'm afraid I can't compare your device with mine in this regard.
Kindly tell me which browsers are you using so I can comment further
Click to expand...
Click to collapse
Using Chrome. That's the whole point of having more memory, so they don't have to be reloaded when switching.
If I had 10 tabs open and switching back and forth over a long period of time, this is understandable. Not 2 or 3 tabs and switching between two tabs within 10 seconds. Defeats the entire purpose of having 2GB of RAM. The same thing happens switching between apps. Many of them fall out of memory within just a few seconds of switching back and forth. My 1GB phone does better than this. Something to do with whatever memory management Asus has set up.
damian5000 said:
Using Chrome. That's the whole point of having more memory, so they don't have to be reloaded when switching.
If I had 10 tabs open and switching back and forth over a long period of time, this is understandable. Not 2 or 3 tabs and switching between two tabs within 10 seconds. Defeats the entire purpose of having 2GB of RAM. The same thing happens switching between apps. Many of them fall out of memory within just a few seconds of switching back and forth. My 1GB phone does better than this. Something to do with whatever memory management Asus has set up.
Click to expand...
Click to collapse
I understand your frustrations and it could be Asus related buy I think this is how chrome operates generally so it's the browser in my opinion. I suggest you use dolphin browser (not mini version) because it usually preloads pages on my devices and it is fast as well but I usually use it for flash support only. I prefer opera classic (now opera) on my phone with chrome . On my tab, I use chrome only. It always works for me and it's Asus made. Tell me what you think of it after using it a bit . I like chrome for its sync support which is very simple and helpful.
Hnk1 said:
Yes as I mentioned before, if the apps which are preloaded are more than RAM can handle, you'd surely see a lag but killing background apps wouldn't be of much help either unless your RAM memory has too many preloaded apps already which is affecting performance of your phone. If you are rooted, apps like greenify / titanium can hibernate / freeze apps which take up memory and usually this helps in better user interface but again many other argue the opposite.
Are you using Asus Browser ? If yes, I'd suggest to use chrome as your default browser because Asus Browser is not only slow but also it drains a lot of battery. This has been proven extensively and even reviewed on different websites including gsmarena.
Basically Nexus provides pure Android interface which every manufacturer tweaks a bit according to their own needs. Usually this tweaking means more memory usage(Ram) by system UI. This is one reason that Samsung's touch wiz lags a lot on lower end phones but the same hardware runs smooth without touchwiz. The reason is Samsung has lots of tweaks in system UI .
Some browsers conserve memory by only keeping the tab used in memory and rest are loaded when you switch them. They aren't preloaded but usually this option is available in settings to preload pages which would use more memory.
I have preordered the device with 4gb so I'm afraid I can't compare your device with mine in this regard.
Kindly tell me which browsers are you using so I can comment further
Click to expand...
Click to collapse
Using Firefox, I read about the stock browser issues before getting the phone.
Clearing ram using the built in booster appears to help with performance, although it could be a placebo, and it's certainly less pronounced than on my previous phone with only 1GB of ram.
I have greenify'd/frozen a lot of apps, including some of the Asus bloatware. No comment on improved performance though.
Overall, I'm happy with the performance but low ram still seems to bother me, although such scenarios are rare.
aloy99 said:
Using Firefox, I read about the stock browser issues before getting the phone.
Clearing ram using the built in booster appears to help with performance, although it could be a placebo, and it's certainly less pronounced than on my previous phone with only 1GB of ram.
I have greenify'd/frozen a lot of apps, including some of the Asus bloatware. No comment on improved performance though.
Overall, I'm happy with the performance but low ram still seems to bother me, although such scenarios are rare.
Click to expand...
Click to collapse
I think you are more worried about RAM that is left in your memory rather than actual performance. This can happen especially if you had very high expectations from this phone. According to ASUS, this is a midrange phone on their website. Not a flagship if you are hoping!
I suggest check the performance by installing some heavy graphic games and see if it lags or not. I am sure that would be the best way to find out!
Good Luck!
The browser pages redrawing is almost certainly the lollipop memory leak. I don't have a zenfone 2 yet, but my nexus 7 had this problem up until the release of 5.1, so hopefully Asus updates to that soon.
i notice when i uninstalled clean master..my ram always on 1 gb free unlike before it stays at 650..700 free...notice my phone is even faster now
TOT_tomdora said:
The browser pages redrawing is almost certainly the lollipop memory leak. I don't have a zenfone 2 yet, but my nexus 7 had this problem up until the release of 5.1, so hopefully Asus updates to that soon.
Click to expand...
Click to collapse
Correct, thank you for finally making that point clear as it's the main reason, which clearly isn't Asus' fault.
pato2015 said:
i notice when i uninstalled clean master..my ram always on 1 gb free unlike before it stays at 650..700 free...notice my phone is even faster now
Click to expand...
Click to collapse
An ironic, yet awesome find pato!:thumbup: Be sure to relay this to the other places on the net that you're involved with that pertains to the Zenfone 2.
Sent from the Ace's MB865 using Tapatalk
My last phone, the G3, has 3 GB of RAM. The G3 runs Lollipop perfectly. The S6 edge has 3 GB of RAM and there's never any of it. I understand that there's a very aggressive low memory killer but it is ridiculous that a top of the line phone needs to reclaim my podcast app or Audible while they're playing. There should be a ton of free memory and a ton of cached apps in it but the memory is full and there is nothing cached. I've never been so frustrated with a phone. I spend a lot of time sighing at it when it does something stupid. Anyway, if anyone knows where this mysterious memory is being used, please chime in.
There are suspicions that it could be related to the touchwiz launcher, try a different launcher just for the heck of it and see how it goes.
Pp.
gunslingerfry said:
My last phone, the G3, has 3 GB of RAM. The G3 runs Lollipop perfectly. The S6 edge has 3 GB of RAM and there's never any of it. I understand that there's a very aggressive low memory killer but it is ridiculous that a top of the line phone needs to reclaim my podcast app or Audible while they're playing. There should be a ton of free memory and a ton of cached apps in it but the memory is full and there is nothing cached. I've never been so frustrated with a phone. I spend a lot of time sighing at it when it does something stupid. Anyway, if anyone knows where this mysterious memory is being used, please chime in.
Click to expand...
Click to collapse
Hi gunslingerfry,
I was just reading about this on forbes. Here is what their author says to explain the poor memory usage and how to fix it "What should happen is RAM used by apps and services is released when those apps and services are not in use. Instead it is not being released which means each new app or service has to eat into additional memory until there is no more available, at which point the slowdowns and crashes begin.
The only half solutions at present are a) to hit the ‘Close All’ button in the multitasking card menu to dismiss all apps to try and claw some memory back, or b) to reboot the device. Interestingly the latter is expected to have helped keep the issue under the radar in reviews as performance testing is always done from a fresh boot."
So it sounds like you are sort of out of luck for now, but I am sure there will be some update that fixes the issue shortly.
I'm experiencing this myself but apps that I reopen from the multitask window have to reload and I lose where I was previously.. Very annoying to say the least.
Sent from my SM-G925T using Tapatalk
PanchoPlanet said:
There are suspicions that it could be related to the touchwiz launcher, try a different launcher just for the heck of it and see how it goes.
Pp.
Click to expand...
Click to collapse
I never use the TW launcher because I don't enjoy using it. I use Action Launcher. It's very lightweight.
Goldmeyer said:
Hi gunslingerfry,
I was just reading about this on forbes. Here is what their author says to explain the poor memory usage and how to fix it "What should happen is RAM used by apps and services is released when those apps and services are not in use. Instead it is not being released which means each new app or service has to eat into additional memory until there is no more available, at which point the slowdowns and crashes begin.
The only half solutions at present are a) to hit the ‘Close All’ button in the multitasking card menu to dismiss all apps to try and claw some memory back, or b) to reboot the device. Interestingly the latter is expected to have helped keep the issue under the radar in reviews as performance testing is always done from a fresh boot."
So it sounds like you are sort of out of luck for now, but I am sure there will be some update that fixes the issue shortly.
Click to expand...
Click to collapse
Goldmeyer, this doesn't explain why it's 75% utilized on boot but with no running apps (according to the smart manager app). I've tried the build.prop tweaks posted around here and there is a significant difference. Smart manager reports there are dozens of apps being pre-loaded on boot (which is normal, this is what we want!) but with the same 75% utilized. Those tweaks tended to lag the device after a couple hours, which may be a manifestation of what the Forbes article is referring to. So I guess the thing I don't get, and maybe a better understanding of what the dha/lmk values that are being tweaked would help, is what is currently allocating all that excess memory? Is TW just allocating ridiculous amounts of memory to make sure it runs smoothly? Is Android hoarding it for its own uses? And if so, how can any device with less than 3 GB of ram possibly function on Lollipop?
On a much more technical note, I understand that running 64 bit means using a little more ram. Addresses are twice the size and integers will be twice the size but that doesn't explain 2.3 GB. It shouldn't be loading the entire system partition into ram.
Hey,
So I've been using my Nexus 5x with much pleasure but lately it's getting impossible to switch tasks fast, because they're all closing because of memory shortage. Looking in my settings it shows me that Android OS (780mb), play services (150mb) and Android system (140mb) and System UI (90mb) together take up almost 1,2GB of the 1,8gb memory. I don;t know if this is related to me being in the preview program (and having a lot of preview images updates over the last year) or it's just that the newer Android takes up more memory.
I'm pondering stepping out of the bèta program and reflashing the stock rom, but I was wondering if any of you can shed some light if this will actually help.
Thanks!
eldinnie said:
Hey,
So I've been using my Nexus 5x with much pleasure but lately it's getting impossible to switch tasks fast, because they're all closing because of memory shortage. Looking in my settings it shows me that Android OS (780mb), play services (150mb) and Android system (140mb) and System UI (90mb) together take up almost 1,2GB of the 1,8gb memory. I don;t know if this is related to me being in the preview program (and having a lot of preview images updates over the last year) or it's just that the newer Android takes up more memory.
I'm pondering stepping out of the bèta program and reflashing the stock rom, but I was wondering if any of you can shed some light if this will actually help.
Thanks!
Click to expand...
Click to collapse
It's part of the new method for ram management. It's normal. You'll notice those take up tons of ram even on a fresh install. Over time the more apps you install the more processes they auto start. This is what will cause those things to happen. For me I noticed for example first when the HDR processing of taking a picture would push hangouts out of memory even when I was actively talking voice, it just wasn't in the front running. Android does much like windows now in claiming lots of memory to better manage and allocate it as needed
Sent from my Nexus 5X using Tapatalk
On a fresh boot, my phone takes up 1.2GB of RAM, and quickly rises to ~1.4-1.5GB. It usually says there, as I don't use a lot of apps, so I'm not multitasking a lot. It's pretty odd compared to my other devices that use anywhere from 500-700MB of RAM for the OS, but it seems to do it's job just fine nonetheless.
Side note, since I don't have a lot of Apps, and I'm not concerned about RAM usage, I've disabled zram and ksm. Haven't noticed any difference, TBH.
crazyates said:
On a fresh boot, my phone takes up 1.2GB of RAM, and quickly rises to ~1.4-1.5GB. It usually says there, as I don't use a lot of apps, so I'm not multitasking a lot. It's pretty odd compared to my other devices that use anywhere from 500-700MB of RAM for the OS, but it seems to do it's job just fine nonetheless.
Side note, since I don't have a lot of Apps, and I'm not concerned about RAM usage, I've disabled zram and ksm. Haven't noticed any difference, TBH.
Click to expand...
Click to collapse
On a fresh boot it loads every apps auto start process. So that doesn't change anything at all. I am not talking about apps using ram from being run. I'm talking about all the processes they have that are triggered and restart when things occur.
Sent from my Nexus 5X using Tapatalk