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
I have been trying to figure out why the Note has so little of the 3 gb of ram available at any given time. After a fresh boot, I might have 1.3 - 1.5 available, but that quickly disappears.
I have frozen all unnecessary apps with Titanium Backup, yet after launching just a few apps, I'll be down to 300 mb or so. Looking at the active applications list in task manager, the apps listed are nowhere near to adding up to over a gb of ram.
Tablet seems to be performing fine, I'd just like to know where the ram is going and why. Especially when tablets with 2 gb of ram seem to have much more free at any given time.
Sent from my SM-P600 using Tapatalk
i am with you on this issue. would like to find out for my self as well! constantly having to clear ram.
youtube, gmail, and browers = 2.1 gb / 3 gb ...
what the heck?
i constantly have to go back and clear apps, this is such a let down because my htc one could load much more than this, and every1 knows, htc one is no where near the spec of note 2014..
I'm not rooted but I noticed the same thing with the ram, I thought rooting and freezing some Samsung apps, specially Knox stuff, would free up a lot of ram. I'm starting to think that it's not a big deal and Android frees up ram as needed before it starts to get laggy (of course it's not perfect). I think lag issues are somewhere else and not so much in freeing up more ram. Don't you feel anyway that your note is a lot faster after rooting and freezing those apps? As far as I know most rooted users feel that way...(?)
Sent from my SM-P600 using XDA Premium 4 mobile app
I have rooted mine about two weeks ago then froze all sort of junk listed in here and some other I identified mysefl. Now my used ram remains around 500 clean and around 700-800 when I open few apps. So guys the secret is getting a lot of useless apps frozen especially knox stuff.
greyhulk said:
I have been trying to figure out why the Note has so little of the 3 gb of ram available at any given time. After a fresh boot, I might have 1.3 - 1.5 available, but that quickly disappears.
I have frozen all unnecessary apps with Titanium Backup, yet after launching just a few apps, I'll be down to 300 mb or so. Looking at the active applications list in task manager, the apps listed are nowhere near to adding up to over a gb of ram.
Tablet seems to be performing fine, I'd just like to know where the ram is going and why. Especially when tablets with 2 gb of ram seem to have much more free at any given time.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Android is based on Linux. Android and Linux both run better when they use as much ram as possible. If you Google Android ram usage you can find a couple of interesting articles about this.
Sent from my SM-P600 using XDA Premium HD app
nrage23 said:
Android is based on Linux. Android and Linux both run better when they use as much ram as possible. If you Google Android ram usage you can find a couple of interesting articles about this.
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
Yup, stuff is kept in the RAM as much as possible to increase performance. As soon as an app requires more RAM than is available, the system moves apps from the RAM as required. Clearing the RAM only increases the time it takes to start an app next time.
I would be disappointed if its NOT beeing used...
Sent from my GT-I9300 using XDA Premium 4 mobile app
delanvital said:
Yup, stuff is kept in the RAM as much as possible to increase performance. As soon as an app requires more RAM than is available, the system moves apps from the RAM as required. Clearing the RAM only increases the time it takes to start an app next time.
Click to expand...
Click to collapse
People are used to Windows needing free ram and do realize that Linux is a completely different animal altogether.
Here is the article for those that want to understand the ram usage.
http://www.androidcentral.com/ram-what-it-how-its-used-and-why-you-shouldnt-care
http://www.linuxatemyram.com/
Okay, guys. Disclaimer: I'm an IT professional and the Mobility expert for my company. I know how the RAM is used and why. I'm just curious as to what is using it. Especially in comparison to the Nexus 10, which has 2/3 of the RAM and has approximately the same amount available at any given time.
I wasn't looking for assurance that this is how it's supposed to work. I'm curious as to what you guys think is actually filling it up. Since I have disabled most unnecessary processes and only run a few apps at any given time, I can't see why so little is free.
greyhulk said:
... I'm curious as to what you guys think is actually filling it up. Since I have disabled most unnecessary processes and only run a few apps at any given time, I can't see why so little is free.
Click to expand...
Click to collapse
The objective of good android RAM management is to keep RAM full of the the highest priority apps. This enables faster and smoother response. The apps that are in RAM on your device will be different than on someone else's device. If you are curious about how android decides what put in RAM and what to take out, do a google search on "android process lifecycle"
if you're concerned about ram usage go to dev settings and change the "Limit background processes" to something more you liking.
Hi,
I own a G3 with 2 GB of RAM, like my previous Nexus 4.
In the N4, with CM-11 or AOSP, and with the same apps that I use in the G3, the free amount of memory was more than 1 GB all the time,
but in the G3 I have 300-400 MB since a few minutes of restart it, and only 500-600 just after the restart.
Any solution to this? Really is relevant?
Thanks!
bartito said:
Hi,
I own a G3 with 2 GB of RAM, like my previous Nexus 4.
In the N4, with CM-11 or AOSP, and with the same apps that I use in the G3, the free amount of memory was more than 1 GB all the time,
but in the G3 I have 300-400 MB since a few minutes of restart it, and only 500-600 just after the restart.
Any solution to this? Really is relevant?
Thanks!
Click to expand...
Click to collapse
Having also the almost same amount of free ram and for me, it pretty much sticks there, no matter how many apps are opened, sometimes there is a launcher redraw, but except of that i haven't faced any problems at multitasking.
Gesendet von meinem LG-D855 mit Tapatalk
Tectas said:
Having also the almost same amount of free ram and for me, it pretty much sticks there, no matter how many apps are opened, sometimes there is a launcher redraw, but except of that i haven't faced any problems at multitasking.
Gesendet von meinem LG-D855 mit Tapatalk
Click to expand...
Click to collapse
yes, which most noticeable is in the redraw of the launcher, especially when closes the gallery app
bartito said:
yes, which most noticeable is in the redraw of the launcher, especially when closes the gallery app
Click to expand...
Click to collapse
This can easily be fixed though, with a third party launcher with persist in memory enabled.
Gesendet von meinem LG-D855 mit Tapatalk
Tectas said:
This can easily be fixed though, with a third party launcher with persist in memory enabled.
Gesendet von meinem LG-D855 mit Tapatalk
Click to expand...
Click to collapse
Yes, but this really don't solves the issue. Only masks
bartito said:
Yes, but this really don't solves the issue. Only masks
Click to expand...
Click to collapse
Well, i must confess it's not a real issue to me, I'm using pretty many widgets and the only one i really notice it is the clock/weather widget, everything else is almost instantly back up.
But that's just me. For sure it will be way better when the first aosp roms come up, because of their way lower memory footprint.
Gesendet von meinem LG-D855 mit Tapatalk
Wait for CM11 come to our G3
Then compare the RAM usage
Sent from my LG-D855 using XDA Free mobile app
Free ram is wasted ram.
Android, or more specifically Linux doesn't use ram in the same way as Windows would, it retains things in memory so that you can quickly resume it when you need it (therefore having less impact on the CPU and battery).
Lennyuk said:
Free ram is wasted ram.
Android, or more specifically Linux doesn't use ram in the same way as Windows would, it retains things in memory so that you can quickly resume it when you need it (therefore having less impact on the CPU and battery).
Click to expand...
Click to collapse
But on this device it is not being managed properly. At least the launcher should be kept in memory without the user having to root and do it him/herself.
These problems were fairly common when high end devices had 1gb ram but with a relatively light launcher and 2gb ram there is no excuse IMO.
Sent from my LG-D855 using XDA Premium 4 mobile app
bobsie41 said:
But on this device it is not being managed properly. At least the launcher should be kept in memory without the user having to root and do it him/herself.
These problems were fairly common when high end devices had 1gb ram but with a relatively light launcher and 2gb ram there is no excuse IMO.
Sent from my LG-D855 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have had no issues with the launcher redrawing, I did have some minor lag when I was purely stock, but removing a few LG apps that I would never use has solved this.
Lennyuk said:
Free ram is wasted ram.
Android, or more specifically Linux doesn't use ram in the same way as Windows would, it retains things in memory so that you can quickly resume it when you need it (therefore having less impact on the CPU and battery).
Click to expand...
Click to collapse
How many times did you tell this chant allready^^
And sure you're true, but the well known (from the galaxy s3 at least, which is my former device) launcher redraw is based on the available amount of ram, the thing isn't really the "free ram" here, it's more the amount of ram that can be freed up on demand to load something new into it and the launcher redraw points into the direction, that there sometimes is a shortage, because the data of the launcher has to be released, because there wouldn't be enough ram for the new application. This isn't the big issue, the launcher has no priority at this point and it takes a big amount of ram, so it's understandable that the system releases it's memory if there is more demand than currently "free". So the current "problem" is less related to "free" ram, but the lack of ram persistance of the launcher, combined with the amount of usable ram for the user, which can lead to freeing the memory of the launcher more often. This would happen to every launcher without persistance at every amount of available ram tough some times, but the higher the available ram, the less often it will happen.
That's not an issue for me, like already said, but the point behind it is understandable to me.
I've noticed in the kernel settings that 600mb of Ram is being used as ZRAM. Could this be an issue?
Sent From My LG G3 Using Tapatalk
Lennyuk said:
Free ram is wasted ram.
Android, or more specifically Linux doesn't use ram in the same way as Windows would, it retains things in memory so that you can quickly resume it when you need it (therefore having less impact on the CPU and battery).
Click to expand...
Click to collapse
I'd still prefer to have 'free or wasted' RAM, at least you know you have some RAM spare plus apps do get killed faster and some don't retain all the information in the RAM (Asphalt 8 and other big games) and restart the app (when playing games and then browsing), but 3gb is doing fine for me
Tectas said:
How many times did you tell this chant allready^^
And sure you're true, but the well known (from the galaxy s3 at least, which is my former device) launcher redraw is based on the available amount of ram, the thing isn't really the "free ram" here, it's more the amount of ram that can be freed up on demand to load something new into it and the launcher redraw points into the direction, that there sometimes is a shortage, because the data of the launcher has to be released, because there wouldn't be enough ram for the new application. This isn't the big issue, the launcher has no priority at this point and it takes a big amount of ram, so it's understandable that the system releases it's memory if there is more demand than currently "free". So the current "problem" is less related to "free" ram, but the lack of ram persistance of the launcher, combined with the amount of usable ram for the user, which can lead to freeing the memory of the launcher more often. This would happen to every launcher without persistance at every amount of available ram tough some times, but the higher the available ram, the less often it will happen.
That's not an issue for me, like already said, but the point behind it is understandable to me.
Click to expand...
Click to collapse
Launcher redraws are down to poorly coded apps, not the ram available on the device. Keeping more free ram is effectively just a dirty workaround to solving the issue that you are using a poorly coded app. Yes in this case its a stock app and there is little excuse for it, but it doesn't change the fact that it is the app at fault, not the devices ram. You shouldn't just keep throwing more ram at a device to counter the fact that people are not optimising their apps properly.
If the launcher had persistance then the device would probably be killing something else in its place, and I don't know about you but I like all my apps to work, I don't want any of them killed, therefore I would rather have a better coded app that meant that nothing needed to be killed. 2GB of ram is plenty for a device like this to cope just fine.
FYI - I removed LG's "voice" app and I have had plenty of free ram ever since.
Guys, stop blaming RAM management, it's done exactly as it should be done in Linux / Android. As Lenny said (multiple times) free RAM is wasted RAM. I'd rather see the phone use it. The problem, if there is one, is the launcher that doesn't handle "lack of free RAM" as it should. 3rd party launchers do that well (Nova for example), so LG is the one that needs to be blamed here. Having more free RAM would not solve the issue, only delay it.
On a related note, perceived lag might also comes from that: some people always close all open apps to free some RAM (for no reason), so restarting an app from scratch would indeed cause a small lag. If you keep them all in memory, perceived lag is reduced (not completely gone, but reduced a lot).
Lennyuk said:
Launcher redraws are down to poorly coded apps, not the ram available on the device. Keeping more free ram is effectively just a dirty workaround to solving the issue that you are using a poorly coded app. Yes in this case its a stock app and there is little excuse for it, but it doesn't change the fact that it is the app at fault, not the devices ram. You shouldn't just keep throwing more ram at a device to counter the fact that people are not optimising their apps properly.
If the launcher had persistance then the device would probably be killing something else in its place, and I don't know about you but I like all my apps to work, I don't want any of them killed, therefore I would rather have a better coded app that meant that nothing needed to be killed. 2GB of ram is plenty for a device like this to cope just fine.
FYI - I removed LG's "voice" app and I have had plenty of free ram ever since.
Click to expand...
Click to collapse
Protagoras said:
Guys, stop blaming RAM management, it's done exactly as it should be done in Linux / Android. As Lenny said (multiple times) free RAM is wasted RAM. I'd rather see the phone use it. The problem, if there is one, is the launcher that doesn't handle "lack of free RAM" as it should. 3rd party launchers do that well (Nova for example), so LG is the one that needs to be blamed here. Having more free RAM would not solve the issue, only delay it.
On a related note, perceived lag might also comes from that: some people always close all open apps to free some RAM (for no reason), so restarting an app from scratch would indeed cause a small lag. If you keep them all in memory, perceived lag is reduced (not completely gone, but reduced a lot).
Click to expand...
Click to collapse
I didn't really blame the ram nor the ram management, as i said, it's the launcher taking that much ram, that's why it probably get's killed earlier than others and yes, sure, that's an optimization issue. I also didn't say the system does anything wrong with it, i just tried to point out why it acts that way regarding the launcher and I also didn't say that it really is free ram I'm talking about, but available ram (with which i meant ram available for userspace apps, not ram amount not used).
Also I've never said more ram would be the fix, i said it would just happen less, because that's simply how it works and also like i said, it's not an issue for me, because i'm aware why it acts that way and even when it get's killed, it's almost instant back up, i just said, i can understand that someone could be annoyed about it.
Protagoras said:
Guys, stop blaming RAM management, it's done exactly as it should be done in Linux / Android. As Lenny said (multiple times) free RAM is wasted RAM. I'd rather see the phone use it. The problem, if there is one, is the launcher that doesn't handle "lack of free RAM" as it should. 3rd party launchers do that well (Nova for example), so LG is the one that needs to be blamed here. Having more free RAM would not solve the issue, only delay it.
On a related note, perceived lag might also comes from that: some people always close all open apps to free some RAM (for no reason), so restarting an app from scratch would indeed cause a small lag. If you keep them all in memory, perceived lag is reduced (not completely gone, but reduced a lot).
Click to expand...
Click to collapse
I had much the same Ram usage on my Nexus 5. I've been looking at an app that shows what is actually using the Ram and at any given time there's only around 1gb in actual use, the rest is cached files. All pretty normal. Incidentally, I've turned the Zram off using faux clock as you really don't need it in a 2gb device and you get a very slight performance boost and battery increase with it off.
Sent From My LG G3 Using Tapatalk
I just rooted mine and froze a load of apps I do not use and its defo speeded it up having around 600-750mb free
You could always go into developer options and turn on strict mode that will kill everything as soon as you leave it .... It has to free up ram huh ......
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
You could always go into developer options and turn on strict mode that will kill everything as soon as you leave it .... It has to free up ram huh ......
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
That would work You could also leave your phone switched off, to make sure it doesn't use any RAM at all
My free ram is about at 1.7 with 0 apps running in the task bar. Iam already using greenify, lspeed and uninstalled bunch of bloatware after rooting my device. Was wondering if we can all share how to improve battery life, tweak the stock rom further to free up more ramp?
Mine can go as high as 2.1 GB, unroot | google now launcher | limited the auto-launched apps
Running FB, Messenger, Work Email, Gmail, YahooMail, AdGuard, Fingerprint Service etc in the background.
Why would you want more free ram? In linux based os, free ram=unused uram=useless ram
Incogn said:
Why would you want more free ram? In linux based os, free ram=unused uram=useless ram
Click to expand...
Click to collapse
It will determine how optimum your device is.
More free RAM = More Apps that you can load throughout the usage period. And it will keep the OS from reloading your apps.
Joms_US said:
It will determine how optimum your device is.
More free RAM = More Apps that you can load throughout the usage period. And it will keep the OS from reloading your apps.
Click to expand...
Click to collapse
A bit of both though, clearing apps out of ram will then cause them to cold launch which is slower. I guess that's not really what you're after though. If you're after base level free ram, that's ok, as long as you're disabling things that you won't be relaunching. For what it's worth though, free ram is about the same on CM so that's just where it sits on this phone. I've personally never had anything close and redraw/reopen on this phone on stock, CM, or miui (though miui has ram management adjustments to play with). Has this been an issue for you?
benjmiester said:
A bit of both though, clearing apps out of ram will then cause them to cold launch which is slower. I guess that's not really what you're after though. If you're after base level free ram, that's ok, as long as you're disabling things that you won't be relaunching. For what it's worth though, free ram is about the same on CM so that's just where it sits on this phone. I've personally never had anything close and redraw/reopen on this phone on stock, CM, or miui (though miui has ram management adjustments to play with). Has this been an issue for you?
Click to expand...
Click to collapse
Rarely like when I loaded 10+ apps and games, couple of benchmarks then went back and forth to them.
Joms_US said:
Rarely like when I loaded 10+ apps and games, couple of benchmarks then went back and forth to them.
Click to expand...
Click to collapse
Ah, that's certainly understandable, that's quite a load!
My have 3,5-4,5 of free RAM.
marik1 said:
My have 3,5-4,5 of free RAM.
Click to expand...
Click to collapse
6GB variant? :cyclops:
Ofc, 4 gb cant have over it.
Im currently running the cm13 for the x727 4gb variant. I always have around 2.3 of free ram. Disabled all the bloatware that I saw fit and it runs smoothly. No cold launch.
Good to disable bloatwares, rarely used apps, apps causing wakelocks. Other than that, good to keep the apps in RAM. I see lots of people misusing Greenify misunderstanding this concept.
PeaKay.18 said:
Im currently running the cm13 for the x727 4gb variant. I always have around 2.3 of free ram. Disabled all the bloatware that I saw fit and it runs smoothly. No cold launch.
Click to expand...
Click to collapse
How do you use headphones.... the included ones dont work correct?
Hi guys, does your RAM usage for System is around 2.7GB - 3GB? (Under "Developer options > Running services")
Previously when on Nougat, System usage of RAM is around 1.7GB to 2GB. But ever since upgrade to OOS 5.0 and then recently to OOS 5.0.1, it goes up to 2.7GB and sometimes even 3.1GB!
I'm rooted using SuperSU, I try reflash rom and use magisk but the System still use around the same RAM.
I have a handful of apps that I frequently access usually cached in the RAM. During Nougat time whenever I open back those app it will open immediately, indicating that it's still in RAM. But now I have to wait the app to load, must be because of the System is using additional 1GB RAM that makes my apps being cleared from the cache.
Is it OOS 5.0.1 use so much RAM for System? Or there's bug on my system? Compared to Mi A1 8.0, it's System only use around 1.3GB RAM.
Is there a way to make the System use less RAM? Or any other custom ROM where it's System use less RAM?
My OP3 with OB29 is eating that much ram too but it is not problem for me because we have a loot of ram
Magisk 15.2, Google Play Services doze module, no other modifications.
Sent from my OnePlus 3 using XDA Labs
qhsusb_bulk said:
My OP3 with OB29 is eating that much ram too but it is not problem for me because we have a loot of ram
Magisk 15.2, Google Play Services doze module, no other modifications.
Sent from my OnePlus 3 using XDA Labs
Click to expand...
Click to collapse
So I guess it's normal for 1+3 Oreo to use so much RAM for System? That feels like poor optimization from Oneplus developer. Even Windows 10 system use around 2GB or less.
I have a handful of apps that I prefer to be kept in RAM cache, it's annoying to have to wait for these apps to be load again every time I access it.
xb360 said:
So I guess it's normal for 1+3 Oreo to use so much RAM for System? That feels like poor optimization from Oneplus developer. Even Windows 10 system use around 2GB or less.
I have a handful of apps that I prefer to be kept in RAM cache, it's annoying to have to wait for these apps to be load again every time I access it.
Click to expand...
Click to collapse
Thats because most of windows 10 does its stuff off machine.
Unused ram in android is completed wasted ram. The more options you add to a device the more ram usage it will take. Not to mention apps are second rate when it comes to ram usage. Its more important for it to be used on system stuff then on apps.
Also with the way doze works. Your apps will have to reload alot anyway. So its just something to get used to.
Where is the problem? We have 6gig ram...
zelendel said:
Thats because most of windows 10 does its stuff off machine.
Unused ram in android is completed wasted ram. The more options you add to a device the more ram usage it will take. Not to mention apps are second rate when it comes to ram usage. Its more important for it to be used on system stuff then on apps.
Also with the way doze works. Your apps will have to reload alot anyway. So its just something to get used to.
Click to expand...
Click to collapse
System usage on Nougat is 2GB, now jumped to 3GB in Oreo. That's a big increase, considering that other devices with Oreo can get by with around 1.5GB System usage.
Even with Doze, if the app still stay in cache it would be load immediately compared to app that have to be fetch in storage. Because of this it feels like Oreo is slower than when in Nougat.
MarcTremonti said:
Where is the problem? We have 6gig ram...
Click to expand...
Click to collapse
Honestly now it feels more like 4GB RAM device.
xb360 said:
System usage on Nougat is 2GB, now jumped to 3GB in Oreo. That's a big increase, considering that other devices with Oreo can get by with around 1.5GB System usage.
Even with Doze, if the app still stay in cache it would be load immediately compared to app that have to be fetch in storage. Because of this it feels like Oreo is slower than when in Nougat.
Honestly now it feels more like 4GB RAM device.
Click to expand...
Click to collapse
What do you expect? With each update comes more features. With more features comes higher ram usage.
Again. Unused ram is wasted on Android. It doesn't even remotely work like it does on windows.
If your apps are reloading then there is something rom with the the setup. Be it the OS or what have you.
I normally am about at 1.5gb when I'm it using my device. Mind you I don't care about keeping apps in the background. When I'm done with them I completely close them out.
xb360 said:
So I guess it's normal for 1+3 Oreo to use so much RAM for System? That feels like poor optimization from Oneplus developer. Even Windows 10 system use around 2GB or less.
I have a handful of apps that I prefer to be kept in RAM cache, it's annoying to have to wait for these apps to be load again every time I access it.
Click to expand...
Click to collapse
On my phone, Oreo uses 1.9 to 2 GB for System. Something is wrong with your setup.
zelendel said:
What do you expect? With each update comes more features. With more features comes higher ram usage.
Again. Unused ram is wasted on Android. It doesn't even remotely work like it does on windows.
If your apps are reloading then there is something rom with the the setup. Be it the OS or what have you.
I normally am about at 1.5gb when I'm it using my device. Mind you I don't care about keeping apps in the background. When I'm done with them I completely close them out.
Click to expand...
Click to collapse
But don't you think 2GB jump to 3GB is high compared to the features added in Oreo?
Supposedly my frequent accessed apps should stay cached in RAM, but because not enough free RAM it was flushed, presumedly because those apps don't have elevated priority compared to System apps. Missed those days where we have more control of the RAM by using minfree and can set ourself each app priority value.
Your 1.5GB is your System usage of RAM?
xb360 said:
But don't you think 2GB jump to 3GB is high compared to the features added in Oreo?
Supposedly my frequent accessed apps should stay cached in RAM, but because not enough free RAM it was flushed, presumedly because those apps don't have elevated priority compared to System apps. Missed those days where we have more control of the RAM by using minfree and can set ourself each app priority value.
Your 1.5GB is your System usage of RAM?
Click to expand...
Click to collapse
This is my usage:
Sent from my ONEPLUS A3003 using XDA Labs
tnsmani said:
On my phone, Oreo uses 1.9 to 2 GB for System. Something is wrong with your setup.
Click to expand...
Click to collapse
You checked from Developer options > Running services?
I also feels it's abnormal for such big jump from Nougat, but everyone seems to indicate that's how their system usage also.
Bjarne73 said:
This is my usage:
Sent from my ONEPLUS A3003 using XDA Labs
Click to expand...
Click to collapse
Thanks bro. Indeed mine is too high.
I try to format and re install OOS.
xb360 said:
You checked from Developer options > Running services?
I also feels it's abnormal for such big jump from Nougat, but everyone seems to indicate that's how their system usage also.
Click to expand...
Click to collapse
Check the attachment:
So I downloaded all the necessary files and updated to latest TWRP 3.2.1.0.
After wiping my System, Cache, Data, I thought of change the file system to f2fs for some speed improvement. And proceed to change file system for those I mention again, and forgetting that doing so will format it, and Data is linked to Internal Storage...
My internal storage is wiped clean... And I didn't make an external backup... :crying: :crying:
Expensive lesson to learn, always do an external backup even when it's tens of GBs that will take long time to finish. :crying:
This is mine
Try greenify