[BetterBatteryStats] damian5000:
That will be impossible. It's some Chinese nuts who have apparently thought it's cool to hide this info from people. Likely all Aliyun kernels. THL is in cahouts with Alibaba. Nothing good will come out of this turd fork. As I said before, they make great phones for the money, but I won't be buying another if I can't figure this out.

You see in the images it shows it's the Kernel (OS) as reported by GSAM, and no other apps show up for significant amount of wake periods. But I'm wondering if it's RELATED to interacting with another app. Is that possible? I'm asking because I don't want to go through trouble shooting each app if it's not a possibility. The only info I have looks like this:

https://drive.google.com/file/d/0B1y5ZqRAxj5Ld1M4SnVsWGJDc2s/edit?usp=sharing

Here is usage while phone kept awake for 20 hours by Kernel. It's interesting it's only taken 10m of CPU time. It's just locking the phone awake for some poo reason.

GSam Labs - Battery Monitor - Export Data

Kernel (Android OS)

Jun 10, 2014 9:36:55 PM

Usage Details

CPU Usage:10m 58s

CPU Usage (Background Only):10m 58s

Keep Awake:19h 13m 23s

App UID:0

Wakelock Detail

Included Packages

Included Processes

kworker/4:1

kworker/4:0

kworker/7:1

migration/4

kworker/6:0

migration/3

kworker/6:1

migration/2

vold

migration/1

mtk_stp_psm

kworker/7:0

jbd2/mmcblk0p7-

migration/7

migration/6

migration/5

kworker/u:4

kworker/5:1

kthreadd

migration/0

btif_rxd

kworker/5:0

kworker/0:4

kworker/0:0

kworker/u:0

kworker/0:1

kworker/0:2

kworker/u:2

kworker/u:1

kworker/0:3

bdi-default

debuggerd

tx_thread

sh

disp_clean_up_k

ueventd

bat_thread_kthr

disp_config_upd

flush-179:96

ion_mm_heap

kswapd0

disp_ovl_kthrea

ksoftirqd/6

ksoftirqd/7

/init

ksoftirqd/0

ksoftirqd/1

mtk charger_hv_

ksoftirqd/4

ksoftirqd/5

ksoftirqd/2

ksoftirqd/3

pmic_thread_kth

app_process

mmcqd/0

netd

ptp volt

zygote

kworker/1:2

libestool2.so

flush-179:0

kworker/1:1

kworker/1:0

wdtk-4

wdtk-3

wdtk-2

workqueue_trust

wdtk-1

mtk_wmtd

wdtk-7

wdtk-6

wdtk-5

kworker/2:1

kworker/2:0

kworker/3:1

fsnotify_mark

wdtk-0

kworker/3:0

sync_supers

Here is when the phone was deep sleeping fine:

Usage Details

CPU Usage:7s

CPU Usage (Background Only):7s

Keep Awake:9s

App UID:0

Wakelock Detail

Included Packages

Included Processes

kworker/4:1

kworker/4:0

kworker/7:1

migration/4

kworker/6:0

migration/3

kworker/6:1

vold

migration/2

migration/1

kworker/7:0

jbd2/mmcblk0p7-

migration/7

migration/6

migration/5

kworker/u:4

kworker/5:1

kthreadd

btif_rxd

migration/0

loop1

kworker/5:0

kworker/0:4

su

kworker/0:0

kworker/u:0

kworker/0:1

kworker/u:2

kworker/u:1

kworker/0:3

tx_thread

sh

disp_clean_up_k

bat_thread_kthr

disp_config_upd

kswapd0

ion_mm_heap

disp_ovl_kthrea

ksoftirqd/6

ksoftirqd/7

/init

ksoftirqd/0

ksoftirqd/1

mtk charger_hv_

ksoftirqd/4

ksoftirqd/5

ksoftirqd/2

ksoftirqd/3

pmic_thread_kth

mmcqd/1

app_process

mmcqd/0

netd

zygote

kworker/1:2

flush-179:0

kworker/1:1

kworker/1:0

kworker/2:1

kworker/2:0

kworker/3:1

kworker/3:0

I have a question, Is it likely the kernel itself doing something on it's own, or is it related to it's interaction with an app? :rolleyes: