• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] Can Someone Teach Me To Use Better Battery

gapi

gapi

Android Expert
Since leaving the incredible battery performance of ROM AOKP M3 going to M4 my sleeping battery life has plummeted.

After trying several kernels and re-flashes I have purchased Better Battery Stats.

Can someone give me a jumper on how to set it up to monitor whats going on during the night?

What preference settings and what to do just before putting it down for the night.
And then what to look for in the AM?

Thanks. Its a little french to this ole, dog.
 
Just before you go to bed, open BetterBatteryStats and press:

Menu > Actions > Set Custom Ref.

When you wake up, change the first pulldown menu to say "Partial Wakelocks" and the second to say "Since Custom Ref."

This will show you what wakelocks kept the phone from entering deep sleep while you were in deep sleep yourself. If you can't figure out what they are referencing, either google the wakelock, or post here and I'll try to help ya out.
 
I have some battery tips including using BBS in the link in my sig.

I'm going to add a blurb on custom references now that you bring it up.

Thanks for the tip. Oh, and on mine you set them by Menu > More > Set Custom Ref. Not sure if we have different versions of BBS or what?
 
Thanks, I loaded BBS just for monitoring M4 to see what was the drain. I did not see anything like wake locks and such. Once for a few seconds the media server took a peek but that's it.

Its all moot now with B28 she is back to loosing less than 1% per hour in sleep vs more then 3% per in M4.
 
AlarmManager is keeping my phone awake all the time, even when I don't have an alarm set.

I screwed up my dump this morning (that sounds weird), but AlarmManager has over 1000 partial wakelocks in one night alone.

My battery bar in Settings is basically a solid line next to Awake.

Any ideas?
 
Also, what is "vbus-tuna_otg." I think it's related to the USB connection, but not sure. But it's really high on kernel wakelocks.
 
My charging isn't 100% either.

I think I'm just going to have to wipe Monday. It's behaving very strangely.

I'm on second to latest kernel.
 
I see the same thing with alarm manager. I think it must do something ridiculous like check every 2 seconds to see if there's an alarm set.
 
Ok. Updated to latest (AOKP b28 w/ Lean 2.7.1) and let it sleep overnight.

Here's the dump:
================
Kernel Wakelocks
================
"vbus-tuna_otg" (): 6 h 34 m 1 s (23641 s) Cnt:(c/wc/ec)0/0/1 99.7%
"PowerManagerService" (): 2 h 22 m 56 s (8576 s) Cnt:(c/wc/ec)7666/0/0 36.2%
"wlan_rx_wake" (): 2 h 15 m 17 s (8117 s) Cnt:(c/wc/ec)7015/0/7015 34.2%
"wlan_wake" (): 3 m 4 s (184 s) Cnt:(c/wc/ec)104466/0/0 0.8%
"alarm" (): 51 s (51 s) Cnt:(c/wc/ec)9545/0/0 0.2%
"max17040-battery" (): 20 s (20 s) Cnt:(c/wc/ec)437/0/0 0.1%
"radio-interface" (): 19 s (19 s) Cnt:(c/wc/ec)19/0/0 0.1%
"twl6030 adc" (): 11 s (11 s) Cnt:(c/wc/ec)4426/0/0 0.0%
"nfc" (): 5 s (5 s) Cnt:(c/wc/ec)20/0/20 0.0%
"sec_jack_det" (): 3 s (3 s) Cnt:(c/wc/ec)2/0/2 0.0%
"modem_usb_gpio_wake" (): 3 s (3 s) Cnt:(c/wc/ec)7/0/7 0.0%
"modem_usb_suspend_block" (): 2 s (2 s) Cnt:(c/wc/ec)7/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cnt:(c/wc/ec)179/0/0 0.0%
"power-supply" (): (0 s) Cnt:(c/wc/ec)33/0/0 0.0%
"musb_autosuspend_wake_lock" (): (0 s) Cnt:(c/wc/ec)1/0/0 0.0%
"client-interface" (): (0 s) Cnt:(c/wc/ec)27/0/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)168/0/0 0.0%
======================
Alarms (requires root)
======================
com.android.email (): Wakeups: 1463
Alarms: 1463, Intent: com.android.email.intent.action.MAIL_SERVICE_WAKEUP

