Database Info

[Q] Nexus S stock 2.3.4 and how to check keep-awake culprits

Hey guys,
N00b here.
I've read the n00b guide and also searched around in the forum. I did find a thread similar to mine however I couldn't really get any useful info out of it and maybe since then new tools are available to help me track my problem, so I post my question.
So... on to it...
My Nexus S is suddenly having high keep-awake times. About phone tells me a battery usage of 32% android system, followed by 21% Display. Android system has a keep awake time of 3h 51m and a CPU total of 7m 52s. All this over the course of 19 hours. I don't have a screenshot with me but it's clear that the phone is awake a lot when the screen is off.
Automatic updates are off.
Some days ago everything was fine. My google acount is only synching contacts and calendar and even that is turned off when I'm not at home. Even so, I saw a high usage of the keep-awake bar even when the screen was off.
I've installed some weather widgets and battery info widgets and the update cycles of weather applications are around 45 mins so I wouldn't see a reason for such a high period of keep-awake cycles.
Anyway, each phone is a phone, is there an application that can tell you what is keeping the phone awake ? I have installed Watchdog lite but it doesn't show anything abnormal. I've installed Spare Parts Plus but it can't show me the battery usage history because apparently stock 2.3.4 Gingerbread doesn't support it.
So now I'm stick with trying to disabled notifications on one app, remove its widget and see if it helps. If it doesn't.. go to the next. This is quite tedious work really.
Still the battery life is ok I guess... 50% after 19 hours however I haven't played around with it much but I would be happier to have a low keep-awake cycle for the Android System like I had some days ago.. makes me feel like everything is fine
Thanks for any hints guys!

Having the same issue as well.. I have my widgets and such to only check every 4-6 hours, but the awake time in the battery stats is nearly on all the time.
Keep awake time is 4 hours and 22 min, out of 12 hours of battery. I'm left with 42 % battery with only 1 hr 15 min on screen time (texts and such, no games).

Hmmm a memory drain of 60% in 1 hour is quite a bit heavy. I would suggest you to download Watchdog lite from the app store and use it's real time CPU analyzer to try and see what's consuming the most.
Once I had weatherbug going rogue. But then it showed up in the battery usage list with a high CPU usage and clicking on the item I could see a high awake time so I uninstalled it.
At the moment I've removed some of my widgets and so far it seems to be OK. However tonight I had some weird awake times again. I uninstalled Battery Info widget from the phone and I'll see if it all goes well tonight. Then I'll start to activate the other widgets I had deactivated before to see what happens.
Also I downloaded aCatLog from the app store. Pretty interesting tool... you can see what's going on in the logs. I see a few Java exceptions every now and then.. never a good sign as they might not be handled properly by the application code that threw them. I see evernote synch problems, a data traffic counter throwing exceptions and K-9 to have problems with idle connection reset by peer. And I often see the garbage collector working. But I assume all this is normal. Switching to the event log it's too much information to absorve. Nevertheless I haven't seen in any of those logs an explicit request or grant of a system wake lock.

mindwalkr said:
My Nexus S is suddenly having high keep-awake times.
Click to expand...
Click to collapse
Did you recently enable Latitude, by any chance?

Try top -m 5 -n 1 in terminal

fallenguru said:
Did you recently enable Latitude, by any chance?
Click to expand...
Click to collapse
No Latitude enabled

snandlal said:
Try top -m 5 -n 1 in terminal
Click to expand...
Click to collapse
Do I need to download Terminal Emulator from the market to do this ? Or do I need to download the Android SDK and connect to the device via USB ? I need to check out to do this, never done it before and this is my first android phone.. only a week old

