What is keeping my phone awake and eating my battery?!?

[DirkBelig]

Something has happened with my phone's battery life in the past couple of weeks. It seems to coincide with my fixing the location problems as detailed in this thread, but my investigation can't see a connection between that and what's happening.

Attached are screenshots showing how I drained nearly half the battery while I slept. Normally, after 10 hours of standby, I would have 80-85% left. as you can see, it's constantly awake while the screen is off. Here is the BetterBatteryStats dump file:

===================
General Information
===================
BetterBatteryStats version: 1.7.1.0
Creation Date: 2012-04-15 12:14:10
Statistic Type: (3) 
Since 10 h 12 m 33 s 
VERSION.RELEASE: 2.3.6
BRAND: samsung
DEVICE: SPH-D710
MANUFACTURER: samsung
MODEL: SPH-D710
RADIO: unknown
BOOTLOADER: unknown
FINGERPRINT: samsung/SPH-D710/SPH-D710:2.3.6/GINGERBREAD/EL29:user/release-keys
HARDWARE: smdkc210
ID: GINGERBREAD
Rooted: true
===========
Other Usage
===========
Wifi On (): 10 h 12 m 33 s  (36753 s) Ratio: 100.0%
Bluetooth On (): 10 h 12 m 33 s  (36753 s) Ratio: 100.0%
Awake (): 1 h 21 m 56 s  (4916 s) Ratio: 13.4%
Wifi Running (): 52 m 16 s  (3136 s) Ratio: 8.5%
Screen On (): 4 m 42 s  (282 s) Ratio: 0.8%
=========
Wakelocks
=========
WifiService (Android System): 1 h 15 m 1 s  (4501 s) Count:455 12.2%
Managewakelock: partial (com.handcent.nextsms.Handcent SMS): 50 m 25 s  (3025 s) Count:13 8.2%
PollService wakeLockAcquire (com.fsck.k9.K-9 Mail): 14 m 3 s  (843 s) Count:276 2.3%
com.mufumbo.craigslist.notification.android.service.WakefulIntentService (com.mufumbo.craigslist.notification.android.CraigsNotifica): 8 m 48 s  (528 s) Count:68 1.4%
Event Log Service (Google Services): 7 m 35 s  (455 s) Count:174 1.2%
*sync* (com.google.android.gm.Gmail): 4 m 44 s  (284 s) Count:25 0.8%
Starting CM_VnoteService (com.coremobility.app.vnotes.Voicemail): 4 m 26 s  (266 s) Count:16 0.7%
NetworkLocationLocator (Google Services): 2 m 35 s  (155 s) Count:113 0.4%
BWL (com.levelup.beautifulwidgets.Beautiful Widgets): 1 m 41 s  (101 s) Count:41 0.3%
AlarmManager (Android System): 1 m 28 s  (88 s) Count:1611 0.2%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 1 m 8 s  (68 s) Count:70 0.2%
SyncManagerHandleSyncAlarm (Android System): 1 m 1 s  (61 s) Count:174 0.2%
FacebookService (com.facebook.katana.Facebook): 42 s  (42 s) Count:26 0.1%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 41 s  (41 s) Count:63 0.1%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 40 s  (40 s) Count:48 0.1%
SyncService (com.evernote.Evernote): 33 s  (33 s) Count:15 0.1%
CoreService execute (com.fsck.k9.K-9 Mail): 20 s  (20 s) Count:329 0.1%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 14 s  (14 s) Count:71 0.0%
RILJ (Dialer): 13 s  (13 s) Count:86 0.0%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 12 s  (12 s) Count:6 0.0%
CM Message wakeup (com.coremobility.app.vnotes.Voicemail): 10 s  (10 s) Count:14 0.0%
GTALK_CONN (Google Services): 9 s  (9 s) Count:485 0.0%
com.google.android.apps.googlevoice.UpdateService (com.google.android.apps.googlevoice.Google Voice): 9 s  (9 s) Count:4 0.0%
CoreReceiver getWakeLock (com.fsck.k9.K-9 Mail): 8 s  (8 s) Count:155 0.0%
Lookout (com.lookout.Lookout): 8 s  (8 s) Count:2 0.0%
GTALK_ASYNC_CONN (Google Services): 8 s  (8 s) Count:126 0.0%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 7 s  (7 s) Count:3 0.0%
WifiService (Google Services): 6 s  (6 s) Count:343 0.0%
DataConnection (Dialer): 5 s  (5 s) Count:6 0.0%
ActivityManager-Launch (Android System): 4 s  (4 s) Count:338 0.0%
NotificationService (Android System): 4 s  (4 s) Count:463 0.0%
NetworkLocationBurstCollector (com.google.android.apps.maps.Maps): 4 s  (4 s) Count:117 0.0%
CoreService onStart (com.fsck.k9.K-9 Mail): 4 s  (4 s) Count:265 0.0%
SMSDispatcher (Dialer): 3 s  (3 s) Count:9 0.0%
window (com.handcent.nextsms.Handcent SMS): 3 s  (3 s) Count:13 0.0%
LocationManagerService (Android System): 2 s  (2 s) Count:314 0.0%
StartingAlertService (com.handcent.nextsms.Handcent SMS): 2 s  (2 s) Count:11 0.0%
sleep_broadcast (Android System): 1 s  (1 s) Count:179 0.0%
WifiService (com.google.android.apps.maps.Maps): 1 s  (1 s) Count:105 0.0%
GpsLocationProvider (Android System): 1 s  (1 s) Count:122 0.0%
Checkin Service (Google Services): 1 s  (1 s) Count:544 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 1 s  (1 s) Count:37 0.0%
StartingAlertService (com.android.mms.Messaging): 1 s  (1 s) Count:3 0.0%
================
Kernel Wakelocks
================
"sec-battery-monitor" (): 19 m 10 s  (1150 s) Cnt:(c/wc/ec)1973/1807/0 3.1%
"[P]_com.mufumbo.craigslist.notification.android.service.WakefulIntentService" (): 10 m 31 s  (631 s) Cnt:(c/wc/ec)68/0/0 1.7%
"radio-interface" (): 7 m 50 s  (470 s) Cnt:(c/wc/ec)398/0/0 1.3%
"power-supply" (): 6 m 19 s  (379 s) Cnt:(c/wc/ec)1967/0/0 1.4%
"alarm_rtc" (): 6 m 12 s  (372 s) Cnt:(c/wc/ec)600/0/126 1.0%
"wlan_rx_wake" (): 5 m 59 s  (359 s) Cnt:(c/wc/ec)419/0/419 1.0%
"[P]_NetworkLocationLocator" (): 5 m 31 s  (331 s) Cnt:(c/wc/ec)116/0/0 0.9%
"alarm" (): 5 m 28 s  (328 s) Cnt:(c/wc/ec)1383/2/0 0.9%
"[P]_WifiService" (): 4 m 6 s  (246 s) Cnt:(c/wc/ec)410/0/0 0.7%
"[P]_*sync*" (): 3 m 56 s  (236 s) Cnt:(c/wc/ec)26/0/0 0.6%
"[P]_BWL" (): 3 m 53 s  (233 s) Cnt:(c/wc/ec)41/0/0 0.6%
"[P]_AlarmManager" (): 1 m 53 s  (113 s) Cnt:(c/wc/ec)1199/0/0 0.3%
"wlan_wake" (): 1 m 22 s  (82 s) Cnt:(c/wc/ec)12238/38/0 0.2%
"[P]_SignalCollector.ScannerThread" (): 1 m 11 s  (71 s) Cnt:(c/wc/ec)7/0/0 0.2%
"[P]_NetworkLocationPassiveCollector" (): 1 m 10 s  (70 s) Cnt:(c/wc/ec)26/0/0 0.2%
"[P]_FacebookService" (): 59 s  (59 s) Cnt:(c/wc/ec)26/0/0 0.2%
"[P]_GmailProviderProviderChangedBroadcastWakeLock" (): 42 s  (42 s) Cnt:(c/wc/ec)23/0/0 0.1%
"[P]_SyncService" (): 37 s  (37 s) Cnt:(c/wc/ec)15/0/0 0.1%
"[P]_RILJ" (): 28 s  (28 s) Cnt:(c/wc/ec)76/0/0 0.1%
"[P]_GTALK_ASYNC_CONN" (): 22 s  (22 s) Cnt:(c/wc/ec)13/0/0 0.1%
"AudioOutLock" (): 20 s  (20 s) Cnt:(c/wc/ec)7/0/0 0.1%
"[P]_DataConnection" (): 19 s  (19 s) Cnt:(c/wc/ec)6/0/0 0.1%
"[P]_com.google.android.apps.googlevoice.UpdateService" (): 18 s  (18 s) Cnt:(c/wc/ec)4/0/0 0.0%
"[P]_AlarmReceiver" (): 17 s  (17 s) Cnt:(c/wc/ec)6/0/0 0.0%
"[P]_NetworkLocationActiveCollector" (): 14 s  (14 s) Cnt:(c/wc/ec)1/0/0 0.0%
"[P]_Lookout" (): 13 s  (13 s) Cnt:(c/wc/ec)2/0/0 0.0%
"[P]_SMSDispatcher" (): 12 s  (12 s) Cnt:(c/wc/ec)3/0/0 0.0%
"[P]_GTALK_CONN" (): 12 s  (12 s) Cnt:(c/wc/ec)163/0/0 0.0%
"[P]_NetworkLocationBurstCollector" (): 8 s  (8 s) Cnt:(c/wc/ec)5/0/0 0.0%
"[P]_LocationManagerService" (): 8 s  (8 s) Cnt:(c/wc/ec)295/0/0 0.0%
"[P]_StartingAlertService" (): 5 s  (5 s) Cnt:(c/wc/ec)9/0/0 0.0%
"vib_present" (): 5 s  (5 s) Cnt:(c/wc/ec)6/0/0 0.0%
"[P]_GpsLocationProvider" (): 4 s  (4 s) Cnt:(c/wc/ec)171/0/0 0.0%
"[P]_SyncManagerHandleSyncAlarm" (): 4 s  (4 s) Cnt:(c/wc/ec)52/0/0 0.0%
"DPRAM_PWDOWN" (): 4 s  (4 s) Cnt:(c/wc/ec)18100/0/0 0.0%
"[P]_sleep_broadcast" (): 3 s  (3 s) Cnt:(c/wc/ec)4/0/0 0.0%
"[P]_VibratorService" (): 2 s  (2 s) Cnt:(c/wc/ec)3/0/0 0.0%
"[P]_NetworkLocationCallbackRunner" (): 1 s  (1 s) Cnt:(c/wc/ec)35/0/0 0.0%
"[P]_StartingPopupUtilsService" ():  (0 s) Cnt:(c/wc/ec)6/0/0 0.0%
"event1-2691" ():  (0 s) Cnt:(c/wc/ec)5/1/0 0.0%
"vbus_present" ():  (0 s) Cnt:(c/wc/ec)0/0/1 0.0%
"event7-2691" ():  (0 s) Cnt:(c/wc/ec)15206/0/0 0.0%
"[P]_NotificationService" ():  (0 s) Cnt:(c/wc/ec)8/0/0 0.0%
"[P]_ColorNote" ():  (0 s) Cnt:(c/wc/ec)1/0/0 0.0%
"[P]_GOOGLE_C2DM" ():  (0 s) Cnt:(c/wc/ec)23/0/0 0.0%
"[P]_ActivityManager-Sleep" ():  (0 s) Cnt:(c/wc/ec)3/0/0 0.0%
"sync_system" ():  (0 s) Cnt:(c/wc/ec)2/0/0 0.0%
"mmc_delayed_work" ():  (0 s) Cnt:(c/wc/ec)2091/0/1 0.0%
"[P]_ServiceStateTracker" ():  (0 s) Cnt:(c/wc/ec)11/0/0 0.0%
"client-interface" ():  (0 s) Cnt:(c/wc/ec)6268/0/0 0.0%
"[P]_AsyncCollectorListener" ():  (0 s) Cnt:(c/wc/ec)7/0/0 0.0%
"KeyEvents" ():  (0 s) Cnt:(c/wc/ec)1307/0/0 0.0%
======================
Alarms (requires root)
======================
nextapp.systempanel.r1 (): Wakeups: 123
  Alarms: 123, Intent: nextapp.systempanel.action.MONITOR_UPDATE

