Database Users

[Q] Battery drain with no obvious perp?

I've been using this forum as resource in debugging a battery problem for some time now. Great resource.
I have a nexus 7, 32GB, 3G.
The "Here are the similar threads we found" section I got after writing the title is neat, but they all usually lead to an answer ala "An app is eating up your battery." "Google Now is bad." "Turn off wifi when sleeping." "Leave wifi on when sleeping." Not to mention baseband_xmm_power.
My tablet eats battery at a rate of 7-8%/hour, as measured by BBS.
My case is a bit odd. At first I thought I had the baseband_xmm_power wakelock problem. So I've installed Franco's kernel. I'm currently at r58. That did in fact stop all those, but it didn't really help me with the battery.
So I've done a number of factory resets (did many of those prior to rooting and francokerneling and a few after.) I've been running the tablet with nothing installed except the apps that comes with. In safe mode. Not syncing. In airplane mode. Still eating battery.
So I bought BBS. If you have any problem with battery/power/runaway apps: Buy That App. Now. Learn what it does! I also tried Wakelock Detector. If you're serious, get BBS.
So why am I still unhappy?
BBS claims that my tablet has been sleeping for 10 hours, (Yes, really. Deep sleep.) having never been turned on once. It usually have few minutes of various wakeups, but the tablet is mostly deep sleeping. Checking the battery page in settings says "yup, sleeping. Screen off". Battery drained 80%. Sometimes it is blamed on "screen" which was on the few seconds it took me to sleep the app and the few seconds it took me get into BBS. "Tablet idle" is another favorite: "Battery used by tablet when idle" I think it says. Why not "eaten by gremlins"?
A few weeks ago I noticed that the tablet was hot in the upper left corner. (holding the n7 in portrait mode, with the camera on top). I repeated the 10h deep sleep maneuver only checking the heat of the tablet. Hot all through the day. Deep sleeping all day. Repeated in safe mode. Same result. After a full reset. Same result. Something is using my battery to heat up the tablet.
So whats in that corner? ifixit.com has a great pictorial of what's inside an n7. It's not quite the same as mine... Oh. Did I not mention that I voided my warranty opening my n7? (Being a noob, I'm not allowed to post it here. Sorry.)
The motherboard of the N7 is shaped like an L. In the corner of the L is the Azurewave AW-NH665 chip which has Everything Radio on the N7. Wifi, bluetooth, it's even got and FM receiver and transmitter and it seems as if the chip supports 802.11a, even though the n7 does not.
Inside the AW is a bcm4330 which is The Chip to use if you need low power radio. Googling "bcm4330" it seems as if every portable device out there uses it. There is also an NFC chip. (I've done a bit of testing with/without NFC enabled. Most sources claims that NFC is really, really low power. I probably concur.)
I have access to an IR thermometer. Point and shoot and it'll tell you the temperature of the object you point it at. Ice cubes: 0C (32F)
So I reopened the n7, powered it up and put it to sleep. Withing seconds the bcm4330 went from room temperature to 38-40C (about 100F?). I measured a bit back and forth to see if the NFC chip was in fact the source. I doubt it.
I've read a bit about the bcm4330. It supports rfkill, which sounded just like something I could use to find the cause. I don't have the syntax at hand but you can say something like "rfkill block wifi" which, I think, will shut down wifi. It seemed to confuse the wifi settings button. Wifi was off, the tablet was offline but the ui hadn't noticed. Neither had the bcm4330. It was still chugging down mAmps...
There are two lines in the output from dmesg right after boot that puzzles me a bit:
<4>[ 1.999795] bcm4330_rfkill_probe: can't find bcm4330_32k_clk. assuming 32k clock to chip
<4>[ 1.999927] bcm4330_rfkill_probe : can't find reset gpio.
I don't know if this is normal. I only tested it twice and it was there both times.
If I power the tablet down it does not eat battery.
I tried to start the boot process while holding the volume down button to enter the boot menu. Leaving it like that the screen never turns off and I didn't leave it like that for long so I really don't at what rate the battery is used, but the hotspot did in fact heat up so I'm guessing that it still used battery.
I don't really know where to go from here. I used to think that the bcm4330 was confused about something and was in an active loop of sorts. But wouldn't a factory reset handle that? Or many resets? I've even had the battery disconnected for half a day and that should have reset it?
I want to thank the entire community for all the hits I've gotten and the leads I've been trying to follow, but now I'm stuck. Is there anything I haven't tested or told you about?
PS: I have tried several other, presumably, dead ends. Some of them really silly. "What if it's something in the air? Like my wifi at home telling it something?" Hardly, but I still wrapped the tablet in several layers of tinfoil to see if it made a difference. It didn't.

Since you didn't specifically mention it, I'm assuming you were on stock rom+kernel before you went to Franco's?

lhakedal said:
There are two lines in the output from dmesg right after boot that puzzles me a bit:
<4>[ 1.999795] bcm4330_rfkill_probe: can't find bcm4330_32k_clk. assuming 32k clock to chip
<4>[ 1.999927] bcm4330_rfkill_probe : can't find reset gpio.
I don't know if this is normal. I only tested it twice and it was there both times.
Click to expand...
Click to collapse
This is normal; I see it on mine too.
Have you tried resetting your ROM + user data back to stock, to isolate whether it's software or hardware?
How do your wakeup counts and CPU states look with airplane mode + safe mode both enabled? Do the Screen On times look accurate?
Are you sure it's just the bcm4330 chip that's heating up? Do you still observe this effect in airplane mode? You could try hitting other chips with freeze spray and seeing if they quickly exceed room temperature.
Any chance that something got broken when you opened the device?

adotkdotjh said:
Since you didn't specifically mention it, I'm assuming you were on stock rom+kernel before you went to Franco's?
Click to expand...
Click to collapse
Yes, I was. I went to Franco's to get rid of the baseband_xmm_power bug.

bespons appears
SW686 said:
This is normal; I see it on mine too.
Have you tried resetting your ROM + user data back to stock, to isolate whether it's software or hardware?
How do your wakeup counts and CPU states look with airplane mode + safe mode both enabled? Do the Screen On times look accurate?
Are you sure it's just the bcm4330 chip that's heating up? Do you still observe this effect in airplane mode? You could try hitting other chips with freeze spray and seeing if they quickly exceed room temperature.
Any chance that something got broken when you opened the device?
Click to expand...
Click to collapse
I haven't tried going back to stock. It would bring back the baseband_xmm_power wakelocks.
Didn't measure temperature in the two tests, but in both cases the outer shell was noticeably warm to touch.
[I'll paste the full reports below.]
Wakeup counts. First line is online, second is offline/airplanemode.
"baseband_xmm_power" (): 1 h 7 m 52 s (4072 s) Cntc/wc/ec)1599/0/0 14.0%
"baseband_xmm_power" (): 5 m 22 s (322 s) Cntc/wc/ec)55/0/0 1.4%
Is 1h7m a lot? It shouldn't account for a 61% drop in battery?
"wlan_rx_wake" (): 24 m 38 s (1478 s) Cntc/wc/ec)1544/0/1543 5.1%
NA offline.
"Other Usage"
Online:
Deep Sleep (): 6 h 38 m 21 s (23901 s) Ratio: 82.1%
Awake (): 1 h 19 m 27 s (4767 s) Ratio: 16.6%
Screen On (): 2 s (2 s) Ratio: 0.0%
Wifi On (): 7 h 57 m 49 s (28669 s) Ratio: 100.0%
Wifi Running (): 7 h 57 m 49 s (28669 s) Ratio: 100.0%
No Data Connection (): 7 h 57 m 49 s (28669 s) Ratio: 100.0%
No or Unknown Signal (): 7 h 57 m 49 s (28669 s) Ratio: 100.0%
Screen dark (): (0 s) Ratio: 0.0%
Screen dimmed (): 2 s (2 s) Ratio: 0.0%
Offline:
Deep Sleep (): 6 h 18 m 37 s (22717 s) Ratio: 98.2%
Screen dark (): 49 s (49 s) Ratio: 0.2%
Battery Info
Online:
Level lost [%]: Bat.: -61% (99% to 38%) [7.7%/h]
Voltage lost [mV]: (4136-3697) [55.2%/h]
Offline:
Level lost [%]: Bat.: -44% (100% to 56%) [6.9%/h]
Voltage lost [mV]: (4196-3793) [62.8%/h]
Screen time looks accurate. I didn't set a customref on the online test. I did the setup of the test, unplugged and put to sleep so the timing may be a few secs off.
The heat emanates from the corner where the 4330 is. There is another set of chips on the back of the MB. I guess freeze spray could help. I'll see if I have some. I'll check if we have an IR camera too, not just a thermometer.
The heating was the reason I opened it in the first place, so it predates the opening. I went in with plastic tools starting next to the sim card hatch. There is a number of feathered contacts (?) that connect to copper tape on the rear. They are intact.
Here is the BBStats from the online test:
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-05-01 17:19:47
Statistic Type: Unplugged to Current
Since 7 h 57 m 49 s
VERSION.RELEASE: 4.2.2
BRAND: google
DEVICE: tilapia
MANUFACTURER: asus
MODEL: Nexus 7
OS.VERSION: 3.1.10-franco.Kernel
BOOTLOADER: 4.18
HARDWARE: grouper
FINGERPRINT: google/nakasig/tilapia:4.2.2/JDQ39/573038:user/release-keys
ID: JDQ39
TAGS: release-keys
USER: android-build
PRODUCT: nakasig
RADIO: 1231_0.17.0_1205
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -61% (99% to 38%) [7.7%/h]
Voltage lost [mV]: (4136-3697) [55.2%/h]
===========
Other Usage
===========
Deep Sleep (): 6 h 38 m 21 s (23901 s) Ratio: 82.1%
Awake (): 1 h 19 m 27 s (4767 s) Ratio: 16.6%
Screen On (): 2 s (2 s) Ratio: 0.0%
Wifi On (): 7 h 57 m 49 s (28669 s) Ratio: 100.0%
Wifi Running (): 7 h 57 m 49 s (28669 s) Ratio: 100.0%
No Data Connection (): 7 h 57 m 49 s (28669 s) Ratio: 100.0%
No or Unknown Signal (): 7 h 57 m 49 s (28669 s) Ratio: 100.0%
Screen dark (): (0 s) Ratio: 0.0%
Screen dimmed (): 2 s (2 s) Ratio: 0.0%
=========
Wakelocks
=========
AlarmManager (Android System): 44 s (44 s) Count:542 0.2%
AudioOut_2 (1013): 3 s (3 s) Count:2 0.0%
Event Log Service (Google Services): 3 s (3 s) Count:19 0.0%
GTALK_ASYNC_CONN_ [email protected]/android_talkf1ef8825c8e5 (Google Services): 1 s (1 s) Count:1 0.0%
GTALK_CONN (Google Services): 1 s (1 s) Count:185 0.0%
*sync*_subscribedfeeds_Account {name=338e43a8455a5ac597caea168f73b6a5, type=com.google} (Google Services): 1 s (1 s) Count:249 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 1 s (1 s) Count:202 0.0%
AlarmManager (com.google.android.deskclock.Clock): 1 s (1 s) Count:32 0.0%
================
Kernel Wakelocks
================
"baseband_xmm_power" (): 1 h 7 m 52 s (4072 s) Cntc/wc/ec)1599/0/0 14.0%
"wlan_rx_wake" (): 24 m 38 s (1478 s) Cntc/wc/ec)1544/0/1543 5.1%
"alarm" (): 2 m 21 s (141 s) Cntc/wc/ec)713/408/0 0.5%
"alarm_rtc" (): 2 m 16 s (136 s) Cntc/wc/ec)184/0/69 0.5%
"PowerManagerService" (): 57 s (57 s) Cntc/wc/ec)780/0/0 0.2%
"wlan_wake" (): 2 s (2 s) Cntc/wc/ec)27719/1017/0 0.0%
"cable_state_changed" (): 1 s (1 s) Cntc/wc/ec)2/0/2 0.0%
"radio-interface" (): 1 s (1 s) Cntc/wc/ec)9/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)4367/0/0 0.0%
"PowerManagerService.Broadcasts" (): (0 s) Cntc/wc/ec)2/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)27/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
102 MHz (): 57 m 58 s 12.1%
475 MHz (): 21 m 25 s 4.5%
760 MHz (): 0.0%
1 GHz (): 0.0%
1.3 GHz (): 2 s 0.0%
Deep Sleep (): 6 h 38 m 21 s 82.1%
==================
Reference overview
==================
ref_custom: Reference ref_custom created 7 m 12 s (Wl: 0 elements; KWl: 0elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 0 elements; CPU: 5 elements)
ref_unplugged: Reference ref_unplugged created 7 m 16 s (Wl: 0 elements; KWl: 0elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 5 elements; CPU: 5 elements)
ref_current: Reference ref_current created 8 h 5 m 5 s (Wl: 8 elements; KWl: 11elements; NetS: null; Alrm: null; Proc: 19 elements; Oth: 9 elements; CPU: 6 elements)
And from the offline test:
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-05-02 12:29:43
Statistic Type: Custom to Current
Since 6 h 25 m 43 s
VERSION.RELEASE: 4.2.2
BRAND: google
DEVICE: tilapia
MANUFACTURER: asus
MODEL: Nexus 7
OS.VERSION: 3.1.10-franco.Kernel
BOOTLOADER: 4.18
HARDWARE: grouper
FINGERPRINT: google/nakasig/tilapia:4.2.2/JDQ39/573038:user/release-keys
ID: JDQ39
TAGS: release-keys
USER: android-build
PRODUCT: nakasig
RADIO: 1231_0.17.0_1205
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -44% (100% to 56%) [6.9%/h]
Voltage lost [mV]: (4196-3793) [62.8%/h]
===========
Other Usage
===========
Deep Sleep (): 6 h 18 m 37 s (22717 s) Ratio: 98.2%
Screen dark (): 49 s (49 s) Ratio: 0.2%
=========
Wakelocks
=========
ConnectivityService (Android System): 14 s (14 s) Count:22 0.1%
================
Kernel Wakelocks
================
"baseband_xmm_power" (): 5 m 22 s (322 s) Cntc/wc/ec)55/0/0 1.4%
"alarm_rtc" (): 36 s (36 s) Cntc/wc/ec)49/0/29 0.2%
"alarm" (): 15 s (15 s) Cntc/wc/ec)95/47/0 0.1%
"PowerManagerService" (): 15 s (15 s) Cntc/wc/ec)93/0/0 0.1%
"PowerManagerService.Broadcasts" (): (0 s) Cntc/wc/ec)4/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)146/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
102 MHz (): 5 m 48 s 1.5%
475 MHz (): 1 m 8 s 0.3%
760 MHz (): 0.0%
1 GHz (): 0.0%
1.3 GHz (): 8 s 0.0%
Deep Sleep (): 6 h 18 m 37 s 98.2%
==================
Reference overview
==================
ref_custom: Reference ref_custom created 20 h 49 m 21 s (Wl: 11 elements; KWl: 13elements; NetS: null; Alrm: null; Proc: 21 elements; Oth: 9 elements; CPU: 6 elements)
ref_unplugged: Reference ref_unplugged created 20 h 49 m 46 s (Wl: 0 elements; KWl: 13elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 6 elements)
ref_charged: Reference ref_charged created 20 h 49 m 46 s (Wl: 0 elements; KWl: 13elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 6 elements)
ref_current: Reference ref_current created 1 d 3 h 15 m 4 s (Wl: 5 elements; KWl: 13elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 6 elements)

