Related
Hi everybody,
Does anyone have the same wakelock?
Nearly 3 wakelocks/min and only 3h30 SOT at 17% of battery
I already searched to find informations about this, but I have no answer..
Thank you all
Yes,same issue here
Yep, same here, although still managing to get around 80-90% deep sleep
Sent from my ONEPLUS A3003 using Tapatalk
I've never seen this before... Only one frequency is used by the system ?
Even i had this.. Clean flashed helped in elimination for me
Hey.
I have the same problems on my Leeco LePro 3 with 7.1.2 rom.
*job.deadline* is keeping device awake.
I lost 10% overnight battery.
What service is that?
Thanks
Same here, do u guys have a EAS kernel or HMP?
Same issue, OOS 4.1.6
So nobody of the developers interested in this?
same here, 2 full wipes without success.
I seem to have the same problem on my S5. I'm on ResurrectionRemix 5.8.3 Nougat.
Battery draining is about 1%+ an hour when idle. In trying to solve this I have discovered a whole bunch of settings'n stuff to increase power-savings on android. I even use greenify, boeffla kernel, and I've turned of LTE.
My phone should now be the champion of battery life, but it only gets about 1/3 of what stock Marshmallow ROM gets. - !!! 1/3 !!! -
Someone mentioned clean flash? Sounds like magic. I mean, that's how I installed the rom in the first place...
I have the same problem. On my OnePlus5 though.
Mine is a staggering 99.4 wakes per minute though.
8771 total for *job.deadline* and 5204 for *job.delay*
I have both a Moto 360 and a Fitbit Charge 2 though. Possibly related to bluetooth and or android wear?
Suggestion: Try to get the latest stock firmware to update bootloader / modem. I did this and battery life improved 50%+ No more crazy wakelocks.
I already was on a very recent firmware, but getting a newer samsung firmware from a different region did the trick.
Edit: Battery still not as good as stock rom. That may be limitation of LOS or something else I don't know.
ive use the latest 4.1.6 stable and the beta 19 with the same issues (clean flashes), it takes no another effekt with or without root.
Same issue here. I found this when I googled it:
/** Deadline alarm tag for logging purposes */
private final String DEADLINE_TAG = "*job.deadline*";
Does this mean it's related to logging? Can I find out what app or how I can disable it?
Push! Same Problem here....
Same Problem here. Android has 2,0 Alarms per minute. After I closed all running apps Android went to 14 Alarms per hour. Next time when I get the failure I will see if I can find the exact App who triggered the problem.
Same issue here on Redmi Note 3 kenzo.
Resurrection remix 5.8.X, guyver kernel
same wakelock on redmi note 3 pro, nitrogen os. can i block it?is it an important wakelock
Blackfireball5 said:
I have the same problem. On my OnePlus5 though.
Mine is a staggering 99.4 wakes per minute though.
8771 total for *job.deadline* and 5204 for *job.delay*
I have both a Moto 360 and a Fitbit Charge 2 though. Possibly related to bluetooth and or android wear?
Click to expand...
Click to collapse
i have that problem too! LG G4, Resurrection Remix and Moto 360. Do other users experiencing this use a smartwatch or some other BT accessory?
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.
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.
Okay people like to know it's there any reason to go back Oreo like battery life, performance, and gcam? Never tested Oreo this phone I update right away phone when I get it.
Stig to pie or Oreo?
And about the camera does hht mode supposed to work this phone? I don't see any difference normal and this Xiaomi night mode.
For me the battery drain is better on Oreo. It's funny because everybody say the ScreenOnTime on Pie is better, but on Oreo I get 8h and on Pie not even 6h of SoT. I use the same apps, same configuration (50% of the time WiFi, 50% Mobile Data activated, Bluetooth activated the whole time).
Also the bluetooth is broken on Pie. I can't even hear music with my bluetooth-earphones, because the audio stutters every 10 seconds... (I tried everything, but nothing work). On Oreo the aren't problems like this.
That are the reasons why I prefer Oreo till they fix these bugs on Pie.
I like Pie and I tested many Treble-Roms, which are based on Pie (battery drain is normal and no bluetooth-audio-bug!!), but there are other bugs (for example the lowest-brightness-bug).
So I will stay on Oreo till there are better alternatives
I recently got this phone. It came with Oreo but I let it update to Pie. Then I downgraded again (using fastboot flash_all) because Xposed doesn't work on Pie and I noted many comments about issues with Pie, particularly with GSIs.
After a week with the phone, I felt like I could do without Xposed so I tried Pie again. Here's my thoughts (after about a week with each).
1) Oreo's automatic display brightness was better. I feel that Pie gets dark too easily and changes brightness too rapidly.
2) Under Oreo my battery only lasted till the end of the day but with Pie, it could probably go 2 days. (see below).
3) No Xposed on Pie. No Play Games is the only thing that I am noticing (stupid games ask for it every time you run them).
* When I flashed back to Oreo, I didn't flash the Pie modem image. That may have been causing the battery drain (one sim slot failed to work at all). I had to manually flash the modem image when going back to Pie since the OTA failed to do that (breaking my 4G in the process).
I'm not really a heavy user. Apart from those 3 things, I haven't noticed much of a difference between Oreo and Pie. All of my apps and use cases have been fine. I haven't even got around to flashing any GSIs because the stock experience suits me.
- Gcam Focus is Broken
- Bluetooth sometimes bad connection
- If BT and WiFi is on, WiFi Speed is broken
Top BT OFF; Bottom BT ON
https://i.ibb.co/sbNQ9g7/50902-screenshot-20190111-110915-2.jpg
- Battery drain much better, holds easily 2 days
- Xposed is working with some bugs, if Xprivacy is active, Apps takes sometimes very long to start
https://i.ibb.co/cxt82Nb/Screenshot-20190310-090520.png
- Automatic Display Brigthness is kinda aggresiv
Is this pure Xposed or can it be used as Magisk-modul?
I had the Xposed magisk module for oreo to avoid modifying system.
For Oreo i use magisk xposed framework v90b3r22. Newer one i can't found in the magisk-modullist.
I returned to Oreo because I was pissed off by a lot of problems in Pie (the system is not finished yet - we got an unfinished version from Xiaomi!) mostly the lack of autofocus in Gcam.
You can see the differences right away:
Brighter screen, a better and more loud sound of the phone, better battery life, a slightly faster interface, logically looking and located icons on the statusbar (everything is shown),
of course, super wifi and other connections and finally AF in Gcam .
We still have to wait until Xiaomi corrects Pie.
It seems that not every Pie user has the same bugs. Never had problems with autofocus on Gcam 6.1 and since I have a new router at home the Bluetooth-WiFi is gone.
Gumka1977 said:
I returned to Oreo because I was pissed off by a lot of problems in Pie (the system is not finished yet - we got an unfinished version from Xiaomi!) mostly the lack of autofocus in Gcam.
You can see the differences right away:
Brighter screen, a better and more loud sound of the phone, better battery life, a slightly faster interface, logically looking and located icons on the statusbar (everything is shown),
of course, super wifi and other connections and finally AF in Gcam .
We still have to wait until Xiaomi corrects Pie.
Click to expand...
Click to collapse
Hi. Did you flash the modem file or just the zip file that fixes sims when downgrading to oreo?
I don't like the battery performance in pie so i want to downgrade but I read there are problems with sims
DonRober said:
Hi. Did you flash the modem file or just the zip file that fixes sims when downgrading to oreo?
I don't like the battery performance in pie so i want to downgrade but I read there are problems with sims
Click to expand...
Click to collapse
In brief: I prophylactically used the options: 'fastboot oem EDL-> Miflash (deep flash)' and 9.6.4 -> ota 9.6.11 to avoid problems with the modem & etc. And factory reset between each operation!
Hi you version of Oreo?
Most stable
Thanks
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.