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
Hi,
I'll try to keep this short. I am reading about battery drain from this forum, and I am not finding what I am looking for. So while I continue to look. I figured I'd ask here in case someone can help.
I bought a N4 6-8 months ago with a defective Digitizer. I bought a replacement lcd/dig/front frame assembly and changed it. The phone worked great since a week ago.
A while back I noticed the gps was not working. I found a thread on here about the new front frame not having the proper grounds for the main board. I switched the conductive pads from my old frame (the ones that did not rip) and it worked for a day. After that, it didn't. So I bought copper tape and put some where the pads where. No change. I left it like that. Not sure if this is relevant, but what the hell.
a week and a half later, I clicked the stock phone app (which was deactivated) and the phone blacked out. When i plugged it into a computer, I got "transfer-mode, do not unplug) and the phone did not boot. I brought it home, plugged it into the wall charger, and it charged up. So i thought, cool! This is running stock android 5.0.1 or 5.1 i don't remember.
Woke up the next day, phone is dead, when i plug it in, i get solid red light.
Next day i read up, decide to jump start the battery using a charger with bare wires on the leads for 5-6 min and plus it back in. The phone lights up and starts charging. So i figure, battery is dead. I order one off ebay.
change battery with new one, phone charges up, I'm happy.
Next day, wake up, phone is dead. Plug it in, i get solid red light again. Jump-start the new battery and think maybe it is a sofware issue.
day after flash the phone with CM 10.2 (or what the latest stable build is) and hope for the best. It changes nothing.
next day i open up the phone and remove all the copper tape I installed thinking, maybe I shorted something. No change
day after I completely erase the phone and do a clean install of Android stock 5.1, no change
I then install betterbatterystats and start monitoring. I am not rooted so I don't have access to everything. but from what I can tell, no wakelocks and the phone is pretty much in deep sleep (91%) all night long, yet if I go to bed around 10 with 100% bat, at 5 in the morning i have less than 20%. Everything looks like it is okay to me. Is rooting to see all the stats a good idea?
since the clean install of android. I dont see all the app in the battery stats page, and everything is at 1-3%, which i find odd.
When i was on CM I had "Android idle at 6x%" and "cellphone idle" at 3x%. Not sure those where the exact titles, but something along the lines.
When the phone is fully charged, it says i have 8 hours left (which i find very low), but it seems more like 6-7 hours. and if it drops too low, i get solid red light...
I also noticed that when plugged into a computer, the phone takes forever to charge (like 6-7 hours until full from what android tell me) and if i use the phone when plugged into a computer, it actually discharges faster then it charges...
Can it be my microphone/charger/ect. module that is no good?
The phone literally went from fully functionnal, to totally ****ed in one seconds in my hands...
Any thoughts?
Try to root and track all the services..u might have a massive wakelock..but..i don.t know..this story it.s a nightmare :| it.s preety strange to have such a battery drain..
Sent from my Nexus 4 using XDA Free mobile app
Thank you. I just rooted the phone, I'll charge to 100% and post pics of what betterbatterystats shows.
Also u can try to calibrate the battery , u can find some apps on Play Store
Thanks I'll look into that too.
It's weird because today I only rooted the phone, and stock battery app tells me I have 12 hours on full charge (I still don't see everything in the list) instead of 8-9 hours...
In betterbatterystats i have 9.x%/hr battery drain, compared to 12-20%/hours before rooting... It makes no sense.
I'm charging to phone to full and I'll see what happened with the battery tomorrow morning.
Also I read in other threads here that it can possibly have something to do with the wifi network. I don't even know where to begin on this one... But i did log into a different network at work this week because the usual one wasn't available where i was in the building. Which I hadn't done until now, and my phone had been switching for one network to another when i moved in the building.
Like I said I don't even know where to start if it' sa network/router thing. And I don'T even know if it is at all possible that this could be the source of the problem. And nothing changed at home.
I'm just considering every possible options as I am really stumped, and nothing that has happened until now makes sense... Like the phone getting better battery life from rooting or monitoring with BBS while rooted. It makes no sense.
I didn't mention but all localisation and wifi scanning options have been deactivated. Brightness is at minimum with auto brightness on. Wifi is always on during sleep because I use Fongo to make and receive calls on VoIP.
I never checked battery status before, but i seem to remember having 16-20 hours of battery life if I didn't use the phone.
I can live with having 5-8 hours of usage time, but as is, if i don't fully charge the phone before going to bed (i left it plugged in the last few days), it's dead in the morning and i have to open up the phone to boost the battery....
Thanks again for the help, I'll see if my phone is dead tomorrow, and try a calibration app.
So phone was 100% when i went to bed down to 27% when i woke up. From what i can see, no wakelocks. When i look at stock battery app, i get a steady descending slope to 0% and the numbers don't make sense either. I'll try to attach a pic (sorry the phone is in french)
I decided to see what would happen if i let the phone go down as low as it could. I was at about 18% while using the phone (i think i was looking at instagram or this forum on tapatalk) and the phone blacked out.
It would not boot up and when I plugged it in. I got Solid red light again. The phone won't boot, won't charge.
So i had to take my battery out and boost it again before the phone would recognise it and charge it. The battery is new, from ebay. Is it possible the battery is a dud? then again i had the same results with my old battery. And the one I got from ebay looks pretty much the same as the old one, tagged LG BL-T5 and the seller was a power seller.
Here is a pic of the stock battery settings app, and the text dump from BBS. Thanks for any help
{
"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"
}
BetterBatteryStats-2015-04-23_071904024.txt
Open with
===================
General Information
===================
BetterBatteryStats version: 2.0.0.0
Creation Date: 2015-04-23 07:19:03
Statistic Type: Unplugged to Current
Since 9 h 49 m 30 s
VERSION.RELEASE: 5.1
BRAND: google
DEVICE: mako
MANUFACTURER: LGE
MODEL: Nexus 4
OS.VERSION: 3.4.0-perf-gf75bb4f
BOOTLOADER: MAKOZ30f
HARDWARE: mako
FINGERPRINT: google/occam/mako:5.1/LMY47O/1783956:user/release-keys
ID: LMY47O
TAGS: release-keys
USER: android-build
PRODUCT: occam
RADIO: M9615A-CEFWMAZM-2.0.1701.06
Rooted: true
SELinux Policy: Enforcing
BATTERY_STATS permission granted: true
XPosed BATTERY_STATS module enabled: false
============
Battery Info
============
Level lost [%]: Bat.: -73%(100% to 27%) [7,4%/h]
Voltage lost [mV]: (4255-3562) [70,6%/h]
===========
Other Usage
===========
Deep Sleep (): 9 h 39 m 54 s 98,4%
Awake (): 9 m 35 s 1,6%
Screen On (): 2 m 42 s 0,5%
Wifi On (): 9 h 49 m 30 s 100,0%
Wifi Running (): 9 h 49 m 30 s 100,0%
No Data Connection (): 9 h 49 m 30 s 100,0%
No or Unknown Signal (): 9 h 49 m 30 s 100,0%
Screen dark (): 2 m 42 s 0,5%
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
*alarm* (Système Android): 31 s Count:381 0,1%
NextAlarmTracker (Système Android): 24 s Count:83 0,1%
FbClientConnManager (com.facebook.katana.Facebook): 15 s Count:11 0,0%
*net_scheduler* (Services Google): 14 s Count:431 0,0%
*sync*/gmail-ls/com.google/[email protected] (com.google.android.gm.Gmail): 9 s Count:9 0,0%
Checkin Service (Services Google): 9 s Count:359 0,0%
*sync*/com.google.android.apps.plus.content.EsProvider/com.google/[email protected] (com.google.android.apps.plus.Google+): 6 s Count:5 0,0%
FbClientConnManager (com.facebook.orca.Messenger): 6 s Count:5 0,0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 5 s Count:4 0,0%
Config Service fetch (Services Google): 5 s Count:21 0,0%
*backup* (Système Android): 4 s Count:103 0,0%
Icing (Services Google): 3 s Count:69 0,0%
*sync*/com.google.android.apps.docs.editors.trix/com.google/[email protected] (com.google.android.apps.docs.editors.sheets.Feuilles de calcul): 2 s Count:3 0,0%
Event Log Service (Services Google): 2 s Count:48 0,0%
*sync*/subscribedfeeds/com.google/[email protected] (Services Google): 2 s Count:49 0,0%
GCM_CONN (Services Google): 1 s Count:341 0,0%
GCM_CONN_ALARM (Services Google): 1 s Count:23 0,0%
BaseSyncManager (com.google.android.apps.docs.editors.sheets.Feuilles de calcul): 1 s Count:1 0,0%
hangouts_rtcs (com.google.android.talk.Hangouts): 1 s Count:4 0,0%
================
Kernel Wakelocks
================
"PowerManagerService.WakeLocks" (): 2 m 32 s Cntc/wc/ec)472/0/0 0,4%
"msm_hsic_host" (): 57 s Cntc/wc/ec)51/26/0 0,2%
"qcom_rx_wakelock" (): 41 s Cntc/wc/ec)881/458/881 0,1%
"alarm_rtc" (): 11 s Cntc/wc/ec)258/231/0 0,0%
"suspend_backoff" (): 9 s Cntc/wc/ec)1/0/1 0,0%
"alarm" (): 6 s Cntc/wc/ec)457/0/0 0,0%
"radio-interface" (): 5 s Cntc/wc/ec)8/0/0 0,0%
"sns_async_ev_wakelock" (): 3 s Cntc/wc/ec)3/0/0 0,0%
"kickstart" (): 1 s Cntc/wc/ec)7/0/0 0,0%
"KeyEvents" (): Cntc/wc/ec)1568/0/0 0,0%
"power-supply" (): Cntc/wc/ec)-22/0/0 0,0%
"mmc0_detect" (): Cntc/wc/ec)844/0/0 0,0%
"PowerManagerService.Display" (): Cntc/wc/ec)3/0/0 0,0%
"PowerManagerService.Broadcasts" (): Cntc/wc/ec)6/0/0 0,0%
"qmuxd_port_wl_9" (): Cntc/wc/ec)143/0/0 0,0%
======================================================
Processes (requires root / system app on Android 4.4+)
======================================================
system (Système Android): Uid: 1000 Sys: 12 s Us: 24 s Starts: 0
com.asksven.betterbatterystats (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10113 Sys: 6 s Us: 17 s Starts: 0
surfaceflinger (Système Android): Uid: 1000 Sys: 6 s Us: 7 s Starts: 0
mmcqd/0 (0): Uid: 0 Sys: 14 s Us: Starts: 0
com.android.systemui (com.android.systemui.IU système): Uid: 10024 Sys: 2 s Us: 10 s Starts: 0
com.facebook.katana (com.facebook.katana.Facebook): Uid: 10096 Sys: 4 s Us: 6 s Starts: 0
com.fongo.dellvoice (com.fongo.dellvoice.Fongo): Uid: 10090 Sys: 10 s Us: Starts: 0
com.google.android.gm (com.google.android.gm.Gmail): Uid: 10074 Sys: 1 s Us: 6 s Starts: 1
com.facebook.orca (com.facebook.orca.Messenger): Uid: 10112 Sys: 2 s Us: 3 s Starts: 0
mpdecision (0): Uid: 0 Sys: 5 s Us: Starts: 0
com.google.process.gapps (Services Google): Uid: 10009 Sys: 1 s Us: 3 s Starts: 0
com.google.android.gms (Services Google): Uid: 10009 Sys: 2 s Us: 2 s Starts: 0
ueventd (0): Uid: 0 Sys: 2 s Us: Starts: 0
kworker/0:3 (0): Uid: 0 Sys: 2 s Us: Starts: 0
kworker/u:21 (0): Uid: 0 Sys: 2 s Us: Starts: 0
*wakelock* (com.facebook.katana.Facebook): Uid: 10096 Sys: 1 s Us: Starts: 0
kworker/u:4 (0): Uid: 0 Sys: 2 s Us: Starts: 0
kworker/u:25 (0): Uid: 0 Sys: 2 s Us: Starts: 0
kworker/u:30 (0): Uid: 0 Sys: 2 s Us: Starts: 0
com.android.launcher (com.android.launcher.Lanceur d'appli): Uid: 10016 Sys: Us: 1 s Starts: 0
kworker/0:2 (0): Uid: 0 Sys: 2 s Us: Starts: 0
kworker/u:35 (0): Uid: 0 Sys: 2 s Us: Starts: 0
kworker/0:5 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:7 (0): Uid: 0 Sys: 1 s Us: Starts: 0
migration/0 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/0:0 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:9 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:22 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:37 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:26 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:34 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:28 (0): Uid: 0 Sys: 1 s Us: Starts: 0
*wakelock* (com.facebook.orca.Messenger): Uid: 10112 Sys: 1 s Us: Starts: 0
jbd2/mmcblk0p23 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:18 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:2 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:13 (0): Uid: 0 Sys: 1 s Us: Starts: 0
com.google.android.apps.plus (com.google.android.apps.plus.Google+): Uid: 10071 Sys: Us: 1 s Starts: 0
kworker/u:38 (0): Uid: 0 Sys: 1 s Us: Starts: 0
logd (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:23 (0): Uid: 0 Sys: 1 s Us: Starts: 0
com.google.android.apps.docs.editors.sheets (com.google.android.apps.docs.editors.sheets.Feuilles de calcul): Uid: 10045 Sys: Us: 1 s Starts: 1
kworker/u:17 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:14 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:10 (0): Uid: 0 Sys: 1 s Us: Starts: 0
*wakelock* (Services Google): Uid: 10009 Sys: Us: Starts: 0
kworker/u:6 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:40 (0): Uid: 0 Sys: 1 s Us: Starts: 0
zygote (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:27 (0): Uid: 0 Sys: 1 s Us: Starts: 0
*wakelock* (com.google.android.apps.plus.Google+): Uid: 10071 Sys: Us: Starts: 0
kworker/u:20 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:8 (0): Uid: 0 Sys: 1 s Us: Starts: 0
kworker/u:5 (0): Uid: 0 Sys: 1 s Us: Starts: 0
netd (0): Uid: 0 Sys: Us: Starts: 0
com.google.android.gms.persistent (Services Google): Uid: 10009 Sys: Us: Starts: 0
kworker/u:29 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:33 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:36 (0): Uid: 0 Sys: Us: Starts: 0
com.google.android.inputmethod.latin (com.google.android.inputmethod.latin.Clavier Google): Uid: 10057 Sys: Us: Starts: 0
kworker/u:15 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:11 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:16 (0): Uid: 0 Sys: Us: Starts: 0
mediaserver (1013): Uid: 1013 Sys: Us: Starts: 0
kworker/u:32 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:12 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:19 (0): Uid: 0 Sys: Us: Starts: 0
tmp-mksh (0): Uid: 0 Sys: Us: Starts: 0
kworker/0:1 (0): Uid: 0 Sys: Us: Starts: 0
com.google.android.gms.unstable (Services Google): Uid: 10009 Sys: Us: Starts: 1
kworker/u:3 (0): Uid: 0 Sys: Us: Starts: 0
sensors.qcom (0): Uid: 0 Sys: Us: Starts: 0
lmkd (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:0 (0): Uid: 0 Sys: Us: Starts: 0
kthreadd (0): Uid: 0 Sys: Us: Starts: 0
daemonsu:10113 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:31 (0): Uid: 0 Sys: Us: Starts: 0
RX_Thread (0): Uid: 0 Sys: Us: Starts: 0
TX_Thread (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:1 (0): Uid: 0 Sys: Us: Starts: 0
com.android.settings (Système Android): Uid: 1000 Sys: Us: Starts: 1
kworker/u:24 (0): Uid: 0 Sys: Us: Starts: 0
su (com.asksven.betterbatterystats.BetterBatteryStats): Uid: 10113 Sys: Us: Starts: 0
flush-179:0 (0): Uid: 0 Sys: Us: Starts: 0
bdi-default (0): Uid: 0 Sys: Us: Starts: 0
MC_Thread (0): Uid: 0 Sys: Us: Starts: 0
android.process.media (Médias): Uid: 10006 Sys: Us: Starts: 1
rild (0): Uid: 0 Sys: Us: Starts: 0
com.google.android.googlequicksearchbox:search (com.google.android.googlequicksearchbox.Application Google): Uid: 10026 Sys: Us: Starts: 0
com.android.phone (Téléphone): Uid: 1001 Sys: Us: Starts: 0
kworker/u:41 (0): Uid: 0 Sys: Us: Starts: 0
kworker/u:39 (0): Uid: 0 Sys: Us: Starts: 0
thermald (0): Uid: 0 Sys: Us: Starts: 0
ksoftirqd/0 (0): Uid: 0 Sys: Us: Starts: 0
android.process.acore (Applications de base Android): Uid: 10004 Sys: Us: Starts: 1
com.google.android.keep (com.google.android.keep.Keep): Uid: 10075 Sys: Us: Starts: 2
servicemanager (Système Android): Uid: 1000 Sys: Us: Starts: 0
com.google.android.talk (com.google.android.talk.Hangouts): Uid: 10015 Sys: Us: Starts: 1
jbd2/mmcblk0p21 (0): Uid: 0 Sys: Us: Starts: 0
kworker/1:1 (0): Uid: 0 Sys: Us: Starts: 0
com.android.vending (com.android.vending.Google Play Store): Uid: 10020 Sys: Us: Starts: 2
healthd (0): Uid: 0 Sys: Us: Starts: 0
com.android.nfc (com.android.nfc.Service NFC): Uid: 1027 Sys: Us: Starts: 0
jbd2/mmcblk0p22 (0): Uid: 0 Sys: Us: Starts: 0
ks (Système Android): Uid: 1000 Sys: Us: Starts: 0
com.google.android.apps.maps (com.google.android.apps.maps.Maps): Uid: 10060 Sys: Us: Starts: 1
file-storage (0): Uid: 0 Sys: Us: Starts: 0
com.android.providers.calendar (com.android.providers.calendar.Stockage de l'agenda): Uid: 10002 Sys: Us: Starts: 0
com.google.android.calendar (com.google.android.calendar.Agenda): Uid: 10034 Sys: Us: Starts: 2
vold (0): Uid: 0 Sys: Us: Starts: 0
daemonsu:master (0): Uid: 0 Sys: Us: Starts: 0
======================
Alarms (requires BATTERY_STATS permissions)
======================
com.google.android.gms (): Wakeups: 154 (15,7 / h)
Alarms: 0, Intent: ALARM_WAKEUP_ACTIVITY_DETECTION
Alarms: 1, Intent: com.google.android.intent.action.GCM_RECONNECT
Alarms: 127, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 19, Intent: com.google.android.gms/.checkin.EventLogService$Receiver
Alarms: 2, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 1, Intent: com.google.android.gms.reminders.REFRESH_NOTIFICATION
Alarms: 0, Intent: com.google.android.gms.fitness.aggregate
Alarms: 0, Intent: snet.service.intent.action.IDLE_MODE
Alarms: 0, Intent: com.google.android.gms/.common.download.DownloadAlarmReceiver
Alarms: 1, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE
Alarms: 1, Intent: com.google.android.gms/com.google.android.libraries.social.mediamonitor.MediaMonitorIntentService
Alarms: 1, Intent: com.google.android.gms/.checkin.CheckinService$Receiver
Alarms: 0, Intent: com.google.android.gms.fitness.trim
Alarms: 1, Intent: snet.service.intent.action.NORMAL_MODE
Alarms: 0, Intent: com.google.android.gms.common.receiver.LOG_CORE_ANALYTICS
android (): Wakeups: 82 (8,4 / h)
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 0, Intent: android.content.jobscheduler.JOB_DELAY_EXPIRED
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 46, Intent: android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED
Alarms: 0, Intent: android.content.jobscheduler.JOB_DEADLINE_EXPIRED
Alarms: 23, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 0, Intent: com.android.server.task.controllers.BatteryController.ACTION_CHARGING_STABLE
Alarms: 10, Intent: android.app.backup.intent.RUN
Alarms: 2, Intent: com.android.server.task.controllers.IdleController.ACTION_TRIGGER_IDLE
Alarms: 1, Intent: android.appwidget.action.APPWIDGET_UPDATE
Alarms: 0, Intent: com.android.server.WifiManager.action.START_SCAN
Alarms: 0, Intent: NextAlarmTracker.trigger
com.fongo.dellvoice (): Wakeups: 58 (5,9 / h)
Alarms: 58, Intent: REG_KEEP_ALIVE
com.facebook.orca (): Wakeups: 56 (5,7 / h)
Alarms: 39, Intent: com.facebook.push.mqtt.keepalive.b.ACTION_INEXACT_ALARM.com.facebook.orca
Alarms: 12, Intent: com.facebook.analytics.service.a.ACTION_ALARM
Alarms: 5, Intent: com.facebook.common.executors.cr.ACTION_ALARM.com.facebook.orca
Alarms: 0, Intent: com.facebook.orca.database.ACTION_ALARM
com.facebook.katana (): Wakeups: 53 (5,4 / h)
Alarms: 39, Intent: com.facebook.push.mqtt.keepalive.KeepaliveManager.ACTION_INEXACT_ALARM.com.facebook.katana
Alarms: 12, Intent: com.facebook.analytics.service.AnalyticsEventUploader.ACTION_ALARM
Alarms: 2, Intent: com.facebook.common.executors.WakingExecutorService.ACTION_ALARM.com.facebook.katana
Alarms: 0, Intent: com.facebook.katana/com.facebook.videoads.scheduler.VideoAdsFetchService
Alarms: 0, Intent: com.facebook.orca.database.ACTION_ALARM
com.android.providers.calendar (): Wakeups: 5 (0,5 / h)
Alarms: 5, Intent: com.android.providers.calendar.intent.CalendarProvider2
com.quoord.tapatalkpro.activity (): Wakeups: 4 (0,4 / h)
Alarms: 4, Intent: com.quoord.tapatalkpro.activity/com.quoord.tapatalkpro.alarm.PingsOnAlarmReceiver
com.google.android.googlequicksearchbox (): Wakeups: 2 (0,2 / h)
Alarms: 2, Intent: com.google.android.googlequicksearchbox/com.google.android.velvet.VelvetBackgroundTasksImpl$Service
com.google.android.talk (): Wakeups: 2 (0,2 / h)
Alarms: 0, Intent: com.google.android.apps.hangouts.RENEW_ACCOUNT_REGISTRATION
Alarms: 2, Intent: com.google.android.apps.hangouts.CLEANUP_DB
com.google.android.apps.plus (): Wakeups: 1 (0,1 / h)
Alarms: 1, Intent: com.google.android.apps.moviemaker.analyzer.PING
Alarms: 0, Intent: com.google.android.apps.plus.checkandengagesync
com.google.android.keep (): Wakeups: 1 (0,1 / h)
Alarms: 1, Intent: com.google.android.keep.intent.action.REFRESH_NOTIFICATION
======================
Network (requires root)
======================
10074 (Wifi) (com.google.android.gm.Gmail): 299.0 KBytes 21,8%
10009 (Wifi) (Services Google): 274.0 KBytes 20,0%
10096 (Wifi) (com.facebook.katana.Facebook): 217.0 KBytes 15,8%
10090 (Wifi) (com.fongo.dellvoice.Fongo): 177.0 KBytes 12,9%
10045 (Wifi) (com.google.android.apps.docs.editors.sheets.Feuilles de calcul): 143.0 KBytes 10,5%
10112 (Wifi) (com.facebook.orca.Messenger): 125.0 KBytes 9,1%
0 (Wifi) (0): 55.0 KBytes 4,1%
10071 (Wifi) (com.google.android.apps.plus.Google+): 27.0 KBytes 2,0%
1000 (Wifi) (Système Android): 21.0 KBytes 1,6%
10020 (Wifi) (com.android.vending.Google Play Store): 12.0 KBytes 0,9%
10026 (Wifi) (com.google.android.googlequicksearchbox.Application Google): 10.0 KBytes 0,8%
10060 (Wifi) (com.google.android.apps.maps.Maps): 7.0 KBytes 0,5%
10006 (Wifi) (Médias): 52.0 Bytes 0,0%
==========
CPU States
==========
1,51 GHz (): 3 m 7 s 0,5%
1,46 GHz (): 4 s 0,0%
1,35 GHz (): 6 s 0,0%
1,24 GHz (): 5 s 0,0%
1,13 GHz (): 7 s 0,0%
1,03 GHz (): 1 m 24 s 0,2%
918 MHz (): 4 s 0,0%
810 MHz (): 10 s 0,0%
702 MHz (): 6 s 0,0%
594 MHz (): 10 s 0,0%
486 MHz (): 9 s 0,0%
384 MHz (): 3 m 58 s 0,7%
Deep Sleep (): 9 h 39 m 54 s 98,4%
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
See http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
com.android.bluetooth (com.android.bluetooth.hid.HidService)
Active since: 38 s
Last activity: 38 s
Crash count:0
com.android.systemui (com.android.systemui.keyguard.KeyguardService)
Active since: 42 s
Last activity: 42 s
Crash count:0
com.android.systemui (com.android.systemui.ImageWallpaper)
Active since: 39 s
Last activity: 39 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.geocode.GeocodeService)
Active since: 18 h 18 m 13 s
Last activity: 3 h 50 m 17 s
Crash count:0
com.google.process.gapps (com.google.android.gms.gcm.GcmService)
Active since: 40 s
Last activity: 3 h 50 m 19 s
Crash count:0
com.google.android.music:main (com.google.android.music.download.artwork.ArtDownloadService)
Active since: 4 h 20 m 3 s
Last activity: 1 h 44 m 9 s
Crash count:0
com.google.android.gms (com.google.android.gms.analytics.service.AnalyticsService)
Active since: 12 h 14 m 23 s
Last activity: 3 h 50 m 42 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.fused.service.FusedProviderService)
Active since: 18 h 18 m 13 s
Last activity: 3 h 50 m 17 s
Crash count:0
com.google.android.music:main (com.google.android.music.preferences.MusicPreferenceService$MusicPreferenceServiceBinder)
Active since: 4 h 20 m 3 s
Last activity: 1 h 42 m
Crash count:0
com.fongo.dellvoice (com.fongo.dellvoice.FongoPhoneService)
Active since: 1 m 2 s
Last activity: 2 h 54 m 51 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.pbap.BluetoothPbapService)
Active since: 38 s
Last activity: 38 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.fused.FusedLocationService)
Active since: 18 h 18 m 13 s
Last activity: 3 h 50 m 17 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.a2dp.A2dpService)
Active since: 38 s
Last activity: 38 s
Crash count:0
com.google.android.googlequicksearchbox:search (com.google.android.search.core.service.SearchService)
Active since: 56 s
Last activity: 56 s
Crash count:0
com.google.process.gapps (com.google.android.gms.gcm.http.GoogleHttpService)
Active since: 40 s
Last activity: 3 h 51 m 6 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.geofencer.service.GeofenceProviderService)
Active since: 18 h 18 m 13 s
Last activity: 3 h 50 m 17 s
Crash count:0
com.google.android.talk (com.google.android.libraries.hangouts.video.CallService)
Active since: 10 h 50 m 10 s
Last activity: 3 h 44 m 23 s
Crash count:0
com.google.process.gapps (com.google.android.gms.icing.service.LightweightIndexService)
Active since: 19 h 32 m 28 s
Last activity: 3 h 52 m 30 s
Crash count:0
com.android.systemui (com.android.systemui.SystemUIService)
Active since: 36 s
Last activity: 36 s
Crash count:0
system (android.hardware.location.GeofenceHardwareService)
Active since: 40 s
Last activity: 40 s
Crash count:0
com.google.android.music:main (com.google.android.music.net.NetworkMonitor)
Active since: 4 h 20 m 2 s
Last activity: 1 h 44 m 9 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.internal.PendingIntentCallbackService)
Active since: 1 m 12 s
Last activity: 1 m 29 s
Crash count:0
com.google.process.gapps (com.google.android.gms.auth.GetToken)
Active since: 19 h 32 m 27 s
Last activity: 3 h 52 m 29 s
Crash count:0
system (com.android.server.telecom.BluetoothPhoneService)
Active since: 40 s
Last activity: 41 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.internal.server.GoogleLocationService)
Active since: 41 s
Last activity: 3 h 51 m 16 s
Crash count:0
com.google.android.talk (com.google.android.libraries.hangouts.video.VideoChatService)
Active since: 45 s
Last activity: 45 s
Crash count:0
com.facebook.katana (com.facebook.fbservice.service.DefaultBlueService)
Active since: 10 h 45 m 48 s
Last activity: 3 h 50 m 47 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.network.NetworkLocationService)
Active since: 18 h 18 m 13 s
Last activity: 3 h 50 m 17 s
Crash count:0
com.android.phone (com.android.stk.StkAppService)
Active since: 55 s
Last activity: 3 h 48 m 52 s
Crash count:0
com.google.android.gms.persistent (com.google.android.location.internal.GoogleLocationManagerService)
Active since: 41 s
Last activity: 3 h 48 m 48 s
Crash count:0
com.google.android.inputmethod.latin (com.android.inputmethod.latin.LatinIME)
Active since: 40 s
Last activity: 3 h 48 m 37 s
Crash count:0
com.facebook.orca (com.facebook.fbservice.service.DefaultBlueService)
Active since: 3 h 56 m 19 s
Last activity: 3 h 51 m 14 s
Crash count:0
com.google.android.gms.persistent (com.google.android.gms.deviceconnection.service.DeviceConnectionServiceBroker)
Active since: 41 s
Last activity: 3 h 50 m 19 s
Crash count:0
com.google.android.googlequicksearchbox:interactor (com.google.android.voiceinteraction.GsaVoiceInteractionService)
Active since: 39 s
Last activity: 40 s
Crash count:0
system (com.android.internal.backup.LocalTransportService)
Active since: 36 s
Last activity: 36 s
Crash count:0
com.google.process.gapps (com.google.android.gms.playlog.service.PlayLogBrokerService)
Active since: 12 h 13 m 28 s
Last activity: 3 h 51 m 27 s
Crash count:0
com.google.android.gms.persistent (com.google.android.gms.common.stats.GmsCoreStatsService)
Active since: 40 s
Last activity: 3 h 50 m 19 s
Crash count:0
com.google.process.gapps (com.google.android.gms.clearcut.service.ClearcutLoggerService)
Active since: 4 h 7 m 44 s
Last activity: 3 h 51 m 6 s
Crash count:0
com.facebook.katana (com.facebook.push.mqtt.service.MqttPushService)
Active since: 53 s
Last activity: 2 h 45 m 34 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.map.BluetoothMapService)
Active since: 38 s
Last activity: 38 s
Crash count:0
com.facebook.orca (com.facebook.push.mqtt.service.MqttPushService)
Active since: 49 s
Last activity: 50 s
Crash count:0
com.android.phone (com.android.phone.TelephonyDebugService)
Active since: 41 s
Last activity: 41 s
Crash count:0
system (com.android.server.telecom.TelecomService)
Active since: 36 s
Last activity: 36 s
Crash count:0
com.google.android.gms (com.google.android.gms.icing.service.IndexService)
Active since: 19 h 32 m 28 s
Last activity: 3 h 52 m 32 s
Crash count:0
com.android.bluetooth (com.android.bluetooth.pan.PanService)
Active since: 38 s
Last activity: 38 s
Crash count:0
com.google.android.gms.persistent (com.google.android.gms.backup.BackupTransportService)
Active since: 18 h 18 m 13 s
Last activity: 3 h 50 m 16 s
Crash count:0
==================
Reference overview
==================
ref_boot: Reference ref_boot created 1 m 2 s (Wl: 3 elements; KWl: 9elements; NetS: 7 elements; Alrm: 0 elements; Proc: 24 elements; Oth: 9 elements; CPU: 12 elements)
ref_custom: Reference ref_custom created 4 h 5 m 57 s (Wl: 11 elements; KWl: 22elements; NetS: 20 elements; Alrm: 13 elements; Proc: 107 elements; Oth: 9 elements; CPU: 13 elements)
ref_unplugged: Reference ref_unplugged created 9 h 42 m 56 s (Wl: 0 elements; KWl: 23elements; NetS: 23 elements; Alrm: 14 elements; Proc: 0 elements; Oth: 8 elements; CPU: 13 elements)
ref_charged: Reference ref_charged created 9 h 42 m 58 s (Wl: 0 elements; KWl: 23elements; NetS: 23 elements; Alrm: 14 elements; Proc: 0 elements; Oth: 8 elements; CPU: 13 elements)
ref_current: Reference ref_current created 19 h 32 m 27 s (Wl: 19 elements; KWl: 23elements; NetS: 24 elements; Alrm: 15 elements; Proc: 111 elements; Oth: 8 elements; CPU: 13 elements)
Displaying BetterBatteryStats-2015-04-23_071904024.txt.
Just installed Battery Calibration and will try to calibrate when the phone reaches 100%
Ok so after installing a new battery, flashing roms, clean install, rooting, betterbatterystats, battery calibration...
I still have the drain... I don't know why I didn't test this earlier, but I charged the phone last night and shut it down before going to sleep. It was at 90% when shutting down, and 17% when booting up this morning...
So now I'm charging at 100%, and I'll unplug the battery for a couple of hours to see if it's the battery itself that doesn't hold a charge...
I have looked for a physical short in the phone and haven't found one...
If it's not the battery I'll try to unplug modules one at a time and leaving the battery plugged in to see if unplugging something stops the drain.
If i can't find the source of the drain, I guess the brick wall is my last option...
If anyone has any ideas, I'm all ears.
Thanks
fullpampers said:
Ok so after installing a new battery, flashing roms, clean install, rooting, betterbatterystats, battery calibration...
I still have the drain... I don't know why I didn't test this earlier, but I charged the phone last night and shut it down before going to sleep. It was at 90% when shutting down, and 17% when booting up this morning...
So now I'm charging at 100%, and I'll unplug the battery for a couple of hours to see if it's the battery itself that doesn't hold a charge...
I have looked for a physical short in the phone and haven't found one...
If it's not the battery I'll try to unplug modules one at a time and leaving the battery plugged in to see if unplugging something stops the drain.
If i can't find the source of the drain, I guess the brick wall is my last option...
If anyone has any ideas, I'm all ears.
Thanks
Click to expand...
Click to collapse
You may have some apps running the background causing the drain. You might check out Greenify App from the App store. It will manage any apps running in the background and it is very simple to use.
I hope that helps........ I seriously doubt that your battery is bad. What version of Lollipop are you on?
Running 4.4.4 right now, just to try a different version of android. was running 5.1 before.
How can apps cause draining if the phone is completely powered down?
with a voltmeter you can check if it may is hardware related..but you have to find someone who knows about circuits and stuff..(I don't know)..
After 4.5 hours with the battery unplugged, the battery retained it's charge.... I'll look again for physical shorts...
This sucks, we're getting closer to the brick wall....
ZaNobey said:
with a voltmeter you can check if it may is hardware related..but you have to find someone who knows about circuits and stuff..(I don't know)..
Click to expand...
Click to collapse
Yeah I thought about using a voltmeter to try and find the short, but with out a schematic, I'd just be blindly probing stuff.
I'll try and isolate modules to see if i can find which one is drawing from the battery. but if it's not just swapping out parts. I guess I'm screwed...
Looking at your BBS logs, your phone is in deep sleep for 98% which is actually very good, minimal wakelocks. Only awake for 9 minutes of of 9 hours.
Looking at the battery lost levels is a bit more telling. You should not be loosing 7.5% an hour, especially with these stats, it should be more around 1%.
Download battery monitor widget and see what your battery drain is like over a 12 hour period. Post results
I'm 90% sure there is something physically (hardware) wrong with the phone.
Last night I charged the battery to 100%, unplugged all modules from the main logic board and left it in the case (so battery plugged into logic board, logic board still in front frame assembly, i left the power and volume buttons in). With the phone powered down.
When I woke I reassembled the phone, battery was at 30%.
Tonight I'll do the same thing but take the battery/logic board out of the frame assembly. If it still drains, then it's the logic board, if not i would suspect a short between the board and the frame of the phone or one of the power/volume buttons.
I really hope it's one of either because if it's something wrong with the logic board, I'm not going to buy a new one. I guess I could look into getting a phone with a broken glass from someone and swapping the logic board, but at the prices people are selling these phone, I might just change phone altogether.
Again, this effin' sucks....
Looks like it's the logic board (motherboard, whatever the kids call it)
The battery plugged into only the logic board (all other modules removed), outside the phone, still drew about 7-9% an hour. The part just above where the battery plugs in got slightly warmer, so maybe it's that part... As to if I can/want to find one and replace it is another story.
Looks like I'm going to have to buy a new phone...
Anyone have any idea if this can be fixed/where to get a cheap main board? Or I just trash the phone?