[Galaxy Note 3 Q&A, Help & Troubleshooting] AlexBlomkvist:
Hi,

I have a Note 3 SM-N9005 running a Temasek's UNOFFICIAL CM12.1 with an arte97 kernel and the latest bootloader and modem. Yesterday I changed my 18 months old battery with a new Anker 3200mAh battery.

Although, the battery life increased with about 30-40%, I still feel like I don't get enough Screen ON timpe when comparing my battery stats to others I found online. Some people get arroung 6 hours os Screen ON time, while I only got about 3 and a half hours. I also use greenify to freese a lot of apps and I did not use GPS in this session.

Can someone please take a look at my BBS logs and tell me if there's something that eats too much battery, some service that I may not be aware of? I'm asking this here becouse at a first glance, everything looks OK. Or maybe I am mistaken and my battery life is OK...or maybe after a new battery only reaches its full potential after more than one cycle, the attached logs being for my first cycle after the replacement. I am pasting here only the top consumers because the log is really long. For the entire thing, please check the attachment. There are many other parameters like alarms (many), CPU and Network logs.

I would really appreciate any oppinion. Thanks a lot.

BetterBatteryStats version: 2.0.0.0

Creation Date: 2015-06-30 19:29:03

Statistic Type: Unplugged to Current

Since 1 d 3 h 30 m 53 s

VERSION.RELEASE: 5.1.1

BRAND: samsung

DEVICE: hltexx

MANUFACTURER: samsung

MODEL: SM-N9005

OS.VERSION: 3.4.107-arter97-7.0.1-g17147d9-01916-g6f9acf6

BOOTLOADER: N9005XXUGBOEA

HARDWARE: qcom

FINGERPRINT: samsung/hltexx/hlte:4.4.2/KOT49H/N9005XXUENC2:user/release-keys

ID: LMY48B

TAGS: test-keys

USER: root

PRODUCT: cm_hlte

RADIO: N9005XXUGBOD3

Rooted: true

SELinux Policy: Permissive

BATTERY_STATS permission granted: true

XPosed BATTERY_STATS module enabled: false

============

Battery Info

============

Level lost [%]: Bat.: -96%(100% to 4%) [3.5%/h]

Voltage lost [mV]: (4231-3630) [21.8%/h]

===========

Other Usage

===========

Deep Sleep (): 21 h 28 m 31 s 78.1%

Awake (): 6 h 2 m 21 s 21.9%

Screen On (): 3 h 35 m 58 s 13.1%

Phone On (): 18 m 4 s 1.1%

Wifi On (): 14 h 41 m 25 s 53.4%

Wifi Running (): 14 h 41 m 24 s 53.4%

No Data Connection (): 13 h 31 m 15 s 49.1%

No or Unknown Signal (): 13 h 31 m 15 s 49.1%

Moderate Signal (): 10 m 41 s 0.6%

Screen dark (): 1 h 31 m 48 s 5.6%

Screen dimmed (): 1 h 59 m 56 s 7.3%

Screen medium (): 4 m 13 s 0.3%

======================================================

Wakelocks (requires root / system app on Android 4.4+)

======================================================

AudioMix (com.android.gallery3d.Gallery): 28 m 15 s Count:1 1.7%

ProximitySensorManager (): 15 m 6 s Count:784 0.9%

*net_scheduler* (Google Play services): 6 m 42 s Count:3940 0.4%

AudioMix (ro.callromania.callRomania): 5 m 32 s Count:11 0.3%

AudioIn (ro.callromania.callRomania): 5 m 32 s Count:10 0.3%

com.csipsimple.ongoingCallLock (ro.callromania.callRomania): 5 m 30 s Count:126 0.3%

com.csipsimple.CallProximity (ro.callromania.callRomania): 5 m 26 s Count:9 0.3%

AudioMix (1013): 5 m 22 s Count:186 0.3%

WeatherUpdateService (com.cyanogenmod.lockclock.cLock): 4 m 20 s Count:27 0.3%

