[Q]Android OS - LG Optimus G (International)

Last night, around 2am, I unplugged my phone from the charger before i went to sleep (it had WiFi on) and now when I woke up and checked it at 1:30pm the next day, I had 35% battery left! WHAT!? checked battery stats and Android OS ate up 51%! with phone idle at 12%
anyone have any idea what's going on? I have everything except WiFi turned off, GPS, Location Services, Auto-Sync, Auto-Backup, everything. I also underclocked everything via cpu master and trickster mod. I greenified facebook, viber, skype and any other app that could potentially wake my phone from deep sleep.
I checked trickster mod, deep sleep was at around 5hrs with 162mhz at around 7hrs. don't have any screenies of those since I rebooted my device right after I plugged in the charger (helps with displaying correct percentage)
I've attached a screenshot. I've never seen that kind of downar plunge in my battery stats. ever. this is the first time it's ever happened.
I'll install wakelock detector and give it a few hours. I know my phone drains around 1%/hr while idle, maybe even less.
EDIT: I already started when I took the second screenshot. I forgot to take a screenshot of the rest of my battery stats. so don't mind the time and the difference in battery percentage.

that's kernel problem. I meet that problem before, while I'm using AK-kernel with Vanir ROM. Kernel make screen always on to increase respond for S2W and Double Tap to Wake, but also cause this problem. In Android 4.4.2 also have this issues ( Nexus 4 and Nexus 5 is an example, you can search Google for this ).
You can install Better Battery Stats to check wakelock issues, but you can't do nothing, unless you have to changed to another kernel

BIBUBO BCJ said:
that's kernel problem. I meet that problem before, while I'm using AK-kernel with Vanir ROM. Kernel make screen always on to increase respond for S2W and Double Tap to Wake, but also cause this problem. In Android 4.4.2 also have this issues ( Nexus 4 and Nexus 5 is an example, you can search Google for this ).
You can install Better Battery Stats to check wakelock issues, but you can't do nothing, unless you have to changed to another kernel
Click to expand...
Click to collapse
don't have S2W and knock on enabled on my kernel. I also tried those and their battery drain is nothing compared to this!
I've charged my device and now it's showing Google Search as the culprit. now looking for a solution.

vangeodee said:
don't have S2W and knock on enabled on my kernel. I also tried those and their battery drain is nothing compared to this!
I've charged my device and now it's showing Google Search as the culprit. now looking for a solution.
Click to expand...
Click to collapse
what's your kernel ?

BIBUBO BCJ said:
what's your kernel ?
Click to expand...
Click to collapse
Solid Kernel + Stock 4.1.2 with a few xposed modules. I've solved the problem. Had to completely turn off Google Now and blocked wakelocks from Google Play Services.
I'll give this 3 hours and see if it goes back to the 1%-1hr idle drain. Battery stats seems to have improved, I'll post my post-fix battery stats in around 5 hours just to check if the problem comes back.

aaaaaaaaaaand it's back. This time it's not Android OS but Google Play Services that's eating the battery up. I now get 2%/hr with this new problem.
I checked trickster mod and my phone is not entering deep sleep. checked wakelock detector and it showed GCMSEND as keeping the phone awake. (1h 52m out of 2h)
Anyone know a fix for this? I've currently filtered it in Wakelock Terminator and I'll see how it goes from there.
UPDATE:
22 mins in and phone is in Deep Sleep 84% of the time. filtered GCMSEND and added 2 lines to build.prop that supposedly improves deep sleep.
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
Source: http://forum.xda-developers.com/showpost.php?p=46301722&postcount=2
Will leave it overnight to see if it stays this way.

yeah, noway to fix it because it was an issues of kernel.
If GCMSEND always running, you can downlod app called Disable Services, and Open it to disable some service in Google Play Store and another system app. Try it and will see if it's working.

Related

[Q] Why won't my phone goto sleep?

