Develop Bugs

CM9a4 FE22 kernel battery drain

In 10 hours 15 minutes of just sitting in my house with Wifi on, my phone dropped from 100% to 40%. Screen was off the entire time, sync was turned on. This is CM9 w/FE22 kernel and FE16 modem. Help me figure out what is using all the battery.
Phone was awake for 5h 55m and in deep sleep for only 4h 22m:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wifi was on the entire time, something kept waking the phone at no set interval, screen was off the entire time.
Of the 60% of the battery that is drained, 86% of it was from Android OS. So, Android OS ate 51.6% of my battery just by sitting there, with the screen off. Wifi ate 3% of my battery, Cell Standby ate 2.4% of my battery, screen time (less than 10 minutes) ate up 1.8%, and Phone Idle ate up 1.2%. 51.6 + 3 + 2.4 + 1.8 = 58.8%. 1.2% is unaccounted for, but that is probably because Android rounds the percentages to the nearest whole number. I didn't get a screenshot of the Android OS battery usage, but the CPU Total for Android OS was 3h 44m 27s, and Keep Awake was 5h 30m 31s.
According to Badass Battery, 41.1% of my battery drain was due to App Usage.
The kernel ate up 31.1% of my battery. You can see the rest of the list...
Processes included in the Kernel are:
pppd
ksdioirqd/mmc2
dhd_cfg80211_ev
wimax_queue
vold
migration/1
file-storage
ecryptfs-kthrea
jbd2/mmcblk0p7-
kworker/u:4
kworker/u:3
kthreadd
su
kworker/0:4
cyasblkdev_queu
kworker/0:0
kworker/u:0
kworker/0:1
kworker/u:2
kworker/0:2
irq/359-max8997
kworker/0:3
kworker/u:1
bdi-default
debuggerd
flush-253:0
sh
dhd_sysioc
ueventd
pppd_runner
dhd_watchdog
mmcqd/0boot0
mmcqd/0boot1
jbd2/mmcblk0p10
kswapd0
irq/356-mxt224_
installd
cyasdevice_slee
/init
ksoftirqd/0
ksoftirqd/1
irq/361-wimax_i
app_process
mmcqd/0
netd
watchdog/0
watchdog/1
zygote
kworker/1:2
flush-179:0
kworker/1:1
kworker/1:0
dhd_dpc
sync_supers
Is there a way to see how much battery each process is eating up?

I rebooted my phone today and it magically lost 19%.
Did your led light ever come on? I forget all the wake locks.

yeah, actually the led light does come on. i should disable that.

Same story here. I would like to know what is causing it too.

Chris41g narrowed it down to pppd and wifi conflicting with each other, at least in my case. Battery life is excellent when wifi is turned off, but once it's on, battery life is terrible.

I was getting terrible battery life on alpha 4.

I am having the same issue

Same problem kernel eats 80%, currently on CM9 ( cm-9-20120628-NIGHTLY-n7000 )..

Jelly Bean: What is your percent battery drain during DEEP SLEEP?

Ever since I moved to JB, my phone has been experiencing high battery drain DURING DEEP SLEEP!
Before JB, with everything set up on my phone BEING THE SAME, the phone would only drain 0.5% - 1.0% per hour. Now, according to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My battery drain is:
100% total - 71% remaining = 29% used
29% used * 81% used while in DEEP SLEEP = 23.49% total battery drain used while in DEEP SLEEP
7:10 (hrs:min) spent in DEEP SLEEP = 7hr * 60min/hr + 10min = 430 minutes spent in DEEP SLEEP
23.49% total battery drain used while in DEEP SLEEP / 430 minutes spent in DEEP SLEEP = 3.278% drain per hour while in DEEP SLEEP
Click to expand...
Click to collapse
My battery drain while in DEEP SLEEP basically tripled! Is this happening to anyone else?
My Gnex has the following:
ROM: CodeNameAndroid 3.5.0
Kernel: this ROM's built in kernel (3.0.41-tuna-faux123-jb-020)
I have tried two other kernels for about 2-3 days each with the same results, those kernels are: Franco Milestone 5 and Trinity