com.google.android.apps.plus (): Wakeups: 836
Alarms: 27, Intent: com.google.android.apps.plus.content.cleanup
Alarms: 27, Intent: com.google.android.apps.plus.content.sync
Alarms: 782, Intent: com.google.android.apps.plus.NEW_PICTURE

com.google.android.apps.maps (): Wakeups: 424
Alarms: 0, Intent: com.google.android.location.ALARM_WAKEUP_CACHE_UPDATER
Alarms: 0, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.1
Alarms: 0, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.3
Alarms: 0, Intent: com.google.android.location.ALARM_WAKEUP_S_COLLECTOR
Alarms: 2, Intent: com.google.android.location.ALARM_WAKEUP_BURST_COLLECTOR
Alarms: 0, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.9
Alarms: 13, Intent: com.google.android.location.ALARM_WAKEUP_SENSOR_UPLOADER
Alarms: 395, Intent: com.google.android.location.ALARM_WAKEUP_LOCATOR
Alarms: 0, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.5
Alarms: 0, Intent: com.google.location.lbs.collectionlib.STOP_SCANNER.7

com.android.exchange (): Wakeups: 733

com.rageconsulting.android.lightflow (): Wakeups: 132

com.android.phone (): Wakeups: 69
Alarms: 64, Intent: com.android.internal.telephony.gprs-data-stall
Alarms: 5, Intent: com.android.internal.telephony.gprs-reconnect.0
Alarms: 0, Intent: com.android.internal.telephony.cdma-reconnect

com.google.android.gsf (): Wakeups: 41
Alarms: 26, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 1, Intent: com.google.android.intent.action.SEND_IDLE

net.dinglisch.android.tasker (): Wakeups: 40
Alarms: 39, Intent: net.dinglisch.android.tasker.ANOFFCHECKORUM
Alarms: 1, Intent: net.dinglisch.android.tasker.ALARUM

android (): Wakeups: 25
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 395, Intent: android.intent.action.TIME_TICK
Alarms: 14, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 40, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 1, Intent: android.net.wifi.DHCP_RENEW
Alarms: 0, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 6, Intent: android.app.backup.intent.RUN
Alarms: 18, Intent: android.content.syncmanager.SYNC_ALARM

com.sec.android.internal.ims (): Wakeups: 16

com.gau.go.launcherex (): Wakeups: 8
Alarms: 7, Intent: com.jiubang.intent.action.ACTION_TIDY_DATA
Alarms: 1, Intent: com.jiubang.intent.action.AUTO_CHECK_UPDATE
Alarms: 0, Intent: com.jiubang.intent.action.SCAN_APPS

com.twitter.android (): Wakeups: 6
Alarms: 6, Intent: com.twitter.android.poll.alarm

com.google.android.apps.walletnfcrel (): Wakeups: 4
Alarms: 4, Intent: com.google.android.apps.wallet.services.periodic.PERIODIC_EXECUTION

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

Edit: Turned off smilies. I love how they were all frowning though.
 
I had a very similar experience today. I plug my phone in over night and rarely reboot it (generally it only gets rebooted when I flash something). Over the last couple of days, it seems that I have been having more issues with runaway services that prevent the phone from sleeping. Today it was the same vbus-tuna_otg service and PowerManagerService was also high (about 1/3 of the total unplug time).

Prior to rebooting today, busybox was running at a very high rate (I turned on the CPU usage overlay). When I rebooted, busybox did not show up on the overlay anymore. So it seems that whatever the problem, it was busybox related.

I have also noticed that just about every time I have an issue like this, as soon as I reboot, the market goes through it's updating process and downloads and updates several programs. I'm not sure if the system gets hung up in the early stages of the update process and keeps the phone from sleeping and never finishes. It is also possible that the phone has issues first, isn't able to sleep, and this process is preventing the phone from checking the market to update properly.

Anyway, those have been my experiences and I wanted to share in case it helps anyone figure out what is going on.

I'm running GummyNex 0.9.0 and Franco r112.
 
You must log in or register to reply here.
Back
Top Bottom