yashsingh1/xdaforums huggingface dataset:
[Android General] ke1v3y:
So I've been in a war against wakelocks for some time now. Unfortunately, I'm losing, so I'm here to find some assistance. I know the Skyrocket is plagued by battery issues, so improvement (not perfection) is the goal.

I'm currently running the latest stable SlimROM 4.3 build. Currently, my battery drain is 9.2% per hour with limited usage. I have Gsam and BBS installed. The issue has followed my phone and persists across ROMs. I am meticulous with my installation process, ensuring that data, ROM, cache, and dalvik are all wiped multiple times. My recovery is the latest CWM.

Thanks in advance!
[Android General] Perseus:
Can you please post your Partial Wakelock screen on the BBS ?

Also please post the battery drain screenshot?
[Android General] ke1v3y:
May have found the issue, although I do think there are other factors. I just downloaded Greenify, then I went ahead and Greenified Drive and a few others to begin with.

Anyway, here are my screenshots. Usually I see a wlan_rx wakelock, but it's noticeably absent.
[Android General] Perseus:
I see spotify chewing up quiet a bit of your battery. Greenify it as well.
[Android General] ke1v3y:
Won't that prevent background playing?
[Android General] jwhyte:
Do you have a search bar on home screen that caused 113 wake ups too.

Cancel sync on anything you don't use regularly. Google sound search gmail g+ etc.

Greenify won't stop background playing just keep it from starting itself in background. Greenify everything you don't need syncing.
[Android General] Perseus:
No it won't. My (strictly personal) opinion tends to not use Greenify. It does seems to help a lot of users. So I'd say greenify Spotify and then post the Partial Wakelock screen after next charge cycle. We'll see then.
[Android General] xcrazydx:
Greenify does nothing but eat up more battery instead of saving juice. It's junk.
[Android General] Perseus:
I can give junk to charity or recycle. So this is less than junk.

It creates even more wakelocks. There are some who are very passionate about it. So don't want to get into arguments.
[Android General] mimart7:
Any and all "battery saving" apps are garbage. Every one of them causes wakelocks.
[Android General] NoSpamDan:
I would normally agree, but this is hard to refute:
[Android General] mimart7:
I would wait for further info. Not that i have any doubts, but my past experience has shown otherwise. I may give this a try when I have some time to check it out.
[Android General] bps119:
I also have to hand it to greenify. I was skeptical at first, but it's worked well for me. While using it, I've gained around 3 more hours of battery overall and/or at least another hour of screen on time than I had on the same roms before using it.

It has been very unobtrusive as well. I've noticed no new wake locks while using it.

---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------

See the thread above which I posted here a while back. Lots of testing has gone on in this thread.
[Android General] xcrazydx:
I ran it for 5 days(hoping it would get better) and it decreased my battery life every day. It was also one of the biggest things on my battery consumption list.

The only thing I can think of is it helps people who can't get control of tons of social media apps.

Total garbage and it doesn't work for me, it only makes things worse. I already get almost 2 days without it. So I don't need it.
[Android General] NoSpamDan:
Sorry it didn't work out for you. I have been using it for 6+ months on different ROMs, and I have yet to see it among the top battery drainers. It keeps a lot of things in check for me :)

EDIT: And I only use Friendcaster with 1x/hour polling (and Tapatalk for XDA).
[Android General] xcrazydx:
I guess I do better at managing my phone on my own. Apps like that make my battery drain faster.
[Android General] Perseus:
This part is correct. That thread got hijacked into Greenify Bugs and features thread.

Honestly IMHO, the Op is spot on in nailing the wakelocks and reccomending BBS. Rather than suppressing the wakelocks from happening or slowing. Its better to remove them all together. At the end of the day, we all want good battery life free from the leeches that are Partial Wakelocks. Greenify spaces out the duration of the *Sync*. This helps when apps like facebook don't respect their own settings.

