Related
This is a general discussion thread. You can share your Current setup of Robin, it would be helpful for us to know which ROM can be used as Our daily driver.
_____________________________________________________________
I'm currently using OmniRom's last build with Magisk module cross-breeder lite edition.
It's giving me Quite decent performance and Battery life.
Normally on continuous usage, it lasts almost 5-6 hrs on single charge.
_____________________________________________________________
If anyone getting a better Battery life, don't hesitate to post below.?
Post-Credit: @me ?
Thanks for sharing, I cannot give screenshots for everything here. I might have them but have to dig into the folder of screenshots but for now here is my battery experience over all.
I have used PA, Carbon and Omni extensively. So everything below is not a ROM review but its battery usage over all with them.
P.S. : For all ROMs, I use Greenify and Doze mode (within ROM, if not available then via NapTime).
PA for me has always been close to stock nothing great maybe a bit better. But because of its roaming issue I stopped using it. And switched to carbon.
Carbon is far better than PA and has very little standby/idle drain but it started giving me a weird 20-25% battery cut off issue and device used to shut down randomly anytime below 25% so I switched to Omni.
Omni has fared pretty well for me. Unlike other ROMs I get consistent battery life i.e. 3-4hrs SOT over a period of 10-15hrs. The ROM seems far more stable and there aren't any random battery drains. Omni sometimes behaves a bit erratic when using new camera apps i.e. first few times it would drain battery a lot but later it works fine. Its the device or ROM I don't know.
For Duo video calls it isn't so great after 30-40mins of call the battery is down by 30% maybe. But that is fine I guess the video call is on data too. So Robin isn't so great for that sort of heavy use in general I guess.
Here is my most heavy use day (on all ROMs) for which 10-12hrs is most the device can sustain.
Morning (for the device) starts at about 6:30-7am.
Its day starts with 96-100%; no matter how much juice it has I make sure I unplug anywhere above 95%.
My usage isn't heavy but I use data(3G/4G) 90% of the time,
Location/GPS is ON for about 40-80mins,
Voice calls ~30-90mins in total, (Most are cellular, 5-10mins VoIP calls)
60-90mins podcast/music, Podcasts which I listen are downloaded before but music is streamed via NewPipe ,
Mail, Twitter, Excel, Pocket app, Camera is used in between randomly.
I don't watch much YouTube on the device maybe a couple of 2-3mins clips, I mostly scroll YouTube to add them to watch later for watching on desktop,
SOT ~3hrs
I have to plug the device by 6-7pm with all that usage. Because by that time its about 15%. And for me Robin at 15% means about 10-15mins of use.
For not so heavy use days the device lasts from 7am to 9pm with SOT of ~3-3.5hrs + voice calls of 30-60mins + 40-60mins GPS/location.
Since Android N I haven't touched 4hrs+ SOT over a period of 10-15hrs of usage sadly.
That only happens if I unplug the device and use it continuously for 4-5hrs reading maybe with no waste in idle drain or data or wifi or push notifs etc. But that isn't a case of regular use for me so I will disregard that.
I have recently started using interactive governors like GlassFish and FairPark but can't say they have helped much. Standby/Idle drain is as low as 1-2% over 4-5hrs.
If you are getting 4hrs+ SOT over a longer charge time of 10-12hrs, I am all ears and want to know what different do you do.
I use Omni with Unicornblood kernel and Hawktail profile in Ex Kernel manager. I also use greenify and naptime. I'd say on average I can get between 3 and 4 hours SOT. On the lower end will be days where I'm out and about a lot so I'm on data, lots of idling, random browsing, reddit, messenger, etc. Usually have spotify running in my car through bluetooth. On the higher end will be days where I'm playing on my phone most of the day, with little screen off time, I can probably push over 4 hours on those days.
Today I've been off the charger for 10 1/2 hours, I have 1 1/2 hours of SOT. I spoke on the phone for about 15 minutes, browsed the internet a bit, some instagram, messaging, etc. and I still have 54% left.
I've tried Paranoid Android and LOS.
With PA the battery on my Robin drains like crazy and I noticed some heat problems as well.
As for LOS, it gives me quite decent battery life but had issues with the power button, the phone struggles to wake sometimes.
Should I try Omni then?
Luisalejandroqi said:
I've tried Paranoid Android and LOS.
With PA the battery on my Robin drains like crazy and I noticed some heat problems as well.
As for LOS, it gives me quite decent battery life but had issues with the power button, the phone struggles to wake sometimes.
Should I try Omni then?
Click to expand...
Click to collapse
Sadly there is no perfect ROM every ROM has some issue. The only question is if you can live with that issue.
The only reason for me to stop using PA was it won't work on roaming. But if PA has been stable and battery drain was the only issue try using Greenify and Naptime. The combination of both can drastically bring down your battery drain. And then use some interactive cpu governors aimed for battery life it should bring down drain to as low as 1-2%.
If you are looking for a different better ROM to try then surely try omni, Omni has been great for me so far and has no major issues as such.
/root said:
Sadly there is no perfect ROM every ROM has some issue. The only question is if you can live with that issue.
The only reason for me to stop using PA was it won't work on roaming. But if PA has been stable and battery drain was the only issue try using Greenify and Naptime. The combination of both can drastically bring down your battery drain. And then use some interactive cpu governors aimed for battery life it should bring down drain to as low as 1-2%.
If you are looking for a different better ROM to try then surely try omni, Omni has been great for me so far and has no major issues as such.
Click to expand...
Click to collapse
Omni, however, doesn't have Qualcomm's hotplugging solution, so both big cores are always on all the time and draining battery whenever your screen is on. Gandalf also messed something up with the kernel sources and broke NFC, requiring you to flash a kernel from an Omni weekly from around June-ish or July-ish to restore that functionality.
If you're patient enough, javelinanddart and Sultanxda will soon figure out how to fix the wake-on-plug lag in LineageOS. Hopefully, they'll also start on figuring out the power-button-not-waking-device issue afterwards.
EDIT: oops. Though javelinanddart proooobably found what might be causing the power-button-not-waking-device issue? Haven't had it happen on his LOS 15.1 unofficials yet so...
I am currently using Lineage 14.1-14.1-20180321 and eagerly awaiting the 'official' release of 15.1. I typically do not update to every weekly build. I usually watch the change logs and update only when the new security patches are released. Provided that update is stable (i.e. fast, everything works, no crashes) I will continue on with that build until the next security patch is released. More often than not, there are no issues, as I have found Lineage to be stable and fast.
I am running non-rooted, and I re-locked my bootloader. As a result, Google Pay is working well, without the use of Magisk.
I run Nova Prime launcher, and do not have a vast amount of apps installed:
Music - Google Play Music, Spotify, Amazon Music
Email and Calendar - Outlook, GMail, Google Calendar
Assistant - Google Assistant
Office Suite - Docs, Sheets, Drive, MS One Drive, Word, Excel, Google Keep, One Note
Camera - Stock lineage OS camera, Snapseed (editing)
Messaging - stock AOSP / Lineage OS messaging app
Video - YouTube, Netflix, Hulu (I only use YouTube to be honest... have the other two because of Chromecasting)
Misc - Google Home, Amazon Kindle
I list all those apps to say that given the relative few apps I use, I have all day battery life, for the most part. I am not a heavy user, but I check email multiple times a day, as well send/receive a LOT of MMS/SMS messages throughout the day. I generally only watch video on my phone (YouTube mostly) at home, and I generally cast it to my TV so that the Chromecast does the heavy lifting.
Overall, I have been very happy with Lineage. I finally settled on Lineage after growing disgruntled with AOSPA. The stock ROM (I gave it a good, honest shot at one point) could not cut it because of the lack of stability, heat issues, Bluetooth issues, and no updates.
I have only run into one issue (on a previous build) where by no doing of my own, the screen went blank on a full battery and would not turn on. I though the phone was essentially bricked. Held down power + volume down for 60 seconds (actually had to do this a few different times) and all was resolved. Still do not know why this happened.
Hopefully this helps someone...
@sfbest23
Thank you for replying with so much detail. But a bit of numbers would help in terms of battery life you get from your usage and setup.
Typical phone idle time and SOT. Gives a rough idea of the battery drain in standby.
I am running non-rooted, and I re-locked my bootloader.
Click to expand...
Click to collapse
I am more curious about this. So after flashing LOS you flash back the stock recovery and lock the bootloader? But when you flash back TWRP to install the updated LOS do you lose all your data again or what? Can you tell me the process you follow, I would love to do it but I find backing up and restoring everything for every update is tiresome and a little annoying. Even if one opts to only update for major releases once a month or few months I am not a fan of backup and restore process quite often.
/root said:
@sfbest23
Thank you for replying with so much detail. But a bit of numbers would help in terms of battery life you get from your usage and setup.
Typical phone idle time and SOT. Gives a rough idea of the battery drain in standby.
I am more curious about this. So after flashing LOS you flash back the stock recovery and lock the bootloader? But when you flash back TWRP to install the updated LOS do you lose all your data again or what? Can you tell me the process you follow, I would love to do it but I find backing up and restoring everything for every update is tiresome and a little annoying. Even if one opts to only update for major releases once a month or few months I am not a fan of backup and restore process quite often.
Click to expand...
Click to collapse
I do not have any detailed battery metrics, but I will start tracking this and get back to you.
Regarding your question about re-locking the bootloader... I am still running TWRP, just with a locked bootloader. I did not flash back to the stock recovery. After unlocking the bootloader, installing TWRP and ROM of choice, it is simply a 'fastboot oem lock' command. I cannot remember off hand, but I do believe that the OS was reset when I did that.
My setup. Works very well. I think omni is the best ROM available.
EAT_CHICKEN said:
My setup. Works very well. I think omni is the best ROM available.
Click to expand...
Click to collapse
Same ROM version, same Magisk version but I still get the SafetyNet API Error.
/root said:
Same ROM version, same Magisk version but I still get the SafetyNet API Error.
Click to expand...
Click to collapse
Do you have /system modified? Or xposed installed? Those will cause safetynet to fail.
EAT_CHICKEN said:
Do you have /system modified? Or xposed installed? Those will cause safetynet to fail.
Click to expand...
Click to collapse
Not using xposed.
Does using EXKM for CPU governors constitute to being a /system modification? Then I guess that would be the cause.
Hi, after months (since ai bought my OP5T) of useless attempts to fix my issue, I decided to post here; I was hesitant to do it, because I think if here is someone that can help me, he wouldn't have wanted to do it.
But now, I don't know what else to try.
Sometimes, my phone boot as expected, and my battery drains between 0.3% and 0.9% per hour, and the battery life is about of 2 days, 3 if I don't use Spotify (about 2 hours per day).
But when I reboot, almost always my battery drains between 2% and 4% per hour!
Seems crazy, but I can't find the reason.
I've tried with Official Lineage OS, OmniROM, Liquid Remix, AOSiP, MSM Extended, Validus ROM, FrankenROM, CrDroid and now with Havoc OS; I also tried with Flash Kernel, Franco Kernel, blu_spark and Singularity Kernel; tried also with AKT, Helix Engine, Greenify and Naptime. I also tried disabling Doze for Google Play Service and deny running in background for it.
I tried to disable my apps in blocks, and change any kind of Andoid setting and apps, but nothing, I can't find a solution!
Strangely checking the CPU stats my phone seems to sleep most the time, and I can't find nothing of unusual in BetterBatteryStats or in stock battery stats, but maybe I'm not able to interpret them.
Can I post some kind of log or stats that can helps someone that wants help me? You can ask me any question, I could just be happy because of someone's interest.
?
Hey guys,
I have changed my phone battery recently hoping a better battery behavior and less heating while charging/discharging.
After a few weeks of using the 10 with Resurrection Remix 5.8.3 (I belive, latest official based on 7.1.2) I am sure the battery live increased, but it still has the same problems like before:
1. High battery discharge, even of only listing to music using Bluetooth
2. Very hot in specific apps like YouTube and Fallout Shelter
3. Very Hot while charging, even if powered off
So, there is a problem with the heat management system...
This made me wonder what have recently changed?
I wasn't aware of EAS before my Oreo update, neither I know rhiht right now if the kernel of my nougat Rom is using this system...
I will check on this in a few days.
Another thing I came across, was someone mentioning he is still on marshmallow firmware and it works better for him. At least that was what I understand.
I will search the conversation later, I only have my phone right now.
So I have like three questions:
1. Does anyone know since when EAS was introduced into official htc roms?
2. Someone compared the "stock" kernel behavior to a EAS enabled kernel?
3. Someone compared the problems from nougat/Oreo to a marshmallow firmware?
Greets
Houston
Hi everyone
First of all, I'm not an expert and I'm not a developer as well; I'm just a geek who loves to understand things and solve problems. Now, since I first bought the Mi Mix 3, I noticed that I always had a problem with the battery discharge. When the phone was locked, in fact, it kept discharging very quickly and during the winter, now that my hands are colder than my ex-girlfriend heart, I could notice that even if the phone has been locked for hours, it's always a little bit warm. So he keeps doing something in the background. On the other hand, I never decided to go deeper into this, because I use two LTE sim cards and the network signal in my room is very bad, so I always end up thinking "Maybe the problem is the quality of the signal, the phone keeps attempting to connect to the mobile antennas and it needs a lot of energy". The fact is that my Mi Mix 3 kept discharging even with a very good signal, like 100m straight line to the tower. But again, I thought it was because of the bad optimization of the beta Chinese ROM (I was testing the MIUI 11).
Ok, Two days ago, I finally decided to flash a custom ROM. I love the MIUI but the temptation of flashing stuff is too high, so I went ahead, I downloaded the Evolution X 2.1 and I finally flashed it. The problem was still there. Moreover, now I'm using only one sim card. So let's flash Magisk and then BetterBatteryStats. And finally, I discovered the real problem: The DAMN CPU (both BIG cores and LITTLE cores) never go into the deep sleep state, literally. So I downloaded Kernel Auditor for more details and listen here: when the phone is locked, the BIG cores remain at their minimum frequency (825 MHz) as well as the Little ones (576 MHz, I could set it to 300 and actually I noticed a slight improvement). But no Deep Sleep at all; Kernel Auditor itself says "Never used frequencies: Deep Sleep".
So excellent! The Deep Sleep state doesn't exist at all into my phone, I'd understand having a small percentage of it, but nothing at all, what kind of problem is that? I checked the wakelocks anyway, but there was nothing weird going on. The highest value on the Kernel wakelocks was because of the display management and on the partial ones, the highest was the Google Play Services (Nah, just 1%). So wakelocks were fine. I ended up thinking that the problem was the FIrmware or the Kernel, that's something I'll never know maybe. But I managed to solve the problem.
How did I solve it?
Right at this moment I'm using the Evolution X 2.1 ROM and, to be frank, I thought it could solve the problem but it didn't. For instance, I also tried different governors instead of the schedutil set by default, like conservative or powersave, nothing changed again.
"Ok ok, enough about that, how can I solve it?"
You have to install the XASP (M.A.R.S.) mod. This will solve your problem.
Check the topic:
https://forum.xda-developers.com/mi-mix-3/development/rom-xasp-xiaomi-aosp-snapdragon-patch-t3931721
And the developer's website:
https://sites.google.com/view/miustone/HOME
And the developer's GitHub repository related to the project:
https://github.com/Miustone/MARS-Patch
Some hints:
You need an AOSP ROM in order to make it work. It won't work on any MIUI ROM (I think)!
The installation instructions say that you should flash it right after a fresh install of the ROM (It must be Android 9 / SDK 28 - AOSP ARM64), but I flashed it even after a few days of using and it worked as well.
You need to clone/download the repository, unzip it, move into the unzipped directory (where there's the META-INF), select everything and compress it into a zip file and that will be the patch you should flash using the TWRP recovery.
P.S. I know, it's not really a solution, I mean, If you don't want to root your phone, you have to rely on the original version of the MIUI, but from what I've seen, bot MIUI 10 global developer and MIUI 11 china developer have this problem. If you just don't want a custom ROM but you rooted your phone, you could try the MIUI EU ROM, I don't know if it has the same problem tho.
And finally, let your CPU rest a little bit!
UPDATE: The MIUI EU ROM works very well. The phone manages to go in the deep sleep state as well and everything works fine. So if you don't want to flash multiple zips and do tricky things, just use the MIUI EU ROM and you'll be ok. Let's keep reporting any deep sleep issue here tho!
And thanks everyone for the help!
EU MIUI 11 does not have the problem. I got fed up with the various inadequacies of the current AOSP-based roms and decided to give MIUI another go, although I previously disliked it intensely. Turns out that the EU version of MIUI 11 is stunningly good. Camera works properly, including with the slider, it's super-smooth and fast, notifications work correctly, but the biggest difference is battery life because when the screen is off there's almost no drain at all (in contrast to all the other ROMs I've tried). The only thing I didn't like about MIUI 11 was the launcher, even with the new app drawer option it's still not to my taste, but with Nova installed it works just like AOSP.
invisiblewave said:
EU MIUI 11 does not have the problem. I got fed up with the various inadequacies of the current AOSP-based ROMs and decided to give MIUI another go, although I previously disliked it intensely. Turns out that the EU version of MIUI 11 is stunningly good. Camera works properly, including with the slider, it's super-smooth and fast, notifications work correctly, but the biggest difference is battery life because when the screen is off there's almost no drain at all (in contrast to all the other ROMs I've tried). The only thing I didn't like about MIUI 11 was the launcher, even with the new app drawer option it's still not to my taste, but with Nova installed it works just like AOSP.
Click to expand...
Click to collapse
Well, this is a great thing to hear! Actually, the Evolution X 2.1 with that mod is just amazing, but the preinstalled GCam (Which works perfectly with pictures instead of the one you can install on the MIUI) can't take videos in 4K, only FHD; in general, I find the MIUI camera app excellent, but I can't find it and I'm quite sure I can't use it on this ROM. So maybe I'll give the MIUI 11 EU a try as well, thank you for sharing!
P.S. Turned out that I was having the deep sleep issue even after flashing the patch, but I was able to notice that it was because of the Google Photo app, so check for that if you're experiencing the battery drain problem.
Takenfal said:
Well, this is a great thing to hear! Actually, the Evolution X 2.1 with that mod is just amazing, but the preinstalled GCam (Which works perfectly with pictures instead of the one you can install on the MIUI) can't take videos in 4K, only FHD; in general, I find the MIUI camera app excellent, but I can't find it and I'm quite sure I can't use it on this ROM. So maybe I'll give the MIUI 11 EU a try as well, thank you for sharing!
P.S. Turned out that I was having the deep sleep issue even after flashing the patch, but I was able to notice that it was because of the Google Photo app, so check for that if you're experiencing the battery drain problem.
Click to expand...
Click to collapse
Yes! I'm somewhat shocked at how good MIUI 11 is. The app permissions are still a bit of an annoyance, they seem to install with no permissions by default, so you have to grant them, but there's a new option (I assume it's an Android 10 feature) to allow a permission only while an app is in use which is nice. I've been running it for a few days now and I can't see any reason to go back. The other huge thing it solved for me is the reboot issue with wireless charging that seems to afflict all the AOSP/LOS-based roms (random reboots and bootloops while charging, to test it put your phone on a wireless charger and reboot).
invisiblewave said:
Yes! I'm somewhat shocked at how good MIUI 11 is. The app permissions are still a bit of an annoyance, they seem to install with no permissions by default, so you have to grant them, but there's a new option (I assume it's an Android 10 feature) to allow a permission only while an app is in use which is nice. I've been running it for a few days now and I can't see any reason to go back. The other huge thing it solved for me is the reboot issue with wireless charging that seems to afflict all the AOSP/LOS-based roms (random reboots and bootloops while charging, to test it put your phone on a wireless charger and reboot).
Click to expand...
Click to collapse
Look like you're right! I rebooted my phone while charging it wirelessly and it kept rebooting on MI logo. Interesting bug lol
Takenfal said:
Look like you're right! I rebooted my phone while charging it wirelessly and it kept rebooting on MI logo. Interesting bug lol
Click to expand...
Click to collapse
Yes, and if you leave it on charge overnight, it will occasionally randomly reboot then bootloop until the light wakes you up. Ask me how I know..... I highly recommend you try MIUI 11, I still haven't found any problems with it and I even managed to get Google Pay working, which I wasn't able to do on any of the other roms.
I know that the collection of scripts and stuff posted above have been massively flamed as causing issues elsewhere in the forums. I would generally caution against installing them as many users ended up fastbooting other MIUI devices after trying to install them. I think the dev who made them is trying to do good things, but I would proceed with caution. As others have mentioned, MIUI11 does not seem to have this problem.
@PWn3R Yep, had a nice stressy afternoon with the patch. Managed to make a few aditional mistakes and was locked out of recovery and ended up flashing the phone through fastboot.
I did fix my battery issues though, and it is running quite well now. Instead of roughly 12 hours of battery life I now get over 24 with the same usage.
I really hate MIUI and will never go back for the simple reason that my phone that I used for development was unable to activate ADB sideloading because it has to validate this against Xiaomi servers. And there was an issue there. To much control over my device is in China, so that is a big no no for me. I rather deal with some custom rom issues than that.
I see, but It's the only way I was able to finally put the phone in deep sleep. I don't know what's wrong with the Mi MIX 3 but it's very hard to see the deep sleep state with any ROM, MIUI or customs doesn't matter. I'm trying the MIUI EU now and guess what? The CPU is constantly running at 576 MHz. Only 2 minutes of deep sleep over an entire day without charging it. I only installed Whatsapp, Telegram X, and BetterBatteryStats. The integrated battery tool shows that WhatsApp is the cause of the massive battery drain (don't know if it's really because it prevents the deep sleep state or because it had to restore all the media after the installation); in any case, BetterbatteryStats, on the partial wakelocks tab, shows WhatsApp but only 1% of wakelocks. So I don't really know what the cause is.
Hi - here's my device with over 150 apps installed. I am running Xaomi EU atm with the latest weekly beta.
PWn3R said:
Hi - here's my device with over 150 apps installed. I am running Xaomi EU atm with the latest weekly beta.
Click to expand...
Click to collapse
+1. That looks like mine, too. With the screen off, the drain is less than I've ever seen on any device previously. Modified versions of the rom optimized for a device always perform better than AOSP, particularly on battery. It all comes down to whether you can live with the rest of the crap they usually add. EU MIUI 11 is a pretty good compromise, imo, with a third party launcher installed it's very similar to the other roms anyway.
Takenfal said:
Hi everyone
First of all, I'm not an expert and I'm not a developer as well; I'm just a geek who loves to understand things and solve problems. Now, since I first bought the Mi Mix 3, I noticed that I always had a problem with the battery discharge. When the phone was locked, in fact, it kept discharging very quickly and during the winter, now that my hands are colder than my ex-girlfriend heart, I could notice that even if the phone has been locked for hours, it's always a little bit warm. So he keeps doing something in the background. On the other hand, I never decided to go deeper into this, because I use two LTE sim cards and the network signal in my room is very bad, so I always end up thinking "Maybe the problem is the quality of the signal, the phone keeps attempting to connect to the mobile antennas and it needs a lot of energy". The fact is that my Mi Mix 3 kept discharging even with a very good signal, like 100m straight line to the tower. But again, I thought it was because of the bad optimization of the beta Chinese ROM (I was testing the MIUI 11).
Ok, Two days ago, I finally decided to flash a custom ROM. I love the MIUI but the temptation of flashing stuff is too high, so I went ahead, I downloaded the Evolution X 2.1 and I finally flashed it. The problem was still there. Moreover, now I'm using only one sim card. So let's flash Magisk and then BetterBatteryStats. And finally, I discovered the real problem: The DAMN CPU (both BIG cores and LITTLE cores) never go into the deep sleep state, literally. So I downloaded Kernel Auditor for more details and listen here: when the phone is locked, the BIG cores remain at their minimum frequency (825 MHz) as well as the Little ones (576 MHz, I could set it to 300 and actually I noticed a slight improvement). But no Deep Sleep at all; Kernel Auditor itself says "Never used frequencies: Deep Sleep".
So excellent! The Deep Sleep state doesn't exist at all into my phone, I'd understand having a small percentage of it, but nothing at all, what kind of problem is that? I checked the wakelocks anyway, but there was nothing weird going on. The highest value on the Kernel wakelocks was because of the display management and on the partial ones, the highest was the Google Play Services (Nah, just 1%). So wakelocks were fine. I ended up thinking that the problem was the FIrmware or the Kernel, that's something I'll never know maybe. But I managed to solve the problem.
How did I solve it?
Right at this moment I'm using the Evolution X 2.1 ROM and, to be frank, I thought it could solve the problem but it didn't. For instance, I also tried different governors instead of the schedutil set by default, like conservative or powersave, nothing changed again.
"Ok ok, enough about that, how can I solve it?"
You have to install the XASP (M.A.R.S.) mod. This will solve your problem.
Check the topic:
https://forum.xda-developers.com/mi-mix-3/development/rom-xasp-xiaomi-aosp-snapdragon-patch-t3931721
And the developer's website:
https://sites.google.com/view/miustone/HOME
And the developer's GitHub repository related to the project:
https://github.com/Miustone/MARS-Patch
Some hints:
You need an AOSP ROM in order to make it work. It won't work on any MIUI ROM (I think)!
The installation instructions say that you should flash it right after a fresh install of the ROM (It must be Android 9 / SDK 28 - AOSP ARM64), but I flashed it even after a few days of using and it worked as well.
You need to clone/download the repository, unzip it, move into the unzipped directory (where there's the META-INF), select everything and compress it into a zip file and that will be the patch you should flash using the TWRP recovery.
P.S. I know, it's not really a solution, I mean, If you don't want to root your phone, you have to rely on the original version of the MIUI, but from what I've seen, bot MIUI 10 global developer and MIUI 11 china developer have this problem. If you just don't want a custom ROM but you rooted your phone, you could try the MIUI EU ROM, I don't know if it has the same problem tho.
And finally, let your CPU rest a little bit!
Click to expand...
Click to collapse
I fixed mine by disabling proximity sensor. My phone got to deep sleep just after
I am running the latest Xiaomi.eu MIUI 11. According the Kernel Adiutor Frequency Table it is going to Deep Sleep whenever not awake, but the lowest frequency for Cores 0-3 is 576MHz, (everything below is unused). Cores 4-7 are almost always in their lowest frequency, 825MHz.
So is this deep sleeping or not? I would not say battery life is amazing. The biggest battery drainer is cell standby, which is more even than screen. I can't get better battery stats to work (keeps repeatedly flashing up the superuser message).
Deep sleep is a know problem on most custom rom, solution: flash XENT kernel, been using RR with xent for a while and deep sleep work well.
patp said:
I am running the latest Xiaomi.eu MIUI 11. According the Kernel Adiutor Frequency Table it is going to Deep Sleep whenever not awake, but the lowest frequency for Cores 0-3 is 576MHz, (everything below is unused). Cores 4-7 are almost always in their lowest frequency, 825MHz.
So is this deep sleeping or not? I would not say battery life is amazing. The biggest battery drainer is cell standby, which is more even than the screen. I can't get better battery stats to work (keeps repeatedly flashing up the superuser message).
Click to expand...
Click to collapse
There should be a deep sleep state even for the BIG cores; the fact that they remain at the lowest frequency (825 MHz) is not good. Also, I don't understand why, when the phone is locked, the minimum frequency is not lower than 576 MHz when the LITTLE cores could go at 300 MHz, but that's not really a problem). Maybe it's related to the fact that your phone keeps searching for a good signal, and maybe that's why stats tell you that "cell standby" is draining a lot of battery. Is your phone the global version (the phone, not the ROM) or the Chinese one?
GVN.Gallus said:
Deep sleep is a known problem on most custom ROM, solution: flash XENT kernel, been using RR with xent for a while and deep sleep work well.
Click to expand...
Click to collapse
Interesting, I'd like to give it a try;
UPDATE : Anyway, besides the first deep issue problem, now the phone is working perfectly with the MIUI EU v 11 based on Android 10. When I lock the phone there's no more battery drain AT ALL. If I lock it at 15% and I unlock it after 2 hours, it's still at 15%. This is how deep sleep should Work. Maybe the first problem I had with the EU ROM was related to the google services syncing all my stuff (still don't understand why some things that keep the CPU from going in the deep sleep state are not shown even using BBS).
Note for anyone switching to the weekly MIUI/10 rom, I had microphone issues on calls which appear to be solved by flashing the latest firmware.
Edit: Firmware wasn't the fix. The workaround is to toggle the speakerphone on and off again. The microphone then works on all calls until you reboot the phone, then you have to do the toggle trick again.
GVN.Gallus said:
Deep sleep is a know problem on most custom rom, solution: flash XENT kernel, been using RR with xent for a while and deep sleep work well.
Click to expand...
Click to collapse
Where can I find XENT kernel, please?
ChienJian said:
Where can I find XENT kernel, please?
Click to expand...
Click to collapse
You can find it in the Mi Mix 3 Global Community telegram group: https://t.me/MiMix3Global
Takenfal said:
There should be a deep sleep state even for the BIG cores; the fact that they remain at the lowest frequency (825 MHz) is not good. Also, I don't understand why, when the phone is locked, the minimum frequency is not lower than 576 MHz when the LITTLE cores could go at 300 MHz, but that's not really a problem). Maybe it's related to the fact that your phone keeps searching for a good signal, and maybe that's why stats tell you that "cell standby" is draining a lot of battery. Is your phone the global version (the phone, not the ROM) or the Chinese one?
Click to expand...
Click to collapse
Global version. But I fixed the battery drain. Completely uninstalled WhatsApp, deleted folder and reinstalled latest. Deleted Play Services data. Set preferred network to LTE/WCDMA. Now I have minimal cell-standby and battery doesn't drop significantly when screen is off.
Frequencies remain the same, but maybe the min freq is a red herring - Kernel Adiutor says it spends plenty of time in Deep Sleep.
My phone is usually on idle and not used due to my job. But Im noticing extreme battery consumption even when Im not using it. Never had this issue with other phones. Last night I checked the batter before sleep and it was at 67% at 1 AM, today its 62% at 7 AM so there must be an issue because it should only drain 1 or 2 percents during idle.
In battery settings the top app using the battery is phone idle.
Im on xiaomi.eu 12.5.6 rom but I had the same issue with stop 12.5.3 so I dont think it's because of rom.
I had great battery life with my last phone which was poco x3 nfc with the same settings and apps so it's not because of any third party apps either.
Anyone else experiencing the same problem?
With AOSP ROMs, I even had worst experience when I installed one of the custom kernels because they somehow didn't put the phone into deep doze correctly. But yeah, the idle consumption is quite high - even on stock Kernel.
Currently I use HavocOS and its stock Kernel - and SuperFreeze (from F-Droid store) to freeze most apps right after screen lock. Idle consumption has dropped to 0.1-0.2%/h as a result. I made a thread some days ago regarding this topic... see here.
Thanks. Im gonna try your guide but it's not the most noob friendly guide I've seen
Just Kidding, thanks for your time.
Oh, my thread wasn't meant to be a guide... I did put it in "Question" like you did, but a mod seems to have moved the thread to "General"
My "solution" is only temporary - at least I hope there are still developers out there who value a low idle drain more than fast charging and benchmark numbers...
esszett said:
... and SuperFreeze (from F-Droid store) to freeze ...
Click to expand...
Click to collapse
Sorry for the OT, could it be that the app. is called SuperFreezZ?
Have you noticed any good battery life gains with this app.?
Yeah, sorry, SuperFreezZ: https://f-droid.org/en/packages/superfreeze.tool.android/
For several months I had the problem that from a certain moment, the consumption at idle suddenly increased enormously (from 0.1-0.2 % to 2-3% per hour). Even if I manually forced all apps to stop, In Android's battery info "Android OS" and "Android System" showed up with double-digit percentages. I could only get the phone back to its previous behavior with a restart.
To date, however, it is not clear to me what triggered this. I suspected GCam for a while, then Osmand+, but I couldn't ever confirm that because the problem didn't start whenever I used those programs, just sometimes.
I never found a real solution for this, but SuperFreezZ did.
The best thing I've used for years now is Greenify, its hasn't received an update in more than a year but still works perfectly
Do we need root to use these apps? I remember using greenify before onmy older devices with root but havent used it for a while. Gonna see how much it drops tonight and then try to tweek some things and recheck it tomorrow night.
Weird thing is, I was getting an awesome battery life out of poco x3 nfc, could it be because of the cpu idle? Because that's the only thing that seems different between the 2 devices. (X3 even had an lcd which is supposedly less battery friendly)
Kianush said:
Do we need root to use these apps?
Click to expand...
Click to collapse
Yes.
Kianush said:
I was getting an awesome battery life out of poco x3 nfc
Click to expand...
Click to collapse
Unfortunately, hardly anyone notices this because most users do exactly what the F3 was designed for: Playing games.
I came from a 2.5 years old F1 and it lasts easily longer than the F3 although it has a smaller battery and a LCD screen... The F3 behaves anything but fully developed. These latest high-end SOCs (870, 888) are really powerful, but unfortunately not equally power-efficient. That's the reason why I throttled the CPU and undervolted the GPU. This dropped the active drain from ~8 %/h to <5 %/h on my device and my usecases.
esszett said:
Yes.
Unfortunately, hardly anyone notices this because most users do exactly what the F3 was designed for: Playing games.
I came from a 2.5 years old F1 and it lasts easily longer than the F3 although it has a smaller battery and a LCD screen... The F3 behaves anything but fully developed. These latest high-end SOCs (870, 888) are really powerful, but unfortunately not equally power-efficient. That's the reason why I throttled the CPU and undervolted the GPU. This dropped the active drain from ~8 %/h to <5 %/h on my device and my usecases.
Click to expand...
Click to collapse
Yeah. I used to underclock the cpu on my old phones but I dont know about undervolting. wouldnt it cause issues? I just used 3c toolbox app to set a lower max clock and a lower min clock for cpu cores. I read somewhere that rooting xiaomi.eu rom breaks some functions so I havent rooted it yet. do you have any info on that?
Kianush said:
Yeah. I used to underclock the cpu on my old phones but I dont know about undervolting. wouldnt it cause issues?
Click to expand...
Click to collapse
As long you don't push too hard with undervolting, it works quite well. See attached image (it's not mine, but I have oriented to it).
Kianush said:
I just used 3c toolbox app to set a lower max clock and a lower min clock for cpu cores.
Click to expand...
Click to collapse
I've never heard of it... This seems to be a powerful tool! Nice!
Kianush said:
I read somewhere that rooting xiaomi.eu rom breaks some functions so I havent rooted it yet. do you have any info on that?
Click to expand...
Click to collapse
Konabess doesn't need root, afaik. Extract the boot.img of your ROM and copy it into a folder of your device. Then use Konabess to modify the settings and repack it into a modified boot.img. This file you can flash with TWRP. No guarantee that it works for xiaomi.eu, but it works for AOSP (at least it worked for me).
Kianush said:
My phone is usually on idle and not used due to my job. But Im noticing extreme battery consumption even when Im not using it. Never had this issue with other phones. Last night I checked the batter before sleep and it was at 67% at 1 AM, today its 62% at 7 AM so there must be an issue because it should only drain 1 or 2 percents during idle.
In battery settings the top app using the battery is phone idle.
Im on xiaomi.eu 12.5.6 rom but I had the same issue with stop 12.5.3 so I dont think it's because of rom.
I had great battery life with my last phone which was poco x3 nfc with the same settings and apps so it's not because of any third party apps either.
Anyone else experiencing the same problem?
Click to expand...
Click to collapse
I'm ont he same rom as you and let me explain my experience.
My battery has been insanely good. Even with heavy usage over a period of 4 hours, which included 1.5hrs of SoT and pandora playing though bluetooth all 4 of those hours with dolby and viper enabled. Was at 100 and dropped down to 94%. So It may be an app or setting that you have installed causing problems and draining battery. The only battery saver addition I have installed is Universal GMS doze. Idle time for me It takes me about 5 hours to drop down 1%.
Zaiaku said:
I'm ont he same rom as you and let me explain my experience.
My battery has been insanely good. Even with heavy usage over a period of 4 hours, which included 1.5hrs of SoT and pandora playing though bluetooth all 4 of those hours with dolby and viper enabled. Was at 100 and dropped down to 94%. So It may be an app or setting that you have installed causing problems and draining battery. The only battery saver addition I have installed is Universal GMS doze. Idle time for me It takes me about 5 hours to drop down 1%.
Click to expand...
Click to collapse
Well if there is an app that is causing this, it should be shown in the battery settings. But the only thing that is eating up my battery is phone idle. So it might be a service or something. Im out of options right now unless I find a way to root this rom without facing new problems.... Worst thing with miui is that you cant do things like rooting as easy as other roms.
Btw, would you please tell me the settings and xiaomi.eu version you are on? Im on 12.5.6 stable and using 120hz + vivid color scheme and most of my apps are on blcok background activity except my messaging app. And Im losing battery on phone idle not the screen on time!
Ss below.(dropped from 92 to 82 woh only 30mins screen on time doing nothing but checking xda!) And 7hrs of those 9hrs I was asleep and the phone was on airplane mode + gps off!
You could try BBS or similar apps. Maybe it's an app which prevents the phone to go to deep doze (wakelocks).
BTW: MIUI sucks
Kianush said:
Well if there is an app that is causing this, it should be shown in the battery settings. But the only thing that is eating up my battery is phone idle. So it might be a service or something. Im out of options right now unless I find a way to root this rom without facing new problems.... Worst thing with miui is that you cant do things like rooting as easy as other roms.
Btw, would you please tell me the settings and xiaomi.eu version you are on? Im on 12.5.6 stable and using 120hz + vivid color scheme and most of my apps are on blcok background activity except my messaging app. And Im losing battery on phone idle not the screen on time!
Ss below.(dropped from 92 to 82 woh only 30mins screen on time doing nothing but checking xda!) And 7hrs of those 9hrs I was asleep and the phone was on airplane mode + gps off!
Click to expand...
Click to collapse
I switch my screen refresh rate down to 60hz but since your phone is idle it really shouldn't come into play unless you have always on display or turn screen on for notifications.
Rooting this phone is amazingly easy. Takes like 5mins if that. My Mi 9 lite took longer to root then this phone.
As far as an app draining battery, It more then likely not it since you saying phone idle, which in the past people have said if you phone has problems with signal this can drain a battery. For me this has been a major issue. With AT&T service I would loose double the amount of battery over night (I play pandora through out the night when sleeping). Also if you have apps that are heavy internet usage (unsure where you at but things like facebook and messenger drain tons and yet don't register battery drain on most analytics. And since you using a xiaomi.eu rom I know alot of those bg services are disabled or removed.
Zaiaku said:
I switch my screen refresh rate down to 60hz but since your phone is idle it really shouldn't come into play unless you have always on display or turn screen on for notifications.
Rooting this phone is amazingly easy. Takes like 5mins if that. My Mi 9 lite took longer to root then this phone.
As far as an app draining battery, It more then likely not it since you saying phone idle, which in the past people have said if you phone has problems with signal this can drain a battery. For me this has been a major issue. With AT&T service I would loose double the amount of battery over night (I play pandora through out the night when sleeping). Also if you have apps that are heavy internet usage (unsure where you at but things like facebook and messenger drain tons and yet don't register battery drain on most analytics. And since you using a xiaomi.eu rom I know alot of those bg services are disabled or removed.
Click to expand...
Click to collapse
Yeah thanks for the info. I used to root my devices easily by flashing magisk but it seems they have changed the method, though I found the method on a post on xiaomi.eu website and rooted my device.
Tried to lower cpu frequencies a little and use superfreez app. It seems better now but not as good as what you say...
Gonna play with settings a little bit more and wait for another xiaomi.eu stable update to see if it's a bug on this version.
Kianush said:
Yeah thanks for the info. I used to root my devices easily by flashing magisk but it seems they have changed the method, though I found the method on a post on xiaomi.eu website and rooted my device.
Tried to lower cpu frequencies a little and use superfreez app. It seems better now but not as good as what you say...
Gonna play with settings a little bit more and wait for another xiaomi.eu stable update to see if it's a bug on this version.
Click to expand...
Click to collapse
Someone made a auto script for it, but you will have to reflash rom and factory reset data. You really shouldn't have to change cpu feqs. Also uploading a screenshot of my last 2 hours. I know its only 21min of SoT but also 2 hours off charger but playing pandora as well as some other app usage but still at 100%
esszett said:
As long you don't push too hard with undervolting, it works quite well. See attached image (it's not mine, but I have oriented to it).
I've never heard of it... This seems to be a powerful tool! Nice!
Konabess doesn't need root, afaik. Extract the boot.img of your ROM and copy it into a folder of your device. Then use Konabess to modify the settings and repack it into a modified boot.img. This file you can flash with TWRP. No guarantee that it works for xiaomi.eu, but it works for AOSP (at least it worked for me).
Click to expand...
Click to collapse
Konabess without root won't start, any idea?
thanks
tojdvd said:
Konabess without root won't start, any idea?
Click to expand...
Click to collapse
Ah, ok... I thought you could load a separate boot.img - my fault, sorry!
Then you've to have root for Konabess...
Just to show what's possible with HavocOS 4.9 and 12.5.6 EEA firmware, see atached screenshot... It's with the stock kernel of HavocOS, but with the modifications I did mention here.
Running for almost 2 days
~8 hrs SOT (2 hrs of which with 120 Hz and 2 hrs of which with 100 % brightness, otherwise 60 Hz and brightness between 25 and 50 %) and still 50 % battery left.