smp2p-sleepstate Wakelock - Xiaomi Mi 9 Questions & Answers

Hey.
I have a problem. With battery drain caused by a wakelock called smp2p-sleepstate. I guess. I have 0% deep sleep according better battery stats.
What is this and how can i block it?
Thanks in advance

Would you mind specifying what ROM and kernel are you using, and whether you are rooted or not?

Sorry. Forgot it. Its rooted with magisk. Global rom 10.2.9. And stock kernel. Also installed edxposed.

I have the same wakelock on latest ROS with Magisk 19. 4 Canary and everything else stock.
Although it isn't as bad as on your phone

On EEA, Global and Global Beta my phone never went into deep sleep. On ROS my phone is in deep sleep 73% of the time and I'm not rooted.
Battery drain has been a complaint with the MI 9 since launch. The only way to fix it currently seems to be by flashing a custom ROM.

jhs39 said:
On EEA, Global and Global Beta my phone never went into deep sleep. On ROS my phone is in deep sleep 73% of the time and I'm not rooted.
Battery drain has been a complaint with the MI 9 since launch. The only way to fix it currently seems to be by flashing a custom ROM.
Click to expand...
Click to collapse
How do you measure deep sleep in Android pie without root??? And also, cpu usage per application?

MysteriousStranger said:
How do you measure deep sleep in Android pie without root??? And also, cpu usage per application?
Click to expand...
Click to collapse
The DevCheck Hardware and System Info app by flar2 (which can be downloaded from the Play Store) shows the amount of time your phone goes into deep sleep without requiring root access or any special ADB permissions.

jhs39 said:
The DevCheck Hardware and System Info app by flar2 (which can be downloaded from the Play Store) shows the amount of time your phone goes into deep sleep without requiring root access or any special ADB permissions.
Click to expand...
Click to collapse
Mine show 100% deep sleep total. Why?? LoL

Figured out that is has to do Something with the tap2wake and lift2wake feature. When switched off. I have no problems. At the Moment 46% deep sleep.
Any idea how to solve this. Except switching it off of course. I like this feature.

The Shared Memory Point to Point (SMP2P) protocol facilitates communication of a single 32-bit value between two processors.
As the complexity of the SoC grew the state bits array grew and the need for
targeting specific state information at specific remote processors appeared.
SMP2P solves this by having separate shared memory regions per processor-pair.
This state information is e.g. used to convey progress and status of remote firmware loading. Individual bits maps to various stages of the boot and error states.

I have this same wakelock, just appeared on my Mi 9 randomly.
Any fix for this?