Again this morning my awake time was on for quite a bit (I guess 1 hour). I got an extract of the main log...
Some things are curious, the following occurs more or less each half hour. I am signed out of gtalk why was the service trying to keep alive ?
06-08 06:10:03.656 W/GTalkService( 189): [GTalkConnection.18] doConnect: caught XMPPError connecting to mtalk.google.com:5228.: (502)
06-08 06:10:03.656 W/GTalkService( 189): -- caused by: java.net.SocketTimeoutException: Connection timed out
06-08 06:10:03.660 D/GTalkService( 189): [GTalkConnection.18] connectionClosed: connId=0, error=CONNECTION FAILED
This is also giving me trouble, I might uninstall my Traffic Counter app
06-08 06:42:30.710 W/System.err( 4015): java.io.FileNotFoundException: /data/data/com.carl.trafficcounter/app_pref_bytes_last/0_0_bytes_last (No such file or directory)
Evernote seems to have some issues as well sometimes
06-08 06:44:36.371 I/com.evernote.android.edam.TAndroidHttpClient( 5320): 25: Response received in: 126718ms
06-08 06:44:36.398 E/com.evernote.client.SyncService( 5320): Sync failed
06-08 06:44:36.398 E/com.evernote.client.SyncService( 5320): org.apache.thrift.transport.TTransportException: java.net.UnknownHostException: www.evernote.com
And that's all I could see. Everything else seems to be garbage collection WiFi activities and what not..

It seems that I've narrowed down Go Weather as what's making my Android System stay awake. I couldn't see anything really useful on logcat about this but empiric observations seem to confirm it.
If I remove the Go Weather widget and turn off it's background updates (hourly), then restart the phone... I see the Android System incrementing some 3-4 mins keep awake time per hour. If I set the widget again and turn on Go Weather's background updates, after an hour the Android System keep awake time goes up like 15-20 mins or so. If at this point I remove the Go Weather widget and turn off it's background updates, the Android System keep awake will still go up at the same rate as if the Widget was there. If I restart the phone without the widget, then the Android System keep awake seems to increase back to regular 3-4 mins per hour.
The funny thing is that according to Permission Dog, Go Weather doesn't even use the WAKE permission so I would rule it out as what was keeping Android System awake.

Android System was driving me crazy too. I figured out that when my WiFi was enabled, it would continually keep the phone awake when the screen was off. So I just toggle the wifi off when I'm not using it, and android system behaves now.
I'm curious as to what changed though, because when I was using stock 2.3.4 and CM7.0.3 I would leave wifi on all day, and android system didn't cause any battery issues.

Accellerometer Sleep App Showdown

Hello all,
There appears to be a few accelerometer based sleep apps that track your sleep cycles available. I always have issues waking up so the ability that these programs have to wake you up when you are in the "lightest phase" of sleep has been truly godsend. I have not been late to work once since I began using it (usually at least 3 days a week I'm late. It is truly life changing so far for me. But id like some feedback if there are other apps out there. or what personal experiences are. Id also like to know what most of you have for your "deep sleep ratio" to see how I stack up.
Sleep as Android - I am about 5 days from the trial version expiration of "Sleep as Android". So far I love the program and am highly considering purchasing it when the trial is up. I love that it can determine the best time to wake me up, and I have a nice graph of my movements through the night, another feature I like is that it record my noise. I have found that In the beginning I was a loud snorer it has apparently gone down by utilizing an eye mask that puts pressure on my nose as well. Just about everyday my % of deep sleep is falling into the 45-49% range with one bad night being 23%.
Sleep timer - I will be trying this program this weekend once my trial version of sleep as android is up. I want to test it over the weekend so I dont miss work or anything. will update my experience
Anyone have experience with other programs or the ones I mentioned?
Electric Sleep - Not tried yet
Smart Alarm Clock -Not tried yet
Gentle Alarm -Not tried yet

Suffering fron DSPS and Non24-h sleep/wake syndrome so it's crucial for me to monitor my sleep. Up to a year ago I was using SleepSense for WP6 when I reverted to Sleep as Android and was amazed by the features.
However recently I discovered Sleep Time which works in a similar way but is way more simple. Just enter the time, the offset, a couple of settings and you're good to go. Plus, the shake-to-snooze feature is awesome. I couldn't decide which one to use so I'm using them both on my two devices lol.

Sleep as android Trial ran out. I have been using sleep time I will post my thoughts on it below.
I like the charts given by sleep time a little more and it attempts to break your sleep into 3 segments (wake, light sleep, deep sleep). regarding the statistics, I am in the same range of sleep efficiency that I was with android so whether it is accurate or not remains to be seen but it is at least consistent. Another thing I can not vouch for on Sleep as android but the "algorithm" claim suggested by sleep time I believe is BS.
Theory, the app measures your movement throughout the night you set an alarm that is the "absolute latest" you can wake up. Then you tell the app either 10/20/30 minutes before the alarm you are willing for it to begin going off. Ideally the app monitors your sleep and as you come out of your deep sleep or in a light sleep phase the alarm is supposed to begin going off. This app is steadfast on ticking to the rules, you say 10 minutes with an alarm of 7 its gonna wake you at 650 everyday whether your in deep sleep or not. I notice my wakes are not as "refreshed" as SAAD was.
Bottom line, I like seeing the graph on this and it is very light on the options, but you cant expect much for free. Personally though, until they fix their setup and stop claiming it is an algorithm waking you up, I could just as easily just set my alarm to wake me up 10 minutes sooner.
Will begin trying another app over the weekend.

I haven't heard of these type programs, but now I'm intrigued (thanks for bringing them up in the forum).
As I understand, we have to allocate a window of time when the alarm might go off. So if I need to get up 5:00 absolute latest, the window might be 4:30 to 5:00.
a few questions:
1 - is 30 minutes a big enough window to make any difference?
2 - is this any better than just setting tradiaional alarm for 4:30 and hitting snooze until you're ready to get out of bed (or until it's 5:00, whichever comes first).
3 -you have to keep the phone in bed with you? How do you avoid rolling over on it?