Having said that, we are not looking to space it out. We want these apps to respect System settings and allow undisturbed deep sleep in C3 state. So you have to follow the OP and get rid of the apps' PWL.
[Android General] ke1v3y:
So I Greenified a few apps, including the ones mentioned previously. Drain improved, but now I'm dealing with my wlan wakelocks.
[Android General] Perseus:
You fergot to Greenify Google Plus. Better yet, sign out of it if not being used. Also inside News and Weather, the Google app, set refresh frequency to 24 hours.
[Android General] ke1v3y:
Unfortunately, I actually use G+, so I can't sign out of it. On the other hand, I did Greenify it. I also changed the refresh frequency per your suggestion. I'll post back later with the results.
[Android General] Perseus:
I just saw, What on Gods Green Earth are the Beautiful Widgets waking your phone so much ? Loose them or deal with them.
[Android General] 1BadWolf:
Wlan wakelocks are caused by WiFi, not Google +. To get rid of that wakelock, either turn off WiFi or go to settings>WiFi, press menu and select the "Advanced" option. There you'll see a menu option labeled "Keep WiFi on during sleep" select that and set it to either "never" or "only when plugged in".

If I had a dollar for every time I said that, I'd be making money in a very weird way.
[Android General] aldus320:
what is related with rilj, activitymanager, , android.gsm, android.gsf wakelock
[Android General] Perseus:
Him an I had on and off line conversation over PM. I was simply answering his other question of what else should he turn off. At no point did I try to insenuate G+ causes Kernel Wakelock for WiFi.

Practically all of these are Kernel Wakelocks that are placeholder for various apps.
[Android General] aldus320:
can you explain it deeper please? :confused:
[Android General] Perseus:
You need to read OP post 2 & 3. That will explain a lot better than I could.
[Android General] 1BadWolf:
Right on. Looking at the public posts between you two it just looked that way. No offence intended. :thumbup:

If I had a dollar for every time I said that, I'd be making money in a very weird way.
[Android General] Perseus:
None Taken. Always appreciate and thank for such quality opinion. I will never get to learn otherwise.
[Android General] hotdog125:
What are the kernel wakelocks SCIM and GKI_LOCK_TIMER?
[Android General] Perseus:
They both are somehow related to Tower Lock. Sounds like Signal problem. A reboot might get a fresh lock.
[Android General] gc84245:
Well, I'm one of the few unlucky souls who went through the nightmare of having mmc1_detect and mmc0_detect wakelocks. Searching Google wasn't very helpful, so here's my experience:

Both of these wakelocks appeared together along with suspend_backoff. Each one would cause anywhere from 10-30% kernel wakelocks, keeping my device awake anywhere from about 40-75% of the time. I don't think it had anything to do with the microSD card. I deleted all of the files, formatted the microSD card (both on the phone and on the computer using quick format and full format), rebooting each time and still get the wakelock. Removed the microSD card completely and rebooted, wakelocks are still there.

Backed up my apps and factory reset the phone. Wakelocks went away. Added all of my files back to the microSD card, re-inserted card and rebooted. Still has not returned yet (*fingers crossed). Now I'm going to reinstall all of my apps a few at a time and see if it returns. I'll keep you posted. Wish me luck.
[Android General] Perseus:
I wish you all the Luck! I hope those torturous little fiends don't return. Apology for adding to your pain, but please you are going to install the apps one at a time, reboot, work the app for couple of hours and see if the pair came. If not repeat.
[Android General] gc84245:
I had considered doing them one at a time, but I think this way is better. If I have 100 apps and I do them all individually, that's possibly 100 reinstalls & reboots!

If I do 10 at a time, I can narrow it down only having to do this 10 times. Then I can narrow it down to 3. Then to 1. So, in total it would take a maximum of 16 tries instead of 100!

Plus, I'm not sure that they will return, so I'd much rather have to do this 10 times than 100!
[Android General] gc84245:
Well, I have good news and bad news. The good news is that after doing a factory reset and restoring my apps + data, the mmc0_detect and mmc1_detect wakelocks are now only a few % and are no longer the biggest wakelocks. My phone is now going into deep sleep about 90% of the time. So far so good (knock on wood). The bad news is that I was unable to figure out what caused the problem, so I might not be much help to others with the same problem.

