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.
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....
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
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
I've noticed this phone has hit or miss battery life depending on what you have installed, greenified and frozen. I thought it would be a good idea to create a thread where everyone could share their battery life tips and tricks on this phone.
Below I posted what I have done to maximize battery life. I have not rooted my phone yet, so none of the below tips require root.
I disabled all bloatware apps that came with the phone. I did not disable any of the Asus applications.
I utilize the Asus autostart manger and denied auto start to all my applications except music applications, messenger applications, and google photo sync.
battery sucks. drain to much.
Just use until you have 5% free battery, this should make at least your day
With Android OS taking so much thanks to lollipop, there is not a lot to hope.
We wont see a good battery improvement until we get 5.1
Luckily, that is in the future for this device acc. to Asus.
Since the issue seems to primarily be Android os draining the battery I don't think most battery saving measures will make a difference. We will just have to wait for an update
When I was looking at the phone reviews people were claiming 8 hours screen on time, I can barely get 2 hours screen on time.
The problem I'm having is that the phone never goes to sleep and is constantly awake. Has anyone else seen this issue?
facelessloser said:
When I was looking at the phone reviews people were claiming 8 hours screen on time, I can barely get 2 hours screen on time.
The problem I'm having is that the phone never goes to sleep and is constantly awake. Has anyone else seen this issue?
Click to expand...
Click to collapse
I had the same problem after the latest update, no deepsleep in BetterBatteryStats (I'm rooted), I wiped everything and now it goes to deepsleep.
marcof93 said:
I had the same problem after the latest update, no deepsleep in BetterBatteryStats (I'm rooted), I wiped everything and now it goes to deepsleep.
Click to expand...
Click to collapse
Which firmware version are you on. I've wiped the phone once already, did you clear any caches? It's driving me mad
facelessloser said:
Which firmware version are you on. I've wiped the phone once already, did you clear any caches? It's driving me mad
Click to expand...
Click to collapse
I'm on 2.18.40.12 (ZE551ML of course), I restored the phone from backup & restore in settings (It may take 30 minutes or more). Before restoring I had 45+% of Android OS during the night, now 20% more or less, but, as said, also in BBS I can see deepsleep in frequencies.
Someone posted on Zentalk to turn off remote lock and scan for security threats in google settings. Not sure if it helps or not.
marcof93 said:
I'm on 2.18.40.12 (ZE551ML of course), I restored the phone from backup & restore in settings (It may take 30 minutes or more). Before restoring I had 45+% of Android OS during the night, now 20% more or less, but, as said, also in BBS I can see deepsleep in frequencies.
Click to expand...
Click to collapse
I wiped my phone yesterday and restored back up like you suggested and it seams to have sorted out my wake lock issue. I wonder why that is?
facelessloser said:
I wiped my phone yesterday and restored back up like you suggested and it seams to have sorted out my wake lock issue. I wonder why that is?
Click to expand...
Click to collapse
Glad you solved, but don't know why, maybe they are working hard on the firmware and there are lot of changes that can cause problem, maybe we have to wipe after every update, Intel processor and Lollipop are so unstable right now!
toebus said:
Someone posted on Zentalk to turn off remote lock and scan for security threats in google settings. Not sure if it helps or not.
Click to expand...
Click to collapse
It helps..i turned andriod device manager too
Ok so this is my battery with a normal day of use... Tomorrow ill show the results with your sugestions. My normal days have gsm calls(normal phone calls) whasapp (chat) youtube, twich, game like plant vs zombies 2, look at gmail, surfing internet, taking pics like 25 today.
I notice that battery drains a lot more while photo app open.
I use doble sim as you can see
If you want to test app battery drain, try GSAM Battery Monitor, or for some extra functionality the Pro version. Also very useful to determine what is causing wakelocks when you run into them.
Sammaul said:
If you want to test app battery drain, try GSAM Battery Monitor, or for some extra functionality the Pro version. Also very useful to determine what is causing wakelocks when you run into them.
Click to expand...
Click to collapse
Really interesting app ill download tomorrow im tring to lock some functionalities from google like sending data for app security and after that will download this and tell you what i got
Thank u sir thats a good one
Everyone is always wondering about Android using the most battery. Without doing some in depth debugging and tracing I would guess Houdini falls under Android. Because the ZenFone 2 uses the Intel processor a binary conversion for ARM instructions takes place with Houdini. More than likely you have a lot of apps native for ARM.
Force closing asus support app and zenui services app from apps setting gives me good amount of battery boost. Apart I have also disabled google books, movies, plus etc. I don't know if its placebo effect but someone can try and confirm. These app tend to restart at times so if you feel the battery decreasing at high rates again, make sure you force close them again.
Roughly speaking, I tend to get 3-5 min per percentage of screen on time with this which totals to 5 to 6 hrs on SOT on continous usage. Without the apps being force closed, I barely get 2min/%. The usage scenarios are normal web browsing, chats etc. This is using mobile data. It gets even better with wifi.
Try and let me know if this helps.
Maybe I don't use my phone as much as other people. I posted this last night on another forum. My phone was unplugged at 07:00, It's now 21:00. I have 80% battery left and the battery monitor shows 3 days left
I have received email, 3 phone calls and text messages. I checked Twitter a couple of times with the browser. I have read Google News a couple of times and played GSN Casino for about 20 minutes.
In Auto Start Manager I turned off Docs, Sheets, Skype, Slides, Translate, Amazon Kindle, Data Transfer and Web Storage. Everything else is Allow, but I have no social networking applications installed.
Its looks like battery life is a right mixed bag. At the start of the week I was suffering wake lock issue, my phone wouldn't go into deep sleep and was constantly awake. I wiped and restored from backup which seams to fix the issue.
Got up this morning and it looks like the wake lock issue is back. I don't know what to do to fix it.
Feel like giving up on the phone and sending it back if I can
So after updating facebook and messenger (facebook) I've found huge wakelocks in bbs. Anyone else having this issue? It's related to some kind of bug reporting?
======================================================
Wakelocks (requires root / system app on Android 4.4+)
======================================================
*job*/com.facebook.orca/com.facebook.bugreporter.scheduler.LollipopService (com.facebook.orca.Messenger): 37 m 20 s Count:10 22.2%
*job*/com.facebook.katana/com.facebook.bugreporter.scheduler.LollipopService (com.facebook.katana.Facebook): 30 m 2 s Count:6 17.8%
Same here........I'm locking it down using the Amplify Xposed module.
Prey521 said:
Same here!
Click to expand...
Click to collapse
It's causing massive wake time if left alone for a few hours. I went ahead and limited the wakelocks in amplify. Set it to allow them every 10th hour on trial. We'll see if that causes any problem.
I noticed this too. I watch battery like a hawk but this is the first time Facebook had shown much drain in the last few months. This was build still 59.0.0.3.313
Looks like tonight's build still has the issue.
I recommend reporting in the Facebook app itself.
Sent from my A0001 using Tapatalk
dmo580 said:
I noticed this too. I watch battery like a hawk but this is the first time Facebook had shown much drain in the last few months. This was build still 59.0.0.3.313
Looks like tonight's build still has the issue.
I recommend reporting in the Facebook app itself.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I've disabled them both in amplify. I don't feel I want battery every spent on uploading any form of reports. I've also limited facebook wakelocks apart from this to every 15th minute. It's spending too much battery on something irrelevant.
Reported it already.
Even my fiancee's Galaxy S5 (which can usually get through to the end of the day with 65+% battery left) was saying that her battery has been draining very quickly.
So I know Facebook in general gets a bad reputation, but as someone who watches wakelocks on a daily basis and the battery page, this is really the first instance of Facebook misbehaving in at least 2-3 years.
Anyway, is this something like you guys are seeing? https://imgur.com/a/rpO0j
The background drain isn't TOO Terrible. It's around ~2.5% / hour screen off on LTE (honestly that's what I got on a OnePlus One on Lollipop anyway), while the screen on drain was around 25% / hr
BTW, are you using Facebook/Messenger beta? I'm only in the Facebook beta program, so I don't see any issues for Messenger on my side yet.
are you using Facebook/Messenger beta?
Not using betas. I can't agree regarding facebook and battery life. It'd suppose to use cgm but still it had a heap of timers going off and the app is ever high in wakelock detector. I've had enough and now limited most of its alarms and wakelocks in amplify to no more often than every 15 mins. This has lowered facebooks position in the wakelock list to a much more acceptable level. No problems arise either apart from not getting notifications as expected but that's been a problem for years over multiple handsets.
I can even confirm it, the same wakelocks and drain have been appearing on my OnePlus One too.
I use amplify and prevent wakelocks to everything pertaining to Facebook to 86400s. That's once per day and haven't had any detrimental effects from the app. All still works as it should.
TigerSoul925 said:
Not using betas. I can't agree regarding facebook and battery life. It'd suppose to use cgm but still it had a heap of timers going off and the app is ever high in wakelock detector. I've had enough and now limited most of its alarms and wakelocks in amplify to no more often than every 15 mins. This has lowered facebooks position in the wakelock list to a much more acceptable level. No problems arise either apart from not getting notifications as expected but that's been a problem for years over multiple handsets.
Click to expand...
Click to collapse
What version of Facebook are you on?
BTW Facebook does use GCM. IT only uses MQTT when you are actively in the Messenger app. I'm not entirely certain what's going on here. The wakelock is com.facebook.bugreporter.scheduler.LollipopService so it seems to be bug reporting related and not notification related.
dmo580 said:
What version of Facebook are you on?
BTW Facebook does use GCM. IT only uses MQTT when you are actively in the Messenger app. I'm not entirely certain what's going on here. The wakelock is com.facebook.bugreporter.scheduler.LollipopService so it seems to be bug reporting related and not notification related.
Click to expand...
Click to collapse
Oh! Funny thing is, I've limited the mqtt stuff and I've had zero issues getting messages right away when screen is on or off in messenger but thanks to the mods facebook stuff is now farther down on the list of wakelocks rather than high. If those mqtts were only used when active, why use wakelocks for it at all? And why do they creep up in count when the screen is off? 60.0.0.2.76
Sent from my Nexus 6P using Tapatalk
TigerSoul925 said:
Oh! Funny thing is, I've limited the mqtt stuff and I've had zero issues getting messages right away when screen is on or off in messenger but thanks to the mods facebook stuff is now farther down on the list of wakelocks rather than high. If those mqtts were only used when active, why use wakelocks for it at all? And why do they creep up in count when the screen is off? 60.0.0.2.76
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
MQTT is only used when the app is in the foreground meaning its being actively used and screen on. Therefore it shouldn't cause wakelocks. I'm guessing MQTT is used because GCM can see delayed notifications sometimes. MQTT is probably better suited for real time chat.
What wakelock are you seeing? Is it the one I posted earlier? If so I'm not sure if that sure it has anything to do with the actual chatting and communication portion of the app. The wakelock has to do with a bugreporter, which is misbehaving when your screen is off.
I think I know the answer, but no way to help this without root right?
I can confirm, same problem on Nexus 5x (not rooted) latest version of Facebook... Updated this morning, caused wakelocks, uninstalled, problem solved. Shame I have to uninstall it to fix...
I have 60.0.0.5 now... Facebook simply minimizes itself automatically now. Anyone else seeing this behavior? I have greenify on Facebook as well as amplify to limit some wakelock. Might be the cause...
I am seeing this issue as well with com.facebook.bugreporter.scheduler.LollipopService causing massive drain.
I just have Messenger 53.0.0.17.308.
Since I do not want to install Xposed + Amplify to address the issue, is there a way to block this Job? I am digging into MyAndroidTools, but I can't find anything like that in Messenger services or Activities.
EDIT: According to BetterBatteryStats, it's a Service, but I can't find it.
EDIT2: By changing display mode in MyAdroidTools, I was able to find the service, the normal display name is Lollipop Service. However, if disabled, the app does not work properly, closes as soon it's opened.
same here guys!nexus 5 with cm13. huge wakelock with facebook and messenger. I tryed to greenify it but it doesn't work and after few minutes they come back again. I have to hybernate them with SDMaid app and it works well, but of course once hybernate i can't use them anymore until i dishybernate. Any solution?i don't use xposed..:crying:
Confirm this wakelock on 1+1 with CM 13.