electricpete1 said:
As I understand, we have to allocate a window of time when the alarm might go off. So if I need to get up 5:00 absolute latest, the window might be 4:30 to 5:00.
Click to expand...
Click to collapse
Yup.
electricpete1 said:
1 - is 30 minutes a big enough window to make any difference?
Click to expand...
Click to collapse
Short answer, yes. Provided that the app actually works as intended and does not just hit the alarm at the earliest time possible!
Long answer, this has to do with the duration of the sleep cycles, which last about 60 to 90 minutes on average, depending on the person. Those cycles consist of five sleep stages, stage 1, stage 2 (light sleep), stage 3 and 4 (deep sleep) and stage 5 (or REM). In general your sleep goes like this: [stage 1, 2, 3, 4, 3, 2, REM] - [2, 3, 4, 3, 2, REM] - [2, 3, 4, 3, 2, REM] etc.
The important thing is that during stage 2 and REM its easier to wake up, and both those stages last more than the rest, taking up to 65-75% of the whole sleep cycle. So, 30 minutes should be an ideal offset. No matter what time you set the alarm, it's almost certain that 30 minutes before that you will eventually enter light sleep or REM sleep.
That's how these kind of apps work, they're supposed to detect the sleep stage you're on using the accelerometer (based on any movements) and wake you up only during "light" sleep.
electricpete1 said:
2 - is this any better than just setting tradiaional alarm for 4:30 and hitting snooze until you're ready to get out of bed (or until it's 5:00, whichever comes first).
Click to expand...
Click to collapse
Theoretically, it is. If you just set the alarm earlier and it rings while you're in deep sleep, it could be a lot harder to wake up plus you will probably still feel tired and drowsy, possibly for the rest of the day. If, however, the alarm rings while you're in light sleep or REM sleep, it will be easier for you to wake up and you will definitely feel more refreshed.
I've woken up during deep sleep after 8:30 hours and felt awful for the rest of the day. I've woken up during light sleep after just three hours of sleep and had enough energy to pull an all-nigher the next night. It all comes down to general sleep hygiene of course but the actual sleep stage on which you wake up can and will have an effect on the quality of your sleep.
electricpete1 said:
3 -you have to keep the phone in bed with you? How do you avoid rolling over on it?
Click to expand...
Click to collapse
I usually keep it right next to my pillow (flight mode on), in it's case and connected to the charger.

Is it bad to set a really low screen timeout?

Is it bad for the display to set a really low screen timeout? I always have this feeling that turning on and off the display on a frequent basis is bad for the hardware (display) and will burnout. I like to check my Twitter whenever I'm not doing something, so sometimes it can be every 5 minutes in an hour. Let's put it this way: if I spam press the lock button at 4 second intervals repeatedly for a long duration, would it be bad for the screen? (Just to put things into perspective, since every 5 minutes in an hour is a lot). I know setting the timeout on the display low can save battery life, but is a really low "timeout" bad for the display?

