Right, no matter what, I'm getting battery drain in stand by. No sync, Google now disabled, no mail, no location reporting/history etc. and yet I'm getting weird battery readings. In the pic below you can see, I'll let it idle for a couple of hours and the battery will drain. Then I'll use the n10 and the levels will spike. BBS shows that the n10 is awake for about 4 hours but the partial wakelock and kernel wakelock nothing untoward. I'm reluctant to root as I dont want to void my warranty but is any one facing similar issues?
yets said:
I'm reluctant to root as I dont want to void my warranty but is any one facing similar issues?
Click to expand...
Click to collapse
You can unroot and relock your device. Rooting should not be a warrenty issue.
See: " [NEXUS 10 TOOLKIT V1.3.0] Drivers, Backup, Unlock, Root, Flash, Mods + MUCH MORE"
http://forum.xda-developers.com/showthread.php?t=2001868&highlight=unroot
Features mentioned among many: "* Unlock/Re-Lock your Bootloader"
You will not lose warranty just by rooting the tablet. Nexus devices are pretty much made to be unlocked and Google provides the tools themselves to do the unlocking. I have heard of other people get warranty stuff done even while their tablet was rooted. This is because warranty is for hardware defects, which are not caused by root. If you have software problems then yes, those are to do with rooting. But normally you can fix software issues simply by finding a better ROM that has more bugfixes.
Also, that is some really terrible battery life. My tablet loses 1% every 7-9 days while idle. CM10.1 ROM from CraigGomez (November build) with KTManta kernel.
EniGmA1987 said:
You will not lose warranty just by rooting the tablet. Nexus devices are pretty much made to be unlocked and Google provides the tools themselves to do the unlocking. I have heard of other people get warranty stuff done even while their tablet was rooted. This is because warranty is for hardware defects, which are not caused by root. If you have software problems then yes, those are to do with rooting. But normally you can fix software issues simply by finding a better ROM that has more bugfixes.
Also, that is some really terrible battery life. My tablet loses 1% every 7-9 days while idle. CM10.1 ROM from CraigGomez (November build) with KTManta kernel.
Click to expand...
Click to collapse
Is it worth getting in touch with Google? I've had it since just after xmas? I'm about to factory reset it for the second time this week.
Why do you need to factory reset it so often?
I would root it, install a custom kernel, and run better battery stats to try and see what exactly is causing such a huge idle drain.
EniGmA1987 said:
Why do you need to factory reset it so often?
I would root it, install a custom kernel, and run better battery stats to try and see what exactly is causing such a huge idle drain.
Click to expand...
Click to collapse
I'd rather not factory restore it, this is my second time doing it. I'm starting from the beginning like it's a fresh install, just using the Google apps only to see if there are issues there and then adding more until I'm comfortable.
I want to root the tablet only as a last resort as I'm attempting to see if it is an app or it is the battery. I'd rather not brick it or void warranty only to find out it is the battery and then be unable to get a replacement.
There must be somebody that has similar problems?
So, factory reset, this is after 24 hours; This is not kosher. Stock apps. Only thing syncing if you can call it that was Google now. No syncing or anything. Purely from stock apps with updates. Stock battery graph says that it's not awake but stats say it's awake for 19 hours.This doesn't even come close to advertised idle/stand by time. Surely I should return it? I was adamant that I wouldn't complain but I didn't pay so much money for it to come out with this as stock performance.
That is massive usage from Android OS. Something in there is causing a wakelock, which means it is probably a software problem. If you were rooted and had better battery stats installed then it would tell you exactly what the wakelock was from. The built in Android battery info just gives it a generic "Android OS". It looks to me like that sudden sharper downhill slope is the point which the wakelock started. Although that is a bit steep drain before that point too. The point before the sharper decline section looks closer to a non-deep sleeping device stuck at its lowest frequency, but it had to have been sleeping if the device says it was only awake for 14 hours. Still, that 14 hours is a wakelock. Probably from the kernel. Cant say what it is exactly unless you have a better app installed
The Google Services thing is probably Google Now sucking up battery. It tends to do that.
You can either continue to diagnose this problem from the software/firmware or you can just send it back if you want.
EniGmA1987 said:
That is massive usage from Android OS. Something in there is causing a wakelock, which means it is probably a software problem. If you were rooted and had better battery stats installed then it would tell you exactly what the wakelock was from. The built in Android battery info just gives it a generic "Android OS". It looks to me like that sudden sharper downhill slope is the point which the wakelock started. Although that is a bit steep drain before that point too. The point before the sharper decline section looks closer to a non-deep sleeping device stuck at its lowest frequency, but it had to have been sleeping if the device says it was only awake for 14 hours. Still, that 14 hours is a wakelock. Probably from the kernel. Cant say what it is exactly unless you have a better app installed
The Google Services thing is probably Google Now sucking up battery. It tends to do that.
You can either continue to diagnose this problem from the software/firmware or you can just send it back if you want.
Click to expand...
Click to collapse
Thanks. To be fair I think if purchasing such an item, you shouldn't have to become a developer/hacker to study such an issue. Haha! I've used Google now when I first got the tablet and not understanding what it was had it enabled and get there was no battery drain to such an extent.
Fair play to Google, they've agreed to send me out a new one. It reached a point where I couldn't enjoy using the tablet and everything was a test to see what could be causing the issue.
I won't bad mouth Google, as I understand that things do become faulty and these items are complex enough. On another note I called up the RMA team in American (I googled the wrong number) and the two ladies were more than helpful. I don't know how anyone has problems with them. Maybe it was my British accent that did it!
So, I've got a replacement and so far it is not displaying the same issues. It got me thinking about when my original problem started and I think it started when it was updated to 4.2.2. This model comes stock 4.2.1 and it's prompting me to update. Should I bother? Was I just unlucky? Is there a specific way to ensure that the update is a clean update?
yets said:
... This model comes stock 4.2.1 and it's prompting me to update. Should I bother? ...
Click to expand...
Click to collapse
Upgrade to 4.2.2 as it's more stable, especially with the Chrome browser but there are additional bug fixes that address overall stability. A rule of thumb is to install new apps one at a time so you can judge if it causes instability.
You can also install, free from the playstore, "Bootlog Uptime" which tracks crashes and sometimes provides crash related information from the Android logs. It is very handy when you are trying to determine the cause of a force close, freezing or general odd behaviour.
3DSammy said:
Upgrade to 4.2.2 as it's more stable, especially with the Chrome browser but there are additional bug fixes that address overall stability. A rule of thumb is to install new apps one at a time so you can judge if it causes instability.
Click to expand...
Click to collapse
Yeah, I kind of did that when I factory reset it, I just loaded up the stock apps, desynced everything, logged out of everything that wouldn't be used, disabled Google Now and location settings, rebooted and it was still iffy. Before I sent it back I left it for a day and the battery stats were going up and down like a roller coaster. Could it of been a faulty battery? I would like to update but I'm so wary of the problem coming back.
You can also install, free from the playstore, "Bootlog Uptime" which tracks crashes and sometimes provides crash related information from the Android logs. It is very handy when you are trying to determine the cause of a force close, freezing or general odd behaviour.
You may have been unlucky. I have had great battery on all 4.2.2 some ROMs/kernels make a difference.
Sent from my Nexus 10 using XDA Premium HD app
So, after a few days my new Nexus 10 started displaying exactly the same issues as before and I had just about ruled everything out. I used BBS again and looked at the stats, with PowerManagerService being the main culprit but the numbers in Partial wake locks just didn't match. There were very little wakelocks but something was still draining. I looked at the CPU and for most of the CPU was running at 200hz in deep sleep. I just couldn't figure it out and looked at the Running apps and there was only a few but one remained constant throughout all my tests and that was the Settings app. I took a punt and stopped it and cleared it from recent apps. Lo and Behold, the drain has disappeared and the battery doesn't drop at all in idle.
Excuse my noobiness, I didn't know that Android treated Settings as a separate app? On my Samsung S3, this isn't the case, once you leave settings it closes it and suspends it causing no drain.
200MHz in deep sleep doesnt make sense. Cause deep sleep is different than a MHz value. If you are mostly on 200MHz then that means something on the tablet is not letting you sleep properly.
EniGmA1987 said:
200MHz in deep sleep doesnt make sense. Cause deep sleep is different than a MHz value. If you are mostly on 200MHz then that means something on the tablet is not letting you sleep properly.
Click to expand...
Click to collapse
Sorry, didn't make myself clear. BBS was saying that tablet was running at 200mhz preventing it from deep sleep and that thing causing it was having the System Settings app not closing. Hope that makes sense and helps people in the future.
Well that is certainly an interesting find. If you restart the tablet and dont open settings does the tablet sleep fine?
Yes, if you restart it and avoid going into settings, it sleeps happily only waking sync if you have any. It has been idling for about 10 hours without dropping.
I've attached a picture and if you compare to the one I posted at the start of the thread you can see a clear difference. There was a point where I forgot to close Settings and you can see the drain (middle of the graph).
Somehow I don't think this is normal. It dropped almost 30% at home while I was at work. Google now is disabled but groove IP running. No apps that should be sucking battery, but its mostly the android OS. Any thoughts?
Sent from my Nexus 10 using xda app-developers app
Probably the exact same thing as the guy above me. Doesnt look like you are deep sleeping one bit.
So im a flashaholic, and ill usually flash new builds every couple weeks if they've included performance or features improvements. Ive always had good battery life .5 to 1.5% an hour. Well lately its sucked, at around 3%/hr idle. I always use the same stuff, Xylon Rom, and francos kernel. Ive tried just about everything to try and figure out why its happening, even trying different roms and kernels. One thing i will say is i believe when i had the best battery life was before the latest system update. When i was using baseband .33. So im thinking that might be my next test, to try to flash the older .33 radio.
Here are all the constants as far as applications i install that people might think be causing problems, even though BetterBatteryStats really shows no problematic wakelocks to my knowledge, which ill post screenshots of later for you guys to analyze
Facebook
Messenger
DashClock
Ez Weather Widget
Mightytext SMS
Franco Kernel App
What ive tried so far
1. Restored my phone stock 4.2.2 image from google developers. Flashing all the img files via fastboot trying to start from a clean phone. Right after that i flashed latest Xylon rom and franco milestone 2 kernel. After that i install all my apps, customize my phone and such. I charged it last night pulled it off and let it idle through the night and it dropped from 100% to 85% ~3%/hr. This is what ive been getting for the past 2 months so im guessing the stock flashing didnt help do anything. Unfortunately i didnt save the screen shots of betterbatterystats for you guys before i decided to proceed to step 2 this morning.
2. Trying a different kernel this morning and also upgraded my .48 baseband to the .54 one. I flashed Faux kernel this time, and also his Faux123 App. I kept all the default settings just like i do with Francos kernel. Im currently charging my phone to 100% right now, going to drain it throughout the day, and then charge it up again, clear the battery information and let it idle overnight. Ill report back after that, including the BetterBatteryStats information. Hopefully you guys can help me get this sorted out.
The problem is not coming from the kernels or the baseband. Most likely the trouble is coming from your apps. Install "wake lock detector" to find the cause of issue. Optional: download "Greenify" and hibernate apps so they won't drain power and wake up constantly.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
The problem is not coming from the kernels or the baseband. Most likely the trouble is coming from your apps. Install "wake lock detector" to find the cause of issue. Optional: download "Greenify" and hibernate apps so they won't drain power and wake up constantly.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, ill install that app and include Wakelock detectors findings as well.
i'm chasing a battery drain issue.
i can leave my phone at idle even after a reboot and still even after hours of idle it never goes to deep sleep and shows 8 hours in the 384 mhz.
i have deleted apps, factory reset, flashed stock kernel, flashed factory image, NOT loaded the apps from google restore and still it comes up.
i have tried using better battery stats and all it shows is SUSPEND BACK OFF WIFI..
what gives? how do people use BBB when it is never specific with what is causing things, its so vague and generic.
my device SHOULD go into deep sleep if i reboot and leave it at idle right?
nothing?
I just want to know how so many people swear by BBB when all it ever does for me is show generic wake locks and not which specific apps are contributing to those wake locks.
Hi! I just wanted to tell you that this has been haunting me as well during the last 5 days.
Before, I had tremendously good deep sleep. But now I have the same problem. I have tried different kernels, reinstall CM. It must be app related.
Sent from my Nexus 4 using xda premium
nextelbuddy said:
nothing?
I just want to know how so many people swear by BBB when all it ever does for me is show generic wake locks and not which specific apps are contributing to those wake locks.
Click to expand...
Click to collapse
There are 2 fields there. Kernel wakelocks and partial wakelocks.
Kernel ones are those that are held by the OS. Partial are the ones that are held by apps. You can find out which apps are consuming battery by looking into it.
wifi wakelock is held by the OS and not an app. So you'll see it mentioned under kernel wakelocks. Most likely your wifi router isn't allowing your phone to sleep. Try disabling wifi and see if you still get wakelocks.
Sent from my Nexus 4
thanks guys
i tracked it down manually to the app called ULTIMATE ROTATION and ULTIMATE ROTATION LICENSE
as soon as i removed those apps no more wake locks and i can now deep sleep properly.
posted a message on the play store but no response yet
i have the same problem after i reflashed my rom! i didnt have this issue b4! im using the exact same rom with the exact same apps, i just restored my backup... im not sure wat is causing the problem... i tried everything with no luck :S
Hello everyone I hope I got the right forum
I have a problem with the new system update released
The new update did not help at all to my nexus
I ran out of battery really fast, before the update it was fine
Battery had stayed a long time
What should I do?
1headshot said:
Hello everyone I hope I got the right forum
I have a problem with the new system update released
The new update did not help at all to my nexus
I ran out of battery really fast, before the update it was fine
Battery had stayed a long time
What should I do?
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=2385843
To get battery like this:
http://forum.xda-developers.com/showpost.php?p=44364085&postcount=5089
:cyclops:
Galaxo60 said:
Read this:
http://forum.xda-developers.com/showthread.php?t=2385843
To get battery like this:
http://forum.xda-developers.com/showpost.php?p=44364085&postcount=5089
:cyclops:
Click to expand...
Click to collapse
A quick look through that thread shows that it is focused on problems relating to Google Services. Since the update, I too am having issues with the battery draining more quickly than it ever did before. However, it appears to be msm_hsic_host wakelock causing the problem. Google services are a very small part of my battery usage.
I have posted a couple times about it in various threads, but I haven't seen a fix that applies to 4.3.
The battery drain is out of hand. I love my N4, but this is a big turn off for me.
I have tried these configurations to make sure it wasn't an oddball app causing the problem -
Stock 4.3 with stock Kernel - no root/stock recovery - Only apps being the ones that load on a factory reset
Wiped all partitions and reloaded stock 4.3/gapps/no root/stock recovery
Stock 4.3/rooted/TWRP/Stock gapps
Stock 4.3/rooted/TWRP/gapps+ a handful of other apps (photobucket/es file explorer/bbs - essentially, my normal config)
Added note - I also have cell broadcasts of all types turned off.
All of the above combinations respond the same way in regard to battery drain overnight. 7-9 hours off the charger/no screen time nets me 25-30% loss of battery from a full charge. msm_hsic shows up in BBS with 1.75 to 2.5 hours of wake time and is the highest power consumer. Putting the phone in flight mode reduces power consumption to ~2% over the same 7-9 hour timeframe. Just turning wifi off doesn't change anything.
Ideas anyone?
Calebz said:
A quick look through that thread shows that it is focused on problems relating to Google Services. Since the update, I too am having issues with the battery draining more quickly than it ever did before. However, it appears to be msm_hsic_host wakelock causing the problem. Google services are a very small part of my battery usage.
I have posted a couple times about it in various threads, but I haven't seen a fix that applies to 4.3.
The battery drain is out of hand. I love my N4, but this is a big turn off for me.
I have tried these configurations to make sure it wasn't an oddball app causing the problem -
Stock 4.3 with stock Kernel - no root/stock recovery - Only apps being the ones that load on a factory reset
Wiped all partitions and reloaded stock 4.3/gapps/no root/stock recovery
Stock 4.3/rooted/TWRP/Stock gapps
Stock 4.3/rooted/TWRP/gapps+ a handful of other apps (photobucket/es file explorer/bbs - essentially, my normal config)
Added note - I also have cell broadcasts of all types turned off.
All of the above combinations respond the same way in regard to battery drain overnight. 7-9 hours off the charger/no screen time nets me 25-30% loss of battery from a full charge. msm_hsic shows up in BBS with 1.75 to 2.5 hours of wake time and is the highest power consumer. Putting the phone in flight mode reduces power consumption to ~2% over the same 7-9 hour timeframe. Just turning wifi off doesn't change anything.
Ideas anyone?
Click to expand...
Click to collapse
As far as I know, this wakelock is caused because of the usage of 3G, like browsing, syncing, or any other thing that consumes data. This drain for me is usually between 10%-15%. There is no way t completely get rid of it, because it is part of the Android system.
There are many kernels that tried to fix this, about stock image and JW branch I don´t know, but maybe you should try to install an AOSP variant, because AOSP has many bugs fixed.
Also I remember I read somewhere that also bad radio could be causing this kind of issues, so try to get latest radio/bootloader for 4.3.
Hope it helps.
:highfive:
Galaxo60 said:
As far as I know, this wakelock is caused because of the usage of 3G, like browsing, syncing, or any other thing that consumes data. This drain for me is usually between 10%-15%. There is no way t completely get rid of it, because it is part of the Android system.
There are many kernels that tried to fix this, about stock image and JW branch I don´t know, but maybe you should try to install an AOSP variant, because AOSP has many bugs fixed.
Also I remember I read somewhere that also bad radio could be causing this kind of issues, so try to get latest radio/bootloader for 4.3.
Hope it helps.
:highfive:
Click to expand...
Click to collapse
To avoid having loose ends out there (in case anyone finds this thread during a search) - The problem turned out to be the latest radio. Not my lack of it :lol:
After flashing back to the .48 radio, from the .84 radio - everything is back to normal. No more weird Android OS wakelocks. ~3-4% battery drain overnight instead of 20-30%
There are more and more people popping up on XDA with this problem. So far, all of them that I have seen are outside the US. A few have even discovered the same fix.
So - future person that finds this thread during a search, look into the possibility of flashing back to version .48 of the radio. Hopefully this saves someone the trouble of experimenting with a bunch of different ROMs and kernels.
Calebz said:
To avoid having loose ends out there (in case anyone finds this thread during a search) - The problem turned out to be the latest radio. Not my lack of it :lol:
After flashing back to the .48 radio, from the .84 radio - everything is back to normal. No more weird Android OS wakelocks. ~3-4% battery drain overnight instead of 20-30%
There are more and more people popping up on XDA with this problem. So far, all of them that I have seen are outside the US. A few have even discovered the same fix.
So - future person that finds this thread during a search, look into the possibility of flashing back to version .48 of the radio. Hopefully this saves someone the trouble of experimenting with a bunch of different ROMs and kernels.
Click to expand...
Click to collapse
I put your post into my thread for people looking for an answer to this wakelock. Hope you don´t mind. Credits to you are there.
http://forum.xda-developers.com/showthread.php?p=44122105
:fingers-crossed:
Hi, I have installed Quarx's awesome 4.4.2 kitkat build and I am very impressed with its performance so far. I read up on the recent comments saying that the build from 6-11 is pretty stable and I believe it's true. I'm also running the 2.6 kernel along with the aerokernel app by blechd0se.
as you can see from the attached screen shot, my defy isn't entering deep sleep... I've frozen a lot of unnecessary apps and turned airplane mode on while leaving the defy alone for some time but it's still draining really fast. there is no deep sleep happening.
does anybody know how I can improve this phone?
thanks!
UPDATE: It seems I fixed my own issue by looking into every running app that looked like they were trying to collect data or keep the defy awake. from there I stopped/unchecked the services and then rebooted into recovery to wipe dalvic/cache, fixed permissions
only until then did it start deep sleep! hope this helps others as well