Related
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...
hey,
i've just done some kernal updates (infinityPLAY) and (Jacobs). I installed the infinity kernal...all seemed fine, smooth running, better oc capabilities, better signal (i think)
then to test which one was better, i installed jacobs kernal, which brought up a few issues, mainly a crashing phone.
It now crashes when ever i try to open applications or settings and I get a FC i've never seen before to do with the hotmail app.
I've restored a previous nandroid and reverted back to infinityplay to no avail.
The phone freezes up about 30 seconds into any app then reboots.
havent tried to reflash ROM yet, will do this after work, then restore nandroid again and see if this works......
Any other ideas?
Have you tried lowering the CPU limit ?
UTID
yeah that was one thing on jacobs kernal the settings were UC 19MHz and OC 768MHz and not changable. Now i've reverted back to infinityplay, i cant get into settings because the phone crashes before the settings load so i dont know what my settings are. I've been running at 658-691 on the CM7 nfinity kernal since xmas with no issues
the only other thing i've done recently is installed launcher pro (paid version)
Not sure then sorry,maybe do the fresh Rom like you said.
UTID
Sorted. OC was still at 768 was eventually let me into CPU settings without crashing. Persistence paid off. Back at 652 now...looking better. ill increase to 691 on the morrow.
Ok so for the past 2 AOKP builds (the latest nightly and M1 both Jellybean) i have had this weird issue where upon boot, the CPU would be capped at 700Mhz. so i went into ROM control, set it to 1200 and made sure "set on boot" was on.
eventually, even without a reboot, it woud revert back to 700 MHZ. so i checked my other apps that can controll OC/UC. Franko kernal app, and ROM toolbox were both set at 1200 and not set on boot. so ROM control was in charge of the CPU.
yet, no matter what i do, after about 4 hours on use it reverts back to 700 mhz.
this happened on the included Faux kernel and Franko's latest milestone kernel.
anyone else experiencing this? know what causes it?
On CNA and get the same thing. It's horrible because it will lock up my phone.
Bumping Cuz it happened again. This is the most annoying thing I have come across.
Some of these phones are really picky. Try another rom and see if the problem persists.
tgyberg said:
Some of these phones are really picky. Try another rom and see if the problem persists.
Click to expand...
Click to collapse
*whimpering* b...b....but... I.. like this rom...
BTW, I am on CNA with popcorn kernel which is different than the op so I feel like it's a deeper issue.
CNA kangs literally everything from everyone (not saying that in a derogatory sense).
AOKP has this bug as well, and I'm sure it's being worked on on their side...which CNA will then cherry pick.
I had this before,Download nofrills cpu from play store and set the desired freq,your problem will
Be solved.
Sent from my Galaxy Nexus using Tapatalk 2
I've been using CNA 3.5 and had no problem with the max CPU setting to 700Mhz until i started playing around with all of the settings in the start-up tweaks, Kernel controls, color hack presets, and color gamma tuning. I changed all of the settings back to default and have not had the issue since then (18 hours). I have slowly started enabling all of the tweaks one at a time to see what was causing the max CPU to set at 700MHz.
max boot speed to 700mhz is defined in init.tuna.rc, if i recall it correctly.
Sent from my i9250
tried changing the kernel !
I used CNA 3.5 and 3.6.6 Still the same issue.
Tried Trinity Kernel too it did help for sometime but still it reverts back to 700mhz..
Is there any fix yet.... I really Love CNA so i prefer to stay on this rom.
My friend using PARANOID ANDROID has never experienced such an issue.
Hope it is fixed soon
Thanks
I'm having the same issue on CNA 3.6.6. Even when I set it back to 1200mhz it still never goes above 700 mhz.
I'm having the same problem. On CNA 3.8 right now, but have had the same problem on other custom rooted ROMs based off of cm. I finally figured out that it reverts back to 700 MHz during phone calls--or maybe not every phone call, not sure on that part. All my calls recently have bumped it down. At least now I know when it's switching. Just installed the no frills cpu--hopefully that'll help until this bug gets fixed.
since i cant post this in the dev for cm10 i have to post this here. i installed it last night on my phone and everything has been running pretty good. i understand its still a wip so im not complaining. what has come to my attention is the fact that my phone now likes to run at 1026 no matter how low i set it at. if its sitting there itll change to 384. when i was on stock rom rooted and unlocked, it would never change speed on powersave. now if i go into antutu or just performance under settings minimum will always change to 1026. i havent had a chance to really test if its affecting my battery life but i can let someone know. im bringing it up so maybe the devs can have their way with it. if theres any way i can help, just let me know.
0328 update
with the latest update the speed issue is still there and the camera has been improved although i havent tried video yet. but on 0327 it has like a staircase set up on the upper lefthand side of the screen. did a wipe and fresh 0328 so ill see how that goes. keep up the great work and as always let me know if there is anything i can do to help.
update:recorded video still has issue but nexus7 camera apps work perfectly to get to camera here. flash or the camera worked once and hasnt worked since. still a great rom.
It looks like you're not using the latest cm10 builds, you need to hit the "next" thing on the top right of the download page.
I recommend taking a spin with the houcha kernel. It's pretty much fixed the cpu stuff, and intellidemand governor is amazing; Turns off 3 cores when nothing is taxing and idles at correct minimums.
They are always up to date with the cm10 kernel commits as well.
I get amazing battery life.
Sent from my LG-LS970 using xda app-developers app
0429 update
yeah. its running pretty good. the video recording is fixed so that helps me out at work. with all the phones and tablets i have, i havent installed another kernal so thats the only thing im a little sketchy on doing. but since you recommend it i think i have to give it a look. if theres anything i should know about it, just let me know.
I was on the latest update but I just fat fingered my posts and wasn't double checking it. Just had to install a keyboard that better suites me.
update-flash on the camera work only when i use touch to focus. does that kernal help with that?
clean install of 5/5
Did a clean install last night with standard 4.2.2 gapps. Camera icon has has appeared without the need to install a 3rd party app to access it. Battery life is about the same as before with installing a different kernel. As my daily driver I would recommend it all the way. Follow the forums specific to the ROM and you can't go wrong. I'll keep updating about the progress until I can post on there.
powersave for cm10.1
If you want to get powersave to work correctly; 1.set both speeds to the same number 2.must be below 1026.
If you set them both to 1026, they will stay at that speed. If you set them to two different numbers the minimum and maximum will default to 1026 and1350, respectively, when the system feels it needs the power above 384 and will stay there. Hopefully this will help someone out.
The reason the cpu speed gets raised to 1026 is due to mpdecision. It boosts the cpu speed on touch to increase the interactivity and decrease the lag. mpdecision is a qcom blob and since we are trying to stay as close to mako as possible these is nothing I can do about that blob.
Then I guess my question is why on stock I can run at 384 min with max at 1512 on powersave and it'll actually run at 384 but this cant?
fine for me
I have not really had this problem at all weird
harrybear25 said:
I have not really had this problem at all weird
Click to expand...
Click to collapse
So what min and max speeds is your phone set at? What speed does it end up at after using it for 5 mins on the net?
5/14
my powersave settings with the max at 1512 and min at 384 seemed to stick longer than normal with this rom. im going to backup everything, revert back to zvb and then do a clean install of the latest and see how that fairs.
Did a full restore of my phone back to zvb. Did all the GPS stuff I needed to, rooted and unlocked. Proceeded to do a full wipe and install of 5/27 ROM. Speed issue still there but as noted before I found a small workaround and randomly today I got a message that maps had stopped working.
I did play around with the ROM before install gapps and found some interesting things. None really stuck out except Bluetooth not working at all.
After installing gapps, everything seems to work perfectly. Downloading 5/28 right now and dont expect much to change. Some updates hold my speed settings and some dont. Not really an issue.
6/1 build
powersave function was working correctly with the max at 1512 and the min at 384 right after initial update. using antutu the temp and battery level would be displayed incorrectly. after the first reboot though, everything went back to "normal." but on the brightside if you set the max to 918 and the min at 384 on powersave, it appears to now stay that way. no more having to set them both at the same speed. i will continue to play with the speed settings and see if anything else comes up.
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.