mindstormer said:
Is it bad for the display to set a really low screen timeout? I always have this feeling that turning on and off the display on a frequent basis is bad for the hardware (display) and will burnout. I like to check my Twitter whenever I'm not doing something, so sometimes it can be every 5 minutes in an hour. Let's put it this way: if I spam press the lock button at 4 second intervals repeatedly for a long duration, would it be bad for the screen? (Just to put things into perspective, since every 5 minutes in an hour is a lot). I know setting the timeout on the display low can save battery life, but is a really low "timeout" bad for the display?
Click to expand...
Click to collapse
Now that u mention it I could see how it could be bad... But I don't think its gonna be too hard on the device. I usually use a screen timeout of one minute.
Press thanks if I've helped u!
Sent from my GT-P5110 using XDA Premium HD app

no i don't think it will damage anything on you device, but it is better to keep your timeout as 1 or 2 minutes because i think that a timeout as low as 15 seconds
can damage the power button as it will be used up continuously after every 15 seconds if you forgot to keep the screen awake. STILL, i will give it a thought and
will let you know tomorrow

Still waiting for your response.

isaahiln
as for the led lighting, apparently cycling them off and on does not reduce lifespan, although heat does so it may help with that
that doesn't speak for video display circuitry, or (as previously mentioned) physical switches lifetime

Stop wifi drain on standbyI

I just got an LG V20 which is good on battery when in use but sucks when not in use. The culprit is always wifi. I just discovered the root cause is Location services that is using wifi to get locations even when wifi is off.
To stop this, go to settings->location->scanning.
Uncheck wifi scanning. For good measure, uncheck bluetooth scanning.
Go to wifi menu ->advanced-> keep wifi on when screen is off
Change to never or "only when plugged in"