android (): Wakeups: 75
  Alarms: 1, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
  Alarms: 482, Intent: android.intent.action.TIME_TICK
  Alarms: 2, Intent: com.android.server.WifiManager.action.DEVICE_IDLE
  Alarms: 60, Intent: com.android.server.ThrottleManager.action.POLL
  Alarms: 20, Intent: android.appwidget.action.APPWIDGET_UPDATE
  Alarms: 52, Intent: android.content.syncmanager.SYNC_ALARM

com.mufumbo.craigslist.notification.android (): Wakeups: 68

getjar.android.client (): Wakeups: 61

com.google.android.apps.maps (): Wakeups: 58
  Alarms: 1, Intent: com.google.android.location.ALARM_WAKEUP_PASSIVE_COLLECTOR
  Alarms: 2, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.1
  Alarms: 0, Intent: com.google.android.location.ALARM_WAKEUP_CACHE_UPDATER
  Alarms: 2, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.3
  Alarms: 14, Intent: com.google.android.location.ALARM_WAKEUP_S_COLLECTOR
  Alarms: 2, Intent: com.google.android.location.ALARM_WAKEUP_ACTIVE_COLLECTOR
  Alarms: 7, Intent: com.google.android.location.ALARM_WAKEUP_BURST_COLLECTOR
  Alarms: 6, Intent: com.google.android.location.ALARM_WAKEUP_SENSOR_UPLOADER
  Alarms: 1, Intent: com.google.android.location.ALARM_WAKEUP_LOCATOR
  Alarms: 2, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.5
  Alarms: 1, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.7

