Develop Bugs

Phone Coma

I've tried several builds and am quite happy with each (getting better and better as I learn more and more). I've gotten newer and newer kernels and builds and am currently using Thoughlesskyle's not so super froyo and am really liking it.
The one deal-breaker issue that's keeping me from using this phone full time is something I'm calling a phone coma. The phone periodically refuses to wake up from sleep. I may have a flashing notification light that makes it look like the phone is sleeping but I am not receiving emails or phone calls when it's in this state. To wake it up, I have to press the reset button.
I think this may be related to battery (http://forum.xda-developers.com/showpost.php?p=9360324&postcount=7) and I'm going to try to debug this a bit but I was wondering if anyone else is seeing this. I don't think it's specifically related to any one build as I've seen this with DZO and Thoughlesskyle.
Just for completeness, I'm running a Kaiser with a 1 year old 1600mAh battery, a 2.6.25 kernel and, currently, both Sys and Data are on NAND.
Anyone experiencing anything like this?

Sorry, read too quickly your post.

usually is a radio problem that hang the kernel. try with different radio firmware.

I seem to get one of those about 1 or 2 hours after every kernel flash (that may just be a cooincidence though), and maybe once or twice a week as well.
I haven't been able to identify any app or other thing that might have caused it, as they usually happen when I haven't been using the phone for a while.
Info:
Kaiser 130, 23-11-10 l1q1d kernel, Fat Free Froyo RLS5
I thought it might be something to do with the screen turning on (ie wrong panel type), as when it "freezes", the keyboard lights still go on and off when you open the keyboard. I've never been sure if my Kaiser is panel 2 or 3, but it's happened to me on both panel 2 and panel 3 nbhs, so maybe it's unrelated.

That is a known issue with the .25 kernel did it give you backwards text too? What's weird is its only froyo that has that issue these freezes are also why dzo started porting the new one
Sent from my HERO200 using XDA App

I've never seen the backward text. I'll look at rebuilding with the .32 kernel. Interestingly, it doesn't seem to happen when plugged in (so far). It's only happened once today so I may let it roll for a few days and see what it's like.

I observed it too
Adomatic said:
I've tried several builds and am quite happy with each (getting better and better as I learn more and more). I've gotten newer and newer kernels and builds and am currently using Thoughlesskyle's not so super froyo and am really liking it.
The one deal-breaker issue that's keeping me from using this phone full time is something I'm calling a phone coma. The phone periodically refuses to wake up from sleep. I may have a flashing notification light that makes it look like the phone is sleeping but I am not receiving emails or phone calls when it's in this state. To wake it up, I have to press the reset button.
I think this may be related to battery (http://forum.xda-developers.com/showpost.php?p=9360324&postcount=7) and I'm going to try to debug this a bit but I was wondering if anyone else is seeing this. I don't think it's specifically related to any one build as I've seen this with DZO and Thoughlesskyle.
Just for completeness, I'm running a Kaiser with a 1 year old 1600mAh battery, a 2.6.25 kernel and, currently, both Sys and Data are on NAND.
Anyone experiencing anything like this?
Click to expand...
Click to collapse
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.

doghead said:
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
Click to expand...
Click to collapse
have some patience guys, kernel .25 has this issues, and devs are working hard on kernel .32 to solve this problems, this is a linux kernel and has to mount the file system to read it and then unmount it on shutdown, but recently there have been some issues with the unmounting part on the shutdown (like when u just unplug the power cord on a PC and windows restart with the "blue screen") until devs find a solution, its wise to always keep on hand a recent /data backup. Another word of advice: read! i dont want to sound rude, but all this is commented extensively over the forum.... like l1qu1d would wisely suggest: use the search tool!

doghead said:
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
Click to expand...
Click to collapse
the old kernel only does this with froyo if you still want to use android use n eclair build or donut its not the latest and greatest but they are very stable though

Thanks, I may give it a shot (or I may just buy a samsung captivate ). Your build is very good. Doesn't seem to be as quick as some of the others I've tried but yours has been really stable. I've been running it for about a week. The others
This problem doesn't seem to happen when plugged in - it's only when on battery. I've had some app freeze-ups but, in general, the phone has been really nice.

Adomatic said:
Thanks, I may give it a shot (or I may just buy a samsung captivate ). Your build is very good. Doesn't seem to be as quick as some of the others I've tried but yours has been really stable. I've been running it for about a week. The others
This problem doesn't seem to happen when plugged in - it's only when on battery. I've had some app freeze-ups but, in general, the phone has been really nice.
Click to expand...
Click to collapse
yea not so super is a little bloated if you dont mind a little work fat free is very snappy i just has a blue theme

battery drain

I'm experiencing that my phone seems always died. It doesn't even last 2 hours. I'm using stock everything everything up to date. Is there anything I can do to fix this issue

One user wrote here, that he found a very old battery in his quite new device. Maybe, your's too. There are YouTube's about opening the cover.
Or try a clean install. Stock is no guarantee for clean.

Bump

Wipe it is what I'd do first. I mean like go into twrp and format data then encrypt again. Only takes a minute to encrypt.. if that doesn't work I'd say what the first person who commented could be true. Old battery or your device has been left plugged in too long too many times. I zap mine until it's at 100% then immediately take it off. That's my 2¢ on this. Hope you get it resolved soon. All else fails contact Google and tell them to give you a replacement in a nice way and maybe they will let you send them that unit in and send you another. Worth a shot anyway. Good luck.

Is there a best combo schedular?

Dulguundd said:
Is there a best combo schedular?
Click to expand...
Click to collapse
You may have better luck reviewing what everyone uses in this thread here: https://forum.xda-developers.com/showthread.php?t=3229424
Different schedulers work different ways with different governor's from what I understand. Check out that thread. Plenty of nice settings shared there..
Sent from my Nexus 5X using XDA-Developers Legacy app

If the battery looks warped and gets noticeably hot while charging, it needs to be replaced. That's a no brainer and it cannot be salvaged or worked around. It's kaput.
If the battery is fine, but when you pick up the phone and it feels slightly warm, even though you haven't used it, then it's probably running something when it shouldn't be running. This can be caused by a lot of different things, and can be solved from anything from clearing your cache (this, often solves it), doing a malware/virus scan, all the way to factory resets and data wipes. And what is using the power isn't always apparent via battery usage/monitoring apps, so i wouldn't even bother going that route. And even though it may solve the problem, it may come back, for no apparent, traceable reason - because over time there are updates and we add or remove apps when we use our phone, and we don't know what things are changed and left alone.
Personally, i've tried so many things and some measures have worked but problems come back and persist, to varying degrees. The only sure way that i have done that gives me result is to use the Greenify app and use shallow hibernation and aggressive doze, along with not keeping wifi on during sleep (only when plugged). This ensures that, when i'm not actually using the phone, all processes (apart from core/critical) and any data is completely shut down and thereby the power that is used toward that end is cut off. If i have light use, i can have a charge for as long as 4-5 days at a time, which sounds incredible, but with the screen off most of the time and no background, rogue processes, it's possible. And the app allows you to whitelist apps, so you still get notifications and such (if you keep wifi on or plugged in).
But for this to really work well, you need to have your phone rooted and Greenify working in root, with Usage Access. Also note that this aspect of the app requires you to be on Android 6 or higher. It's a good idea to root your phone since you want to be able to get rid of bloatware that is probably draining a lot of your juice in the first place. But you may have some luck using the app without root or not at Android 6. Try it - who knows.
But do try clearing your cache first (in settings->storage). That may resolve it and you may not need to go further.
Anyway to sum up, ROOT, Greenify, shallow/aggressive doze. Hope that helps.

[SETUP] Share your Current Rom Status Honestly?

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.

CPU frequency sometimes lock on maximum frequency values

Hi guys.
I have global device version, without root, everything is default.
Sometimes (independently how exactly I use the device) it could be locked on maximum CPU frequency. I noticed this issue just, randomly. I've installed CPUZ to see more details about phone and then noticed that all frequencies in maximum (1612 first 4 cores and 1804 all another 4 cores).
Then I've installed AccuBattery to see the energy consumption and noticed that when this bug occurs, the device consumes about 210-240 mAh (with disabled all wireless interfaces surely), but after restart, when everything OK with frequencies stepping, it consumes about 110-140 mAh.
I've been facing this issue on 9.5.19.0 and the same on 8.8.16.
Have someone similar issues? Could you please install CPU-Z (or any anorher similar application) and say if everyone has locked frequencies?
Yes, I know, I've checked all background processes, I've enabled debug mode, connected via cable to laptop and.. adb shell -> top, I was seeing on real CPU activity. It could occurs randomly and then only reboot device could fix it until it happen again.
The same bug I found on the same phone in my friend. Strange, actually.

iFreeMan said:
Hi guys.
I have global device version, without root, everything is default.
Sometimes (independently how exactly I use the device) it could be locked on maximum CPU frequency. I noticed this issue just, randomly. I've installed CPUZ to see more details about phone and then noticed that all frequencies in maximum (1612 first 4 cores and 1804 all another 4 cores).
Then I've installed AccuBattery to see the energy consumption and noticed that when this bug occurs, the device consumes about 210-240 mAh (with disabled all wireless interfaces surely), but after restart, when everything OK with frequencies stepping, it consumes about 110-140 mAh.
I've been facing this issue on 9.5.19.0 and the same on 8.8.16.
Have someone similar issues? Could you please install CPU-Z (or any anorher similar application) and say if everyone has locked frequencies?
Yes, I know, I've checked all background processes, I've enabled debug mode, connected via cable to laptop and.. adb shell -> top, I was seeing on real CPU activity. It could occurs randomly and then only reboot device could fix it until it happen again.
The same bug I found on the same phone in my friend. Strange, actually.
Click to expand...
Click to collapse
i have samne problem on 8.8.16

Just uninstall CPU Z and accu battery problem solve

iFreeMan said:
Hi guys.
I have global device version, without root, everything is default.
Sometimes (independently how exactly I use the device) it could be locked on maximum CPU frequency. I noticed this issue just, randomly. I've installed CPUZ to see more details about phone and then noticed that all frequencies in maximum (1612 first 4 cores and 1804 all another 4 cores).
Then I've installed AccuBattery to see the energy consumption and noticed that when this bug occurs, the device consumes about 210-240 mAh (with disabled all wireless interfaces surely), but after restart, when everything OK with frequencies stepping, it consumes about 110-140 mAh.
I've been facing this issue on 9.5.19.0 and the same on 8.8.16.
Have someone similar issues? Could you please install CPU-Z (or any anorher similar application) and say if everyone has locked frequencies?
Yes, I know, I've checked all background processes, I've enabled debug mode, connected via cable to laptop and.. adb shell -> top, I was seeing on real CPU activity. It could occurs randomly and then only reboot device could fix it until it happen again.
The same bug I found on the same phone in my friend. Strange, actually.
Click to expand...
Click to collapse
I knew this problem about 2-3 weeks ago. When you charging, it go up top freqs too
That's why I want to use custom kernel. But sometimes ( much less than stock ) locked at top freqs so I think it is Miui system policy also.
You should try some kernel manager to solve temporary.
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
SunilSuni said:
Just uninstall CPU Z and accu battery problem solve
Click to expand...
Click to collapse
Problem will back soon on stock kernel

SunilSuni said:
Just uninstall CPU Z and accu battery problem solve
Click to expand...
Click to collapse
Actually bad solution, you know
Zanr Zij said:
I knew this problem about 2-3 weeks ago. When you charging, it go up top freqs too
That's why I want to use custom kernel. But sometimes ( much less than stock ) locked at top freqs so I think it is Miui system policy also.
You should try some kernel manager to solve temporary.
Click to expand...
Click to collapse
Aha, yes, you're right. Now I sorted our everything in my mind and seems it occurs after charging.
Do you think the same issue has all people with this smartphone? But just a lot of them doesn't look on that?
But I'd say it's critical bug to have locked frequencies. Why do you think it's like "miui system policy"?
I had many xiaomi devices, only here I faced with this issue. I thought may be my phone has manufacturing defects.. but seems the bug is general on our device.
What the miui version you have?
Ah, I didn't want to root my device.. I wanted to leave it as is, as stock and don't think about all this headache, but seems the time to unlock bootloader.. Because I haven't root, so, I'm not able to use any kernel managers to reset the frequencies/governors

iFreeMan said:
Actually bad solution, you know
Aha, yes, you're right. Now I sorted our everything in my mind and seems it occurs after charging.
Do you think the same issue has all people with this smartphone? But just a lot of them doesn't look on that?
But I'd say it's critical bug to have locked frequencies. Why do you think it's like "miui system policy"?
I had many xiaomi devices, only here I faced with this issue. I thought may be my phone has manufacturing defects.. but seems the bug is general on our device.
What the miui version you have?
Ah, I didn't want to root my device.. I wanted to leave it as is, as stock and don't think about all this headache, but seems the time to unlock bootloader.. Because I haven't root, so, I'm not able to use any kernel managers to reset the frequencies/governors
Click to expand...
Click to collapse
- I'm on Masik 2.5 with BlackBox kernel. If Kirks solve Dual app problem I will switch
- Miui system policy: I can not freeze/delete many system apps/modules after rooted. I also can not disable many Miui services/procsess ( by MyAndroidTools ). Miui also has performance mode for some purposes, can be auto activate in some cases

Does it drain battery faster? It can be caused by one of your user app. Try to remember when this started to happen, and traceback to the time you install/update apps during that period. Use MiXplorer and check the last installed app. There are apps that can triggered to mine cryptocurrency during charging, making your phone super hot and charge very slow. I am not saying it must be a malware, but it can be some apps that act similarly.
Try to boot to safe mode for several hours to check if it really caused by user app. Turn off your phone > Hold power to turn on > As soon as mi logo appear, quickly hold volume down until the phone finish booting (can be up to 30 seconds). You should see "safe mode" watermark at the bottom left corner, indicating all user app has been temporary disabled. Leave it for several hours to see if the battery still drain or the phone stay awake all the time (high cpu usage). To exit from safe mode, simply reboot.
I always found it is kind of a habit to blame MIUI for everything. I am not defending MIUI here, they bloat a lot. I also hate it and I am using RR now. But on several occassions when we troubleshoot, we found out it is one of the user app that cause the trouble, ads, or slow charging; not anything related to MIUI. Blaming MIUI won't solve the problem, only troubleshooting will lead us to the real culprit. In your case, it still can be caused by the MIUI itself. But until you troubleshoot it out, you won't know who is the real culprit.
For comparison, when still using MIUI 9.5.17.0 I can easily achieve 10+ hours SOT within 1,5 days (max is 14 hours). When switched to RR, affected by the wifi deep sleep drain, I rarely get 10 hours SOT anymore. Still in the process of troubleshooting the problem.

Zanr Zij said:
- I'm on Masik 2.5 with BlackBox kernel. If Kirks solve Dual app problem I will switch
- Miui system policy: I can not freeze/delete many system apps/modules after rooted. I also can not disable many Miui services/procsess ( by MyAndroidTools ). Miui also has performance mode for some purposes, can be auto activate in some cases
Click to expand...
Click to collapse
I don't mind to have additional applications.. But I don't like when my CPU works incorrect O_O
Desmanto said:
Does it drain battery faster? It can be caused by one of your user app. Try to remember when this started to happen, and traceback to the time you install/update apps during that period. Use MiXplorer and check the last installed app. There are apps that can triggered to mine cryptocurrency during charging, making your phone super hot and charge very slow. I am not saying it must be a malware, but it can be some apps that act similarly..
Click to expand...
Click to collapse
I've checked everything. It occurs after charging in most cases. I think that is the bug in governor. Yes, it drain battery a bit faster, but just a bit, I just calculated emergy consumption.
So, when my frequencies was locked, I just connected my phone via ADB to laptop and was looking at the "top" utility to see the load of CPU. And guess what? No load! Idle 796%. (all another 4% for top with refreshing each second and for CPU-Z ran on device).
Weird bug, actually...
I think I have unlock device and re-flash firmware via fastboot to over-write everything.. who knows where bug is hidden.
I've already done full reinstall system. wipe.. but it could occurs even during I read the book. Or just.. enable device, go to CPUZ, and frecuencies locked at max. Absolutely random event

iFreeMan said:
I've checked everything. It occurs after charging in most cases. I think that is the bug in governor. Yes, it drain battery a bit faster, but just a bit, I just calculated emergy consumption.
So, when my frequencies was locked, I just connected my phone via ADB to laptop and was looking at the "top" utility to see the load of CPU. And guess what? No load! Idle 796%. (all another 4% for top with refreshing each second and for CPU-Z ran on device).
Weird bug, actually...
I think I have unlock device and re-flash firmware via fastboot to over-write everything.. who knows where bug is hidden.
I've already done full reinstall system. wipe.. but it could occurs even during I read the book. Or just.. enable device, go to CPUZ, and frecuencies locked at max. Absolutely random event
Click to expand...
Click to collapse
Try not to install anything first after the wipe. Or just try the safe mode. As I said before, it might be caused by the same user app you installed after you wipe.

Desmanto said:
Try not to install anything first after the wipe. Or just try the safe mode. As I said before, it might be caused by the same user app you installed after you wipe.
Click to expand...
Click to collapse
That's could be.
I've unlocked bootloader and just flashed the last 8.8.16 with fastboot (just had thought about it could fix something, may be some thin deep bug).
But no, after I've installed the firmware with fastboot, I've started to install all my software from Google play. And guess what? I just see in cpuz and see the same - frequencies are locked on maximum values.
Strange .. I don't use something custom, or from unverified sources, just everything from google play.
Even without games (just PUBG). All another software just social. FB, messenger, Instagram, telegram, WhatsApp, Viber, and so on. And I even cannot to see what application could cause that. Don't want to root the device. After I've installed everything and rebooted device (to reset that bug with frequencies), now everything normal. Continue observation...
Just wanted to find someone who has the same issue and at least compare revisions, installed apps and so on...to try to find the trigger which causes this issue.

iFreeMan said:
That's could be.
I've unlocked bootloader and just flashed the last 8.8.16 with fastboot (just had thought about it could fix something, may be some thin deep bug).
But no, after I've installed the firmware with fastboot, I've started to install all my software from Google play. And guess what? I just see in cpuz and see the same - frequencies are locked on maximum values.
Strange .. I don't use something custom, or from unverified sources, just everything from google play.
Even without games (just PUBG). All another software just social. FB, messenger, Instagram, telegram, WhatsApp, Viber, and so on. And I even cannot to see what application could cause that. Don't want to root the device. After I've installed everything and rebooted device (to reset that bug with frequencies), now everything normal. Continue observation...
Just wanted to find someone who has the same issue and at least compare revisions, installed apps and so on...to try to find the trigger which causes this issue.
Click to expand...
Click to collapse
That's why I prefer the troubleshooting starting from small first, before going thru the whole ROM flashing. 80% of the time, it is caused by user app. A simple safe mode or factory reset will pointed out a very obvious clue immediately.
Not all playstore app are bug-free, we just don't know what happened in the next update of the app.
While you don't state it before, it can be mediaserver bug. It is caused by the mediascan which stucked at certain file/folder during the scan and keep eating CPU cycle forever. But I've never seen it goes thru almost full CPU load. The solution is to rearrange the files/folder in your internal storage or microsd (if you have it), clean up as needed. Sometimes, a simple restart resolve the issue, but not always.
I have Whatsapp. Some users in the kaskus has FB, IG, Telegram installed; I don't see much complaint from them regarding the CPU usage, except that the IG story are cropped/zoomed (16:9 to 18:9 ratio problem). You can only troubleshoot it step by step, by installing one app at a time. It is very lengthy process and tedious. But usually you can spot which app can be the potential culprit by looking at the battery usage of them. Example, you don't use viber at all, by it appears as one of the highest battery usage.

Desmanto said:
That's why I prefer the troubleshooting starting from small first, before going thru the whole ROM flashing. 80% of the time, it is caused by user app. A simple safe mode or factory reset will pointed out a very obvious clue immediately.
Not all playstore app are bug-free, we just don't know what happened in the next update of the app.
While you don't state it before, it can be mediaserver bug. It is caused by the mediascan which stucked at certain file/folder during the scan and keep eating CPU cycle forever. But I've never seen it goes thru almost full CPU load. The solution is to rearrange the files/folder in your internal storage or microsd (if you have it), clean up as needed. Sometimes, a simple restart resolve the issue, but not always.
I have Whatsapp. Some users in the kaskus has FB, IG, Telegram installed; I don't see much complaint from them regarding the CPU usage, except that the IG story are cropped/zoomed (16:9 to 18:9 ratio problem). You can only troubleshoot it step by step, by installing one app at a time. It is very lengthy process and tedious. But usually you can spot which app can be the potential culprit by looking at the battery usage of them. Example, you don't use viber at all, by it appears as one of the highest battery usage.
Click to expand...
Click to collapse
Yes, I understand that and understand why it would occurs and tried to investigate in this way, but...
I have equals application list which I had on previous device except...CPU-Z and AccuBattery (the AccuBattery for now is removed) because of I faced with this frequencies issues.
This morning it happened again. But I just.. woke up, saw on frequencies - everything OK. Then I just.. Instagram, Telegram, Facebook Messenger and Google Chrome and no more. Then I realized that the phone became a bit warm.. I saw on frequencies - it was locked again
As it happened, I've came to office, connected via ADB to laptop and made several screenshots from `top` utility and looked a bit into `adb logcat`. But nothing... IDLE ~798%. And then I've tried to go to all apps and do force stop for ALL apps. But nothing.
I just rebooted device again...
Please look on it.. https://drive.google.com/open?id=1yXjQQ4rsF3MURh1PF0DZ1Z_Gtgc4-m4_

Just concerning about.. there are a lot errors in logcat. But I understand that.. that's ok.
But 90% of logs flowing from system processes, not from apps. But there is nothing critical.. Nothing something what could flow unstoppable text and caused over-loading CPU.
I'm afraid that it could be manufacturing defects
I event tried to re-flash firmware with fastboot (I thought that byte-by-byte flasing into ROM memory could fix some random small issues). But after flashing with fastboot this CPU locking happening again.
Actually.. dunno what to do with that. The last thought to try any custom ROM (may be Lineage OS) with custom kernel and make sure that it is just bug in Xiaomi's ROM..

And I've posted about this bug on official MIUI forum and seems this bug happening with some people.
http://en.miui.com/thread-3620931-2-1.html
Talking about me. I've flashed Pixel Experience and for now everything good. Seems that's the bug in xiaomi firmware.

iFreeMan said:
And I've posted about this bug on official MIUI forum and seems this bug happening with some people.
http://en.miui.com/thread-3620931-2-1.html
Talking about me. I've flashed Pixel Experience and for now everything good. Seems that's the bug in xiaomi firmware.
Click to expand...
Click to collapse
Maybe that's the random issue with certain apps configuration with some users. Not all reporting the same. Seems to be related to thermal engine or CPU governor configuration. But I don't know where it goes wrong. At least you solved it now by flashing custom ROM.

Desmanto said:
Maybe that's the random issue with certain apps configuration with some users. Not all reporting the same. Seems to be related to thermal engine or CPU governor configuration. But I don't know where it goes wrong. At least you solved it now by flashing custom ROM.
Click to expand...
Click to collapse
I just used custom firmware just for check is that factory defect. But seems that's issue only with xiaomi's firmware.
Yes, I thought that could be governor likewise. But.. Don't think so, because this low-level things, I think, debugged and enhanced successfully by default. Seems some conflicts between system applications.
On custom ROM I haven't faced with this issue, so...
But this morning I've flashed again the global stable firmware (9.6.3.0), will see how it will going..

iFreeMan said:
But this morning I've flashed again the global stable firmware (9.6.3.0), will see how it will going..
Click to expand...
Click to collapse
Yes, I've got first lock on maximum frequencies.
So, after researches.. I could say that it's a bug in xiaomi firmware. Definitely.

I also have this problem on every MIUI rom, with stock or custom kernel. It happens randomly. I have tested in 9.6.19, 9.6.4.0, and betas 8.8.23 and 8.8.30.
If I flash any custom rom the problem desapears so it must be a problem of miui rom itself.

marc_alv said:
I also have this problem on every MIUI rom, with stock or custom kernel. It happens randomly. I have tested in 9.6.19, 9.6.4.0, and betas 8.8.23 and 8.8.30.
If I flash any custom rom the problem desapears so it must be a problem of miui rom itself.
Click to expand...
Click to collapse
I have no problem with Miui based custom Rom + custom kernel

Zanr Zij said:
I have no problem with Miui based custom Rom + custom kernel
Click to expand...
Click to collapse
Could you specify the rom and kernel, please?

Deep Sleep issue and fast battery discharge, how I solved the problem

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.