That took many frustrating hours to fix. Needless to say, I'm going to be keeping a very close eye on wakelocks over the next little while.
[Android General] xcrazydx:
Don't restore apps and data. Do fresh installs or its pointless
[Android General] gc84245:
It's not pointless, it worked! And even if it didn't work, at least I can pinpoint the app that caused it and go from there. Anyways, I was pretty sure that it was the system and not an app that I downloaded.
[Android General] xcrazydx:
The wakelocks are still there, they just haven't gone totally crazy yet.
[Android General] Perseus:
+1. They won't go banana until you let them work for some hours.
[Android General] gc84245:
Nope. The wakelocks were there *every single time* immediately after rebooting and were *always* present no matter what I did. It has now survived several reboots with no problems. Lost 7% battery over 10 hours (overnight). Just wish I knew what the problem was.
[Android General] Perseus:
If its corrupt file or incomplete saved file for some app, we will never know...
[Android General] *system error*:
They were there because you put the same apps the same way every time. Listen and learn.
[Android General] gc84245:
Huh?
[Android General] mrfeuss:
What he's saying is that if you restore an app and its data with Titanium Backup that was creating a Wakelock, you're just going to recreate that Wakelock. It's fairly well known that restoring app data can cause a lot of issues. Sometimes you'll get away without any known or recognized issues, but not always. If you don't want to listen to the advice they're giving, then don't, but don't argue the point.
[Android General] gc84245:
Maybe I am not making myself clear. I am not here because I need help getting rid of a wakelock. I am here because I want to figure out what causes the mmc0_detect and mmc1_detect wakelocks so that I can help others avoid them. Therefore I want the wakelock to reappear so I can figure out what caused it. It will also help me should it reappear in the future. Unfortunately, even though I restored all of my apps + data (using ROM toolbox pro) the wakelock did not reappear, despite what other people here are telling me would for sure happen. I am still trying to rack my brain to figure out what caused it, even though it is no longer affecting me, so that others won't have to go through the same process that I did. I am just trying to give something back to the XDA community that has been a very valuable resource for me, but all I get is criticism in return :(
[Android General] Perseus:
Perhaps you should restore a Nandroid from the time when the wakelock did exist. Restoring on a clean flashed partition will rectify bad or corrupted app data.
[Android General] gc84245:
Ok, so if I restore from the Nandroid that I made before doing the factory reset and the wakelocks do come back, where do I go from there?

And if they don't come back, then I'm just at the same point I'm at now, no?
[Android General] Perseus:
If they do come back, I'd go systematically on a hunt.

Yes you will be back to square one if they don't come back. In that case I'd try even older Nandroid.
[Android General] gc84245:
I tried hunting it down a bit before the factory reset. Basically I tried clearing cache & dalvik cache, removing the microSD card, deleting large files from the internal storage, uninstalling certain apps that I thought might cause a problem (basically anything with root access, anything running in the background, and anything installed within the past month or so). Turning off sync & other features. Rebooted each time. I didn't remove every single app or delete every single file, though in hindsight I probably should have tried that. I'm not sure what else I could have tried other than uninstalling more apps or deleting everything from internal storage?

My last Nandroid before that was about a month ago, and I don't think the wakelocks were occurring then (only noticed it a week or two ago).
[Android General] Perseus:
Any app does not need root to cause that wakelock. Quiet possibly your simple mp3 player or desktop weather widget can cause it.

Corrupt or fragmented SQLLITE of some app is my best bet. Now after app restore, the fragmented app may have done re-org of the db. This latter may have caused the wakelock to disappear.
[Android General] gc84245:
Thank you, this is very useful. I'll keep this in mind if it ever comes back.
[Android General] gc84245:
I think I finally figured out the source of the mmc0_detect, mmc1_detect and suspend_backoff wakelocks. In my case at least they are caused by Google Location Reporting and Location Settings. I can reliably reproduce this wakelock by turning Location Reporting ON (Google Settings -> Location -> Location Reporting) and at the same time UNCHECK "Use wireless networks" (Settings -> Location services).

When Location Reporting is ON and "Use wireless networks" is checked I get the "NetworkLocationLocator" partial wakelock, which is what I would expect and this is well known.

When Location Reporting is ON and "Use wireless networks" is unchecked I get the mmc0_detect, mmc1_detect and suspend_backoff wakelocks which are actually much WORSE than when "Use wireless networks is checked"

