asksven / BetterBatteryStats

An attempt to provide advanced battery stats for Android
618 stars 156 forks source link

deepSleep % is always showing "from boot" #385

Closed stefan1368 closed 9 years ago

stefan1368 commented 11 years ago

I have a small bug report regarding 1.13.0.0RC1. Don't care which FROM reference I use, the deepSleep percentage in CPUState is always "from boot" % value.

a cutout of the log (Unplugged to Current)

CPU States 1,2 GHz (): 38 s 0,4% 1 GHz (): 6 s 0,1% 800 MHz (): 1 m 17 s 0,9% 500 MHz (): 2 m 10 s 1,5% 200 MHz (): 15 m 1 s 10,3% Deep Sleep (): 2 h 6 m 19 s 38,7% (-> should be 86.8%)


betterbatterystat.log:

General Information

BetterBatteryStats version: 1.13.0.0RC1 Creation Date: 2013-04-03 20:46:41 Statistic Type: Unplugged to Current Since 2 h 25 m 33 s VERSION.RELEASE: 4.1.2 BRAND: samsung DEVICE: GT-I9100 MANUFACTURER: samsung MODEL: GT-I9100 OS.VERSION: 3.0.31-Jeboo_Kernel_v2.1+ BOOTLOADER: unknown HARDWARE: smdk4210 FINGERPRINT: samsung/GT-I9100/GT-I9100:4.1.2/JZO54K/I9100XWLS8:user/release-keys ID: JZO54K TAGS: release-keys USER: dpi PRODUCT: GT-I9100 RADIO: I9100XXLS8

Rooted: true

Battery Info

Level lost [%]: Bat.: -5% (97% to 92%) [2,1%/h]

Voltage lost [mV]: (4183-4036) [60,7%/h]

Other Usage

Deep Sleep (): 2 h 6 m 19 s (7579 s) Ratio: 38,7% Awake (): 19 m 14 s (1154 s) Ratio: 13,2% Screen On (): 11 m 55 s (715 s) Ratio: 8,2% No Data Connection (): 3 s (3 s) Ratio: 0,0% No or Unknown Signal (): 3 s (3 s) Ratio: 0,0% Poor Signal (): 3 s (3 s) Ratio: 0,0% Moderate Signal (): 1 h 31 m 14 s (5474 s) Ratio: 28,0% Good Signal (): 51 m 17 s (3077 s) Ratio: 35,2%

Screen dark (): 11 m 55 s (715 s) Ratio: 8,2%

Wakelocks

ImapFolderPusher GMX:INBOX (com.fsck.k9.K-9 Mail): 1 m 40 s (100 s) Count:10 1,2% GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google-Dienste): 12 s (12 s) Count:36 0,1% AlarmManager (Android-System): 8 s (8 s) Count:129 0,1% RILJ (Telefon): 5 s (5 s) Count:189 0,1% ActivityManager-Launch (Android-System): 4 s (4 s) Count:21 0,0% sleep_broadcast (Android-System): 3 s (3 s) Count:41 0,0% PhoneWindowManager.mBroadcastWakeLock (Android-System): 2 s (2 s) Count:27 0,0% BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 2 s (2 s) Count:1 0,0%

NetworkStats (Android-System): 2 s (2 s) Count:11 0,0%

Kernel Wakelocks