I think my phone is suffering from the Android OS keep awake bug. I just charged my phone to 100%, rebooted, opened and closed the camera app and left it alone for about an hour and a half. I am down to 92% batter life remaining. This seems excessive. The Android OS app shows a keep awake time of exactly 93 minutes which is also exactly the same as the up time.
I don't quite understand BetterBatteryStats just yet, but BetterBatteryStats shows "gps-lock" as 1h27m4s under Kernel Wakelocks since charged. Nothing else comes close. The highest Partial Wakelock is ActivityManager-Launch with 12s. Under Other Awake is 93 minutes and Screen on is 2 minutes. BetterBatteryStats is the first item under Process the surfaceflinger and com.android.phone.
Before rebooting I had set my GPS settings to (and they remained this way after reboot)
-Google's Location Service : Unchecked
-GPS satellites : Checked
-Location & Google search : Unchecked
Other stats:
-Verizon LTE
-bigxie IML74K Build 2
-franco.Kernel #12 (hotplug enabled, 350k low, 120k high)
-No widgets
-No other apps were opened
-Gmail is set to sync. I haven't run or configured Google+ (don't use it). Gmail/Calendar/Contacts should be the only things syncing, no facebook sync.
I had similar issues before flashing the kernel and rom.
How can I get this thing to go to sleep? I don't think this should be consuming so much battery life while idle.
you have a "bad app" that is preventing the phone from deep sleeping.
get cpu spy from the market to verify how long your phone is staying in each state
do you have any notifications in the notification bar?
No notifications were received in the last 90 minutes (forever alone yes). I just installed CPUSpy. This says 00:01:25 was spent in 1200Mhz, 01:39:52 in 350mhz and 0:00:0 in Deep Sleep.
How can I find what app is preventing deep sleep? The only apps listed in the battery app are Android OS, Screen, Phone Idle, Cell standby and Android System.
Wouldn't this bad app show up in BetterBatteryStats under Process?
lethologica said:
No notifications were received in the last 90 minutes (forever alone yes). I just installed CPUSpy. This says 00:01:25 was spent in 1200Mhz, 01:39:52 in 350mhz and 0:00:0 in Deep Sleep.
How can I find what app is preventing deep sleep? The only apps listed in the battery app are Android OS, Screen, Phone Idle, Cell standby and Android System.
Wouldn't this bad app show up in BetterBatteryStats under Process?
Click to expand...
Click to collapse
I don't use BetterBatteryStats so I wouldn't know.
I personally set my CPU speeds from 700-1200MHz (as indicated by Franco and others... setting it to ~300 is bad because it makes the phone use more power to catch up)
How many apps do you have? can you use AppBrain or something to provide me a list of what apps you use?
I just took a list at my CPU Spy...
0:09:51 1200Mhz
920 MHz... 0:01:35
700MHz: 0:09:49
Deep Sleep: 3:21:43
82%... 3h 50m 35s on battery
Android OS 28%
Screen 24%
Google Voice 14%
Phone idle 14%
Android system 7%
Cell standby 3%
Nova Launcher 3%
Wi-Fi 2%
Beautiful Widgets 2%
Market 2%
700-1200MHz. Conservative Governor. Hotplug off
I did try 700 with earlier versions (I think 8 & 9) and was also getting poor battery performance during idle. I wish there was an easier way to determine what app is preventing deep sleep, however it would almost certainly have to be a system app as I did not run any app when I started this test.
lethologica said:
I did try 700 with earlier versions (I think 8 & 9) and was also getting poor battery performance during idle. I wish there was an easier way to determine what app is preventing deep sleep, however it would almost certainly have to be a system app as I did not run any app when I started this test.
Click to expand...
Click to collapse
It doesn't have to be a system app. A app can be started as the moment as Android OS is started.
Not all apps are listed in that battery monitor. I can tell you that for sure. Definitely something is wrong with your phone setup.
The best way to debug it (in my opinion) would be to backup all of your apps and reflash the ROM from scratch. Flash bigxie's ROM (or try another ROM if you choose to) and Franco's Kernel.... install CPU Spy and leave the phone off for like 5-10 minutes. See if it deep sleeps.
Edit: Try this https://market.android.com/details?...251bGwsMSwxLDEsIm5leHRhcHAuc3lzdGVtcGFuZWwiXQ this should help you figure out what app it is.
Thanks for the tip. I am going to recharge and test again with all GPS settings disabled to rule the GPS out. Seeing the gps-lock as the top process in Kernel Waitlocks makes me wonder. I will give SystemPanelLite a try after this test.
lethologica said:
Thanks for the tip. I am going to recharge and test again with all GPS settings disabled to rule the GPS out. Seeing the gps-lock as the top process in Kernel Waitlocks makes me wonder. I will give SystemPanelLite a try after this test.
Click to expand...
Click to collapse
You did update to the latest Google Maps right? it contained fixes for the battery. Maps is a huge drain if it runs in the background. I always leave my GPS deactivated even though it's activated ondemand. I just don't trust it.
Ahh hah! It has only been 20 minutes, but the GPS is the culprit. I did the same charge, reboot, camera cycle. Then I walked away. Checked CPUSpy and sure enough there was 18 minutes of deep sleep time out of a 20 minutes up time. Google Maps is up to date by the way.
Now the funny thing is, the GPS isn't all that great even when it was keeping my phone awake. Last night I checked the GPS after I got out of the subway (public transit, not sandwiches), for a second it still thought I was in the location prior to taking the subway. It took close to ten seconds to get within 500 meters of my location, and after that it was unable to pinpoint my exact location. The phone has been able to pinpoint my exact location in the past though.
So now, how can I determine if this is a software bug or a hardware bug? If it is software then no big deal, I can hold out. If it is hardware then I need to revert to factory, unroot, etc.
lethologica said:
Ahh hah! It has only been 20 minutes, but the GPS is the culprit. I did the same charge, reboot, camera cycle. Then I walked away. Checked CPUSpy and sure enough there was 18 minutes of deep sleep time out of a 20 minutes up time. Google Maps is up to date by the way.
Now the funny thing is, the GPS isn't all that great even when it was keeping my phone awake. Last night I checked the GPS after I got out of the subway (public transit, not sandwiches), for a second it still thought I was in the location prior to taking the subway. It took close to ten seconds to get within 500 meters of my location, and after that it was unable to pinpoint my exact location. The phone has been able to pinpoint my exact location in the past though.
So now, how can I determine if this is a software bug or a hardware bug? If it is software then no big deal, I can hold out. If it is hardware then I need to revert to factory, unroot, etc.
Click to expand...
Click to collapse
It's probably software. Something is keeping the GPS on. Either by a app or ROM. Most likely app.
If you're not using gps with google location services, it will take a while to lock.
Also, you have an app that is requesting GPS constantly while the phone is sleeping.. That is all.
joshnichols189 said:
Also, you have an app that is requesting GPS constantly while the phone is sleeping.. That is all.
Click to expand...
Click to collapse
Any idea on how to figure out what that app is?
I'm not sure how to find an app that is constantly requesting GPS, but I know the app Watchdog will help find an app that is running in the background consuming processor cycles.. you might want to try that but I have no idea if it will work.
holy ****! thank you! I've been trying to figure out what was causing my phone to not deep sleep for a week! I uninstalled google maps and it worked! now I'd like to figure out how to have both deep sleep and google maps installed...
did you tuck your phone in?
I had that problem with a Rom and turning on and off the Bluetooth would fix the problem.
Sent from my GalaxyNexus using Tapatalk
imail724 said:
holy ****! thank you! I've been trying to figure out what was causing my phone to not deep sleep for a week! I uninstalled google maps and it worked! now I'd like to figure out how to have both deep sleep and google maps installed...
Click to expand...
Click to collapse
Try disabling GPS when you're not using it. Worked for me.
i tried to freeze the google maps, but still getting the GPS wakelock.
from the other thread, some one mentioned about facebook.
i freeze facebook in titanium backup. looks like the GPS time is not increasing.
are you guys having this issue installed facebook app?
the other thread:
http://forum.xda-developers.com/showthread.php?t=1419087&page=3

