Speedup for Moto E 2nd Gen - ro.config.low_ram=true - E 2015 General

Just for kicks I thought I would check and see what would happen if I added ro.config.low_ram=true to my build.prop. Before doing this, I had about 250MB of free ram reported in Settings / Apps / Running. Afterwards I have about 375MB of free ram, mostly from a reduction in system memory usage. You do lose some transparency and animation effects, but the phone seems to be much faster now, especially when switching between Apps. I have an xt1527 Moto E 2nd Gen LTE running stock 5.1 with the squid kernel r6.
Instructions:
** Root is required **
Using a root file explorer edit the build.prop file located at /system
Add the line ro.config.low_ram=true
Save the change and reboot

spiked_mistborn said:
Just for kicks I thought I would check and see what would happen if I added ro.config.low_ram=true to my build.prop. Before doing this, I had about 250MB of free ram reported in Settings / Apps / Running. Afterwards I have about 375MB of free ram, mostly from a reduction in system memory usage. You do lose some transparency and animation effects, but the phone seems to be much faster now, especially when switching between Apps. I have an xt1527 Moto E 2nd Gen LTE running stock 5.1 with the squid kernel r6.
Instructions:
** Root is required **
Using a root file explorer edit the build.prop file located at /system
Add the line ro.config.low_ram=true
Save the change and reboot
Click to expand...
Click to collapse
I'm surprised you never got a reply to this post. How did this tweak work out in the long run? I'm thinking of applying it to my own Moto E 2015. Thanks!

Isn't it making lockscreen solid black and notification background black too? I'm using this on my tablet with 4.4.4 too but when I tried it on 5.0 it was pretty strange. BTW it's good to disable animations too because this tweak can make them less smooth.

Psiufoxx said:
I'm surprised you never got a reply to this post. How did this tweak work out in the long run? I'm thinking of applying it to my own Moto E 2015. Thanks!
Click to expand...
Click to collapse
Ha ha, I figured nobody cared since there were never any replies!
It seems like many of the Google apps will recognize this setting, so it can help somewhat if you are running the stock rom with all of the Google apps that come with it. You do give up some graphical effects; the biggest for me was the tab previews in Chrome. I'm running CM13 now and I haven't tried it yet with that, but I only have a few Google apps installed so I don't know if it would help much.

spiked_mistborn said:
Ha ha, I figured nobody cared since there were never any replies!
It seems like many of the Google apps will recognize this setting, so it can help somewhat if you are running the stock rom with all of the Google apps that come with it. You do give up some graphical effects; the biggest for me was the tab previews in Chrome. I'm running CM13 now and I haven't tried it yet with that, but I only have a few Google apps installed so I don't know if it would help much.
Click to expand...
Click to collapse
We care we care!
I've also gone the CM13 route with my Moto.. and I find it mostly smooth. I should probably update with a more recent nightly.
Though I was wondering about the ram tweak for my Blu Studio 7.0 LTE phone.. also running a Snapdragon 410 and only 1gb ram and on Lollipop. It stutters here and there.
Did you find/learn any other tweaks for 410s?

Hi, i'll test on my moto e 2gen (Otus) and pos the results here!

Psiufoxx said:
Did you find/learn any other tweaks for 410s?
Click to expand...
Click to collapse
Not really, other than setting some apps to not load at startup, and using Titanium backup to freeze others that I only use on occasion. This is not really SD410 specific, but more for devices with only 1GB of RAM.

exactly as spiked_mistborn says, it's the issue with 1gb of ram. SD410 with 2gb of ram (even with 1,5 gb) can really fly, my sister has phone with this configuration and it's way faster than my moto e. Just keep your ram usage low but no with "ram cleaners", just uninstall apps that have big background processes (like facebook ect). Check ram stats and you will know what to uninstall. If you're real hardcore you can try using rom without gapps, with micro-g and some alternative app store.
and one more thing
because we have 5.0-6.0 android that is less ram efficient than 4.4.4 (imo) moto decided to enable zram and it makes this phone slower, old moto g on 4.4.4 doesn't have zram enabled and it's faster.

you said add the line.. but where in prop??

Related

Improving performance by removing virtual keyboard