If you still see the problem in airplane mode then I'd suggest running all tests in airplane mode. The more factors you can eliminate, the better.
I ran my 16GB wifi N7 (CM10.1) in airplane mode for ~6.5hrs and this is what my stats looked like:
Code:
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-05-02 19:54:42
Statistic Type: Custom to Current
Since 6 h 31 m 16 s
VERSION.RELEASE: 4.2.2
BRAND: Google
DEVICE: grouper
MANUFACTURER: Asus
MODEL: Nexus 7
OS.VERSION: 3.1.10-g5f0f8fd
BOOTLOADER: 4.18
HARDWARE: grouper
FINGERPRINT: google/nakasi/grouper:4.2.2/JDQ39/573038:user/release-keys
ID: JDQ39
TAGS: test-keys
USER: owner
PRODUCT: nakasi
RADIO:
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: 0% (100% to 100%) [0.0%/h]
Voltage lost [mV]: (4130-4119) [1.7%/h]
===========
Other Usage
===========
Deep Sleep (): 6 h 29 m 29 s (23369 s) Ratio: 99.5%
Awake (): 1 m 47 s (107 s) Ratio: 0.5%
Screen On (): 59 s (59 s) Ratio: 0.3%
Wifi On (): 13 s (13 s) Ratio: 0.1%
Wifi Running (): 12 s (12 s) Ratio: 0.1%
No Data Connection (): 6 h 31 m 16 s (23476 s) Ratio: 100.0%
No or Unknown Signal (): 6 h 31 m 16 s (23476 s) Ratio: 100.0%
Screen dark (): 53 s (53 s) Ratio: 0.2%
Screen dimmed (): 5 s (5 s) Ratio: 0.0%
=========
Wakelocks
=========
ConnectivityService (Android System): 42 s (42 s) Count:79 0.2%
AudioOut_2 (1013): 29 s (29 s) Count:8 0.1%
AlarmManager (Android System): 3 s (3 s) Count:78 0.0%
SCREEN_FROZEN (Android System): 2 s (2 s) Count:7 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:18 0.0%
================
Kernel Wakelocks
================
"PowerManagerService" (): 27 s (27 s) Cnt:(c/wc/ec)32/0/0 0.1%
"alarm_rtc" (): 14 s (14 s) Cnt:(c/wc/ec)23/0/6 0.1%
"alarm" (): 2 s (2 s) Cnt:(c/wc/ec)35/17/0 0.0%
"PowerManagerService.Broadcasts" (): (0 s) Cnt:(c/wc/ec)2/0/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)144/0/0 0.0%
"event1-499" (system, com.google.android.syncadapters.contacts, com.google.android.gsf, com.android.location.fused): (0 s) Cnt:(c/wc/ec)2/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
51 MHz (): 20 s 0.1%
102 MHz (): 1 s 0.0%
204 MHz (): 0.0%
340 MHz (): 43 s 0.2%
475 MHz (): 14 s 0.1%
640 MHz (): 5 s 0.0%
760 MHz (): 1 s 0.0%
860 MHz (): 0.0%
1 GHz (): 1 s 0.0%
1.1 GHz (): 0.0%
1.2 GHz (): 10 s 0.0%
1.3 GHz (): 7 s 0.0%
Deep Sleep (): 6 h 29 m 29 s 99.5%
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 2 m 50 s (Wl: 7 elements; KWl: 9elements; NetS: null; Alrm: null; Proc: 1 elements; Oth: 8 elements; CPU: 12 elements)
ref_charged: Reference ref_charged created 2 m 50 s (Wl: 7 elements; KWl: 9elements; NetS: null; Alrm: null; Proc: 1 elements; Oth: 8 elements; CPU: 12 elements)
ref_custom: Reference ref_custom created 2 m 59 s (Wl: 7 elements; KWl: 9elements; NetS: null; Alrm: null; Proc: 1 elements; Oth: 8 elements; CPU: 12 elements)
ref_current: Reference ref_current created 6 h 34 m 16 s (Wl: 10 elements; KWl: 8elements; NetS: null; Alrm: null; Proc: 2 elements; Oth: 9 elements; CPU: 13 elements)
Similarly, nothing in your offline test shows more than a few minutes' worth of system activity.
Franco's kernel is "supposed" to work on the tilapia but it might be worth reverting the whole unit to stock just to prove it isn't a software problem. Not sure what else to try at this point.
Can you slow-charge the unit from a PC's USB port, preferably for 24hrs, so you know for sure it's really starting at a full charge?

SW686 said:
If you still see the problem in airplane mode then I'd suggest running all tests in airplane mode. The more factors you can eliminate, the better.
I ran my 16GB wifi N7 (CM10.1) in airplane mode for ~6.5hrs and this is what my stats looked like:
Code:
===================
General Information
===================
[snipped]
Similarly, nothing in your offline test shows more than a few minutes' worth of system activity.
Franco's kernel is "supposed" to work on the tilapia but it might be worth reverting the whole unit to stock just to prove it isn't a software problem. Not sure what else to try at this point.
Can you slow-charge the unit from a PC's USB port, preferably for 24hrs, so you know for sure it's really starting at a full charge?
Click to expand...
Click to collapse
Amazing to see no drop in charge at all? Did you select the correct reference?
I've reverted to google's kernel.
The N7 has been charged in the asus 2A-charger so I feel quite confident that the battery is fully charged.
The tablet heated up considerably when i reflashed it so I've turned it off and left it in the charger to cool down and top off the battery.
I'll do another in-airplane-mode test with BBS later.
This is my second N7, the first I managed to crack the screen so 2/5ths of the screen is untouchable (s******) and I've been performing several similar tests on that as I have on the Hot-one.
1. It doesn't heat up while sleeping.
2. It has the baseband_xmm_power wakelock disease.
I'm wondering if I should try a motherboard swap. Put the healthy MB and the uncracked screen in the same tablet. Problem is that the connectors and various flat cables looks like a night mare to release and reattach.

