Is anyone having issues with the new android wear app update and the it was causing a lot of wakelocks.
Lmfao
BACARDILIMON said:
Lmfao
Click to expand...
Click to collapse
just saying though!
I had tens of thousands of wakelocks under android wear under WLD.
Anyone have any input?
see this
http://forums.androidcentral.com/android-wear/440265-android-wear-phone-app-eating-battery.html
and this
https://productforums.google.com/fo...oter#!category-topic/android-wear/-1Crx26hm6k
My work IT says they didn't block port 53 or googles dns, but this is what's causing my battery to die , not sure what to do at this point besides sell the damn thing because it's useless to me if i cannot use it wherever i am
further research shows that freezing "google app" stops all android wear google dns rerouting . thus making it not work properly , causing wakelocks. will verify and confirm,
They took a page from samsung. That why watch in garbage
Related
hi everyone, recently i discovered huge battery drain on my note. when i fully charge it the battery drops from 100 to 80 percent in about 9 hours of standby. in order to find the culprit i installed better battery stats and let it run over night. i found out that something called networklocationlocator keeps my device from going into deep sleep (see attached screenshot).
does anyone know which app is behind this service? i think that its google now but i am not quite sure and dont want to uninstall it since its a really good app.
thanks in advance
Sent from my Note
probably when you go to settings and then location services, switch all off, switch back on only when you need it.
It would be interesting what is triggering your phone to seek location, could be a buggy app running silently updating every so often. I think the logs could tell you that. But not sure. I set location of in many apps in app settings cause I feel they dont need it.
I know that switching apps is buggy, It could be google maps running silently in background. Got to settings, apps running and stop those. Might need to stop as well in cached running.
I guess with root, and something like pdroid or lbe you can block apps requesting location services, also an option
Sent with a grin (^.^)
baz77 said:
probably when you go to settings and then location services, switch all off, switch back on only when you need it.
It would be interesting what is triggering your phone to seek location, could be a buggy app running silently updating every so often. I think the logs could tell you that. But not sure. I set location of in many apps in app settings cause I feel they dont need it.
I know that switching apps is buggy, It could be google maps running silently in background. Got to settings, apps running and stop those. Might need to stop as well in cached running.
I guess with root, and something like pdroid or lbe you can block apps requesting location services, also an option
Sent with a grin (^.^)
Click to expand...
Click to collapse
This is a 'bug' with google maps that has persisted for at least over a year now and it affects a lot of devices. Users have been complaining for the longest time and it seems like it's falling on deaf ears at google. It's a shame! There is NO acceptable 'fix' - turning off google locations services will get rid of this problem but again, as i said, that's not acceptable!
jknolls said:
This is a 'bug' with google maps that has persisted for at least over a year now and it affects a lot of devices. Users have been complaining for the longest time and it seems like it's falling on deaf ears at google. It's a shame! There is NO acceptable 'fix' - turning off google locations services will get rid of this problem but again, as i said, that's not acceptable!
Click to expand...
Click to collapse
I dont think its a bug affecting all roms. Nor that it has been there for over a year.
I really like the chromecast so far, but the android app is killing me (well my phone).
Ever since I installed the Chromecast app on my Galaxy S4 My battery life is horrible. When I look at the battery stats Chromcast is always the highest by far (even more than screen). It apparently doesn't matter if I force close it either. I tried reinstalling it and that didn't help either. Unfortunately I can't keep this on my phone! Is anyone else seeing this?
I'm seeing the same thing, but my drain is not coming from the Chromecast app, but rather from Google Services.
If you're rooted you could try Greenify from the Play store, it'll identify background apps(and their memory usage) and you can select & disable them until you actually start it.
Play store link:
http://goo.gl/LSsNw
Sent from my HTCONE using Tapatalk 4 Beta
Thanks, I will take a look at it.:good:
empirescrumble said:
I'm seeing the same thing, but my drain is not coming from the Chromecast app, but rather from Google Services.
Click to expand...
Click to collapse
Yea its been a problem on the S4, now I turn it off when I can
The app doesn't do anything aside from getting it initially setup to connect to your wifi.
Are you saying its automatically starting up the app even after you've killed it the first time?
hawkns said:
The app doesn't do anything aside from getting it initially setup to connect to your wifi.
Are you saying its automatically starting up the app even after you've killed it the first time?
Click to expand...
Click to collapse
Yes, it is very odd. The only other thing I can think of is that the battery status app (stock) is misreporting the app info and something else is killing my battery and chromecast app is being blamed ... I will try to dig around a bit more and see whats going on.
Thanks
My Nexus 6 is compeletely stock and untouched software. I have attached screenshots from Nexus 6 (5.0.1) and Note 3 (5.0) to show the point I'm talking about.
When I'm sleeping as you can see on the Note 3 it has very few awakes. But Nexus 6 on the other hand is almost always awake. It drains about 20-25% battery overnight.
I have performed factory reset 3 times and now it has almost no additional apps installed but still the same. (don't judge by the facebook on the screenshot it's just installed and the problem is the same with or without it) I'm not rooted so i can't use the wakelock detector. I've installed GSam and it shows Android OS and Android system as biggest drainers for the current situation (16%, 6%) which i suspect nothing extraordinary.
I have play services 6.7.76 on both devices if it has anything to do with it. I tried something like turning the ambient display off and some other settings to see if theyre waking it but no luck yet. Do you think it is a software thing and Google will eventually fix it and I should wait or what should i do?
I really want to keep this phone but the battery is a big concern for me right now. every morning seeing the battery down without touching the phone is a big problem. Any help and information on the subject is appreciated.
Edit: I have added a screenshot from safe mode. I restarted in safe mode to see if any 3rd party is the cause of the problem. But the problem persists. And I have noticed that when the wifi is compeletely off (Keep awake, Always scanning etc.) the problem is solved. But whenever i turn on the wifi, even when it is not connected to any network, it starts draining battery and keeping phone awake like on the graphics. Can anyone give me a hint if this can be a hardware related issue with the wifi receiver? Or it looks like a software issue and can be solved with the 5.1 update? I have 3 days to return the phone if its a hardware thing. Thanks
You should probably update to 5.1 and see if that helps.
biggiestuff said:
You should probably update to 5.1 and see if that helps.
Click to expand...
Click to collapse
Do you know if it is a common issue and 5.1 fixes it? I've checked the updates but nothing showed up so far. I'm close to 14 day window for my T-Mobile purchase so i need info on 5.1 about this issue and i didn't see anything related :/
HKNRN said:
Do you know if it is a common issue and 5.1 fixes it? I've checked the updates but nothing showed up so far. I'm close to 14 day window for my T-Mobile purchase so i need info on 5.1 about this issue and i didn't see anything related :/
Click to expand...
Click to collapse
You might have the sensor ind bug that was in 5.01 that kept the phone from sleeping properly. From my short experience with 5.1, it's gone. Hard to tell about your situation without screenshots from better battery stats and the app list.
biggiestuff said:
You might have the sensor ind bug that was in 5.01 that kept the phone from sleeping properly. From my short experience with 5.1, it's gone. Hard to tell about your situation without screenshots from better battery stats and the app list.
Click to expand...
Click to collapse
Thank you for the info. Root is not an option on the Nexus 6 cause my sister will be using it and she's not a techie. Without root I can't properly see what keeps it awake :/ As i said, besides the screen, biggest consumers are the Android OS and Android system in Battery settings list. But they're similiar on the Note 3 too so i dont think i can get somewhere with them.
I guess i will have to wait for 5.1 and hope it is fixed as you've said. Do you know what sensor is causing the sensor ind error? Does it have anything with the Ambient display?
HKNRN said:
My Nexus 6 is compeletely stock and untouched software. I have attached screenshots from Nexus 6 (5.0.1) and Note 3 (5.0) to show the point I'm talking about.
When I'm sleeping as you can see on the Note 3 it has very few awakes. But Nexus 6 on the other hand is almost always awake. It drains about 20-25% battery overnight.
I have performed factory reset 3 times and now it has almost no additional apps installed but still the same. (don't judge by the facebook on the screenshot it's just installed and the problem is the same with or without it) I'm not rooted so i can't use the wakelock detector. I've installed GSam and it shows Android OS and Android system as biggest drainers for the current situation (16%, 6%) which i suspect nothing extraordinary.
I have play services 6.7.76 on both devices if it has anything to do with it. I tried something like turning the ambient display off and some other settings to see if theyre waking it but no luck yet. Do you think it is a software thing and Google will eventually fix it and I should wait or what should i do?
I really want to keep this phone but the battery is a big concern for me right now. every morning seeing the battery down without touching the phone is a big problem. Any help and information on the subject is appreciated.
Click to expand...
Click to collapse
Do you use Microsoft Exchange services?
I mean, did you setup other e-mail accounts. Like- Outlook, hotmail .etc??
Because last time I found, that service kept my phone to always wake up..
Masum56k said:
Do you use Microsoft Exchange services?
I mean, did you setup other e-mail accounts. Like- Outlook, hotmail .etc??
Because last time I found, that service kept my phone to always wake up..
Click to expand...
Click to collapse
Oh yeah it has a hotmail account set up besides gmail. I will remove the hotmail account and restart the phone at night and observe in the morning again. Thanks for the suggestion!
If it is the problem, how did you overcome the issue? Are you using browser for your exchange mail account? If so, it will be a pain not getting mails to the app :/
Made some edits on the original post. If it helps..
As the title states, has anyone actually found the answer to NLPWAKELOCKS? can we just tell Google to F#CK off and stop waking our devices to ask for our damn location, while still having everything from searches and maps work peoperly? Is it a setting that needs to be changed? An app that needs reinstallation? Everyone has the apparent answer but includes breaking something.
darkfangex5 said:
As the title states, has anyone actually found the answer to NLPWAKELOCKS? can we just tell Google to F#CK off and stop waking our devices to ask for our damn location, while still having everything from searches and maps work peoperly? Is it a setting that needs to be changed? An app that needs reinstallation? Everyone has the apparent answer but includes breaking something.
Click to expand...
Click to collapse
Well look, here is the thing; if you stop nlp wakelock, then whatever it is that uses the data it builds will not have that data, thus *something* will break. Your best bet is to look at what is broken by the different solutions, and decide if that is something you are willing to live with.
I have most of the network location crap turned off on mine, and am observing nlp and nlpcollector wakelocks at 1 and 4 runs respectively, 0.1 seconds each total, over the last 5 hours. Not a big deal IMO.
Now the big google services wakelock that I'm seeing, is castsocketmultiplexer, at 117 runs, totalling 2m23s over the same time period. Also not a big deal.
My *total* google services keepawake is at 4m26s.
Since receiving the 9.0.83 update I have massive battery drain. Anyone else notice this?
MrBrady said:
Since receiving the 9.0.83 update I have massive battery drain. Anyone else notice this?
Click to expand...
Click to collapse
you just in reality not really said nor showed us your problem. ok, battery drain.. i have that. my battery drains when i use my phone.. understand? give us some more info, screenshots, etc.
simms22 said:
you just in reality not really said nor showed us your problem. ok, battery drain.. i have that. my battery drains when i use my phone.. understand? give us some more info, screenshots, etc.
Click to expand...
Click to collapse
Of course - details are always better! Here are some screenshots. I just re-installed the system yesterday (from N release 3 to TuPac's Lite 6.0.1 ROM). Charged overnight and listened to a few minutes of music this morning. The rest of the time the phone has been idle.
MrBrady said:
Of course - details are always better! Here are some screenshots. I just re-installed the system yesterday (from N release 3 to TuPac's Lite 6.0.1 ROM). Charged overnight and listened to a few minutes of music this morning. The rest of the time the phone has been idle.
Click to expand...
Click to collapse
Looks similar to an issue I had, turned out it was an issue that Google play services was having trouble with system update feature. It started when I switch from stock to Pure Nexus rom the rom, and many others, does something to disable the update button in the settings app but in some cases Google Play Services holds a wakelock for it for some reason or another. The way I fixed it was wiping Google play services and uninstalling its updates and letting it start fresh. Also if you have the app "GasBuddy" installed it causes a bluetooth wakelock, it only shows up in kernel wakelocks as "bluesleep," looking for beacons at gas stations to send you ads.
StykerB said:
Looks similar to an issue I had, turned out it was an issue that Google play services was having trouble with system update feature. It started when I switch from stock to Pure Nexus rom the rom, and many others, does something to disable the update button in the settings app but in some cases Google Play Services holds a wakelock for it for some reason or another. The way I fixed it was wiping Google play services and uninstalling its updates and letting it start fresh. Also if you have the app "GasBuddy" installed it causes a bluetooth wakelock, it only shows up in kernel wakelocks as "bluesleep," looking for beacons at gas stations to send you ads.
Click to expand...
Click to collapse
Thanks for the tip. No Gasbuddy installed. A few weeks back I had FiveStars installed (a purchasing points app) and it caused a huge Bluetooth wakelock. But that was removed a while ago and didn't affect Google Play Services.
MrBrady said:
Of course - details are always better! Here are some screenshots. I just re-installed the system yesterday (from N release 3 to TuPac's Lite 6.0.1 ROM). Charged overnight and listened to a few minutes of music this morning. The rest of the time the phone has been idle.
Click to expand...
Click to collapse
looks like its google play services updating itself or something. that happens every once in a while. best thing to do is to leave it alone for a day or two and it should "fix" itself after. but in a day or two, check your battery again just to make sure.
simms22 said:
looks like its google play services updating itself or something. that happens every once in a while. best thing to do is to leave it alone for a day or two and it should "fix" itself after. but in a day or two, check your battery again just to make sure.
Click to expand...
Click to collapse
Yeah, I think you're right.
Sent from my Nexus 6 using XDA Labs
MrBrady said:
Since receiving the 9.0.83 update I have massive battery drain. Anyone else notice this?
Click to expand...
Click to collapse
There is an app in the playstore called 'Disable services.
You can disable the services you don't use/need.
In case anyone has this same issue, I think I found the problem and solution. The latest version of Google Play Services causes a massive wakelock on ROMs that are blocking system update checks.
Using the DisableService app I enabled the update service and the wakelock has disappeared.
Sent from my Nexus 6 using XDA Labs
MrBrady said:
In case anyone has this same issue, I think I found the problem and solution. The latest version of Google Play Services causes a massive wakelock on ROMs that are blocking system update checks.
Using the DisableService app I enabled the update service and the wakelock has disappeared.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I've noticed the GPS wakelock using GPS on my N5, my wife's N5X, and a buddy's 6P as well. Did you enable systemupdateservice in only Google Play Services or both GPS and Google Services Framework? Both were disabled for me... Thanks in advance!
kornball said:
I've noticed the GPS wakelock using GPS on my N5, my wife's N5X, and a buddy's 6P as well. Did you enable systemupdateservice in only Google Play Services or both GPS and Google Services Framework? Both were disabled for me... Thanks in advance!
Click to expand...
Click to collapse
Just Google Play Services. I didn't think of looking in GS Framework.
Sent from my Nexus 6 using XDA Labs