use betterbattery stats to checkout wakelocks, most likely you have a misbehaving app.
Sent from my i9250

Here purely jb 4.1.1 stock rom around 1% in sleep mode
Sent from my Galaxy Nexus using xda app-developers app

completely stock gsm 4.1.1 around 3-4% as well.
I don't have better battery stats but from GSam Battery Monitor: It shows my Maps waking the device few hundred times every several hours, it probably wakes the phone about 30-50 times per hour. I used to have Latitude enabled but I disabled that, I'd like to keep Google Now working so I have left the Google's "Location Service" on. Is this normal behavior? It seems ridiculously excessive for the map to wake the phone that often.

stock rom with data disabled 10hrs and hasnt budged yet (idle)
---------- Post added at 05:29 PM ---------- Previous post was at 05:29 PM ----------
stock ota jb as well. prolly an app that doesnt like jb

GSM GNex + Stock JB Lite + Trinity stable-35 kernel - wifi always on - data sync on - emails on push
to the OP - what does betterbatterystats show for kernel/partial wakelocks and processes?
Also, your calculation doesn't seem to be correct:
81% CPU idle time (deep sleep) is simply the time the CPU was sleeping (7 hrs 10 mins or 430 minutes) versus the total time in unplugged state (8 hrs 48 mins or 528 minutes) so 430/528*100 = 81%. Your phone was in deep sleep for 81% of the time. That doesn't equate to it using 81% of your battery drainage (which you derive by 29% * 81). The remaining 19% of the time your CPU was NOT in deep sleep is what used the majority of your battery drain.
You need to charge to full then reset cpu spy and turn screen off and let it be like that (not use it) for 5-6 hours to get a clear picture of deep sleep batt. drain

Okay, I turned off Google Now and will keep it off for a few days and see if it makes any difference.

Guiding.God said:
GSM GNex + Stock JB Lite + Trinity stable-35 kernel - wifi always on - data sync on - emails on push
to the OP - what does betterbatterystats show for kernel/partial wakelocks and processes?
Also, your calculation doesn't seem to be correct:
81% CPU idle time (deep sleep) is simply the time the CPU was sleeping (7 hrs 10 mins or 430 minutes) versus the total time in unplugged state (8 hrs 48 mins or 528 minutes) so 430/528*100 = 81%. Your phone was in deep sleep for 81% of the time. That doesn't equate to it using 81% of your battery drainage (which you derive by 29% * 81). The remaining 19% of the time your CPU was NOT in deep sleep is what used the majority of your battery drain.
You need to charge to full then reset cpu spy and turn screen off and let it be like that (not use it) for 5-6 hours to get a clear picture of deep sleep batt. drain
Click to expand...
Click to collapse
You're right! I was thinking more in terms of overall battery drain. But, it's true, it could be draining LIKE MAD when it's on but it doesn't seem likely.
I just popped in a new battery. Only got about <6hrs total time on the last battery, way less than half what I used to get. My BBS doesn't show any useful info because I have it set to SINCE BOOT.
I'll post screen tomorrow. I'm hoping that I can get 1% drain every hour during DEEP SLEEP and I'm at 92% right now. So by morning, hoping to see 84ish% but my guess is that I'll be down to 72% or something.

I turn off data when idle unless on a work order or something but we communicate by text anyway. No data and idle it does not move like at all. Left it all night and after 9hrs it stayed at 81% where I left it. Dang that 3g radio must be very inefficient
-----------
Vaj tswv is the creation of people with nowhere left to turn

3g stand by, one night like 7,8 hours, took approximately 9%
Sent from my Galaxy Nexus using xda premium

About 1-2% at night (consider 8 hours sleeping).