lhakedal said:
Amazing to see no drop in charge at all? Did you select the correct reference?
Click to expand...
Click to collapse
Yes
After ~24 hours unplugged and in airplane mode, it's at 97% (0.1%/hr).
Not too surprising - it's a pretty well-optimized design from a power standpoint, and the battery is >4 Ah
I'm wondering if I should try a motherboard swap. Put the healthy MB and the uncracked screen in the same tablet. Problem is that the connectors and various flat cables looks like a night mare to release and reattach.
Click to expand...
Click to collapse
I haven't opened an N7 yet but I have broken other devices doing this... these toys are quite delicate. Not much to lose if both warranties are voided, though.
Having the right tools helps, of course.

Final update
It's been a while.
Found a video describing how to transplant a screen from one n7 to another. Did that. Wasn't completely impossible. Several different types of connectors, I had to use a magnifying glass on some of them to see how to open and close them.
Thanks for listening.

lhakedal said:
It's been a while.
Found a video describing how to transplant a screen from one n7 to another. Did that. Wasn't completely impossible. Several different types of connectors, I had to use a magnifying glass on some of them to see how to open and close them.
Thanks for listening.
Click to expand...
Click to collapse
Hi! Already wrote you several mails, and decided to write here in case google will put them to spam =).
So what was result?

Hello! I have problem with my Nexus 7 32gb mobile (3g).
Clear stock 4.4.4 (Tried AICP, cm11, cm12, stock 5.0.2 and e.t.) massive battery drain. 5%-10% in hour.
And if airplane on, (wifi and mobile off, sync off, only stock apps) the area on the top right corner of the motherboard warm.
I think it AzureWave AW-NH665
How fix it?

well well well,
I have the same problem, exactly
My Nexus 7 is 32G 3G, I flash the rom 5.1.1 from google( developers.google.com_android_nexus_images ), no work
finally I found the chip AW-NH665 warm, even in airplane mode.
since now is 2015, a nexus 7 2012 mother board is very very chip, 120RMB ( 20 USA$ ), I think by another mother board is a better way

[Q] Battery Drain Due To Suspend_Backoff Kernel Wakelock, Suspect Wi-Fi