org.jraf.android.nolock (): Wakeups: 61

com.facebook.katana (): Wakeups: 32
  Alarms: 1, Intent: com.facebook.katana.service.40
  Alarms: 2, Intent: com.facebook.katana.service.12
  Alarms: 1, Intent: com.facebook.katana.service.24
  Alarms: 1, Intent: com.facebook.katana.service.11
  Alarms: 2, Intent: com.facebook.katana.service.14
  Alarms: 1, Intent: com.facebook.katana.service.22
  Alarms: 1, Intent: com.facebook.katana.service.13
  Alarms: 2, Intent: com.facebook.katana.service.16
  Alarms: 1, Intent: com.facebook.katana.service.28
  Alarms: 2, Intent: com.facebook.katana.service.18
  Alarms: 1, Intent: com.facebook.katana.service.26
  Alarms: 0, Intent: com.facebook.katana.service.9
  Alarms: 2, Intent: com.facebook.katana.service.8
  Alarms: 2, Intent: com.facebook.katana.service.10
  Alarms: 0, Intent: com.facebook.katana.service.5
  Alarms: 1, Intent: com.facebook.katana.service.32
  Alarms: 4, Intent: com.facebook.katana.service.4
  Alarms: 1, Intent: com.facebook.katana.service.20
  Alarms: 1, Intent: com.facebook.katana.service.6
  Alarms: 1, Intent: com.facebook.katana.service.30
  Alarms: 1, Intent: com.facebook.katana.service.36
  Alarms: 0, Intent: com.facebook.katana.service.3
  Alarms: 1, Intent: com.facebook.katana.service.34
  Alarms: 2, Intent: com.facebook.katana.service.2
  Alarms: 1, Intent: com.facebook.katana.service.38