Icing (Google Play services): 3 m 51 s Count:1798 0.2%

GCM_CONN_ALARM (Google Play services): 3 m 47 s Count:161 0.2%

AudioMix (com.google.android.youtube.YouTube): 3 m 7 s Count:3 0.2%

*alarm* (): 2 m 54 s Count:2459 0.2%

AudioMix (com.android.chrome.Chrome): 2 m 52 s Count:182 0.2%

WakeupEventReceiver (com.skype.raider.Skype): 2 m 41 s Count:1 0.2%

ActivityManager-Launch (): 2 m 29 s Count:768 0.2%

NextAlarmTracker (): 2 m 24 s Count:820 0.1%

AudioIn (com.google.android.googlequicksearchbox.Google App): 1 m 50 s Count:41 0.1%

RILJ (Phone): 1 m 9 s Count:5678 0.1%

sendinactive (com.whatsapp.WhatsApp): 1 m 2 s Count:51 0.1%

ConnectivityService (): 57 s Count:773 0.1%

GsmConnection (Phone): 39 s Count:5722 0.0%

SipWakeLock (ro.callromania.callRomania): 38 s Count:280 0.0%

AWakeLock (1013): 33 s Count:7 0.0%

AudioMix (com.facebook.katana.Facebook): 32 s Count:259 0.0%

================

Kernel Wakelocks !!! wakeup_sources !!!

================

PowerManagerService.Display (): 4 h 12 m 53 s Cnt: (c/wc/ec)120/0/0 15.3%

bam_dmux_wakelock (): 2 h 3 m 23 s Cnt: (c/wc/ec)3360/110/0 7.5%

PowerManagerService.WakeLocks (): 1 h 52 m 50 s Cnt: (c/wc/ec)10290/230/0 6.8%

wlan_rx_wake (): 44 m 35 s Cnt: (c/wc/ec)6497/78/6497 2.7%

wlan_wd_wake (): 44 m 34 s Cnt: (c/wc/ec)11015/182/0 2.7%

radio-interface (): 31 m 36 s Cnt: (c/wc/ec)1496/52/0 1.9%

event0-768 (): 11 m 4 s Cnt: (c/wc/ec)2721/2/0 0.7%

event1-768 (): 11 m 3 s Cnt: (c/wc/ec)2723/2/0 0.7%

event4-768 (): 10 m 53 s Cnt: (c/wc/ec)121859/2/0 0.7%

event15-768 (): 10 m 30 s Cnt: (c/wc/ec)3194/179/0 0.6%

event2-768 (): 10 m 28 s Cnt: (c/wc/ec)2964/2/0 0.6%

event3-768 (): 10 m 28 s Cnt: (c/wc/ec)2738/2/0 0.6%

nfc_wake_lock (): 9 m 59 s Cnt: (c/wc/ec)262/0/261 0.6%

wlan_wake (): 6 m 41 s Cnt: (c/wc/ec)247593/277/0 0.4%

alarm (): 4 m 53 s Cnt: (c/wc/ec)4311/824/0 0.3%

smdcntl0 (): 4 m 34 s Cnt: (c/wc/ec)9633/247/0 0.3%

resume_wakelock (): 4 m 17 s Cnt: (c/wc/ec)2715/2/2715 0.3%

alarm_rtc (): 3 m 20 s Cnt: (c/wc/ec)847/177/0 0.2%

ssp_wake_lock (): 2 m 43 s Cnt: (c/wc/ec)1506/9/30 0.2%

PowerManagerService.Broadcasts (): 2 m 16 s Cnt: (c/wc/ec)242/0/0 0.1%

wlan_ctrl_wake (): 2 m 12 s Cnt: (c/wc/ec)622/1/622 0.1%

sec-battery-monitor (): 58 s Cnt: (c/wc/ec)3403/179/0 0.1%

KeyEvents (): 39 s Cnt: (c/wc/ec)126749/379/0 0.0%