Related
TL: DR - Use Rescan Media, win.
So, I think that I've finally found the source of my constant stress regarding the battery life of my beautiful Samsung Captivate SGH-i897.
I know that a good majority of you have just rolled your eyes in disbelief, or just thought to yourself, "Great....another one of these threads".
If it helps one person get their battery life under control, then roll away.
I've had the phone for about 2-3 months and I've been active on these boards since a few days after getting it.
I've recalibrated, done the on / off / on / off trick, battery stats delete, deleted battery info from CWM, tried a second battery, used battery monitors on the phone, turned off wi-fi, turned off auto-synch, turned off bluetooth, lowered display brightness, and everything else I could think of to conserve juice.
Yesterday afternoon, I downloaded OSMonitor from the market in an effort to try another app in a long line of failures.
Nothing seemed out of the ordinary so I was going to give up hope.
While installed, I had clicked on the box to monitor the app in the notification bar.
I noticed that I would have times where the CPU was being maxed but nothing strange was being reported in OSMonitor.
And then it hit me.....
The entire time I'm watching the OSMonitor, I'm being distracted by the media scanner.
It's running over and over and over and over and over.
When the screen shuts off after 30 seconds, it comes back on, the media scanner runs.
When I update something from the market, the media scanner runs.
When I close a program, the media scanner runs.
It is running constantly and maxing my CPU to 100%.
It finishes fairly quickly, (I have 9.4GB / 13GB available on internal and hardly anything used on my 4GB external SD card) but it just KEEPS....ON.....RUNNING.
I do a quick search, stumble upon the .nomedia file trick from XDA archives, and VOILA ! ! ! !
I'm losing about only one half of one percent per hour while it sits on standby, where I would sometimes lose 10-11% per hour, when the phone isn't even being used by me.
I went to bed last night with 48% at around 3:30am.
It is approx. 11 hours later right now.
I've made approx. 8-10 calls, checked my email a few dozen times, and mostly just let the phone sit.
I'm sitting at 39%.
Previous to doing this, I would have lost that amount in one hour.
So, for anyone who has a phone that is losing battery life like it's going out of style, I highly recommend doing the .nomedia fix.
I did mine using ES Explorer and Super Manager.
Go into your root folder and add a file named .nomedia, then go into your external SD folder and do the exact same thing.
If you do not want to do it this way, you can go the easy route and add a program called Rescan Media that does it for you.
(link supplied)
Hopefully this helps at least one lost soul, I'm so happy to see my phone behave more along the lines of what my expectations were and not have to be fully charged 2 times per day.
For the record, I've tried the following ROM's for the Cappy:
Perception
Phoenix
Assonance
Darkytt3r's port of Darky's ROM
Stock ROM (ODIN Rooted)
Cognition
And the following kernels:
Glitterballs
SpeedMod
SetiroN
Xcalibur
Will this not cause the media scanner to not pick up anything at all then?
IE no custom ringtones/msg alerts, nothing displayed in gallery, playlists wont work with the music player....
Or will it run media scanner selectively instead of all the time?
The only time I notice media scanner running is after rebooting the phone... yet I'm still only getting about 9-10 hours on a full charge with very conservative use.
evoic said:
TL: DR - Use Rescan Media, win.
So, I think that I've finally found the source of my constant stress regarding the battery life of my beautiful Samsung Captivate SGH-i897.
I know that a good majority of you have just rolled your eyes in disbelief, or just thought to yourself, "Great....another one of these threads".
If it helps one person get their battery life under control, then roll away.
I've had the phone for about 2-3 months and I've been active on these boards since a few days after getting it.
I've recalibrated, done the on / off / on / off trick, battery stats delete, deleted battery info from CWM, tried a second battery, used battery monitors on the phone, turned off wi-fi, turned off auto-synch, turned off bluetooth, lowered display brightness, and everything else I could think of to conserve juice.
Yesterday afternoon, I downloaded OSMonitor from the market in an effort to try another app in a long line of failures.
Nothing seemed out of the ordinary so I was going to give up hope.
While installed, I had clicked on the box to monitor the app in the notification bar.
I noticed that I would have times where the CPU was being maxed but nothing strange was being reported in OSMonitor.
And then it hit me.....
The entire time I'm watching the OSMonitor, I'm being distracted by the media scanner.
It's running over and over and over and over and over.
When the screen shuts off after 30 seconds, it comes back on, the media scanner runs.
When I update something from the market, the media scanner runs.
When I close a program, the media scanner runs.
It is running constantly and maxing my CPU to 100%.
It finishes fairly quickly, (I have 9.4GB / 13GB available on internal and hardly anything used on my 4GB external SD card) but it just KEEPS....ON.....RUNNING.
I do a quick search, stumble upon the .nomedia file trick from XDA archives, and VOILA ! ! ! !
I'm losing about only one half of one percent per hour while it sits on standby, where I would sometimes lose 10-11% per hour, when the phone isn't even being used by me.
I went to bed last night with 48% at around 3:30am.
It is approx. 11 hours later right now.
I've made approx. 8-10 calls, checked my email a few dozen times, and mostly just let the phone sit.
I'm sitting at 39%.
Previous to doing this, I would have lost that amount in one hour.
So, for anyone who has a phone that is losing battery life like it's going out of style, I highly recommend doing the .nomedia fix.
I did mine using ES Explorer and Super Manager.
Go into your root folder and add a file named .nomedia, then go into your external SD folder and do the exact same thing.
If you do not want to do it this way, you can go the easy route and add a program called Rescan Media that does it for you.
(link supplied)
Hopefully this helps at least one lost soul, I'm so happy to see my phone behave more along the lines of what my expectations were and not have to be fully charged 2 times per day.
For the record, I've tried the following ROM's for the Cappy:
Perception
Phoenix
Assonance
Darkytt3r's port of Darky's ROM
Stock ROM (ODIN Rooted)
Cognition
And the following kernels:
Glitterballs
SpeedMod
SetiroN
Xcalibur
Click to expand...
Click to collapse
So... exactly what did you do to solve the problem? can you describe how do you do the .nomedia fix?? I have exactly the same issue..
Hm, I haven't experienced that bad of a battery drain, but I installed the market app even though it said 2.2... maybe this will make my battery life better! Thanks for the tip.
It's running over and over and over and over and over.
When the screen shuts off after 30 seconds, it comes back on, the media scanner runs.
When I update something from the market, the media scanner runs.
When I close a program, the media scanner runs.
It is running constantly and maxing my CPU to 100%.
It finishes fairly quickly, (I have 9.4GB / 13GB available on internal and hardly anything used on my 4GB external SD card) but it just KEEPS....ON.....RUNNING.
Click to expand...
Click to collapse
When you say the media scanner runs when doing all of these actions, does the Media Scanning icon show in the notification bar? If so, then I think it's just an issue with your phone cause I don't think that happens with anyone else's phone.
Unless you are saying that the media scanner runs in the background secretly after every action and there is no icon in the notification bar or anything? If so, I think you can be on to something.
GTIVRon said:
Will this not cause the media scanner to not pick up anything at all then?
IE no custom ringtones/msg alerts, nothing displayed in gallery, playlists wont work with the music player....
Or will it run media scanner selectively instead of all the time?
The only time I notice media scanner running is after rebooting the phone... yet I'm still only getting about 9-10 hours on a full charge with very conservative use.
Click to expand...
Click to collapse
You could just run Media Scanner manually. SwitchPro even gives you a button to initiate it. The only time Media Scanner runs automatically for me is when the phone boots (and probably some other infrequent times that I can't remember) so disabling automatic media scanning isn't much of a loss at all for me.
GTIVRon said:
Will this not cause the media scanner to not pick up anything at all then?
IE no custom ringtones/msg alerts, nothing displayed in gallery, playlists wont work with the music player....
Or will it run media scanner selectively instead of all the time?
Click to expand...
Click to collapse
I'm curious of the same thing. I've only seen the media scanner run when I restart or disconnect my SD card from my computer.
trekie86 said:
I'm curious of the same thing. I've only seen the media scanner run when I restart or disconnect my SD card from my computer.
Click to expand...
Click to collapse
trying to get it working... ill report wassup after...
minlee85 said:
evoic said:
TL: DR - Use Rescan Media, win.
...
I did mine using ES Explorer and Super Manager.
Go into your root folder and add a file named .nomedia, then go into your external SD folder and do the exact same thing.
If you do not want to do it this way, you can go the easy route and add a program called Rescan Media that does it for you.
(link supplied)
...
Click to expand...
Click to collapse
So... exactly what did you do to solve the problem? can you describe how do you do the .nomedia fix?? I have exactly the same issue..
Click to expand...
Click to collapse
I'll be nice... see the quoted paragraph that was in your quote?
Minlee, no need to quote an entire post, especially when you aren't responding to something in it directly.
As others have said, I only ever see Media Scanning in the Notification bar when I do a reboot. If it runs at other times it is transparent to the phone.
This is probably an issue specific to myself and a few others.
Someone above asked me if I saw a lot of activity in the background or if I actually saw the "Media Scanning" icon pop up in my notification bar.
The answer is that I saw the icon pop up and then watched it scan, over and over and over, all day long, dozens....if not hundreds of times.
That little fix, coupled with the battery calibration that I've done a few times, along with getting rid of some of the resource hogs that run in the background (Do I reeeeally need Google Maps to run 23 hours out of the day???) has given my Captivate new life.
evoic said:
This is probably an issue specific to myself and a few others.
Someone above asked me if I saw a lot of activity in the background or if I actually saw the "Media Scanning" icon pop up in my notification bar.
The answer is that I saw the icon pop up and then watched it scan, over and over and over, all day long, dozens....if not hundreds of times.
Click to expand...
Click to collapse
Yeah, I've never seen that kind of behavior. I only see the scanning activity when I first boot and when I do something like take a picture or a screen shot.
Hello XDA,
I've recently purchased a samsung infuse and there were a few things standing out that i was wondering about. When i bought the phone, it had already been unlocked + rooted + flashed with S7, it should be running on the default kernal that came with S7. Afterwards, i installed dynamicRAM's tweaks in the development section.
1) Lock screen lag.
Wondering if anybody else is having this problem. When i hit the unlock button, theres a small lag time present before the screen activates, subsequently, when swiping my finger across to unlock the screen, theres a lag time before the imagine/slider/what have you responds. At first, i thought this had no functional problem and that it was just a little ugly. Until i received a phone call and in my attempt to answer it, the slider didn't respond. I wonder if this is perhaps a kernal problem?
2) If it is a kernal problem, is it compatible to try flashing the infusion 1.1 kernal overtop the default S7 kernal (Granted that the phone itself is first backed up with tibu and a NANDroid backup performed). Would this help the above problem?
3) The seller had the phone overclocked to 1.6 ghz with setCPU which isn't a large problem as its an ondemand clocking. however, the battery usage seems to be lower than expected? Note that i do not use data plan so thats turned off, wifi is turned off, but i like having the brightness as full (i acknowledge this eats up a lot of the battery).
Leaving the phone on my bedside table for sleep, it depletes 6% over the course of my 6 hour sleep. 1% an hour seems pretty fair. However yesterday, i unplugged from 100% at 2pm and used it till the following day 10 am. During this period, it depleted to 49%. I used aldiko for my book for an hour before bed. Sent a total of 14 texts, received 18. No music player was used, rest of the time the phone was essentially idle. I'm a little surprised at this.
I have yet to calibrate the phone but it is only a month old, granted it was calibrated after flashing S7, could this be the problem? I don't think the phone is undervolted yet, would voltage control from the market help this by lowering it a bit?
4) sometimes my volume slider just dissapears, i don't know why. Using the volume rocker on the homescreen usually has the ringer volume pop up. But once in a while, it stops showing up, the settings still work, but the slider is invisible. It is not restored upon reboot, and it eventually comes back and dissapears again.
5) First phone call has no audio. I believe this is a documented problem with S7, just asking to confirm this.
6) A couple of albums in my music library aren't tagged properly in the player despite being correctly tagged with MP3TAG on my computer. After some research, i think i found this is a GB media scanner problem. Is there a way to correct this? Perhaps take an apk from another ROM and replace it?
Many thanks to anybody who takes the time to read this thread
I'm trying to set up an old Samsung Infuse 4G (CM10.1 Unofficial) as an audio server, feeding audio into my home audio amplifier. I've got aMPD (android port of Media Player Daemon) running on the phone and have checked the "stay awake" option that's supposed to grab a wakelock and keep the CPU from going to sleep. Yet as soon as the phone display times out, the device become terribly sluggish to remote aMPD commands. If I unlock the phone and get aMPD back on the display, it becomes highly responsive again. Kinda seems like it's failing to get a wakelock, but if I look at battery statistics, I can see that aMPD is responsible for 50% of my battery usage, so it seems like it IS getting a wakelock correctly.
I went ahead and installed the app "Wake Lock" and used it to set PARTIAL_WAKE_LOCK, and I get the same result. Very sluggish unless aMPD is showing on the display.
I've also got "Keep wifi on during sleep" set to "always," so I don't think that the issue is the network.
Any suggestions?
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.
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?