Develop Bugs

VillainROM 12.0.0 Wi-Fi system hang...

Hello all. Kinda new here, but I've been flashing my hero with roms from here for a while now. My latest attempt at a good rom is the VillainROM 12.0.0, this is my first time with a VillainROM, and I don't know if this bug exists in previous versions. In my opinion it is a very minor issue, but maybe not for someone else. I'm not a developer, so I don't know what could be causing it, and I don't know if I should be reporting bugs on the VillainROM site, or here, so I'm going to start here...
I downloaded the ROM from the VillainROM12.0.0 thread...
Install was flawless, worked perfectly.
The ROM runs extremely well in all functions, so no complaints there.
The only issue is a slight (10+ seconds) hang when I press the power button to turn on the screen to unlock it and the WiFi connection has timed out. Other ROMs I've used, including the stock ROM would come out of this sleep mode, and then try to reconnect to the WiFi, and they've done so with flawless success. However, this ROM does not, at least not for a minute or so.
This is how I can reproduce the problem, and it takes a while. I usually plug my phone into a charger at night and let it charge over night, and unplug it in the morning to head off to work or whatever. Once the screen turns on on its own after the external power source is disconnected (which all ROMs have done) the screen is unresponsive, and all buttons are unresponsive. The screen remains lit up on the lock screen stuck for at least 10 seconds, then goes black, then pressing the power button to turn the screen back on will restore the phone to an unlocked state (assuming it remembered the swipe action from when the screen was locked and stuck) but takes about another 5 seconds to come back on. This only happens if I have the WiFi radio on while the phone is sitting idle for an extended period of time (long enough for the radio to automatically go into its sleep mode perhaps?).
Here's the info from my phone...
Firmware Version: VillainROM9.0.0
Baseband Version: 63.18.55.06JU_6.35.09.26
Kernel Version: 2.6.29-ninpo-freqtwk{AT}titan-dirty-b7a296faninpo{AT}titan #39
Build Number: VillainROM12.0.0
Software Number: 3.32.405.1
Browser Version: 3.1
I'm not sure if this is just a fluke, if I should reflash and see if the problem persists. Anyone else able to reproduce this?
Again, if this is the wrong forum, please feel free to move it, and thanks XDA, this site is an awesome resource!
PS... I had to replace the at sign with {AT} in the Kernel Version due to Forum restrictions (It thinks it's an outside URL and I'm too green to be able to do that...)...

Are you running setCPU or OC Widget?

It look likes the lower CPU frequency is too low. Open SetCPU or Overclock Widget and increase it a little.
If you use profiles, in SetCPU:
> Check if you have a "Sleep Profile"
> Check if its frequences are too low.
> If yes, increase it.
It normaly happens when you have a 19Mhz - 2XXMhz on-demand sleep profile.
Increasing that 2XXMhz to 3XX or 4XX may solve the issue.
If not, try to reflash, or use VillainROM IRC at their website.

First your radio is a bit old. Try upgrading to the latest radio from here:
http://villainrom.co.uk/viewtopic.php?f=24&t=323
Second, especially regarding the wakeup issues, try my kernel for VR12 from here:
http://villainrom.co.uk/viewtopic.php?f=97&t=1928
It has no wake-up problems even @ 691/160 (what I used) as well as better battery life and performance....

Turn up your minimum set cpu speed.

erasmux said:
It has no wake-up problems even @ 691/160 (what I used) as well as better battery life and performance....
Click to expand...
Click to collapse
Pulser has no problems waking up at 19MHz with my kernel. Stable Min/Max frequencies are unique to each phone it has nothing to do with the kernel.

In theory I agree with you completely. But in practice with each kernel I get a different wakeup "performance" using the exact same frequencies. I always prefer setting the min to 160Mhz, but like many many others, in most kernels - including your kernel which comes with VR12 I get heavy wakeup issues which disappear only @ min 480. In other kernels (such as those by Radu) these wakeup issues still exist but are less pronounced (very very rare).
For me and others which have given my kernel a shot there have been no wake up issues @ min 160Mhz. Battery life and responsiveness also improved according to those who have tried my kernel (and optimizations).
BTW "my" kernel is just the HTC official kernel release + OC enable, so its more HTC's kernel than mine.
Like you said it is device dependent, ROM dependent, user dependent, everything.... I am just saying that until now I have not gotten any negative feedback on my kernel, and I think people should give it a shot and decide for themselves. Hopefully they will also be kind enough to share their experiences with me, so if there are problems I can try to fix them.