[Q] Jellytime ROM on DHD - battery drain

How much does your Jellytime ROM drain from battery? Using battery e.g. Battery monitor widget, I can see 60mA drain when phone is standby. Seems to be a lot for me. I didn't find comparsion just subjective claims - high/low drain. 60mA is with wifi turned off, bt disables, no gprs/3g data, just standby. No application seems to be running. Battery stat shows that 60 % is display (but I can confirm that display is off), 40 % cell stand by and about the same amount phone idle.
You can try BetterBatteryStats to check what might be draining your battery (if any).
Here's the link to the beta version for xda users: http://forum.xda-developers.com/showthread.php?t=1179809
xbiggyl said:
You can try BetterBatteryStats to check what might be draining your battery (if any).
Here's the link to the beta version for xda users: http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
Thanks, I will try it. So far I was using Battery Monitor apk. However, I have no reference if my battery drain level is expected for that rom or not.
I'm also having issues with battery drain on JT... really strange. It seems to have drain when in standby, and when the screen is on it goes like crazy, I can't get more than like 20-30 minutes of screen-on time. I really like this ROM, it is pretty stable and works fine, no major bugs but the battery drain is crazy. I took a couple of screenshots. It seems that process Media is keeping it "awake" and causing battery drain. In all other ROMs I used (and in stock) I have never seen any other process except SCREEN using more than couple of percent of battery. Now this media process is using almost as screen! Any clues as what it is?
Also, I noticed that it discharges quickly when screen is on, but it also charges quickly! Something wrong with battery stats? It simply can't go from 20% to 70% in 10 minutes while charging?
xhejtman said:
How much does your Jellytime ROM drain from battery? Using battery e.g. Battery monitor widget, I can see 60mA drain when phone is standby. Seems to be a lot for me. I didn't find comparsion just subjective claims - high/low drain. 60mA is with wifi turned off, bt disables, no gprs/3g data, just standby. No application seems to be running. Battery stat shows that 60 % is display (but I can confirm that display is off), 40 % cell stand by and about the same amount phone idle.
Click to expand...
Click to collapse
Its about 1% per hour about the battery drain..quite good battery with usage
KeshavJave said:
Its about 1% per hour about the battery drain..quite good battery with usage
Click to expand...
Click to collapse
Hmm, could you provide mA value (battery monitor shows it in history in 10 minutes intervals..)
I can do five hours with normal use on a full charge..
These are battery stats for my DHD. The first one is standby over night with stok HTC ROM (2.3.5), the second one is with JellyTime ROM 9.1. It takes 10times more power.
marclooman9 said:
I can do five hours with normal use on a full charge..
Click to expand...
Click to collapse
That's not much. Was it better as long as you can remember with stock HTC ROM? I could do 2-3 days with normal use with stock ROM.
xhejtman said:
That's not much. Was it better as long as you can remember with stock HTC ROM? I could do 2-3 days with normal use with stock ROM.
Click to expand...
Click to collapse
Wow 2 to 3 days? Last time I had a phone like that was back in non smart phone days...
ai6908 said:
Wow 2 to 3 days? Last time I had a phone like that was back in non smart phone days...
Click to expand...
Click to collapse
Yes, but my cost for 2-3 days is: no gsm data, no wifi (or wifi for something like 5 minutes), no widgets except htc clock & weather, almost no background apps, few phone calls, moderate number of sms. (Yes I hear you saying, you don't need 'smart' phone , I do, I use some apps but not too frequently, so avg running time from 100% to say 10% of battery was 2-3 days, mainly depending on number of sms sent
I had it charged to 100%. Then I kept it charging, went to recovery and deleted battery stats. I booted and when it displayed lock screen I unplugged. Then I played for like 10 minutes (screen on) and my battery went from 100% to 88% !!! A bit too much? I installed betterbatterystats so I hope I'll see which process keeps it awake (there's drain even when screen off)...
D.
dalanik said:
I had it charged to 100%. Then I kept it charging, went to recovery and deleted battery stats. I booted and when it displayed lock screen I unplugged. Then I played for like 10 minutes (screen on) and my battery went from 100% to 88% !!! A bit too much? I installed betterbatterystats so I hope I'll see which process keeps it awake (there's drain even when screen off)...
D.
Click to expand...
Click to collapse
perhaps try to install: http://play.google.com/store/apps/details?id=ccc71.bmw
it provides history of current consumption, that can tell whether it is a lot or not.
Btw, what do you exactly mean by "played for 10m"? What did you do?
xhejtman said:
Btw, what do you exactly mean by "played for 10m"? What did you do?
Click to expand...
Click to collapse
Thanx for the tip, I'll try installing the app you suggest. "Played" means I turned the screens on louncher a couple of times to update all widgets, went into settings, looked at the battery stats etc. Maybe lounched foursquare and titanium backup, nothing really intensive... Here are shots from batterystats. Seems to me media service is doing it...
dalanik said:
Thanx for the tip, I'll try installing the app you suggest. "Played" means I turned the screens on louncher a couple of times to update all widgets, went into settings, looked at the battery stats etc. Maybe lounched foursquare and titanium backup, nothing really intensive... Here are shots from batterystats. Seems to me media service is doing it...
Click to expand...
Click to collapse
yes media service seems to be suspicious. It says, the phone was in deep sleep only half an hour for last hour while screen on was really only for about 10 minutes. I think the problem is in remaining time. I am not really familiar with bbs logs, maybe post the log into BBS thread here on XDA for help if you cannot figure it yourself.
dalanik said:
I had it charged to 100%. Then I kept it charging, went to recovery and deleted battery stats. I booted and when it displayed lock screen I unplugged. Then I played for like 10 minutes (screen on) and my battery went from 100% to 88% !!! A bit too much? I installed betterbatterystats so I hope I'll see which process keeps it awake (there's drain even when screen off)...
D.
Click to expand...
Click to collapse
There is no need for wiping battery stats.
Once your phone recharges to 100%, battery stats reset by default.
xbiggyl said:
There is no need for wiping battery stats.
Once your phone recharges to 100%, battery stats reset by default.
Click to expand...
Click to collapse
I know, I read that somewhere, but just wanted to be sure This is really driving me nuts, I always have to be near charger
xbiggyl said:
You can try BetterBatteryStats to check what might be draining your battery (if any).
Here's the link to the beta version for xda users: http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
Ok, I figured out, what is causing high battery drain. It FM radio. After clean flash and basic setup, it consumes 10mA when standby. Which is twice more than with stock ROM, but seems to be acceptable. If I run and then exit Sprite FM radio app, phone starts to consume 60mA until reboot. After reboot, it is ok, until I run Sprite FM app again.
However, BBS does not show anything useful. Maybe because of FM HW keeps running? There is shown no SW battery eater..
I still can't figure it out Here's log of consumptuon in standby from last night, I have it set on profile manager to turn off data and set airplane mode from 1am-7am. Looks good to me, can someone confirm these are OK values?
Code:
2012/09/24|00:28:43|587mA|60%|4182mV|34.0ºC|.258|1
2012/09/24|00:29:43|529mA|60%|4182mV|34.0ºC|.100|1
2012/09/24|00:39:43|-61mA|60%|3869mV|32.0ºC|.256|2
2012/09/24|00:49:43|-11mA|59%|3960mV|27.0ºC|.0|0
2012/09/24|00:59:43|-28mA|59%|3957mV|25.0ºC|.0|0
2012/09/24|01:09:43|-18mA|59%|3960mV|23.0ºC|.0|0
2012/09/24|01:19:43|-8mA|59%|3957mV|22.0ºC|.0|0
2012/09/24|01:29:43|-10mA|58%|3940mV|22.0ºC|.0|0
2012/09/24|01:39:43|-13mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|01:49:44|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|01:59:43|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|02:09:43|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|02:19:43|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|02:29:43|-7mA|57%|3945mV|21.0ºC|.0|0
2012/09/24|02:39:43|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|02:49:44|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|02:59:43|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|03:09:43|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|03:19:43|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|03:29:44|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|03:39:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|03:49:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|03:59:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|04:09:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|04:19:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|04:29:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|04:39:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|04:49:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|04:59:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|05:09:43|-10mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|05:19:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|05:29:43|-13mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|05:39:43|-7mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|05:49:44|-7mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|05:59:43|-12mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|06:09:43|-7mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|06:19:43|-7mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|06:29:43|-7mA|53%|3891mV|20.0ºC|.18|0
2012/09/24|06:39:43|-7mA|53%|3891mV|20.0ºC|.0|0
2012/09/24|06:46:44|-210mA|53%|3740mV|21.0ºC|.0|0
2012/09/24|06:56:44|356mA|57%|4187mV|24.0ºC|.3|6
2012/09/24|07:00:44|-264mA|71%|3816mV|25.0ºC|.360|2
2012/09/24|07:10:44|-254mA|51%|3721mV|24.0ºC|.1000|0
2012/09/24|07:20:44|-32mA|36%|4174mV|24.0ºC|.736|6
2012/09/24|07:30:44|397mA|75%|3933mV|26.0ºC|.3|2
2012/09/24|07:40:44|-61mA|73%|3784mV|26.0ºC|.76|0
2012/09/24|07:50:44|-121mA|63%|3779mV|26.0ºC|.450|0
2012/09/24|08:00:44|-233mA|44%|3730mV|26.0ºC|.998|0
2012/09/24|08:10:44|-125mA|37%|3769mV|27.0ºC|.200|0
2012/09/24|08:19:36|607mA|55%|3850mV|27.0ºC|.1|1
2012/09/24|08:29:35|611mA|64%|4187mV|28.0ºC|.130|1
2012/09/24|08:39:35|426mA|69%|4189mV|28.0ºC|.0|1
2012/09/24|08:49:18|136mA|94%|4087mV|27.0ºC|.8|3
But look at the 2nd attached screenshot, at the end of the graph - how fast it charges, isn't that unusual?
Code:
2012/09/24|00:28:43|587mA|60%|4182mV|34.0ºC|.258|1
2012/09/24|00:29:43|529mA|60%|4182mV|34.0ºC|.100|1
charging at rate 500-600mA, is it external charger? I do charging on ntb and it's up to 400mA when battery is not close to 100%.
Code:
2012/09/24|00:39:43|-61mA|60%|3869mV|32.0ºC|.256|2
2012/09/24|00:49:43|-11mA|59%|3960mV|27.0ºC|.0|0
2012/09/24|00:59:43|-28mA|59%|3957mV|25.0ºC|.0|0
2012/09/24|01:09:43|-18mA|59%|3960mV|23.0ºC|.0|0
2012/09/24|01:19:43|-8mA|59%|3957mV|22.0ºC|.0|0
2012/09/24|01:29:43|-10mA|58%|3940mV|22.0ºC|.0|0
2012/09/24|01:39:43|-13mA|58%|3955mV|21.0ºC|.0|0
seems to be of slight using or runnign backgroud processes this hour?
Code:
2012/09/24|01:49:44|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|01:59:43|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|02:09:43|-7mA|58%|3955mV|21.0ºC|.0|0
this is expected consumption, with stock HTC ROM I got -3 - -5mA, but -7mA is pretty good. With R10 I got -10mA, don't know why it does sleep less than it should.
Code:
2012/09/24|06:46:44|-210mA|53%|3740mV|21.0ºC|.0|0
2012/09/24|06:56:44|356mA|57%|4187mV|24.0ºC|.3|6
2012/09/24|07:00:44|-264mA|71%|3816mV|25.0ºC|.360|2
2012/09/24|07:10:44|-254mA|51%|3721mV|24.0ºC|.1000|0
what happened here? -264mA is a lot of power consumption, do you remember what did you do? Common usage should be around -100mA.