Hi, I've been having issues with the suspend_backoff kernel wakelock since installing CM 10.1.3 stable. It is a fresh install (performed reset in CWM) with almost no user apps. I have disabled and signed out of most Google services, e.g. Google+, Hangouts, Google apps location, Google search, tailored ads, app verification. Bluetooth, NFC, and GPS are all disabled.
When Wi-Fi is enabled, I seem to get "no data connection". The phone is being kept awake by suspend_backoff.
When Wi-Fi is disabled and I am connected to 3G, this problem disappears and the phone is able to enter deep sleep.
I've tried to search for a solution. It is unrelated to the old msm_hsic_host wakelock problem that was fixed upstream by Google. It is also unrelated to Google Chrome problem, as it is not installed. I have tried deleting data and cache for Google apps and services, which does not appear to fix the issue.
===================
General Information
===================
BetterBatteryStats version: 1.13.4.0
Creation Date: 2013-10-08 11:28:28
Statistic Type: Boot to Current
Since 1 h 32 m 23 s
VERSION.RELEASE: 4.2.2
BRAND: google
DEVICE: mako
MANUFACTURER: LGE
MODEL: Nexus 4
OS.VERSION: 3.4.0-perf-g825e82a
BOOTLOADER: MAKOZ10l
HARDWARE: mako
FINGERPRINT: google/occam/mako:4.2.2/JDQ39/573038:user/release-keys
ID: JDQ39E
TAGS: test-keys
USER: jenkins
PRODUCT: occam
RADIO: M9615A-CEFWMAZM-2.0.1700.33
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -4% (90% to 86%) [2.6%/h]
Voltage lost [mV]: (4101-4116) [-9.8%/h]
===========
Other Usage
===========
Deep Sleep (): 18 m 28 s (1108 s) Ratio: 19.9%
Awake (): 1 h 13 m 55 s (4435 s) Ratio: 80.0%
Screen On (): 2 m 9 s (129 s) Ratio: 2.3%
Wifi On (): 1 h 32 m 23 s (5543 s) Ratio: 100.0%
Wifi Running (): 1 h 32 m 23 s (5543 s) Ratio: 100.0%
No Data Connection (): 1 h 28 m 20 s (5300 s) Ratio: 95.6%
No or Unknown Signal (): 1 h 28 m 20 s (5300 s) Ratio: 95.6%
Good Signal (): (0 s) Ratio: 0.0%
Screen dark (): 2 m 9 s (129 s) Ratio: 2.3%
=========
Wakelocks
=========
RILJ (Phone): 1 m 34 s (94 s) Count:177 1.7%
ConnectivityService (Android System): 1 m 7 s (67 s) Count:360 1.2%
NfcService:mRoutingWakeLock (com.android.nfc.Nfc Service): 14 s (14 s) Count:30 0.3%
GCM_CONN_ALARM (Google Services): 13 s (13 s) Count:200 0.2%
AlarmManager (Android System): 12 s (12 s) Count:340 0.2%
GpsLocationProvider (Android System): 5 s (5 s) Count:190 0.1%
AudioOut_2 (1013): 4 s (4 s) Count:7 0.1%
Checkin Service (Google Services): 4 s (4 s) Count:183 0.1%
ActivityManager-Launch (Android System): 4 s (4 s) Count:140 0.1%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats.BetterBatteryStats): 3 s (3 s) Count:7 0.1%
show keyguard (Android System): 3 s (3 s) Count:9 0.1%
WakefulIntentService[GCoreUlr-ExternalChangeService] (Google Services): 2 s (2 s) Count:313 0.1%
DHCP (Android System): 2 s (2 s) Count:214 0.1%
SyncLoopWakeLock (Android System): 2 s (2 s) Count:461 0.0%
GCM_CONN (Google Services): 2 s (2 s) Count:304 0.0%
AudioOut_3 (1013): 2 s (2 s) Count:2 0.0%
NetworkStats (Android System): 2 s (2 s) Count:126 0.0%
SMSDispatcher (Phone): 2 s (2 s) Count:13 0.0%
*sync*_subscribedfeeds_Account {name=b8c35ab0c3f90d29ae9cc189659604ee, type=com.google} (Google Services): 1 s (1 s) Count:3 0.0%
MediaScannerService (Media): 1 s (1 s) Count:2 0.0%
AlarmManager (Google Services): 1 s (1 s) Count:352 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:248 0.0%
ActivityManager-Sleep (Android System): 1 s (1 s) Count:471 0.0%
================
Kernel Wakelocks
================
"suspend_backoff" (): 54 m 31 s (3271 s) Cntc/wc/ec)330/0/330 58.8%
"msm_hsic_host" (): 3 m 35 s (215 s) Cntc/wc/ec)128/17/0 3.9%
"PowerManagerService" (): 3 m 31 s (211 s) Cntc/wc/ec)384/0/0 3.8%
"radio-interface" (): 1 m 33 s (93 s) Cntc/wc/ec)100/0/0 1.7%
"alarm_rtc" (): 1 m 13 s (73 s) Cntc/wc/ec)87/7/26 1.3%
"alarm" (): 4 s (4 s) Cntc/wc/ec)192/1/0 0.1%
"wlan" (): 3 s (3 s) Cntc/wc/ec)19/0/0 0.1%
"PowerManagerService.Broadcasts" (): 1 s (1 s) Cntc/wc/ec)19/0/0 0.0%
"qcril" (): 1 s (1 s) Cntc/wc/ec)344/0/0 0.0%
"KeyEvents" (): 1 s (1 s) Cntc/wc/ec)5732/0/0 0.0%
"power-supply" (): 1 s (1 s) Cntc/wc/ec)87/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)3407/0/1 0.0%
"qmuxd_port_wl_9" (): (0 s) Cntc/wc/ec)1263/0/0 0.0%
======================
Alarms (requires root)
======================
com.google.android.gms (): Wakeups: 36
Alarms: 22, Intent: com.google.android.intent.action.GCM_RECONNECT
Alarms: 1, Intent: com.google.android.gms.recovery.WAKEUP
Alarms: 8, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 5, Intent: com.google.android.intent.action.MCS_HEARTBEAT
android (): Wakeups: 16
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 0, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 10, Intent: android.net.wifi.DHCP_RENEW
Alarms: 5, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 1, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
com.android.phone (): Wakeups: 11
Alarms: 8, Intent: com.android.internal.telephony.gprs-reconnect.0
Alarms: 3, Intent: com.android.internal.telephony.gprs-data-stall
com.android.vending (): Wakeups: 6
Alarms: 3, Intent: {com.android.vending
Alarms: 3, Intent: {com.android.vending
com.google.android.gsf (): Wakeups: 3
Alarms: 3, Intent: {com.google.android.gsf
com.cyanogenmod.lockclock (): Wakeups: 1
Alarms: 1, Intent: {com.cyanogenmod.lockclock
com.google.android.talk (): Wakeups: 1
Alarms: 1, Intent: com.google.android.apps.babel.CLEANUP_DB
bbc.mobile.weather (): Wakeups: 1
Alarms: 1, Intent: {bbc.mobile.weather
com.mobitobi.android.gentlealarm (): Wakeups: 1
Alarms: 1, Intent: com.mobitobi.android.gentlealarm.ALARM_INIT
com.google.android.apps.plus (): Wakeups: 1
Alarms: 1, Intent: com.google.android.apps.plus.NEW_PICTURE
com.android.providers.calendar (): Wakeups: 1
Alarms: 1, Intent: com.android.providers.calendar.intent.CalendarProvider2
======================
Network (requires root)
======================
10067 (Wifi) (com.google.android.googlequicksearchbox.Google Search): 266.0 KBytes 34.2%
0 (Wifi) (0): 195.0 KBytes 25.1%
10051 (Wifi) (Google Services): 159.0 KBytes 20.5%
10061 (Wifi) (com.android.vending.Google Play Store): 84.0 KBytes 10.9%
10038 (Wifi) (com.google.android.configupdater.ConfigUpdater): 16.0 KBytes 2.1%
10005 (Wifi) (com.cyanogenmod.account.CyanogenMod Account): 11.0 KBytes 1.5%
10078 (Wifi) (com.asksven.betterbatterystats.BetterBatteryStats): 10.0 KBytes 1.3%
10051 (Mobile) (Google Services): 9.0 KBytes 1.3%
0 (Mobile) (0): 9.0 KBytes 1.2%
1014 (Wifi) (1014): 7.0 KBytes 0.9%
1000 (Wifi) (Android System): 6.0 KBytes 0.8%
1000 (Mobile) (Android System): 693.0 Bytes 0.1%
10018 (Wifi) (Media): 373.0 Bytes 0.0%
==========
CPU States
==========
384 MHz (): 1 h 8 m 39 s 74.3%
486 MHz (): 8 s 0.1%
594 MHz (): 37 s 0.7%
702 MHz (): 12 s 0.2%
810 MHz (): 3 s 0.1%
918 MHz (): 3 s 0.1%
1.03 GHz (): 1 m 15 s 1.4%
1.13 GHz (): 6 s 0.1%
1.24 GHz (): 14 s 0.3%
1.35 GHz (): 3 s 0.1%
1.46 GHz (): 5 s 0.1%
1.51 GHz (): 2 m 24 s 2.6%
Deep Sleep (): 18 m 28 s 19.9%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 22 s (Wl: 2 elements; KWl: 0elements; NetS: 7 elements; Alrm: 1 elements; Proc: 0 elements; Oth: 5 elements; CPU: 11 elements)
ref_current: Reference ref_current created 1 h 32 m 45 s (Wl: 23 elements; KWl: 13elements; NetS: 14 elements; Alrm: 11 elements; Proc: 12 elements; Oth: 9 elements; CPU: 13 elements)

Android OS keeps waking up the phone

Hi,
I have unrooted stock I9500.
I see that something keeps waking my phone (Android OS getting 40% when idle).
I used to have battery life of 2 days waiting and 3 hours of screen.
Now I worse battery life. about 2% per hour.
Will you please help me?
here's my bbs
===================
General Information
===================
BetterBatteryStats version: 1.14.0.0
Creation Date: 2013-11-28 08:43:10
Statistic Type: Unplugged to Current
Since 1 d 10 h 42 m 45 s
VERSION.RELEASE: 4.2.2
BRAND: samsung
DEVICE: ja3g
MANUFACTURER: samsung
MODEL: GT-I9500
OS.VERSION: 3.4.5-1083225
BOOTLOADER: I9500XXUBMG9
HARDWARE: universal5410
FINGERPRINT: samsung/ja3gxx/ja3g:4.2.2/JDQ39/I9500XXUBMG9:user/release-keys
ID: JDQ39
TAGS: release-keys
USER: se.infra
PRODUCT: ja3gxx
RADIO: I9500JKUBMG9
Rooted: false
============
Battery Info
============
Level lost [%]: Bat.: -52% (100% to 48%) [1.5%/h]
Voltage lost [mV]: (4288-3713) [16.6%/h]
===========
Other Usage
===========
Deep Sleep (): 1 d 7 h 9 m 49 s (112189 s) Ratio: 89.8%
Awake (): 3 h 32 m 55 s (12775 s) Ratio: 10.2%
Screen On (): 23 m 8 s (1388 s) Ratio: 1.1%
Phone On (): 8 s (8 s) Ratio: 0.0%
Good Signal (): 44 s (44 s) Ratio: 0.0%
Screen dark (): 21 m 18 s (1278 s) Ratio: 1.0%
Screen dimmed (): 55 s (55 s) Ratio: 0.0%
Screen bright (): 54 s (54 s) Ratio: 0.0%
=========
Wakelocks
=========
NlpCollectorWakeLock (Google Services): 5 m 44 s (344 s) Count:1079 0.3%
AlarmManager (מערכת Android): 5 m 26 s (326 s) Count:3150 0.3%
*sync*_gmail-ls_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.gm.Gmail): 4 m 51 s (291 s) Count:200 0.2%
AudioOut_2 (1013): 4 m 41 s (281 s) Count:68 0.2%
fullsync (com.whatsapp.WhatsApp): 3 m 12 s (192 s) Count:64 0.2%
*sync*_com.google.android.apps.plus.content.EsProvider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.apps.plus.Google+‎): 2 m 37 s (157 s) Count:59 0.1%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 2 m 1 s (121 s) Count:90 0.1%
ActivityManager-Launch (מערכת Android): 1 m 40 s (100 s) Count:415 0.1%
MAIL_SERVICE (com.android.exchange.שירותי Exchange): 1 m 40 s (100 s) Count:154 0.1%
Icing (Google Services): 1 m 15 s (75 s) Count:852 0.1%
MediaScannerService (מדיה): 1 m 2 s (62 s) Count:2 0.0%
FbClientConnManager (com.facebook.katana.Facebook): 38 s (38 s) Count:28 0.0%
RILJ (טלפון): 23 s (23 s) Count:1673 0.0%
GTALK_CONN (Google Services): 19 s (19 s) Count:1805 0.0%
NlpWakeLock (Google Services): 17 s (17 s) Count:607 0.0%
sendinactive (com.whatsapp.WhatsApp): 17 s (17 s) Count:8 0.0%
AlarmManager (Google Services): 13 s (13 s) Count:2158 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 13 s (13 s) Count:723 0.0%
AlarmManager (com.viber.voip.Viber): 12 s (12 s) Count:211 0.0%
AlarmManager (com.android.exchange.שירותי Exchange): 11 s (11 s) Count:323 0.0%
AlarmManager (טלפון): 8 s (8 s) Count:330 0.0%
Event Log Service (Google Services): 7 s (7 s) Count:1309 0.0%
SyncLoopWakeLock (מערכת Android): 7 s (7 s) Count:3899 0.0%
AlarmReceiver (com.sec.android.app.clockpackage.שעון): 7 s (7 s) Count:3 0.0%
GOOGLE_C2DM (Google Services): 6 s (6 s) Count:1239 0.0%
show keyguard (מערכת Android): 6 s (6 s) Count:51 0.0%
SNS (com.sec.android.app.sns3.SNS): 5 s (5 s) Count:2 0.0%
GSM (טלפון): 5 s (5 s) Count:332 0.0%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 5 s (5 s) Count:2 0.0%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 4 s (4 s) Count:5 0.0%
backupdb (com.whatsapp.WhatsApp): 4 s (4 s) Count:10 0.0%
AlarmManager (com.facebook.katana.Facebook): 3 s (3 s) Count:92 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 3 s (3 s) Count:17 0.0%
SyncManagerHandleSyncAlarm (מערכת Android): 3 s (3 s) Count:561 0.0%
NetworkStats (מערכת Android): 2 s (2 s) Count:124 0.0%
NetworkLocationLocator (Google Services): 2 s (2 s) Count:858 0.0%
AlarmManager (flipboard.app.Flipboard): 2 s (2 s) Count:3 0.0%
AlarmManager (com.whatsapp.WhatsApp): 2 s (2 s) Count:61 0.0%
AlarmManager (com.sec.esdk.elm.ELM Agent): 2 s (2 s) Count:5 0.0%
*sync*_com.google.android.location.reporting_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 2 s (2 s) Count:610 0.0%
mResetWakelock (מערכת Android): 2 s (2 s) Count:10 0.0%
wake:com.sofascore.android/.GCMIntentService (com.sofascore.android.SofaScore): 2 s (2 s) Count:39 0.0%
RingtonePlayer (com.android.systemui.ממשק המערכת): 2 s (2 s) Count:36 0.0%
*sync*_subscribedfeeds_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 1 s (1 s) Count:2161 0.0%
ActivityManager-Sleep (מערכת Android): 1 s (1 s) Count:3182 0.0%
SamsungPhoneWindowManager.mBroadcastWakeLock (מערכת Android): 1 s (1 s) Count:423 0.0%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.syncadapters.calendar.סינכרון 'יומן Google'): 1 s (1 s) Count:2 0.0%
GCM_LIB (Google Services): 1 s (1 s) Count:718 0.0%
AlarmManager (com.google.android.apps.plus.Google+‎): 1 s (1 s) Count:101 0.0%
TAG (טלפון): 1 s (1 s) Count:333 0.0%
AlarmManager (com.sec.chaton.ChatON): 1 s (1 s) Count:5 0.0%
GpsLocationProvider (מערכת Android): 1 s (1 s) Count:568 0.0%
AlarmManager (com.sec.android.app.shealth.S Health): 1 s (1 s) Count:2 0.0%
com.coolots.chaton.lock.noncerefresh (מערכת Android): 1 s (1 s) Count:417 0.0%
*sync*_com.sec.android.app.sbrowser.tabs_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 1 s (1 s) Count:3 0.0%
com.coolots.chaton.lock.startlogin (מערכת Android): 1 s (1 s) Count:3189 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
l2_hsic (): 1 h 59 m 43 s (7183 s) Cntc/wc/ec)5666/563/5666 5.7%
radio-interface (): 53 m 47 s (3227 s) Cntc/wc/ec)3239/45/0 2.6%
PowerManagerService (): 33 m 39 s (2019 s) Cntc/wc/ec)4582/198/0 1.6%
umts_ipc0 (): 31 m 56 s (1916 s) Cntc/wc/ec)3727/198/3727 1.5%
rpm_hsic (): 25 m 19 s (1519 s) Cntc/wc/ec)5711/279/0 1.2%
rmnet0 (): 18 m 33 s (1113 s) Cntc/wc/ec)1314/372/1314 0.9%
alarm (): 9 m 18 s (558 s) Cntc/wc/ec)3413/200/0 0.4%
sec-battery-monitor (): 6 m 5 s (365 s) Cntc/wc/ec)4419/136/0 0.3%
alarmtimer (): 4 m 19 s (259 s) Cntc/wc/ec)131/131/131 0.2%
battery (): 1 m 46 s (106 s) Cntc/wc/ec)4419/136/0 0.1%
event11-2940 (): 16 s (16 s) Cntc/wc/ec)302/24/0 0.0%
ssp_sensorhub_wake_lock (): 15 s (15 s) Cntc/wc/ec)59/7/60 0.0%
KeyEvents (): 3 s (3 s) Cntc/wc/ec)16500/1043/0 0.0%
mmc2_detect (): 2 s (2 s) Cntc/wc/ec)4531/131/0 0.0%
mmc0_detect (): 2 s (2 s) Cntc/wc/ec)4531/131/0 0.0%
sec-battery-vbus (): 1 s (1 s) Cntc/wc/ec)0/0/1 0.0%
vib_present (): (0 s) Cntc/wc/ec)42/1/0 0.0%
autosleep (): (0 s) Cntc/wc/ec)72/4/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.6 GHz (): 1 m 22 s 0.1%
1.5 GHz (): 4 s 0.0%
1.4 GHz (): 4 s 0.0%
1.3 GHz (): 10 s 0.0%
1.2 GHz (): 2 m 31 s 0.1%
1.1 GHz (): 10 s 0.0%
1 GHz (): 24 s 0.0%
900 MHz (): 19 s 0.0%
800 MHz (): 1 m 15 s 0.1%
600 MHz (): 26 m 34 s 1.3%
550 MHz (): 1 m 4 s 0.1%
500 MHz (): 1 m 3 s 0.1%
450 MHz (): 1 m 3 s 0.1%
400 MHz (): 1 m 7 s 0.1%
350 MHz (): 54 s 0.0%
300 MHz (): 1 h 1 m 14 s 2.9%
250 MHz (): 1 h 53 m 30 s 5.4%
Deep Sleep (): 1 d 7 h 9 m 49 s 89.8%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 45 s (Wl: 0 elements; KWl: 10elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 0 elements; CPU: 7 elements)
ref_unplugged: Reference ref_unplugged created 3 h 58 m 23 s (Wl: 0 elements; KWl: 20elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 4 elements; CPU: 18 elements)
ref_charged: Reference ref_charged created 3 h 58 m 23 s (Wl: 0 elements; KWl: 20elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 4 elements; CPU: 18 elements)
ref_current: Reference ref_current created 1 d 14 h 41 m 8 s (Wl: 56 elements; KWl: 19elements; NetS: null; Alrm: null; Proc: 95 elements; Oth: 8 elements; CPU: 18 elements)
Thank you.