Start rant.The worst part is that once I enabled location reporting the wakelocks persist, even after turning location reporting back off. I've even unchecked "Access location" from Google Settings -> Location. I've also tried turning off Google Now, removing and re-adding my Google account, clearing data for the Maps app, but I still get the NetworkLoctionLocator wakelock showing up as Google Services when "Use wireless networks" is checked or I get the mmc0 and mcc1 when unchecked. Google Services should not be determining my location if "Access location" is unchecked, right? As much as I love Android, this wakelock issue has been a huge frustration. What's the point in having services like Google Now if it's going to kill my battery. At least give me the option to turn it off! Now I will restore my Nandroid from before I enabled location reporting (I was getting 95% deep sleep when unused) and I'm going to leave it off, because I'm afraid if I turn it on it will never turn off again! End rant.

Anyways, can someone confirm that they get the same results? Turn on Location Reporting in Google Settings and Uncheck "Use wireless networks" under location settings, then check for mmc0_detect and mmc1_detect wakelocks (might need to reboot?). Then re-check "use wireless networks" and see if they go away. If someone else can confirm this then maybe we can add it to the guide on page 1 of this thread.

---------- Post added at 10:51 AM ---------- Previous post was at 10:33 AM ----------

I cleared the data for "Google Services Framework" and the NetworkLocationLocator wakelock has disappeared (for now). I guess I don't need to restore from Nandroid afterall. Back to 95% deep sleep. Whew.
[Android General] Perseus:
I truly wish I can help reproduce this wakelock. Unfortunately I am battling another big demon with Google Maps. So can't help. Besides I need to keep Location reporting off otherwise RILJ will haunt me forever.
[Android General] M3lory:
Solution?

Sry for my english but i m trying my best.

I had the same wakelock, and it was really annoying. I used a lot of Google researching without finding a solution.

I m not sure if it is really done, but at this stage there is no mmc1_detect wakelock anymore.

I found out that the wakelock is present after I switched apps from the internal memory to the external ssd card. After I switched back to the internal ssd followed with a reeboot the wakelock is not longer present.

Hope it will help u like it did for me.

Peace rAa@
[Android General] esimon311:
pm8921_eoc, anyone have any idea were this wake lock came from?

_________________

Beavers & Ducks!
[Android General] Perseus:
I wouldn't worry about that one. Unplug the phone and it will go away.
[Android General] ahasae:
thanks :)
[Android General] vibes340:
I'm getting smd_partial_wakelock, keeping phone from sleeping. What is it and how to get rid of it?

Thanks
[Android General] Perseus:
Are you talking about SDM Walkelock ? Its caused by you postponing OTA System update.
[Android General] hakreul:
Tried changing roms as well as kernel,uncheck usb debhugging,disabled mobile internet

The problem jst wont go away
[Android General] Perseus:
Is there a question in there somewhere ? Besides, you didn't post the 2 screens that would have helped. Partial wakelock and Alarms.
[Android General] hakreul:
Well yes...i want to know why my android OS percentage is so high...i suspect because of the wakelock USB...but then why and what is that wakelock...the USB one...my usb wasnt connected at all
[Android General] vmancini3:
Read this thread...it's only 4 pages worth of posts...I'm warning you though, you're not gonna like what you read...

http://www.galaxynexusforum.com/forum/rescue-squad/2720-kernel-wakelock-draining-my-battery.html

Sent from my SCH-I535 NOT using that garbage called TapaTalk 4!
[Android General] Perseus:
Colud be rom could be something else. Please post BBS Text dump to tell for sure.
[Android General] basilhs1985:
never sleeps after notification-wake

this has propably been discussed elsewhere but i couldn't find it. my phone sleeps properly (i have deep sleep battery saver installed) and does not wake up for weird reasons.

the problem is that when it does wake up (e.g for a missed call ) it doesn't go back to sleep. i have set it to go to sleep if idle for 15 seconds both in system settings and deep sleep baterry saver. this is solved temporarily if i remove the battery and reopen the phone but eventually happens again. (simple restart doesn't affect it).

how can i find what is KEEPING my phone awake? (not what wakes it ).
[Android General] Perseus:
Please get BetterBatteryStats and then post me its text Dump file after 3 hours of use.
[Android General] basilhs1985:
thnx for your responce. i already had better battery pro installed. i'd be glad to post the dump file but i don't see it anywhere in my sd card!! and there's no option within the app to extract data to file. am i missing something here?