My biggest problem with G1 is not having enough ram. While checking what sits in my ram with MemoryUsage app I noticed virtual keyboard. Since I almost never used it, I killed it. This caused home to reload, but I believe that keyboard has not been loaded instantly.
But after some time, I could see it there again hogging my precious 9MB. Since my phone has usually only like 15MB ram free, this was quite annoying.
After doing some research and BACKUP, since I am rooted I decided to rename the application to see if it will work. The app in question is LatinIME.apk. I renamed it to LatinIME.apkBkp. While I have been there, I did the same thing with LatinImeTutorial.apk. Both files are located in /system/app.
You have to remount it writable first, search this forum for how to do it.
After renaming that file (and maybe killing the app, don't remember exactly) my phone tried to reload home. It failed to do so, force closed and then tried again, resulting in infinite loop.
I rebooted the phone and it worked well, starting normally. Now I have more ram and performance of my phone improved a bit. My free ram stays a bit higher and apps are not so often removed from it.
Overall I am happy about the result and I am looking for more unnecessary stuff to remove.
I am on CyanogenMod 4 btw., so there might be different keyboard apps on other roms.
I have not found anyone mentioning this here, only some tutorials how to change default keyboard, so hopefully someone will find this useful.
If you have any suggestion how to sqeeze even more ram from my G1, bring them on please. (I know of swap, compcache, 10mb hack and keeping low number of apps)
raqua said:
My biggest problem with G1 is not having enough ram. While checking what sits in my ram with MemoryUsage app I noticed virtual keyboard. Since I almost never used it, I killed it. This caused home to reload, but I believe that keyboard has not been loaded instantly.
But after some time, I could see it there again hogging my precious 9MB. Since my phone has usually only like 15MB ram free, this was quite annoying.
After doing some research and BACKUP, since I am rooted I decided to rename the application to see if it will work. The app in question is LatinIME.apk. I renamed it to LatinIME.apkBkp. While I have been there, I did the same thing with LatinImeTutorial.apk. Both files are located in /system/app.
You have to remount it writable first, search this forum for how to do it.
After renaming that file (and maybe killing the app, don't remember exactly) my phone tried to reload home. It failed to do so, force closed and then tried again, resulting in infinite loop.
I rebooted the phone and it worked well, starting normally. Now I have more ram and performance of my phone improved a bit. My free ram stays a bit higher and apps are not so often removed from it.
Overall I am happy about the result and I am looking for more unnecessary stuff to remove.
I am on CyanogenMod 4 btw., so there might be different keyboard apps on other roms.
I have not found anyone mentioning this here, only some tutorials how to change default keyboard, so hopefully someone will find this useful.
If you have any suggestion how to sqeeze even more ram from my G1, bring them on please. (I know of swap, compcache, 10mb hack and keeping low number of apps)
Click to expand...
Click to collapse
Unused RAM is wasted RAM. The system will kill applications when more memory is needed. Don't worry about it.
And time for you to upgrade to CM6, don't you think?
lbcoder said:
Unused RAM is wasted RAM. The system will kill applications when more memory is needed. Don't worry about it.
And time for you to upgrade to CM6, don't you think?
Click to expand...
Click to collapse
Idiocy runs rampant at Dream forums, huh? Blame the stupid Advanced Task killer dev for getting all these idiots believing killing apps actually serves a purpose...
Anyway, if the OP is concerned about memory usage and bloat, I very much doubt CM6 is a step in the right direction. Maybe the latest CM 5 is a better option.
lbcoder said:
Unused RAM is wasted RAM. The system will kill applications when more memory is needed. Don't worry about it.
And time for you to upgrade to CM6, don't you think?
Click to expand...
Click to collapse
Yep, I am very well aware how does it work, but killing the app and loading the other one uses CPU cycles and makes system slow. Especially if it happens all the time as it does on my phone. This is actually the biggest source of laggines imho.
Plus, I am pretty sure, that system apps are not unloaded (some of them at least) or they are unloaded as a last resort. Which was also the case here. I could see other apps being killed (which I did not wanted to be killed) while unused virtual keyboard was happily sitting there.
For the record, I do not use task killer of any sort, does not make significant difference for me and occupies more ram than it saves. So please save that 'idiot' for someone else.
I do not plan to switch to CM5 or CM6, because those need even more ram as CM4 does. Afaik, those roms use hw graphics support which prohibits 10mb hack. I definitely keep 10mb hack on my phone. Did a lot of good to it's speed.
Okay so what setup are you using?
I have tryed every which rom out there since i got into it and i usually only use my phone for browsing youtube music and normal phone stuff and am find these new firmwares to be getting sluggish. Basically i want a lightning quick basic build. I am interested in what exactly you are using.
elltg said:
Okay so what setup are you using?
I have tryed every which rom out there since i got into it and i usually only use my phone for browsing youtube music and normal phone stuff and am find these new firmwares to be getting sluggish. Basically i want a lightning quick basic build. I am interested in what exactly you are using.
Click to expand...
Click to collapse
I am using last version of CyanogenMod from 4 series. That is Android 1.6 based.
I have apps2sd, 10mb hack and compcache enabled. No swap. Was not working for me. I removed all the apps that stay in memory like all widgets etc. The only things that is running in my memory permanently are: SeePU (to monitor my phone), JuiceDefender (to save battery), Battery Left widget and Astrid.
I set my phone to keep Home app in memory all the time, removed all the unnecessary effects in Spare Parts and removed virtual keyboard.
With this setup, my phone performs quite ok. Not as snappy as I would want it to be, but acceptable.
Hope it helps.
I have been using Super-D 1.9.3 with 10mb hack. Removed VPN, VoiceDialer, GenieWidget and some other misc things. Latest ADW instead of Launcher.apk, MusicMod 1.5 instead of stock music, latest 1.6 Phone.apk from Wysie. I also themed my lockscreen and Powertop widget. I has been about 4 months since I flashed it and it hasn't slowed down much at all (and I rarely reboot it). Not a singel FC! Battery lasts me thru the day (I have facebook, twitter and Gmail updating themselves). All in all, its one of the best set-ups I've used. I strongly suggest trying out earlier Super-D roms if you're looking for reliable daily driver (anything before 1.11 should be quite good, 1.11 is when it all went downhill)
Good luck.
raqua said:
I am using last version of CyanogenMod from 4 series. That is Android 1.6 based.
I have apps2sd, 10mb hack and compcache enabled. No swap. Was not working for me. I removed all the apps that stay in memory like all widgets etc. The only things that is running in my memory permanently are: SeePU (to monitor my phone), JuiceDefender (to save battery), Battery Left widget and Astrid.
I set my phone to keep Home app in memory all the time, removed all the unnecessary effects in Spare Parts and removed virtual keyboard.
With this setup, my phone performs quite ok. Not as snappy as I would want it to be, but acceptable.
Hope it helps.
Click to expand...
Click to collapse
You have options.
-Remove apps2sd and use the mtd patch method. That way you cut out the slowest link on the phone: the memory card. With the MTD hack, you can get maybe 150 megs or more of internal space for apps on a donut rom.
-Use the latest version of setcpu since it doesn't stay in memory. You can try an overclock, it will help but shorten battery life some. Maybe 576 or 595 would be enough of an overclock to make it feel faster yet not drain battery like crazy.
-Keep CC on and lock home in memory
-remove the battery widget lol.
=Delete juicedefender and just use the power control widget.
-I usually remove apps that tend to launch on their own, such as the genie widget or the voice search, as well the the VK since I never use those. It's easy enough to write a script or remove them by hand from the terminal. for example, to remove the VK, open terminal and type
Code:
su
mount -o rw,remount /system
rm -f /system/app/LatinIME.apk
-reboot your phone often, and try clearing your cache using cachemate or similar

V6 SuperCharger for a laggy phone

I just want to know if anyone else is running this script. I refused to believe my Nexus S was not behaving, after all, it's a Nexus S! But, eventually even I had to get real. Truth is, lately, no matter what ROM I'm running after a few days things would slow down way too much. Lag, Launcher redraws, FCs due to lag. Things were too slow.
Anyway, I used the V6 SuperCharger script and it really has changed things. I used the MegaRAM option for 512 MB phones and I swear it has been a revelation. Even overclocking couldn't bring about this change. Currently, I'm on MIUI which most people consider to be a bit heavy and clunky. However, after supercharging with the MegaRAM option and Bulletproofing the launcher it's unstoppable! Highly recommended for those of you experiencing phone lag. Make sure to follow the Dev's instructions for using his script. All credit to user: zeppelinrox. Amazing stuff!
Which MegaRAM option did you select? I picked the second option, but I don't know which is better for Nexus S. So far I noticed browser is much much smoother now, other things has always been smooth for me, so I can't really tell the difference.
I used the 2nd MegaRAM option as well. But, I'm going to test out the first option. As I understand it, the more memory you want free in the 3rd slot the less multi tasking you can do (as this is where the secondary apps will be places)...I THINK!
As per that thread if 25 MB is good enough on a Milestone, a Nexus S should do well with 40 MB.
THIS from the thread:
zeppelinrox said:
Additional Info: You can find each app's priority and OOM.
....................... In AMM, Press Menu > Running Processes > Group by OOM grouping.
....................... Expand each group and see what apps are included and each app's priority level. (Higher numbers get killed first!)
....................... If you tap on an app, you can get additional info. Tip: Check and see what's included with android.process.acore
The default minfree values ("kill thresholds") for each OOM group are, as far as I can tell: 6, 8, 16, 20, 22 and 24 mb. (CyanogenMod 6.1.2)
This means that: when free memory lowers to 24 mb, EMPTY_APPS get killed; at 22 mb free ram, CONTENT_PROVIDER apps get killed; and so on...
Now, because the Milestone has only 256 mb of memory, I found these numbers too low, especially the 3rd one.
Basically, with those settings, you will usually be sitting with only 20 - 25 mb of ram.
Possibly less. Basically, it's the 3rd number (16) + 5. That's your free memory.
And my phone just chokes when it has that little ram available. Lag, home screen redrawing, the launcher getting killed.... ugh....
After extensive fiddling around, I've come to the conclusion that setting the third slot to about 25mb works great.
No home screen redraws while not being too aggressive on secondary/background apps while having about 30-35mb free all the time
BTW, free ram is not wasted. Android will use that memory to cache the file system and this speeds things up. See this informative post.
Click to expand...
Click to collapse
Si_NZ said:
Which MegaRAM option did you select? I picked the second option, but I don't know which is better for Nexus S. So far I noticed browser is much much smoother now, other things has always been smooth for me, so I can't really tell the difference.
Click to expand...
Click to collapse
Just tested the 1st MegaRAM option and things are quite smooth. Launcher is not as buttery as with the 2nd option but, it's still great. The browser does quite well too, pinch to zoom is smooth but, scrolling is a little stuttery on a heavy page like Engadget's.
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
never heard of this till this morning, thanks for bringing it up
trying it out now
brainmaster said:
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
Click to expand...
Click to collapse
I love it when a tweaker tells tweakers not to tweak.
Really!
zeppelinrox said:
I love it when a tweaker tells tweakers not to tweak.
Really!
Click to expand...
Click to collapse
you should know that two scripts running can cause issues......
zeppelinrox said:
I love it when a tweaker tells tweakers not to tweak.
Really!
Click to expand...
Click to collapse
I didn't said anything against your script, just told the users to not use it on my custom ROM. A think that as maker of your script you should know - two RAM scripts on same ROM are doing only damage.
They don't stay running.
They execute and end.
Whichever one runs last is the one that sticks.
Many people were using juwe's script with the V6 script and things ran fine so it's not a big deal.
Of course, if somebody wanted to, they can delete the minfrees in any of their custom roms and plug them into supercharger...
Why do you guys like scaring the crap out of people for nothing? lol
brainmaster said:
Just wanted to tell - if you are on my MIUI ROM, don't use it because I have my own RAM Optimization script integrated.
Click to expand...
Click to collapse
Great to hear from you. Haha. Just about to ask you
does it work well with cm7?
mohsin125 said:
does it work well with cm7?
Click to expand...
Click to collapse
I'm running it on cm7, and my phone seemed to be a bit snappier
time will tell though
Can someone put this in a stock rom? Sounds too complicated
. Interested in more speed but stock on matrix rom is pretty fast
rican408 said:
Can someone put this in a stock rom? Sounds too complicated
. Interested in more speed but stock on matrix rom is pretty fast
Click to expand...
Click to collapse
use this guide, and it will be easier than you could imagine
http://forum.xda-developers.com/showthread.php?t=1126940
I tried this and for some reason it derped my sim card, said it was locked (couldnt unlock it when booted as it just went passed the pin screen and onto home screen) and the home button wouldnt work. Anyone got any ideas?
Haizum74 said:
I tried this and for some reason it derped my sim card, said it was locked (couldnt unlock it when booted as it just went passed the pin screen and onto home screen) and the home button wouldnt work. Anyone got any ideas?
Click to expand...
Click to collapse
I've seen this problem with the SIM/PIN lock on other ROMs. You might want to try disabling and re-enabling the SIM/PIN lock from settings. It should immediately ask for the PIN and reenable you Home key. What settings did you apply? Maybe they killed off your system guard.
Sent from my Google Nexus S using XDA App
Just an update on my settings. The MegaRAM seem to really speed everything up but, I find that they weren't being nice to my Whatsapp (I was missing messages now and then) I think Whatsapp would receive the message but get immediately killed before it could broadcast the notification. Once it even seemed to exit in app for no reason at all. So I switched to Balanced Settings 3 and so far Whatsapp as well as the launcher and phone in general has been very responsive.
Sent from my Google Nexus S using XDA App
deejaylobo said:
I've seen this problem with the SIM/PIN lock on other ROMs. You might want to try disabling and re-enabling the SIM/PIN lock from settings. It should immediately ask for the PIN and reenable you Home key. What settings did you apply? Maybe they killed off your system guard.
Sent from my Google Nexus S using XDA App
Click to expand...
Click to collapse
I went for Megaram option 1 (I think). I disabled password and it then worked but by this time I had uninstalled the script. Any particular option you suggest? Cheers for the reply too.
It depends on your usage. I would suggest starting out with Balanced settings 3 and moving up or down the menu depending on whether you want more(down) or less speed(up). I've found that the trade off is speed vs multitasking. Though, I think zeppelinrox could confirm whether I'm right.

[Q] [Help] Poor Multi-Tasking experience

Hello everyone.
My issue is rather simple.
I used to have a Galaxy S3 that had a really poor multi-tasking experience with its very limited 1Gb of RAM.
So I bought the Note 3 that was bound to provide me with enough RAM for a better multitasking experience.
So far it was OK and way better than S3 capability but then KitKat came along and this is where my nightmare began.
Simply put, I cannot take benefit of the 3Gb of RAM I have on my device.
My Galaxy Note 3 is the international version bought in France with a Snapdragon S800 and 3Gb of RAM.
During my every day usage, I ofently switch between a certain sets of applications so to me, it is very important that these applications are not killed.
My original settings :
OOM is untouched, though I tried to set it to light with System Tuner but it did not help.
I have a few services that are launched when the device boot : Network Speed to measure bandwith in real time, OS Monitor to display CPU and RAM usage in real time as well and finally System Tuner.
Under develpoment options in the Settings, the limit of apps in background is set to standard (by default)
This is a sequence of test runs I made to show what is going on and why I deem my multitasking experience poor.
In the aim to offer accurate data, this is the list of apps I am using a lot :
app 1 = World War - a 2D non dynamic video game ;
app 2 = iMobster - same as above ;
app 3 = TweetCaster - a twitter client
app 4 = EvolveSMS - a SMS client. Can take a lot of RAM if many SMS are loaded (over thousands of SMS = 100Mb of RAM)
app 5 = Google Chrome - the web browser (not beta) with one tab loaded, two tabs saved but unloaded
Here we go.
Reboot phone -> 1.5Gb of free RAM (1.9Gb at the beginning then 1.5Gb in average after waiting for the aforementioned on-boot apps to be launched)
Launch app 1 -> 1.4Gb of free RAM
Launch app 2 -> 1.3Gb of free RAM
Launch app 3 -> 1.0Gb of free RAM
Launch app 4 -> 800Mb of free RAM
Launch app 5 -> 600Mb of free RAM
Upon each launch I waited for the app to be completely loaded (no splashscreen or loading screen). Then I check with both OS Monitor and System Tuner's widgets to check up the free RAM (sometimes their data differ, but not a lot ~100/200mb).
Repeating this particular sequence bears the same results : when launching app 5 (Google Chrome), app 1 and 3 are closed.
Some time only one of them. But most of the time two apps are closed.
Futhermore, I notice I can't not get less than 500Mb of free RAM. Unless I use Google Chrome to load heavy websites, there is no way than by launching more apps I will get under this limit.
Simply put, I cannot have more than 4 to 5 apps running in background.
I tried different ROMS :
- 2 based on Samsung KitKat ROMs : Jackyaway and S5 port V6. I have the same issue.
- CM 11. : too unstable at the time but perhaps better because the OS takes less RAM than Samsung.
So here I am.
When I was on Android 4.3, it was nice, Moving to 4.x is a disaster.
What can I do ? How is your experience ? How many apps do you manage to keep in the background ?
You are aware that the default setting for 'keep in background' equals 4?
Sent from my SM-N9005 using Tapatalk 2
ShadowLea said:
You are aware that the default setting for 'keep in background' equals 4?
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
Then how can I change it ???
This is really common and isn't an issue. Android will cache a lot of resources in RAM. When that RAM space is needed, the cache is freed. Do not worry.
Colton127 said:
This is really common and isn't an issue. Android will cache a lot of resources in RAM. When that RAM space is needed, the cache is freed. Do not worry.
Click to expand...
Click to collapse
Sorry but no.
How come ..
In Android 4.3 I had better multi-tasking experience (more apps in background) while having a smooth system ...
In Android 4.4,x I have an horrible multi-tasking experience (less apps in background).
I mean I have been doing more tests and it's driving me CRAZY ! After just rebooting my phone, I have about 1300Mb of FREE RAM and then after starting my 4 usual applications, it still have 1Gb of FREE RAM, why, please tell me why would Android feel the need to kill one of these apps after I launched a 5th one ?
This is getting ridiculous ! In what world could Android based on Linux kernel simply decide to kill my apps when it has 1Gb of FREE RAM !
When I was on 4.3 I could have ;
- my 2 2D video games
- my twitter client
- my SMS application
- chrome with 3 tabs opened
- play store opened,
- galerie displaying a picture
etc etc.. all stayed in background. They just got killed whenever I started a heavy application such as a 3D video game and in that case it's completely normal.
Heck I even recalled playing to Asphalt 7 then having a phone call while replying to an SMS (or checking my tweets) all at the same time.
Guess what I can do, now in KitKat ?
Oh god I hate my self for moving to kitkat. Makes me want to throw my phone away.
Search for zeppelinrox's V6 supercharger, I recall it has a feature to allow more apps to run in the background.
I am yet to do this myself, noticed the poor multitasking also.
Someguyfromhell said:
Search for zeppelinrox's V6 supercharger, I recall it has a feature to allow more apps to run in the background.
I am yet to do this myself, noticed the poor multitasking also.
Click to expand...
Click to collapse
That could be a solution. I used in on my Galaxy S3 but it did little help since the phone was lame at the beginning.
I never believed I would use it again on the phone I deemed good for multitasking.
But I am glad to hear that I am not the only one thinking the same thing.
I will try the fix and post here my findings. Should you try the same thing, do not hesitate to share your experience here.
Bump
Quite some time have passed since my last post here ... but my problem remains still.
I've juste moved to Cynogen Mode 11 as of last Snapshot (stable) version.
Overall, the system is stable. Much faster, way smoother. I won't miss TouchWiz I think.
RAM usage is lower : now on boot with the same services I like to have, it sill have over 1.6Gb of free RAM.
That's quite a lote I would like to use, but still can't.
But I must be fair, my multitasking experience is slightly better. First because I can finally have other options to switch between apps other than by long-pressing the home button.
But also because it seems I can finally have a few more apps staying in the background.
When looking for solutions to my problem, I ran across this : RAM and multitasking...so bad.
I said : "finally, someone understanding me".
I read all replies, and this is what seems to come out : KitKat seems to have a built-in feature that auto-kills app whenever a limit of active apps is reached.
This limit is around 10 and 20. I don't know where this limit is set, how it is defined, where I can find, how I can change, and why it exists.
I believe V6 Supercharger did change that limit on Jelly Bean and ICS. I thought this limit disappeared in 4.3.... did it come back in 4.4 ?
Does it work on KitKat ?
Well, I hope someone here can help me. Thanks !
Bump to this. I have a Xperia Z3 Compact and experience the same problem... I never have this problem before with other devices in 4.3.. The multitask since Kitkat is just horrible.

[q]very high system ram usage[lollipop][5.0][lrx21t]

Hi ,new user on xda
i have a nexus 4
running completely stock 5.0 LRX21T NO ROOT
i have noticed very high ram usage on 5.0 as compared to 4.4 after the update
normally had ~1gb Ram free but now only ~500mb remains free
on ruuning applications screen,it shows
system-~750mb
apps-~600 mb
why is system using so much Ram,wasnt the case in 4.4...
is it bcoz of ART ?
is this normal?
same problem..on my nexus 4 after 5.0 update
After reboot, system ram usage stays low (read 100 to 150mb) for 1 to 2 days.. But suddenly shoots up to more than 1gb.
Does anyone know the root cause.
I think i found the root cause to this..
In Settings -> Sound & Notifications
change the setting When Device is locked -- Don't show notifications at all
By doing this, the system ram usage never shot up above 200mb for the past 2 days for me.
previously I had to reboot my device every night before going to bed.
I will further observe if this is the root cause and revert back.
apv25 said:
Hi ,new user on xda
i have a nexus 4
running completely stock 5.0 LRX21T NO ROOT
i have noticed very high ram usage on 5.0 as compared to 4.4 after the update
normally had ~1gb Ram free but now only ~500mb remains free
on ruuning applications screen,it shows
system-~750mb
apps-~600 mb
why is system using so much Ram,wasnt the case in 4.4...
is it bcoz of ART ?
is this normal?
Click to expand...
Click to collapse
art by default use more ram than dalvic to run applications so this might be normal for you. on top of that there is some memory leak found in android l.
the important thing to now is how android manage ram. when you open an application it is loaded in the ram. whether you close the application or let it run on the backround android does not clean the memory occupied by the application until it has to. android LMK (low memory killer) clean the ram memory occupied by a program denpending on the priority id of the app. for example system apps (system ui) has lowest priority so LMK never kills that app. other apps have different priority. an application that runs in the backround (facebook messenger or whatsup) have lower priority than a game so when android need more ram it will empty the ram occupied by the game first and if there is more need for ram it will later empty the ram occupied by the backround app.
Long story short android will handle the ram as it sees fit. unlike windows, android will keep the memory full so apps can be launched faster. the problem is that android l has memory leak so you need to reboot your device every few days if you feel it starts to have some lags.
apps like task killers do more harm than good in terms of performance or lags. also facebook and facebook messenger are very badly written apps so they will consume a lot of memory. also antiviruses (especially cm security) are responsible for lags and memory leaks.
hope i helped you somehow understand android and find your problem (if there is one)
P.S. sorry for the long post!!
ttheodorou said:
art by default use more ram than dalvic to run applications so this might be normal for you. on top of that there is some memory leak found in android l.
the important thing to now is how android manage ram. when you open an application it is loaded in the ram. whether you close the application or let it run on the backround android does not clean the memory occupied by the application until it has to. android LMK (low memory killer) clean the ram memory occupied by a program denpending on the priority id of the app. for example system apps (system ui) has lowest priority so LMK never kills that app. other apps have different priority. an application that runs in the backround (facebook messenger or whatsup) have lower priority than a game so when android need more ram it will empty the ram occupied by the game first and if there is more need for ram it will later empty the ram occupied by the backround app.
Long story short android will handle the ram as it sees fit. unlike windows, android will keep the memory full so apps can be launched faster. the problem is that android l has memory leak so you need to reboot your device every few days if you feel it starts to have some lags.
apps like task killers do more harm than good in terms of performance or lags. also facebook and facebook messenger are very badly written apps so they will consume a lot of memory. also antiviruses (especially cm security) are responsible for lags and memory leaks.
hope i helped you somehow understand android and find your problem (if there is one)
P.S. sorry for the long post!!
Click to expand...
Click to collapse
thanks
ttheodorou said:
art by default use more ram than dalvic to run applications so this might be normal for you. on top of that there is some memory leak found in android l.
the important thing to now is how android manage ram. when you open an application it is loaded in the ram. whether you close the application or let it run on the backround android does not clean the memory occupied by the application until it has to. android LMK (low memory killer) clean the ram memory occupied by a program denpending on the priority id of the app. for example system apps (system ui) has lowest priority so LMK never kills that app. other apps have different priority. an application that runs in the backround (facebook messenger or whatsup) have lower priority than a game so when android need more ram it will empty the ram occupied by the game first and if there is more need for ram it will later empty the ram occupied by the backround app.
Long story short android will handle the ram as it sees fit. unlike windows, android will keep the memory full so apps can be launched faster. the problem is that android l has memory leak so you need to reboot your device every few days if you feel it starts to have some lags.
apps like task killers do more harm than good in terms of performance or lags. also facebook and facebook messenger are very badly written apps so they will consume a lot of memory. also antiviruses (especially cm security) are responsible for lags and memory leaks.
hope i helped you somehow understand android and find your problem (if there is one)
P.S. sorry for the long post!!
Click to expand...
Click to collapse
This is why Google needs to give us an extended power menu. I understand they say it shouldn't be necessary under normal circumstances, but I consider every single nexus update to be a beta, of sorts...and we all know how buggy betas can be from time to time. They're very unpredictable, and you never know if you'll need to reboot. Saying it's simply never necessary for something that is basically beta is just plain egotistical as hell.
hp420 said:
This is why Google needs to give us an extended power menu. I understand they say it shouldn't be necessary under normal circumstances, but I consider every single nexus update to be a beta, of sorts...and we all know how buggy betas can be from time to time. They're very unpredictable, and you never know if you'll need to reboot. Saying it's simply never necessary for something that is basically beta is just plain egotistical as hell.
Click to expand...
Click to collapse
my philosophy is that when you buy a nexus device, because it is a very simple os without the good stuff that lg/sammy or any other oem android manufacturer put on their phone(i am refereeing to the shortcuts power menu or toggles and other things that make your life easier and not the whole change of the os like touchwizz) you have to root so you can do your own small changes as you see fit (and fortunately for me i live in europe where there is a European law that states that you have the right to do whatever you want to the software of your device an be eligible to waranty).
So if you root your device you can do everything you want. for me on kit kat it was xposed and gravity box. on android l, yesterday i installed simple aosp.
In my opinion pure android with a twist is the way to go! and of course a custom kernel for better battery life and ad free for no ads!!
P.S. a quote by a fellow nexus user: A nexus without root is like an angel without wings
ttheodorou said:
my philosophy is that when you buy a nexus device, because it is a very simple os without the good stuff that lg/sammy or any other oem android manufacturer put on their phone(i am refereeing to the shortcuts power menu or toggles and other things that make your life easier and not the whole change of the os like touchwizz) you have to root so you can do your own small changes as you see fit (and fortunately for me i live in europe where there is a European law that states that you have the right to do whatever you want to the software of your device an be eligible to waranty).
So if you root your device you can do everything you want. for me on kit kat it was xposed and gravity box. on android l, yesterday i installed simple aosp.
In my opinion pure android with a twist is the way to go! and of course a custom kernel for better battery life and ad free for no ads!!
P.S. a quote by a fellow nexus user: A nexus without root is like an angel without wings
Click to expand...
Click to collapse
I do have root access and a custom kernel, but I prefer the nexus factory images, and the only system change I want is an extended power menu. Have you ever actually looked for an odexed version of an extended power menu flashable zip??? Don't waste your time. The last one I saw myself was for Nexus S. It can be done, but it never IS done. Stuff like that I could almost definitely do myself, but I just don't have the time anymore to sit down and read how to do it, actually do it, test it, etc. I haven't done any android dev at all in a few years and I'm rusty as hell, not to mention how much things have changed for android in the last two years.

Is there any way to improve ram management on miui v7?

So yeah, I've been using nexus 5 prior I got this phone. It had 2 gigs of ram too. When I was getting RN2 I thought I won't face any ram related problems, but I was wrong. It feels like I have 1 gig of ram judging on phone's ability to keep apps in memory. Chrome is capable of keeping only 1 tab in memory, and not for a long time. I'm sick of seeing everything being reloaded every time I go back to it. Any thoughts on this?
PS
No need to tell me about 'lock' feature in recents, it's just useless.
I set up my own battery profile using the security app. Security - Battery - Battery Profiles. In here I changed the Clean Memory to never.
Sent from my Redmi Note 2 using Tapatalk
I use the default profile, and it already has 'never' option picked. And as far as I can judge, this features is meant to be an automatic task killer sorta. The device's problem is in poor ram management, 2 gigs of ram is simply not enough for it, which is kinda 'wtf', considering my nexus experience.
Try freeze build in apps, root first, then use titanium backup or link2sd
If you're using MIUI, there's nothing you can do to lower RAM used by the system and get more RAM available for your apps. I personally clear my apps before use, but the apps I got start fast and are mainly utilities. The only app I lock is School Assistant because it warns me of my classes and exams at University.
sxeMonster said:
So yeah, I've been using nexus 5 prior I got this phone. It had 2 gigs of ram too. When I was getting RN2 I thought I won't face any ram related problems, but I was wrong. It feels like I have 1 gig of ram judging on phone's ability to keep apps in memory. Chrome is capable of keeping only 1 tab in memory, and not for a long time. I'm sick of seeing everything being reloaded every time I go back to it. Any thoughts on this?
PS
No need to tell me about 'lock' feature in recents, it's just useless.
Click to expand...
Click to collapse
Hi.
Im on Xiaomi.eu 5.10.16 with Google Now launcher. No problem having a lot of tabs open in Chrome.
Its smooth and stable. No ram issues. No better or worse than my Nexus 5.
My experience is that using task killers etc only making things worse. We better leave ram management to the os alone
Thanks
Knievel.
Well, I don't use any task killer or something. I just experience ram shortage symptoms.
Kinda late, but eh...
It's not really RAM shortage, but MIUI's asinine memory "optimization". It basically kicks any apps (even active ones!) from RAM after a while. I've been foaming at the mouth blaming my media player for simply disappearing mid-song randomly without any error messages, when I stumbled over the "memory optimization" setting in developer options. Looking around on the net brought me here. Disabled that sucker, rebooted, no disappearing apps anymore. The phone feels as smooth as it did before, so the usual low memory killer settings work. Tweaked them a bit using kernel adiutor and I'm more than happy. You could also try this in addition, but I wasn't able to get it to run smoothly - apparently an exception. Idle RAM usage fell significantly, though.
Crim Soukyuu said:
Kinda late, but eh...
It's not really RAM shortage, but MIUI's asinine memory "optimization". It basically kicks any apps (even active ones!) from RAM after a while. I've been foaming at the mouth blaming my media player for simply disappearing mid-song randomly without any error messages, when I stumbled over the "memory optimization" setting in developer options. Looking around on the net brought me here. Disabled that sucker, rebooted, no disappearing apps anymore. The phone feels as smooth as it did before, so the usual low memory killer settings work. Tweaked them a bit using kernel adiutor and I'm more than happy. You could also try this in addition, but I wasn't able to get it to run smoothly - apparently an exception. Idle RAM usage fell significantly, though.
Click to expand...
Click to collapse
You're talking about 1 or 2 ?
One, memory optimization. Disabling two, MIUI optimization, is a bit overkill, since it also removes the recent tasks management.
Crim Soukyuu said:
... since it also removes the recent tasks management.
Click to expand...
Click to collapse
There are a thousand and one apps that do that.
@Crim Soukyuu Task manager doesn't dissappear - it can be re-assigned to any button by going into Settings - Additional Settings - Buttons
DarthJabba9 said:
There are a thousand and one apps that do that.
Click to expand...
Click to collapse
But why would you want to use them instead of the built-in one? If you disable MIUI optimizations, you might as well use an un-mutilated AOSP/CM ROM.
jajk said:
@Crim Soukyuu Task manager doesn't dissappear - it can be re-assigned to any button by going into Settings - Additional Settings - Buttons
Click to expand...
Click to collapse
I based my statement on what DarthJabba9 said in the Skinny Pro thread:
DarthJabba9 said:
Disable "Turn on MIUI optimization" in the developer options (if you have enabled developer options). After this, you will have to close down recent apps manually (I use "RecentTask" from the Play Store).
Click to expand...
Click to collapse
In any case, to get rid off the symptoms @sxeMonster was having, it's enough to disable "Memory optimization" in the developer options.
maow425 said:
I set up my own battery profile using the security app. Security - Battery - Battery Profiles. In here I changed the Clean Memory to never.
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
I can confirm the clean memory setting is a major reason for poor battery life,
I've set it to never and my battery life is much better.
Regards
---------- Post added at 05:02 PM ---------- Previous post was at 04:57 PM ----------
Crim Soukyuu said:
One, memory optimization. Disabling two, MIUI optimization, is a bit overkill, since it also removes the recent tasks management.
Click to expand...
Click to collapse
That's correct, no need to disable MIUI optimisation.
Memory optimisation option is basically Zram,
I've got it disabled, too.
Haven't had any ram issues and it can still keep a dozen or so apps on the background before android starts killing them.
Regards
Crim Soukyuu said:
But why would you want to use them instead of the built-in one? If you disable MIUI optimizations, you might as well use an un-mutilated AOSP/CM ROM.
Click to expand...
Click to collapse
Non sequitur. MIUI optimizations are not the only (or even the main) difference between MIUI ROMS and AOSP/CM ROMs.
Sequitur or non sequitur, you haven't answered my question - why would I want to disable MIUI optimization instead of only memory optimization?
Crim Soukyuu said:
Sequitur or non sequitur, you haven't answered my question - why would I want to disable MIUI optimization instead of only memory optimization?
Click to expand...
Click to collapse
Your question was "But why would you want to use them instead of the built-in one?" The answer is "This is a very small price to pay for removing MIUI optimization". Disabling memory optimisation may do the deal for you - but it did not solve all my problems.
I will refer you to the following which is in response to issues that have been raised here.
http://forum.xda-developers.com/redmi-note-2/development/b-skinny-pro-t3347906/page9#post66369078
I disabled a few things given by @jajk , I think the most important one for multi tasking is the battery saver, it closes apps and restricts backgroud activity.
Not only that but too much crap is held in memory by miui.
Get disable service and disable:
InCallUI - CallRecordingRemoteService
Security - SecurityCenterAnalyticsService + SecurityCenterService + PowerSaveService --- it still works just not held in memory
Settings - MiuiWifiService + ObserverService ---- Wifi still works
GooglePlayServices - I disabled a few things I don't need and everything works for me except Gmail account sms verification, I had to put in the code manually.
Default SMS app stays in memory for some reason, I disabled it and using google messenger, just gotta disable wearable service
If disabled it breaks SMS, just disable SmsReportService, SMS works that way. Also in settings disable auto download MMS.
I'm getting 600-700 free ram and apps stay in cache much longer. Outside of settings it reaches 800 Free memory + all apps still in cache
Screenshots: https://www.dropbox.com/sh/a7lq8k5jzo2htcc/AAByd8UBFR4AKAiS9Rcg-dWTa?dl=0
I would prefer better memory management than High Free Memory, because Linux is good already with Memory Management.
Sent from my Redmi Note 2 using XDA-Developers mobile app

Resources