Battery Life - Idle drain?

I was wondering if anybody else had this issue or had any suggestions.
Battery life is normally great on the tablet, except every once and a while it gets stuck awake overnight. There doesn't seem to be a 3rd party app that is holding it awake, as Android system and OS is what's using most of the battery.
As you can see in the screenshot, Doze works fine and barely any better is drained, I used it briefly, came home from work and half the battery had been drained.
Thanks for the help
Not sure if it's normal but mine does the same.
Sent from my Nexus 6 using Tapatalk
I've seen a 30ish % drain sitting overnight a couple of times over the past 2 weeks. Can't seem to find a rhyme or reason for it.
I can't imagine it being "normal" since, with Wifi set to off while sleeping that the device should drain that much.
It's odd and happens randomly, I'm on the same page as you bluestang.
It happened to me once, at night it wastes a 15% battery.
I changed in wifi advance options to not maintain WiFi always awake, only in charge.
sabisavi said:
It happened to me once, at night it wastes a 15% battery.
I changed in wifi advance options to not maintain WiFi always awake, only in charge.
Click to expand...
Click to collapse
That's the setup I have though - so I get no notifications or anything when it's not on. Yet something is still keeping the device up.
I have *exactly* the same problem with an all new device, and with nothing but a game installed on it. After a reboot, if I let the Pixel C right there for a night, then it only drains ~3/4%.
Then I play the only game I have for 5 minutes, and let the device again for a night => it now wastes a 20% battery!
No idea what's going on... "Android OS" appears first in the list of app, but this does not help me so much to find what is actually happening...
The issue still appears even after a full reset of the system (I'v tried, without success).
sylar12 said:
I have *exactly* the same problem with an all new device, and with nothing but a game installed on it. After a reboot, if I let the Pixel C right there for a night, then it only drains ~3/4%.
Then I play the only game I have for 5 minutes, and let the device again for a night => it now wastes a 20% battery!
No idea what's going on... "Android OS" appears first in the list of app, but this does not help me so much to find what is actually happening...
The issue still appears even after a full reset of the system (I'v tried, without success).
Click to expand...
Click to collapse
Exactly. If I reboot the device and let it sit, doze works fine, the second I open an app, use it and put the tablet down, something hangs and keeps it awake. Always Android OS that is keeping it awake as well...
I have this issue too. Are you guys on xceed Kernel?
Whats really interesting even better battery stats Shows no culprit.
I'm on the stock-just-reset-again last version of the system.
Freak07 said:
I have this issue too. Are you guys on xceed Kernel?
Whats really interesting even better battery stats Shows no culprit.
Click to expand...
Click to collapse
I'm on stock - not even rooted
I'm on stock MM here as well.
Also, not sure if it a coincidence or not, but I changed this and haven't seen overnight battery drops anymore. In Settings>Location I changed the Mode from High accuracy to Battery saving. Since the Pixel C doesn't have GPS device, then why use it.
Like I said, not sure if it a coincidence, but battery life has been great overnight since.
bluestang said:
I'm on stock MM here as well.
Also, not sure if it a coincidence or not, but I changed this and haven't seen overnight battery drops anymore. In Settings>Location I changed the Mode from High accuracy to Battery saving. Since the Pixel C doesn't have GPS device, then why use it.
Like I said, not sure if it a coincidence, but battery life has been great overnight since.
Click to expand...
Click to collapse
So last night, I rebooted before I went to sleep, but overnight the battery drained from 85% down to 57% in about 8 hours.
I decided to check my location settings as per your post and found it was set to high accuracy, so I changed it to "Battery Saving".
I did nothing else(no reboot) until I checked my battery now about 3 hours later, it has only dropped by a further 2%.
Looking at "Battery Monitor Widget Pro" history statistics, it is clear to see that overnight the battery was draining considerably more.
It takes readings every 10 minutes and was showing between 450 and 275 mA being used every 10 minutes overnight.
Since I changed the location settings, most of the time it is 15mA with occasional jumps up to a max of 297mA.
Although this could not be classed as conclusive proof, it does seem to have had an effect, I will keep monitoring it to see how it goes.
Yep, I change that setting on the 19th or 20th and haven't seen any major drains overnight.
I think I may have found a winner with that little tweak
So far so good for me too. I don't know if it is related to the GPS settings, but no more inconsistent major drains so far.
if location services is on it can drain a good deal
Just to add that I had exactly the same issue on stock 7.1.2, tablet was staying awake and draining. Reduced location precision and now only a 2% drain during an 8 hour sleep which is a massive improvement.

Terrible battery life probably caused by wakelocks

My battery will completely drain after <10 hours while the screen is off!
However I was able to find out thatquickgooglesearchbar is always the top app.
Those screenshots are a bit old but it's still the same thing, I did manage to root it today, and I was testing Greenify which did nothing even with the Xposed modules, service disabler apps just did not show that specific service for some reason. I was able to remove the widget with Xposed GEL settings but it was still running even though the widget wasn't there.
So can someone please help me out here, maybe the search bar isn't the problem but I just want some battery life.
h ttp://imgur.com/a/gdXKW
(I still can't post links sorry If this is against your forum rules but this is urgent)
Eidoss said:
My battery will completely drain after <10 hours while the screen is off!
However I was able to find out thatquickgooglesearchbar is always the top app.
Those screenshots are a bit old but it's still the same thing, I did manage to root it today, and I was testing Greenify which did nothing even with the Xposed modules, service disabler apps just did not show that specific service for some reason. I was able to remove the widget with Xposed GEL settings but it was still running even though the widget wasn't there.
So can someone please help me out here, maybe the search bar isn't the problem but I just want some battery life.
h ttp://imgur.com/a/gdXKW
(I still can't post links sorry If this is against your forum rules but this is urgent)
Click to expand...
Click to collapse
search and install betterbatterystats (read the whole first post) and it will tell you if its wakelocks etc.
Service disabler apps will need a setting to show system apps (or something similar) ticked or switched to etc.
greenify system apps in greenify also needs to be selected. You may also need to cut wake up paths to get it to stay greenified.
You could alternatively delete the apk of hibernate it (byfar the easiest option of all this).
Darke5tShad0w said:
search and install betterbatterystats (read the whole first post) and it will tell you if its wakelocks etc.
Service disabler apps will need a setting to show system apps (or something similar) ticked or switched to etc.
greenify system apps in greenify also needs to be selected. You may also need to cut wake up paths to get it to stay greenified.
You could alternatively delete the apk of hibernate it (byfar the easiest option of all this).
Click to expand...
Click to collapse
I don't need betterbatterystats, I have battery Battery Historian, check the screenshots, It's clearly the search bar, on my other phone It isn't shown as a top app.
Also I went in the system folder /apps and there was no googlesearchbar, or in any other system apk remover tool, perhaps it was removed by another app, but it's still for some reason running.
Eidoss said:
I don't need betterbatterystats, I have battery Battery Historian, check the screenshots, It's clearly the search bar, on my other phone It isn't shown as a top app.
Also I went in the system folder /apps and there was no googlesearchbar, or in any other system apk remover tool, perhaps it was removed by another app, but it's still for some reason running.
Click to expand...
Click to collapse
Your 3rd image shows googlequicksearchbox had 370ms (milliseconds) of wakelocks over a 9hr period. I really doubt that is your issue.
If it is your top app, then it is probably because of Google Now launcher listening for OK Google spoken keyword.
I seriously doubt that is your battery drain problem as almost 90% of people probably have OK Google turned on and are using Google Now launcher and only a very few have serious battery drain.
BTW wakelocks aren't the issue usually. In the past it has been "partial wakelocks" which means an app locked the device from sleeping, but never released the lock, so the device never goes to full sleep. If you see some app with partial wakelocks or if you see some app with hours of regular wakelocks then that might be an issue. Minutes or microseconds of wakelocks are inconsequential.
I suggest you flash factory image and install your battery tester only. Turn off wifi, bluetooth, nfc, cell radio. Test the drain overnight. That is a baseline for the minimum drain your device can have. Then enable what wireless stuff you normally have turned on. See what that drain is. Then start installing apps and see what that drain is.
If you have reasonable/expected battery drain with stock and everything turned off, then it is just a process of elimination to see what is causing your battery drain.
If you can't get reasonable/expected battery drain with stock and everything turned off, then you probably have a bad battery.
For the record, my overnight battery drain with everything turned off is 0-1% With wifi turned on about 1-2%. With wifi+cell about 2-3%.
IMO the biggest drains for standby are wifi and/or cell signal related. Either bad signals or apps sending data in background or apps that are polling all the time.
sfhub said:
Your 3rd image shows googlequicksearchbox had 370ms (milliseconds) of wakelocks over a 9hr period. I really doubt that is your issue.
If it is your top app, then it is probably because of Google Now launcher listening for OK Google spoken keyword.
I seriously doubt that is your battery drain problem as almost 90% of people probably have OK Google turned on and are using Google Now launcher and only a very few have serious battery drain.
BTW wakelocks aren't the issue usually. In the past it has been "partial wakelocks" which means an app locked the device from sleeping, but never released the lock, so the device never goes to full sleep. If you see some app with partial wakelocks or if you see some app with hours of regular wakelocks then that might be an issue. Minutes or microseconds of wakelocks are inconsequential.
I suggest you flash factory image and install your battery tester only. Turn off wifi, bluetooth, nfc, cell radio. Test the drain overnight. That is a baseline for the minimum drain your device can have. Then enable what wireless stuff you normally have turned on. See what that drain is. Then start installing apps and see what that drain is.
If you have reasonable/expected battery drain with stock and everything turned off, then it is just a process of elimination to see what is causing your battery drain.
If you can't get reasonable/expected battery drain with stock and everything turned off, then you probably have a bad battery.
For the record, my overnight battery drain with everything turned off is 0-1% With wifi turned on about 1-2%. With wifi+cell about 2-3%.
IMO the biggest drains for standby are wifi and/or cell signal related. Either bad signals or apps sending data in background or apps that are polling all the time.
Click to expand...
Click to collapse
Factory reset didn't do anything a few days ago, the results were exactly the same that was when my phone wasn't rooted, so I guess I should return the phone, and get a new one?
Eidoss said:
Factory reset didn't do anything a few days ago, the results were exactly the same that was when my phone wasn't rooted, so I guess I should return the phone, and get a new one?
Click to expand...
Click to collapse
What is your battery drain per hour with nothing installed and all wireless turned off and everything stock?
I'd only return it if that is significantly more than 0-.2% or 1% every 5 hours.
Otherwise it is something you have installed or something to do with the signal and how it interacts with your phone.
Once you start installing stuff or turning on wireless (wifi/bt/cell) then it is no longer purely about the battery and there are more factors that need to be isolated independently.
You really need to establish a baseline to see what the minimum battery drain is. Then you can determine if the battery is the problem or something else.
If you just install everything and turn everything on, there are too many moving parts.
sfhub said:
What is your battery drain per hour with nothing installed and all wireless turned off and everything stock?
I'd only return it if that is significantly more than 0-.2% or 1% every 5 hours.
Otherwise it is something you have installed or something to do with the signal and how it interacts with your phone.
Once you start installing stuff or turning on wireless (wifi/bt/cell) then it is no longer purely about the battery and there are more factors that need to be isolated independently.
You really need to establish a baseline to see what the minimum battery drain is. Then you can determine if the battery is the problem or something else.
If you just install everything and turn everything on, there are too many moving parts.
Click to expand...
Click to collapse
Okay, I now have android N, and my battery life seems to be better, I will leave mobile data off. I will see tomorrow if my battery life has changed.
Do you think I should use Adaptive brightness for more battery life?
Eidoss said:
Okay, I now have android N, and my battery life seems to be better, I will leave mobile data off. I will see tomorrow if my battery life has changed.
Do you think I should use Adaptive brightness for more battery life?
Click to expand...
Click to collapse
Which battery life was the one you think you have a problem with, standby or in use? IMO for in use battery time this phone is about average. Your title of "wakelock" made it seem like you were concerned about standby battery time as it doesn't matter if there is a wakelock if the device is already turned on and in active use.
When turned on, the screen is probably the number one thing eating power, so adaptive brightness could help, but if you are in a bright area, it might be worse than if you fixed the brightness below max.
Even if you have adaptive brightness turned on, the slider scale still is useful as you give the adaptive brigthness mechanism some idea what level of brightness you feel comfortable when the mechanism detects dark, med, bright situations.
One of the worse things for eating power is for the cell radio to be turned on but have no signal, like inside office building or just a bad signal area in general. The reason is the cell radio is power efficient once it establishes signal, but when it is searching for (or loses) signal it uses a lot of power.
If you are doing a lot of disk activity like taking video or hdr pictures, it would probably help to have your userdata unencrypted as this device does software (kernel) encryption and doesn't use the fast/more power efficient co-processor.
sfhub said:
Which battery life was the one you think you have a problem with, standby or in use? IMO for in use battery time this phone is about average. Your title of "wakelock" made it seem like you were concerned about standby battery time as it doesn't matter if there is a wakelock if the device is already turned on and in active use.
When turned on, the screen is probably the number one thing eating power, so adaptive brightness could help, but if you are in a bright area, it might be worse than if you fixed the brightness below max.
Even if you have adaptive brightness turned on, the slider scale still is useful as you give the adaptive brigthness mechanism some idea what level of brightness you feel comfortable when the mechanism detects dark, med, bright situations.
One of the worse things for eating power is for the cell radio to be turned on but have no signal, like inside office building or just a bad signal area in general. The reason is the cell radio is power efficient once it establishes signal, but when it is searching for (or loses) signal it uses a lot of power.
If you are doing a lot of disk activity like taking video or hdr pictures, it would probably help to have your userdata unencrypted as this device does software (kernel) encryption and doesn't use the fast/more power efficient co-processor.
Click to expand...
Click to collapse
Standby is the problem, on screen times are good enough.
Anyway, I don't even know what to do at this point. Android N didn't help enough (cell data is off), I guess I can flash Android 6.0 again and then try to fix it using apps...
What do you suggest I should do, I'm out of ideas at this point.
Eidoss said:
Standby is the problem, on screen times are good enough.
Anyway, I don't even know what to do at this point. Android N didn't help enough (cell data is off), I guess I can flash Android 6.0 again and then try to fix it using apps...
What do you suggest I should do, I'm out of ideas at this point.
Click to expand...
Click to collapse
What is the power drain over a couple of hours with *no apps installed* completely stock, and wifi/cell turned off? What is the change when wifi is turned on?
Eidoss said:
What do you suggest I should do, I'm out of ideas at this point.
Click to expand...
Click to collapse
Have you set "WiFi on during sleep" to "Never"? in the Advanced WiFi settings?
In the original release, there was a bug where WiFi would stay on even if you had set it to "Never" draining battery in standby.
Somewhere between MDA89E and MHC19Q they fixed it and WiFi will go to deep sleep after being in standby for a while, but they introduced another (or exposed existing) bug where WiFi will not resume after coming out of sleep, unless you cycle WiFi off/on. So you're standby battery should be better with this setting, but it'll be a little more annoying when turning on your device.

Battery drain Oreo

I'm on Atomic and from the beginning I've got a problem with battery drain. This night I charged phone to 100% and during the night I plugged out the charger. NFC / WIFI / DATA / GPS OFF. After 1,5h from 100% battery drain to 93% !
https://imgur.com/a/kN5IO
From what I see WIFI running whole the time (even it was off) + phone is not going to deep sleep whole time but stays 518,4Mhz for long time
Any ideas what to do ?
I found that one of miui apps captures tcp dump. If you look under the /MIUI/debug_log/common you will find 2 PCAP files called tcpdump.pcap0 and tcpdump.pcap1
I think that miui findphone application creates it, because i have set disabled "find my phone" and cleared data of these app and files did not appear again
I'm not on MIUI.
So... you can have enabled "always scan" option in wifi setting.
https://www.reddit.com/r/GooglePixel/comments/5t93e4/turned_off_wifi_and_bluetooth_scanning_battery/
Ok I have disabled this option.
Lets see after some time, but I feel like something is keeping my phone awake and it is not getting to deep sleep all the time..
There is a module for magisk that force Doze.
SkubiDoo said:
Ok I have disabled this option.
Lets see after some time, but I feel like something is keeping my phone awake and it is not getting to deep sleep all the time..
Click to expand...
Click to collapse
Try turning off nfc.
I have installed crDroid and looks like drain gone. Just NFC has to be off.

Categories

Resources