Thank you all for the suggestions. I do not use any OC utilities, it's the ROM as it was when I downloaded it. Barely any applications installed (some games, auto task killer, handcent...).
I've updated the radio to a version I found in a SenseHero 2.1 thread, but that radio broke MMS and some other data network features. I am in the US, on AT&T (I know, no 3G, but I'm ok with that ), will the radios listed work propperly on this network?
I was also able to reproduce the hanging issue by turning on the WiFi, browsing around the Market, and then exiting the market and turing off the WiFi. It seems that during the switch to the mobile network from WiFi is when something funky happens. Is there a way to get logs to show what might be going on?

First of all try the newest radio from here:
http://villainrom.co.uk/viewtopic.php?f=24&t=323
If 6.35.15.14 does not work well for you, try either 6.35.15.11 or 6.35.15.01 - If I am not mistaken they are all from the latest HTC release from different parts of the world, so one of them should work well for you.
If you want to get a log for the problem, use the adb logcat. Another simpler option to try and isolate the problem is check if reflashing the ROM (after a backup and a full wipe) solves the problem. Also check if the problem exists in other ROMs.

I have flashed the radio with the latest from the site as suggested (6.35.15.01 was no good when I flashed with that one before, caused all kinds of problems with MMS/SMS, and other network fuctions, but I didn't try that radio with the VillainROM). MMS and such still work, so that is good. I'm going to try to reproduce the other issue tonight, but that may have fixed the issue... I'll update the thread with the results.

Looks like the new radio did not solve the problem. Is the next step the new Kernel?

Sorry for the long delay in response...
The problem is still happening. I have now flashed with a different ROM (Chronos Droid 2.1.2) and the problem persists. However, the lockup doesn't seem to be as bad... Am I the only one with this problem? Should I change my wireless network settings to GSM only? Or leave it on Auto? I'll play around with that and see what happens. It just seems that changing from the mobile network to the WiFi network (and vise versa) is when the problem happens...

Nope, that didn't help. When I went to GSM only, I had no data network connection, and when I went to WCDMA only I had no connection at all. On GSM/WCDMA Only I have both... I wonder if it is something with this phone and the .29 kernel? But then wouldn't everyone here have this problem?

I have this issue too, using ninpo's kernel. I am going to increase my min freq but it's already at 3xx - fingers x'd

I don't see this being a kernel issue, I have a feeling its just a wifi issue on the new rom bases.

m4rk84 said:
I have this issue too, using ninpo's kernel. I am going to increase my min freq but it's already at 3xx - fingers x'd
Click to expand...
Click to collapse
Please let me know what happens.
I did not have these problems using the SenseHero ROMs (older Kernel), only Villain and now Chronos... :S I don't use any OC apps, just leave it all stock from the ROM. If I use one and increase the speed at sleep, (probably an obvious answer) will this drain the battery faster?

Still hanging. Does this have anything to do with wifi's android default sleep behaviour?

I'm having all kinds of lag issues when network queries are starting, especially during MMS/SMS operations. Could be a Handcent update, but the default messager thinger is also quite slow. I'm tempted to go back to an older ROM, this is getting frustrating...

galaxy nexus crash randomly, battery remove is needed.

my galaxy nexus has a problem since a few months.. the phone get stuck and the screen go weird (sometimes totally black, or "noisy"), nothing works, not even the power button, i have to remove the battery to make it work again.
this has happened most of the times while downloading and installing something from goole play or while i get emails notifications and im doing something else in the phone. it does not reboot, like i said, just totally dies till i remove the battery and turn it on again.
now i updated to stock jellybean and i had the same issue. is not all the time like i said, just happens once in a while.. but i do not think is normal..
could it be a hardware issue?? i've been thinking that maybe it could be that the internal storage has some demaged sector and when android tries to write or read from that area make the phone crash.
is there any app for android to find and isolate demaged sectors??? what else could it be??

perhaps it's a hardware issue, probably with your cpu not being able to handle the load

rhed said:
perhaps it's a hardware issue, probably with your cpu not being able to handle the load
Click to expand...
Click to collapse
it seems, it is a common issue called "sleep of death", i wanna think it is a software issue, because users of the nexus 7 are experiencing this too..
but i cant find a solution for this.. everyone seems to know this issue but i have not find a solution..
it is not an app, im sure because this has happened in stock, after a factory reset without any app installed.. i've tried wipe cache also..
in other forum a guy said that could be that the device cant support low voltages and when the cpu go to its minimum frequency it shuts down.. that sounds kind of logical to me, because when the phone crash the battery usage is in its minimum (saw it in the battery statistics)..
i wanna try uncreasing the voltage a little but i cant do it in stock.. if anyone found the solution to this weird and annoying issue please help!!!

Use a uv-capable kernel, disable smartreflex, increase voltages for core, mpu and iva by 10 mV.

[HELP] Panic - CPU seems broken, I need help!

First of all, Hi everyone - chefs, users and admins!
I am writing this post with a really heavy heart now, almost bleeding experience happened to me from nowhere about 2 months ago. I feel quite an advanced "flashoholic", however I've broke up with that few years ago. In 2013 I sold my Note 2 and started "new life" with Android, bought a DSLR and engaged into photography. This year, in february I have bought a tablet as I needed really something for business purposes, and I have chosen a Tab S 10.5 LTE. I didn't ever hear about any Knox tripping or anything, and as soon as it arrived I flashed a AOSP ROM to my thingie as I love AOSP overall. Than strange things started to happen with my CPU. As I recall I have noticed it first after installing Xposed to the tablet - it started heating pretty badly. When I checked my CPU states through ROM Toolbox etc I noticed it sometimes freezes at frequencies around 1.7-1.9 GHz, and during this behavior max frequencies could even fluctuate from 1.7 to 1.8, 1.9 and so on. It looks like "something" changes max frequency setting of CPU as it wants, whenever it wants to and pushes usage to the maximum.
Now, I started to look for a fix - uninstalled Xposed, every root apps etc. Nothing stopped it. I was "pretty sure" the cause is in AOSP thing and the conflict between my hardware and custom AOSP Roms. So after 2 months of tryouts to solve the problem, I today reflashed TW to "finally" get rid if this and save my battery life. What shocked me was... the bug is still here! Even with 0 apps installed, all ROM stock and clean, my CPU goes crazy, the back is hot, and CPU monitoring apps show a hard usage of 1.9 and 1.8 GHz frequencies. At this point I started to panic.
To mention - before I posted this here, tried to search over xda, googling it and so on, but it seems noone has such problem anywhere! As long as I know I can't get my warranty back, and I feel really panic and don't know what to do. I am asking experienced devs or anyone who faced it before for some help, on my knees. This tablet is great, but pretty useless when my battery hits 20% after 4 hours!
EDIT
I snapped a screenshot of some kernel options I don't understand, however someone maybe would find any wrong input here (as I can change them thanks to the app). Thanks. PS. I have changed max fr tp 550 in order to avoid heating and battery drainage, to this moment thayt's the only way I know to stop it.
Thank you very much for any help and advices, and sorry for my bad english.
/K.Z.

Try installing Watchdog, and in the setting include phone and all other process monitoring, see if it can locate what is taxing your cpu.
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite&hl=en_GB
John.

Tinderbox (UK) said:
Try installing Watchdog, and in the setting include phone and all other process monitoring, see if it can locate what is taxing your cpu.
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite&hl=en_GB
John.
Click to expand...
Click to collapse
Thank you, I will try it. Very helpful. I'll post how it's gone.

Tinderbox (UK) said:
Try installing Watchdog, and in the setting include phone and all other process monitoring, see if it can locate what is taxing your cpu.
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite&hl=en_GB
John.
Click to expand...
Click to collapse
Hi John, it looks like that option doesn't work. I see that none of apps exceeds CPU usage over 10%, but the clock still goes on 1.7GHz etc. Sometimes it cools down, but it happens rarely.

Did you adjust the setting to monitor all phone processes, even if you have an wifi only tablet still do this.
John.
Thejungle said:
Hi John, it looks like that option doesn't work. I see that none of apps exceeds CPU usage over 10%, but the clock still goes on 1.7GHz etc. Sometimes it cools down, but it happens rarely.
Click to expand...
Click to collapse

Tinderbox (UK) said:
Did you adjust the setting to monitor all phone processes, even if you have an wifi only tablet still do this.
John.
Click to expand...
Click to collapse
Sure, but the app doesn't seem to have any options button anywhere, just 3 tabs... sorry. However I can see it is monitoring all system apps also, if it helps.

it`s been a while, i will install it on my T800
John.
Thejungle said:
Sure, but the app doesn't seem to have any options button anywhere, just 3 tabs... sorry. However I can see it is monitoring all system apps also, if it helps.
Click to expand...
Click to collapse
---------- Post added at 10:40 PM ---------- Previous post was at 10:37 PM ----------
Hold the button left of the home button down to get the settings, the left touchkey button hold it down to get settings.
John.

Thanks but umm.. nothing happens. Tried holding down task switch capacitive button for few seconds on every tab, but it just goes to task switch view.

Strange, I just hold the button down and within 2 seconds the strip along the bottom of the display appears, maybe you are in the wrong mode, there are three section on the top of the screen, you need to select the far left one called STATS.
John.

Tinderbox (UK) said:
Strange, I just hold the button down and within 2 seconds the strip along the bottom of the display appears, maybe you are in the wrong mode, there are three section on the top of the screen, you need to select the far left one called STATS.
John.
Click to expand...
Click to collapse
VERY strange. I did it on all 3 tabs, just nothing happens. Is it possible that app changes maximum frequency of my CPU? I don't believe any app has possibility to do it on it's own...

Have you tried it again with watchdog on the same screen in my screenshot then press the button, watchdog does not change cpu frequency.
John.

I used to have the same problem on AOSP roms and some Touchwiz roms! When you first flash it and set things up, CPU usage is fine. But after a few days maybe hours, CPU would do the same exact thing like yours! Then my device gets hot and drains battery.
I found this to be a problem with AOSP 5.1.1 roms. Resurrection remix, CM12, PAC ROM and yeah. Never had problems on Cm11. The only ROM that solved my heating issues and no cpu problems are AOSP roms on 5.0.2 or Liquid Smooth rom. 5.0.2 was bug free. Liquid Smooth ROM has an custom kernel which helps cool down the device and reduce the high CPU usage. Seems to be the only ROM without issues for me on 5.1.1. For Touchwiz roms, I just install skyhigh kernel and turn on hotplugging and CPU multicore power saving to solve heat issues. But really on Touchwiz roms, CPU is fine most of the time for me.
My device is SM-T800 BTW. This is what I found out from flashing many roms.
Sent from my SM-T800 using Tapatalk

Little cores running at 1440 all the time

Hey guys, need some help. I have an AT&T H810 rooted 10o. My little cores seem to be running full out at 1440mhz even though my governor is set to Interactive. This is causing it to heat up incredible, to 70c+, and is draining the battery quickly. It seems to have only started occurring in the last few days! I can run it in powersave governor which fixes it to 384mhz, and it fixes the problem, but I don't understand why it is running at full speed under interactive now. The big cores do NOT have this problem AT ALL.
I've removed any apps I installed during that time, cleared my phones cache, cleared the memory, I have tried running it in airplane mode, I've looked into what apps were running and it seems to be very few. Turned location off. I've tried freezing the play services because I have been getting a very intermittent force close. I have also tried to disable all xposed modules, and used avg to scan for any malware. Possibly init.d? Possibly the new xposed v79? I'm at a loss as to what is causing this!
Does anyone have any other ideas as to what could be happening?

There's always the good old factory reset if everything else fails.
Just asking the obvious but there is no offending wakelocks or anything that sticks out in the battery usage stats?

spartan268 said:
There's always the good old factory reset if everything else fails.
Just asking the obvious but there is no offending wakelocks or anything that sticks out in the battery usage stats?
Click to expand...
Click to collapse
Battery usage Android OS is highest at 33, followed by screen at 16%.
Wakelocks, I seem to have them under control with amplify, and I don't see any new ones.
Question about factory reset, I am not near a pc for the next few days, will it cause any problems with xposed or my rooted system image, and basically what can I expect with it? I came from a M8 where with custom recovery I was pretty fearless with being to wipe and refresh, can't do that here.

Noticed that disabling 2 of the little cores with kernel auditor really helps with the heat buildup of the phone with not much slowdown

elementalfusion said:
Noticed that disabling 2 of the little cores with kernel auditor really helps with the heat buildup of the phone with not much slowdown
Click to expand...
Click to collapse
Doesn't solve why it's running at full speed, but I'll keep that in mind.

question about factory reset, I am not near a pc for the next few days, will it cause any problems with xposed or my rooted system image, and basically what can I expect with it? I came from a M8 where with custom recovery I was pretty fearless with being to wipe and refresh, can't do that here.

Personally I never done a factory reset myself yet so i cannot comment.
For the most part it does look like you have something to work with seeing Android OS is taking up the most battery. The hard part is tracking down which process. I'm not the best at this so maybe someone else can chime in. Try taking a look at your currently running processes and see if there's anything odd

Well, after a few factory resets which did not affect xposed, I was able to resolve it to where the cores now return to 384mhz idle. It was something that was installed, and it took 3 or 4 resets after restoring my app backups, and I'm still not sure which app was the culprit. I'm possibly wondering if it was the Amplify module

Sorry for bumping this. I just suffered from this problem and it seems for me it was antutu. For some reasons it was running the background keeping the 4 small cores at 1,2-1,4 cuz constantly. I stopped it and now it's back to normal. Just wondering why it started itself in the first place.
Sent from my LG-H815 using XDA-Developers mobile app

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.