Related
So, i've tried many different roms out there on my SGS. Never got any major issue with flashing or setting them up. Supposedly a custom rom has something improved but there was one think i kept thinking they all fail and i was wondering if anyone else feels the same.
I see random posts all the time telling how great multitasking in android is. But all these roms i keep using try their very best to close just about everything i have running. As far as i can tell, a few seconds after i switch to anything else, my first app gets closed. For example, everytime i'd leave browsing to manage what im listening to or sort out files on some file manager i'd find i needed to open my browser again instead of being there opened and waiting for me to return.
After searching for a while, the best explanation i could find out is to prevent battery drain from opened apps and to keep things smooth by having free ram, which kind of makes sense. Goes against what i read in a paper from google about android multitasking but fair enough.
Except the other day i happened to returned to a froyo stock rom (JS8 with darkcore 1.4) on my SGS and found out this does not happen. Apps stay open for the most part, except when i run something really heavy (like a game). And i dont really notice any performance decrease or extra battery drain from my usual usage.
Granted, i could be just told something along the lines "well dude, just use whatever works for you" and i totally plan on doing so, hence me experimenting, but thats not really my point. What i'm going for is, are custom roms being overzealous? because this really spoils any attempt at multitasking...
Again, this is not a rant of any sort, i was just wondering what are other people's thoughts about it
I'm suffering same problem
i want to have the browser and messenger at the same time
it close one after swetching to the other
i have 80mb free ram
I had the same problems, although lack of multitasking appeared on my stock rom, not a custom... sgs couldn't handle faceboom messager, viber, and a browser at the same time, everytime I switch from my browser to something else - it gets killed, which is frustrating
at the same time I saw how nexus s work, and how much free memory it has, compared to mine, the difference was huge!
I tried cyanogen at first, which was very close to stock nexus s, but it doesn't work good with sgs's camera and crashes once in a while
so eventually I installed JVT with voodoo and uninstalled different samsung stock apps, which gave me about 50mb of additional RAM compared to stock, and there doesn't seem to be any aggressive memory cleaners working, so I can now finally switch between all the apps I need
If you want the best roms for multitasking, go for the final builds of Froyo 2.2.1. They have plenty of free ram and are very smooth. I'd recommend Froyo ZSJPK. You can download it from XDA.
I think it depends on the ram settings in your ROM. The way android works is there are a bunch of system settings on how much ram to keep clear, and if it drops beneath certain values they start killing apps.
It's highly possible these values were tweaked in the custom roms, to improve the perceived smoothness and so on, but at the same time reducing multitasking. There's a trade off between performance and multitasking (guess why apple was so reluctant to add multitasking?)
I'm not really an expert on it, but I'm sure some quick searches around will find out where those values are and how to change them.. some rom/app probably even allows you to tweak them to your liking.
All Gingerbread roms do the same, closing apps after moving away from this, don't know why, but froyo didn't do this and ginger does.
I used to be like TS, clearing RAM because it might let the phone run smoother. After getting more exposed to Android, I realised that it could be logical to keep your apps in RAM instead of doing a cold boot again, meaning to close an app, open, close and open again, making it taxing on the phone.
So I tried to use up as much RAM as possible and it works just fine, it feels good. I believe the problem you have stated is that in your ROM, the task manager has instructions to clear the RAM once it hits a certain threshold. When it does, it starts to clear apps in different category, starting from what is known as empty apps, which are generally just apps you use and are not important to the android OS or rather independent from the OS.
In the new Samsung ROM, the threshold is set to 40MB, and it is working great for me. You can go to the android market and download "Galaxy Tuner" to set the threshold to a value you feel comfortable with. To multitask better, set the threshold as low as possible.
MaoJie said:
I used to be like TS, clearing RAM because it might let the phone run smoother. After getting more exposed to Android, I realised that it could be logical to keep your apps in RAM instead of doing a cold boot again, meaning to close an app, open, close and open again, making it taxing on the phone.
So I tried to use up as much RAM as possible and it works just fine, it feels good. I believe the problem you have stated is that in your ROM, the task manager has instructions to clear the RAM once it hits a certain threshold. When it does, it starts to clear apps in different category, starting from what is known as empty apps, which are generally just apps you use and are not important to the android OS or rather independent from the OS.
In the new Samsung ROM, the threshold is set to 40MB, and it is working great for me. You can go to the android market and download "Galaxy Tuner" to set the threshold to a value you feel comfortable with. To multitask better, set the threshold as low as possible.
Click to expand...
Click to collapse
ok i downloaded galaxy tuner but idk how to change threshold
After getting a little annoyed at the runty, poorly mapped-out, scratchy thicket of real and imagined performance tweaks, I decided to embark on a semi-long term project to determine what's real and what's "zomg mega-booster performance pills".
First project was to evaluate existing performance options on stock CM10 for actual gains using experimental design. (tl;dr: for those geeky enough to want to know, it was a main effects only d-optimal design with 32 design points for the 16 parameters listed, including several lack-of-fit and pure-error replicates. I could go on, but do you really want me to?). I ended up with a list of 16 parameters all together, from the Developer Options and Performance settings, based on their showing up in various performance tweaks discussions.
The main challenge was finding a way to measure actual performance instead of perception. I settled on several benchmarking tools: Antutu, Quadrant, SQL Benchmark, and Chainfire's benchmarking app. One of the parameters being tested ("don't keep activities") actually breaks Antutu at the graphics testing step, so I'm not reporting anything from Antutu.
All told, out of the 16 parameters tested, only 9 showed any kind of effect whatsoever, and combining best settings for all 9 simultaneously, total performance only boosted by ~20%, of which fully half was due to switching max speed from 1000 to 1100. this means the other 8 settings combined for a total boost of ~10%, meaning individually they're peanuts. The remaining 7 settings that showed no effect are only so much fluff and unlikely to do a thing for you performance-wise.
Results are summarized below for your reading/teeth-gnashing pleasure:
Max Speed (1000 versus 1100): Very clear, notable difference between the two settings on all benchmarks. This is the expected result, about 10% improvement in all benchmarks on average. Recommendation: set max speed at 1100.
Governor (convservative vs interactive vs ondemand): This only had any impact on Quadrant benchmark, no other benchmarks appeared to care. In Quadrant, conservative was the worst overall, while interactive provided an ~ 5% boost and ondemand gave ~6% boost. Recommendation: use ondemand.
Scheduler (BFQ, CFQ, noop, deadline): I don't know what schedulers do or the differences between these settings, but the only place they had any effect at all was in the SQL benchmark. There were clear differences here though: BFQ was by far the worst. CFQ and deadline were about the same with a 17% increase in SQL activity performance. noop was the best with ~ 20% increase in SQL activity performance. Recommendation: use noop. [update: some have reported stability issues with noop. If thus us the case for you, CFQ would be the next best choice]
Zram (disabled, 18% default, 26%): Zram effects only showed up in Chainfire's benchmark app, specifically for Java activities. Default 18% setting performed worst but disabled setting wasn't significantly different. 26% setting gave a 4% boost, but again, only for the java-specific benchmark. Recommmendation: use 26% setting.
16-bit transparency (off or on): Turning on the 16-bit transparency setting gave a smallish 3% boost to Chainfire's java benchmark. It did not have a measureable effect anywhere else, and I did not visually see any differences anywhere during testing. Recommendation: turn on 16-bit transparency.
Kernel same-page merge (off or on): This had a *negative* effect when turned on, resulting in a 1% performance hit on Chainfire's native benchmark. It did not have any measurable effect anywhere else. Recommendation: Keep off.
Don't keep activities (off or on): This was very problematic: it provided a distinct improvement in quadrant score (+8%) when turned on, but behaved poorly with other apps (Antutu being one). Since it didn't seem to help anywhere else outside of Quadrant and didnt' play well with others, recommendation is to keep off:
The following list are the settings that had no measureable impact anywhere. Any attempt to claim they have "zomg" status should be summarily whipped with placebo pills, or else they should let me know the exact details in which they supposedly work and I can test.
Placebo hall of shame:
Surface improvement (since it had no effect anywhere, why not just set it on banding/blur and have the best pictures?)
Background process limit
Disable HW overlays
Force GPU setting
Any of the animation scale settings (although they look snappier at lower settings, so it at least *feels* faster)
minimum speed (seriously? people think this has an effect? keep at 300 for best battery life)
Allow purging of assets
Hope you like this, y'all! Let me know if there's any other mad-scientist experiments you'd like to see.
Nicely done. How many times did you run each test? Or perhaps the results were very consistent.
FYI; regarding the governor, scheduler and the like, you may want to have a look at this thread;
http://forum.xda-developers.com/showthread.php?t=1369817
I think gives your tests / results some perspective as well.
Re: [CM10] NC Performance (and) Placebos
NCKevo said:
Nicely done. How many times did you run each test? Or perhaps the results were very consistent.
FYI; regarding the governor, scheduler and the like, you may want to have a look at this thread;
http://forum.xda-developers.com/showthread.php?t=1369817
I think gives your tests / results some perspective as well.
Click to expand...
Click to collapse
Thanks for the link. Very informative.
How familiar are you with factorial designs? All parameters were tested simultaneously in such a way that their individual effects can be partitioned out mathematically. That's what allows me to test all those settings with just 32 runs and still get solid estimates of their effects, and more importantly, the amount of variation around them (a requirement for distinguishing real effects from noise).
I suggest googling "factorial design of experiments" if you're interested.
skwalas said:
Let me know if there's any other mad-scientist experiments you'd like to see.
Click to expand...
Click to collapse
Here are some others you could try gauging:
Seeder
http://forum.xda-developers.com/showthread.php?t=1987032
V6 Supercharger
http://forum.xda-developers.com/showthread.php?t=1191747
Lagfix
http://forum.xda-developers.com/showthread.php?t=2104326
OOM/Sysctl tweaks
http://forum.xda-developers.com/showthread.php?p=34123854#post34123854
http://forum.xda-developers.com/showthread.php?p=34448792#post34448792
Re: [CM10] NC Performance (and) Placebos
Good suggestions. Before trying these third party tweaks would be good to know a few things from actual users:
Has anyone tried any combinations of these tweaks simultaneously? If yes, did they all play well together? If no, details please!
Some of these appear to have device specific settings, can anyone share settings being used on the NC?
I intend to sandbox these, as i have little desire to use then in real life just yet. Can anyone confirm that if i restore my current setup, the restore process will clean out whatever settings these tweaks out in place?
Speaking for all scientists, thank you kindly!
skwalas said:
Good suggestions. Before trying these third party tweaks would be good to know a few things from actual users:
Has anyone tried any combinations of these tweaks simultaneously? If yes, did they all play well together? If no, details please!
Some of these appear to have device specific settings, can anyone share settings being used on the NC?
I intend to sandbox these, as i have little desire to use then in real life just yet. Can anyone confirm that if i restore my current setup, the restore process will clean out whatever settings these tweaks out in place?
Speaking for all scientists, thank you kindly!
Click to expand...
Click to collapse
Have only used V6, from my experiences, restoring a Nandroid or flashing a new nightly will clean out everything it changes other than the files you store on the SDcard. This post details how I set it up http://forum.xda-developers.com/showpost.php?p=34991382&postcount=1234
I never really noticed a huge performance boost from V6, it did reduce the lag that was in the Beta's and early nightlies, mostly seemed to keep memory available and avoid the lag issued in the early builds. Have not used for the last few weeks since performance has improved on the newer builds.
Re: [CM10] NC Performance (and) Placebos
I set all recommendations. I get back to you in a couple of days. I am running 20130120 nightly
Sent from my NookColor using Tapatalk HD
Thank you!
Thank you for your measured and logical approach and recommendations! It is appreciated. I have experimented a little with the third party tweaks and haven't found any that fascinating, honestly.
When I install CM10.1, I also flash a script I made to customize to my preference and delete stuff I don't use like language modules, ringtones, quicksearch, boot animation, etc to free up some RAM. Between that and killing memory hungry apps when I'm done, my old Nook is still holding on reasonably well.
Re: [CM10] NC Performance (and) Placebos
Skwalas:
Got to tell you, your suggestions on settings are paying off. My nook is smooooooth. Is working ok there is sometime that lag liittle bit, but my p3113 also doing the same. I will stay with this 0120 nightly for a while with your settings on perfomance. .
I will report later how i am doing
Sent from my NookColor using Tapatalk HD
Re: [CM10] NC Performance (and) Placebos
performance is ok....
Sent from my NookColor using xda app-developers app
Re: [CM10] NC Performance (and) Placebos
Sometimes mook freezes and I have to leave it until it settles. The rest of the time works good
Sent from my GT-P3113 using Tapatalk HD
Re: [CM10] NC Performance (and) Placebos
Ok. Today my nook wakeup crazy. Rebooted, but it stays changing from settings , battery and some icos. It llok like it retains some touches i did to the screen and created like a loop. I have to rebooted again. Then i change the io scheduler to cfq.
Sent from my NookColor using Tapatalk HD
Re: [CM10] NC Performance (and) Placebos
Lakland said:
Ok. Today my nook wakeup crazy. Rebooted, but it stays changing from settings , battery and some icos. It llok like it retains some touches i did to the screen and created like a loop. I have to rebooted again. Then i change the io scheduler to cfq.
Sent from my NookColor using Tapatalk HD
Click to expand...
Click to collapse
Would be hard to know what is settings specific and what is hardware or OS specific. I've had no issues with the settings as described, so let us know if you are able to resolve your issues.
Re: [CM10] NC Performance (and) Placebos
skwalas said:
Would be hard to know what is settings specific and what is hardware or OS specific. I've had no issues with the settings as described, so let us know if you are able to resolve your issues.
Click to expand...
Click to collapse
I know and I am using your settings as a baseline, rigght now I change de io scheduler to cfq. Is working fine. Keep you posed and thanks!
Sent from my GT-P3113 using Tapatalk HD
Lakland said:
I know and I am using your settings as a baseline, rigght now I change de io scheduler to cfq. Is working fine. Keep you posed and thanks!
Sent from my GT-P3113 using Tapatalk HD
Click to expand...
Click to collapse
I have had erratic behavior from schedulers also, especially BFQ, NOOP is not bad, but have had better luck with CFQ.
skwalas said:
Zram (disabled, 18% default, 26%): Zram effects only showed up in Chainfire's benchmark app, specifically for Java activities. Default 18% setting performed worst but disabled setting wasn't significantly different. 26% setting gave a 4% boost, but again, only for the java-specific benchmark. Recommmendation: use 26% setting.
Click to expand...
Click to collapse
I'm surprised that zram enabled IMPROVED things. So between disabled, 18%, and 26% (no idea what default really is without digging in the code), 26% was the best option?
Interesting. I thought zram would improve multitasking (maintaining background activities) at the expense of potential slowdowns (compressed swap to ramdisk).
khaytsus said:
I'm surprised that zram enabled IMPROVED things. So between disabled, 18%, and 26% (no idea what default really is without digging in the code), 26% was the best option?
Interesting. I thought zram would improve multitasking (maintaining background activities) at the expense of potential slowdowns (compressed swap to ramdisk).
Click to expand...
Click to collapse
It might have that effect, but wasn't apparent in the benchmarks i used. It could be that a different benchmark is needed to detect it, or it could be the negative effects are too small to be measurable compared to the normal "noise" of operation.
Any ideas how we could measure this more explicitly, if there is any interest?
skwalas said:
It might have that effect, but wasn't apparent in the benchmarks i used. It could be that a different benchmark is needed to detect it, or it could be the negative effects are too small to be measurable compared to the normal "noise" of operation.
Any ideas how we could measure this more explicitly, if there is any interest?
Click to expand...
Click to collapse
Good question, I'd think it'd require some way to switch activities around and somehow measure their switch rates, but the environment would be quite difficult to keep consistent.
BTW thanks for the scientific work on this stuff, MUCH better than "OMG THIS TURNED MY TABLET INTO A UNICORN" posts we see a lot on tech forums.
skwalas said:
Any ideas how we could measure this more explicitly, if there is any interest?
Click to expand...
Click to collapse
Since it would help most when memory is low (like it ever isn't), running two memory hogs simultaneously should show an effect if there is one. A custom memory-hog app built under two different names, perhaps?
I have a shell script that creates a swapfile and enables its use that would also be well tested this way, since zram creates an in-memory swapfile. I was never able to see any tangible results except for the output of "free", so I don't use it anymore, and haven't tried it under CM10.1.
Sent from my NookColor using xda premium
Sometimes we feel that our nexus 7 us getting slower.Here are some tips to speed it up again!!
1 Free Up Some Space
Many people report that the Nexus 7 slows down as it fills up. When the 16GB Nexus 7 gets to about 3GB of storage space left, it begins to slow down.so freeing some space helps a lot.
2 Disable Currents Background Sync & Other Background Apps
Google Currents syncing is a notorious cause of lag on the Nexus 7. If your Nexus 7 is too slow or isn’t responding to touch events properly, open the Currents app, go into its Settings screen, and disable the Syncing option. This will prevent Google Currents from constantly downloading and writing data in the background.You may also want to disable background-syncing in other apps, or set them to sync infrequently — similar problems could be caused by other apps downloading and writing data in the background.
3 Delete Multiple User Accounts
If you have multiple user accounts set up on your Nexus 7, you may want to disable them. When you have multiple user accounts set up, apps on other user accounts are syncing data in the background — so if you have three user accounts, three different Gmail accounts will be syncing in the background at once. It’s no surprise that this can slow things down on the Nexus 7′s older hardware.
4 Android 4.2.2
If u ever upgraded to android 4.2.2 and felt there is some lag and found no other way 2 fix it dont hesitate to downgrade to 4.1.2 (I have done this as 4.1.2 feels a lot more faster than 4.2.2 for me.)
5-Run TRIM (LagFix or ForeverGone)
Due to a bug with the driver for the Nexus 7′s internal Samsung NAND storage, Android on the Nexus 7 was not properly issuing TRIM commands to clear unused sectors. This caused write speeds to slow down dramatically. This was fixed in Android 4.1.2, and Android should now properly be issuing TRIM commands to the internal storage.
However, this update does nothing to fix existing sectors that should have been TRIMMed in the past, but were not. To do this yourself, you can try the LagFix app from Google Play AND this will will fix the problem.Link-
https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix
6 My personal best recomendation
Use the AVG Memory & Cache Cleaner app. link- https://play.google.com/store/apps/details?id=com.avg.cleaner
After clearing the cache with this app my nexus 7 runs like new .Also try Advanced Task Killer, might help a bit.link- https://play.google.com/store/apps/details?id=com.rechild.advancedtaskkiller
Please press the thanks button :good: if this helped you!
6 - don't use too many widgets, they run in the background and can slow down your tablet too
Sent from XDA app
Task killers are pretty debatable. Android is designed in a way that means task killers can actually decrease battery life and slow the device down in some situations.
Sent from my Nexus 7 using XDA Premium HD app
The first few are common-sense solutions that demonstrably work on most devices.
The task manager and memory cache suggestions are snake oil and should be avoided. There is almost no evidence that demonstrates that any of these apps actually improve performance, and there's a lot that suggests they actually impede both performance and battery life. A task killer/memory cleaner sweeps through the system, looks for things not running in the foreground, and kills them. Sounds simple enough, right?
That is, until you realize that these programs can't prevent the apps they just killed from being triggered, and often cannot distinguish between benign apps that have legitimate background services and programs you don't want running. It then unloads them from memory (because free RAM is always good, right? Wrong), which generally results in I/O thrashing as the system tries to reload the killed applications and sees them killed again. And that ties up I/O operations, which have never been the Nexus 7's strong point.
And mind you, starting an activity is one of the most memory-intensive processes in Android, whereas keeping an app in a dormant state has significantly less impact on the system. Multitasking works better to boot, and battery life is better because the system doesn't have to waste resources regenerating resources over and over and over again.
As of this writing, the only real "performance boosting" apps I have seen are Lagfix and Greenify, because they go in at the system level (requiring root access) and actually make the right changes. Greenify temporarily "freezes" an app similar to the Disable option (or Titanium Backup) until it's in use, but unlike a task killer, it also shuts down any self-triggers an app might have to avoid thrashing. If you open the app, Greenify defrosts the app immediately for a minimal performance hit, then freezes it again after you haven't used it for a while.
Lagfix is an implementation of fstrim, which helps keep the internal memory running more smoothly. It's particularly useful on the Nexus 7 owing to the generally poor I/O performance of the internal NAND flash.
1) Install custom ROM
2) Install custom kernel
3) Overclock your CPU
4) Change CPU Governor to performance
5) Change Tegra 3 CPU Quiet Governor to Userspace
6) Setup ZRAM
7) ???
8) Profit
Username invalid said:
1) Install custom ROM
2) Install custom kernel
3) Overclock your CPU
4) Change CPU Governor to performance
5) Change Tegra 3 CPU Quiet Governor to Userspace
6) Setup ZRAM
7) ???
8) Profit
Click to expand...
Click to collapse
9) Come on XDA and complain about battery life.
Sent from my Nexus 7 using Tapatalk HD
veeman said:
9) Come on XDA and complain about battery life.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
The more energy efficient ROM, kernel and undervolting would compensate for the higher clock speed voltage.
Username invalid said:
The more energy efficient ROM, kernel and undervolting would compensate for the higher clock speed voltage.
Click to expand...
Click to collapse
And the one step that users who would do 9) always mess up will invariably muck things up/they'll have bad sync settings and moot the whole process.
veeman said:
9) Come on XDA and complain about battery life.
Click to expand...
Click to collapse
Yep. Performance governor? Derp. This whole thread is derp.
Try many different ROMs with many different kernels, find the best match, and be happy with it
On another note, keep away from Gapps. They are a real issue, take about 50 mb on my phone, an the first thing I nuked after rooting. Beleive me, my HTC Sense forgot bein laggy after that. This implies to most devices. Every ROM that I have used, has been devoid of Gapps.
Use F2FS ported to nexus 7 by legolas
Sent from my Nexus 7 using Tapatalk
Another tip: apps may open faster with row io scheduler (prioritized read speed) in custom kernel.
Sent from my iPhone using Tapatalk
Amisuta said:
Another tip: apps may open faster with row io scheduler (prioritized read speed) in custom kernel.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
which rom will you choose for better performance
omni or slimkat
nat510 said:
which rom will you choose for better performance
omni or slimkat
Click to expand...
Click to collapse
I haven't used omni or the normal slimkat before, but I've used the all-f2fs version, which works great.
nat510 said:
which rom will you choose for better performance
omni or slimkat
Click to expand...
Click to collapse
Omni worked much better for me. Also benchmarks are much much higher.
Sent from my Nexus 7 using Tapatalk
467) isn't there 45 000 000 other threads just like this?
Thank you :good:
Good tips.
I personally use ROW and performance governor with no overclocking and my tab runs super smooth.
Thanks.
Although Android 4.3 solved the issue with NAND Trimming.
T-Keith said:
Omni worked much better for me. Also benchmarks are much much higher.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Year, Omni is awesome
Guys kindly share your opinion on what's the best gaming ROM for our Xperia Z.
Sent from my C6603 using XDA-Developers mobile app
There is no such thing as "best ROM".(not to mention there is rule to not post such questions)
basically, there is too much variables, every user have different behavior, they use different apps, different setup. Their phones have different quality and performance after all those years(especially battery). They have different habits, like enabling background synchronization, different brightness, they use different features(NFC, BT, LTE)...
And all that make every phone different even if they would use the same model with the same ROM.
Not to mention that most of ROMs that you can find on XDA are nothing more than stock roms with few addons for look, few external apps putted as system ones, and few removed stock apps, and some typical copy-paste build.prop functions that are the same in most of them. Its all placebo effect in terms of performance, or its small change of 5-10% boost, and for most of time its only for few first days of usage, after that it all work the same because of different behavior that I mentioned (sorry if someone feel offended by this but this is obvious truth).
Different story is for kernel modification but I never had luck with it so I cant say anything good about it even if some changes can boost performance.
All what I could recommend, is enabling airplane mode and using some manager like L speed or Kernel Adiutor for enabling "performance" for CPU/GPU instead of "ondemand" + some app that force close background services and apps. Disabling all of that release some resources and enabling airplane mode give some battery boost because phone doesnt need to keep that features active all the time(also phone doesnt heat that much).
You cant jump over older hardware of Xperia Z and most important, you can jump over tragic optimization of most of games(especially unity engine) so there is no simple way to deal with it.
Hi everyone, this is a guide based on my personal tests, which I have the pleasure to share with the whole community, for experienced users and not. Regardless of whether you prefer to use a MIUI stock or a custom ROMs, these are a series of tricks, Tweaks, passages, let's call them what we want, to get the maximum in terms of battery life, without sacrificing performance. First of all, we talk mainly to have the better experience for MIUI and PRINCIPALLY for ROOTED users, and custom ROMs too. No rooted users cannot expect miracles because there are modifications that mainly affect the entire operating system. I also hoped to find the Holy Grail, but unfortunately it still hasn't happened.
Anyway,: If you want to use a MIUI (preferably GLOBAL, I will explain later why this is the case); the first thing I recommend in addition to a backup (just in case), it's a pretty safe Debloat using the complete Saki tool:
https://saki-eu.github.io/XiaomiADBFastbootTools/
After giving our device a nice cleanup from Bloatware (obviously you choose which ones to remove or not, personally I removed almost all of them leaving only Gallery, Phone and Messages without any problem), the best part comes, and that is to apply all the settings for a better user experience in every aspect. The MIUI is obviously not optimized as a custom ROM, so we should do it ourselves. Personally I am a root user, so first of all I flashed Evira Kernel and Magisk (with which I am wonderfully) and put modules that I personally recommend: LKT (or others similar modules), Syconfig Patcher (they are the ones that interest us), but of course the appearance rooting is optional.
But back to optimization; for each application that we will install, we will have to configure its type of activity in the background based on how much you want the app to act in the background. For example, the "MIUI Calculator" app, which I almost never use, will have set "limit app functions", otherwise applications that we will use more often will suffice "MIUI optimization", such as "Youtube", and what more important, for apps for which notification is essential (such as Whatsapp or Gmail), remove the limitations.
But it's not over. Write in the settings menu "change system settings", then a list will open with all the apps we have installed. Clicking on one of them, a menu will open, where clicking on "battery and performance", we will choose whether to put the limitations in the background or not, same speech as before, limit everything that is not necessary, inverse speech obviously goes for app important to us (gmail whats etc), which we will leave free to act in the background.
Still in the "battery and performance" menu, click on "battery optimization" and optimize everything you can, except as usual, the apps you don't want to be limited as in the previous two steps.
Now we can activate the "Battery saving" mode, which will obviously work on the whole system, except for all the apps that we have NOT optimized before. They will absolutely not be touched. (A nice break of *** optimize the MIUI , Doh!)
Remember that at the beginning of the guide I told you "better to focus on the global rather than the ROM developer?" well, using a third-party tool like Kernel auditor (personally I use EX Kernel Manager with which I am wonderfully), in the dashboard the developer rom had higher CPU peaks than the Global.Il that involved higher consumption. And it is a tool like this "Ex Kernel Manager etc" that we will now configure.
Step 1 Configure the Governor.
The mode and the speed with which the processor passes from the maximum frequency to the minimum one is regulated by the so-called * "Governor"
There are more than 100 different types of Governor for kernel, more or less different; but not all Governors are present in the Kernels. In case you are using Evira Kernel, my advice is to set the CPU to the "Alucardsched" Governor which offers an excellent compromise between performance and battery life.
EDIT: Recently tested zzmove gov with Evira Kernel: little performance is lost compared to alucardsched, but the battery benefits. Personally i have chosen profile 3 (ybatex).
Step 2 I / O scheduler
It is precisely a program in the form of an algorithm which, given a set of requests for access to a resource, establishes a temporal order for the execution of such requests, privileging those that respect certain parameters, so as to optimize the access to this resource and thus allow the completion of the desired service / instruction or process. In this case, I recommend setting it to noop or Zen, for an approach closer to the battery.
In the GPU section, if you don't use particularly heavy games, (personally I play every now and then in clash royale and I don't have any kind of lag at all) you can also set up your own governor here, setting one like Powersave, but in any case this is completely subjective .
Once everything is set up, all that remains is to talk about the last aspect,
the Doze.
Originally introduced with Android Marshmallow, it allows applications and various activities in the background to "sleep" when the device is screen off. Of course over time it has been increasingly perfect, which is why: In a Stock MIUI you can afford to download Naptime, Servicely or Greenify if you want (personally I use Nap & Serv) to enhance Doze or hibernation as in the case of Greenify (excluding as always the apps we want to be in the whitelist).
IMPORTANT: different words must be made for Custom ROMs, which being already optimized, and having a definitely more effective Doze than the basic stock, DO NOT NEED third-party apps like Naptime or Greenify. In this case, even setting everything as the guide, notifications will not arrive when the screen is off, except when you unlock the device.
so as far as custom ROMs are concerned, you just need to limit the apps as in the guide, leave in the background those you don't want to be touched, and always remove the optimization for these "important" apps, I always repeat "whatsapp gmail etc". In this way you will be able to activate energy saving quietly, the apps you prefer will not be touched, and you already have a Doze optimized like the rest of the system. The only thing that applies to Custom ROMs, is always to set the Governors as described above.
That's all at last :fingers-crossed:.
Attached here are my screenshots, with 8 hours of SOT, DIVIDED IN THREE DAYS, so sometimes the phone was idle as during the night or at work. With these configurations, in a single day, or in a day and a half, you will easily arrive even at 10 hours of SOT and maybe even beyond. I hope you fell asleep while reading, but I wanted to make a guide (even if long), to explain to those who may not be very practical, some things that can always be useful. A simple "thanks" is always welcome!
Greetings .:good:
Two more things: for more battery saving, u can disable automatic sync in settings menu (so sync when u want), and probably after some rebooting, it is possible that the governors will reset itself to the default one. So I suggest you check it out.
Really thanks for your concern about battery life stuff, and yup indeed on custom ROMs sometimes we can get up to 10hrs SoT without any mod or even a custom kernel (my experience)!
I'm looking forward to see how long the battery will last when we get Android Q update from MI..
AbboodSY said:
Really thanks for your concern about battery life stuff, and yup indeed on custom ROMs sometimes we can get up to 10hrs SoT without any mod or even a custom kernel (my experience)!
I'm looking forward to see how long the battery will last when we get Android Q update from MI..
Click to expand...
Click to collapse
Thank you very much! If I am not mistaken, beyond the various new functions, the "Extreme battery savings" will return. With an adequate optimization, as above (also to be as clear as possible with any type of user), we hope to see many beautiful new performances :fingers-crossed::fingers-crossed:
LionHeart90 said:
If I am not mistaken, beyond the various new functions, the "Extreme battery savings" will return. With an adequate optimization, as above (also to be as clear as possible with any type of user), we hope to see many beautiful new performances :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
I hope that MIUI 11 will bring some new battery saving techniques as well!
Thanks for the guide, with it you cleared some doubts that I had, I just have a question, for battery/performace Anxiety can be better than Zen? For what I read the past days is an optimized version of Maple wich gives good balance between battery and performance.
:good:
Eddywarez said:
Thanks for the guide, with it you cleared some doubts that I had, I just have a question, for battery/performace Anxiety can be better than Zen? For what I read the past days is an optimized version of Maple wich gives good balance between battery and performance.
:good:
Click to expand...
Click to collapse
Thanks bro; Zen and Anxiety are so similar as they are also different. Each I/O scheduler we choose can be the most indicated according to what we do with our device. Let me clarify: Anxiety is better in term of battery saving comparing with Maple, "It prioritizes reads over writes but tends to starve writes more".
Zen is based on noop and deadline, very stable and have a great balance, for this reason i choose it. But as mentioned there are no schedulers better than others. But better according to our needs. My advice is to try them both, and see how you are in your daily use of the device :fingers-crossed::fingers-crossed:
LionHeart90 said:
Thanks bro; Zen and Anxiety are so similar as they are also different. Each I/O scheduler we choose can be the most indicated according to what we do with our device. Let me clarify: Anxiety is better in term of battery saving comparing with Maple, "It prioritizes reads over writes but tends to starve writes more".
Zen is based on noop and deadline, very stable and have a great balance, for this reason i choose it. But as mentioned there are no schedulers better than others. But better according to our needs. My advice is to try them both, and see how you are in your daily use of the device :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Thanks for your answer and your work.
:good:
Battery life is not the only thing I look for. Stock rom batter life is good enough after debloat in many crapps using saki. Stability, functionalities, security.. overall stock rom is the way to go for me at the moment. Did you mention restricting permission on apps?
Welp, after playing Free Fire for 1:20:00 and PUBG for 4:00:00, a little Browsing, my battery usage was of 76%, I don't use LKT because last time I try it my wifi started working weird, only use Snaptime. Evira 2.2.
:good:
I would like to know what do you think about zzmove governor that was added in Evira 2.3. Thanks.
I tried to use your settings but at reboot all configuration change to interactive or schedutil for CPU, msm-adreno-tz for GPU e anxiety for Scheduler I/O. I guess there are some conflicts with LTK.... I don't kwow how you have 8 hours of screen on your device...
Eddywarez said:
Welp, after playing Free Fire for 1:20:00 and PUBG for 4:00:00, a little Browsing, my battery usage was of 76%, I don't use LKT because last time I try it my wifi started working weird, only use Snaptime. Evira 2.2.
:good:
I would like to know what do you think about zzmove governor that was added in Evira 2.3. Thanks.
Click to expand...
Click to collapse
Sure bro, i just flashed it few minutes ago. After a complete recharge cycle, ill tell u my opinion :highfive:
empedocle86 said:
I tried to use your settings but at reboot all configuration change to interactive or schedutil for CPU, msm-adreno-tz for GPU e anxiety for Scheduler I/O. I guess there are some conflicts with LTK.... I don't kwow how you have 8 hours of screen on your device...
Click to expand...
Click to collapse
Mate, if u read with more attention, i wrote about it in my second post..
Just reconfig Governor already. It could be happen, is normal
Im going to test darknesssched with zen without sysconfig patcher (Had mobile data connection issues), alucardsched give me a little lag in PUBG, when I use darknesssched that dont happen, zzmoove dont convince me, it is based in conservative and hasnt been updated since 2015, for what I know cpu governors schedutil based are more "smart".
:good:
Nice guide, bro :fingers-crossed:
@LionHeart90 thanks for your useful guide!
just a curiosity, you dont use miui? from your screenshot you have a aosp rom?
iaio72 said:
@LionHeart90 thanks for your useful guide!
just a curiosity, you dont use miui? from your screenshot you have a aosp rom?
Click to expand...
Click to collapse
Yes man, i use the MIUI 10.3.3.0 If u see, the 2 screenshots about battery life have been taken from it :cyclops:
MIUI 10.3.3.0 instead of latest 10.3.5.0?
iaio72 said:
MIUI 10.3.3.0 instead of latest 10.3.5.0?
Click to expand...
Click to collapse
Yep
Hm, i am locked...and have no kernels installed. And I'm not planing to do it.
Did restrictions and debloat and this is what I get.
Since I am on 10.3.5. my battery is weaker..
On 10.2.7 I had 2 sims with lousy signal, and I was having about 7,8 h of sot and same use.
Now before this tweaks I was hardly getting 5h in 24h
Yesterday I had weaker use then ussual but still, this isn't very good..but I think it is better.
I dont like this 10.3.5.
Spoiler
Sent from my Redmi Note 7 using Tapatalk