com.levelup.beautifulwidgets (): Wakeups: 41
  Alarms: 41, Intent: com.levelup.beautifulwidgets.ACTION_UPDATEWEATHER
  Alarms: 2410, Intent: com.levelup.beautifulwidgets.ACTION_UPDATECLOCK

com.google.android.gsf (): Wakeups: 35
  Alarms: 6, Intent: com.google.android.intent.action.GTALK_RECONNECT
  Alarms: 9, Intent: com.google.android.intent.action.GTALK_HEARTBEAT

com.google.android.location (): Wakeups: 3
  Alarms: 3, Intent: com.google.android.location.ALARM_WAKEUP_LOCATOR

com.fsck.k9 (): Wakeups: 12
  Alarms: 12, Intent: com.fsck.k9.service.BroadcastReceiver.fireIntent

com.noinnion.android.greader.reader (): Wakeups: 10

com.aws.android (): Wakeups: 10
  Alarms: 10, Intent: com.aws.action.free.PERIODIC_DATA_UPDATE

com.google.android.maps.mytracks (): Wakeups: 7

com.amazon.venezia (): Wakeups: 6
  Alarms: 6, Intent: com.amazon.mas.client.framework.UpdateService.EXECUTE_RECURRING_TASKS

com.handcent.nextsms (): Wakeups: 5