scottishblood said:
I have this same wakelock, just appeared on my Mi 9 randomly.
Any fix for this?
Click to expand...
Click to collapse
Bump -
Having the same issue.
(Changing settings under the *#*#4636#*#* dialer code didn't have an effect, nor did turning off 'double-tap to wake'...etc.)
There's a thread on the Russian Mi forum - but Google Translate only goes so far...

My issue looks to have been resolved with a factory reset. Now showing less than 2% kernel wakelock.

Related

[Q] Help with CM11 based ROMs ! Low performance and battery drain

Hello to all,
I have two problems that are almost making me go back to stock 4.3 ROM
The first is related to the battery, the android system appears first with 25% + battery drain, and in most cases equal to or greater than the battery consumption of the screen! This makes my battery does not pass a day, and the stock I went much further (without STAMINA MODE).
The second issue is regarding the performance measured by AnTuTu. I know that does not mean much, but in the STOCK I get 25.5k and I read out there that people also manages the same in CM11 LBL (the MrSteve555 and also bagyusz), I do not understand why I can here the maximum 22.5K .
Independent of ROM I have put the same results. Tested in all versions of MrSteve555 and in the last two of bagyusz. Also tested in the PAC-man RC-1 neXus PRIME, same result and battery consumption.
In all ROMs I wipe system, data, cache, dalvik cache.
Does anyone have any idea how to solve this? I am discouraged because I love the CM11.
Ps: I use .207 kernel and I've tried with .205 also, same result. (I have LBL)
Damn what is that screenshot supposed to show?? 30 minutes off charge and it is at 99%!!! It's obvious that the screen consumption will be minimum, it was on for a minute or so probably... I know that usually android system drain is higher in cm than stock but you should compare your battery stats at the end of the day...
Please reset the counter by tapping on the trash icon on the activity bar. Then please post a screenshot after hours of usage. This will enable other people to properly interpret your battery stats.
Some tips though, you will most likely encounter a slight battery drain while using custom ROMs. This is due to the fact that stock ROM and custom ROM works differently. You might actually having a normal drain than a supposedly "bad" one.
By the end of the day will be the same... Anyway I will post later.
I attached new images for better understanding.
Does anyone have any idea?
Firstly, Antutu scores mean sh*t...
In the past I've had allot of ROMs with very bad Antutu scores which performed much better in terms of speed and general user experience than a standard ROM with higher Antutu score.
Furthermore, install better battery stats or any other wakelock detector app to see what is draining your battery. The pictures you are showing us now don't help at all.
I've exactly the same problem, android consumes always more than 25% battery too...
Silver Wx said:
I've exactly the same problem, android consumes always more than 25% battery too...
Click to expand...
Click to collapse
As I mentioned above, you need to identify what is causing the wakelocks first. Untill then there's absolutely no solution that can be presented to both of you.
By pointed by Gamm86, it might be due to wakelocks. Once the wakelocks are found, you may use Greenify to hibernate that rogue app. When the app is selected within Greenify, you will find it easier to see the wakeup path and cut it off through Greenify.
Wakelock Detector
Greenify
TechnoSparks said:
By pointed by Gamm86, it might be due to wakelocks. Once the wakelocks are found, you may use Greenify to hibernate that rogue app. When the app is selected within Greenify, you will find it easier to see the wakeup path and cut it off through Greenify.
Wakelock Detector
Greenify
Click to expand...
Click to collapse
It's not always apps themselves that cause wakelocks.
Background services related to phone or app settings are usually the culprits, meaning greenify won't resolve all wakelocks.
Gamm86 said:
It's not always apps themselves that cause wakelocks.
Services related to phone or app settings are usually the culprits, meaning greenify won't resolve all wakelocks.
Click to expand...
Click to collapse
yes I understand. Hmm i believe you are more experienced in this matter. Would you tell me how to stop those wakelocks that caused from other services? I would really appreciate that, cause I find many people solve this problem but they never did expose where they learn from or the methods they use. and yea, I've googled but I got nothing
TechnoSparks said:
yes I understand. Hmm i believe you are more experienced in this matter. Would you tell me how to stop those wakelocks that caused from other services? I would really appreciate that, cause I find many people solve this problem but they never did expose where they learn from or the methods they use. and yea, I've googled but I got nothing
Click to expand...
Click to collapse
Use Disable service app. Check which wakelock is occurring and disable that service.
Or get the donate version of unbounce and delay the wakelocks like every hour or so.
I already use Greenify and hibernate all apps that are not chat, not solved.
I also noticed that while I sleep and the phone remains idle the android system does not consume a lot of battery, something around 6%, but when you turn on the screen and the phone is active it starts to drain. So the problem is not in the wakelock, but elsewhere.
I'm using the applications suggested to post new screenshots later.
I used the apps for a day and I'm posting the screenshots of the result ... the system keeps draining and I don't see any information that would help me on the images.
Anyone have any ideas?
Jeanborba said:
Hello to all,
The second issue is regarding the performance measured by AnTuTu. I know that does not mean much, but in the STOCK I get 25.5k and I read out there that people also manages the same in CM11 LBL (the MrSteve555 and also bagyusz), I do not understand why I can here the maximum 22.5K .
Click to expand...
Click to collapse
I'm on MrSteve555's CM for LBL and was also wondering why I was getting a much lower AnTuTu score than stock. Then I discovered that I get 22.5K scores WHEN CHARGING and 25.5K scores running off the battery!
Jeanborba said:
I used the apps for a day and I'm posting the screenshots of the result ... the system keeps draining and I don't see any information that would help me on the images.
Anyone have any ideas?
Click to expand...
Click to collapse
I have noticed the same issues on all 4.4.x based roms (slimkat, pac, PA etc.). The only fix i found was to disable the automatic screen brightness. After disabling it the system_server service became normal and Android System dropped to 9-8% of overall battery consumption.
Good luck
Diablo.69 said:
I have noticed the same issues on all 4.4.x based roms (slimkat, pac, PA etc.). The only fix i found was to disable the automatic screen brightness. After disabling it the system_server service became normal and Android System dropped to 9-8% of overall battery consumption.
Good luck
Click to expand...
Click to collapse
I've exactly the same problem of you : thanks very much for find!
My phone never enters deep sleep when i lock it with WiFi on, this happens on cm11 by steve it drains a lot overnight
4.00 - 4.30 hours on screen = 2 days with playing fifa 15 and facebook + viber. 1-2 photos, 60 mins browsing and about 30 mins talk good for me without using battery safe apps - lock my bl and using .207's kernel on mr.steve555's Weeklies CM11 lbl
try CM11 Mahdi Rom 4.4.4 with gapps minimal 23mb ,my battery work as well after play music,game and facebook

How can I fix this battery drain?

According to BBS, https://m.imgur.com/gbpwAIy,ARaAKEw,YhEGL7w,8rCXPAf,ekGOuPM
Android has a very high alarm count, and it's also partially preventing my phone from entering deep sleep. I somehow forgot to provide a screenshot of bbs's main screen, but IIRC it was awake 27% of the time and deep sleeping the rest. I'd absolutly love to achieve the 0.0%/hr. drain. Plus, I don't use gapps. I also have few xposed modules for battery saving, but I'd really love to fix these. I tried doing a ddg (and google) search on the alarms from Android, especially PKT_CNT_SAMPLE_INTERVAL_ELAPSED, but no luck. Other than that, I have absolutly 0 partial wakelocks and I, obviously, have a few kernel wakelocks. Without any kernel wakelocks, the device wouldn't even work, but even then, the kernel wakelocks barley even exist. I'm currently running minimal os 5.1.1 with the v13 monster kernel. Thank you in advance.
I have a similar problem in stock rom (http://forum.xda-developers.com/moto-g-2014/help/android-os-wakelock-hell-t3390342)
A question:
Do you use "Ambient display" (screen wakes up when you get a notification)?
rafaelrgi said:
I have a similar problem in stock rom (http://forum.xda-developers.com/moto-g-2014/help/android-os-wakelock-hell-t3390342)
A question:
Do you use "Ambient display" (screen wakes up when you get a notification)?
Click to expand...
Click to collapse
No I don't. I've had it in several different roms.
sonic64 said:
According to BBS, https://m.imgur.com/gbpwAIy,ARaAKEw,YhEGL7w,8rCXPAf,ekGOuPM
Android has a very high alarm count, and it's also partially preventing my phone from entering deep sleep. I somehow forgot to provide a screenshot of bbs's main screen, but IIRC it was awake 27% of the time and deep sleeping the rest. I'd absolutly love to achieve the 0.0%/hr. drain. Plus, I don't use gapps. I also have few xposed modules for battery saving, but I'd really love to fix these. I tried doing a ddg (and google) search on the alarms from Android, especially PKT_CNT_SAMPLE_INTERVAL_ELAPSED, but no luck. Other than that, I have absolutly 0 partial wakelocks and I, obviously, have a few kernel wakelocks. Without any kernel wakelocks, the device wouldn't even work, but even then, the kernel wakelocks barley even exist. I'm currently running minimal os 5.1.1 with the v13 monster kernel. Thank you in advance.
Click to expand...
Click to collapse
Revert back to stock rom and update to marshmallow, from this you will be able to get deep sleep mode easily and the rom will be much stable. then for any customization use xposed framework. also use greenify app in boost mode you will get maximum out of your android. cheers.

XT1064 Android 6.0 will not go into deep sleep, CPU stuck awake

I have a Moto G 2014 (XT1064) running Android 6.0 that will not go into deep sleep. I could see that the CPU was never going into the deep sleep state even when the phone was not being used and no user apps were actively running in the background. This is causing abysmal battery life as expected. The phone was updated to Android 6.0 via regular OTA updates. I haven't flashed any third party ROMs onto it at all since I bought it.
The first thing I did to investigate was to unlock the bootloader (it was still locked since purchase prior to this) so that I could obtain root access to see what was going on. This also had the additional affect of wiping the phone to stock Andoird 6.0, which I had hoped would maybe solve the problem but it did not.
My first thought was that it was a user app that was holding a wakelock keeping the phone awake. I looked at the user and kernel wakelock counts via BetterBatteryStats and WakeLockDetector, but from what I can tell it is not any user app that is holding a wakelock at all. Instead it must be some kernel level app keeping the CPU awake, but I can't determine what it is. There isn't any single entry in the wakelock list that sticks out as the culprit.
I have done some other investigative tests such as turning WiFi off while the phone sits unused overnight. This did not have any effect as the phone still remained awake the whole time. I also repeated this test with the phone in airplane mode (WiFi + cellular radios off) and again it had no affect. From this I could only conclude that it was not the wireless radios that were keeping the phone awake. The wakelock counts also didn't show any evidence that WiFi, cellular or GPS were holding wakelocks.
Here are two screenshots I took of the BetterBatteryStats and WakeLockDetector apps showing the highest count kernel wakelocks over a roughly 17 hour period:
(I'd link them in properly but I am prevented from posting outside links on this forum until I have 10 cumulative posts...)
i.imgur.com/nPAY3S6.png
i.imgur.com/5VfgFv1.png
You can see that the phone has been awake 96% of the time during this period, and that the highest count kernel wakelocks are from "event8-1877", "event9-1877", "qpnp_soc_wake" and "qpnp-vadc-e4a28400". I could not find any information as to what these entries mean or what they're related to. Whatever they are, they appear to have abnormally large wakelock counts which leads me to believe that they are related to this problem. The other thing that puzzles me is that the total time for the top four entries in that list only sum to about 2 hours, yet the phone has been awake for almost 17 hours within the same period.
If anyone has any idea about this I'd appreciate the help. I may be completely wrong about the root cause here but I'm running out of ways to debug this.
Updating this thread to say that I have also tried re-flashing stock Android 6.0 using the firmware files linked from this thread (in my case I used XT1064_TITAN_RETCA_6.0_MPB24.65-34_cid14_CFC.xml since I am in Canada). I still experienced the same behaviour where the phone would rarely enter deep sleep. It seemed to be marginally better after re-flashing, going into deep sleep about 10% of the time over a 12 hour period or so, where as before it was only going into deep sleep about 4% of the time during the same period. This still doesn't solve the problem though.
Now I am thinking about downgrading to stock Android 5.0.2 and see if that fixes the problem since I don't know how else to diagnose this.

Battery Life and Wakelocks

Hi guys,
so i newly setup my phone recently with OOS 4.0.3 in order to have a clean phone for the most efficient use.
For my surprise, for the first time using the 3T my energy efficiency was very good, i managed to get 4,5h SOT with the first 50% because i had almost no drain when the screen was turned off.
I attached the screenshots.
Basically, i just flashed OOS 4.0.3 and the newest franco kernel and magisk for root. I didnt use greenify (which i usually do), just the strict standby option in the android settings.
So far so good, but now to the part i cant understand.
I installed gsam battery monitor and gave it root access, so i can have detailed battery information.
From that point, i experienced again the standby drain combined with wakelooks, as u can see in the screenshot starting around 60% of the battery.
So far i uninstalled the app, i used greenify, but i cant get back when i had no wakelocks.
Is it really because of Gsam Battery? How can get away the standby drain without setting up the phone completely new?
PS: I also deactivated some of the access rights of apps, especially for play services.
Is it possible that they regain the access by themselves or that google play services is draining the battery
LazerH said:
Hi guys,
so i newly setup my phone recently with OOS 4.0.3 in order to have a clean phone for the most efficient use.
For my surprise, for the first time using the 3T my energy efficiency was very good, i managed to get 4,5h SOT with the first 50% because i had almost no drain when the screen was turned off.
I attached the screenshots.
Basically, i just flashed OOS 4.0.3 and the newest franco kernel and magisk for root. I didnt use greenify (which i usually do), just the strict standby option in the android settings.
So far so good, but now to the part i cant understand.
I installed gsam battery monitor and gave it root access, so i can have detailed battery information.
From that point, i experienced again the standby drain combined with wakelooks, as u can see in the screenshot starting around 60% of the battery.
So far i uninstalled the app, i used greenify, but i cant get back when i had no wakelocks.
Is it really because of Gsam Battery? How can get away the standby drain without setting up the phone completely new?
PS: I also deactivated some of the access rights of apps, especially for play services.
Is it possible that they regain the access by themselves or that google play services is draining the battery
Click to expand...
Click to collapse
Don't deactivate app rights of play services. It would break the functionality randomly and u won't know what happened. Just enable and reboot. Next time something happens, check the stat in gsam battery monitor. It's a good app and I am using it from 3 years.
It's not gsam I've had it installed on every phone for years and I always get amazing battery life.
I dont use google apps at all besides gmail and maps sometimes. But ill try around if it makes a difference.
I also cant believe that GSAM really is the problem there, but i didnt change anything else, i was just surprised of the good battery life and wanted to see the characteristics of battery statistics when i have a normal standby drain.
And immediatelly from that point on, the standby drain changed as u can see on the screenshots, even after uninstalling GSAM.
I now get 2h SOT with 50%, not 4,5.
So, is it possible that anything influencing that is changing by itself?
I didnt install any app or changed any setting, all i use was setted up in the beginning (franco, magisk, viper, all apps)
Yes google play store and google play services if you downloaded it and installed it that way? Google ruins battery life very randomly. If you restored a titanium backup or sideloaded the app then I have no clue. Even if you didnt do anything different there are a ton of things that can go wrong with android in the background. Recharge and reboot and start over.
954wrecker said:
Yes google play store and google play services if you downloaded it and installed it that way? Google ruins battery life very randomly. If you restored a titanium backup or sideloaded the app then I have no clue. Even if you didnt do anything different there are a ton of things that can go wrong with android in the background. Recharge and reboot and start over.
Click to expand...
Click to collapse
tried everything already + wiping cache/dalvik
I just now wiped also system and dirty flashed the ROM + the stuff i need. Ill see it that solves the deal.
I just cant accept to not have the control over my phone as thats one of the advantages of rooting. I got the same battery life with same usage with my 2,5 year old OnePlus One.
I run the same apps on every phone and this phone has doubled the performance and battery compared to my nexus 6 note 5 and nexus 6p. First phone I've owned that actually sleeps when I turn off the screen.
954wrecker said:
I run the same apps on every phone and this phone has doubled the performance and battery compared to my nexus 6 note 5 and nexus 6p. First phone I've owned that actually sleeps when I turn off the screen.
Click to expand...
Click to collapse
The OPO with CM back then was a dream.
Are u using any apps or adjust settings in order to tweak that behavior?
LazerH said:
The OPO with CM back then was a dream.
Are u using any apps or adjust settings in order to tweak that behavior?
Click to expand...
Click to collapse
I've been on CM13 since the day it came out Dec 11th. I was getting amazing battery and standby on stock since I got the phone late November. I use xposed for tweaking everything but no modules or apps or settings for battery savings.
LazerH said:
Hi guys,
so i newly setup my phone recently with OOS 4.0.3 in order to have a clean phone for the most efficient use.
For my surprise, for the first time using the 3T my energy efficiency was very good, i managed to get 4,5h SOT with the first 50% because i had almost no drain when the screen was turned off.
I attached the screenshots.
Basically, i just flashed OOS 4.0.3 and the newest franco kernel and magisk for root. I didnt use greenify (which i usually do), just the strict standby option in the android settings.
So far so good, but now to the part i cant understand.
I installed gsam battery monitor and gave it root access, so i can have detailed battery information.
From that point, i experienced again the standby drain combined with wakelooks, as u can see in the screenshot starting around 60% of the battery.
So far i uninstalled the app, i used greenify, but i cant get back when i had no wakelocks.
Is it really because of Gsam Battery? How can get away the standby drain without setting up the phone completely new?
PS: I also deactivated some of the access rights of apps, especially for play services.
Is it possible that they regain the access by themselves or that google play services is draining the battery
Click to expand...
Click to collapse
I found 4.0.3 would get wakelocks from location service. I have installed firmware from OOS 3.5.4 and used Leandroid, since then I've had my old battery life back.
damiensturdy said:
I found 4.0.3 would get wakelocks from location service. I have installed firmware from OOS 3.5.4 and used Leandroid, since then I've had my old battery life back.
Click to expand...
Click to collapse
I like that app, but its only fully functional with SuperSU. Do u know if there is any similar app also working with Magisk?
LazerH said:
I like that app, but its only fully functional with SuperSU. Do u know if there is any similar app also working with Magisk?
Click to expand...
Click to collapse
Which app? Magisk?
Magisk has its own root now. Fyi
Navi44 said:
Which app? Magisk?
Magisk has its own root now. Fyi
Click to expand...
Click to collapse
I know, but the app still asks for root permission with SuperSU for all the foot options
LazerH said:
I like that app, but its only fully functional with SuperSU. Do u know if there is any similar app also working with Magisk?
Click to expand...
Click to collapse
Some parts of it only work with SuperSU, sure. The important bit that fixes the MRa big does unfortunately.
Not found a magisk equivalent, but I'm eager to find one!
I just recently got my 3T two weeks ago running OOS 4.0.3 and I also notice a lot of wakelocks, especially when on mobile data (3G/4G).
I am still tinkering to figure out what are the root causes for wakelocks in this case.
I suggest you install BetterBatteryStats from XDA, it does provide a lot of good info. GSAM is good too but I prefer BBS. You can grant it permissions to Battery_Stats if you are not rooted.
Here are my findings so far:
Google Services likes to access the GPS a lot, so I turned of Location History. This resulted in fewer wakelocks when the screen is off.
I have changed the GPS and set it to GPS Only so that it doesn't use the cell towers and WiFi to help determine a location. I am not sure if this makes a difference for wakelocks yet.
I know Nougat has doze, I am not sure how well it works...fortunately there is Aggressive Doze in the battery section of the settings. I have not tested this yet but this is something I will look into once I have determined all others aspects that may be causing wakelocks.
I do have the LED notification light enabled and I am using LightFlow to manage it. It works in conjunction with the built-in LED settings from OOS. This is fine, but I do believe this may cause wakelock issues.
Once again, in my experience, I get a lot of wakelocks when I am on mobile data compared to being on WiFi and I am not sure why there is a difference.

Question High battery drain

Hi guys. I am rocking CN version of Mi11 Ultra 12/256. It's currently on stable 12.0.10. i have allowed the application for notification and set up the system in my way to be usable by uninstalling most of the chinese ops that i was able to. Now, i can see that the battery drains abnormally it seems that the phone doesn't go to deep sleep. The second highest usage stats is android system.
Awesome phone!
It's a bit old but you can use Wakelock detector to see what is preventing your phone from going into deep sleep.
I'd also try to check the logcat to see if there is some system process working in the background continuously draining your battery.
I'm also looking at that graphic, it doesn't seem like Battery Drain is much at all. The phone has been active for 8 hours and it's around 80%? Doesn't seem bad to me.
Screen and Android System are the commonly the two most battery drainers if nothing else is cpu intensive.
Yes, but it was 8 hours overnight
bitpushr said:
I'm also looking at that graphic, it doesn't seem like Battery Drain is much at all. The phone has been active for 8 hours and it's around 80%? Doesn't seem bad to me.
Screen and Android System are the commonly the two most battery drainers if nothing else is cpu intensive.
Click to expand...
Click to collapse
Thanks for the input BTW, I'll definitely check wakelock. Maybe it's just me, but it seems it's draining in my eyes.
20% overnight is indeed too much... Might it had something to do with the debloat ? Did you uninstalled the Chinese aps via the getapp store or ADB ( disable or remove )?
After I upgraded to 12.0.13 my battery did drain a bit faster the very first couple of hours. ( background optimizations i Guess ).
Today I updated OTA to 12.5.
We'll see how this goes .
Good luck to you !
You probably already checked these settings but don't forget to disable AOD (if you don't need it), WiFI/Bluetooth scanning and WLAN Assistant too as thais will help reduce power consumption slightly.
I think its normal drain...the system drain is just there for example i debloated around 30 apps and its good
Last night with everything on as during the day ( Bluetooth, wifi, mobile data, gps, nfc, etc ) it drained only 4%.
For me it's a new record
Here is mine
Jhonxs said:
20% overnight is indeed too much... Might it had something to do with the debloat ? Did you uninstalled the Chinese aps via the getapp store or ADB ( disable or remove )?
After I upgraded to 12.0.13 my battery did drain a bit faster the very first couple of hours. ( background optimizations i Guess ).
Today I updated OTA to 12.5.
We'll see how this goes .
Good luck to you !
Click to expand...
Click to collapse
I uninstalled some chinese apps traditionally, so didn't use ADB download method.
Is the same that i did when i got my phone.
I went in the getapps store ( xiaomi store ) and uninstalled everything that i could there
Maibe you have some other software then installed , that isn't perfectly optimized.
My best advice is to go ahead and clear the full data for ALL the aps you are using ( including google playstore and the related services )
Also you can try to keeps the phone plugged during a night or two ( without touching it )
As i read somewhere, if the system sees that it has full battery and is plugged in after a while ( more than 20 min or so ) will start the optimizations of apps/general system ( otherwise it will try to do the optimizations during the day when it's in standby and above certain battery level )
I had some success doing this on my mi9 with xiaomi.eu, but in that case the rom version had a known battery drain
Do you have the miui optimizations disabled ( i left it enabled and haven't touched it ).
Have no issues with batter drain so far.
Good luck and keep us posted !
Did you ever fix the issue with the high battery drainage? I got my global unit last Friday (running 12.0.1) and I feel like I'm seeing a similar thing. Wanted to see what other users were averaging for screen on time. Is around 5hours of SOT with 120Hz and WQHD+ enabled decent?
panda24z said:
Did you ever fix the issue with the high battery drainage? I got my global unit last Friday (running 12.0.1) and I feel like I'm seeing a similar thing. Wanted to see what other users were averaging for screen on time. Is around 5hours of SOT with 120Hz and WQHD+ enabled decent?
Click to expand...
Click to collapse
I did, bu flashing EU rom 5hours SOT with both options turned on is decent. And recharging the bat takes minutes
panda24z said:
Did you ever fix the issue with the high battery drainage? I got my global unit last Friday (running 12.0.1) and I feel like I'm seeing a similar thing. Wanted to see what other users were averaging for screen on time. Is around 5hours of SOT with 120Hz and WQHD+ enabled decent?
Click to expand...
Click to collapse
Same.. i am on global with 12.0.6.
Batt drain is very bad, overnight, from 100% at 1am to 88% at 8am.
i have scheduled batt saver to turn on.
i am getting average 4 to 5+ SOT with 90hz and wqhd,
If it would happen to me i would check every app behavior closely ( battery app and maybe a third party battery monitor like accubattery that i'm using ), see if i find anything suspicious and if nothing is out of the ordinary i would do a complete reset, reinstall again and if this doesn't work, install xiaomi.eu stable at the very least .
But that's just me
on a side note, on my china unit when i was on the 12.0 the experience was not so great...
As soon as the 12.5 update came i could see a major improvement.
So maybe have a bit more patience until 12.5 will launch for global versions as well, all tough china will always be ahead in terms of improvement...which leads me to xiaomi.eu, again.
Jhonxs said:
If it would happen to me i would check every app behavior closely ( battery app and maybe a third party battery monitor like accubattery that i'm using ), see if i find anything suspicious and if nothing is out of the ordinary i would do a complete reset, reinstall again and if this doesn't work, install xiaomi.eu stable at the very least .
But that's just me
on a side note, on my china unit when i was on the 12.0 the experience was not so great...
As soon as the 12.5 update came i could see a major improvement.
So maybe have a bit more patience until 12.5 will launch for global versions as well, all tough china will always be ahead in terms of improvement...which leads me to xiaomi.eu, again.
Click to expand...
Click to collapse
i had the 12.5 CN rom on the mi 10 ultra, it was bad, notifications were delayed or not coming in at all until i opened the app, like whatsapp.
it was working fine in 12.0
that is why i decided to go back to global rom
I don't know about mi 10 ultra but i can tell you that for me on the mi 11 ultra, it's very good.
Good luck !

Categories

Resources