Here's what I got this morning:
I never tether charge my batteries. I use an external charger and charge them. I put in a freshly charged battery and turned the screen off.
I also turned off Google Now and that seemed to help a bit. Now, the phone used:
8% in 4:29 = 1.78% per hour
It looks like Google Now could've been responsible for the 3%+ idle / DEEP SLEEP drain per hour.
I'd like to get back down to a more normal 1% idle/DEEP SLEEP drain per hour like I was getting with ICS.
How are you guys on JB getting <1% drain per hour in DEEP SLEEP? That's simply amazing!
Any input?
Lastly this is with CDMA/LTE.

I'm on GSM and I have only one battery, the 1750mAh that came with it. Have been stuck at home last couple of days so been using my PC for all internet tasks such as emails and browsing etc and also music. Phones been mostly idling and used only for calls, sms and whatsapp texts and so on and it's been on wifi all of that time with data sync on. Down to 37% or so now with about 2.5hrs of screen on time and 39-40 hrs total unplugged time. Most of the time the cpu state was deep sleep.
Your wakelocks show mediascannerservice, maps and amazon as the main ones. There have been some threads about those, maybe this one can point you in the right direction http://forum.xda-developers.com/showthread.php?t=1801378&page=2
On a separate note, I see you use Tasker too lol....any funky profiles you've set? It's a little confusing but I'm trying to get the hang of it.

faux and ktoonz. explain yourselves to your users

Certain people that use your work, trust you guys.
faux's 2.1ghz kernel is really 1.8
KT's kernel @ 1.5 is really running @ 1.86
he is making it seem his kernel is faster than it really is by
making it display x speed when it is really clocked higher.
Why faux does the opposite. I have no idea. But this is grimy.
here is KT747's code - you can see this for yourself at his github
here is the link to this part of his github -> https://github.com/ktoonsez/KT747-J...be41bf639e/arch/arm/mach-msm/acpuclock-8960.c
Code:
{ 1, { 1512000, HFPLL, 1, 0, 0x3C }, L2(16), 1200000 },
{ 1, { 1512000, HFPLL, 1, 0, 0x3E }, L2(16), 1200000 },
{ 1, { 1512000, HFPLL, 1, 0, 0x40 }, L2(16), 1200000 },
#ifdef CONFIG_SUPER_CLOCKED
{ 1, { 1512000, HFPLL, 1, 0, 0x42 }, L2(16), 1200000 },
{ 1, { 1512000, HFPLL, 1, 0, 0x44 }, L2(16), 1200000 },
#endif
{ 0, { 0 } }
};
this is part of his "static struct acpu_level acpu_freq_tbl_8960_kraitv2_stock[] = {" table
now lets have a look here
Code:
{ 1, { 1512000, HFPLL, 1, 0, 0x42 }, L2(16), 1200000 },
{ 1, { 1512000, HFPLL, 1, 0, 0x44 }, L2(16), 1200000 },
what he have here is some additional 1.512 entries on top of the stock samsung one
lets take this apart
1512000 is the clock speed displayed in sysfs, or apps such as system tuner, or set cpu - it has NO impact on cpu speed - you can put ANY number here
HFPLL is the reference clock, for most MSM based devices, HFPLL = 27 MHz, or 27000 Hz
the "1" following HFPLL is the divider used - mainly for lower clock speeds, as any number divided by 1 is the number
now on to the good part
the 0x42
and 0x44
are the multipliers used to adjust the clock
so
convert 42 hex to decimal, we get 66
we multiply 66 by 27,000 and we get 1782000
we divide by 1, we get 1782000, or 1.782 GHz
now - since he also uses 0x44 - lets do some math
0x44 hex = 68 dec
68 x 27000 = 1836000
1836000 divided by 1 = 1836000
so, his kernel will display 1.5GHz, even though it is really running 1.836
here are some pics for further proof. because faux has either deleted or removed his git. or made it hidden. who knows. he's a fox (pun). these are of ktoonz' however, but they use the same tricky mathematics nonetheless.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dont have to be a genius to see it. its simple math.
All respect. Lost. Until explanation is provided.
Pretty sheisty when you take donations for your "superior" work.

