Related
So I bought the new Seidio 1750 battery, and am running a supposedly decent kernel for battery usage (Chad's 2.6.32.26-HAVS-BFQ-GPU+-smartass )
But I still strugle to get about a day's usage out of it. It's usually down to about 20 percent by the time I leave the office.
I have 1 facebook widget, one New York Times Widget, 1 other News Widget, and thats it for data retrieval widgets. I'm running LAuncherpro.
I hardly used my phone today. About 10 minutes in total internet usage twice, and the rest of the days its either sitting on my desk or in my poskcet.
Battery drainage looks like this, but I just don't know whether this is good or bad, and whether I should be looking to see if there is something hogging my system ?
I thought that with the new battery, I'd get at least a day out of it ?
date time status charge_percentage degrees_celsius volts
11/30/2010 2:18 PM Discharging 50 28.3 3.792
11/30/2010 2:17 PM Discharging 51 27.3 3.794
11/30/2010 2:05 PM Discharging 52 26.9 3.815
11/30/2010 1:55 PM Discharging 53 27.6 3.833
11/30/2010 1:11 PM Discharging 54 30.9 3.838
11/30/2010 12:37 PM Discharging 55 32.1 3.817
11/30/2010 12:30 PM Discharging 56 32.7 3.811
11/30/2010 12:30 PM Discharging 57 32.4 3.797
11/30/2010 12:28 PM Discharging 58 30.7 3.779
11/30/2010 12:19 PM Discharging 59 28.8 3.814
11/30/2010 11:35 AM Discharging 60 26.7 3.866
11/30/2010 11:31 AM Discharging 61 27.3 3.871
11/30/2010 11:28 AM Discharging 62 28.8 3.861
11/30/2010 11:24 AM Discharging 63 31.8 3.826
11/30/2010 11:23 AM Discharging 64 32.1 3.83
11/30/2010 11:21 AM Discharging 65 31.5 3.815
11/30/2010 11:06 AM Discharging 66 29.1 3.89
11/30/2010 11:01 AM Discharging 67 30.1 3.864
11/30/2010 11:01 AM Discharging 68 30.4 3.863
11/30/2010 11:00 AM Discharging 69 30.1 3.86
11/30/2010 10:56 AM Discharging 70 30.1 3.905
11/30/2010 10:54 AM Discharging 71 29.6 3.933
11/30/2010 10:54 AM Discharging 72 29.6 3.877
11/30/2010 10:46 AM Discharging 73 29.6 3.948
11/30/2010 10:03 AM Discharging 74 32.7 3.904
11/30/2010 10:00 AM Discharging 75 30.9 3.931
11/30/2010 9:59 AM Discharging 76 30.7 3.908
11/30/2010 9:59 AM Discharging 77 29.8 3.877
11/30/2010 9:58 AM Discharging 78 29.1 3.864
11/30/2010 9:36 AM Discharging 79 30.9 3.981
11/30/2010 9:14 AM Discharging 80 30.9 3.984
11/30/2010 8:49 AM Discharging 81 32.7 3.986
11/30/2010 8:47 AM Discharging 82 31.8 3.962
11/30/2010 8:43 AM Discharging 83 31.2 3.973
11/30/2010 8:41 AM Discharging 84 31.2 3.971
11/30/2010 8:35 AM Discharging 85 32.4 3.984
11/30/2010 8:34 AM Discharging 86 31.5 3.999
11/30/2010 8:30 AM Discharging 87 28.1 4.02
11/30/2010 8:26 AM Discharging 88 25.6 4.043
11/30/2010 8:21 AM Discharging 89 24.7 4.024
11/30/2010 7:54 AM Discharging 90 30.7 3.997
11/30/2010 7:51 AM Discharging 91 29.3 4.077
11/30/2010 7:47 AM Discharging 92 26.9 4.089
11/30/2010 7:46 AM Discharging 93 26.4 4.085
11/30/2010 7:45 AM Discharging 94 25.8 4.099
11/30/2010 7:18 AM Discharging 95 27.3 4.086
11/30/2010 7:16 AM Discharging 96 25.8 4.088
11/30/2010 7:10 AM Discharging 97 25.6 4.081
11/30/2010 7:09 AM Discharging 98 24.2 4.099
11/30/2010 7:09 AM Unplugged 99 23.4 4.102
It depends if you have other features on as well like GPS, WiFi, and the update interval of your widgets but I'd say your battery usage is pretty normal even with the extended battery it will not be that much better.
If you're in a low coverage area then that would even better explain it.
Do you overclock at all? Are you using setcpu? I overclock, and use a screen off profile lowering the cpu to 384 max/min, and setting it to powersave. Last night I was at 21 hours disconnected with about 20% left. That's with moderate internet browsing (emails, texts, tweetdeck checking/updating, but no games), maybe 1 call if that. This is all with the stock battery.
grifforama said:
So I bought the new Seidio 1750 battery, and am running a supposedly decent kernel for battery usage (Chad's 2.6.32.26-HAVS-BFQ-GPU+-smartass )
But I still strugle to get about a day's usage out of it. It's usually down to about 20 percent by the time I leave the office.
I have 1 facebook widget, one New York Times Widget, 1 other News Widget, and thats it for data retrieval widgets. I'm running LAuncherpro.
I hardly used my phone today. About 10 minutes in total internet usage twice, and the rest of the days its either sitting on my desk or in my poskcet.
Battery drainage looks like this, but I just don't know whether this is good or bad, and whether I should be looking to see if there is something hogging my system ?
I thought that with the new battery, I'd get at least a day out of it ?
date time status charge_percentage degrees_celsius volts
11/30/2010 2:18 PM Discharging 50 28.3 3.792
11/30/2010 2:17 PM Discharging 51 27.3 3.794
11/30/2010 2:05 PM Discharging 52 26.9 3.815
11/30/2010 1:55 PM Discharging 53 27.6 3.833
11/30/2010 1:11 PM Discharging 54 30.9 3.838
11/30/2010 12:37 PM Discharging 55 32.1 3.817
11/30/2010 12:30 PM Discharging 56 32.7 3.811
11/30/2010 12:30 PM Discharging 57 32.4 3.797
11/30/2010 12:28 PM Discharging 58 30.7 3.779
11/30/2010 12:19 PM Discharging 59 28.8 3.814
11/30/2010 11:35 AM Discharging 60 26.7 3.866
11/30/2010 11:31 AM Discharging 61 27.3 3.871
11/30/2010 11:28 AM Discharging 62 28.8 3.861
11/30/2010 11:24 AM Discharging 63 31.8 3.826
11/30/2010 11:23 AM Discharging 64 32.1 3.83
11/30/2010 11:21 AM Discharging 65 31.5 3.815
11/30/2010 11:06 AM Discharging 66 29.1 3.89
11/30/2010 11:01 AM Discharging 67 30.1 3.864
11/30/2010 11:01 AM Discharging 68 30.4 3.863
11/30/2010 11:00 AM Discharging 69 30.1 3.86
11/30/2010 10:56 AM Discharging 70 30.1 3.905
11/30/2010 10:54 AM Discharging 71 29.6 3.933
11/30/2010 10:54 AM Discharging 72 29.6 3.877
11/30/2010 10:46 AM Discharging 73 29.6 3.948
11/30/2010 10:03 AM Discharging 74 32.7 3.904
11/30/2010 10:00 AM Discharging 75 30.9 3.931
11/30/2010 9:59 AM Discharging 76 30.7 3.908
11/30/2010 9:59 AM Discharging 77 29.8 3.877
11/30/2010 9:58 AM Discharging 78 29.1 3.864
11/30/2010 9:36 AM Discharging 79 30.9 3.981
11/30/2010 9:14 AM Discharging 80 30.9 3.984
11/30/2010 8:49 AM Discharging 81 32.7 3.986
11/30/2010 8:47 AM Discharging 82 31.8 3.962
11/30/2010 8:43 AM Discharging 83 31.2 3.973
11/30/2010 8:41 AM Discharging 84 31.2 3.971
11/30/2010 8:35 AM Discharging 85 32.4 3.984
11/30/2010 8:34 AM Discharging 86 31.5 3.999
11/30/2010 8:30 AM Discharging 87 28.1 4.02
11/30/2010 8:26 AM Discharging 88 25.6 4.043
11/30/2010 8:21 AM Discharging 89 24.7 4.024
11/30/2010 7:54 AM Discharging 90 30.7 3.997
11/30/2010 7:51 AM Discharging 91 29.3 4.077
11/30/2010 7:47 AM Discharging 92 26.9 4.089
11/30/2010 7:46 AM Discharging 93 26.4 4.085
11/30/2010 7:45 AM Discharging 94 25.8 4.099
11/30/2010 7:18 AM Discharging 95 27.3 4.086
11/30/2010 7:16 AM Discharging 96 25.8 4.088
11/30/2010 7:10 AM Discharging 97 25.6 4.081
11/30/2010 7:09 AM Discharging 98 24.2 4.099
11/30/2010 7:09 AM Unplugged 99 23.4 4.102
Click to expand...
Click to collapse
I also use the Seidio 1750, and I usually make it about 14hrs before it sees the charger. Now of course this is very subjective, but you might try and app called System Panel. It will let you see if any apps are hogging resources. Just a thought.
I've found that bump charging does a world of good on mine. I used to just pull it off the charger in the morning and head for work. I have a 10 minute commute and when I got to my office I was down to around 88-92% and by noon I was around 40%. Now, when I get up in the morning I pull it off the charger (after its full charged), turn it off, plug it back in and hit the shower. Usually when I get ready to head to work it is fully charged (being turned off) and my battery life has been fabulous. At noon I'm around 80-85% depending on how much I use it. I never believed the whole bump charge stuff but it actually does work. I'm rooted, running HeyItsLou's Redemptive rEVOlution ROM with the stock kernel. It charges fast and has been the best I've used for battery life. Hope this helps a little.
Yeah I'll vouch for that bump charging thing too. I use a Set CPU profile to bring my processor speed down to 384 when my screen is off, and I also couple that with Juice Defender. Basically it just toggles my 3G on and off when I'm not using it (i.e. when my screen is off) I've also messed around different kernels and I really do like the .17 stock HTC one, but for the time being I'm using the latest one from Ziggy. Not sure how I feel about the battery life on this one yet. Give that combo a shot, (bump charge, setCPU profiles, Juice Defender) I think you'll be pretty pleased.
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?
Hallo peoples! I have made new flash tool (command line tool called xflasher, see my signature!), tool do not depend on java or anything, only flash tool usb driver (one which everybody use for flashtool) is only need to get it work. Linux and android version apsolutly depend on nothing, so no need for any driver or anything while you use linux or android version! What help I need? First of all let say some things first. Tool fully support sin v1, v2, v3, v4, so all, tool do not use .FSC scripts as like on flashtool, first thing! Which I need to know and which is realy strange to me is that hard bricks which you had while you flashed your mediatek phone without that fsc script. But thing which I want to know is, why that happen? I know somebody will say because of missing fsc. But, I can say xflasher do not use that things but we have confirmed working xflasher on devices like z1, z1c, z3, z5, x compact...etc, no one used fsc since xflasher simple do not have something like that. So how that is possible that there is no hardbricks? Simple don't know how but I'm believing fsc scripts is no need at all , everything went right and without any isue, all that devices working as expected. One thing now I need to know, does somebody want to risk an test for me (ofcourse do it on your own risk) and try xflasher on M5 device? If you realy want to try please read instructions from xflasher thread, AND PLEASE flash only cache.sin (because of less risk for hard brick), and please let me know! Show xflasher.log if you done! Use v22 version if you are ready to try!!
Edit:
Here is some speaks between Androxide and me https://forum.xda-developers.com/showthread.php?p=72754821#post72754821 if you are interesting to see why I reguest this.
I would try it but my phone has spent half its life getting repaired because the repair centre are terrible at fixing phones apparently and I don't want to send my new one off because I don't have heaps of money lying around
Is possible to downgrade M5 from 6.0 to 5.0 without any problems like bootloop etc with Your flasher?
I tried xflasher v22 with Xperia M5 (e5603) on windows 7.
I checked my firmware with
Code:
fastboot get-var all
(bootloader) version-baseband: 1295-9162_30.2.A.0.100
(bootloader) version-bootloader: 1295-0246 S1_Boot_MT6795_M0.MP17.TC9SP
I took loader.sin using XperiFirm and correct firmware version.
Then run xflasher
Code:
xflasher.exe loader.sin 0 0 0FCE ADDE 0 0 >xflasher.log
And this is the output:
Code:
-------------------------------------------------------
Xperia Command Line Flasher v22
by Munjeni @ 2014,2017
-------------------------------------------------------
Device path: \\?\usb#vid_0fce&pid_adde#5&12809bec&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Class Description: USB-Controllers
Device Instance Id: USB\VID_0FCE&PID_ADDE\5&12809BEC&0&2
Successfully read 0xd bytes from handle.
Raw input [0xD]:
00000000 00 00 00 01 00 00 00 01 00 00 03 8F 93 .............
Successfully read 0x393 bytes from handle.
Raw input [0x393]:
00000000 50 52 4F 54 5F 56 45 52 3D 22 30 34 22 3B 56 45 PROT_VER="04";VE
00000010 52 3D 22 53 31 5F 42 6F 6F 74 5F 4D 54 36 37 39 R="S1_Boot_MT679
00000020 35 5F 4D 30 2E 4D 50 31 37 2E 54 43 39 53 50 5F 5_M0.MP17.TC9SP_
00000030 32 30 35 22 3B 53 31 53 42 4C 5F 56 45 52 3D 22 205";S1SBL_VER="
00000040 4D 54 36 37 39 35 5F 31 37 22 3B 49 44 3D 22 31 MT6795_17";ID="1
00000050 32 39 35 2D 30 32 34 36 22 3B 54 59 50 45 3D 22 295-0246";TYPE="
00000060 53 31 5F 42 4F 4F 54 22 3B 41 43 54 49 56 45 5F S1_BOOT";ACTIVE_
00000070 43 4F 4D 50 5F 41 49 44 3D 22 30 30 30 34 22 3B COMP_AID="0004";
00000080 4D 41 58 5F 50 4B 54 5F 53 5A 3D 22 30 30 38 30 MAX_PKT_SZ="0080
00000090 30 30 30 30 22 3B 49 47 4E 4F 52 45 5F 43 52 43 0000";IGNORE_CRC
000000A0 3D 22 48 44 52 2C 44 41 54 41 22 3B 44 45 46 5F ="HDR,DATA";DEF_
000000B0 53 45 43 3D 22 4F 4E 22 3B 48 57 43 4F 4E 46 5F SEC="ON";HWCONF_
000000C0 41 49 44 3D 22 30 30 30 34 22 3B 4C 4F 41 44 45 AID="0004";LOADE
000000D0 52 5F 41 49 44 3D 22 30 30 30 34 22 3B 42 4F 4F R_AID="0004";BOO
000000E0 54 5F 41 49 44 3D 22 30 30 30 34 22 3B 4E 4F 5F T_AID="0004";NO_
000000F0 53 55 42 5F 53 59 53 54 45 4D 53 3D 22 30 30 30 SUB_SYSTEMS="000
00000100 31 22 3B 4F 54 50 5F 44 41 54 41 5F 31 3D 22 30 1";OTP_DATA_1="0
00000110 34 30 30 22 3B 4F 54 50 5F 4C 4F 43 4B 5F 53 54 400";OTP_LOCK_ST
00000120 41 54 55 53 5F 31 3D 22 4C 4F 43 4B 45 44 22 3B ATUS_1="LOCKED";
00000130 55 4E 49 51 55 45 5F 44 45 56 5F 49 44 5F 31 3D UNIQUE_DEV_ID_1=
00000140 22 38 42 36 38 32 45 37 35 45 45 36 30 35 33 34 "8B682E75EE60534
00000150 34 22 3B 49 44 43 4F 44 45 5F 31 3D 22 39 35 36 4";IDCODE_1="956
00000160 37 30 30 30 30 30 30 30 30 30 30 30 30 22 3B 53 7000000000000";S
00000170 55 49 44 5F 31 3D 22 30 39 30 30 30 30 30 30 39 UID_1="090000009
00000180 35 36 37 30 30 30 30 33 35 35 43 46 44 30 38 36 5670000355CFD086
00000190 41 46 37 39 38 43 37 22 3B 53 31 5F 52 4F 4F 54 AF798C7";S1_ROOT
000001A0 3D 22 53 31 5F 52 6F 6F 74 5F 61 63 34 35 2C 53 ="S1_Root_ac45,S
000001B0 31 5F 52 6F 6F 74 5F 54 65 73 74 5F 62 33 31 36 1_Root_Test_b316
000001C0 22 3B 4D 53 4E 3D 22 59 54 39 31 31 43 41 51 32 ";MSN="YT911CAQ2
000001D0 37 22 3B 48 57 5F 43 4F 4E 46 49 47 5F 56 45 52 7";HW_CONFIG_VER
000001E0 3D 22 30 30 30 36 22 3B 48 57 5F 43 4F 4E 46 49 ="0006";HW_CONFI
000001F0 47 5F 49 4E 46 4F 3D 22 48 57 43 5F 43 68 61 6D G_INFO="HWC_Cham
00000200 62 61 6C 50 6C 75 73 5F 43 6F 6D 5F 30 30 33 22 balPlus_Com_003"
00000210 3B 53 45 43 5F 53 54 41 54 45 3D 22 48 57 43 5F ;SEC_STATE="HWC_
00000220 43 68 61 6D 62 61 6C 50 6C 75 73 5F 43 6F 6D 5F ChambalPlus_Com_
00000230 30 30 33 22 3B 49 4D 45 49 3D 22 33 35 34 31 38 003";IMEI="35418
00000240 38 30 37 35 37 32 30 39 36 22 3B 50 52 4F 44 5F 807572096";PROD_
00000250 49 44 3D 22 30 30 30 31 22 3B 47 4C 4F 42 5F 53 ID="0001";GLOB_S
00000260 45 43 3D 22 30 30 30 30 22 3B 50 48 4F 4E 45 5F EC="0000";PHONE_
00000270 49 44 3D 22 30 30 30 30 3A 33 35 34 31 38 38 30 ID="0000:3541880
00000280 37 35 37 32 30 39 36 22 3B 48 57 5F 43 4F 4E 46 7572096";HW_CONF
00000290 49 47 3D 22 53 31 5F 42 6F 6F 74 3A 30 30 30 34 IG="S1_Boot:0004
000002A0 3A 30 30 31 33 2C 53 31 5F 4C 6F 61 64 65 72 3A :0013,S1_Loader:
000002B0 30 30 30 34 3A 30 30 30 42 2C 53 31 5F 53 57 3A 0004:000B,S1_SW
Then it stops maybe for 120 seconds, and then it continues (the lonely colon is the last character of the first part)
Code:
:
000002C0 30 30 30 35 3A 30 30 31 33 2C 53 31 5F 43 75 73 0005:0013,S1_Cus
000002D0 74 3A 30 30 30 34 3A 30 30 31 33 2C 53 31 5F 45 t:0004:0013,S1_E
000002E0 4C 61 62 65 6C 3A 30 30 30 34 3A 30 30 31 33 2C Label:0004:0013,
000002F0 53 31 5F 53 4C 3A 30 30 30 34 3A 30 30 34 33 2C S1_SL:0004:0043,
00000300 53 31 5F 46 4F 54 41 3A 30 30 30 35 3A 30 30 32 S1_FOTA:0005:002
00000310 33 2C 53 31 5F 52 4C 6F 63 6B 3A 30 30 30 34 3A 3,S1_RLock:0004:
00000320 30 32 32 33 22 3B 52 4F 4F 54 49 4E 47 5F 53 54 0223";ROOTING_ST
00000330 41 54 55 53 3D 22 52 4F 4F 54 41 42 4C 45 22 3B ATUS="ROOTABLE";
00000340 50 4C 46 5F 52 4F 4F 54 5F 31 3D 22 31 39 43 43 PLF_ROOT_1="19CC
00000350 43 34 30 35 31 39 43 43 43 34 30 35 38 36 44 44 C40519CCC40586DD
00000360 41 35 42 34 38 36 44 44 41 35 42 34 35 36 43 33 A5B486DDA5B456C3
00000370 32 43 32 45 35 36 43 33 32 43 32 45 45 34 30 32 2C2E56C32C2EE402
00000380 45 43 31 34 45 34 30 32 45 43 31 34 22 3B 00 68 EC14E402EC14";.h
00000390 17 1F 63 ..c
ERROR: TIMEOUT: failed with error code 997 as follows:
Overlapped I/O operation is in progress
Successfully read 0x0 bytes from handle.
Raw input [0x0]:
Seems it is not safe now to flash anything more (even the cache.sin).
It stops for 120 seconds on 3rd read, timeout. Can you try again with loader.sin only??