Hello,
It seems that MIUI is terminating background apps too easy.
My 4 year old s7 edge keeps almost every app "alive" in task manager.
With Mi9 , the next day gives only ~6-7 of the last apps used. All the others are obviously forced to close in order (obviously) for the device to perform better/faster.
Is there any way i can adjust its memory management?
Thanks in advance.
Yes, that's true.
You have some configurations available in Setting > Battery.
By default all apps are optimized. You need to manually changed it.
4Freedom said:
Yes, that's true.
You have some configurations available in Setting > Battery.
By default all apps are optimized. You need to manually changed it.
Click to expand...
Click to collapse
Not only that, but MIUI is very aggressive when it comes to closing apps to save battery and keep performance up.
You can go to the developer settings and disable MIUI Optimizations, it's at the very bottom. With that your memory management should be as close to stock Android as possible with Xiaomi.
The only downside is you will get notifications saying that you should enable the optimizations.
Related
Please tell my which is best software that stops applications to run automatically at startup
tell me the application which works
no one is using any app. to stop unnecessary start up of tasks
try autostarts its very good
Sent from my GT-I9000 using Tapatalk
Ditto on Autostarts. Also, Autokiller Memory Optimzer works really well, it doesn't kill tasks itself, it tweaks the Android function thar does it to work better.
auto killer mem optimizer workd well for me.but now i simply don use any of those batt saving app,mem apps etc i jus kill apps in inbuilt task killer...iam using my phone to the peek cause at the end ill b getting a 2ghz dual core by selling sgs.......cant stick to old things lol........cheeerz
tarunagg said:
Please tell my which is best software that stops applications to run automatically at startup
tell me the application which works
Click to expand...
Click to collapse
... what?
Do any of you even understand how Android works?
so mind sharing ur exp wiv us on how it works???
manosv said:
try autostarts its very good
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
+1 Autostarts. It amazes me what runs on the phone after start-up, after you switch states or update apps. The perfect cure for batt draining nonsense
rocky23 said:
so mind sharing ur exp wiv us on how it works???
Click to expand...
Click to collapse
Google it. Android is Linux based. Its memory management is not the same as Windows. I'd explain further, but you're the 4,753,857,195 person to ask.
I spent 10s and googled it for you. Here's a quick link that explains it in simple terms.
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Basically having applications in RAM is a GOOD thing. Constantly killing them is likely to WORSEN PERFORMANCE AND BATTERY LIFE.
Shanakin said:
I spent 10s and googled it for you. Here's a quick link that explains it in simple terms.
http://lifehacker.com/5650894/andro...ed-what-they-do-and-why-you-shouldnt-use-them
Basically having applications in RAM is a GOOD thing. Constantly killing them is likely to WORSEN PERFORMANCE AND BATTERY LIFE.
Click to expand...
Click to collapse
That's right. On the other hand - permitting almost every app to load at startup isn't the best approach, as you will soon run out of memory - therefore using apps like autostart makes sense imho. But constantly killing everything isn't the right approach either. Android removes "old" apps automatically.
Bottom line:
- just letting those apps load at startup, which you use on regular basis, is fine
- using a "ram tweaker", auto-kill app, etc. is not
Kind regards,
ww
webwude said:
That's right. On the other hand - permitting almost every app to load at startup isn't the best approach, as you will soon run out of memory - therefore using apps like autostart makes sense imho. But constantly killing everything isn't the right approach either. Android removes "old" apps automatically.
Bottom line:
- just letting those apps load at startup, which you use on regular basis, is fine
- using a "ram tweaker", auto-kill app, etc. is not
Kind regards,
ww
Click to expand...
Click to collapse
And when you run out of memory, Android will free memory by automatically killing cached (unused) apps. Therefore, I don't see the point of stopping apps from running at start--unless they're actually doing something in the background and not letting your phone sleep.
RAM tweaks (or memory management), on the other hand, is the only thing I use. I adjust OOM settings to adjust which apps Android closes to free memory, as well as how much free RAM Android should keep open in various situations.
upichie said:
And when you run out of memory, Android will free memory by automatically killing cached (unused) apps. Therefore, I don't see the point of stopping apps from running at start--unless they're actually doing something in the background and not letting your phone sleep.
RAM tweaks (or memory management), on the other hand, is the only thing I use. I adjust OOM settings to adjust which apps Android closes to free memory, as well as how much free RAM Android should keep open in various situations.
Click to expand...
Click to collapse
Well actually I don't see the point that an app, that I hardly use once per month should be loaded everytime I start the phone or change my internet connection. Also more apps at startup increase the time when the phone is available...
But on the other hand, you are certainly right, after a while, only the latest apps are still in background / memory. What I have recognized nevertheless: if you use a lot of apps with push functionality and load on startup, the phone runs out of memory...
Kind regards,
ww
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
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'm on Honor 7 Lite (NEM-L21C432B356), I love the phone hardware itself but the stock OS (EMUI 5.0.2) is driving me crazy. Background tasks get killed really quickly and often notifications get deleted before I can even see them. I've tried factory reset and everything I've found on Google to no effect.
This isn't about the known push notifications issue. Notifications do work, but then they usually disappear almost immediately. I sometimes hear the notification tone, pick up the phone and unlock it to see a notification icon in the top bar for less than a second and then it's gone. Or if a notification comes in when I'm using the phone, I might see the notification in the list briefly and then it just vanishes.
Background tasks like Twilight or JuiceSSH with statusbar icons seem to get killed really aggressively. This seems to happen more to some apps than others, but I can't figure out any common denominator for the apps. It happens to both online and offline apps.
I've disabled everything related to Huawei's task killing/battery saving settings and added all apps to all exception lists that I've been able to find. Free memory seems to hover consistently around 500-700MB, I don't think I've ever seen free memory dip below 500MB.
It's hard to get good memory stats out of Android 7 without root, but it almost seems like the OS is pre-emptively keeping that 0.5GB of RAM free in case some foreground app wants a lot of memory, and it's willing to pre-emptively kill background tasks, even ones with status bar icons, to achieve it. I don't know if this is true, but Huawei doesn't seem to trust Android's own memory management much in general, with all their dumb "memory cleaning" and "battery optimization" stuff.
I'm at my wits' end here. I rely on seeing all notifications to keep up with reminders and other things, and I need background apps to stay there when I multitask. Custom ROMs aren't really an option, since I want everything on the phone to Just Work without any extra fiddling and hassle and I can't risk my only phone. I appreciate custom ROM developers' work though.
Thanks in advance for any useful answers.
On the P9 Lite with 2 GBs of RAM they are using more than 1.5GBs of zRAM which is crazy. I don't think that's needed at all. If your phone is rooted, you can install a Magisk module called Swap Torpedo to disable swap and maybe change some LMK values. Also you can disable the Power Genie app if you don't have root access.
erayrafet said:
If your phone is rooted, you can install a Magisk module called Swap Torpedo to disable swap and maybe change some LMK values. Also you can disable the Power Genie app if you don't have root access.
Click to expand...
Click to collapse
I'm not rooted, because unlocking the bootloader and rooting would trip SafetyNet, which I can't afford because I need some apps that depend on SafetyNet and I don't want the whole cat and mouse game with Magisk trying to keep ahead of Google on that.
Thanks a lot for the Power Genie tip (called Power Genius on my phone), I haven't seen that mentioned anywhere else and will try it out. I hadn't noticed that process at all since it's running under AndroidSystem.
Edit: unfortunately the "Disable" button is grayed out on Power Genius, so disabling it doesn't seem like an option. I can stop it manually, but I assume it'll just get autostarted again. I don't seem to have permissions to hide it from adb shell either.
Same problem here (NEM-L51C432). It aggressively kills all background applications. This prevents multitasking. It is annoying to see a lot of RAM is free and will not be used. RAM is there to take use of it and not to keep it free.
Hello,
I noticed the recent apps on my Note 9 will close them self if the running apps are over 5 overnight.
I have already changed every settings possible, disable battery optimization for apps that I don't want to close, locked them in recent apps. changed running background apps to standard limit.
yet it will still every morning I see my gmail, my skype are auto closed from recent apps.
I have already did full clean installation too with latest pie CDJ.
I don't have this problem with the S10+
check under Device care/Auto optimisation