Hi guys,
Been having this Wakelock trouble for a while..
I flashed the cm11 4.4.4 (nightly 12th July) along with the gapps and modem firmware provided on the official topic of cyanogenmod 11 for i9305.
To fix the issue - I installed WAKELOCK TERMINATOR and XPOSED FRAMEWORK. Then suspended couple of Wakelock trigger from the Google Play Services. But not improvement so far
I have also attached the screen shot from Wakelock Detector app, BetterBatteryStats and dump file.
Would appreciate any help.
Cheers
BBS Dump file - https://www.dropbox.com/s/sjbxxvo4yajwvna/BetterBatteryStats-2014-07-13_223313312.txt
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have been fighting with this wakelock for quite some time now.
For me it got much better with the latest Boeffla kernel version, most notably 2.3 Beta7b
Btw don't let you irritate by the "Omni" in the file name, this kernel works just fine here with CM11 4.4.4 and the latest nightlies
Good luck ,
Axel
s3axel said:
Have been fighting with this wakelock for quite some time now.
For me it got much better with the latest Boeffla kernel version, most notably 2.3 Beta7b
Btw don't let you irritate by the "Omni" in the file name, this kernel works just fine here with CM11 4.4.4 and the latest nightlies
Good luck ,
Axel
Click to expand...
Click to collapse
Trying the solution out.. Will keep posted how things work out... I am pretty sure a lot of people are trying to fix the mdm_hsic_pm0 Wakelock issue.
Also, using XPOSED frameworks with Wakelock Terminator..should I remove it?
Thanks again
The mdm_hsic_pm0 is not the wakelock, it's the result of the Wakelock. Something is keeping the device awake and using data (thus, the hsic)
Regarding the suspend_backoff:
https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/suspend_backoff
suspend_backoff is triggered whenever there's a rapid succession of sleep-wakeup-sleep transitions in a short period of time (10 occurrences within x ms IIRC). When that happens, SB makes sure the device is continuously awake for a bit instead of alternating a lot. The KWL count indicator could give a hint about the source of those continuous wakes, but not a definite answer because it doesn't show their time distribution.
i try this application but it crash directly on oneplus one paranoid 4.45(android 4.4.4)
this is the screenshoot
chicks0315 said:
i try this application but it crash directly on oneplus one paranoid 4.45(android 4.4.4)
this is the screenshoot
Click to expand...
Click to collapse
You mean, you are having Wakelock on the one plus one phone?... Then definitely it's related to the rom.. As new phone with new rom can't have the Wakelock this early on....
Related
So, recently, my battery life has gone to ****...mostly due to Android OS. I'm running MonsterRom 1.2. I just SBF'd the phone clean yesterday and restored apps via MyBackUp Root and TB. I made sure not to use a hand backup because I figured that would restore system settings causing the issue to re-surface. Any help would be much appreciated.
EDIT: I understand that this isn't a drained battery, but the volume of use remains proportional when the phone is nearly dead.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Me too
I've also had a similar problem on both copies of the droid 3 I own. Can't seem to find the answer. Anyone had any luck out there?
Looking into it further
There is a great thread here.
I installed betterbatterystats and turned off syncing for instant upload and Google Docs to see if that would help. Also, com.motorola.blur.service.sync.engine.wakelock.task seems to be a possible culprit on the wakelock side of things. It would be nice if we could put this problem to bed. Besides this and not being able to receive SMS with images in it (I think it's something to do with my provider, Koodo), I love this phone.
Assuming that the phone is rooted, download a app called battery calibration from the market, charge your battery to 100 percent or 4200mah,give the app root access and tap calibrate. You should be good. When changing roms it is important to calibrate your battery. Also you can do the same thing by booting to cwm recovery and erasing battery stats.
Sent from my DROID3 using XDA App
Possible progress here
Removing the calendar widget, docs sync, facebook sync and instant update seem to have made a significant improvement over the last couple of hours. I will update as I get more data.
I should note that I'm on .890, I have rooted and debloated except for blur (I want the calendar app unless someone else can suggest a better one), motoprint and task manager.
Has anyone noticed this wakelock in Better Battery Stats or any other battery stats app? For the past day or so, this has been keeping my phone from deep sleep continuously and I've never seen it before. I just wiped cache & dalvik to see if it persists.
Yes I got it for the first time yesterday. Did a force stop on the google frame work and it stopped. Seems like it came with the latest gooogle play services. I hope they fix it soon. Has not come back so far.
clankfu said:
Has anyone noticed this wakelock in Better Battery Stats or any other battery stats app? For the past day or so, this has been keeping my phone from deep sleep continuously and I've never seen it before. I just wiped cache & dalvik to see if it persists.
Click to expand...
Click to collapse
I have seen this dreaded wakelock and found no good solution....It comes and goes away on its own (I had tried cache and dalvik)
Back when I had root, I also tried to disable this service using a root app called DisableService. Though that seemed to have some other side effects, so I gave up....Now I am on 4.4 and Wakelock detector does not work with Kitkat, so I am not even able to check if these are happening anymore...Ignorance is bliss
tejaskary said:
Ignorance is bliss
Click to expand...
Click to collapse
So you haven't noticed any significant battery drain from it?
clankfu said:
So you haven't noticed any significant battery drain from it?
Click to expand...
Click to collapse
Yes, no significant drain..However, it would still annoy me seeing this one in Wakelock detector/ betterbatterystats that too for hours.....Its a service contained in Google Play services which is closed source, so can't even find out for sure what this exactly does
Damm you Google
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Julianocas said:
Damm you Google
Click to expand...
Click to collapse
I wiped cached and that wakelock seems to be gone. *knock on wood*
Hey guys, here is a fix for guys who are suffering with Google Play Services battery drain..
SCREENSHOTS:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOAD:
https://play.google.com/store/apps/details?id=com.playfulgeeks.gservicefix&hl=en
Much Needed One Bro :good:
Does anyone know what they are actually doing with this.
Website doesn't exist, there's no details on what it is or does.
Just some random promotions on a couple of forums.
Suspicious head on suggests this might be suspicious., I haven't downloaded it to rip apart yet, but I wouldn't rely on the word of a developer who says "this won't harm your device " as a product description
Sent from my C6603 using Tapatalk
What is the problem people have with the Google Play Services? Is it wakelocks create by it? What kind of wakelocks?
Kocayine said:
What is the problem people have with the Google Play Services? Is it wakelocks create by it? What kind of wakelocks?
Click to expand...
Click to collapse
Hi.
Wakelocks are called "nlpwakelock"
See picture.
Greets,
Marco
gork1975 said:
Hi.
Wakelocks are called "nlpwakelock"
See picture.
Greets,
Marco
Click to expand...
Click to collapse
You should try Wakelock Terminator, if you've got xposed.
Quoted from Reddit:
I know a great fix, if this can get to the top it will help a lot of people. It requires the Xposed framework and the module Wakelock Terminator. The free version lets you block 1 app, and that's all we need. Open up Wakelock Terminator, choose to block Google Play services, and filter it with the following: NlpCollectorWakeLock NlpWakeLock CheckinService NetworkLocationLocator
My Google Play Services and whatever else alias it is called went down by a ton, no effect on Google Now. Here's a screenshot of the Wakelock terminator app so you can see what it should look like.
Click to expand...
Click to collapse
Basically this just disallows it to keep the phone awake while still keeping the functions.
If you don't care about the functions (all these 'location' functions) then you could also get this: https://play.google.com/store/apps/details?id=cn.wq.disableservice - go to 'Google Play Services' and turn off the servces that keeps a wakelock.
anyone going to "approve" this?
So in that way we must choose batery drain or localization ?
testing now... ty bro
is it really working?
I dont know anything about codes nor trying to bash this developer, but the some google play reviewers state they have gone through the codes and it is nothing but a scam......
Thread closed on OP Request..
Hi everyone I have been flashing Roms for over a year or more now having a great time with it, have a question though I have been on the Omni Rom for a few moths now flashing the nightly at least once a week my last few flashes I have had OK Google going the problem is every time i say "OK Google" it responds understands what I have asked (as it writes it on the screen) then crashes. This happens every time and will not respond to the hot word till I reboot.
just to give full story my voice search will still work fine if I just press the microphone its only having a cow when I use the hotword. If anyone else has had this and fixed it please help.
thanks in advance
I'm having the exact same issue on my t0lteatt device running AOKP. It just started yesterday. I'm wondering if it's a google play services issue.
gtn7000steveo said:
Hi everyone I have been flashing Roms for over a year or more now having a great time with it, have a question though I have been on the Omni Rom for a few moths now flashing the nightly at least once a week my last few flashes I have had OK Google going the problem is every time i say "OK Google" it responds understands what I have asked (as it writes it on the screen) then crashes. This happens every time and will not respond to the hot word till I reboot.
just to give full story my voice search will still work fine if I just press the microphone its only having a cow when I use the hotword. If anyone else has had this and fixed it please help.
thanks in advance
Click to expand...
Click to collapse
-Sn1PeR- said:
I'm having the exact same issue on my t0lteatt device running AOKP. It just started yesterday. I'm wondering if it's a google play services issue.
Click to expand...
Click to collapse
Go to Google Search setting > Voice >Audio History " Disable" ( see the screenshot)
Clear cache and data of Google search
Now it should work[emoji2]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I should start off with, my phone normally ends an at least 12 hour day with ~40% and over 5 hours today, It had dropped to 10%. I have barely used it because I unplugged it to go to a doctors appointment, so not much use there, then for like 3 hours at home on my desk while I've been doing stuff on my computer, so almost none there either. Another confusing thing is that it says that "Over-Counted" used 32% of my battery but >3000 mAh?
Overall:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Over-Counted:
Second Highest Usage app (Google App)
Click to expand...
Click to collapse
Any ideas or fixes?
Also, how do I spoiler, there's no button
We can't see your pictures. They are on your google drive apparently. If I right click and open in new tab it shows them, one at a time.
Using Google, I found "over counted" is the new "Miscellaneous" in Marshmallow. Are you on a Marshmallow ROM?
Some relevant threads using Google search:
https://www.reddit.com/r/AndroidQue...ble_battery_bug_since_andorid_m_over_counted/
https://www.reddit.com/r/nexus6/comments/3osxfl/what_is_over_counted/
You basically have to go in and find out WHAT in the new Miscellaneous is causing your battery drain.
Many people have reported high wi-fi drain with Marshmallow, that could be your issue. There are ways to limit that -- @iiWoodstocK has some great settings. Or you can flash a custom Lollipop ROM (like CM12.1) while you wait for the bugs to be worked out.
ChazzMatt said:
We can't see your pictures. They are on your google drive apparently. If I right click and open in new tab it shows them, one at a time.
Using Google, I found "over counted" is the new "Miscellaneous" in Marshmallow. Are you on a Marshmallow ROM?
Some relevant threads using Google search:
https://www.reddit.com/r/AndroidQue...ble_battery_bug_since_andorid_m_over_counted/
https://www.reddit.com/r/nexus6/comments/3osxfl/what_is_over_counted/
You basically have to go in and find out WHAT in the new Miscellaneous is causing your battery drain.
Many people have reported high wi-fi drain with Marshmallow, that could be your issue. There are ways to limit that -- @iiWoodstocK has some great settings. Or you can flash a custom Lollipop ROM (like CM12.1) while you wait for the bugs to be worked out.
Click to expand...
Click to collapse
I'm using CM13 and It didn't update or anything, this happened randomly. Anyway, how do I "go in and find out" the details, it only shows me the computed and observed mAh usage. Also, I should have updated the post with that info but yeah I basically found the same thing.
I'm still on CM12.1, so I'm not sure how to investigate the over-counted stats on Marshmallow.