So faux kernel was set to.. .... wait for it..... a "faux 1.5 GHz".... ??
Looollll

It's 2:57 am I'm sure this thread will closed.by 3:00 am
Sent from my SGH-T999 using xda app-developers app

OP updated with screen shots... since faux decided to hide or delete his entries about ten minutes ago. i figured he would do this, because he is a faux

cobraboy85 said:
Did you cure cancer or something?
Click to expand...
Click to collapse
iirc he's a douche... (lol.. Google it)

Holy crabs, what is going on? That wins pic of the year in any case. "There's a cobraboy in my boot." Let's just hope the boot doesn't come and find you!
Also, to quote, you really have no ****ing clue who I am? Really? Son of a ***** you're re...diculously uproarious, son.

cobraboy85 said:
i found this rather funny. kind of depicts everything this thread stands for.
Click to expand...
Click to collapse
I'm so sleepy but waiting to see when they close this lol
Sent from my SPH-L710 using Tapatalk 2

oh i promise, it will be closed. and deleted as well. any type of truth around here about what people are really doing gets stifled out quickly.
i know people that use their kernels, and i have before. and this is flat out dishonest when you take donations from people for your "superior" work.

cobraboy85 said:
oh i promise, it will be closed. and deleted as well. any type of truth around here about what people are really doing gets stifled out quickly.
i know people that use their kernels, and i have before. and this is flat out dishonest when you take donations from people for your "superior" work.
Click to expand...
Click to collapse
It is..I have only ran one of those kernels it was great for a couple days then it went all weird on me..plus didn't like the app that forcefully was added. But this is shinning light to a point, but at least from sprint section there are limited kernels, therefore his creates traffic to that section even other kernels I've seen with his "governor" so doubt any action would be taken mods will point towards the disclaimer, probably hand out warnings if not bans and **** will remain dude
Sent from my SPH-L710 using Tapatalk 2

well hopefully that is all that happens, but we'll see. history of this site says otherwise, however.
i just want an explanation. and not some slimy excuse, which unfortunately faux is known for from what i have observed before.

Man wish it would happen but I seriously doubt it...another thing that will get blamed on "anthrax" people starting ****. Which is not even the case but the disclaimer and past actions here I guess will be used to scapegoat into no explanation
Sent from my SPH-L710 using Tapatalk 2

That escalated quickly!
Sent from my SGH-T999

chrisram88 said:
That escalated quickly!
Sent from my SGH-T999
Click to expand...
Click to collapse
And died quickly, I was kinda hoping for a response from one of the devs :-\

we need/deserve some answers. do we need to start a petition or something. if we dont get some answers im going to all the android news sites to get the ball rolling with these saved pages. thanks for pointing this out cobraboy85

So faux still doesn't get his clock
tables right?
Or another innovation?
Sent from my SGH-T889 using Tapatalk 2

imneveral0ne said:
And died quickly, I was kinda hoping for a response from one of the devs :-\
Click to expand...
Click to collapse
I'm guessing that's not going to happen around here. But maybe we will get lucky..
Sent from my SGH-T999 with using Tapatalk 2

Closed due to flaming and disrespect to each other
It also became more about dev bashing than getting answers
Some posts had to be edited including the OP for name calling
The kernel source has ALWAYS been available as per GPL
And just NOW someone decides to examine it with a microscope?
We have too few developers making S3 kernels and you want to try and run them off?
XDA is about development and nothing here is aiding development
The developers in question have always responded to my PMs.
Perhaps you should have asked these questions there instead of this
Had this been an intelligent discussion politely requesting the developers to help understand what happened, it would have remained open.
Instead it became a circus and witch hunt. You might want to question the source of the information as well as the source of the code used as a base.

[Q] ADB but not charging?

Have been having charging issues mentioned in another thread, but was wondering if any one has seen this or could explain why it might happen?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADB connected
Connected as USB media device (not shown)
6% battery
Not charging
Any ideas? I am using a $30 disposable phone and am getting really frustrated with my GNex.
Thanks,
Annoyed and desperate

