[T-Mobile, Samsung Galaxy SIII] Hairy07:
These are shots after 1 hour of screen use using airplane mode. Extrapolation means a screen lifetime of about 7 hrs. Not sure if that's considered good under airplane mode.

Bbs dump:

=================== General Information ===================

BetterBatteryStats version: 1.13.4.0

Creation Date: 2013-06-26 13:20:18

Statistic Type: Unplugged to Current Since 6 h 44 m 9 s

VERSION.RELEASE: 4.2.2

BRAND: samsung

DEVICE: d2tmo

MANUFACTURER: samsung

MODEL: SGH-T999 OS.VERSION: 3.4.45-cyanogenmod-gaff1224

BOOTLOADER: T999UVDLJC

HARDWARE: qcom

FINGERPRINT: samsung/d2tmo/d2tmo:4.1.1/JRO03L/T999UVDLJA:user/release-keys

ID: JDQ39E

TAGS: test-keys

USER: jenkins

PRODUCT: d2tmo

RADIO: T999UVDLJC

Rooted: true

============ Battery Info ============

Level lost [%]: Bat.: -13% (100% to 87%) [1.9%/h]

Voltage lost [mV]: (4116-4101) [2.2%/h]

=========== Other Usage ===========

Deep Sleep (): 5 h 35 m 48 s (20148 s) Ratio: 83.1%

Awake (): 1 h 8 m 21 s (4101 s) Ratio: 16.9%

Screen On (): 1 h 4 m 26 s (3866 s) Ratio: 15.9%

No Data Connection (): 6 h 44 m 9 s (24249 s) Ratio: 100.0%

No or Unknown Signal (): 6 h 44 m 9 s (24249 s) Ratio: 100.0%

Screen dark (): 28 m 58 s (1738 s) Ratio: 7.2%

Screen dimmed (): 33 m 36 s (2016 s) Ratio: 2.1%

Screen light (): 1 m 50 s (110 s) Ratio: 0.1%

========= Wakelocks =========

ActivityManager-Launch (Android System): 52 s (52 s) Count:237 0.2%

AlarmManager (Android System): 36 s (36 s) Count:491 0.2%

AudioOut_2 (1013): 31 s (31 s) Count:7 0.1%

show keyguard (Android System): 21 s (21 s) Count:79 0.1%

JuiceDefender.Service (JuiceDefender): 19 s (19 s) Count:81 0.1%

Cleaner (com.oasisfeng.greenify.Greenify): 10 s (10 s) Count:6 0.0%

ActivityManager-Sleep (Android System): 9 s (9 s) Count:531 0.0%

StartingAlertService (Calendar): 8 s (8 s) Count:7 0.0%

RILJ (Phone): 6 s (6 s) Count:105 0.0%

AlarmClock (com.android.deskclock.Clock): 6 s (6 s) Count:15 0.0%

*vibrator* (com.android.deskclock.Clock): 5 s (5 s) Count:9 0.0%

sendinactive (com.whatsapp.WhatsApp): 5 s (5 s) Count:13 0.0%

FbClientConnManager (com.facebook.katana.Facebook): 4 s (4 s) Count:6 0.0%

keyguardWakeAndHandOff (Android System): 3 s (3 s) Count:278 0.0%

Event Log Service (Google Services): 2 s (2 s) Count:14 0.0%

AlarmManager (Google Services): 2 s (2 s) Count:94 0.0%

BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 1 s (1 s) Count:7 0.0%

================ Kernel Wakelocks ================

"PowerManagerService" (): 1 m 40 s (100 s) Cnt:(c/wc/ec)305/0/0 0.4%

"sec-battery-monitor" (): 1 m 14 s (74 s) Cnt:(c/wc/ec)281/0/0 0.3%

"alarm_rtc" (): 32 s (32 s) Cnt:(c/wc/ec)146/124/12 0.1%

"PowerManagerService.Broadcasts" (): 18 s (18 s) Cnt:(c/wc/ec)95/0/0 0.1%

"alarm" (): 8 s (8 s) Cnt:(c/wc/ec)296/0/0 0.0%

"mmc1_detect" (): 7 s (7 s) Cnt:(c/wc/ec)179/0/0 0.0%

"sec-battery-measure" (): 2 s (2 s) Cnt:(c/wc/ec)287/0/0 0.0%

"KeyEvents" (): 1 s (1 s) Cnt:(c/wc/ec)8409/0/0 0.0%

"power-supply" (): (0 s) Cnt:(c/wc/ec)269/0/0 -0.0%

"qmuxd_port_wl_0" (): (0 s) Cnt:(c/wc/ec)519/0/0 0.0%

"smdcntl0" (): (0 s) Cnt:(c/wc/ec)516/0/0 0.0%

"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)179/0/0 0.0%

====================== Alarms (requires root) ======================

====================== Network (requires root) ======================

========== CPU States ==========

384 MHz (): 59 m 40 s 14.8%

486 MHz (): 46 s 0.2%

594 MHz (): 22 s 0.1%

702 MHz (): 16 s 0.1%

810 MHz (): 9 s 0.0%

918 MHz (): 8 s 0.0%

1.03 GHz (): 4 s 0.0%

1.13 GHz (): 4 m 34 s 1.1%

1.24 GHz (): 21 s 0.1%

1.35 GHz (): 29 s 0.1%

1.46 GHz (): 10 s 0.0%

1.51 GHz (): 1 m 15 s 0.3%

Deep Sleep (): 5 h 35 m 48 s 83.1%

================== Reference overview ==================

ref_boot: Reference ref_boot created 1 m 38 s (Wl: 3 elements; KWl: 0elements; NetS: null; Alrm: null; Proc: 1 elements; Oth: 5 elements; CPU: 3 elements)

ref_unplugged: Reference ref_unplugged created 19 h 42 m 4 s (Wl: 0 elements; KWl: 30elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 13 elements)

ref_charged: Reference ref_charged created 19 h 42 m 4 s (Wl: 0 elements; KWl: 30elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 13 elements)

ref_current: Reference ref_current created 1 d 2 h 26 m 14 s (Wl: 17 elements; KWl: 30elements; NetS: null; Alrm: null; Proc: 11 elements; Oth: 8 elements; CPU: 13 elements)

Is there a way to determine if screen is using more power than it should? If the screen is somehow using more power than it should, then we obviously have a screen issue.

otherwise, it appears that some processes run only when the screen is on and eats up juice. The Q is then, can we find out what the heck is it?