[Nexus 5 Original Android Development] Technecium:
amg you fixed it! Well not that it's broken but this appears to be a great improvement. The bulk of the time is spent at 300 and 422. You'll notice some time above 1GHz, I hit the snooze button 3 times so the screen kept coming on.

bbs below for 6h 43min/interactive and only lost 11%

Well done!

===================
General Information
===================
BetterBatteryStats version: 1.16.0.0
Creation Date: 2014-07-23 09:27:36
Statistic Type: Custom to Current
Since 6 h 43 m 42 s
VERSION.RELEASE: 4.4.4
BRAND: Android
DEVICE: hammerhead
MANUFACTURER: LGE
MODEL: AOSP on HammerHead
OS.VERSION: 3.4.88-franco.Kernel
BOOTLOADER: HHZ11k
HARDWARE: hammerhead
FINGERPRINT: Android/aosp_hammerhead/hammerhead:4.4.4/KTU84P/eng.koe.20140628.234910:user/test-keys
ID: KTU84P
TAGS: test-keys
USER: koe
PRODUCT: aosp_hammerhead
RADIO: M8974A-2.0.50.1.16
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -11% (94% to 83%) [1.6%/h]
Voltage lost [mV]: (4127-4058) [10.3%/h]
===========
Other Usage
===========
Awake (): 6 h 43 m 42 s (24222 s) Ratio: 100.0%
Screen On (): 2 m 55 s (175 s) Ratio: 0.7%
No Data Connection (): 6 h 43 m 42 s (24222 s) Ratio: 100.0%
No or Unknown Signal (): 6 h 43 m 42 s (24222 s) Ratio: 100.0%
Screen dark (): 13 s (13 s) Ratio: 0.1%
Screen dimmed (): 2 m 42 s (162 s) Ratio: 0.6%
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
AMP (com.jrtstudio.AnotherMusicPlayer.Rocket Player): 6 h 41 m 56 s (24116 s) Count:0 99.6%
AudioOffload (1013): 54 s (54 s) Count:8711 0.2%
AudioOffload (com.jrtstudio.AnotherMusicPlayer.Rocket Player): 26 s (26 s) Count:88 0.1%
AlarmManager (Android System): 10 s (10 s) Count:466 0.0%
AlarmClock (com.android.deskclock.Clock): 9 s (9 s) Count:11 0.0%
TimedEventQueue (1013): 9 s (9 s) Count:76 0.0%
AudioMix (1013): 8 s (8 s) Count:81 0.0%
AudioMix (com.android.deskclock.Clock): 7 s (7 s) Count:49 0.0%
ActivityManager-Launch (Android System): 1 s (1 s) Count:38 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
PowerManagerService.WakeLocks (): 6 h 40 m 46 s (24046 s) Cnt:(c/wc/ec)0/0/0 99.3%
alarm (): 6 s (6 s) Cnt:(c/wc/ec)1684/0/0 0.0%
qpnp-vadc-ee250800 (): 5 s (5 s) Cnt:(c/wc/ec)880/0/0 0.0%
qpnp-iadc-ee250a00 (): 3 s (3 s) Cnt:(c/wc/ec)520/0/0 0.0%
alarm_rtc (): (0 s) Cnt:(c/wc/ec)3/0/1 0.0%
PowerManagerService.Broadcasts (): (0 s) Cnt:(c/wc/ec)8/0/0 0.0%
max17048_alert (): (0 s) Cnt:(c/wc/ec)22/0/0 0.0%
power-supply (): (0 s) Cnt:(c/wc/ec)11/0/0 0.0%
PowerManagerService.Display (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
KeyEvents (): (0 s) Cnt:(c/wc/ec)1052/0/0 0.0%
ipc00000094_FLP Service Cal (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000098_FLP Service Cal (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc0000007b_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000079_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000033_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000031_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc0000002f_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc0000002d_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc0000002b_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000029_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000027_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
event2-624 (): (0 s) Cnt:(c/wc/ec)2/0/0 0.0%
ipc0000008d_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc0000007d_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000025_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000023_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000021_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc0000001f_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc0000001d_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc0000001b_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000017_sensors.qcom (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000015_time_daemon (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000013_rild (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000010_rild (): (0 s) Cnt:(c/wc/ec)4/0/0 0.0%
ipc00000008_time_daemon (): (0 s) Cnt:(c/wc/ec)65/1/0 0.0%
ipc00000006_sensors.qcom (): (0 s) Cnt:(c/wc/ec)64/1/0 0.0%
ipc00000003_rmt_storage (): (0 s) Cnt:(c/wc/ec)64/1/0 0.0%
======================
Alarms (requires root)
======================
android (): Wakeups: 64 (9.5 / hr.)
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 14, Intent: android.appwidget.action.APPWIDGET_UPDATE cmp={de.devmil.minimaltext/de.devmil.minimaltext.MinimalTextWidget_1_1}
Alarms: 14, Intent: android.appwidget.action.APPWIDGET_UPDATE cmp={de.devmil.minimaltext/de.devmil.minimaltext.MinimalTextWidget_2_1}
Alarms: 33, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED
Alarms: 1, Intent: android.appwidget.action.APPWIDGET_UPDATE cmp={com.painless.pc/com.painless.pc.PCWidgetActivity}
Alarms: 1, Intent: com.android.server.IdleMaintenanceService.action.UPDATE_IDLE_MAINTENANCE_STATE
Alarms: 1, Intent: android.content.syncmanager.SYNC_ALARM

com.google.android.gms (): Wakeups: 16 (2.4 / hr.)
Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.playlog.uploader.UploaderAlarmReceiver}
Alarms: 12, Intent: {com.google.android.gms/com.google.android.gms.checkin.EventLogService$Receiver}
Alarms: 4, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.security.snet.SnetService}

com.android.deskclock (): Wakeups: 8 (1.1 / hr.)
Alarms: 8, Intent: change_state cmp={com.android.deskclock/com.android.deskclock.alarms.AlarmStateManager}
Alarms: 0, Intent: com.android.deskclock.ON_QUARTER_HOUR

com.quoord.tapatalkxdapre.activity (): Wakeups: 3 (0.4 / hr.)
Alarms: 3, Intent: {com.quoord.tapatalkxdapre.activity/com.quoord.tapatalkpro.alarm.PingsOnAlarmReceiver}

com.android.keyguard (): Wakeups: 1 (0.1 / hr.)
Alarms: 1, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD

======================
Network (requires root)
======================
==========
CPU States
==========
2.27 GHz (): 1 m 50 s 0.5%
1.96 GHz (): 6 s 0.0%
1.73 GHz (): 6 s 0.0%
1.57 GHz (): 4 s 0.0%
1.5 GHz (): 5 s 0.0%
1.27 GHz (): 9 s 0.0%
1.19 GHz (): 7 m 45 s 1.9%
1.04 GHz (): 1 m 43 s 0.4%
960 MHz (): 1 m 45 s 0.4%
883.2 MHz (): 3 m 9 s 0.8%
729.6 MHz (): 3 m 21 s 0.8%
652.8 MHz (): 10 m 11 s 2.5%
422.4 MHz (): 3 h 1 m 10 s 44.9%
300 MHz (): 3 h 12 m 12 s 47.6%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 37 s (Wl: 3 elements; KWl: 0elements; NetS: 4 elements; Alrm: 0 elements; Proc: 12 elements; Oth: 5 elements; CPU: 14 elements)
ref_custom: Reference ref_custom created 17 m 28 s (Wl: 7 elements; KWl: 45elements; NetS: 9 elements; Alrm: 4 elements; Proc: 52 elements; Oth: 8 elements; CPU: 15 elements)
ref_current: Reference ref_current created 7 h 1 m 10 s (Wl: 12 elements; KWl: 49elements; NetS: 9 elements; Alrm: 7 elements; Proc: 67 elements; Oth: 9 elements; CPU: 15 elements)

One thing that is interesting to note is that there is no reference to Deep Sleep in cpu time. If you look again at the short 5/5 test you'll see the same. Ondemand does have Deep Sleep, granted it is 0.0% but it does have an entry. I wonder how much time it would accumulate over 6-8hrs.

In the past I know for a fact interactive did go into Deep Sleep during playback. It was for relatively short times over many hours. I don't recall exactly how much but I want to say for at least a few minutes over the course of 6-8hrs. I remember this because I kept wondering how it can Deep Sleep while constantly processing audio? Is it due to dsp tunneling? And for example if it can Deep Sleep for 1min, is it possible to get it to 2min, or 5min?

I'll do another test tonight with ondemand and a lower max freq and see if it accumulates any time.

EDIT: I just did a quick test of ondemand with a 1GHz cap. No Deep Sleep at all, just like interactive. Hmmm. Interesting.

Great work! Thanks for looking into it!