try to calibrate your battery
is it swelled ?
my friends battery also showed such problem when it swelled in size he changed it and everything is fine now

aditya rathee said:
try to calibrate your battery
is it swelled ?
my friends battery also showed such problem when it swelled in size he changed it and everything is fine now
Click to expand...
Click to collapse
It doesn't look swelled.
it's seems that something keeps waking the phone.
just charged 2 hours ago and now it has 93%. when I enter the battery I see under "Wake" alot of stripes.

please help?

Turn off location settings
Me Gusta!

Turn off Google Now if enabled, turn off location in the Google settings app, go into WiFi settings and turn off always scan even if WiFi off along those lines it's a Google thing. All these may help. Reduce any widgets or apps that rely on location such as weather apps.
Sent from my GT-I9505 using Tapatalk

nikzDHD said:
Turn off Google Now if enabled, turn off location in the Google settings app, go into WiFi settings and turn off always scan even if WiFi off along those lines it's a Google thing. All these may help. Reduce any widgets or apps that rely on location such as weather apps.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I've noticed that I have alot of wakelocks from Exchange services.
I thinks that's hotmail sync.
I configured it to sync only manually but still even if I don't launch the mail app I can see almost 200 wakelocks from this process.
Why is this happenning?

TheBenjamin said:
I've noticed that I have alot of wakelocks from Exchange services.
I thinks that's hotmail sync.
I configured it to sync only manually but still even if I don't launch the mail app I can see almost 200 wakelocks from this process.
Why is this happenning?
Click to expand...
Click to collapse
As nikzDHD said, " Turn off Google Now if enabled, turn off location in the Google settings app, go into WiFi settings and turn off always scan even if WiFi off along those lines it's a Google thing"
It is something about Google Services.
About batery stats, thats ok, but sometimes we can see better the problem by watching the battery graphs in Android settings. Upload some screenshots for both battery graph screens.

jaswinky said:
As nikzDHD said, " Turn off Google Now if enabled, turn off location in the Google settings app, go into WiFi settings and turn off always scan even if WiFi off along those lines it's a Google thing"
It is something about Google Services.
About batery stats, thats ok, but sometimes we can see better the problem by watching the battery graphs in Android settings. Upload some screenshots for both battery graph screens.
Click to expand...
Click to collapse
So you're saying that Exchange services is something of Google?

TheBenjamin said:
So you're saying that Exchange services is something of Google?
Click to expand...
Click to collapse
No, I mean your main problem is something in Google services. Exchange is not very different to others I have seen.
I assume you have tried our suggestions about turn off all about Google locations, if it didn't work, I am really sure that if you update to last Android 4.3 it will be fixed.
Enviado desde mi GT-I9500 usando Tapatalk 2

jaswinky said:
No, I mean your main problem is something in Google services. Exchange is not very different to others I have seen.
I assume you have tried our suggestions about turn off all about Google locations, if it didn't work, I am really sure that if you update to last Android 4.3 it will be fixed.
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
I'm trying to figure out why there is a 400+ wakelocks from exchange services when I configured it on manual sync only.

TheBenjamin said:
I'm trying to figure out why there is a 400+ wakelocks from exchange services when I configured it on manual sync only.
Click to expand...
Click to collapse
There is no direct relation between syncs and wakelocks. Most of wakelocks are caused by other processes from the app.
Enviado desde mi GT-I9500 usando Tapatalk 2

TheBenjamin said:
I'm trying to figure out why there is a 400+ wakelocks from exchange services when I configured it on manual sync only.
Click to expand...
Click to collapse
Hi.
Make sure in wifi/advanced, scanning always available in unchecked.
In Settings/MyDevice/Accessibility, notification reminder is unchecked.
Open Google Settings app, go to Android Device Manager and unchecked "Remotely locate this device".
Anyways, u might want to refer here: http://forum.xda-developers.com/showthread.php?t=2532210
There may be 3rd party apps u had installed that's making the Android OS to wake.
Cheers.

N900 BT_bt_wake wakelock

Hello. I have this terrible wakelock. I searched the web and didn't find anything. I'm really tired of these wakelocks
Version MK2
It won't let my phone to go to deep sleep. my wifi was off all the time. if I turn it on other wakelocks happen too
Actually, Most of the times I have lots of kernel wakelocks. and Android OS battery drain
Another wakelocks are sec-battery-monitor and wlan_rx_wake when I turn on wifi.
Hope Samsung fix all of these terrible wakelocks...
But anyway... Does anyone know what is causing this wakelock?

No one knows? It's the only thing that won't let my phone to go to deep sleep.
I think it's related to bluetooth maybe. But it's off all the time.
Anyone can help me?
Sent from my SM-N900 using Tapatalk