A little photo journey threw a failed charge cycle.
I also have the corresponding output of a SL4A script I wrote to monitor the battery and charging state and status
Code:
05-18-13 22:04:50
status : 4
temperature : 260
level : 17
battery_present : False
plugged : 2
health : 2
voltage : 3761
technology : Li-ion
05-18-13 22:08:57
status : 4
temperature : 290
level : 16
battery_present : False
plugged : 2
health : 2
voltage : 3726
technology : Li-ion
05-18-13 22:43:36
status : 4
temperature : 260
level : 18
battery_present : False
plugged : 2
health : 2
voltage : 3767
technology : Li-ion
05-18-13 23:12:49
status : 4
temperature : 250
level : 19
battery_present : False
plugged : 2
health : 2
voltage : 3773
technology : Li-ion
05-18-13 23:31:47
status : 4
temperature : 250
level : 20
battery_present : False
plugged : 2
health : 2
voltage : 3776
technology : Li-ion
05-18-13 23:50:00
status : 4
temperature : 250
level : 20
battery_present : False
plugged : 2
health : 2
voltage : 3776
technology : Li-ion
05-19-13 04:00:29
status : 4
temperature : 210
level : 41
battery_present : False
plugged : 2
health : 2
voltage : 3806
technology : Li-ion
05-19-13 05:03:43
status : 4
temperature : 200
level : 46
battery_present : False
plugged : 2
health : 2
voltage : 3817
technology : Li-ion
05-19-13 05:19:58
status : 4
temperature : 200
level : 46
battery_present : False
plugged : 2
health : 2
voltage : 3817
technology : Li-ion
05-19-13 13:29:58
status : 4
temperature : 310
level : 9
battery_present : False
plugged : 2
health : 2
voltage : 3671
technology : Li-ion
05-19-13 14:02:41
status : 4
temperature : 340
level : 6
battery_present : False
plugged : 2
health : 2
voltage : 3598
technology : Li-ion
The legend for the return values
Any ideas, particularly about the trickle charging while 'not charging', the discharge to 9% as seen on the right of pic12 and the 'battery_present : False' found in the script output.
Thanks,
Gabe

After multiple chargers, batteries, charging sub-boards and trip threw a re-flow oven it has been diagnosed as a bad power control chip. I hope that someone can benefit from this experience.
Gabe

[Q] Optimus G E975 overnight drain (2.2%/h)