com.coremobility.app.vnotes (): Wakeups: 2
  Alarms: 2, Intent: com.coremobility.app.vnotes.SERVICE_DOPROCESS

com.groupon (): Wakeups: 2

com.socialnmobile.dictapps.notepad.color.note (): Wakeups: 1
  Alarms: 1, Intent: note.socialnmobile.intent.action.AUTO_SYNC

com.google.android.apps.googlevoice (): Wakeups: 1
  Alarms: 1, Intent: com.google.android.apps.googlevoice.RETRY_UPDATE

Anyone see what I'm overlooking as to what's keeping my phone awake? TIA!

 

[sparkeater79]

I am pretty sure you have more knowledge with Android, however I think you need to check the apps you installed recently. some funky rogue app out to get you.

 

[dtm_stretch]

I am pretty sure you have more knowledge with Android, however I think you need to check the apps you installed recently. some funky rogue app out to get you.

The only problem is; when you check the battery stats he posted and the log there is no app out of wack.



Dirk, is there a reason you have your bluetooth on the the whole time? Something weird is going on with your phone though and I wouldn't attribute it completely to bluetooth. Have you thought about doing a factory reset or a reflash if you are rooted?

 

[DirkBelig]

I forgot to mention in my OP but I don't have any widgets other than the Fancy Widgets time/weather and a calendar thing that shows an agenda view. These have always been there. I haven't added many new apps other than replacing the Network Location apk to fix my busted Foursquare stuff. That's when I noticed I was getting crazy short battery life. If an update to an app has started this drain coincident to that change is unknown.

As for doing a factory reset - kill me now. I've got too damn many apps and whatnot that I don't want to have to reload, etc. even with Titanium Backup. (That it caused my phone to reboot when I launched it the other day is another matter.) About a month ago I had to reflash my phone with ODIN One-Click after an app laid waste to it, so it's reasonably fresh.

I've had this phone since October and have a feel for how long it should last and how much battery should be left in the morning as I usually top it off before going to sleep and using it as a secondary alarm. I have always left the wifi, GPS and Bluetooth on 24/7 because I can't remember to turn them on and off when I get into the car, etc. It's just a PITA and until the past couple of weeks there wasn't a drastic unexplained power drain going on.

 

[JayWill]

I bet its related to location services. You may want to try clearing data on Google maps and Latitude. Then reboot and charge to full.

Sent from my SPH-D710 using Tapatalk 2

 

[DirkBelig]