Same here.
===================
General Information
===================
BetterBatteryStats version: 1.15.0.0
Creation Date: 2013-12-23 07:39:12
Statistic Type: Unplugged to Current
Since 7 h 56 m 25 s
VERSION.RELEASE: 4.3
BRAND: samsung
DEVICE: ha3g
MANUFACTURER: samsung
MODEL: SM-N900
OS.VERSION: 3.4.39-2217357
BOOTLOADER: N900XXUCMK2
HARDWARE: universal5420
FINGERPRINT: samsung/ha3gxx/ha3g:4.3/JSS15J/N900XXUCMK2:user/release-keys
ID: JSS15J
TAGS: release-keys
USER: dpi
PRODUCT: ha3gxx
RADIO: N900XXUCMK1
Rooted: false
============
Battery Info
============
Level lost [%]: Bat.: -20% (100% to 80%) [2.5%/h]
Voltage lost [mV]: (4317-4017) [37.8%/h]
===========
Other Usage
===========
Awake (): 7 h 56 m 25 s (28585 s) Ratio: 100.0%
Screen On (): 47 m 5 s (2825 s) Ratio: 9.9%
Wifi On (): 7 h 56 m 25 s (28585 s) Ratio: 100.0%
Wifi Running (): 2 h 50 m 14 s (10214 s) Ratio: 35.7%
Screen dark (): 40 m 55 s (2455 s) Ratio: 8.6%
Screen medium (): 6 m 9 s (369 s) Ratio: 0.6%
=========
Wakelocks
=========
AudioOut_F6 (1013): 4 m 54 s (294 s) Count:4 1.1%
android.media.MediaPlayer (com.sec.android.app.music.Music): 4 m 50 s (290 s) Count:6 1.1%
AudioOut_2 (1013): 2 m 21 s (141 s) Count:12 0.5%
ConnectivityService (Android System): 2 m 7 s (127 s) Count:1125 0.5%
FbClientConnManager (com.facebook.katana.Facebook): 1 m 56 s (116 s) Count:81 0.5%
TimaService (Android System): 1 m 26 s (86 s) Count:98 0.3%
AlarmManager (com.devexpert.weather.Android Weather): 1 m 10 s (70 s) Count:476 0.3%
NlpWakeLock (Google Services): 1 m 10 s (70 s) Count:65 0.3%
ActivityManager-Launch (Android System): 51 s (51 s) Count:403 0.2%
AlarmManager (Android System): 42 s (42 s) Count:1120 0.2%
*sync*_com.android.contacts_Account {name=a0edf64bcb96cc80c74f8b215dc4ded0, type=com.facebook.auth.login} (com.facebook.katana.Facebook): 31 s (31 s) Count:3 0.1%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 26 s (26 s) Count:6 0.1%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 16 s (16 s) Count:12 0.1%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 16 s (16 s) Count:6 0.1%
RILJ (Phone): 15 s (15 s) Count:457 0.1%
WifiStateMachine (Android System): 14 s (14 s) Count:523 0.1%
*sync*_gmail-ls_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.gm.Gmail): 10 s (10 s) Count:13 0.0%
*sync*_com.android.calendar_Account {name=0c074206062eebb0a95994421870ecb0, type=com.sec.android.app.sns3.facebook} (com.sec.android.app.sns3.SNS): 10 s (10 s) Count:3 0.0%
wakeLock (Android System): 9 s (9 s) Count:121 0.0%
*sync*_com.samsung.android.SmartClip_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (com.samsung.android.app.pinboard.Scrapbook): 7 s (7 s) Count:3 0.0%
*sync*_com.google.android.gms.people_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 7 s (7 s) Count:415 0.0%
*sync*_com.sec.android.app.sbrowser_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.osp.app.signin} (Samsung Syncadapters): 6 s (6 s) Count:15 0.0%
GCM_CONN_ALARM (Google Services): 5 s (5 s) Count:171 0.0%
Icing (Google Services): 5 s (5 s) Count:514 0.0%
*sync*_com.android.calendar_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.syncadapters.calendar.Google Calendar Sync): 5 s (5 s) Count:18 0.0%
NlpCollectorWakeLock (Google Services): 5 s (5 s) Count:556 0.0%
NetworkLocationLocator (Google Services): 5 s (5 s) Count:517 0.0%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.linkedin.android} (com.linkedin.android.LinkedIn): 5 s (5 s) Count:3 0.0%
*sync*_com.android.contacts_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 4 s (4 s) Count:177 0.0%
AlarmManager (com.facebook.katana.Facebook): 4 s (4 s) Count:361 0.0%
NetworkStats (Android System): 4 s (4 s) Count:225 0.0%
SNS (com.sec.android.app.sns3.SNS): 4 s (4 s) Count:12 0.0%
*sync*_com.google.android.music.MusicContent_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (com.google.android.music.Google Play Music): 4 s (4 s) Count:20 0.0%
AlarmManager (Google Services): 3 s (3 s) Count:412 0.0%
*sync*_subscribedfeeds_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 3 s (3 s) Count:636 0.0%
*sync*_com.anydo.provider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.anydo.account} (Any.DO): 2 s (2 s) Count:19 0.0%
SyncLoopWakeLock (Android System): 2 s (2 s) Count:1389 0.0%
E (net.dinglisch.android.taskerm.Tasker): 2 s (2 s) Count:111 0.0%
fullsync (com.whatsapp.WhatsApp): 2 s (2 s) Count:39 0.0%
*sync*_com.evernote.evernoteprovider_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.evernote} (com.evernote.Evernote): 2 s (2 s) Count:5 0.0%
M (net.dinglisch.android.taskerm.Tasker): 2 s (2 s) Count:99 0.0%
com.google.android.music.leanback.AutoCacheSchedulingService (com.google.android.music.Google Play Music): 2 s (2 s) Count:17 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 2 s (2 s) Count:4 0.0%
SyncService (com.evernote.Evernote): 2 s (2 s) Count:2 0.0%
DHCP (Android System): 1 s (1 s) Count:453 0.0%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Calendar storage): 1 s (1 s) Count:34 0.0%
Event Log Service (Google Services): 1 s (1 s) Count:583 0.0%
*sync*_com.google.android.gms.games.background_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 1 s (1 s) Count:3 0.0%
*sync*_com.google.android.location.reporting_Account {name=c6e4f0109f89c57f75b7928770c57fb0, type=com.google} (Google Services): 1 s (1 s) Count:93 0.0%
show keyguard (Android System): 1 s (1 s) Count:126 0.0%
ConnectMQTT (com.nuance.swype.dtc.Swype + Dragon): 1 s (1 s) Count:33 0.0%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 1 s (1 s) Count:4 0.0%
SCREEN_FROZEN (Android System): 1 s (1 s) Count:455 0.0%
RILS (com.sec.phone.com.sec.phone): 1 s (1 s) Count:11 0.0%
AudioOut_F7 (1013): 1 s (1 s) Count:14 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
BT_bt_wake (): 7 h 9 m (25740 s) Cntc/wc/ec)6/0/6 -387.9%
PowerManagerService.WakeLocks (): 17 m 34 s (1054 s) Cntc/wc/ec)2411/0/0 3.7%
l2_hsic (): 9 m 17 s (557 s) Cntc/wc/ec)1163/0/1163 2.0%
bluetooth_timer (): 7 m 21 s (441 s) Cntc/wc/ec)12/0/0 1.5%
umts_ipc0 (): 5 m 57 s (357 s) Cntc/wc/ec)1070/0/1070 1.3%
ril-fd (): 5 m 9 s (309 s) Cntc/wc/ec)23/0/0 1.1%
radio-interface (): 3 m 58 s (238 s) Cntc/wc/ec)342/0/0 0.8%
rmnet0 (): 2 m 43 s (163 s) Cntc/wc/ec)123/0/123 0.6%
wlan_rx_wake (): 2 m 37 s (157 s) Cntc/wc/ec)813/0/814 0.6%
wlan_ctrl_wake (): 1 m 41 s (101 s) Cntc/wc/ec)156/0/157 0.4%
wlan_wd_wake (): 56 s (56 s) Cntc/wc/ec)4838/0/0 0.2%
rpm_hsic (): 55 s (55 s) Cntc/wc/ec)1176/0/0 0.2%
alarm (): 22 s (22 s) Cntc/wc/ec)1790/0/0 0.1%
wlan_wake (): 20 s (20 s) Cntc/wc/ec)34092/0/0 0.1%
sec-battery-monitor (): 20 s (20 s) Cntc/wc/ec)952/0/0 0.1%
LightsService (): 16 s (16 s) Cntc/wc/ec)38/0/0 0.1%
bcm2079x_wake_lock_timeout (): 10 s (10 s) Cntc/wc/ec)12/0/12 0.0%
AudioOutLock (): 7 s (7 s) Cntc/wc/ec)5/0/0 0.0%
battery (): 6 s (6 s) Cntc/wc/ec)952/0/0 0.0%
PowerManagerService.Broadcasts (): 2 s (2 s) Cntc/wc/ec)18/0/0 0.0%
PowerManagerService.Display (): (0 s) Cntc/wc/ec)9/0/0 0.0%
bcm2079x_wake_lock (): (0 s) Cntc/wc/ec)13/0/0 0.0%
KeyEvents (): (0 s) Cntc/wc/ec)65473/0/0 0.0%
ApmCommand (): (0 s) Cntc/wc/ec)64/0/0 0.0%
event19-2744 (): (0 s) Cntc/wc/ec)118/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
1.9 GHz (): 3 m 50 s 0.8%
1.8 GHz (): 1 m 21 s 0.3%
1.7 GHz (): 43 s 0.2%
1.6 GHz (): 1 m 26 s 0.3%
1.5 GHz (): 58 s 0.2%
1.4 GHz (): 21 s 0.1%
1.3 GHz (): 33 s 0.1%
1.2 GHz (): 54 s 0.2%
1.1 GHz (): 2 m 3 s 0.4%
1 GHz (): 1 m 19 s 0.3%
900 MHz (): 1 m 30 s 0.3%
800 MHz (): 5 m 46 s 1.2%
650 MHz (): 5 m 8 s 1.1%
600 MHz (): 15 m 45 s 3.3%
550 MHz (): 25 s 0.1%
500 MHz (): 51 s 0.2%
450 MHz (): 43 s 0.2%
400 MHz (): 2 m 43 s 0.6%
350 MHz (): 5 m 31 s 1.2%
300 MHz (): 2 m 36 s 0.5%
250 MHz (): 7 h 1 m 49 s 88.5%
Deep Sleep (): 0.0%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 40 s (Wl: 7 elements; KWl: 9elements; NetS: null; Alrm: null; Proc: 9 elements; Oth: 3 elements; CPU: 1 elements)
ref_unplugged: Reference ref_unplugged created 9 h 47 m 1 s (Wl: 0 elements; KWl: 39elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 22 elements)
ref_charged: Reference ref_charged created 9 h 47 m 1 s (Wl: 0 elements; KWl: 39elements; NetS: null; Alrm: null; Proc: 0 elements; Oth: 6 elements; CPU: 22 elements)
ref_current: Reference ref_current created 17 h 43 m 27 s (Wl: 55 elements; KWl: 39elements; NetS: null; Alrm: null; Proc: 89 elements; Oth: 7 elements; CPU: 22 elements)

Same here
My Note 3 is just a few days old. It was fine till now, with no funny wakelocks. But all of a sudden, it seeing the same BT_bt_wake activity today. It's draining like 3% every hour.

contactsunny said:
My Note 3 is just a few days old. It was fine till now, with no funny wakelocks. But all of a sudden, it seeing the same BT_bt_wake activity today. It's draining like 3% every hour.
Click to expand...
Click to collapse
My guess is that it is Bluetooth-related, and it should go away if you turn-off Bluetooth (for instance using the quick toggles), so this should be your first test.
If that is correct but you still need to use your Bluetooth-related devices then the next step is to see which device from your paired devices creates problems - my guess is that Bluetooth v4 devices would be fine, but maybe older Bluetooth devices are not handled so well in hardware and as a result keep a wakelock in software.
The problem might also be from a device that is not even paired with your Note 3 but is active around you and keeps sending (discovery?) packets around - in that case I really am curious what could be done (other than trying to turn-off that device).

http://forum.xda-developers.com/showthread.php?t=2473748
Sent from my SM-N9005 using XDA Premium 4 mobile app

xclub_101 said:
My guess is that it is Bluetooth-related, and it should go away if you turn-off Bluetooth (for instance using the quick toggles), so this should be your first test.
If that is correct but you still need to use your Bluetooth-related devices then the next step is to see which device from your paired devices creates problems - my guess is that Bluetooth v4 devices would be fine, but maybe older Bluetooth devices are not handled so well in hardware and as a result keep a wakelock in software.
The problem might also be from a device that is not even paired with your Note 3 but is active around you and keeps sending (discovery?) packets around - in that case I really am curious what could be done (other than trying to turn-off that device).
Click to expand...
Click to collapse
I just did a short test:
activated BT for 10 seconds, didn't connect anything to it.
deactivated BT.
left the device for an hour.
bt_bt_wakelock was stuck

sekely said:
I just did a short test:
activated BT for 10 seconds, didn't connect anything to it.
deactivated BT.
left the device for an hour.
bt_bt_wakelock was stuck
Click to expand...
Click to collapse
That is very interesting (and a little worrying, since it means that turning it off does not solve the problem, at least not immediately) - how many devices do you have in your list of paired devices? And how many other devices do you see around you?
I would assume that restarting the phone would fix things, but that is a really messy workaround.

Same stuff w. my SM-N900
P30SiNa said:
No one knows? It's the only thing that won't let my phone to go to deep sleep.
I think it's related to bluetooth maybe. But it's off all the time.
Anyone can help me?
Sent from my SM-N900 using Tapatalk
Click to expand...
Click to collapse
Have same **** w. my SM-N900 - afther first on/off bluetooth phone does not go to "deep sleep" if I switch WiFi on. Tried wipe out / safe mode etc - does not help. Looks like either SW bug or something wrong w. hardware (unlikely). The only thing helps for a while - to swithch bluethooth on and off once again, then phone goes to bed till next WiFi on/off. Then you need to on-off your bluetooth once again - and os in the loop.
And yes - bt_bt_wake is whown by BBS as main system wakelock.
any ideas how to shoot this bt_bt_wake issue?... Probably buy IPas mini?.. but it does not have awesome stylus...

make Factory reset and try
Sent from my SM-N900 using xda app-developers app

Already tries, as written above. Did not help. Other ideas?..

xclub_101 said:
That is very interesting (and a little worrying, since it means that turning it off does not solve the problem, at least not immediately) - how many devices do you have in your list of paired devices? And how many other devices do you see around you?
I would assume that restarting the phone would fix things, but that is a really messy workaround.
Click to expand...
Click to collapse
I have 3 devices paired (headphone, earphone, keyboard).
regarding to other devices @ the near surrounding - not related. the issue was reproduced in different environments.
restarting the phone solving the issue but I don't think that this is an appropriate solution.
I found an old android code from 2011 that takes the bt_bt_wake. I couldn't find any release.
since I haven't seen much complain about bt_bt_wake my best guess is - rare system flow which cause an internal exception, which doesn't release the lock. but it's just a shot in the dark, I hate C code.

BT is the obvious culprit
xclub_101 said:
My guess is that it is Bluetooth-related, and it should go away if you turn-off Bluetooth (for instance using the quick toggles), so this should be your first test.
If that is correct but you still need to use your Bluetooth-related devices then the next step is to see which device from your paired devices creates problems - my guess is that Bluetooth v4 devices would be fine, but maybe older Bluetooth devices are not handled so well in hardware and as a result keep a wakelock in software.
The problem might also be from a device that is not even paired with your Note 3 but is active around you and keeps sending (discovery?) packets around - in that case I really am curious what could be done (other than trying to turn-off that device).
Click to expand...
Click to collapse
Sorry, I hadn't seen your reply. And a simple restart fixed the issue. This only occurs when I switch on the BT. And then I'll have to restart the device to stop this from occurring again. Its a bit frustrating. If this is fixed, i easily get 24 hours of more with at least 3 hours of screen on, 1 hour of GPS, 1 hour of gaming, and 1 hour of music. That's a good backup for me.