Hello,
I've been experiencing abnormal standby battery loss overnight for a while now....can't rmb exactly when it started but it seems to be after I updated to the stock HK version 10D ROM....
it used be that I could leave wifi and radio on the whole night and the next morning after 7 or 8 hours I'd only lose 5-7%, whereas now this has spiked to 17-20%. I've tested with various combinations of Sync On/Off, WIFI On/Off, Airplaine On/Off, and my hunch tells me it's one or more of the Google Services processes lurking in the background....but I could be wrong.
So far I've done a couple of factory resets to no avail. It used to be that all it took was a factory reset to solve the battery drain issue. For me, this seems to point to the new 10D rom as the main culprit....
I'm rooted, and I've unlocked with FreeGee, though I somehow failed both attempts to flash a custom CM rom...so I'm stuck with the stock ROM and I desperately want to catch these evil processes draining my battery.....attached are my battery stats dumpfile, wakelock screenshots, etc.....any help or advice are much appreciated. thanks for your feedback in advance.....:crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-09-02 07:52:05
Statistic Type: Unplugged to Current
Since 7 h 34 m 12 s
VERSION.RELEASE: 4.1.2
BRAND: lge
DEVICE: geehrc
MANUFACTURER: LGE
MODEL: LG-E975
OS.VERSION: 3.4.0-perf-g1cbed94
BOOTLOADER: MAKOZ10o
HARDWARE: geehrc
FINGERPRINT: lge/geehrc_open_hk/geehrc:4.1.2/JZO54K/E97510d.1374296284:user/release-keys
ID: JZO54K
TAGS: release-keys
USER: xiaohan.liu
PRODUCT: geehrc_open_hk
RADIO:
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -16% (100% to 84%) [2.1%/h]
Voltage lost [mV]: (4291-4076) [28.4%/h]
===========
Other Usage
===========
Deep Sleep (): 7 h 12 m (25920 s) Ratio: 95.1%
Awake (): 22 m 12 s (1332 s) Ratio: 4.9%
Screen On (): 1 m 8 s (68 s) Ratio: 0.2%
Wifi On (): 7 h 34 m 12 s (27252 s) Ratio: 100.0%
Wifi Running (): 7 h 34 m 12 s (27252 s) Ratio: 100.0%
No Data Connection (): 7 h 34 m 12 s (27252 s) Ratio: 100.0%
No or Unknown Signal (): 7 h 34 m 12 s (27252 s) Ratio: 100.0%
Screen dark (): (0 s) Ratio: 0.0%
Screen light (): 1 m 8 s (68 s) Ratio: 0.2%
=========
Wakelocks
=========
AlarmManager (Android System): 13 m 54 s (834 s) Count:325 3.1%
fullsync (com.whatsapp.WhatsApp): 11 m 18 s (678 s) Count:18 2.5%
AudioOut_2 (1013): 10 m 41 s (641 s) Count:9 2.4%
GTALK_CONN (Google Services): 8 m 9 s (489 s) Count:187 1.8%
AlarmManager (com.asksven.betterbatterystats.BetterBatteryStats): 5 m 38 s (338 s) Count:16 1.2%
Event Log Service (Google Services): 5 m 11 s (311 s) Count:41 1.1%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 4 m 5 s (245 s) Count:209 0.9%
AlarmManager (Google Services): 3 m 35 s (215 s) Count:266 0.8%
backupdb (com.whatsapp.WhatsApp): 1 m 36 s (96 s) Count:1 0.4%
SyncLoopWakeLock (Android System): 54 s (54 s) Count:372 0.2%
AlarmManager (com.darshancomputing.BatteryIndicator.BatteryBot): 52 s (52 s) Count:110 0.2%
RILJ (Phone): 18 s (18 s) Count:478 0.1%
StartingAlertService (com.android.mms.Messaging): 17 s (17 s) Count:181 0.1%
*sync*_gmail-ls_Account {name=1e3be46b373d3218050523993f4d3df8, type=com.google} (com.google.android.gm.Gmail): 12 s (12 s) Count:6 0.0%
ActivityManager-Launch (Android System): 8 s (8 s) Count:45 0.0%
WifiOffDelayIfNotUsed (Android System): 8 s (8 s) Count:49 0.0%
Icing (Google Services): 7 s (7 s) Count:5 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 3 s (3 s) Count:2 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 3 s (3 s) Count:8 0.0%
sendinactive (com.whatsapp.WhatsApp): 1 s (1 s) Count:19 0.0%
DataTracker-FD (Phone): 1 s (1 s) Count:182 0.0%
sleep_broadcast (Android System): 1 s (1 s) Count:18 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 13 m 8 s (788 s) Cntc/wc/ec)742/0/0 2.9%
"msm_hsic_host" (): 7 m 27 s (447 s) Cntc/wc/ec)268/250/0 1.6%
"radio-interface" (): 4 m 14 s (254 s) Cntc/wc/ec)251/0/0 0.9%
"alarm" (): 18 s (18 s) Cntc/wc/ec)327/24/0 0.1%
"alarm_rtc" (): 16 s (16 s) Cntc/wc/ec)98/93/1 0.1%
"pm8xxx_adc_wakelock" (): 3 s (3 s) Cntc/wc/ec)2479/17/0 0.0%
"power-supply" (): 1 s (1 s) Cntc/wc/ec)3/1/0 -0.0%
"kickstart" (): (0 s) Cntc/wc/ec)3/0/0 0.0%
"qcril" (): (0 s) Cntc/wc/ec)197/0/0 0.0%
"qmuxd_port_wl_9" (): (0 s) Cntc/wc/ec)1689/0/0 0.0%
"sns_async_ev_wakelock" (): (0 s) Cntc/wc/ec)10/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)1748/39/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)449/2/0 0.0%
"rpm_regulator_tcxo" (): (0 s) Cntc/wc/ec)3/0/0 0.0%
======================
Alarms (requires root)
======================
com.google.android.gsf (): Wakeups: 56
Alarms: 7, Intent: com.google.android.intent.action.GTALK_RECONNECT
Alarms: 33, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 1, Intent: com.google.android.intent.action.SEND_IDLE
android (): Wakeups: 30
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 230, Intent: android.intent.action.TIME_TICK
Alarms: 15, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 7, Intent: com.lge.intent.action.LIGHTS_FLASH
Alarms: 36, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 8, Intent: android.appwidget.action.APPWIDGET_UPDATE
Alarms: 0, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 15, Intent: android.content.syncmanager.SYNC_ALARM
com.whatsapp (): Wakeups: 6
Alarms: 0, Intent: com.whatsapp.messaging.MessageService.CONNECTIVITY_RETRY_ACTION
Alarms: 1, Intent: ALARM_MESSAGES_DB_BACKUP
Alarms: 0, Intent: ALARM_ROTATE_LOGS
Alarms: 1, Intent: ALARM_AVAILABLE_TIMEOUT
Alarms: 8, Intent: ALARM_ACTION
Alarms: 4, Intent: com.whatsapp.MessageService.RECONNECT
com.google.android.googlequicksearchbox (): Wakeups: 4
Alarms: 4, Intent: com.google.android.googlequicksearchbox/com.google.android.velvet.VelvetBackgroundTasksImpl$Service
Alarms: 0, Intent: ACTION_MAYBE_UPDATE_CONTACTS
Alarms: 0, Intent: send_events
com.google.android.gms (): Wakeups: 2
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE
Alarms: 1, Intent: com.google.android.intent.action.SEND_IDLE
======================
Network (requires root)
======================
10076 (Wifi) (com.google.android.googlequicksearchbox.Google Search): 95.0 KBytes 31.4%
10015 (Wifi) (Google Services): 80.0 KBytes 26.6%
10025 (Wifi) (com.google.android.gm.Gmail): 62.0 KBytes 20.5%
10108 (Wifi) (com.whatsapp.WhatsApp): 36.0 KBytes 12.1%
10069 (Wifi) (com.lge.smartshare.SmartShare): 15.0 KBytes 5.2%
0 (Wifi) (0): 12.0 KBytes 4.2%
10110 (Wifi) (edu.shell.freegee_free.FreeGee): 156.0 Bytes 0.1%
==========
CPU States
==========
384 MHz (): 18 m 46 s 4.1%
486 MHz (): 2 s 0.0%
594 MHz (): 11 s 0.0%
702 MHz (): 7 s 0.0%
810 MHz (): 0.0%
918 MHz (): 1 m 5 s 0.2%
1.03 GHz (): 1 m 43 s 0.4%
1.51 GHz (): 14 s 0.1%
Deep Sleep (): 7 h 12 m 95.1%
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 13 h 57 m 57 s (Wl: 0 elements; KWl: 25elements; NetS: 27 elements; Alrm: 9 elements; Proc: 0 elements; Oth: 8 elements; CPU: 10 elements)
ref_charged: Reference ref_charged created 13 h 57 m 59 s (Wl: 1 elements; KWl: 25elements; NetS: 27 elements; Alrm: 9 elements; Proc: 0 elements; Oth: 9 elements; CPU: 10 elements)
ref_current: Reference ref_current created 21 h 32 m 9 s (Wl: 22 elements; KWl: 25elements; NetS: 27 elements; Alrm: 9 elements; Proc: 2 elements; Oth: 9 elements; CPU: 10 elements)
Click to expand...
Click to collapse

insights anyone, please?