Hi, I have read and experienced the terrible aggressive memory management on my Honor 10 lite.
Please can someone advise on how to remove or disable (which ever is best) the standard launcher.
Also any other recommended apps, to remove from the phone for better memory management?
Tyi
Related
Hi. I tried a few of ICS roms available for i9000 out there, and all of them are pretty fast, much better than I expected. The only issue I have with any ICS rom I've recently tried is that they close apps in background quite often. For example, I might open my Opera Mobile, switch to SMS app, send a message, and then when I return Opera has to start over and load all the pages again. Does it happen to You as well? As a comparison, I tested it with a 2.3.4 MIUI rom I had as a Nandroid backup, and it's much better - most apps stay open in background for a longer time.
Is it possible that ICS has that bigger of a memory footprint over Gingerbread? What are your opinions on that? Experienced similar issues? Any workarounds?
warnec said:
Hi. I tried a few of ICS roms available for i9000 out there, and all of them are pretty fast, much better than I expected. The only issue I have with any ICS rom I've recently tried is that they close apps in background quite often. For example, I might open my Opera Mobile, switch to SMS app, send a message, and then when I return Opera has to start over and load all the pages again. Does it happen to You as well? As a comparison, I tested it with a 2.3.4 MIUI rom I had as a Nandroid backup, and it's much better - most apps stay open in background for a longer time.
Is it possible that ICS has that bigger of a memory footprint over Gingerbread? What are your opinions on that? Experienced similar issues? Any workarounds?
Click to expand...
Click to collapse
Try using less widgets. Don't use apps like Facebook. Check push notification services of some apps.
Also, i seem to remember that Opera Mobile tends to "forget" loaded pages very quickly, if you don't come back to the app quite fast...
You can also try and check under settings > developer options > see if you have checked "don't keep activities" and under "background process limit" choose "standard limit"
Since I'm only getting advice, I take it I'm the only one having this problem? Strange. The only widget I have on my desktop is the stock ICS analog clock widget, and there is no such thing as "Developer options" in my Opera Mobile.
Right now I'm using AOKP rom b27, there is an option called "Free memory - Amount of RAM the minfree taskkiller will keep". I tried to change it to max possible - 100MB, didn't change anything.
Is you are using ICS roms, you never had such issues? Which roms do you use?
PS Could a different kernel make it better?
Opera uses alot of memory and the phones memory is very limited. Doesn't matter the ROM it will often get closed when you leave it to do other things.
BTW increasing the memory the OS keeps free makes it worse, how do you think it frees memory? By closing things. You actually want to decrease the memory it keeps free to try and help with this. The downside is that the phone will probably lag more and I have found it doesn't help much.
I'll try to use the stock browser. As to that task manager setting:
The description says:"Amount of RAM the taskkiller will keep", so I have no idea if it means keeping some RAM available at all times or is it the amount of RAM that can't be cleared.
warnec said:
I'll try to use the stock browser. As to that task manager setting:
The description says:"Amount of RAM the taskkiller will keep", so I have no idea if it means keeping some RAM available at all times or is it the amount of RAM that can't be cleared.
Click to expand...
Click to collapse
It is never the amount of RAM that can not be cleared it is the amount of RAM to keep free. ie if you set 64MB Ram to be kept free Taskkiller will keep that amount of memory free by killing the oldest non active task/process
Hi Guys & Gals,
I recently installed the stagefright fix to Build LMY48I (Android 5.1.1, Baseband MDM9625_104446.01.02.101R, Kernel 3.10.40-geec2459. I did it using Nexus root toolkit v2.0.5. Now when I use battery saving apps such as Battery Doctor / Advanced Task Killer Pro / Greenify they all seem to say Excellent / no apps running good memory (despite the memory getting fuller etc). It is definitely rooted and I have reinstalled apps etc and can see them accessing Super SU. It seems to be indicating all ok. When I use clean master it frees up a lot of RAM which Advanced Task killer pro reports has occurred. Basically, battery doctor seems to be having no effect even when using super optimize (it doesn't seem to be killing anything). Am I missing something?
Regards,
Mick
mcwarre said:
. . .When I use clean master it frees up a lot of RAM which Advanced Task killer pro reports has occurred. Basically, battery doctor seems to be having no effect even when using super optimize (it doesn't seem to be killing anything). Am I missing something?
Click to expand...
Click to collapse
You are not missing something, you have to much memory management.
Lollipop has its own modern memory management and there is no need for optimizers/cleaners.
Just uninstall optimizers/cleaners.
For battery life you may use apps with a black background.
I've same probleme and i found this app.
Works with last ota update on nexus 5.
https://play.google.com/store/apps/details?id=mobi.infolife.taskmanager
Hi guys, my n910t3 is on Tekxodus 5.1.1 with root and xposed. It always seems to close the background apps. In the task manager, my ram usage rarely ever goes to 2gb/2.72gb. I have my background processes set to the standard limit. I have tried apps like memory locker and ram manger(root), both of them not working :crying:. I tried to do the build.prop fix that the s6 and note 5 use, but I could not find the ro.config.dha file anywhere. I don't think that Tekxodus is the problem because I always had these problems, and thought that installing a custom rom would fix the problem. Any help would help
michaelw911 said:
Hi guys, my n910t3 is on Tekxodus 5.1.1 with root and xposed. It always seems to close the background apps. In the task manager, my ram usage rarely ever goes to 2gb/2.72gb. I have my background processes set to the standard limit. I have tried apps like memory locker and ram manger(root), both of them not working :crying:. I tried to do the build.prop fix that the s6 and note 5 use, but I could not find the ro.config.dha file anywhere. I don't think that Tekxodus is the problem because I always had these problems, and thought that installing a custom rom would fix the problem. Any help would help
Click to expand...
Click to collapse
The build.prop edit you were talking about (ro.config.dha) has to be added as a new line to the build.prop and you can do that with any root editor. I use 3C Toolbox to add the lines and edit the existing ones.
But honestly, if the RAM management apps aren't able to change it I would try going back to stock software and seeing if the RAM issue still happens. If it does it there too you could have bad RAM blocks (more likely) or the T3 may have a totally different memory management routine that we don't know about (unlikely).
All I would like to do is to keep apps maximum is possible in ram. My goal is for my daily use of most common apps like phone, whatsapp, google messenger, gmail, contacts, calendar etc. to keep them in ram so switching between them is smooth and fast without loading on anything. My memory is always more then 50% empty and little apps like calendar or contact are getting killed with no reason. That is really going on my nerves more and more.
I am on Pure Nexus CMTE rom and I have tried playing with Kernel Auditor low memory killer and virtual memory settings. What ever I do there my ram usage is always about 1 - 1.4 GB newer more then that. How I can force system to keep apps in ram until critical point? Like in my case with more then 50% of ram still available there should not be any apps removed from memory even if is app not active for some time. Can anyone please help me with this.
Possibly you see 1.5G free now, but it may have temporarily been a lot less free when the apps were killed (usage varies over time). See attached how high chrome can jump at its peak.
Just a thought..very half baked. I'm sure someone will give suggestions for what you want.
electricpete1 said:
Possibly you see 1.5G free now, but it may have temporarily been a lot less free when the apps were killed (usage varies over time). See attached how high chrome can jump at its peak.
Just a thought..very half baked. I'm sure someone will give suggestions for what you want.
Click to expand...
Click to collapse
Yes, I know but Chrome memory usage is still nothing compare to free memory available. I did some reading and end up creating local.prop file in root/data and add some lines there. How much that will help I will find out in day or two. If anyone is interested to know what I did I can post it here after.
Just wanted to add that in Android N preview the low memory kill settings by default were very light (like lighter than kernel adiutor's "very light" preset) and it resulted in very stuttery performance. Setting them back to marshmallow stock settings made everything smoother. Looking forward to anything you may uncover on this though.
StykerB said:
Just wanted to add that in Android N preview the low memory kill settings by default were very light (like lighter than kernel adiutor's "very light" preset) and it resulted in very stuttery performance. Setting them back to marshmallow stock settings made everything smoother. Looking forward to anything you may uncover on this though.
Click to expand...
Click to collapse
Okay this is what is confusing me the most. In Kernel Auditor "very light" preset means that apps will be removed soon is possible, very light means small amount of memory to be used. Am I correct? Aggressive on other hand will give more memory for apps, more apps in memory and less removing from it.
So if is that correct then is very understandable why "N" with less then "very light" preset made bad performance and soon you give it more memory to play everything is back to normal.
However I did test on that many times but in both cases my apps are getting removed from memory with more then 50% still available memory. That's why I need somehow to stop system from emptying memory until critical point. Maybe some build.prop lines can help but I am not really expert in that area.
Emilius said:
Okay this is what is confusing me the most. In Kernel Auditor "very light" preset means that apps will be removed soon is possible, very light means small amount of memory to be used. Am I correct? Aggressive on other hand will give more memory for apps, more apps in memory and less removing from it.
So if is that correct then is very understandable why "N" with less then "very light" preset made bad performance and soon you give it more memory to play everything is back to normal.
However I did test on that many times but in both cases my apps are getting removed from memory with more then 50% still available memory. That's why I need somehow to stop system from emptying memory until critical point. Maybe some build.prop lines can help but I am not really expert in that area.
Click to expand...
Click to collapse
What is the solution for Pixel 2 rom of LG Nexus 5X? os ur build prop gonna help for me? if yes plz replay.
MHS3511 said:
What is the solution for Pixel 2 rom of LG Nexus 5X? os ur build prop gonna help for me? if yes plz replay.
Click to expand...
Click to collapse
No idea man, I don't have LG Nexus 5 anymore. Today roms have that battery optimizations build in. Go there and make the app you like to be in memory "not optimized" and in Kernel auditor or any other app flashing memory to "very light". That should help. Good lack
I had the Honor 7, it couldn't keep background apps open at all. I returned the phone quicker than you can say memory management.
How's the P9 about that? My current LG can keep background apps open for more than a day.
First to say it is depending on your usage. If you frequent a lot of apps during the day it is likely and also necessary that some will be killed on every phone! For me the P9 seems to be a little more aggressive than my old Z3 with the sony concept rom, but still ok. It uses about 2 GB of RAM on average, whereas the Z3 used 1.5 GB. I think this is due to EMUI whereas the Z3 was nearly Stock Android.
it's not ram management issue , it's a software feature . you can choose which application to keep running from battery settings , protected application
EMUI is way better than MIUI in terms of memory management. Plus, you can always lock important applications that you don't want the OS to kill.