Related
Hey,
I'm running stock nexus 4. I have been having terrible 8 hour battery life with "Android OS" taking up all the battery in battery status. BetterBatteryStats tells me that "sns_perioidic_wakelock" and "sns_async_ev_wakelock" is using up most of the battery. See attached. Any idea what apps are causing this?
http://i.imgur.com/t1gAr.png
thegreyspot said:
Hey,
I'm running stock nexus 4. I have been having terrible 8 hour battery life with "Android OS" taking up all the battery in battery status. BetterBatteryStats tells me that "sns_perioidic_wakelock" and "sns_async_ev_wakelock" is using up most of the battery. See attached. Any idea what apps are causing this?
Click to expand...
Click to collapse
I'm pretty sure I've seen those wakelocks when making a lot of phone calls. Seems likely related to cell radio use some how, but that's just a guess.
mattb3 said:
I'm pretty sure I've seen those wakelocks when making a lot of phone calls. Seems likely related to cell radio use some how, but that's just a guess.
Click to expand...
Click to collapse
Actually the crazy thing is that i have airplane mode with wifi on most of the day cause I have really bad service. And I only have 100 minutes of talk, so I never talk on the phone.
thegreyspot said:
Actually the crazy thing is that i have airplane mode with wifi on most of the day cause I have really bad service. And I only have 100 minutes of talk, so I never talk on the phone.
Click to expand...
Click to collapse
Just checked mine and those wakelocks are really low today despite several phone calls, I've been on wifi all day though. The right way to figure those wakelocks out is to download the kernel source from one of the devs github and do some searches through the source to see where those wakelocks are logged. You might also search the battery impression thread in general, some smart folks have dissected many kernel wakelocks in there. Seems weird that you would have them in airplane mode.
thegreyspot said:
Actually the crazy thing is that i have airplane mode with wifi on most of the day cause I have really bad service. And I only have 100 minutes of talk, so I never talk on the phone.
Click to expand...
Click to collapse
I have the exact same issue. Wakelocks/Android OS killing my battery (Android OS usually 45% or higher when it should be my screen that is the biggest battery sucker).
I barely use my phone to make phone calls as well. I'd say 1 call every 2 or 3 days.
Same exact wakelocks here. I made 0 phone calls. There is defiantly something up.
I had these two wakelocks too and it turned out to be my live wallpaper that was causing it
http://forum.xda-developers.com/showpost.php?p=35277041&postcount=20
Same wakelocks on my N4....
Solution in my case, delete widget locker....... My Nexy sleeps again:angel:
exact same situation: N4, sns wakelocks killing battery, phone not deep sleeping. culprit? Shake 'n Rotate! app. so add that one to the blacklist as well!
Are any of you running stock kernel and ROM?
Sent from my Nexus 7 using Tapatalk 2
Im Running stock kernal and Rom and i still get sns_periodic_wakelock and sns_async_ev_wakelock Does anyone have any idea what they are or what causes them or how to fix? They seem to be on the whole time my phone is on and they suck battery crazy not as bad as most but my android os is always 2nd battery use to my screen or more depending on how i use it and it sucks cause i know i would have pretty awesome battery life if these were fixed or gone. I appreciate any help!
Apparently you can also add: lightflow vibrate on pickup feature and adding a widget to the lock screen..
PowerManagerService and sns periodic wakelock are my main culprits but I'm not sure these numbers mean there's an issue or not...
I just checked BBS for todays use and I have on 9h use 4h on sns_periodic_wakelock. I have been using DashClock on my lockscreen. I will remove that and post back later to see if that helped.:cyclops:
Hmm can anyone say if this looks problematic?
Sent from my Nexus 4 using xda premium
Yes it does look problematic.
Basically sns_periodic_wakelock kept the device from sleeping for almost three hours.
I have the same issue and don't know what's causing it.
EDIT: Apparently live wallpapers do.
Just writing back to tell you guys how it went. I removed DashClock from my lockscreen and that wakelock seemed to be gone for a few days.
I then later updated the app, and just by updating it, I think it caused the wakelock. This time I'm uninstalling and checking if it comes back again.
Is there a known list of apps suspected of causing this?
dohkoxar said:
Just writing back to tell you guys how it went. I removed DashClock from my lockscreen and that wakelock seemed to be gone for a few days.
I then later updated the app, and just by updating it, I think it caused the wakelock. This time I'm uninstalling and checking if it comes back again.
Click to expand...
Click to collapse
I've had dashclock for the past two days.. Not seeing any wake locks. I have all the extensions from the app enabled.
Sns is related to facebook. If you use Titanium backup, go to apps and you can see a blue icon with a letter f on it that looks like facebook letter and labelled sns. Uninstall that and your lovely nexus 4 will enjoy its sleeeeep....
Edit: The 4.2.2 update seems like it fixed this wakelock from taking over. That's just my personal experience so let me know if yours is different from mine after the update.
I've searched and tried to find a solution to my problem, but I can't find anything. My main kernel wakelocks are sns_async_ev_wakelock and sns_periodic_wakelock and the time they both register is massive. This has been happening for at least a week, or at pretty much the entire time I started monitoring my wakelocks. Does anyone have any idea what these might be attached to? I originally thought they were pertaining to social networking services, so I promptly deleted the Facebook app and for a day it seemed to fix it. But then the wakelocks came back and were even worse.
Have others come across this problem and does anyone know what might be causing it? They've been preventing my phone from going into deep sleep and I would really like to reduce or get rid of them.
Updated info: I have determined that the game Asphalt 7 is at least one app responsible for massive sns wakelocks. As long as the game remains as a "recent app" it will continue to wake the phone up. Angry birds is another game possibly responsible for the wakelock as well as reddit sync. Anyone else that uses these apps regularly us encouraged to report back your findings. Using the phone prompts sns wakelocks, but the amount of time the phone contributes is identical to your talk time, so your phone is triggering a fake wakelock since the device isn't supposed to be in deep sleep while you're on the phone anyways. Right now the only fix I know of for the listed apps is to manually clear them from "recent apps".
Please include the rom and kernel you're using. So far it seems like a new kernel doesn't actually fix the problem when you're on the stock rom. So anyone on CM or PA, do you have this wakelock after having a game like asphalt 7 or angry birds sit in recent apps?
Have you tried a custom kernel like Franco's ? Might be the Qualcomm fixes.
madd0g said:
Have you tried a custom kernel like Franco's ? Might be the Qualcomm fixes.
Click to expand...
Click to collapse
Well I'm getting this on Franco's. I think it has something to do with the phone. [ I mean talking/calling on phone]
@OP,
Do you get this only when you call someone or get a call. In bbs, try a custom ref. setting and monitor for 1 hour where you were not getting/calling anyone and see if it is going down drastically. Also is the msm_hsic wakelock present for you a lot? [The custom kernels like franco, faux and others have fix for this, taken from patch commits done by qualcomm]
What were you doing with your phone in that time, were you making calls, texting, etc?
Sent from my Nexus 4 using xda premium
madd0g said:
Have you tried a custom kernel like Franco's ? Might be the Qualcomm fixes.
Click to expand...
Click to collapse
Currently full stock. And it looks like it's still present even with Franco's kernel
Hrithan2020 said:
Well I'm getting this on Franco's. I think it has something to do with the phone. [ I mean talking/calling on phone]
@OP,
Do you get this only when you call someone or get a call. In bbs, try a custom ref. setting and monitor for 1 hour where you were not getting/calling anyone and see if it is going down drastically. Also is the msm_hsic wakelock present for you a lot? [The custom kernels like franco, faux and others have fix for this, taken from patch commits done by qualcomm]
Click to expand...
Click to collapse
I talk on the phone for maybe an hour every day, so I would be surprised if it was associated with the phone since the wakelock time has been increasing this whole week while my phone time is relatively constant. Although I'm just taking the phone off the charger now and won't use it for calls for the next 2 hours, so I'll report back with what kind of wakelocks I'm getting as well was the apps I've used. As for msm_hsic_host wakelock, it is present but not as prevalent as the sns wakelocks. As you can see from the first picture I'm only getting about 20 minutes for that wakelock compared to the 4 hours of the others. If I remember correctly I ended the day with almost 5 hours for both sns and then an hour and a half for msm_hsic. So sns slowed down a bit and msm_hsic ramped up, but it didn't come close to overtaking sns
steviewevie said:
What were you doing with your phone in that time, were you making calls, texting, etc?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I was using it pretty normally. Had around an hour of talk time (cumulative over the day), texting throughout the day, streaming pandora for a little, checking emails, playing a game for a bit, and on sites like xda, reddit (through apps), and facebook (through chrome).
So far I haven't had any sns wakelocks today (well, nothing compared to what I recently had). The hisc wakelock is dominating now which seems more "normal". I only talked on the phone for a grand total of 3 minutes today so maybe that has something to do with sns. Currently charging it so I'll start getting new stats (the ones I'm posting now were taken a few hours ago), but this time I'll try to use the phone more as well as keep everything else the same. My use today has been streaming pandora, checking emails, reddit, xda, facebook, but no games (maybe that also comes into play). I'll keep updating
I'm getting massive sns kernel wakelocks too. No phone calls.
Xylon + Franco r30
Sent from my Nexus 4 using Tapatalk 2
edgeball said:
I'm getting massive sns kernel wakelocks too. No phone calls.
Xylon + Franco r30
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Hmm, yesterday I started getting sns wakelocks after I was on the phone for a while, so that might be part of it. Of course there might have been another reason behind it if you get a lot of wakelocks without the phone. Forgot to get a screenshot
This is the first day since I've been monitoring that this wakelock just went berserk. I made zero calls today. Then, I went back in time to determine what I was doing when it started. At that time, I was using Reddit Sync. Before doing anything, I locked the screen, and a few minutes later checked BBS and determined that the wakelock was still active after locking the screen. Then, I closed Reddit Sync and locked the screen. After a few minutes, I unlocked the screen and checked BBS. Sure enough, the wakelock times had frozen. So, by simply closing Reddit Sync, this wakelock has stopped, at least for now. After restarting this app, locking the screen and unlocking after a few minutes, I notice that the wakelocks were not re-activated. Well, that's my story. Do any of you use this app too?
floepie said:
This is the first day since I've been monitoring that this wakelock just went berserk. I made zero calls today. Then, I went back in time to determine what I was doing when it started. At that time, I was using Reddit Sync. Before doing anything, I locked the screen, and a few minutes later checked BBS and determined that the wakelock was still active after locking the screen. Then, I closed Reddit Sync and locked the screen. After a few minutes, I unlocked the screen and checked BBS. Sure enough, the wakelock times had frozen. So, by simply closing Reddit Sync, this wakelock has stopped, at least for now. After restarting this app, locking the screen and unlocking after a few minutes, I notice that the wakelocks were not re-activated. Well, that's my story. Do any of you use this app too?
Click to expand...
Click to collapse
No, I never used Reddit sync. However, it could be related to a general sync problem
Sent from my Nexus 4 using Tapatalk 2
edgeball said:
No, I never used Reddit sync. However, it could be related to a general sync problem
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Ha. It's not a sync program whatsoever, not in the sense that it syncs anything to the contents of your phone. It does sync in the sense that it keeps track of your "read" articles.
floepie said:
This is the first day since I've been monitoring that this wakelock just went berserk. I made zero calls today. Then, I went back in time to determine what I was doing when it started. At that time, I was using Reddit Sync. Before doing anything, I locked the screen, and a few minutes later checked BBS and determined that the wakelock was still active after locking the screen. Then, I closed Reddit Sync and locked the screen. After a few minutes, I unlocked the screen and checked BBS. Sure enough, the wakelock times had frozen. So, by simply closing Reddit Sync, this wakelock has stopped, at least for now. After restarting this app, locking the screen and unlocking after a few minutes, I notice that the wakelocks were not re-activated. Well, that's my story. Do any of you use this app too?
Click to expand...
Click to collapse
I only use Reddit News. My sns wakelocks for today match the time I was on the phone, almost identically. This has been the case for today and yesterday which leads me to believe that the phone calls are NOT responsible for this runaway wakelock (as others have been saying). I didn't use my Nexus 4 very much this weekend, and the two major functions I used it for were phone calls and checking email sporadically. Others seem to report substantial wakelocks even without calls, so this has to be attributed to some app or setting that we're missing. Although I'm more inclined to think it's a problem with an app (or apps) because limited use seems to result in limited wakelocks, and if it was a system setting then it would be fairly constant. Has anyone gotten low sns wakelocks after not using their phone much in a day (like not using very many apps)? And thanks for the input so far
Async could stand for asynchronous, the CPU functions asynchronously but, I have no clue whether that wake lock is really cpu related.
Sent from my Nexus 4 using xda app-developers app
Ace42 said:
Async could stand for asynchronous, the CPU functions asynchronously but, I have no clue whether that wake lock is really cpu related.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I think it might be but I'm not completely sure.I found out last night that the game Asphalt 7 was responsible for a couple hours of wakelocks. However, in the system battery stats it registered as 0s for keeping the phone awake while android os registered the 2 hour jump I saw after playing the game. I played for a few minutes and jumped back to the home screen and didn't touch the game for those 2 hours. I'm not sure why, but having the game in my recent apps triggered those wakelocks, and the second I swiped it out of recent apps the wakelocks stopped. Either the app is bad or maybe the system isn't handling it correctly. I'll be trying other apps to see what the results are.
Sent from my Nexus 4 using xda app-developers app
I use redditsync and also had a 7hour snsw wake lock overnight... Gonna keep an eye on it and hope it was a one off (or an update gets pushed out)
cyberkid2002 said:
I use redditsync and also had a 7hour snsw wake lock overnight... Gonna keep an eye on it and hope it was a one off (or an update gets pushed out)
Click to expand...
Click to collapse
Alright, so that's two people getting wakelocks from redditsync. What happens when you clear redditsync from your recent apps? Does the wakelock continue or does it stop? This definitely sounds like the system isn't handling some of the open/recent apps correctly. No idea what links these apps together though
I am using Franco 62 with stock ROM and it turns out that Angry Birds Seasons can cause these wakelocks as well. Glad I'm not the only one with this issue.
I have never had these wakelocks previously (only the famous msm_hsic_wakelock). Yesterday after I installed a couple of apps (most are just theme-ing apps with no sync) and flashed custom kernel (Franco.r53); and ever since then these two wakelocks are continously appearing in my BBS stats, almost preventing my phone from entering deep sleep AT ALL. So I thought it was the kernel's problem; flashed back stock kernel and the problem still persists.
It's really weird as I previously NEVER had these two wakelocks.
By the way, I'm on stock ROM (rooted, unlocked)
chy1991 said:
I have never had these wakelocks previously (only the famous msm_hsic_wakelock). Yesterday after I installed a couple of apps (most are just theme-ing apps with no sync) and flashed custom kernel (Franco.r53); and ever since then these two wakelocks are continously appearing in my BBS stats, almost preventing my phone from entering deep sleep AT ALL. So I thought it was the kernel's problem; flashed back stock kernel and the problem still persists.
It's really weird as I previously NEVER had these two wakelocks.
Click to expand...
Click to collapse
Thanks for the update. But, it begs the question as to whether you uninstalled the new apps one by one to hone in on a possible culprit?
floepie said:
Thanks for the update. But, it begs the question as to whether you uninstalled the new apps one by one to hone in on a possible culprit?
Click to expand...
Click to collapse
I'm suspecting something else, will update if it's solved.
UPDATE:
This is really weird, I have uninstalled what I installed yesterday and the problem persists, so I decided to try something else (as it was the another differences factor compared to pre-problem).
My WiFi was disconnected in middle of the night and I thought it could be causing it.
I turned my WiFi off, turn it back on and the problem is gone. This is really weird, as I have rebooted many times prior to trying this solution (and even flashed back to Stock Kernel).
Really random or just plain unlucky? I have even reinstalled the apps that I thought are causing the problem, but still fine so far. Gotta leave it overnight again to judge.
My Android OS is showing a stay always time of over 17 hours (out of a 20 hour run time where my battery is completely depleted). Is there anyway I can find out what cause it?
I am already on 4.2.2
elty123 said:
My Android OS is showing a stay always time of over 17 hours (out of a 20 hour run time where my battery is completely depleted). Is there anyway I can find out what cause it?
I am already on 4.2.2
Click to expand...
Click to collapse
Android os = apps . Facebook maybe ?
You're experiencing wakelocks. Might wanna do some research on the forum so that you can post logs for people to analyze what's really eating your battery.
Sfkn2 said:
You're experiencing wakelocks. Might wanna do some research on the forum so that you can post logs for people to analyze what's really eating your battery.
Click to expand...
Click to collapse
THIS. I was having problems with wakelocks and traced them back to these few things below which got my battery life to greatly increase once disabled.
1) using dashclock extensions like FB and gmail
2) leaving google sync on in settings for the various google services
3) corporate email exchange servers
4) setting a long time variable for the phone to lock after the screen turns off (i did this to prevent putting in a pin to unlock but it kept the phone awake after the screen turned off)
5) live wall papers
There is also a known issue in the stock kernel that causes the phone to stay awake when it is supposed to go into sleep mode during extended periods of inactivity. This can be solved by using a custom kernel just as Franco r90 which has implemented patches in order to allow the phone to go into sleep to preserve battery. It is expected to be fixed in the next official OTA from google although this was also expected to be in 4.2.2 and was not fixed fully.
Same issue here. 4.2.2 stock kernel+rom, rooted
BBS shows "suspend_backoff" is at 45% no idea what's causing that.
Disabled pretty much all of the sync services but no improvement.
Interestingly right after the 4.2.2 update, the battery life was good.
Download this app and it will keep your applications from running in the background.
https://play.google.com/store/apps/...GwsMSwxLDMsImNvbS5vYXNpc2ZlbmcuZ3JlZW5pZnkiXQ..
Here's the forum for the application.
http://forum.xda-developers.com/showthread.php?t=2155737
scream4cheese said:
Download this app and it will keep your applications from running in the background.
https://play.google.com/store/apps/...GwsMSwxLDMsImNvbS5vYXNpc2ZlbmcuZ3JlZW5pZnkiXQ..
Here's the forum for the application.
http://forum.xda-developers.com/showthread.php?t=2155737
Click to expand...
Click to collapse
So far so good! totally eliminated the suspend_backoff wakeup
akiv said:
So far so good! totally eliminated the suspend_backoff wakeup
Click to expand...
Click to collapse
Update: Worked for a day now suspend_backoff is back. Happened after a recharge.
Could it be that afther the phone is charged something gets changed.
Edit: Runnig franco r90 kernel
I'm having the same problem with the Android OS draining lots of battery. When I reboot it sometimes helps but not consistently unfortunately.
Jester23 said:
I'm having the same problem with the Android OS draining lots of battery. When I reboot it sometimes helps but not consistently unfortunately.
Click to expand...
Click to collapse
I have narrowed my problem down to places where I use wifi transmitted by a lot of routers (Office wifi)
akiv said:
I have narrowed my problem down to places where I use wifi transmitted by a lot of routers (Office wifi)
Click to expand...
Click to collapse
I turn off my wifi when not home so I don't think that's the issue here.. I've tried removing a few apps like dash clock and my live wallpaper to see if it helps my issue. Will report back.
Sent from my Nexus 4 using Tapatalk 2
Google play services has something to do with the high usage. Yesterday I was near 20% usage today I disabled it and android os is at 7%. It only affects YouTube app for me, but the browser version is fine. I haven't seen any adverse affects other than maybe losing updates to the play store and ota updates which I don't care about because that's what xda and Roms are for. Now it may be placebo, but it also seems like the ui is smoother. Battery has improved greatly with sot of 3 hours with 57% left.
Hi,
how do you disable Google play services?
Try using the app greenify if your rooted.. It's been helping my battery life. Use it on maps and that will help. If maps is set as a system app, move it or just install banks minimal gapps so you can download from play store.
Sent from my Nexus 4 using xda app-developers app
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.
Hi everyone. I managed to get my hands on a beautiful blue I9505, had some issues while SIM unlocking it, but that's done and I am enjoying the phone very much.
Now, I do have a problem with it. The thing is, it simply will NOT go to deep sleep. Constantly hovering on 384 MHz with msm_hsic_host using a massive 90+ percent of awake time. It is driving me nuts. Our colleagues and friends over at Nexus 4 forums had an identical issue, and I read 57 pages of posts and used all their tips and tricks. Nothing helped.
Attached to this post you can see:
- the original Nexus 4 forum topic - [Q] msm_hsic_host - Nexus 4 forums
- The Google Code page where people complained about this - Google Code - Issue 41855 - "msm_hsic_wakelock" process on Nexus 4 causes severe battery drain
- my battery usage and BBS stats - attached to this post
- Qualcomm's fix for the issue - link 1 and link 2 at Code Aurora
I can't make heads or tails of any of this. The only thing that remains to do today (which I will do) is to flash a custom ROM and kernel for my I9505.
Thanks to anyone who will chime in to this discussion.
Bump - nobody else has this problem? Can you at least share your configurations so I can experiment a bit?
robogo1982 said:
Bump - nobody else has this problem? Can you at least share your configurations so I can experiment a bit?
Click to expand...
Click to collapse
99% chance that some app you installed is causing the wakelock. Install BetterBatteryStatts to determine wich app causes deep sleep/wakelock issues.
gee2012 said:
99% chance that some app you installed is causing the wakelock. Install BetterBatteryStatts to determine wich app causes deep sleep/wakelock issues.
Click to expand...
Click to collapse
I do have BBS as can be seen on the screenshots. I can't find the culprit since I believe it's the system itself.
I had this problem and it turned out to be avg pro app keeping it awake
Sent from my GT-I9505 using xda app-developers app
steveharris87 said:
I had this problem and it turned out to be avg pro app keeping it awake
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I don't have such an app. Wakelock detector reports no odd stuff.
robogo1982 said:
I don't have such an app. Wakelock detector reports no odd stuff.
Click to expand...
Click to collapse
Wakelock couldnt find anything on mine either I just had a feeling it was that app so I removed it and it started going in to deepsleep I also had a problem with maps keeping my phone awake.
Sent from my GT-I9505 using xda app-developers app
robogo1982 said:
I don't have such an app. Wakelock detector reports no odd stuff.
Click to expand...
Click to collapse
clear dalvik cache and see again if it does enter Deep sleep or not, as everyone said its an application if not it must be a setting like sync, scan, or even that damn old wifi advanced settings that kept usual phones awake... reconfigure.
Insomnia
My phone won't sleep, won't time out and tapping the power button won't shut off the display. This happened just after deleting bootsamsung.qng, samsungloop.qng and shutdown.qng.
I'd replace the three deleted files, but they just grew and replaced themselves minus the carrier logo. The Baseband version now says: unknown. I stopped and installed google maps, that didn't help.
The good news is, those pink blocks are gone. The bad, I did a factory reset and noticed my cell network connectivity is gone. Maybe that's the sloppy work cutting down the SIM, or maybe something else? I've reinserted that sucker a dozen times and no joy. Do you know if the phone will stay awake without cell service? Putting it in airplane mode doesn't help.
Any suggestions? Thanks for your consideration.
Build number: JDQ39.I9505XXUAMDC
REVERSiN said:
clear dalvik cache and see again if it does enter Deep sleep or not, as everyone said its an application if not it must be a setting like sync, scan, or even that damn old wifi advanced settings that kept usual phones awake... reconfigure.
Click to expand...
Click to collapse
Cleared Dalvik, will keep an eye out (though I don't know how can it help)...
Wiping Dalvik did not help. I will try a factory reset later this afternoon and let the phone be for an hour or so without any apps installed.
robogo1982 said:
Wiping Dalvik did not help. I will try a factory reset later this afternoon and let the phone be for an hour or so without any apps installed.
Click to expand...
Click to collapse
Same problem here, my msm_hsic_host accounts for ~99% of the wakelocks according to BBS, even when the phone is in airplane mode and Wifi is off.
I'm running stock MDC firmware & kernel, rooted though.
fizzefazze said:
Same problem here, my msm_hsic_host accounts for ~99% of the wakelocks according to BBS, even when the phone is in airplane mode and Wifi is off.
I'm running stock MDC firmware & kernel, rooted though.
Click to expand...
Click to collapse
Read this about the wakelock, has to do with bad/lower 3g connections:
http://www.google.nl/url?sa=t&rct=j...3jjunrjohBvz3zaNvrYSO5g&bvm=bv.46751780,d.d2k
Thanks for the link.
This seems to be a logical explanation, but I've disabled 3G, and it still happens.
Plus it happens when in airplane mode, without any (cell) activity. I'm pretty sure that the kernel isn't configured properly.
Is there a known kernel / stock firmware version where this problem is fixed?
It appears that I have solved my problem.
I reset the device to factory settings and then restored apps, 5 by 5 in 30 min intervals. I still haven't restored all my apps, but so far I restored some 80%, here is the current state of things.
Very interesting.
Please keep us posted once you find out which app caused the problems, or if the factory reset fixed it.
Did you freeze or uninstall any apps?
Did you remove the T-Mobile bloatware?
fizzefazze said:
Very interesting.
Please keep us posted once you find out which app caused the problems, or if the factory reset fixed it.
Did you freeze or uninstall any apps?
Did you remove the T-Mobile bloatware?
Click to expand...
Click to collapse
I froze the same apps I had frozen before. If I find the app that caused the problems, I will report back. So far it's all good, 6h of use and I'm at 87% battery, wifi and 3G always on
P.S. I have Wanam's 1.0 installed
EDIT: 22h30 min, 2h4min screen on time, 48% battery.
I'd say that's an okay result.
robogo1982 said:
I froze the same apps I had frozen before. If I find the app that caused the problems, I will report back. So far it's all good, 6h of use and I'm at 87% battery, wifi and 3G always on
P.S. I have Wanam's 1.0 installed
EDIT: 22h30 min, 2h4min screen on time, 48% battery.
I'd say that's an okay result.
Click to expand...
Click to collapse
What app was the problem?
I have a problem with this wakelock, use about 10-25% of battery time
Napalm Candy said:
What app was the problem?
I have a problem with this wakelock, use about 10-25% of battery time
Click to expand...
Click to collapse
You know what, I can't really say. Since the factory reset I restored all my apps and never had the problem since. Really weird issue. 25% can be bad. I had 99.4%
robogo1982 said:
You know what, I can't really say. Since the factory reset I restored all my apps and never had the problem since. Really weird issue. 25% can be bad. I had 99.4%
Click to expand...
Click to collapse
So, if I give you my app list, can you identificate what you used before wipe?
Maybe can will know what apps are potentially to reproduce the problem