Hi,
thanks for your helpful tips..
So out of the 3 tips you have:
1. Uncheck wifi scanning
2. Uncheck bluetooth scanning
3. Turn wifi off when screen is off
Any idea how much does each option save (if you've quantified)?
I'm happy to follow points 1 and 2. I'd only do 3 if it really helps a lot, because most apps would use data if wifi isn't available to periodically phone home.

I have always been dissappointed with my V20 standby time.. I had all of these settings on.. so i'll see how she does now they are off.
Thanks!

My standby time is from 0-4% over 8-9hrs. I really cant complain.... but the phone is facing down.

I wasn't aware of the wifi location scanning, and the bluetooth scanning. Giving it a try as my standby time has been horrible lately.

I am also facing severe battery drain on my LG V20. Battery easily drains by 5-10% per hour even when the phone is lying idle with screen off. Major culprits are 'Phone Idle', 'Android System' and 'Android OS'.

coolravsun said:
I am also facing severe battery drain on my LG V20. Battery easily drains by 5-10% per hour even when the phone is lying idle with screen off. Major culprits are 'Phone Idle', 'Android System' and 'Android OS'.
Click to expand...
Click to collapse
Try what is mentioned here
Post your screen shots here and tag or quote this post

As a side note, I've found that using wifi and cell data to help location services causes maps to scan these options and slow down (maps keeps saying every 5 to 15 seconds "searching"). By using gps only, the maps app is faster and less battery drain.
Obviously if you are indoors you need the help of wifi or cell data. But in the car or outside it is unnessary.

Thanks for your tips it's very good for my life battery. :good:

One Twelve said:
Try what is mentioned here
Post your screen shots here and tag or quote this post
Click to expand...
Click to collapse
I tried as suggested in the post you shared. Once the Bugreport was generated, I got a notification to click it to share. But, upon clicking nothing happened. I did not get anything (no pop-up, no options) further to share it. I tried thrice but, every time same end result.
How can I access the Bugreports generated on the phone?

coolravsun said:
I tried as suggested in the post you shared. Once the Bugreport was generated, I got a notification to click it to share. But, upon clicking nothing happened. I did not get anything (no pop-up, no options) further to share it. I tried thrice but, every time same end result.
How can I access the Bugreports generated on the phone?
Click to expand...
Click to collapse
Ah, seems like the obvious question but you can't.
I've found the most reliable way is to email them and then download them

One Twelve said:
Ah, seems like the obvious question but you can't.
I've found the most reliable way is to email them and then download them
Click to expand...
Click to collapse
Finally! I was able to share and download the bug report. I am attaching the Historian Graph and Aggregated Stats screenshots here. Please let me know what you find.

coolravsun said:
Finally! I was able to share and download the bug report. I am attaching the Historian Graph and Aggregated Stats screenshots here. Please let me know what you find.
Click to expand...
Click to collapse
- see the cpu running, userspace wakelock & screen on lines. They seem to match. Screen is on, cpu working with userspace wakelock. Close to 7pm the screen is off but the cpu is running, because you were listening to audio. I don't see a problem here. Looks normal
- you screen off discharge rate is 2.56%/h which seems a bit high. If you were streaming audio this might add to it. Do you have the second screen on when the main screen is off ?
- somewhere around 12pm you are using data for about an hour. Mobile Signal strength isn't very good, mostly yellow. What i don't understand is why your wifi is also on ? and this is in an area where wifi signal is bad. Both of these will add to drain. And in two hours your battery dropped from 70 to 40
- little after 1pm you're on wifi for a couple of hours but the signal is weak
- around 5pm you're back on data streaming audio and battery takes a nose dive here. Down 30% in like an hour. Were you moving ?
- then you charge up to 85%, doze kicks in which is good, if there was app drain doze would not come on, for the next 5h without use, you lose about 5%
- the part i don't understand is between 1am & 6am, battery drops 10% yet full doze (blue) is on. So there is some activity going on there. What ? sync ? updates ?
Not sure about the aggregated stats as you've recharged up and run down fr a second cycle so it could be your off screen drain is twice as high because of that
charge up again, go through your day and save log when you're at 5% and lets see the two screenshots from just one charge cycle

One Twelve said:
- see the cpu running, userspace wakelock & screen on lines. They seem to match. Screen is on, cpu working with userspace wakelock. Close to 7pm the screen is off but the cpu is running, because you were listening to audio. I don't see a problem here. Looks normal
- you screen off discharge rate is 2.56%/h which seems a bit high. If you were streaming audio this might add to it. Do you have the second screen on when the main screen is off ?
- somewhere around 12pm you are using data for about an hour. Mobile Signal strength isn't very good, mostly yellow. What i don't understand is why your wifi is also on ? and this is in an area where wifi signal is bad. Both of these will add to drain. And in two hours your battery dropped from 70 to 40
- little after 1pm you're on wifi for a couple of hours but the signal is weak
- around 5pm you're back on data streaming audio and battery takes a nose dive here. Down 30% in like an hour. Were you moving ?
- then you charge up to 85%, doze kicks in which is good, if there was app drain doze would not come on, for the next 5h without use, you lose about 5%
- the part i don't understand is between 1am & 6am, battery drops 10% yet full doze (blue) is on. So there is some activity going on there. What ? sync ? updates ?
Not sure about the aggregated stats as you've recharged up and run down fr a second cycle so it could be your off screen drain is twice as high because of that
charge up again, go through your day and save log when you're at 5% and lets see the two screenshots from just one charge cycle
Click to expand...
Click to collapse
Thanks a lot! Please find my answers in sequence.
- I listen to music while going to work. But, that is, till 8:30 AM only. Yes, I have 2nd screen ON when the Main display is OFF.
- I watch stored videos during lunch (12-1pm) for around an hour but it shouldn't be using data as I am playing stored videos.
- Around 5 pm, I leave for home. Again while going home I listen to music for half an hour.
- I have no Idea of what is happening during Night because I just leave it and don't use it until morning. In fact, I have scheduled the 2nd screen to be off between 11 pm and 6 am
I will try to run a proper cycle as you have suggested and will recapture the logs.
I understand the battery dropping while I am using the phone (listening to music/watching videos/browsing/anything else). What I don't get is the battery dropping insanely when I am not using it. For example, once I reach the office, I stop the music, kill the music player and just keep the phone aside. After 1-2 hours, as I check my phone I find battery dropped by 10% or so! It's the battery drain while my phone is just lying idle that is troubling.
Also, I have noticed that once I charge my phone and then leave it (Not using it) the battery drain is minimal like 1% per hour. But, once I run some app (music/browsing etc) for a little while and then leave the phone, the idle battery drain is pretty high.

coolravsun said:
Thanks a lot! Please find my answers in sequence.
- I listen to music while going to work. But, that is, till 8:30 AM only. Yes, I have 2nd screen ON when the Main display is OFF.
- I watch stored videos during lunch (12-1pm) for around an hour but it shouldn't be using data as I am playing stored videos.
- Around 5 pm, I leave for home. Again while going home I listen to music for half an hour.
- I have no Idea of what is happening during Night because I just leave it and don't use it until morning. In fact, I have scheduled the 2nd screen to be off between 11 pm and 6 am
I will try to run a proper cycle as you have suggested and will recapture the logs.
I understand the battery dropping while I am using the phone (listening to music/watching videos/browsing/anything else). What I don't get is the battery dropping insanely when I am not using it. For example, once I reach the office, I stop the music, kill the music player and just keep the phone aside. After 1-2 hours, as I check my phone I find battery dropped by 10% or so! It's the battery drain while my phone is just lying idle that is troubling.
Also, I have noticed that once I charge my phone and then leave it (Not using it) the battery drain is minimal like 1% per hour. But, once I run some app (music/browsing etc) for a little while and then leave the phone, the idle battery drain is pretty high.
Click to expand...
Click to collapse
Same sequence
- When you have the second screen on, is the phone facing up or down. What i notice with that second screen is it ignores any brightness settings. If the phone is face up and pointed at a light, the second screen becomes very bright. If its facing away from the light then it dims. Depending on how your phone faces you will either have more or less drain here, without doing anything and phone just sitting there. Typical overhead with second screen on and normal brightness ie not too bright is around 1% per hour. This could be adding to your off screen drain. Why not try a couple of cycles. One with second screen off and another with second screen on. Just to see how your off screen drain rate is like.
You say you listen to music only upto 8:30AM, take a look at the audio line. Can you see audio triggering ? there's little blips there after 8:30AM which continues till 5:30PM where its solid. This is your ride back where you listen for an hour. The 5:30 audio is ok but the blips in between are not leaving aside lunch video. Each time there is an audio blip there is a wakelock. Pay attention to the duration of the audio blip, if its a few seconds it could just be notification, but if its longer, does it correspond to your use.
Now look at the top app line, try to find which apps are running when audio triggers. To do that hover over the top app line which coincides with audio when you were not listening to audio. You will see a popup screen with a list of apps. Or check History Stats - TopApplicationSummary for a table, screen shot that and post
Do you use a lot of widgets that update in the background ?
- something was using mobile data when you were watching stored videos at lunch. Take a look at the'mobile radio active' line and you see activity there around lunch. Your wifi however is off and not running. If there were any apps running they were using mobile data, this is extra drain
- take a look at the line that says 'foreground process'. it's pretty solid right through both your runs. The only time it stops is when you recharge. This is a hint something is up. If you hover above it what does the popup say ? try moving along the line and observe whether the information changes
There shouldn't a foreground process running when you're not using the phone. Maybe if you can screen shot, the table that displays under History Stats - Foreground Process Summary
Scroll down and under the graph and on the left you will see three headers with twisties, System stats, History stats & App Stats
Hold on to your bug report files and they will be useful to verify if any changes you make take effect or not
- 1% per hour corresponds to second screen on, with it off your drain would be halved. However having drain after leaving a music or browsing app isn't good. It means a wakelock was caused and its not releasing so doze can't kick in. So battery will drain. If the phone is shaking, say in your pocket as you walk around, full doze won't kick in either
Which social media apps do you use.
Stock launcher or other if so which

I've found just buying a new battery off of ebay for $10 is the the easiest way to gain back that extra hour of on screen time and extend stand by. That's why the phone was made with a removable battery. I have 3 of them and don't need to touch a charger for a week. and when the time comes to charge the batteries, just put them in the charging docks and done.

Phone(s) still hot when turned off. Also, wicked power draw.

G'day,
I've had some odd issues with two consecutive Xiaomi phones, and I'm hoping someone here can shed some light on it for me.
With both my Mi Note 2, and now my current Mi Mix 3, after less than a year of owning each one (respectively), out of nowhere, the battery life drops through the floor, the phone gets really hot, and most oddly, I got wicked battery drop while the phone is off (e.g. I turned the phone completely off at 77%, and about an hour later, I turn the phone back on and it's at 43%).
On both phones, I've tried a factory reset, but it didn't work. It was, for all intents and purposes, fecked. At the moment, I'm waiting for the 15 day countdown for my Mi Mix 3 bootloader to be unlocked so I can try flashing the EU MiUI ROM and see if that helps, but that's still a hell of a long time to wait with a phone that idles at 50+° C and has a battery life of about 3 hours with minimal SoT.
I've installed BetterBatteryStats (using ADB to provide permissions), CPU-Z, CPU Monitor and Ampere to see if I could get some more information. I found a few things:
1. Somehow, with mobile data and WiFi enabled, the system was drawing SO MUCH power (reported by Ampere) that it literally wouldn't charge while plugged into a 2A wall port. It was drawing like 1300mA when it wasn't plugged in, and when it was, it was STILL drawing about 130mA, meaning no matter what, while the phone was on, I was losing battery.
2. BBS reported the biggest battery killer was under the 'Alarms' tab, caused by Android, which were "Intent: *job.delay*" and "Intent: *job.deadline*". I have literally no idea what these are, what's causing them, or how to stop it triggering.
3. I've done a full factory reset. The first hint that something was wrong was when I noticed that the phone wasn't charging when it was plugged in and turned on. I did the full factory reset, didn't help.
I'm currently running Global MiUI 11.0.4.0, Android 9.
Does anyone have any ideas? I haven't manually updated anything, I'm not particularly rough with the phone, but for two phones in a row, this has come straight out of nowhere. It's a shame, because the Mi Mix 3 has spoiled me with it's 100% screen real estate (no hole-punch, no teardrop for front camera), but I think my next phone is gonna go with something else.
Cheers.

Update: I've taken a squizz at the Google Battery Historian and basically, I have no feckin' idea.
The best I can get out of it is "Yep, something in the labyrinthine generic 'Android' system is causing it, but good luck narrowing it down or stopping it."
That being said, I've found that this Partial Wakelock is triggered fairly often (1-6 times per minute, give or take): IntentOp:.common.broadcast.BackgroundBroadcastReceiverSupport$GmsReceiverIntentOperation
I have no idea what the hell it is or does, and the only information I can find about it is from developers asking questions where it just happens to be part of their codebase, or a breakdown of how the WakeBlock app works.
It's getting woken up about every minute or so (usually more than once a minute). However, the wakelocks appear to be part of the core Google/Android systems that can't be individually disabled.
I'm still feckin' confused.

Overloke said:
Update: I've taken a squizz at the Google Battery Historian and basically, I have no feckin' idea.
The best I can get out of it is "Yep, something in the labyrinthine generic 'Android' system is causing it, but good luck narrowing it down or stopping it."
That being said, I've found that this Partial Wakelock is triggered fairly often (1-6 times per minute, give or take): IntentOp:.common.broadcast.BackgroundBroadcastReceiverSupport$GmsReceiverIntentOperation
I have no idea what the hell it is or does, and the only information I can find about it is from developers asking questions where it just happens to be part of their codebase, or a breakdown of how the WakeBlock app works.
It's getting woken up about every minute or so (usually more than once a minute). However, the wakelocks appear to be part of the core Google/Android systems that can't be individually disabled.
I'm still feckin' confused.
Click to expand...
Click to collapse
I think it's an issue with your network operator

XDRdaniel said:
I think it's an issue with your network operator
Click to expand...
Click to collapse
Any ideas as to how I'd further troubleshoot? I've gone into *#*#4636#*#* and changed the sort of signal it looks for, but it doesn't appear to have fixed anything.

In case anyone is interested, I've attached on of my Bugreports (from running adb bugreport), which can be viewed through Google Battery Historian.
I'm not saying there's a cash prize for anyone who can tell me what is happening and why, but I'm also not saying that there isn't.

So, I think we have our culprit (maybe).
I have attached several screenshots from a Battery Historian I took after having my phone on all day. The total phone on time was about 4-5 hours with, no joke, maybe 10 seconds of screen on time. Let's go through this absolute bullshittery together, shall we?
Battery - Full Time: The full length of time captured by the Battery Historian/bugreport command. It's in Zulu Time (GMT+0) and I'm in Australia (GMT+10), so the line starts going up at 5PM last night, which is more or less when I plugged it in to charge. You can see, while 'off', it took 16 hours to charge to 100%, and this was from a 'cold boot' (phone is completely dead), so it didn't have any information about what had been running, etc.
Battery - Discharge: The five or so hours time in which the entire battery discharged, starting from when I woke up in the morning and got ready for work. In the Screen row, you can see the small, three-to-four second windows throughout the day that I turned the phone on to check the battery. For almost the entirety of the time, the screen was off. You can see where the line next to Phone State goes from black to navy blue. This indicates that the phone has been put into Airplane Mode - you can see this is also where everything relating to network connectivity or mobile strength completely disappears. You can also see that App Processor Wakeup completely dies here - that means that actual installed apps (including GOOGLE_SERVICES and Xiaomi's preinstalled Facebook app stop sending commands to wake the CPU.
Battery - Cause: At least once a minute, usually more, two things fire that keep the CPU running - Abort:Wakeup IRQ detected during suspend: 999 msoc-delta and Abort:Wakeup IRQ detected during suspend: 663 qpnp_rtc_alarm. I have no feckin' idea what either of those are, and Googling results in either developer guides or threads that lead nowhere. If anyone knows what they are, for the love of God let me know.
Battery - Foreground Processes: While the phone was off, with every app closed, in Airplane Mode, we can see that there are still four apps that are somehow in the foreground: com.miui.mishare.connectivity (odd, since there's no connection), com.miui.securitycenter (which I tried disabling through ADB last night, and it stopped my phone from booting. Oops), com.miui.notification, and com.android.providers.contacts (which disappeared shortly after entering Airplane Mode).
Battery - Video: You can see here, for the ENTIRETY of the time that the phone was turned on, this odd Video row was enabled. There is no other information about it - what causes it, where it's coming from, what 'Video' means, anything.
Battery - 7 Second Slice: This is just a close-up of a seven-second period of time, wherein the above 999 msoc-delta and 663 qpnp_rtc_alarm kept the CPU running six times within 7 seconds. Not a lot on its own, perhaps, but over the course of hours, it clearly causes issues.
I've also attached the latest bugreport where I took these screenshots from if anyone wants to try and make sense of it.

--

This looks to me like an hardware issue more than anything, what is the idle state of the cpu?

Overloke said:
So, I think we have our culprit (maybe).
I have attached several screenshots from a Battery Historian I took after having my phone on all day. The total phone on time was about 4-5 hours with, no joke, maybe 10 seconds of screen on time. Let's go through this absolute bullshittery together, shall we?
Battery - Full Time: The full length of time captured by the Battery Historian/bugreport command. It's in Zulu Time (GMT+0) and I'm in Australia (GMT+10), so the line starts going up at 5PM last night, which is more or less when I plugged it in to charge. You can see, while 'off', it took 16 hours to charge to 100%, and this was from a 'cold boot' (phone is completely dead), so it didn't have any information about what had been running, etc.
Battery - Discharge: The five or so hours time in which the entire battery discharged, starting from when I woke up in the morning and got ready for work. In the Screen row, you can see the small, three-to-four second windows throughout the day that I turned the phone on to check the battery. For almost the entirety of the time, the screen was off. You can see where the line next to Phone State goes from black to navy blue. This indicates that the phone has been put into Airplane Mode - you can see this is also where everything relating to network connectivity or mobile strength completely disappears. You can also see that App Processor Wakeup completely dies here - that means that actual installed apps (including GOOGLE_SERVICES and Xiaomi's preinstalled Facebook app stop sending commands to wake the CPU.
Battery - Cause: At least once a minute, usually more, two things fire that keep the CPU running - Abort:Wakeup IRQ detected during suspend: 999 msoc-delta and Abort:Wakeup IRQ detected during suspend: 663 qpnp_rtc_alarm. I have no feckin' idea what either of those are, and Googling results in either developer guides or threads that lead nowhere. If anyone knows what they are, for the love of God let me know.
Battery - Foreground Processes: While the phone was off, with every app closed, in Airplane Mode, we can see that there are still four apps that are somehow in the foreground: com.miui.mishare.connectivity (odd, since there's no connection), com.miui.securitycenter (which I tried disabling through ADB last night, and it stopped my phone from booting. Oops), com.miui.notification, and com.android.providers.contacts (which disappeared shortly after entering Airplane Mode).
Battery - Video: You can see here, for the ENTIRETY of the time that the phone was turned on, this odd Video row was enabled. There is no other information about it - what causes it, where it's coming from, what 'Video' means, anything.
Battery - 7 Second Slice: This is just a close-up of a seven-second period of time, wherein the above 999 msoc-delta and 663 qpnp_rtc_alarm kept the CPU running six times within 7 seconds. Not a lot on its own, perhaps, but over the course of hours, it clearly causes issues.
I've also attached the latest bugreport where I took these screenshots from if anyone wants to try and make sense of it.
Click to expand...
Click to collapse
Same problem. Any solution?