[G2 Android Development] Dark_Az_:
My good gentlemen, I am in need of assistance.

I'm currently using 5.4.8 (the non-brand-new-kernel version just yet), and am having a battery issue. To put it simply, my phone randomly goes into overdrive with a rather generous amount of wake time (my battery has been lasting about 1 day with 1h or less of SOT, and I get over 4h of wake time.

The 2 biggest culprits seem to be the Kernel and Android System, however the same thing occurred with Llama Kernel and I find no particular wakelock to blame. Also, this doesn't seem to happen all of the time, the phone can stay "stable" for a number of hours (dropping about .7%/h, and suddenly it nosedives into 3%/h. All this while iddling away on its own).

Said behavior is usually encountered with some extra warmth on the phone (when I had Llama, I noticed the idle temperature to be 45~50º) and took the following screenshots:

These were taken a mere 20m after unplugging the phone, but you can already see a rather high number of wakes (GSam counted 6 minutes of waketime which it blamed on the Kernel). Here are the exports of GSam on them:

Kernel

GSam Labs - Battery Monitor - Export Data

Kernel (Android OS)

23 Jun 2015 13:57:53

Usage Details

CPU U

CPU Usage (Background Only):38s

Keep Awake:6m 7s

Bytes S KB

Bytes R KB

App UID:0

Wakelock Detail

Included Packages

Included Processes

file-storage

thermal-engine

rmt_storage

flush-179:0

sync_supers

auditd

mdss_fb0

dhcpcd

cfinteractive

wl_event_handle

sdcard

system

flush-0:18

zygote

bdi-default

ueventd

kswapd0

debuggerd

loc_launcher

jbd2/mmcblk0p14

jbd2/mmcblk0p22

jbd2/mmcblk0p30

jbd2/mmcblk0p31

jbd2/mmcblk0p35

adbd

lmkd

logd

netd

vold

workqueue_trust

/init

mpdecision

hwrng

khubd

time_daemon

kthreadd

installd

kworker/0:0

kworker/0:1

kworker/0:2

kworker/0:3

kworker/1:0

kworker/1:1

kworker/2:0

kworker/2:1

kworker/2:2

kworker/3:0

kworker/3:1

kworker/3:2

kworker/u:0

kworker/u:1

kworker/u:2

kworker/u:3

kworker/u:4

kworker/u:5

kworker/u:6

sensors.qcom

healthd

dhd_watchdog_th

mmcqd/0

qseecomd

ksoftirqd/0

ksoftirqd/1

ksoftirqd/2

ksoftirqd/3

wpa_supplicant

migration/1

migration/2

migration/3

dhd_dpc

dhd_rxf

netmgrd

kworker/0:0H

kworker/0:1H

kworker/0:2H

kworker/1:0H

kworker/1:1H

kworker/2:0H

kworker/2:1H

kworker/3:0H

kworker/3:1H

kworker/u:0H

irq/170-msm_sdc

Android System

GSam Labs - Battery Monitor - Export Data

Android System

23 Jun 2015 13:58:13

Usage Details

CPU U

CPU Usage (Background Only):36s

Keep Awake:4s

Number of Wake Locks:11

Number of times waking device:2

Bytes S bytes

Bytes R bytes

A

App UID:1000

Wakelock Detail

ActivityManager-Launch1.6s(5)

ConnectivityService1.2s(1)

PhoneWindowManager.mPowerKeyWakeLock1.2s(2)

SyncManagerHandleSyncAlarm0.0s(1)

LocationManagerService0.0s(1)

GpsLocationProvider0.0s(1)

Included Packages

Phone

Input Devices

Key Chain

Quickset SDK

Settings Storage

Android System

Settings

Fused Location

Dev Tools

Included Processes

audiod

system

com.uei.lg.quicksetsdk.maxq616

surfaceflinger

com.android.keychain

system:ui

com.android.settings

servicemanager

I should mention that this is a clean install of 5.4.8, currently using it's default Kernel. Had the same issue with 5.4.7 (didn't mention anything at the time since I was still troubleshooting all I could). Also I believe it is not Wifi related since sometimes the symptoms start while connected to it, and sometimes hours after I've disconnected.

I also left a quick screenshot below after 2 hours had past, and when the phone's temperature was back to normal and the number of wakes is reduced. I'm going to use it as normal for the day and re-take these screenshots / logs when the battery is at 10% or so. In the meantime, can anyone knowledgeable in the arts check these out and see if something is eluding me? Many thanks in advance and let me know if I need to provide any other details.