Related
I installed Spare Parts and saw that my phone was never sleeping, even though it was on standby all the time.
This was caused by the location by antenna feature.
Ever since i unchecked that feature i've had around 50-60 hours of uptime, with a few calls and a lot of texts.
hope this helps alot others
With the new firmware the problem of battery dissapears completely
There is a known issue with network location detection in android 1.6. I had the same issue with my galaxy and it was solved. Now that we have root, we can hopefully do the same.
Also, br aware that I have found spare parts to actually stop the phone from sleeping, as well as tapatalk. I suggest rebooting after using either program.
-------------------------------------
Sent via the XDA Tapatalk App
adrianoftyriel said:
There is a known issue with network location detection in android 1.6. I had the same issue with my galaxy and it was solved. Now that we have root, we can hopefully do the same.
Also, br aware that I have found spare parts to actually stop the phone from sleeping, as well as tapatalk. I suggest rebooting after using either program.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Actually that issue is fixed in the latest update so it's already fixed without needing root.
Which firmware? I know I'm still experiencing it.
RBA020 solved the battery issues for me.
Where in spare parts does it show you if your phone has been sleeping?
you don't need spare parts. Just dial *#*#4636#*#* and click battery history and then the running bar.
Sent from my X10a using XDA App
Inebriatef said:
This was caused by the location by antenna feature.
Click to expand...
Click to collapse
I hope this means that under Location, you had Wireless Networks and Assisted GPS enabled.
One question tho... how did you isolate this feature as the one that was keeping the system awake?
I just found that my phone has been running most of the time, I see Running at 100% under Battery History. Then I select Partial Wake usage and see Android System has the largest share. But what part of Android System? how does one get to know?
I know from having a Samsung galaxy and being part of the androidforums community that was going nuts until Simone found a bug report with Google saying that network location was stopping devices from sleeping. We had root so a Dev applied a patch to services.odex and voila! Phones were napping again.
Sent from my X10a using XDA App
adrianoftyriel said:
I know from having a Samsung galaxy and being part of the androidforums community that was going nuts until Simone found a bug report with Google saying that network location was stopping devices from sleeping. We had root so a Dev applied a patch to services.odex and voila! Phones were napping again.
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Hmm... time to give this a try... so is it just Wireless Network or also AGPS that causes this problem?
I hope I can still leave GPS turned on?
EDIT:
adrianoftyriel said:
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Didn't know that there was an XDA App till I saw your sig. Looks like its worth a try since its free!!
Update after turning location off completely
Well first run with all location methods disabled (I can still enable GPS quickly via a widget when I need to use it)... the battery performance is up phenomenally!!
I charged fully before going to bed last night, then kept the phone unplugged... woke up and found the battery was at 97%. This has never happened to me.
Ok, one thing tho, I use Juice Defender with night time schedule, so my wifi and 3G were off during most of the night. Anyways, its been around 3 hours since I woke up, and I've been using the phone on and off to do some browsing.
The battery is now at 93%.
I do not use any other aid other than Juice Defender... no task killers, no startup editors. Will update on how the rest of the day progresses.
EDIT: my thanks to Inebriatef and adrianoftyriel for pointing this out.
j4mm3r said:
I hope this means that under Location, you had Wireless Networks and Assisted GPS enabled.
One question tho... how did you isolate this feature as the one that was keeping the system awake?
I just found that my phone has been running most of the time, I see Running at 100% under Battery History. Then I select Partial Wake usage and see Android System has the largest share. But what part of Android System? how does one get to know?
Click to expand...
Click to collapse
I too would like to hear a bit more. Could the OP please elaborate?
I'm running the latest FW and although my battery life increased exponentially, I find that it's not going to sleep anymore! I had close to 50 hours battery life and now I repeat everything to get just under 20 hours.
I don't use task killers and crap anymore, just before I put my phone away. If I don't, I have a trillion programs running with like 40mb of RAM free. Although I understand this is Linux based, these programs are RUNNING and not idle. All my **** is draining the battery again after a clean reinstall of everything. What a bummer.
bongd said:
I too would like to hear a bit more. Could the OP please elaborate?
I'm running the latest FW and although my battery life increased exponentially, I find that it's not going to sleep anymore! I had close to 50 hours battery life and now I repeat everything to get just under 20 hours.
I don't use task killers and crap anymore, just before I put my phone away. If I don't, I have a trillion programs running with like 40mb of RAM free. Although I understand this is Linux based, these programs are RUNNING and not idle. All my **** is draining the battery again after a clean reinstall of everything. What a bummer.
Click to expand...
Click to collapse
@bongd, by latest FW, do you mean the R2BA020? If yes, then you shouldn't be affected by the problem being reported here. I'm still on R1FB001, which apparently has this Android 1.6 bug related to location.
As in my case, simply by disabling location settings (even though this reports that network location is the culprit, I disabled them all), the phone is now able to suspend itself and basically consume very little battery in standby.
Personally, I dont see any issue with lot of applications running and having little RAM left because I trust the Android system to manage it efficiently. Furthermore, the RAM on these phones is not as fast as what you would see typically on desktop systems, so it actually helps having things around in memory rather than aggressively cleaning it out. Checkout this link to understand a bit more about Android task management features: http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
I suggest you use Spare Parts to isolate your battery drain, there might be some app that is misbehaving and hogging systems resources. Also turning off very frequent updates/refresh intervals in some applications is the way forward.
I found through trial and error that fancy widgets keeps my phone from sleeping.sad cause I really want to use it.
Sent from my X10a using XDA App
j4mm3r said:
@bongd, by latest FW, do you mean the R2BA020? If yes, then you shouldn't be affected by the problem being reported here. I'm still on R1FB001, which apparently has this Android 1.6 bug related to location.
As in my case, simply by disabling location settings (even though this reports that network location is the culprit, I disabled them all), the phone is now able to suspend itself and basically consume very little battery in standby.
Personally, I dont see any issue with lot of applications running and having little RAM left because I trust the Android system to manage it efficiently. Furthermore, the RAM on these phones is not as fast as what you would see typically on desktop systems, so it actually helps having things around in memory rather than aggressively cleaning it out. Checkout this link to understand a bit more about Android task management features: http://android-developers.blogspot.com/2010/04/multitasking-android-way.html
I suggest you use Spare Parts to isolate your battery drain, there might be some app that is misbehaving and hogging systems resources. Also turning off very frequent updates/refresh intervals in some applications is the way forward.
Click to expand...
Click to collapse
Thanks, j4mm3r. I am using R2BA020. It looks like I have some diagnostic troubleshooting to do when I get home.
Sitting here at work charging my phone, it isn't loading craploads of programs anymore. And it seems to be sleeping okay. I'll play around when I have some free time.
Fixed my problem big time
Hey guys,
I just wanted to throw my two cents into the pot.
OK – so after experimenting with Task Killers, Task Managers, Spare Parts, Juice Defender, etc. I came to the conclusion that they (for the most part) did more bad than good. It was getting to the point that I was just starting to accept that “The X10 just has ****ty battery life” end of story.
I also read in a Google released post on the web, that there are a number of reasons that Task Killers, etc. are actually not required to end tasks. Android actually has a fairly intelligent and systematic approach to killing tasks that are not being used. I haven’t used any sort of proprietary battery saver, task ender, startup cleaner, etc. and I’ve been having the best phone performance since I got the headset.
The time now (Eastern Standard) is 3:30pm on Monday. The last time I charged my phone was Saturday evening at 6pm, and currently I am showing 24% battery remaining. Let those numbers do the talking!
My settings are:
Wi-Fi always off unless I am going to be actively using it (browsing)
Using Phone info, I change WCDMA Preferred to GSM Only (enables 2g instead of 3g without disabling data altogether)
GPS always off
Screen settings, brightness, etc. I believe have a much smaller effect than people tend to believe. The SINGLE BIGGEST factors for me, and noticing this huge increase in battery life are:
Settings -> About Phone -> Software Update -> UNCHECK Automatic Search (this constantly searches the market, etc. for app updates and what not)
Cycle power immediately after charging. Once my phone completes its charge, I turn off and then on again.
I hope that some people can enjoy moderately extended battery life as I have. I am SO ecstatic to be at HOUR 43 and still at 20%+
Worth mentioning also that I am on Rogers (Canada) and have not received any updates, so this extended battery life is not a result of a firmware update.
How I Fixed My Batter Life Problem
My Incredible would run dead in about 4 hrs doing nothing. I finally dug into several "task killer" programs and found that about 20 - 30 apps were invisibily running in the background constantly. As soon as I permanently killed them, my battery life went to normal. I can now get about 2 days of normal use on 1 charge. Even a day of pretty heavy use will last almost all day.
So for me, it was all the new apps I installed when I first got the phone that were running in the background. The free "task killer" program was not showing them. I finally found the app called "System Panel." It was the ONLY app that would show me all the "invisible" apps that were still running invisibly in the background and let me kill them. Once I killed them with System Panel, they stayed dead and the free "task killer" program could auto-kill them from them on.
Not sure why the free programs could not see the rogue apps, but my battery life is GREAT now.
Inebriatef said:
I installed Spare Parts and saw that my phone was never sleeping, even though it was on standby all the time.
This was caused by the location by antenna feature.
Ever since i unchecked that feature i've had around 50-60 hours of uptime, with a few calls and a lot of texts.
hope this helps alot others
Click to expand...
Click to collapse
What do you mean caused by the location of the antenna feature?
Where is this option to uncheck this feature.
Thanks dear.
Vatis
I'm running R2BA023 and I am struggling to get a full day from the phone at the moment. It normally lasts around 12 hours and then its flat.
However, I ran the Telenor R2BA020 update and I manage to get a full day with ease.
I have just done a clean install of R2BA023 Generic UK "root" edtion and going to see how I get on. What I did notice before is that the phone was not returning to a idle state.
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....
Hi everyone. So I've scoured the web high and low for some help on this topic, and so far I've gotten some scattered information, but not a lot of concrete solutions.
I'm having bad idle battery drain problems on my un-rooted, stock Verizon N9000V (MJE). Using BetterBatteryStats I've singled out bam_dmux_wakelock as the culprit. From what I've been able to find online, I guess this is a kernel level wakelock caused by something accessing cellular (not-wifi) data when the phone is asleep. I've pulled my hair out individually un-installing apps one at a time to see if I can pinpoint the culprit. I've also factory reset the phone and started from scratch, adding my apps one at a time, but due to the intermittent nature of this wakelock (it is not always present) I've had a whole bunch of false positives, thinking I'm safe only to have it pop up again the next day.
At it's worst, this wakelock is keeping my phone out of deep sleep around 50-75% of total battery time.
I do know that a thread exists on this topic over on the GSIII board, and I'm not trying to duplicate threads. I'm really just wondering whether any Note 3 users have experienced this patricular wakelock, and maybe what you've done to combat it on this particular phone. I've already tried some of the things others have suggested from other phones (disable Google+, disable Hangouts etc.) I'm really at my wit's end.
Thanks for your time and I appreciate any input.
This is also what is causing my rooted Note 3 to not go to deep sleep.
From previous xda threads, it looks like it is also present on the S3, maybe other phones too.
example:
http://forum.xda-developers.com/showthread.php?t=1811365
Maybe the solution is to just turn off Mobile Data when you are not using internet.
Just noticed yesterday that my battery life has been pretty poor on my new Nexus 6P. It took me a while to narrow it down, but I finally noticed that Bluetooth appears to be keeping the phone awake.
Whenever Bluetooth is on, regardless of whether it's connected or paired to anything (I normally use Android Wear, but I completely unpaired all bluetooth devices on the phone), "Android OS" in the battery info screen appears to be stuck awake. Its "Keep awake" time grows continuously as long as Bluetooth is turned on.
Has anyone else ran into this issue, and have any idea how to fix it? I really can't be leaving Bluetooth turned off, and the phone is not really going to make it through the day like this.
Yes it's been happening to me. I didn't know what was causing it until I saw your post. It seems to be a glitch with Marshmallow and not the phone itself. My Nexus 9 was also stuck awake until I turned off Bluetooth.
Sent from my Nexus 6P using Tapatalk
Hmm. Maybe that's why my battery drained so fast. I'll have to turn off Bluetooth and see if it makes any difference
Sent from my Nexus 6P using XDA Free mobile app
Have you disabled the bluetooth scanning under locations --> settings (the 3 dots) --> scanning.
You can also disable the wifi scanning in there too.
No, I have disabled Bluetooth scanning and it is still occurring. As long as Bluetooth is turned on, the device stays awake. There's something more serious at issue here.
That's disappointing if true. I use BT all the time and leave it on 24/7.
Aw man, bummer hearing that as I keep my Bluetooth on all the time, and am waiting on my 6P. I actually had this same issue on my Note 4 a week ago, but I was able to narrow it down to a 3rd party app called "Gas Buddy" by using Greenify and CPU Spy. And this only happened whenever Bluetooth was enabled.
I know you said Android OS looks to be the culprit, but if you happen to have this app, try uninstalling it (or blocking Bluetooth permissions for the app). Otherwise, there might be another app pinging Bluetooth to keep the phone awake.
Sent from my SM-N910V using Tapatalk
I was seeing the same issue, if BT was on, there was a 100% bluesleep wakelock. Lots of searching later, turns out the Gasbuddy app was the culprit. I still don't understand why, but that was the problem for me.
B
I turned off BT and got significantly bettery battery life. I only use it when driving in my car so it's not a huge deal for me to have to turn it on/off, but there should be a fix for this.
Man, I'm glad I found this thread. It seems to be the only discussion about this issue on the entire internet! After two nights of 20%+ battery drain, and waking up to a completely dead phone one morning, I'll try turning off Bluetooth instead of returning the phone. Here's hoping for a fix soon. This is a pretty unacceptable problem.
Damn, sucks for those of us with smartwatches
10SE said:
Man, I'm glad I found this thread. It seems to be the only discussion about this issue on the entire internet! After two nights of 20%+ battery drain, and waking up to a completely dead phone one morning, I'll try turning off Bluetooth instead of returning the phone. Here's hoping for a fix soon. This is a pretty unacceptable problem.
Click to expand...
Click to collapse
Do you have gasbuddy app installed?
d1ez3 said:
Do you have gasbuddy app installed?
Click to expand...
Click to collapse
I don't.
i had just posted my (poor) battery life on the battery life thread, and then read this. I did have the gasbuddy app installed, and was keeping BT on 100% of the time. I have since removed the gasbuddy app, and disabled BT for now to see if makes a difference. Maybe its the placebo effect, but my drive from home to work seemed to have killed very little battery since i did this. Ill know better as the day progresses. While it would be annoying to know this is what is causing the wakelock, id just be happy knowing how to manage it until a fix is determined.
love you xda....thanks guy..i had the same issue and drained battery 20% overnight during 7 hours sleep. Crazy drain..... I had bluetooth and gasbuddy app.
So I disabled both and will keep you guys posted.
Thanks guys!
By the way / FWIW I've reported the correlation between GasBuddy and Bluetooth to the GasBuddy devs, and actually got a reply from them. They say they'll have it fixed in the app's next update.
Hello supertoast,
I have forwarded this feedback along to our development team for review to be fixed. They're aware of the problem and it should corrected in the near future. Thank you for bringing this to our attention.
Regards,
John
GasBuddy.com
Click to expand...
Click to collapse
Sent from my SM-N910V using Tapatalk
supertoast92 said:
By the way / FWIW I've reported the correlation between GasBuddy and Bluetooth to the GasBuddy devs, and actually got a reply from them. They say they'll have it fixed in the app's next update.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Nice to know. I also sent something to them as well.
Hopefully they fix it, it saves me money when finding cheapest gas...
Is there a way without root to determine what app may be wakelocking BT? I don't have GB installed and I get pretty bad battery life with BT on.
mgorman said:
Is there a way without root to determine what app may be wakelocking BT? I don't have GB installed and I get pretty bad battery life with BT on.
Click to expand...
Click to collapse
Well besides Gas Buddy, it seems that from the above posts that its a fundamental bluetooth issue in marshmallow. So it doesn't matter which app uses it.
It could be, but the GasBuddy correlation for my Note 4 was on 5.0.1. It may very well be some 3rd party app going rogue. That's from my experience though - it could be Marshmallow in general causing it, for all I know! Still waiting on my 6P to experience it. [emoji14]
Sent from my SM-N910V using Tapatalk
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.