"multipdp" (): 2 m 42 s (162 s) Cnt:(c/wc/ec)81/0/81 1,9% "l2_hsic" (): 2 m 21 s (141 s) Cnt:(c/wc/ec)540/136/540 1,6% "PowerManagerService" (): 2 m 9 s (129 s) Cnt:(c/wc/ec)262/0/0 1,5% "secril_fd-interface" (): 1 m 24 s (84 s) Cnt:(c/wc/ec)46/0/0 1,0% "sec-battery-monitor" (): 1 m 9 s (69 s) Cnt:(c/wc/ec)180/23/0 0,8% "umts_ipc0" (): 1 m 3 s (63 s) Cnt:(c/wc/ec)311/0/311 0,7% "radio-interface" (): 51 s (51 s) Cnt:(c/wc/ec)112/0/0 0,6% "alarm" (): 24 s (24 s) Cnt:(c/wc/ec)112/0/0 0,3% "rpm_hsic" (): 24 s (24 s) Cnt:(c/wc/ec)372/0/0 0,3% "alarm_rtc" (): 20 s (20 s) Cnt:(c/wc/ec)31/0/8 0,1% "mmc1_detect" (): 11 s (11 s) Cnt:(c/wc/ec)172/0/0 0,1% "tx_hsic" (): 9 s (9 s) Cnt:(c/wc/ec)2151/0/0 0,1% "power-supply" (): 2 s (2 s) Cnt:(c/wc/ec)170/0/0 -0,0% "sync_system" (): 1 s (1 s) Cnt:(c/wc/ec)5/0/0 0,0% "secril_fmt-interface" (): (0 s) Cnt:(c/wc/ec)1324/0/0 0,0% "KeyEvents" (): (0 s) Cnt:(c/wc/ec)1169/0/0 0,0%

"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)172/0/1 0,0%

Alarms (requires root)

com.google.android.gsf (): Wakeups: 13 Alarms: 1, Intent: com.google.android.intent.action.GTALK_RECONNECT Alarms: 5, Intent: com.google.android.intent.action.MCS_HEARTBEAT Alarms: 2, Intent: com.google.android.intent.action.SEND_IDLE

com.fsck.k9 (): Wakeups: 7 Alarms: -6, Intent: com.fsck.k9.service.BroadcastReceiver.fireIntent Alarms: -6, Intent: com.fsck.k9.service.BroadcastReceiver.fireIntent Alarms: 5, Intent: com.fsck.k9.service.BroadcastReceiver.fireIntent

android (): Wakeups: 6 Alarms: 74, Intent: android.intent.action.TIME_TICK Alarms: 5, Intent: com.android.server.action.NETWORK_STATS_POLL Alarms: 13, Intent: com.android.server.ThrottleManager.action.POLL Alarms: 3, Intent: android.appwidget.action.APPWIDGET_UPDATE Alarms: 2, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD Alarms: 0, Intent: com.android.server.NetworkTimeUpdateService.action.POLL Alarms: 0, Intent: android.app.backup.intent.RUN Alarms: 1, Intent: android.content.syncmanager.SYNC_ALARM

com.google.android.apps.maps (): Wakeups: 2 Alarms: 2, Intent: com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService

Network (requires root)

10005 (Mobile) (com.android.browser.Browser): 802.0 KBytes 94,0% 10082 (Mobile) (com.fsck.k9.K-9 Mail): 24.0 KBytes 2,9% 0 (Mobile) (0): 21.0 KBytes 2,5%

10010 (Mobile) (Google-Dienste): 5.0 KBytes 0,7%

CPU States

1,2 GHz (): 38 s 0,4% 1 GHz (): 6 s 0,1% 800 MHz (): 1 m 17 s 0,9% 500 MHz (): 2 m 10 s 1,5% 200 MHz (): 15 m 1 s 10,3%

Deep Sleep (): 2 h 6 m 19 s 38,7%

Reference overview

ref_boot: Reference ref_boot created 43 s (Wl: 4 elements; KWl: 13elements; NetS: 0 elements; Alrm: 1 elements; Proc: 0 elements; Oth: 5 elements; CPU: 2 elements) ref_unplugged: Reference ref_unplugged created 3 h 40 s (Wl: 0 elements; KWl: 23elements; NetS: 5 elements; Alrm: 7 elements; Proc: 0 elements; Oth: 4 elements; CPU: 5 elements) ref_current: Reference ref_current created 5 h 26 m 13 s (Wl: 9 elements; KWl: 26elements; NetS: 6 elements; Alrm: 7 elements; Proc: 2 elements; Oth: 9 elements; CPU: 6 elements)

stefan1368 commented 11 years ago

After a new install of version 1.13.4.0 it's still the same behavior. The bar and time value seems to be right. Only the percent value shows untrue facts.

Deep Sleep (): 2 h 6 m 19 s 38,7% (-> should be 86.8%)

asksven commented 9 years ago

can not reproduce on 2.0