Related
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
Been running stock Android ever since I got my Pixel XL and have been happily running the phone since it came up with each Android update and security patch. Never an issue.
Since a couple of weeks ago when I got the OTA update for Pie, ever since I have noticed the phone to just be laggy. Switching apps and launching stuff, things just take longer to happen. Sometimes they take seconds sometimes less. Games that would play fine now seem to have low frame rates.
My partner who has the Pixel (not XL) is in the same boat as me but having a worse time with the whole phone becoming unresponsive and locking up all the time.
Now the only reports I've seen regarding Android Pie is fast charging issues but neither of us are suffering those issue. All our PD USB-c chargers continue to fast charge fine. I have also seen some high profile Pixel 2 XL users have lag issues but no lag issues with Pixel XL.
Anyone else having lag issues, low framerates and system lockups with Android Pie on the original Pixel phones?
We have yet to factory flash but want to hold out before having to set everything up again.
A theory I have to why my phone is laggy is that I think the system is throttling back my CPU due to battery health. I know Google put some new smarter battery management in this version of Android but I think it is working too hard to a point where the phone is getting very irritating to use.
Thoughts?
No lags on Android 9 here but also flashed clean with factory image.
My Pixel XL is also bit laggy on android 9.
Clearly visible with this live wallpaper which was running super smoothly in 8.1 android, now it freezes for a fraction of a second when unlocking the phone and live wallpaper kicks in.
General app start seems to have slowed down a bit for me too.
Maybe all this crap began with Adaptive battery thingie?
same problem here a lot of lag and freez in my og pixel xl when using ordinary apps like IG, gallery, clock and even xda apps but strangely it run smoothly when playing heavy game like asphalt or PUBG
---------- Post added at 04:30 PM ---------- Previous post was at 03:31 PM ----------
wingman021280 said:
My Pixel XL is also bit laggy on android 9.
Clearly visible with this live wallpaper which was running super smoothly in 8.1 android, now it freezes for a fraction of a second when unlocking the phone and live wallpaper kicks in.
General app start seems to have slowed down a bit for me too.
Maybe all this crap began with Adaptive battery thingie?
Click to expand...
Click to collapse
I've turn off adaptive battery on my pixel xl but the problem still persists
Phone runs smooth on 9.0 for me. Clean flashed factory image. Maybe you guys too need a clean flash? I do understand that formatting should not be required for a phone to run smoothly after each update but looks like that is the solution for now.
I would agree that Android 9 is not as smooth as 8.1. When I first updated, it ran really bad - I eventually did a factory reset, and while it's not as smooth or fluid as 8.1, there's far less freezes or frame drops.
Went back to 8.1. Pie runs like garbage. It was taking 4-5 seconds to open my texting app. Everything back to normal on Oreo.
Pie was lagging my v1 Pixel XL. Seriously bad and huge battery drain. Did a factory reset and that resolved all my issues. Except for the PITA having to log back into every app and resurrect Google Authenticator for 2FA (make sure to right down all the auth sites and have backup codes ready). But as the other poster mentioned a clean install seems to be the only way to get Pie to work. Just bite the bullet and factory reset Pie.
Same-laggy original pixel XL and fast draining battery+ brightness issue
I'll try to factory reset like everyone is suggesting but wanted to go on record about this since expect more from a Google flagship that's only 2 years old. In addition to what everyone else has said, I've experienced problem with brightness of screen. Before pie update I could really cranking up brightness. Obviously battery would take a hit but sometimes needed that extra brightness. Anyone else experience this?
Relamine said:
I'll try to factory reset like everyone is suggesting but wanted to go on record about this since expect more from a Google flagship that's only 2 years old. In addition to what everyone else has said, I've experienced problem with brightness of screen. Before pie update I could really cranking up brightness. Obviously battery would take a hit but sometimes needed that extra brightness. Anyone else experience this?
Click to expand...
Click to collapse
Do you have adaptive brightness enabled? It is enabled by default and adjusts the brightness based on machine learning algorithms
My pixel xl was lagging too. I noticed my Zooper widgets were not loading. I went into the Zooper widgets app and was prompted with a message about it not being tested on 9 yet. After I acknowledged the message, runs without any lag. Widgets loaded on home screen too. Maybe you have a hanging app in the background.
tiny4579 said:
Do you have adaptive brightness enabled? It is enabled by default and adjusts the brightness based on machine learning algorithms
Click to expand...
Click to collapse
I've had adaptive brightness off so that can't be it. But thanks
how do i disable the pie update notification on my android 8.1 pixel XL?
Can't. Not without root.
My camera was seriously lagging. Sometimes 6-7 seconds to open and then 3-4 seconds to take a pic. Someone mentioned adaptive battery and it occured to me that maybe Accubattery was somehow causing problems with the adaptive battery settings in Pie. I uninstalled Accubattery and now my phone is back to normal. No shutter lag at all, camera opens in a fraction of a second.
Bought it a few days ago with Oreo, updated to Pie, and got one bug fix update after - no lag or something, runs super smooth.
There's really no reason to use things like that anymore, especially with newer versions of Android. It used to be necessary back in the day, hell Greenify was like mandatory lol. But really if you're going to use anything , you'd want a program to turn off GPS while screen is off, stuff like that , but it doesn't honestly make a dramatic difference with the optimization in Pie. I get roughly 4 hours screen on time and about 20% battery life left at the end of a cycle. That's 20% drain per hour and I never turn ANYTHING off. GPS always on, most of my day not on wifi, Facebook, Twitter , I just kill it.
To enjoy pie, its best to format data and flash factory images
I've been rebooting my phone at least once a day because the lag is so bad. It's becoming very frustrating.
murso74 said:
I've been rebooting my phone at least once a day because the lag is so bad. It's becoming very frustrating.
Click to expand...
Click to collapse
Did you OTA update or start fresh flashing an image with fastboot?
I PRESENT TO YOU THE H932 ONLY
RESURRECTION REMIX V6.1.0[WIP]
DISCLAIMER:
Of course flashing this rom you resume the risk of a non-functional device or destruction of a ultimate world war outbreak and adhere the responsibility that comes with flashing a file to your device. If you brick your device, you did something foolish and don't know what you are doing and maybe should not be rooting/roming(that simple). Remember that you are the one taking the risk of flashing/modding your device. Please don't come harassing me due to messing up your device. YOU HAVE BEEN WARNED!!!!!!
ABOUT:
This is a port of Lineage 15.1 and Resurrection Remix V6.1.0 that I have ported over for the H932, it is currently a Work In Progress state. Will continue to work on it as time allows, built it and seen that it is working pretty good and wanted to share with the H932 community
Prerooted(Magisk-systemless), rctd disabled, no verity-force encrypt already installed for your next journey
Due to being a Work In Progress rom, it will have some bugs/issues till they are resolved(hopefully), most of the bugs currently are the ones inherited from Lineage, which this Resurrection Remix is based off of, so please be patient
INSTALLATION NOTES/KNOWN ISSUES:
The percentage meter does not move while installing, simple fix within updaterscript, average install is 5-10min, do not interrupt and it will complete and finish on it own
Install your flavor of Gapps before rebooting to RR, Magisk will force close once after reboot due to Gapps trying to get setup, but don't worry you didn't loose Magisk/Root. After reboot update Magisk binaries
Noticed phone will run a little warm during setup and pre-installation period(reinstalling of backups). After phone settles down and settled in it runs pretty damn smooth
SPECIAL THANKS:
runningnak3d - Making all this possible for the H932. Thank You Running!!!!!!!
me2151 - Bringing Lineage 15.1 to the H932
SGCMarkus - Porting RR to H930
Josh McGrath - Testing & Ideas
Addiso - Testing & Ideas
*If I missed anyone please let me know*
DOWNLOADS:
RR-O-V6.1.0-h932-102318
IN THE NEED OF FLASHING BACK TO STOCK, VISIT THE ALL-IN-ONE FIRMWARE STOP:
H932 T-Mobile Only!!!! All-in-One OEM Firmware Stop
As Always, Thanks for stopping by and ENJOY!!!!:silly:
reserved
reserved-1
I've been running this for the majority of the day. The only thing I'm worried about is my phone running warmer than usual. Especially when on a wireless charger. I can feel the heat just putting my hand on the screen. I'm hoping that this is just the phone "settling in" but I didn't see this behavior when I was on Lineage OS before flashing this. Everything is running smooth otherwise. I'm loving all the customization.
jsgraphicart said:
I've been running this for the majority of the day. The only thing I'm worried about is my phone running warmer than usual. Especially when on a wireless charger. I can feel the heat just putting my hand on the screen. I'm hoping that this is just the phone "settling in" but I didn't see this behavior when I was on Lineage OS before flashing this. Everything is running smooth otherwise. I'm loving all the customization.
Click to expand...
Click to collapse
RR isn't exactly known to be the most coolest (slim ROM, less services, etc.), most battery efficient, most smoothest, etc.
its strenghts are the huge customizability mostly of the UI,
AEX, AOSiP, dot os (having my doubts now with the Smart Pixel overlay and issues with app installations, calls of kang, etc.) - might be better candidates for a reliable daily driver
jsgraphicart said:
I've been running this for the majority of the day. The only thing I'm worried about is my phone running warmer than usual. Especially when on a wireless charger. I can feel the heat just putting my hand on the screen. I'm hoping that this is just the phone "settling in" but I didn't see this behavior when I was on Lineage OS before flashing this. Everything is running smooth otherwise. I'm loving all the customization.
Click to expand...
Click to collapse
It ran a little warm when I first installed it, after adjusting the schedulers and frequencies it runs really cool now(which is what public release is set to), adjustments made was changed scheduler to interactive and changed the max freq. to under what it was set at out of the box, the min was set all the way down to 300mhz so it wouldn't be running max while screen off.
after making adjustments and adding root for public release I reflashed to make sure there was no errors on install, it ran a little warm setting up and installing backups through titanium backup, once set up and settled in it ran way cooler for me
running a bunch of backups of my pc and sd cards, soon as this is done, I will reinstall what I released and give it another go to see if I can replicate what you are experiencing, nothing different should of changed from when I flashed and when you flashed it, unless possibly an app hanging in the background constantly running
zacharias.maladroit said:
RR isn't exactly known to be the most coolest (slim ROM, less services, etc.), most battery efficient, most smoothest, etc.
its strenghts are the huge customizability mostly of the UI,
AEX, AOSiP, dot os (having my doubts now with the Smart Pixel overlay and issues with app installations, calls of kang, etc.) - might be better candidates for a reliable daily driver
Click to expand...
Click to collapse
Yeah, I used to prefer complete AOSP with Xposed and GravityBox but there's nothing available for the T-mobile V30 yet. Just Lineage and now this.
wills3gslide said:
It ran a little warm when I first installed it, after adjusting the schedulers and frequencies it runs really cool now(which is what public release is set to), adjustments made was changed scheduler to interactive and changed the max freq. to under what it was set at out of the box, the min was set all the way down to 300mhz so it wouldn't be running max while screen off.
after making adjustments and adding root for public release I reflashed to make sure there was no errors on install, it ran a little warm setting up and installing backups through titanium backup, once set up and settled in it ran way cooler for me
running a bunch of backups of my pc and sd cards, soon as this is done, I will reinstall what I released and give it another go to see if I can replicate what you are experiencing, nothing different should of changed from when I flashed and when you flashed it, unless possibly an app hanging in the background constantly running
Click to expand...
Click to collapse
It could get better as time goes on. I'll give it another day at least to see how it goes. Do you use wireless charging? That seems to be when it gets the hottest. I also tested out charging with a cable and it wasn't as hot. Again, I'll give it another day. If it continues, I'll try and reinstall
jsgraphicart said:
Yeah, I used to prefer complete AOSP with Xposed and GravityBox but there's nothing available for the T-mobile V30 yet. Just Lineage and now this.
It could get better as time goes on. I'll give it another day at least to see how it goes. Do you use wireless charging? That seems to be when it gets the hottest. I also tested out charging with a cable and it wasn't as hot. Again, I'll give it another day. If it continues, I'll try and reinstall
Click to expand...
Click to collapse
Agree, I normally have xposed installed for all the extra customizing that which ever rom I was running in the past, had it installed on the 20k before I finished RR. Haven't used the wireless charging much due to flashing and constantly having the phone hooked to the computer, but did test it out and did notice it did get a little warmer but not to terribly warmer, have noticed in the past if using NFC to another device or wireless charging the device will usually run a bit warmer, kinda what you are experiencing but not real hot
Is there a way to fix the ctsProfile showing false in magisk? I guess it has something to do with the fingerprint of the device. Maybe a build.prop change?
jsgraphicart said:
Is there a way to fix the ctsProfile showing false in magisk? I guess it has something to do with the fingerprint of the device. Maybe a build.prop change?
Click to expand...
Click to collapse
Have someone pull the fingerprint off the 20k stock LG rom with the following on terminal
getprop ro.build.fingerprint
Or you can simply use the magisk hide module to use a different devices official fingerprint but take note that apps will see your app as that device.
Addiso said:
Have someone pull the fingerprint off the 20k stock LG rom with the following on terminal
getprop ro.build.fingerprint
Or you can simply use the magisk hide module to use a different devices official fingerprint but take note that apps will see your app as that device.
Click to expand...
Click to collapse
Thanks. I'll have to see if someone can get the 20k fingerprint. I don't really want my device showing as something else.
I ended up rerooting/flashing my phone last night. I went back to stock (stock lafs/20k) the other week because I couldn't stop blowing everything out trying roms. Got bored, something about breaking our phones makes it fun. Anyways I loaded this last night once I got everything unlocked. I really like this rom. It's very smooth. The only issue I have run into is not being able to register my fingerprint. On the set up it does nothing. (*I did just read that usually this issue is related to not being on Oreo firmware. Makes sense, I did not goto 20k after unlocking/rooting phone. I will give it a try and report back*)
Only other issue I noticed, my device shows as UNKNOWN. This caused Podcast Addict to have an issue setting language by default.
wireeater said:
I ended up rerooting/flashing my phone last night. I went back to stock (stock lafs/20k) the other week because I couldn't stop blowing everything out trying roms. Got bored, something about breaking our phones makes it fun. Anyways I loaded this last night once I got everything unlocked. I really like this rom. It's very smooth. The only issue I have run into is not being able to register my fingerprint. On the set up it does nothing. (*I did just read that usually this issue is related to not being on Oreo firmware. Makes sense, I did not goto 20k after unlocking/rooting phone. I will give it a try and report back*)
Only other issue I noticed, my device shows as UNKNOWN. This caused Podcast Addict to have an issue setting language by default.
Click to expand...
Click to collapse
The fingerprint sensor does work on this ROM. I use it. And my device shows as LGE LG-H932SV on the play store on my desktop browser. So I do think it's probably not being on Oreo firmware first.
The only other issues I see (and I think they are known in other threads) the always on display causes some issues when turning the screen on sometimes. It also doesn't always turn on after turning the screen off. And the auto brightness is a bit off. I have to turn auto brightness on and slide the brightness bar all the way up for it to work right. This is also the only way the always on display can be seen. Otherwise it's too dim to even use. I have turned off auto brightness and the always on display for now. These two things were also issues in Lineage though.
Fingerprint issue fixed by flashing Oero 20k in twrp then flashing rom. Last night rom was flashed over 10d so firmware wasn't correct. Also device type has corrected itself so that was probably also in relation to firmware versions.
And yes, I noticed the always on display last night. I don't really ever use it anyways so I have no issue disabling it.
I just restored my Lineage OS backup because I just felt the heat issue was too much. It was also causing my battery to drain quickly and not charge as fast on a charger. After restoring Lineage, the phone is a lot cooler and battery seems better. It could have been just me. It could have been something in the background running for some reason but I couldn't find it. Maybe when the next RR update is release, I will do another clean install and see if I still have the issue. But I have to stick with Lineage for now even though I do think Resurrection Remix is better in a lot of ways.
jsgraphicart said:
I just restored my Lineage OS backup because I just felt the heat issue was too much. It was also causing my battery to drain quickly and not charge as fast on a charger. After restoring Lineage, the phone is a lot cooler and battery seems better. It could have been just me. It could have been something in the background running for some reason but I couldn't find it. Maybe when the next RR update is release, I will do another clean install and see if I still have the issue. But I have to stick with Lineage for now even though I do think Resurrection Remix is better in a lot of ways.
Click to expand...
Click to collapse
If you ever decide to go back try kernel managing app and mess with the governors and frequencies, every device is different.
Addiso said:
If you ever decide to go back try kernel managing app and mess with the governors and frequencies, every device is different.
Click to expand...
Click to collapse
I looked into that. I tried other governors but didn't really notice a change. And he already said he set the max CPU to less than what it came with before releasing it so I didn't mess with that all that much. But I'll take another stab at it eventually.
jsgraphicart said:
I just restored my Lineage OS backup because I just felt the heat issue was too much. It was also causing my battery to drain quickly and not charge as fast on a charger. After restoring Lineage, the phone is a lot cooler and battery seems better. It could have been just me. It could have been something in the background running for some reason but I couldn't find it. Maybe when the next RR update is release, I will do another clean install and see if I still have the issue. But I have to stick with Lineage for now even though I do think Resurrection Remix is better in a lot of ways.
Click to expand...
Click to collapse
I'm with you. When I left work my pocket was way too warm. My phone is inside or a thin silicone case. I just tossed it on charge after 6 hours of last full charge because it was already at 5%. System had used over 40% battery use. Only 3hr screen time. Kind of bummed out because I like this rom.
wireeater said:
I'm with you. When I left work my pocket was way too warm. My phone is inside or a thin silicone case. I just tossed it on charge after 6 hours of last full charge because it was already at 5%. System had used over 40% battery use. Only 3hr screen time. Kind of bummed out because I like this rom.
Click to expand...
Click to collapse
Just got home from work, looking in to issues posted
wireeater said:
I'm with you. When I left work my pocket was way too warm. My phone is inside or a thin silicone case. I just tossed it on charge after 6 hours of last full charge because it was already at 5%. System had used over 40% battery use. Only 3hr screen time. Kind of bummed out because I like this rom.
Click to expand...
Click to collapse
Glad to hear someone else's feedback. At least I know it's not just me now. Maybe this can be looked into and fixed with an update.
(FOR LG -H930)
Hello,
I want to share the configuration with which I have been more comfortable with this phone. as always the customs roms have their risks
After trying the following roms & kernels:
Stock rom + lg package disabled
Ion Ios Pie
Havoc Os
Crdroid
ResurrectionRemix 7.0
Bootleggers ROM 4.2 Pie
Pixel Experience
I think I've found the configuration that works best for me:
ROM = LiquidRemix 10.0
KERNEL = AK3Tachyon Enhance EAS T110
OPEN GAPPS = Nano version
CAMARAS
GCAM FOR THE WIDE LENS - DAY PHOTOS - PORTRAIT MODE
GCAM - NIGHT PHOTO
OPEN CAMERA FOR VIDEO RECORDING
* the gcams give me problems with the sound in the video recording, so I use this app
MAGISK MODULES
I know it is designed for other stock versions, but the sound is achieved in both speakers, a non-functional camera app will be installed, with no use of it.
AnxiousV30
OTHER MAGISK MODULES
PIX3LIFY
XMLPAK
YOUTUBE VENCED BLACK
WEB BROWSER
MINT BROWSER
DEVICE CONFIGURATION
Inside Settings we have the liquid lounge section, I have configured this to use the mobile with gestures:
Activate the gestures in: Gestures / Edge gestures, there are different options but this is the one that works best for me
In the screen settings I have the background color in black
With this configuration I get the following:
Stability: I have not rebooted or frozen my phone
Speed: Much difference with some other roms based on aosp and above all compared to stock
Battery: Here one of the main reasons, before almost didn't reach 4 hours screen .. now, usually reach 6, great change!
I run the stock US998 20H on my V30, rooted with Magisk, no modules in use. Hardly anything is really customized I suppose, I do use dark mode wherever possible and I do have the Dark G8 Theme installed from the Play Market. My brightness is always set to 50% unless I'm watching videos (75%) or outside (90%) but I never go higher than that - 100% brightness is bad for OLED technology especially wherever pure white is shown so I avoid full brightness always.
I keep my cellular radio off at home because I only use Google Voice - I don't give out my carrier number to anyone (there's only like 3 people + the carrier that have it) and since I'm always on Wi-Fi at home (Gigabit connection) I have absolutely no reason to have that active. Google Voice does all my voice calls, SMS/MMS, Hangouts (SMS), etc so I'm good there.
Typical SOT? 9+ hours on a charge and that is without using Battery Saver, which I never use, and that is also with a charge from about 88% down to 5% give or take a percentage point either way. The other day I actually got almost 12.5 hours of SOT but I spent a lot of time watching some TV shows ("Billions," a fantastic show, and I basically marathoned the entire 1st season so that was most of the screen on time).
I don't use a lot of things running in the background, in fact I tend to close out apps when I have no reason to leave them in the background whether they go idle or not. I have never thought that using apps like Greenify can help since it's yet another program that does use resources and does require background operation - it's just easier to close the apps I'm not using and be done with it and know for a fact they're not consuming battery.
I use Flipboard quite a bit every day, LiveNewsOn for watching MSNBC/CNN occasionally, Google News multiple times a day, Discord and Hangouts for chatting purposes, not a whole lot else really. I don't do "social media" stuff so no Facebook/etc kinda crap. LG Package Disabler Pro (purchased a long time ago) was used after a clean install of the OS to ensure what I don't need to be there and running isn't there and running.
Only phone that's ever given me this kind of battery life - and I plug in to charge once every 2-3 days, seriously - was a Samsung Galaxy S Active 7 with a 4000 mAh battery, I could run that device for 3+ days with 14+ hours of SOT most every single charge and I really do miss it.
Anyway, I do love this V30 for a variety of reasons but that crazy 9+ hours of SOT on a charge is probably my most favorite aspect so far.
Pics or it didn't happen...
First one was from a few weeks ago with ~9.25 hrs/SOT, the second from a few days ago with ~12.5 hrs/SOT, and again, I don't use Battery Saver at all, if I did, or if I lowered the brightness to 50% or less when watching videos, I'd probably go well past 15+ hrs/SOT without breaking a sweat. The ~9.25 hrs/SOT did have me charging it from my laptop's USB port for about 30 minutes, had to plug it in to move some movie files over to the device so that's why you see the slight rise in the middle there, but the ~12.5 hrs/SOT was done straight off the battery, the charge it had when I disconnected from the charger was 89% so, if it had been a full 100% charge, that would more than likely be close to 15 hrs/SOT. Might have to test that sometime and see if a 100% to 5% run could do that much SOT.
No issues with the stock ROM, no crashes, no force closes, performance is great, I have no complaints whatsoever.
Great post. Thanks for sharing your setups, I will give these suggestions a try once I get mine rooted.
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.