bt_bt_wake wakelock issue has gone after Kitkat upgrade. Confirmed also by other fellows. But still there are some other wakelocks like sec-battery-stat which drain battery fadt if WiFi is on.

Note 3 wakelock
Follow this:
0)I use Cpu Spy app to determine wakelock & Deep Sleep Problems
1) go to Wifi settings & turn on Wifi
2) go to Advanced
3)Set "Keep Wi-Fi on during sleep" to "Never"
4)Wait some seconds (I used to turn off screen, wait for some seconds)
5) turn off wifi
if you want to use wifi, turn on wifi and set "keep Wi-Fi..." to "Always" or not.
Notice that befor turning of Wifi, set it to "Never"
notice that when your phone is connected to charger T before disconnecting charger, unlock phone and wait for a few seconds while screen is on, then disconnect charger,

MTU79 said:
bt_bt_wake wakelock issue has gone after Kitkat upgrade. Confirmed also by other fellows. But still there are some other wakelocks like sec-battery-stat which drain battery fadt if WiFi is on.
Click to expand...
Click to collapse
same here, I'll keep following and update if anything changes.
now I have the l2_hsic issue. it's like hydra - you kill one wakelock issue, 2 pops instead

Today i met this sec-battery-monitor wakelock which is huge problem for going into a deepsleep and drains the battery a lot. Did the postera under these thread resolve the issue?
PS I tried to use a chinese powerbank yesterday and also charged the phone via chinesee car plug today...

solution
I had wlan_wake and bt_bt_wake issue on v4.3. Clear the cache for the system (or all) of the applications for me is the solution!
I used SD Maid to clean.

[Q] n9005 battery drain

