Related
I noticed my abttery life was getting bad and in the battery use details I saw the a lot of wake time when the screen is off. So got Betterbatterystats and tried to locate the app causing the partial wakelocks. Here is the history of wakelocks:
Wakelocks
=========
*backup* (Android System): 49 m 23 s (2963 s) Count:112 25.2%
AlarmManager (Android System): 41 s (41 s) Count:784 0.4%
*wifi* (Android System): 39 s (39 s) Count:88 0.3%
ActivityManager-Launch (Android System): 16 s (16 s) Count:46 0.1%
LockerService (com.teslacoilsw.widgetlocker.WidgetLocker): 15 s (15 s) Count:8 0.1%
*sync* (com.google.android.gm.Gmail): 9 s (9 s) Count:5 0.1%
FacebookService (com.facebook.katana.Facebook): 7 s (7 s) Count:5 0.1%
sleep_broadcast (Android System): 5 s (5 s) Count:76 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 5 s (5 s) Count:10 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 4 s (4 s) Count:5 0.0%
BackgroundFriendService (com.google.android.apps.maps.Maps): 4 s (4 s) Count:7 0.0%
GTALK_CONN (Google Services): 3 s (3 s) Count:68 0.0%
NotificationService (Android System): 3 s (3 s) Count:114 0.0%
SMSDispatcher (Dialer): 2 s (2 s) Count:1 0.0%
show keyguard (Android System): 2 s (2 s) Count:8 0.0%
com.bellshare.util.WakefulIntentService (com.bellshare.beweather.BeWeather Pro): 1 s (1 s) Count:1 0.0%
LocationReportingService (com.google.android.apps.maps.Maps): 1 s (1 s) Count:28 0.0%
NetworkLocationCacheUpdater (com.google.android.apps.maps.Maps): 1 s (1 s) Count:14 0.0%
*network-location* (com.bellshare.beweather.BeWeather Pro): 1 s (1 s) Count:3 0.0%
Checkin Service (Google Services): 1 s (1 s) Count:77 0.0%
*vibrator* (Android System): 1 s (1 s) Count:106 0.0%
Seems to be the backup is causing the problem. I thought it might have to do with whats syncing, so I disabled everything that syncs except my gmail and calendar, but the problem still persists. Anyone have any idea what could be causing the problem?
Hi there... i have a problem with my battery life, can you guys help me?
I'm on franco#13.1 and aokp build 19. As you can see I wasn't using the phone much...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
===================
General Information
===================
BetterBatteryStats version: 1.5.1.0
Creation Date: 2012-01-22
21:03:34
Statistic Type: (0) Since Charged
Since 6 h 58 m 26 s
VERSION.RELEASE: 4.0.3
BRAND: google
DEVICE: maguro
MANUFACTURER: samsung
MODEL: Galaxy Nexus
===========
Other Usage
===========
Awake (): 6 h 58 m 26 s (25106 s) Ratio:
100.0%
Wifi On (): 59 m 5 s (3545 s) Ratio: 14.1%
Screen On (): 4 m 45 s (285 s) Ratio: 1.1%
Phone On (): 2 m 12 s (132
s) Ratio: 0.5%
=========
Wakelocks
=========
RILJ (Telefon): 2 m 12 s (132 s) Count:2800 0.5%
SyncLoopWakeLock (Android-
System): 1 s (1 s) Count:1396 0.0%
AlarmManager (Android-System): 34 s (34 s) Count:1001 0.1%
GTALK_CONN (Google-
Dienste): 2 s (2 s) Count:612 0.0%
ConnectivityService (Android-System): 1 s (1 s) Count:331 0.0%
*backup* (Android-
System): 1 m 5 s (65 s) Count:318 0.3%
SCREEN_FROZEN (Android-System): 1 s (1 s) Count:294 0.0%
DHCP (Android-System): 1
s (1 s) Count:290 0.0%
sleep_broadcast (Android-System): 11 s (11 s) Count:288 0.0%
GpsLocationProvider (Android-
System): 1 s (1 s) Count:258 0.0%
*sync*_com.android.browser_Account {[email protected], type=com.google} (Google-
Dienste): 9 s (9 s) Count:249 0.0%
GOOGLE_C2DM (Google-Dienste): 4 s (4 s) Count:227 0.0%
*sync*_subscribedfeeds_Account
{[email protected], type=com.google} (Google-Dienste): 4 s (4 s) Count:199 0.0%
[email protected]/android_talk82967892be2a (Google-Dienste): 1 m 41 s (101 s) Count:193 0.4%
ActivityManager-Launch (Android-System): 10 s (10 s) Count:190 0.0%
*sync*_com.android.contacts_Account
{[email protected], type=com.google} (Google-Dienste): 4 s (4 s) Count:169 0.0%
NetworkStats (Android-System): 4 s
(4 s) Count:164 0.0%
Checkin Service (Google-Dienste): 1 s (1 s) Count:158 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google-Dienste): 1 m 31 s (91 s) Count:91 0.4%
*sync*_com.android.calendar_Account {[email protected], type=com.google} (com.google.android.calendar.Kalender): 34 s
(34 s) Count:55 0.1%
*sync*_com.android.contacts_Account {[email protected], type=com.facebook.auth.login}
(com.facebook.katana.Facebook): 5 s (5 s) Count:17 0.0%
GmailProviderProviderChangedBroadcastWakeLock
(com.google.android.gm.Gmail): 2 s (2 s) Count:13 0.0%
FacebookService (com.facebook.katana.Facebook): 21 s (21 s)
Count:11 0.1%
*sync*_gmail-ls_Account {[email protected], type=com.google} (com.google.android.gm.Gmail): 19 s (19 s)
Count:11 0.1%
Proximity Partial (Android-System): 2 s (2 s) Count:11 0.0%
AudioOut_1 (1013): 36 s (36 s) Count:10 0.1%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 13 s (13 s) Count:8 0.1%
GSM (Telefon): 56 s (56 s) Count:5
0.2%
*sync*_com.google.android.apps.plus.content.EsGooglePhotoProvider_Account {[email protected], type=com.google}
(com.google.android.apps.plus.Google+): 6 s (6 s) Count:5 0.0%
================
Kernel Wakelocks
================
"wlan_wake" (): (0 s) Cnt:(c/wc/ec)1446/0/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)1125/0/0 0.0%
"secril_fmt-interface"
(): (0 s) Cnt:(c/wc/ec)379/0/0 0.0%
"twl6030 adc" (): (0 s) Cnt:(c/wc/ec)170/0/0 0.0%
"mipi_link" (): 37 s (37 s) Cnt:
(c/wc/ec)123/0/0 5.0%
"wlan_rx_wake" (): 15 s (15 s) Cnt:(c/wc/ec)51/0/51 2.1%
"alarm" (): (0 s) Cnt:(c/wc/ec)46/0/0
0.0%
"max17040-battery" (): (0 s) Cnt:(c/wc/ec)16/0/0 0.0%
"PowerManagerService" (): 4 m 46 s (286 s) Cnt:(c/wc/ec)
12/0/0 38.6%
"radio-interface" (): 2 s (2 s) Cnt:(c/wc/ec)12/0/0 0.3%
"gpio_input" (): (0 s) Cnt:(c/wc/ec)12/0/0 0.0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)5/0/0 0.0%
"vbus-tuna_otg" (): 7 m 51 s (471 s) Cnt:(c/wc/ec)1/0/0 63.5%
=========
Processes
=========
android.process.acore (com.maize.digitalClock.Digitaluhr Widget): Sys: (0 s) Us: (0 s)
Starts: 7
com.google.android.apps.maps:NetworkLocationService (com.google.android.apps.maps.Maps): Sys: (0 s) Us: (0 s)
Starts: 6
com.android.contacts (Android Core Apps): Sys: (0 s) Us: (0 s) Starts: 2
kworker/u:4 (0): Sys: 6 s (6 s) Us:
(0 s) Starts: 0
kworker/u:3 (0): Sys: 3 s (3 s) Us: (0 s) Starts: 0
jrcud (0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
kworker/u:0 (0): Sys: 7 s (7 s) Us: (0 s) Starts: 0
kworker/u:2 (0): Sys: 8 s (8 s) Us: (0 s) Starts: 0
kworker/0:2
(0): Sys: 1 s (1 s) Us: (0 s) Starts: 0
kworker/u:1 (0): Sys: 5 s (5 s) Us: (0 s) Starts: 0
surfaceflinger (Android-
System): Sys: 2 s (2 s) Us: 1 s (1 s) Starts: 0
*wakelock* (Telefon): Sys: 2 s (2 s) Us: 1 s (1 s) Starts: 0
rild
(Telefon): Sys: 1 s (1 s) Us: (0 s) Starts: 0
=========
Alarms
=========
android (): Wakeups: 4
com.facebook.katana ():
Wakeups: 3
com.google.android.gsf (): Wakeups: 1
com.google.android.location (): Wakeups: 1
com.google.android.apps.walletnfcrel (): Wakeups: 1
com.google.android.apps.maps (): Wakeups: 1
com.android.providers.calendar (): Wakeups: 1
========
Services
========
Active since: The time when the service was first
made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the
service (either explicit requests to start it or clients binding to it)
See
http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
com.google.process.gapps
(com.google.android.location.internal.server.NetworkLocationService)
Active since: 36 s
Last activity: 36 s
Crash
count:0
com.android.smspush (com.android.smspush.WapPushManager)
Active since: 36 s
Last activity: 36 s
Crash
count:0
android.process.media (com.android.providers.media.MtpService)
Active since: 36 s
Last activity: 36 s
Crash
count:0
ch.iAgentur.i20Min (com.urbanairship.push.PushService)
Active since: 47 s
Last activity: 47 s
Crash count:0
com.google.process.gapps (com.google.android.location.NetworkLocationService)
Active since: 35 s
Last activity: 35 s
Crash count:0
system (com.google.android.backup.BackupTransportService)
Active since: 34 s
Last activity: 34 s
Crash count:0
com.google.android.talk (com.google.android.videochat.VideoChatService)
Active since: 42 s
Last
activity: 42 s
Crash count:0
com.asksven.betterbatterystats (com.asksven.betterbatterystats.BetterBatteryStatsService)
Active since: 47 s
Last activity: 47 s
Crash count:0
com.google.android.apps.maps:NetworkLocationService
(com.google.android.location.internal.server.NetworkLocationService)
Active since: 45 s
Last activity: 45 s
Crash
count:0
com.whatsapp (com.whatsapp.ExternalMediaManager)
Active since: 49 s
Last activity: 49 s
Crash count:0
com.skcc.gtec.otaproxy (com.skcc.gtec.otaproxy.StartService)
Active since: 42 s
Last activity: 11 m 39 s
Crash
count:0
android.process.acore (com.maize.digitalClock.UpdateService)
Active since: 50 s
Last activity: 50 s
Crash
count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.PushMessagingRegistrar)
Active since: 42 s
Last
activity: 11 m 39 s
Crash count:0
com.android.phone (com.android.phone.BluetoothHeadsetService)
Active since: 36 s
Last activity: 36 s
Crash count:0
com.android.inputmethod.latin (com.android.inputmethod.latin.LatinIME)
Active since:
35 s
Last activity: 35 s
Crash count:0
com.android.systemui (com.android.systemui.ImageWallpaper)
Active since: 35 s
Last activity: 35 s
Crash count:0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 34 s
Last activity: 34 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 42 s
Last activity: 54 s
Crash count:0
com.facebook.katana (com.facebook.katana.service.UploadManager)
Active since: 51 s
Last activity: 54 s
Crash count:0
com.whatsapp (com.whatsapp.messaging.MessageService)
Active
since: 46 s
Last activity: 46 s
Crash count:0
You have a problem with your reception. The graph is showing a lot of time with weak or no signal, which can really drain the battery.
well ok that was when i was at the movies, but still, the rate of battery drain does not change after i get normal signal strenght, so that can't be it... shouldnt there be parts with almost no batterydrain (like 1%/hour) while in deepsleep, which wold be reflected as almost horizontal lines?
You have a problem that is bad battery life, but i dont know the solution. During sleep it should be flat line.
If your phone isn't going in to deep sleep, then no there won't be level parts of the graph.. your phone is not going into deep sleep. There is probably an app that is killing your battery.
try to leave unchecked google localization service (gps or wifi)... every now and then it starts to check and that could be the reason (amoong others program/service you have installed); hopelly, try also to undervolt/underclock with custon kernel and do not use full brightness (it's 1st cause of battery drain, obviously not during sleep) while phone using...
It's my personal experience that you should try one thing at a time and start with the obvious stuff.
Your phone standby is higher than your Android OS so start with there. As others have pointed out, that huge chunk of no reception contributes a lot to your drain. Since you said you were at a movie during that time, evaluate your battery life for one more day when you don't have a huge chunk of a reception gap.
I can't see (but I'm no expert) anything hugely glaring on your BB Stats that screams drain. Your screen-off awake on your battery graph looks rather normal sans the reception gap. Still doesn't explain why you had 6 hours of awake time but I'm almost betting that it's something common.
Also try opening camera, hit back to close out of it.
Also try opening camera, hit back to close out of it.
Click to expand...
Click to collapse
That could be also the problem (and probably affect more tha the other things listed), forget to mention. If you know, this is a ics related bug or a gtalk bug?
I have a similar problem although it is my rild.
I downloaded System panel and it says 8.9% constantly and it is the only source of my battery drain, not causing it to go into a deep sleep.
How do I fix this issue?
im using a custom kernel (Franco) if you dont have one out i suggest one for battery saving
I wonder if there are batch of bad batteries, since my wife phone doesnt do it, while mine has been draining quite a lot too.
kkhanmd said:
I wonder if there are batch of bad batteries, since my wife phone doesnt do it, while mine has been draining quite a lot too.
Click to expand...
Click to collapse
I had a bad battery, returned it for a new phone
Sent from my Galaxy Nexus using Tapatalk
i thought 6-8 hours was pretty normal for this phone? most def with the LTE version..
i got 8hours today with my GSM.. kinda bad..but.. hey
YoungAceAtlanta said:
i thought 6-8 hours was pretty normal for this phone? most def with the LTE version..
i got 8hours today with my GSM.. kinda bad..but.. hey
Click to expand...
Click to collapse
With 4.0.4 on 4g with moderate to heavy use got 15 Hours Yesterday Big Improvement from my 8-9 hours with light use
pollardhimself said:
With 4.0.4 on 4g with moderate to heavy use got 15 Hours Yesterday Big Improvement from my 8-9 hours with light use
Click to expand...
Click to collapse
when talking about battery life, is essential post the screen time..because you can get 15 or also 30 hours, but if ur screen time is 10 minutes (for example), mean ur screen was always off and u didn't used ur phone
andQlimax said:
when talking about battery life, is essential post the screen time..because you can get 15 or also 30 hours, but if ur screen time is 10 minutes (for example), mean ur screen was always off and u didn't used ur phone
Click to expand...
Click to collapse
Crap, Didn't grab a screenshot of that last night. Ill get one tonight, I just know I saw a big improvement in battery life overall.
So I was using an app called time recording, for hours I spend at work. It has ads in the background as it is free. Today I closed the app from the multitasking button, plus disabled google + esp the photo transfer and my battery life is still more than 90% after 6 hours of use. Thank god its solved.
andQlimax said:
when talking about battery life, is essential post the screen time..because you can get 15 or also 30 hours, but if ur screen time is 10 minutes (for example), mean ur screen was always off and u didn't used ur phone
Click to expand...
Click to collapse
What I Consider Heavy use today
do u have the extended battery?
I'm using a second hand Desire HD. (Love it! Love the support through XDA and its wonderful devs and users) I've bought the phone S-OFF with ARHD 6.x installed after which I flashed ARHD 7.0.4 used that for a few months and running AOSP ICS and CM10 nightlies the last couple of weeks.
I've been measureing battery usage using currentwidget ever since I first acquired the phone. On every ROM the phone uses about 25mA in deep sleep and airplane mode. With 2G and WiFithe power usage is about the same, I rarely use 3g/data. I use "better battery stats" and I know that the phone is indeed in deep sleep for most of the day. In deep sleep standby with Wifi on and only 2G I lose about 4% battery every hour.
Radio: 12.65.60.29_26.14.04.28_M
ROM: cfx CM10 nightly 1909 (but problem is on every rom)
Ofcourse I understand that with a 2yr old battery, I need to buy a new battery. But I'm guessing standby time will not really increase, because of the power usage in deep sleep.
Is this normal? I see a lot of reports showing CurrentWidget with under 5mA deepsleep. I always measure 25mA and I'm sure the phone is in deepsleep.
Hi, i recognized that too. During night, with alarm set to enabled, i sometimes (!!!) get a drain of 30% in 8 hours. Normally there is a maximum drain of 7-8% witch is very good for me. I cant reproduce that, becouse one night its normal the other night it drains like hell...
vliegnerd said:
I'm using a second hand Desire HD. (Love it! Love the support through XDA and its wonderful devs and users) I've bought the phone S-OFF with ARHD 6.x installed after which I flashed ARHD 7.0.4 used that for a few months and running AOSP ICS and CM10 nightlies the last couple of weeks.
I've been measureing battery usage using currentwidget ever since I first acquired the phone. On every ROM the phone uses about 25mA in deep sleep and airplane mode. With 2G and WiFithe power usage is about the same, I rarely use 3g/data. I use "better battery stats" and I know that the phone is indeed in deep sleep for most of the day. In deep sleep standby with Wifi on and only 2G I lose about 4% battery every hour.
Radio: 12.65.60.29_26.14.04.28_M
ROM: cfx CM10 nightly 1909 (but problem is on every rom)
Ofcourse I understand that with a 2yr old battery, I need to buy a new battery. But I'm guessing standby time will not really increase, because of the power usage in deep sleep.
Is this normal? I see a lot of reports showing CurrentWidget with under 5mA deepsleep. I always measure 25mA and I'm sure the phone is in deepsleep.
Click to expand...
Click to collapse
That does seem a little high. Do you have BBS screenshots of the wakelocks, alarms and other?
Will post screenshot of bbs 2morrow
Sent from my Desire HD using xda app-developers app
I didn't bring my mini-USB cable so no screenshot, but here is my BBS dumpfile:
80% deepsleep. However, I now notice the screen is on for 45min and the phone has been awake for 1h20m.
I wonder about "Deleted_wakelocks" in de partial wakelocks stats. This is the first time I've seen these (in codefireX CM10 nightly). Before I'm pretty sure these where WLAN (wifi) wakelocks.
Code:
===================
General Information
===================
BetterBatteryStats version: 1.10.5.0
Creation Date: 2012-09-24 13:48:38
Statistic Type: (3) Since Unplugged
Since 6 h 58 m 20 s
VERSION.RELEASE: 4.1.1
BRAND: htc_wwe
DEVICE: ace
MANUFACTURER: HTC
MODEL: Desire HD
OS.VERSION: 3.0.43KangBang-Kernel-g6cfd21c
BOOTLOADER: 0.85.0024
HARDWARE: spade
FINGERPRINT: google/yakju/maguro:4.1.1/JRO03L/330937:user/release-keys
ID: JRO03L
TAGS: test-keys
USER: synergye
PRODUCT: htc_ace
RADIO: 12.65.60.29U_26.14.04.28_M
Rooted: true
============
Battery Info
============
Level lost [%]: 54 Bat.: 54% (100% to 46%)
Voltage lost [mV]: 431 (4152-3721)
===========
Other Usage
===========
Deep Sleep (): 5 h 37 m 34 s (20254 s) Ratio: 80,7%
Awake (): 1 h 20 m 50 s (4850 s) Ratio: 19,3%
No Data Connection (): 6 h 58 m 15 s (25095 s) Ratio: 100,0%
No or Unknown Signal (): 6 h 58 m 15 s (25095 s) Ratio: 100,0%
Wifi On (): 5 h 11 m 49 s (18709 s) Ratio: 74,5%
Wifi Running (): 5 h 11 m 36 s (18696 s) Ratio: 74,5%
Screen On (): 43 m 56 s (2636 s) Ratio: 10,5%
=========
Wakelocks
=========
AlarmManager (com.manor.currentwidget.CurrentWidget): 12 m 50 s (770 s) Count:32 3,1%
AlarmManager (com.google.android.googlequicksearchbox.Google Zoeken): 11 m 10 s (670 s) Count:37 2,7%
AlarmManager (Android-systeem): 10 m 48 s (648 s) Count:1100 2,6%
ConnectivityService (Android-systeem): 8 m 57 s (537 s) Count:1109 2,1%
SyncLoopWakeLock (Android-systeem): 8 m 13 s (493 s) Count:1321 2,0%
Event Log Service (Google Services): 5 m 23 s (323 s) Count:192 1,3%
*backup* (Android-systeem): 5 m 19 s (319 s) Count:592 1,3%
AlarmManager (Google Services): 4 m 3 s (243 s) Count:708 1,0%
show keyguard (Android-systeem): 2 m 43 s (163 s) Count:22 0,7%
ActivityManager-Launch (Android-systeem): 2 m 33 s (153 s) Count:377 0,6%
*sync*_gmail-ls_Account {[email protected], type=com.google} (com.google.android.gm.Gmail): 2 m 29 s (149 s) Count:50 0,6%
Sidekick_CalendarIntentService (com.google.android.googlequicksearchbox.Google Zoeken): 1 m 58 s (118 s) Count:68 0,5%
Genie (com.google.android.apps.genie.geniewidget.Nieuws en weer): 1 m 32 s (92 s) Count:4 0,4%
AlarmManager (com.google.android.apps.genie.geniewidget.Nieuws en weer): 1 m 6 s (66 s) Count:2 0,3%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 60 s (60 s) Count:65 0,2%
NetworkLocationLocator (Google Services): 58 s (58 s) Count:75 0,2%
AlarmManager (com.whatsapp.WhatsApp): 48 s (48 s) Count:10 0,2%
AudioOut_2 (1013): 47 s (47 s) Count:6 0,2%
AlarmManager (com.google.android.apps.maps.Maps): 40 s (40 s) Count:273 0,2%
EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Zoeken): 36 s (36 s) Count:82 0,1%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 23 s (23 s) Count:139 0,1%
sleep_broadcast (Android-systeem): 21 s (21 s) Count:532 0,1%
CallerInfoCache (Telefoon): 19 s (19 s) Count:1 0,1%
GTALK_CONN (Google Services): 18 s (18 s) Count:552 0,1%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 16 s (16 s) Count:9 0,1%
DownloadManager (Media): 15 s (15 s) Count:2 0,1%
[email protected]/android_talk8999f6a5aa06 (Google Services): 13 s (13 s) Count:200 0,1%
ActivityManager-Sleep (Android-systeem): 13 s (13 s) Count:1132 0,1%
SCREEN_FROZEN (Android-systeem): 12 s (12 s) Count:574 0,0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Agenda-opslag): 10 s (10 s) Count:6 0,0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 8 s (8 s) Count:574 0,0%
DropboxCpuOnlyWakeLock (com.dropbox.android.Dropbox): 7 s (7 s) Count:3 0,0%
Checkin Service (Google Services): 7 s (7 s) Count:602 0,0%
RILJ (Telefoon): 5 s (5 s) Count:368 0,0%
*sync*_com.android.contacts_Account {[email protected], type=com.google} (Google Services): 5 s (5 s) Count:77 0,0%
*sync*_com.android.calendar_Account {[email protected], type=com.google} (com.google.android.syncadapters.calendar.Google Agenda synchroniseren): 5 s (5 s) Count:3 0,0%
WifiStateMachine (Android-systeem): 3 s (3 s) Count:602 0,0%
Sidekick_TrafficIntentService_onHandleIntent (com.google.android.googlequicksearchbox.Google Zoeken): 3 s (3 s) Count:83 0,0%
NetworkStats (Android-systeem): 3 s (3 s) Count:85 0,0%
*sync*_com.google.android.apps.docs_Account {[email protected], type=com.google} (com.google.android.apps.docs.Drive): 1 s (1 s) Count:3 0,0%
DocsSyncAdapter (com.google.android.apps.docs.Drive): 1 s (1 s) Count:1 0,0%
GpsLocationProvider (Android-systeem): 1 s (1 s) Count:439 0,0%
================
Kernel Wakelocks
================
"deleted_wake_locks" (): 1 h 25 m 49 s (5149 s) Cnt:(c/wc/ec)71114/0/3490 20,5%
"PowerManagerService" (): 13 m 56 s (836 s) Cnt:(c/wc/ec)1570/0/0 3,3%
"alarm_rtc" (): 2 m 49 s (169 s) Cnt:(c/wc/ec)1282/0/23 0,7%
"SMD_DS" (): 1 m 1 s (61 s) Cnt:(c/wc/ec)686/0/686 0,2%
"alarm" (): 22 s (22 s) Cnt:(c/wc/ec)990/0/0 0,1%
"audio_pcm" (): 13 s (13 s) Cnt:(c/wc/ec)4/0/0 0,1%
"audpp" (): 13 s (13 s) Cnt:(c/wc/ec)4/0/0 0,1%
"ds2746-battery" (): 6 s (6 s) Cnt:(c/wc/ec)540/0/0 0,0%
"KeyEvents" (): 2 s (2 s) Cnt:(c/wc/ec)14407/0/0 0,0%
"mmc1_detect" (): 2 s (2 s) Cnt:(c/wc/ec)7/0/7 0,0%
"radio-interface" (): 1 s (1 s) Cnt:(c/wc/ec)73/0/0 0,0%
"rpcrotuer_smd_xprt" (): 1 s (1 s) Cnt:(c/wc/ec)11137/403/0 0,0%
"rpc_read" (): (0 s) Cnt:(c/wc/ec)5698/0/0 -0,0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)92/0/0 0,0%
"gpio_input" (): (0 s) Cnt:(c/wc/ec)93/26/0 0,0%
"aic3254_suspend_lock" (): (0 s) Cnt:(c/wc/ec)8/0/0 0,0%
"port_list" (): (0 s) Cnt:(c/wc/ec)5128/0/0 0,0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
149,76 MHz (): 44 m 38 s 10,7%
245,76 MHz (): 0,0%
341,64 MHz (): 8 m 56 s 2,1%
614,4 MHz (): 6 m 42 s 1,6%
768 MHz (): 2 m 29 s 0,6%
806,4 MHz (): 2 m 17 s 0,5%
1,02 GHz (): 15 m 47 s 3,8%
1,2 GHz (): 0,0%
1,31 GHz (): 0,0%
1,4 GHz (): 0,0%
1,52 GHz (): 0,0%
1,61 GHz (): 0,0%
1,69 GHz (): 0,0%
1,77 GHz (): 0,0%
1,84 GHz (): 0,0%
1,92 GHz (): 0,0%
2 GHz (): 0,0%
2,02 GHz (): 0,0%
Deep Sleep (): 5 h 37 m 34 s 80,7%
==================
Reference overview
==================
Custom: null
Since charged: Reference since_charged_ref created 3 d 7 h 44 m 51 s (Wl: 0 elements; KWl: 27elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 7 elements; CPU: 19 elements)
Since screen off: null
Since unplugged: Reference since_unplugged_ref created 3 d 7 h 44 m 51 s (Wl: 0 elements; KWl: 27elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 7 elements; CPU: 19 elements)
Since boot: null
vliegnerd said:
I didn't bring my mini-USB cable so no screenshot, but here is my BBS dumpfile:
80% deepsleep. However, I now notice the screen is on for 45min and the phone has been awake for 1h20m.
I wonder about "Deleted_wakelocks" in de partial wakelocks stats. This is the first time I've seen these (in codefireX CM10 nightly). Before I'm pretty sure these where WLAN (wifi) wakelocks.
Click to expand...
Click to collapse
Deleted wakelocks are from uninstalled programs. Reboot and they should be gone.
Try enabling root in BBS settings; I'd like to see Alarms.
bananagranola said:
Deleted wakelocks are from uninstalled programs. Reboot and they should be gone.
Try enabling root in BBS settings; I'd like to see Alarms.
Click to expand...
Click to collapse
Reboot, and they are still there! (or better they return).
I've made screenshots of BBS since reboot. I just turned on root, so no Alarms yet. Will post Alarms as soon as it show something usefull.
Location Manager is using way to much battery. I'll turn that off. (But it does not change the battery drain in deep sleep, it only holds the phone out of deepsleep). Anyway, I realise now that the apps on my "daily driver" rom interfere with this test. I'll try to install a clean GB rom tonight and only install BBS and current widget.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
vliegnerd said:
Reboot, and they are still there! (or better they return).
I've made screenshots of BBS since reboot. I just turned on root, so no Alarms yet. Will post Alarms as soon as it show something usefull.
Location Manager is using way to much battery. I'll turn that off. (But it does not change the battery drain in deep sleep, it only holds the phone out of deepsleep). Anyway, I realise now that the apps on my "daily driver" rom interfere with this test. I'll try to install a clean GB rom tonight and only install BBS and current widget.
View attachment 1351075
View attachment 1351076
View attachment 1351077
Click to expand...
Click to collapse
More information about deleted_wake_locks here. Your LocationManagerService under Partial Wakelocks also seems rather high; try turning off Settings -> Location Services -> "Google's Location Service", "GPS satellites," and "Location and & Google Search." Looks like CurrentWidget is also creating quite a few wakelocks; try disabling/uninstalling that.
Thanks for the help so far.
I just full-wiped and installed CM7.2 (stable) and gapps-gb. After bootup I only downloaded BBS and current widget from the market. Left locations off. Phone is on a shelf in airplane mode now. Will see in a couple of hours how much this clean ROM uses. Will post.
vliegnerd said:
Is this normal? I see a lot of reports showing CurrentWidget with under 5mA deepsleep. I always measure 25mA and I'm sure the phone is in deepsleep.
Click to expand...
Click to collapse
I had about 25-30mA deep sleep on my DHD, reported it as malfunctioning and got it fixed (by replacing just about everything but the battery lid), now deep sleep about 1-4mA. In any way, the phone uses 150-300mA every now and then which drains the battery quite a bunch anyway. Stock rom.
Installed CM7.2-stable-ace and nothing but gapps (for market) BBS and currentwidget.
BBS has no alarms at all and very few (partial) wakelocks. Less than 15s over 10hours.
20% battery loss over a 10h deep sleep. Fantastic for me, but good enough? Seems reasonable.
Currentwidget reports 26mA during the night. This still seems high. But standby time is reasonable.
(I had a GPS wakelock after fresh install, keeping the phone in lowest freq 2xxMhz with screen off. So 100% awake. Currentwidget also reported 26mA in this case! But much more battery loss per hour. Seems currentwidget/phone cannot measure the low current reliably).
BBS screenshot
EDIT: BBS log removed. I used "dumpfile" *after* I attached USB for screenshots... *sigh*. Anyway, There were no alarms and only 15s of partial- and normal wakelocks. In the screenshot it is obvious that the phone was in deep sleep continiously.
vliegnerd said:
Installed CM7.2-stable-ace and nothing but gapps (for market) BBS and currentwidget.
BBS has no alarms at all and very few (partial) wakelocks. Less than 15s over 10hours.
20% battery loss over a 10h deep sleep. Fantastic for me, but good enough? Seems reasonable.
Currentwidget reports 26mA during the night. This still seems high. But standby time is reasonable.
(I had a GPS wakelock after fresh install, keeping the phone in lowest freq 2xxMhz with screen off. So 100% awake. Currentwidget also reported 26mA in this case! But much more battery loss per hour. Seems currentwidget/phone cannot measure the low current reliably).
Click to expand...
Click to collapse
It looks like BBS only recorded 1 minute and 44 seconds of time.
bananagranola said:
It looks like BBS only recorded 1 minute and 44 seconds of time.
Click to expand...
Click to collapse
I removed the BBS log; I attached the USB (for screenshots) before I used dumpfile in BBS. *sigh*.
vliegnerd said:
I removed the BBS log; I attached the USB (for screenshots) before I used dumpfile in BBS. *sigh*.
Click to expand...
Click to collapse
20% down in 10 hours is not bad. When you get a chance, get the BBS log or screenshots for a longer time period. Make sure you gave it root access in settings.
Hey folks,
I am dealing with a weird battery drain on my HTC Desire. First few facts about my device.
- It is running the latest radio
- It is running the Runnymede AIO V6.0.4.3 S.E
- It has the kernel gingercake 0.9 AVS
- No overclock
- smartass v2
- deadline I/O scheduler
- No change between a 2 year old avarage used battery and a brand new original battery
- Phone signal strength is same (4 to 5 bars)
- At both places its next to a PC
- No change in the settings what-so-ever during the 2 positions I am comparing and describing now...
-- The settings are:
--- WiFi on and connected (in both cases. Same signal strength as well)
--- No mobile data on
--- No difference of usage (waking phone up to check clock, notifications, what-so-ever)
--- No GPS
--- No Bluetooth
When I am at home and the phone is idling next to me on the mousepad it is losing maximum 10% - 20% from ~ 19:30 to 08:30. Between 07:30 and 08:30 my alarm goes of every 5 min for ~ 10 sec (yes, I have problems stepping out of the bed ). Looking at the battery history in Spare Parts+ the battery bar is falling slightly during the time.
So far no big deal. Actually it is a pretty good result and the phone would last few days like this... If I would not need to go to work...
And there is my problem. During work (~ 10:00 - 19:00) the phone lies next to me on the table. Same usage as at home (except the alarm, of course ). The battery loses 40% - 50% of battery power during that time! Just for lying around! Looking at the battery history visualizes really good when I am at home and at work. At work the battery bar is dropping like hell. Close to straight down da frelling hill! Comparing home and work it is pretty obvious when I am where.
I tried so many things but there is no real difference in the draining.
What I could observe (with the app G-Mon):
- In both cases I am locked to 1 particular tower (different towers but not switching between others)
- In both cases the locked on tower is about -60dBm to -70dBm
- At home there are 5 to 6 neighbour cells (one has so bad signal that its coming and going)
- At work there are 2 to 3 neighbour cells (same as above)
Does ANYONE has ANY idea what the frell is going on? why does it drop so hard at work and not at home? It is also not dropping so much if I am carrying it around or at my parents place (at my parents place the dropping is as much as at home).
All 3 places are not in the same city and at least some kilometers away.
Maybe someone else had the same issue and could figure out a solution. I am totally lost now. I tried soooo many things now and I am tired of that...
Kind regards,
Sebastian
Edit:
To further add to it... The ROM and device itself run very smooth without any other issue. Its just the battery drain that keeps frelling me.
The phone is stressed at work
The only thing thing that changes from home to work is the network. Maybe you have a 2g network at home, and a 3g network at work. It's the only thing I can think of. I have never heard of battery drainage due to location.
In what conditions are you keeping the phone at work? High or low temperature could influence the battery life, or you keep it in the sun.
Thanks for the reply, abaaaabbbb63.
I also tried this and set the phone to GSM only (so it connects to EDGE only in both cases). I now changed it back to auto and will observe what happens.
It has the exact same conditions at work and home. No direct sun and close to the same temp. So no difference here neither.
Edit:
I added a screenshot to show what I mean. The peak in the middle is because I had to connect the phone to my PC to transfer some files. The more heavy drop in the last 3rd part is because I used it for MP3 player. The almost-flat line after that is... you guess it... the home part. The rest TILL the heavy drop shows the phone at work.
Again. There is no difference between the locations except the WiFi AP and the cell towers its connected to. I could pull out my hair because of that!
I made a second screenshot. I had to charge the phone at work so I charged it to 100% and then plugged it out. The first half on the screenshot is at work and the other half is just at home.
Please help me... I am almost out of hair...
It alomost looks like its draining while its NOT active... but I wouldnt understand that even less...
Blockberd said:
I made a second screenshot. I had to charge the phone at work so I charged it to 100% and then plugged it out. The first half on the screenshot is at work and the other half is just at home.
Please help me... I am almost out of hair...
It alomost looks like its draining while its NOT active... but I wouldnt understand that even less...
Click to expand...
Click to collapse
Install "Better Battery Stats" application. You can find the apk in the apps section. It will tell you exactly what is eating your battery and catch the culprit.
For instance in my case, Google currents was crunching my battery. I uninstalled it and battery is working super fine from then.
dvsk69 said:
Install "Better Battery Stats" application. You can find the apk in the apps section. It will tell you exactly what is eating your battery and catch the culprit.
For instance in my case, Google currents was crunching my battery. I uninstalled it and battery is working super fine from then.
Click to expand...
Click to collapse
Hey,
thanks for the suggestion of the app. I installed it now and charing the phone to 100% so I can observe it in detail again. Will post details later.
But I have a small concern... If there is really an app draining the battery then a) the active bar in my screenshots would need to be blue during the complete drain part (at work) and b) I would have battery draining at home, too (if it would be an app).
Correct me if I might be wrong here...
Again... I only move the phone from home to work and from work to home without switching something on or off.
Blockberd said:
I made a second screenshot. I had to charge the phone at work so I charged it to 100% and then plugged it out. The first half on the screenshot is at work and the other half is just at home.
Please help me... I am almost out of hair...
It alomost looks like its draining while its NOT active... but I wouldnt understand that even less...
Click to expand...
Click to collapse
Well the only thing I can see from here is that network signal had an effect at the drain. As soon as the solid green bar cuts off for the faded one, the battery drain improved significantly. What's weird though is that I often believe seeing green bars as good signal. However if it was good 3G signal then that might be something.
stankyou said:
Well the only thing I can see from here is that network signal had an effect at the drain. As soon as the solid green bar cuts off for the faded one, the battery drain improved significantly. What's weird though is that I often believe seeing green bars as good signal. However if it was good 3G signal then that might be something.
Click to expand...
Click to collapse
Yes. I also noticed that one. The thing is that at work I have only EDGE and at home I am able to login into HSDPA cell towers. But I dont use the mobile data at all. The phone is only connected to the cell towers for normal calls.
But the strange thing is that even if I force EDGE (or GSM) in the settings of the mobile connection it behaves the same way. Even though its connected through EDGE in both situations.
Maybe I am doing something wrong in my testing or whatever...
Anyway... battery is fully charged and BBS can start tracking for the next 4 hours at work now. Lets see.
So. I am at home again and had it running again as usual. Now with BBS.
I uploaded some screens again. You can see in the battery history that the drain is not really bound to the signal (notice the drain stopping at the end of the bar but the signal bar is not changing together with it).
If you need other screenshots or information from BBS, please do let me know what exactly you would need from that app.
Post the partial wakelocks since unplugged screens and stats, they're the most useful in determining if anything is keeping your phone awake.
Ok. Attached are the screen from the morning. So they contain both locations almost equally. I can also try and do the same after it contains the "work part" only.
Here the text output from BBS:
Code:
===================
General Information
===================
BetterBatteryStats version: 1.12.0.0RC11
Creation Date: 2013-03-08 07:34:09
Statistic Type: Unplugged to Current
Since 16 h 31 m 59 s
VERSION.RELEASE: 2.3.5
BRAND: htc_wwe
DEVICE: bravo
MANUFACTURER: HTC
MODEL: HTC Desire
OS.VERSION: 2.6.35.14-gingercakes-0.9-avs
BOOTLOADER: 6.93.1002
HARDWARE: bravo
FINGERPRINT: htc_europe/htc_runnymede/runnymede:2.3.5/GRJ90/182513.4:user/release-keys
ID: GRJ90
TAGS: release-keys
USER: Sebastiaan15
PRODUCT: htc_bravo
RADIO: unknown
Rooted: true
============
Battery Info
============
Level lost [%]: 41 Bat.: 41% (100% to 59%) [2,5%/h]
Voltage lost [mV]: 366 (4172-3806) [22,1%/h]
===========
Other Usage
===========
Deep Sleep (): 11 h 47 m 20 s (42440 s) Ratio: 71,3%
Awake (): 4 h 44 m 39 s (17079 s) Ratio: 28,7%
Screen On (): 35 m 22 s (2122 s) Ratio: 3,6%
Wifi On (): 16 h 31 m 54 s (59514 s) Ratio: 100,0%
Wifi Running (): 16 h 31 m 53 s (59513 s) Ratio: 100,0%
No Data Connection (): 16 h 31 m 59 s (59519 s) Ratio: 100,0%
No or Unknown Signal (): 16 h 31 m 59 s (59519 s) Ratio: 100,0%
Screen dark (): 18 s (18 s) Ratio: 0,0%
Screen dimmed (): 35 m 3 s (2103 s) Ratio: 3,5%
=========
Wakelocks
=========
*backup* (Android System): 36 m 9 s (2169 s) Count:354 3,6%
android.media.MediaPlayer (com.htc.music.Musik): 15 m 41 s (941 s) Count:12 1,6%
Event Log Service (Google Services): 9 m 5 s (545 s) Count:66 0,9%
AlarmManager (Android System): 7 m 44 s (464 s) Count:1147 0,8%
GTALK_CONN (Google Services): 3 m 41 s (221 s) Count:400 0,4%
RILJ (Telefon): 2 m 56 s (176 s) Count:60 0,3%
GTALK_ASYNC_CONN (Google Services): 1 m 58 s (118 s) Count:26 0,2%
ActivityManager-Launch (Android System): 1 m 49 s (109 s) Count:175 0,2%
*sync* (com.google.android.gm.Google Mail): 48 s (48 s) Count:5 0,1%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 43 s (43 s) Count:21 0,1%
sleep_broadcast (Android System): 32 s (32 s) Count:246 0,1%
WifiStateTracker (Android System): 30 s (30 s) Count:177 0,1%
fullsync (com.whatsapp.WhatsApp): 22 s (22 s) Count:2 0,0%
DropboxCpuOnlyWakeLock (com.dropbox.android.Dropbox): 18 s (18 s) Count:11 0,0%
SCREEN_FROZEN (Android System): 13 s (13 s) Count:302 0,0%
show keyguard (Android System): 11 s (11 s) Count:9 0,0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Google Mail): 11 s (11 s) Count:14 0,0%
IdleScreen:command (com.htc.clock3dwidget.Clock widget): 10 s (10 s) Count:60 0,0%
PRE_PARTIAL_WAKELOCK_62923 (com.splunchy.android.alarmclock.AlarmDroid): 10 s (10 s) Count:13 0,0%
IdleScreen:event (com.htc.clock3dwidget.Clock widget): 9 s (9 s) Count:89 0,0%
Checkin Service (Google Services): 8 s (8 s) Count:441 0,0%
backupdb (com.whatsapp.WhatsApp): 8 s (8 s) Count:1 0,0%
PRE_PARTIAL_WAKELOCK_58994 (com.splunchy.android.alarmclock.AlarmDroid): 8 s (8 s) Count:2 0,0%
WifiService (Android System): 7 s (7 s) Count:373 0,0%
com.htc.music.MediaPlaybackService (com.htc.music.Musik): 7 s (7 s) Count:4 0,0%
PRE_PARTIAL_WAKELOCK_54994 (com.splunchy.android.alarmclock.AlarmDroid): 7 s (7 s) Count:1 0,0%
RtcWakeLock (com.kebab.Llama.Llama): 6 s (6 s) Count:4 0,0%
StartingAlertService (com.android.mms.Nachricht): 6 s (6 s) Count:2 0,0%
IdleScreen_base:event (com.htc.clock3dwidget.Clock widget): 6 s (6 s) Count:98 0,0%
PRE_PARTIAL_WAKELOCK_50993 (com.splunchy.android.alarmclock.AlarmDroid): 6 s (6 s) Count:6 0,0%
PRE_PARTIAL_WAKELOCK_46994 (com.splunchy.android.alarmclock.AlarmDroid): 5 s (5 s) Count:7 0,0%
SMSDispatcher (Telefon): 5 s (5 s) Count:1 0,0%
PRE_PARTIAL_WAKELOCK_62966 (com.splunchy.android.alarmclock.AlarmDroid): 4 s (4 s) Count:10 0,0%
PRE_PARTIAL_WAKELOCK_42985 (com.splunchy.android.alarmclock.AlarmDroid): 4 s (4 s) Count:11 0,0%
PRE_PARTIAL_WAKELOCK_38994 (com.splunchy.android.alarmclock.AlarmDroid): 3 s (3 s) Count:17 0,0%
Wecker01 (com.splunchy.android.alarmclock.AlarmDroid): 3 s (3 s) Count:4 0,0%
BatteryServiceUpdateStats (Android System): 3 s (3 s) Count:292 0,0%
PRE_PARTIAL_WAKELOCK_34991 (com.splunchy.android.alarmclock.AlarmDroid): 3 s (3 s) Count:3 0,0%
Event Log Handoff (Google Services): 2 s (2 s) Count:433 0,0%
PRE_PARTIAL_WAKELOCK_30994 (com.splunchy.android.alarmclock.AlarmDroid): 2 s (2 s) Count:9 0,0%
START_SERVICE (UID): 2 s (2 s) Count:4 0,0%
keyguardWakeAndHandOff (Android System): 2 s (2 s) Count:394 0,0%
PRE_PARTIAL_WAKELOCK_26994 (com.splunchy.android.alarmclock.AlarmDroid): 2 s (2 s) Count:16 0,0%
PRE_PARTIAL_WAKELOCK_22994 (com.splunchy.android.alarmclock.AlarmDroid): 1 s (1 s) Count:18 0,0%
SyncManagerHandleSyncAlarm (Android System): 1 s (1 s) Count:214 0,0%
*sync* (Google Services): 1 s (1 s) Count:27 0,0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:1161 0,0%
PRE_PARTIAL_WAKELOCK_18995 (com.splunchy.android.alarmclock.AlarmDroid): 1 s (1 s) Count:8 0,0%
GpsLocationProvider (Android System): 1 s (1 s) Count:218 0,0%
PRE_PARTIAL_WAKELOCK_14993 (com.splunchy.android.alarmclock.AlarmDroid): 1 s (1 s) Count:12 0,0%
================
Kernel Wakelocks
================
"deleted_wake_locks" (): 6 h 18 m 47 s (22727 s) Cnt:(c/wc/ec)261975/0/24392 38,2%
"PowerManagerService" (): 36 m 1 s (2161 s) Cnt:(c/wc/ec)1044/0/0 3,6%
"audio_pcm_suspend" (): 16 m 12 s (972 s) Cnt:(c/wc/ec)15/0/0 1,6%
"AudioHardwareQSDOut" (): 16 m 12 s (972 s) Cnt:(c/wc/ec)15/0/0 1,6%
"kgsl" (): 8 m 36 s (516 s) Cnt:(c/wc/ec)1189/0/0 0,9%
"ds2784-battery" (): 2 m 58 s (178 s) Cnt:(c/wc/ec)577/0/0 0,3%
"alarm" (): 2 m 45 s (165 s) Cnt:(c/wc/ec)853/0/0 0,3%
"alarm_rtc" (): 1 m 20 s (80 s) Cnt:(c/wc/ec)254/0/8 0,1%
"SMD_RPCCALL" (): 33 s (33 s) Cnt:(c/wc/ec)78363/241/0 0,1%
"rpc_read" (): 13 s (13 s) Cnt:(c/wc/ec)61333/0/0 -0,0%
"SMD_DS" (): 8 s (8 s) Cnt:(c/wc/ec)356/4/356 0,0%
"radio-interface" (): 5 s (5 s) Cnt:(c/wc/ec)23/0/0 0,0%
"KeyEvents" (): 4 s (4 s) Cnt:(c/wc/ec)78479/0/0 0,0%
"gpio_kp" (): 1 s (1 s) Cnt:(c/wc/ec)125/5/0 0,0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)13/0/0 -0,0%
"gpio_input" (): (0 s) Cnt:(c/wc/ec)41/5/0 0,0%
"port_list" (): (0 s) Cnt:(c/wc/ec)5735/0/0 0,0%
"ApmCommandThread" (): (0 s) Cnt:(c/wc/ec)19/0/0 0,0%
"rpc-interface" (): (0 s) Cnt:(c/wc/ec)3/0/0 0,0%
======================
Alarms (requires root)
======================
No reference unplugged was saved yet, plug/unplug you phone (): Wakeups: 0
======================
Network (requires root)
======================
==========
CPU States
==========
128 MHz (): 4 h 16 m 26 s 25,9%
245 MHz (): 1 m 42 s 0,2%
384 MHz (): 2 m 28 s 0,2%
537,6 MHz (): 0,0%
576 MHz (): 2 m 38 s 0,3%
652,8 MHz (): 0,0%
729,6 MHz (): 0,0%
768 MHz (): 3 m 14 s 0,3%
806,4 MHz (): 0,0%
883,2 MHz (): 0,0%
960 MHz (): 4 m 14 s 0,4%
998,4 MHz (): 13 m 53 s 1,4%
Deep Sleep (): 11 h 47 m 20 s 71,3%
==================
Reference overview
==================
Custom: null
Since charged: Reference ref_charged created 2 d 5 h 9 m 48 s (Wl: 0 elements; KWl: 34elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 20 elements)
Since screen off: null
Since unplugged: Reference ref_unplugged created 2 d 5 h 9 m 47 s (Wl: 0 elements; KWl: 34elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 20 elements)
Since boot: null
Here are the screens and log from work only. I hope that helps.
Looks like your auto sync, data connection and music player is on always and taking most of the battery.
Turn off auto sync
Turn off data when you don't need
Turn off music and kill the player after you stop listening
Sent from my Nexus 10 using Tapatalk HD
dvsk69 said:
Looks like your auto sync, data connection and music player is on always and taking most of the battery.
Turn off auto sync
Turn off data when you don't need
Turn off music and kill the player after you stop listening
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
But why does the drain stop at home without me changing anything?
So I'm not sure where to look... My battery recently seems to be draining quite quickly. I'm running stock battery, stock google rom 4.2.2, just rooted. At 8 hours, with less than 1 hour of screen time, my battery is at 56% left. I don't see what's causing the battery drain... I've attached some screenshots of the battery stats, but I can include anything else that may be helpful. I did install BetterBatteryStats this morning, but I'm never sure what to read out of that app!
You should look at the kernel wakelocks and partial wakelocks from betterbatterystats and then google the top ones in the list and see what can be done about them. Or just post screenshots here.
garbb said:
You should look at the kernel wakelocks and partial wakelocks from betterbatterystats and then google the top ones in the list and see what can be done about them. Or just post screenshots here.
Click to expand...
Click to collapse
Looking at the BetterBatteryStats, my phone has been "awake" since it was unplugged today (100% of the time). It's only had 33 minutes of screen-on time, but is down to 72%. I don't see much unusual under the wakelocks, DoggCatcher is at the top, which I would suspect, as that's the time count of how much I've used it today.
Not sure about the "PowerManagerService.WakeLocks" being 92% of the off-battery time.
I dumped the BetterBatteryStats to a text file, and here's what was in there for today so far:
Code:
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-08-10 13:53:42
Statistic Type: Unplugged to Current
Since 7 h 12 m 59 s
VERSION.RELEASE: 4.3
BRAND: google
DEVICE: maguro
MANUFACTURER: samsung
MODEL: Galaxy Nexus
OS.VERSION: 3.0.72-gfb3c9ac
BOOTLOADER: PRIMEMD04
HARDWARE: tuna
FINGERPRINT: google/takju/maguro:4.3/JWR66V/737497:user/release-keys
ID: JWR66V
TAGS: release-keys
USER: android-build
PRODUCT: takju
RADIO: I9250XXLJ1
Rooted: false
============
Battery Info
============
Level lost [%]: Bat.: -28% (100% to 72%) [3.9%/h]
Voltage lost [mV]: (4156-3886) [37.4%/h]
===========
Other Usage
===========
Awake (): 7 h 12 m 59 s (25979 s) Ratio: 100.0%
Screen On (): 33 m 6 s (1986 s) Ratio: 7.6%
Phone On (): 13 s (13 s) Ratio: 0.0%
Wifi On (): 7 h 12 m 59 s (25979 s) Ratio: 100.0%
Wifi Running (): 7 h 12 m 59 s (25979 s) Ratio: 100.0%
No Data Connection (): 6 h 44 m 15 s (24255 s) Ratio: 93.4%
No or Unknown Signal (): 6 h 44 m 15 s (24255 s) Ratio: 93.4%
Good Signal (): 21 m 37 s (1297 s) Ratio: 0.4%
Screen dark (): 18 m 16 s (1096 s) Ratio: 4.2%
Screen dimmed (): 6 m 22 s (382 s) Ratio: 0.1%
Screen medium (): 24 s (24 s) Ratio: 0.0%
Screen light (): 24 s (24 s) Ratio: 0.0%
Screen bright (): 7 m 37 s (457 s) Ratio: 0.1%
=========
Wakelocks
=========
AudioOut_3 (1013): 13 m 17 s (797 s) Count:26 3.1%
AudioPlayingWakeLock (com.snoggdoggler.android.applications.doggcatcher.v1_0.DoggCatcher): 12 m 55 s (775 s) Count:14 3.0%
NlpCollectorWakeLock (Google Services): 9 m 55 s (595 s) Count:2759 2.3%
NlpWakeLock (Google Services): 9 m 49 s (589 s) Count:2261 2.3%
StartingAlertService (com.google.android.calendar.Calendar): 6 m 32 s (392 s) Count:67 1.5%
Genie (com.google.android.apps.genie.geniewidget.News & Weather): 4 m 59 s (299 s) Count:42 1.2%
AudioOut_2 (1013): 4 m 48 s (288 s) Count:117 1.1%
FbClientConnManager (com.facebook.katana.Facebook): 1 m 39 s (99 s) Count:104 0.4%
AlarmManager (Android System): 53 s (53 s) Count:1465 0.2%
AlarmManager (com.facebook.katana.Facebook): 42 s (42 s) Count:1346 0.2%
h (com.facebook.orca.Messenger): 33 s (33 s) Count:33 0.1%
NetworkLocationLocator (Google Services): 32 s (32 s) Count:2424 0.1%
*sync*_gmail-ls_Account {name=1aecabf46ba66394d8e55c881a6a9124, type=com.google} (com.google.android.gm.Gmail): 31 s (31 s) Count:21 0.1%
WakefulIntentService[GCoreUlr-LocationReceiverService] (Google Services): 24 s (24 s) Count:4295 0.1%
AlarmManager (Google Services): 23 s (23 s) Count:3947 0.1%
*sync*_com.google.android.apps.plus.content.EsProvider_Account {name=1aecabf46ba66394d8e55c881a6a9124, type=com.google} (com.google.android.apps.plus.Google+): 21 s (21 s) Count:6 0.1%
EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Search): 20 s (20 s) Count:123 0.1%
com.commonsware.cwac.wakeful.WakefulIntentService (com.rageconsulting.android.lightflow.Light Flow): 18 s (18 s) Count:1021 0.1%
MediaPlayerController (com.snoggdoggler.android.applications.doggcatcher.v1_0.DoggCatcher): 18 s (18 s) Count:15 0.1%
ActivityManager-Launch (Android System): 17 s (17 s) Count:837 0.1%
AlarmManager (com.rageconsulting.android.lightflow.Light Flow): 15 s (15 s) Count:1914 0.1%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 12 s (12 s) Count:35 0.0%
FacebookService (com.facebook.katana.Facebook): 12 s (12 s) Count:25 0.0%
dwh (Google Services): 12 s (12 s) Count:198 0.0%
WakefulIntentService[GCoreUlr-LocationReportingService] (Google Services): 11 s (11 s) Count:2307 0.0%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 9 s (9 s) Count:9 0.0%
GpsLocationProvider (Android System): 9 s (9 s) Count:879 0.0%
DownloadManager (Media): 8 s (8 s) Count:1 0.0%
AlarmManager (com.google.android.googlequicksearchbox.Google Search): 6 s (6 s) Count:156 0.0%
GsmConnection (Phone): 6 s (6 s) Count:10 0.0%
*sync*_com.google.android.apps.currents_Account {name=1aecabf46ba66394d8e55c881a6a9124, type=com.google} (com.google.android.apps.currents.Currents): 6 s (6 s) Count:1 0.0%
cpu_lck (com.devuni.flashlight.Flashlight): 6 s (6 s) Count:1 0.0%
LocationManagerService (Android System): 6 s (6 s) Count:801 0.0%
RILJ (Phone): 5 s (5 s) Count:1312 0.0%
Sidekick_CalendarIntentService (com.google.android.googlequicksearchbox.Google Search): 4 s (4 s) Count:98 0.0%
LocationManagerService (Google Services): 4 s (4 s) Count:1373 0.0%
GTALK_CONN (Google Services): 3 s (3 s) Count:3276 0.0%
AudioIn_433 (1013): 2 s (2 s) Count:30 0.0%
LocationManagerService (com.google.android.apps.maps.Maps): 2 s (2 s) Count:418 0.0%
GOOGLE_C2DM (Google Services): 2 s (2 s) Count:2783 0.0%
ConnectivityService (Android System): 2 s (2 s) Count:1469 0.0%
AlarmManager (com.google.android.talk.Hangouts): 2 s (2 s) Count:13 0.0%
AudioIn_438 (1013): 2 s (2 s) Count:37 0.0%
NlpLocationReceiverService (Google Services): 2 s (2 s) Count:3151 0.0%
NetworkStats (Android System): 2 s (2 s) Count:52 0.0%
AlarmManager (com.google.android.apps.genie.geniewidget.News & Weather): 2 s (2 s) Count:30 0.0%
show keyguard (Android System): 2 s (2 s) Count:9 0.0%
TimerifficReceiver (com.alfray.timeriffic.Timeriffic): 2 s (2 s) Count:8 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 1 s (1 s) Count:2332 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:934 0.0%
SyncLoopWakeLock (Android System): 1 s (1 s) Count:1627 0.0%
LocationManagerService (com.facebook.katana.Facebook): 1 s (1 s) Count:1130 0.0%
Icing (Google Services): 1 s (1 s) Count:2442 0.0%
*sync*_com.android.contacts_Account {name=1aecabf46ba66394d8e55c881a6a9124, type=com.google} (Google Services): 1 s (1 s) Count:2477 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:2797 0.0%
LocationManagerService (com.eclipsim.gpsstatus2.GPS Status): 1 s (1 s) Count:833 0.0%
WakefulIntentService[GCoreUlr-SettingsChangedService] (Google Services): 1 s (1 s) Count:2271 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 1 s (1 s) Count:3 0.0%
*backup* (Android System): 1 s (1 s) Count:957 0.0%
AudioIn_3F9 (1013): 1 s (1 s) Count:12 0.0%
AudioIn_410 (1013): 1 s (1 s) Count:6 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:1636 0.0%
================
Kernel Wakelocks
================
"PowerManagerService.WakeLocks" (): 6 h 39 m 48 s (23988 s) Cnt:(c/wc/ec)0/0/0 92.3%
"wlan_rx_wake" (): 19 m 1 s (1141 s) Cnt:(c/wc/ec)952/0/952 4.4%
"wlan_ctrl_wake" (): 17 m 57 s (1077 s) Cnt:(c/wc/ec)555/0/555 4.1%
"mipi_link" (): 6 m 35 s (395 s) Cnt:(c/wc/ec)910/0/0 1.5%
"gps-lock" (): 3 m 22 s (202 s) Cnt:(c/wc/ec)10/0/0 0.8%
"wlan_wd_wake" (): 3 m 1 s (181 s) Cnt:(c/wc/ec)16888/0/0 0.7%
"radio-interface" (): 2 m 59 s (179 s) Cnt:(c/wc/ec)247/0/0 0.7%
"wlan_wake" (): 28 s (28 s) Cnt:(c/wc/ec)35352/0/0 0.1%
"max17040-battery" (): 8 s (8 s) Cnt:(c/wc/ec)451/0/0 0.0%
"alarm" (): 7 s (7 s) Cnt:(c/wc/ec)2621/0/0 0.0%
"twl6030 adc" (): 5 s (5 s) Cnt:(c/wc/ec)5311/0/0 0.0%
"sec_jack_det" (): 4 s (4 s) Cnt:(c/wc/ec)2/0/2 0.0%
"vibrator" (): 4 s (4 s) Cnt:(c/wc/ec)97/0/0 0.0%
"PowerManagerService.Broadcasts" (): 2 s (2 s) Cnt:(c/wc/ec)28/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cnt:(c/wc/ec)3135/0/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)9447/0/0 0.0%
"PowerManagerService.Display" (): (0 s) Cnt:(c/wc/ec)14/0/0 0.0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)8/0/0 -0.0%
"alarm_rtc" (): (0 s) Cnt:(c/wc/ec)7/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
350 MHz (): 6 h 23 m 25 s 88.6%
700 MHz (): 40 m 7 s 9.3%
920 MHz (): 2 m 17 s 0.5%
1.2 GHz (): 7 m 9 s 1.7%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 1 m 28 s (Wl: 11 elements; KWl: 0elements; NetS: null; Alrm: null; Proc: 2 elements; Oth: 6 elements; CPU: 4 elements)
ref_unplugged: Reference ref_unplugged created 3 d 10 h 19 m 18 s (Wl: 0 elements; KWl: 32elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 5 elements)
ref_charged: Reference ref_charged created 3 d 10 h 19 m 18 s (Wl: 0 elements; KWl: 32elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 8 elements; CPU: 5 elements)
ref_current: Reference ref_current created 3 d 17 h 32 m 18 s (Wl: 62 elements; KWl: 32elements; NetS: null; Alrm: null; Proc: 25 elements; Oth: 14 elements; CPU: 5 elements)
already read this thread http://forum.xda-developers.com/showthread.php?t=1462020 ? there are explanations for all wakelocks. the powermanagerservice wakelock is the collection of all partial wakelocks.
i dont know a solution for your case but if you cannot find the answer in the thread try to freez/disable/uninstall one app after the other and monitor bbs. that's how i would do it.
Well, "fixed" my problem by rebooting... my phone now goes to deep sleep, I wonder what was hanging around! Oh well!
I have the same problem with the PowerManagerService.WakeLocks. It keeps draining my battery even if it goes into deep sleep mode. I don't know what's wrong.
Enviado desde mi U9200 mediante Tapatalk