would it be the same if i posted the screenshots of all the wake usage?
[Android General] Perseus:
The Log is residing in your Internal SD Card Folder. Typically its /Sdcard. Could be different if your Rom is changed.

Yes Screenshots will do. Need the ones for Partial Wakelock and Alarms at least.
[Android General] basilhs1985:
betterbatterystats.txt

my bad. i had an other app with similar name.by the way, if it helps my device is htc sensation z710e and its the stock rom not rooted.

here is the dump file. hope you can help. thnx again!
[Android General] Perseus:
Facebook and Hangouts seem to be top drainers. Please sign out of Facebook and then remove it. Same goes for hangouts.

If you must access Facebook, please use their mobile website.
[Android General] TheCybertronian:
But.... But.... I live in hangouts
[Android General] Perseus:
You could Greenify it. I do not recommend that app myself. Others have reported good results.
[Android General] TheCybertronian:
I wasn't the one with the issue lol. Also I'll never use greenify, I fully believe in androids memory management. I was just playing.
[Android General] Perseus:
Sorry my bad. I thought you too had similar issue.

As I said, I am firmly against Greenify.But this isn't about memory. This is Wakelocks.
[Android General] T.J. Bender:
I've never even downloaded the Facebook messaging app, so I doubt I'll be of any help there. Someone else in this thread might know, though.
[Android General] holeindalip:
I can't seem to get rid of this wake lock any help??
[Android General] phantomblu:
The current one is at 3 hours. I went to the raw stats and it states AirDroid and the Play Store. I'm not entirely sure if that's correct. What do the numbers next to (Wifi) mean?
[Android General] T.J. Bender:
Remember that there are apps (especially Google apps) that will hold a wakelock even if the device is awake. Check your deep sleep time. If your phone is awake for a long time with the screen off, you've got an issue. If your phone is basically awake when the screens on (plus a reasonable amount of wakelock time afterwards), who cares if you've got a four-hour Google wakelock? It's just keeping your phone awake when you're using it anyway.

Not sure on the numbers next to wifi in raw network stats for BBS.never worried about them--I'm more interested in data transferred and percentage.
[Android General] phantomblu:
The awake time is 2.5 hours, while the screen was only on for 30 mins. The data transferred for the apps was only a few mb. I'm guessing this wakelock is inherent to CM9. I'm never had this problem in AOSP, and some people claim that it disappears in JB. Now I'm just waiting for a stable build for my phone.
[Android General] kishke:
Still having sdio_al keep phone awake for marginally a long time(half an hour when the phone is idle a few hours) anyone figured out what its related to?
[Android General] T.J. Bender:
The only known causes are a type 6 charger or something wrong with the SD card. Try running your phone without the external SD and see if that fixes it. You might just need a new SD card if there's something wrong with the hardware on your current one that's locking you.
[Android General] kishke:
I already tried without an external, formatting the internal and what not, I didn't use to have all those weird sdio and mmc wakelocks one day they just appeared. Could be it's simply rom related. It's not that big of a deal I'm barely using my phone anyway I just like to get rid of useless things ^^
[Android General] T.J. Bender:
Might be ROM-related, might not. ROMs can definitely create wakelocks where there were none before, but the only way to tell would be to go back to rooted stock for at least two or three battery cycles and see if that wakelock remains a problem or not, as another ROM may well have the same issue. Sounds like it's probably not worth the trouble for you.

I'll point you back to a comment I made early on: every time you go hunting down and destroying a wakelock, especially a KWL, you run the risk of screwing something up and causing you to do a full wipe--or worse. If you're happy with your phone's battery life, don't waste tons of time and energy chasing down those last couple of wakelocks, especially if they're not doing much to drain battery (i.e., mostly locked when the screen is on) in the first place.
[Android General] kishke:
Apparently sdio wakelocks are the wlan wakelocks of data, just tried 3 hours of idle wifi+data off and my phone slept for 99% of the time, no sdio wakelocks only short mmc. You could add it to the OP.
[Android General] Datron:
Awesome. I tried to nail this one down last night. Please add to OP! Great thread here.

Unclefest v2 alive and kicking - support SeanZ! http://xdaforums.com/showthread.php?t=1771446
[Android General] T.J. Bender:
Added to the OP. I never would have found this one, as I'm almost always on Wifi. Thanks, kishke, for letting us all know!