Hey,
My N9005 has recently started to experience battery drain. Couple weeks earlier It was around 0.3..0.5% per hour through the night. Now it is 0.9 and awake time is 2 hours out of 9.
I am rooted, wifi and 4g is on. Location is on (via Network). Google Now is off.
This is the extraction from BBS:
===================
General Information
===================
BetterBatteryStats version: 1.15.0.0
Creation Date: 2014-02-18 08:24:07
Statistic Type: Custom to Current
Since 8 h 42 m 54 s
VERSION.RELEASE: 4.4.2
BRAND: samsung
DEVICE: hlte
MANUFACTURER: samsung
MODEL: SM-N9005
OS.VERSION: 3.4.0-340325
BOOTLOADER: N9005XXUENA6
HARDWARE: qcom
FINGERPRINT: samsung/hltexx/hlte:4.4.2/KOT49H/N9005XXUENA6:user/release-keys
ID: KOT49H
TAGS: release-keys
USER: dpi
PRODUCT: hltexx
RADIO: N9005XXUENA2
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -8% (91% to 83%) [0.9%/h]
Voltage lost [mV]: (4146-4076) [8.0%/h]
===========
Other Usage
===========
Screen On (): 3 m 13 s (193 s) Ratio: 0.6%
Wifi On (): 8 h 42 m 54 s (31374 s) Ratio: 100.0%
Wifi Running (): 8 h 42 m 54 s (31374 s) Ratio: 100.0%
Deep Sleep (): 6 h 37 m 41 s (23861 s) Ratio: 76.1%
Awake (): 2 h 5 m 12 s (7512 s) Ratio: 23.9%
=========
Wakelocks
=========
NlpCollectorWakeLock (Google Services): 6 m 58 s (418 s) Count:35 34.7%
NlpWakeLock (com.google.android.googlequicksearchbox.Google Search): 6 m 1 s (361 s) Count:114 29.9%
AlarmManager (0): 2 m 32 s (152 s) Count:590 12.6%
TimaService (0): 1 m 15 s (75 s) Count:25 6.2%
LocationManagerService (0): 1 m 11 s (71 s) Count:114 5.9%
AlarmReceiver (com.sec.android.app.clockpackage.Clock): 20 s (20 s) Count:37 0.6%
StartingAlertService (Calendar): 15 s (15 s) Count:3 1.2%
AlarmManager (Google Services): 8 s (8 s) Count:57 0.7%
NlpWakeLock (Google Services): 8 s (8 s) Count:164 0.7%
VibratorService (com.sec.android.app.clockpackage.Clock): 8 s (8 s) Count:5 0.2%
BBS_WAKELOCK_WHILE_SAVING_REF (com.asksven.betterbatterystats_xdaedition.BetterBatteryStats): 7 s (7 s) Count:2 0.6%
GCM_CONN (Google Services): 6 s (6 s) Count:39 0.5%
AlarmManager (com.facebook.katana.Facebook): 6 s (6 s) Count:49 0.5%
*sync*/gmail-ls/com.google/eM_ADDR (com.google.android.gm.Gmail): 6 s (6 s) Count:1 0.5%
hfm (com.google.android.googlequicksearchbox.Google Search): 6 s (6 s) Count:101 0.5%
AlarmManager (com.google.android.googlequicksearchbox.Google Search): 5 s (5 s) Count:107 0.4%
Event Log Service (Google Services): 5 s (5 s) Count:17 0.4%
ActivityManager-Launch (0): 4 s (4 s) Count:18 0.3%
AudioMix (0): 4 s (4 s) Count:2 0.3%
NlpLocationReceiverService (com.google.android.googlequicksearchbox.Google Search): 4 s (4 s) Count:125 0.3%
NetworkStats (0): 2 s (2 s) Count:17 0.2%
NlpWakeLock (0): 2 s (2 s) Count:1 0.2%
LocationManagerService (Google Services): 2 s (2 s) Count:221 0.2%
AlarmManager (com.sec.spp.push.Samsung Push Service): 2 s (2 s) Count:15 0.1%
AlarmManager (com.whatsapp.WhatsApp): 2 s (2 s) Count:18 0.1%
Icing (Google Services): 1 s (1 s) Count:17 0.1%
show keyguard (UID): 1 s (1 s) Count:2 0.1%
AlarmManager (com.android.chrome.Chrome): 1 s (1 s) Count:15 0.1%
SyncManagerHandleSyncAlarm (0): 1 s (1 s) Count:4 0.1%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 1 s (1 s) Count:1 0.1%
GpsLocationProvider (0): 1 s (1 s) Count:8 0.1%
AlarmManager (Calendar): 1 s (1 s) Count:4 0.1%
DHCP (0): 1 s (1 s) Count:2 0.0%
StartingAlertService (com.android.calendar.S Planner): 1 s (1 s) Count:5 0.0%
UlrDispatchingService (Google Services): 1 s (1 s) Count:6 0.0%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
PowerManagerService.WakeLocks (): 17 m 47 s (1067 s) Cntc/wc/ec)940/164/0 3.4%
sec-battery-monitor (): 7 m 48 s (468 s) Cntc/wc/ec)4988/84/0 1.5%
alarm (): 7 m 35 s (455 s) Cntc/wc/ec)1350/532/0 1.5%
resume_wakelock (): 7 m 22 s (442 s) Cntc/wc/ec)4646/0/4646 1.4%
qpnp-vadc-ebd30a00 (): 4 m 36 s (276 s) Cntc/wc/ec)35214/2369/0 0.9%
mmc0:0001:2 (): 2 m 33 s (153 s) Cntc/wc/ec)21729/7235/0 0.5%
alarm_rtc (): 1 m 37 s (97 s) Cntc/wc/ec)195/125/0 0.3%
radio-interface (): 16 s (16 s) Cntc/wc/ec)20/4/0 0.1%
ssp_sensorhub_wake_lock (): 11 s (11 s) Cntc/wc/ec)12/2/11 0.0%
ipc00000021_Loc_hal_worker (): 8 s (8 s) Cntc/wc/ec)1432/90/0 0.0%
KeyEvents (): 6 s (6 s) Cntc/wc/ec)7849/265/0 0.0%
smdcntl0 (): 6 s (6 s) Cntc/wc/ec)197/8/0 0.0%
power-supply (): 5 s (5 s) Cntc/wc/ec)4985/83/0 -0.1%
ipc0000000d_rmt_storage (): 2 s (2 s) Cntc/wc/ec)5/0/0 0.0%
PowerManagerService.Broadcasts (): 1 s (1 s) Cntc/wc/ec)10/0/0 0.0%
event18-853 (): 1 s (1 s) Cntc/wc/ec)14/0/0 0.0%
rmt_storage_-1210977736 (): (0 s) Cntc/wc/ec)3/0/0 0.0%
ssp_wake_lock (): (0 s) Cntc/wc/ec)52/2/0 0.0%
rmt_storage_-1210978584 (): (0 s) Cntc/wc/ec)2/0/0 0.0%
event5-853 (): (0 s) Cntc/wc/ec)11/0/0 0.0%
ipc_rtr_smd_ipcrtr (): (0 s) Cntc/wc/ec)1531/105/0 0.0%
MediaPlayerService_Decode (): (0 s) Cntc/wc/ec)4/0/0 0.0%
qpnp-iadc-ebd30c00 (): (0 s) Cntc/wc/ec)25/7/0 0.0%
PowerManagerService.Display (): (0 s) Cntc/wc/ec)5/0/0 0.0%
qmuxd_port_wl_0 (): (0 s) Cntc/wc/ec)248/8/0 0.0%
ipc0000002a_Loc_hal_worker (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc00000022_Loc_hal_worker (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc00000003_rfs_access (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc00000017_time_daemon (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc00000010_time_daemon (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc0000001d_gsiff_daemon (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc0000000e_rmt_storage (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc00000007_thermal-engine (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc0000001b_thermal-engine (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc00000019_thermal-engine (): (0 s) Cntc/wc/ec)5/5/0 0.0%
ipc0000000c_thermal-engine (): (0 s) Cntc/wc/ec)5/5/0 0.0%
======================
Alarms (requires root)
======================
com.google.android.gms (): Wakeups: 162
Alarms: 109, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_LOCATOR
Alarms: 0, Intent: com.google.android.intent.action.GCM_RECONNECT
Alarms: 35, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 10, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVITY_DETECTION
Alarms: 2, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.playlog.uploader.UploaderAlarmReceiver}
Alarms: 4, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVE_COLLECTOR
Alarms: 1, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_PASSIVE_COLLECTOR
Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.common.download.DownloadAlarmReceiver}
Alarms: 0, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_BURST_COLLECTION_TRIGGER
Alarms: 0, Intent: com.google.android.gms.nlp.ALARM_WAKEUP_CACHE_UPDATER
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE cmp={com.google.android.gms/com.google.android.gms.icing.service.IndexWorkerService}
android (): Wakeups: 67
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 17, Intent: android.appwidget.action.APPWIDGET_UPDATE cmp={com.sec.android.widgetapp.easyfavoritescontactswidget/com.sec.android.widgetapp.easyfavoritescontactswidget.SeniorFavoriteWidgetProviderLarge}
Alarms: 4, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 44, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED
Alarms: 0, Intent: edm.intent.action.elm.cleanrecords
Alarms: 0, Intent: com.android.server.LightsService.action.UPDATE_SVC_LED
Alarms: 0, Intent: com.android.server.action.UPDATE_TWILIGHT_STATE
Alarms: 1, Intent: com.android.server.IdleMaintenanceService.action.UPDATE_IDLE_MAINTENANCE_STATE
Alarms: 1, Intent: android.net.wifi.DHCP_RENEW
com.facebook.katana (): Wakeups: 49
Alarms: 35, Intent: com.facebook.push.mqtt.KeepaliveManager.ACTION_INEXACT_ALARM.com.facebook.katana
Alarms: 3, Intent: com.facebook.common.executors.WakingExecutorService.ACTION_ALARM.com.facebook.katana
Alarms: 11, Intent: com.facebook.analytics.service.AnalyticsEventUploader.ACTION_ALARM
Alarms: 0, Intent: {com.facebook.katana/com.facebook.ui.media.cache.MediaCacheCleanupService}
Alarms: 0, Intent: {com.facebook.katana/com.facebook.common.tempfile.TempFileCleanupService}
com.google.android.gsf (): Wakeups: 17
Alarms: 17, Intent: {com.google.android.gsf/com.google.android.gsf.checkin.EventLogService$Receiver}
com.sec.spp.push (): Wakeups: 9
Alarms: 0, Intent: com.sec.spp.push.receiver.PROVISIONING_ACTION
Alarms: 9, Intent: {com.sec.spp.push/com.sec.spp.push.heartbeat.HeartBeat}
Alarms: 0, Intent: com.sec.spp.push.ALARM_TIMER_ACTION
Alarms: 0, Intent: com.sec.spp.push.DAY_TIMER
com.google.android.apps.maps (): Wakeups: 9
Alarms: 9, Intent: {com.google.android.apps.maps/com.google.android.apps.gmm.prefetch.PrefetcherService}
com.google.android.googlequicksearchbox (): Wakeups: 8
Alarms: 8, Intent: {com.google.android.googlequicksearchbox/com.google.android.velvet.VelvetBackgroundTasksImpl$Service}
Alarms: 0, Intent: send_events cmp={com.google.android.googlequicksearchbox/com.google.android.voicesearch.logger.EventLoggerService}
com.whatsapp (): Wakeups: 2
Alarms: 0, Intent: ALARM_ACTION
Alarms: 1, Intent: ALARM_ROTATE_LOGS
Alarms: 0, Intent: ALARM_AVAILABLE_TIMEOUT
Alarms: 1, Intent: ALARM_MESSAGES_DB_BACKUP
Alarms: 0, Intent: com.whatsapp.MessageService.RECONNECT cmp={com.whatsapp/com.whatsapp.messaging.MessageService}
Alarms: 0, Intent: ALARM_CLIENT_PING_TIMEOUT
com.sec.android.app.clockpackage (): Wakeups: 2
Alarms: 1, Intent: com.samsung.sec.android.clockpackage.alarm.ALARM_ALERT
Alarms: 1, Intent: com.samsung.sec.android.clockpackage.alarm.NOTIFY_ALARM_LOCATION
com.sec.chaton (): Wakeups: 2
Alarms: 2, Intent: {com.sec.chaton/com.sec.common.util.log.collector.LogCollectorSender}
com.agilesoftresource (): Wakeups: 1
Alarms: 0, Intent: ALM cmp={com.agilesoftresource/com.avg.toolkit.recurringTasks.RecurringTaskAlarmReceiver}
Alarms: 0, Intent: TSVCDT cmp={com.agilesoftresource/com.avg.toolkit.recurringTasks.RecurringTaskAlarmReceiver}
Alarms: 1, Intent: ADM cmp={com.agilesoftresource/com.avg.toolkit.recurringTasks.RecurringTaskAlarmReceiver}
Alarms: 0, Intent: CSR cmp={com.agilesoftresource/com.avg.toolkit.recurringTasks.RecurringTaskAlarmReceiver}
com.android.calendar (): Wakeups: 1
Alarms: 1, Intent: com.sec.android.calendar.update_data cmp={com.android.calendar/com.android.calendar.magazine.CalendarUpdateRelatedDataReceiver}
com.sec.esdk.elm (): Wakeups: 1
Alarms: 1, Intent: com.sec.esdk.elm.alarm.SAVE_APICALLLOG
======================
Network (requires root)
======================
1000 (Wifi) (Android System): 639.0 KBytes 23.6%
10030 (Wifi) (com.android.chrome.Chrome): 529.0 KBytes 19.5%
10191 (Wifi) (com.google.android.googlequicksearchbox.Google Search): 526.0 KBytes 19.4%
0 (Wifi) (0): 506.0 KBytes 18.7%
10070 (Wifi) (Google Services): 148.0 KBytes 5.5%
10008 (Wifi) (sstream.app.My Magazine): 118.0 KBytes 4.4%
10276 (Wifi) (com.facebook.katana.Facebook): 67.0 KBytes 2.5%
0 (lo) (0): 48.0 KBytes 1.8%
10270 (lo) (com.agilesoftresource.AndroZip File Manager): 33.0 KBytes 1.3%
10069 (Wifi) (com.google.android.gm.Gmail): 22.0 KBytes 0.8%
10064 (Wifi) (com.google.android.apps.maps.Maps): 20.0 KBytes 0.7%
10264 (Wifi) (com.sec.android.daemonapp.Unified Daemon(EUR)): 14.0 KBytes 0.5%
10277 (Wifi) (com.macropinch.swan.Weather): 11.0 KBytes 0.4%
10054 (Wifi) (com.evernote.Evernote): 7.0 KBytes 0.3%
10270 (Wifi) (com.agilesoftresource.AndroZip File Manager): 5.0 KBytes 0.2%
10134 (Wifi) (com.sec.spp.push.Samsung Push Service): 5.0 KBytes 0.2%
10239 (Wifi) (ru.yandex.metro.Yandex.Metro): 1.0 KBytes 0.1%
10113 (Wifi) (com.android.vending.Google Play Store): 992.0 Bytes 0.0%
1014 (Wifi) (1014): 668.0 Bytes 0.0%
10266 (lo) (ru.sports.sochi2014.РћР˜-2014): 500.0 Bytes 0.0%
10030 (lo) (com.android.chrome.Chrome): 200.0 Bytes 0.0%
==========
CPU States
==========
300 MHz (): 1 h 5 m 50 s 12.6%
422.4 MHz (): 48 m 47 s 9.3%
652.8 MHz (): 6 m 19 s 1.2%
729.6 MHz (): 16 s 0.1%
883.2 MHz (): 1 m 21 s 0.3%
960 MHz (): 6 s 0.0%
1.04 GHz (): 9 s 0.0%
1.19 GHz (): 45 s 0.1%
1.27 GHz (): 9 s 0.0%
1.5 GHz (): 30 s 0.1%
1.57 GHz (): 1 s 0.0%
1.73 GHz (): 14 s 0.0%
1.96 GHz (): 21 s 0.1%
2.27 GHz (): 18 s 0.1%
Deep Sleep (): 6 h 37 m 41 s 76.1%
==================
Reference overview
==================
ref_unplugged: Reference ref_unplugged created 4 h 19 m 27 s (Wl: 1 elements; KWl: 47elements; NetS: 48 elements; Alrm: 16 elements; Proc: 56 elements; Oth: 5 elements; CPU: 15 elements)
ref_charged: Reference ref_charged created 4 h 19 m 28 s (Wl: 2 elements; KWl: 47elements; NetS: 48 elements; Alrm: 16 elements; Proc: 56 elements; Oth: 5 elements; CPU: 15 elements)
ref_custom: Reference ref_custom created 10 h 10 m 5 s (Wl: 56 elements; KWl: 50elements; NetS: 62 elements; Alrm: 17 elements; Proc: 278 elements; Oth: 6 elements; CPU: 15 elements)
ref_current: Reference ref_current created 18 h 52 m 59 s (Wl: 64 elements; KWl: 50elements; NetS: 62 elements; Alrm: 20 elements; Proc: 281 elements; Oth: 6 elements; CPU: 15 elements)
Click to expand...
Click to collapse

Turn off Location / GPS and freeze Google Now.
Also you will get Loads of Battery saving tips from my thread here -
http://forum.xda-developers.com/show....php?t=2579075

Thanks for reply.
Google Now is off in settings. I don't want to turn GPS off (it wasn't off previously and there were neither batter drain nor huge awake time).
Anyway, I'll try it this night as an experiment.

Use only wifi for location, turn off GPS, and disable google location, that did the trick for me. Here is an image to show the terrible drain I had.

iterimpius said:
Use only wifi for location, turn off GPS, and disable google location, that did the trick for me. Here is an image to show the terrible drain I had.
Click to expand...
Click to collapse
Although you are probably right, this is not how it is supposed to be. I want to have GPS constatntly turned on and do not have battery drain as it previously was (even after upgrade to 4.4.2).
Thanks anyway - I'll let you know about the results next morning.

zipper3 said:
Although you are probably right, this is not how it is supposed to be. I want to have GPS constatntly turned on and do not have battery drain as it previously was (even after upgrade to 4.4.2).
Thanks anyway - I'll let you know about the results next morning.
Click to expand...
Click to collapse
Well, I guess you can still leave GPS on, it will drain little power. The problem with me was that google services were keeping the CPU awake, retrying to get location continuously, which ended up draining the batter, the device never goes to sleep.

So, I switched GPS OFF this night and the phone was awake 1 hour out of 8 hours and battery dropped by from 53 to 49% - not that bad, I guess. But still awake time seems high.

I think mmc0:0001:2 of Kernel wakelock is the culprit. My galaxy S4 LTE-A suffers from battety drain. I found the kernel wakelock only occurs when wifi is on. But when my S4 is connected to specific routers, wakeup count of the wakelock soars up. Yours is about a third of total count, which is very high. I suggest changing your router.. I tried some tricks to make it right, but none did work. Changing router did the trick. Total count of the kernel wakelock was still high, but wakeup count of it considerably dropped, and battery drain was gone.
Sent from my SHV-E330S using Tapatalk

Battery Drain
kulguy said:
I think mmc0:0001:2 of Kernel wakelock is the culprit. My galaxy S4 LTE-A suffers from battety drain. I found the kernel wakelock only occurs when wifi is on. But when my S4 is connected to specific routers, wakeup count of the wakelock soars up. Yours is about a third of total count, which is very high. I suggest changing your router.. I tried some tricks to make it right, but none did work. Changing router did the trick. Total count of the kernel wakelock was still high, but wakeup count of it considerably dropped, and battery drain was gone.
Sent from my SHV-E330S using Tapatalk
Click to expand...
Click to collapse
What do you mean by "change router"? I only have one router at home and my battery loss occurs everywhere I go anyway.