Tried clearing Maps (don't use Latitude) and rebooted but I was down too low in the morning. Here are shots of the battery trace (it really plunged when I got to my office with its terrible signal) and a very weird sign that the sensors are running a lot when it's just sitting there. What's that about?

Edit: Tapatalk is giving me trouble uploading the images. I'll add them when I get on a PC.

Edit #2: Screens added.

 

[dtm_stretch]

Tried clearing Maps (don't use Latitude) and rebooted but I was down too low in the morning. Here are shots of the battery trace (it really plunged when I got to my office with its terrible signal) and a very weird sign that the sensors are running a lot when it's just sitting there. What's that about?

Edit: Tapatalk is giving me trouble uploading the images. I'll add them when I get on a PC.

Go to settings > location services and uncheck everything. Samsung is notoriously known for building phones that chug battery when in low signal areas. My phone and my og epic do horrible when I am in an area with less than 2 bars.

 

[DirkBelig]

I don't see what that's going to do because at both home and my g/f's place, it's connected to wifi and has been since I bought it. It's only lately that battery drain has gone nuts.

Screenshots have been added to prior post.

 

[dtm_stretch]

I don't see what that's going to do because at both home and my g/f's place, it's connected to wifi and has been since I bought it. It's only lately that battery drain has gone nuts.

Screenshots have been added to prior post.

Well what Jay eluded to before was that some app, most likely after an update, is unnecessarily utilizing the GPS/Acceleromoter/Compass. Problem is there is no app out there that will tell you which app is turning on those tools, so it could be maps which is what Jay suggested and you did the basic trouble shooting. My suggestion was to turn off all location based services so no apps have access to those tools. Other options include uninstalling app by app to see which one is the culprit, reflash and start over(this might not even fix the problem), or continue monitoring the battery till something more definitive pops up. One thing we do know for sure though; you should definitely be getting better battery life than that on GB.

 

[DirkBelig]

I have about 150 apps on my phone, so playing the "uninstall/see what happens for a day/rinse/repeat" thing will mean ICS or the Galaxy S III will be out first. I've tried turning off all the location stuff and am charging it up now and will see how it behaves this evening. I also reapplied the XDA thread's com.google.android.location.apk and we'll see what happens.

 

[dtm_stretch]

I have about 150 apps on my phone, so playing the "uninstall/see what happens for a day/rinse/repeat" thing will mean ICS or the Galaxy S III will be out first. I've tried turning off all the location stuff and am charging it up now and will see how it behaves this evening. I also reapplied the XDA thread's com.google.android.location.apk and we'll see what happens.

Oh my goodness, yeah I wouldn't want to play that game either. Well the well known, unauthorized users of gps tools are; google maps, facebook, and foursquare, although it could be some others. Can you give me a link to that thread by chance?

 

[DirkBelig]

Correction: I have 174 apps on my phone. Here's the XDA thread link.

 

[DirkBelig]

Here's the latest round of WTF screenshots. I charged it up to about 90% and then shut off wi-fi, BT, and GPS along with turning off all the location stuff. The big trouble spots:

* Why is the light sensor showing constant use? Is that normal?

* I have notifications turned off on the Amazon App Store, but it's constantly in the top rank of power suckers.

* K-9 Mail shows up in BetterBatteryStats partial wakelock list a lot. I have that set to check only once an hour. (Gmail is set for instant push.)

* What's the deal with the phone NOT being awake for that stretch?

This is getting really annoying.

 

[dtm_stretch]

Here's the latest round of WTF screenshots. I charged it up to about 90% and then shut off wi-fi, BT, and GPS along with turning off all the location stuff. The big trouble spots:

* Why is the light sensor showing constant use? Is that normal?

* I have notifications turned off on the Amazon App Store, but it's constantly in the top rank of power suckers.

* K-9 Mail shows up in BetterBatteryStats partial wakelock list a lot. I have that set to check only once an hour. (Gmail is set for instant push.)

* What's the deal with the phone NOT being awake for that stretch?

This is getting really annoying.

Light sensor: Auto-brightness...I would definitely keep this off and manually adjust the brightness by dragging down the pull down bar just a little and sliding your finger left and right to increase and decrease the brightness. Check your browser settings also, it has a separate brightness setting.

Something is up with that Amazon app store though, maybe uninstall and re-install?

Ah, K-9, it is a double edged sword. Well known battery sucker no matter what settings you have it on but unfortunately there is no app that does email better. I used to use it when my university was still using an imap email system but luckily they updated to the new MS exchange, which works awesome with the ICS email app.

I am not sure about the phone actually going to sleep, that is a good thing though your phone should go to sleep when you are not using it. Also on another note, with that many apps installed I don't think you will ever have awesome battery life, I mean just think about it. If just a quarter of the number of apps you have, have background tasks which have to run ever hour or so and all of those apps begin those background tasks at different times; your phone will never sleep. Maybe you want to think about shrinking the number of apps you have? Think about which apps you actually need; for example you have craigslist and getjar, both of which are terrible apps and just launch an app version of the mobile webpage, yet, neither app has more function than the web pages. So both can be uninstalled and you can use the browser instead. Do you possibly need all those apps? Or would it be better to uninstall them and install them when you need to use them?

Just some food for thought, this is going to get much worse on ICS. I have maybe 20 apps installed, I keep everything off and barely use my phone, yet, battery life is terrible and I mean significantly worse than GB. On GB I averaged around 3-4 hrs screen on time and about 24 hrs overall on a charge. On ICS i get about 1.5-2hrs screen on time and about 10-12 hrs overall per charge. Same exact settings.


**Edit: sucks that this phone can handle 150+ apps easily but the battery/power management is holding it back.

 

[DirkBelig]

I don't have auto-brightness turned on; I manually adjust that. The Craig's Notifier is an auto-search app that I find too useful to ditch - I was able to save $300 on a camera lens because I was notified of the listing and beat the stampede to score the deal.

I remember discovering that Getjar was slurping power on my Kindle Fire and dumped it off there; I'll try ditching it here. I think I only reloaded it to get an updated Tapatalk. I'll try reloading Amazon when I'm home on the wi-fi.

The thing that bears repeating is that I didn't suddenly load 100 apps and the battery life turned to crap; it started about two weeks ago and it's just weird that there's no obvious cause and the stuff that's seems to be chugging power are system services that can't be killed.

 

[oskar1995]

DirkBelig,

I am very appreciative this thread got started, and I'm certainly curious what the resolution is. A couple thoughts/questions.

1. What app did you use in the screen shots of your most recent post, I noticed BetterBatteryStats, but was wondering what the other one is (or just more components of BBS I'm not using).
2. In terms of linking up a couple of thoughts, You noted that this started happening a couple of weeks ago and Amazon App Store seems to be waking the phone. If I'm not mistaken the app store was updated a couple of weeks ago (and might coincide with some not great battery life I've seen).
3. All of the above being said, I'm curious if its not something in the kernel (66% of the battery) that is pulling more time than normal.

Just a thought.

 

[DirkBelig]

The other app is Badass Battery Monitor which really digs into more things than BBS IMO.

The Samsung Android Bug has always had higher-than-needed kernel use, but I'm wondering if there's something in the Network Location fix that's polling harder. I made a mention of possible increased drain on the XDA thread, but never got a reply.

 

[DirkBelig]

OK, things are definitely moving into a positive direction. I ditched Getjar, Friendcaster (alternate Facebook client), Beautiful Widgets (was using juice despite none being used; huh?), and un/reinstalled Amazon Apps. (You can't dump A'zon Apps entirely because apps are keyed to it being present.)

This morning, after 4 hours off the charger, it was at about 88%, which is a tad lower than usual for that span of time, it's definitely back into the ballpark of what I had before and hella improved compared to what prompted this thread in the first place. The oddball power sucker this morning was GPS Status though I hadn't used it since about 6 pm yesterday and only once. Strange. Let's see what happens tonight with a longer time off the charger. (I'll pull it so it's at least 6 hours off while I sleep. No, I don't get enough sleep.)

 

[E_Cross]

I don't care how many apps I have if I was having that problem, back up important stuff and wipe the .
Don't fiddle faddle around, just take care of it, apps are redownloadable, but a useless phone is a way more annoying problem.

 

[DirkBelig]

I'm not sure which thing was making things go crazy, but it appears I'm getting back into more normal territory, though it still seems low. Here are the screens from this morning after 9-1/2 hours off the charger. I unplugged at 9:30 pm and went to bed around 1:30 am, awaking (OK, hitting the snooze) at 6:45 am. Compared to being under 50% after <6 hours, this is much better, but shouldn't this be better when on wi-fi with full phone bars?

Compared to before (see screens), the wifi isn't running constantly, but there's still that hour of awake time in the middle that's unexplained. I'm also concerned with the power usage by GPS Status since I wasn't using it AND I killed the process early on when I saw after an hour unplugged that it was running. Weird.