yashsingh1/xdaforums huggingface dataset:
[Android General] whatlobster:
I didn't say anything specific about you turning things off. I don't know your preference, neither do I care. I'm not here to argue with you, I just don't think name-calling is productive in any way.
[Android General] sublimaze:
Every time I tried to Greenify Maps, it would give me some crap about not being able to pause system apps. There's probably a workaround but I was too lazy to pursue it. Uninstalled.
[Android General] mtdew:
I didn't call anyone anything but greenify is a scam or a lazy choice instead of actually fixing the problem. I get better life than most here and never cripple my resources but I know how to mitigate problems and get rid of wake locks properly.
[Android General] aca89:
Any general advice you can give?

Short but effective.
[Android General] bso44:
I converted Maps to a user app with Titanium Backup and then Greenified it.
[Android General] NoSpamDan:
Our you can use a root app to delete or uninstall it, then install the user one from the play store. You can Greenify that one.
[Android General] ItsComcastic:
mdm_hsic_pm0 and battery-monitor

Does anyone know what the mdm_hsic_pm0 and battery-monitor kernel wakelocks are and how to lower them? I've spent about a week trying to figure out the mdm_hsic_pm0 but can't find anything on it.

What causes the battery-monitor wakelock? Is it BBS? because I was under the impression that the app doesn't cause wakelocks other than stat saving. If I leave my phone alone about 40% of the standby time is getting used up by those two wakelocks.

Only thing I've gathered so far is mdm_hsci_pm0 seems to be an issue with samsung phones, I don't think I've seen a post about this wakelock on any other brand phone.

I've got a Sprint Note II
[Android General] Canadoc:
Uninstalling maps so that it is no longer a system app. Then reinstall from the play store. Now greenify can hibernate it.
[Android General] T.J. Bender:
So, I tried Greenify to see what all the hype was about. Like Juice Defender, my battery consumption actually went up with it installed and running. Deleted and not recommended.
[Android General] mtdew:
Lol told em, monitoring and controlling another apps built in sync times is never good.
[Android General] Theo X:
Quite the opposite here, works like a charm and improved battery life significantly. Only drawback is that you can't disable system services, if you care.
[Android General] NoSpamDan:
+1 Same big improvement here. It comes down to the cost vs benefit; one app's overhead or several. If you run your phone with very few apps, then it may cost more than it's worth. I have a lot, and I've configured the ones I can to stay dormant.

For example, I don't want sports scores updating all the time behind the scenes unless I've got that app open...
[Android General] ChavitoArg:
Can someone please tell me how to fix RILJ wakelock? ^^

Enviado desde mi S2 con NeatRom bareboned.
[Android General] T.J. Bender:
I remember how hot the debate over Juice Defender was a while back, and it seems like most casual users remain in love with the product, while those of us who know how to do a better job by fixing these things ourselves hate it. Greenify is headed down that same road. IMO, it's junk. Free junk, but junk all the same. This comes from five days using it and testing it out. With Greenify, my phone's battery was worse than without, and I don't consider myself to have turned things off to the point that it's "no longer a smartphone" (ridiculous argument, btw) by any stretch of the imagination. Greenify can only affect PWLs, and the easiest way to affect PWLs is by changing the settings of the app causing them.

If someone were unable to figure out how to keep an app from doing its thing, I'd heartily recommend Tasker. It gives you far better control over apps than Greenify or Juice Defender ever will, and is a pretty formidable battery-saving app once you know how to use it.

But whatever, this isn't the Greenify thread, it's the wakelock thread. Some people are going to love Greenify, others aren't. I'm leaving it out of my OPs because this isn't a thread to talk about battery-saving apps. It's a thread to talk about wakelocks and the apps/processes that cause them.
[Android General] gaich:
Searched through the theme and could not find anything related to my #1 KWL, mipi_link. It is present on every ROM and kernel I tried. Yes, I googled it many times and I know about MIPI alliance and I know some users think it may be an camera issue. No one BBS expert could answer and explain my dump.

I tried to freeze and uninstall Gtalk, Gmail, Skype, Callrecorder, freezed Gallery as well.

I do not use facebook and anything else that has anything to do with cameras. And I doubt this is the reason.

I tried to turn off wifi, mobile data, switch to 3g/2g only. No result.

The only remedy I found - it disappears completely in airplane mode.

I am aware this is skyrocket thread, but, maybe, there are some ideas?:confused:
[Android General] Theo X:
And if you created your own rom, you'd do an even better job. Every opinion is respectable, I'm just against someone insulting others because of their opinions. We need more constructive criticism like T.J's, whom I thank.
[Android General] Canadoc:
Some of what you say is true but some apps do not allow the user to change settings.

Maps is the perfect example of this.

It causes many wake locks that in spite of location settings being turned off still occur.
[Android General] mtdew:
Problem is your controlling in a way that the app wasn't meant to be controlled in creating adverse effects of their own. Some apps freak and stay awake if you cut its sync some apps don't. With an app like maps you normally use it a lot or seldom if you do use it a lot then you can't really do much if seldom it really is safer to just freeze. In the end though greenify only helps those who don't know or won't mitigate the wake locks they can control so my statement still stands. It's a bandaid over a gushing wound. It only helps those who won't handle the real problem.
[Android General] bso44:
Not true on my end. Before I Greenified Maps, I was getting excessive wakelocks from it, especially "NetworkLocationCallbackRunner". After Greenifying it, that wakelock has been minimized and I still have full functionality.
[Android General] mtdew:
I do to when its needed. Look at PAC and look at my times that's with maps unfrozen I don't need greenify to fix my problems for me I can do it without the app.

First pair half WiFi half data, second pair full WiFi.
[Android General] bso44:
Maybe that's true for you but no matter what settings I changed, I observed unacceptably high wakelocks from Maps via Better Battery Stats before using Greenify.
[Android General] mtdew:
OK I'm done bottom line it works for lazy people and ones who don't know any better. Everyone who has knowledge on wakelocks its just going to waste time and battery power.
[Android General] bso44:
So tell me how you would mitigate my issue with Maps giving me excessive wakelocks without the use of Greenify?
[Android General] NoSpamDan:
Ok, you can stop insulting and judging people who use Greenify already. Not the first time, not appreciated, and not forum-friendly.

So let's say you just ran Google Maps (user app), closed it, and now you have a network location/maps wake lock. Please share with everyone what you do to remove/terminate it. This IS the newb wake lock thread, right?

Folks, ignore the condescending opinion, and read about how Greenify works for yourself:

http://xdaforums.com/showthread.php?t=2155737

Works automatically, like a doctor putting stitches in your gushing wound for you, instead of you repeatedly putting a band-aid or even a tourniquet on it. ;)
[Android General] sublimaze:
The tone of this thread reminds me why xda was such a sh!tty forum not too long ago.
[Android General] TheMysteriousOne:
Read the thread title first before posting condescending opinions - it's a newbie's guide.
[Android General] mgbotoe:
Hey everyone, still new with this whole wakelock thing...I am having a kernel wakelock, msm_otg and I am not sure whats causing it. I have done search with no results what so ever...it is preventing my phone from sleeping...anyone know any solution to this?
[Android General] synnth:
Thanks for the great read, OP. I had no idea that this issue even existed until I sat down and read this over the morning coffee. I'll make sure to inform those around me, especially since this gave my fiance and I almost a 1/3 more battery life.
[Android General] plwalsh88:
I had been wondering about this, because I unchecked all those boxes in System Settings a long time ago (touch sounds/vibrations) and I still keep seeing a good amount of AudioOut_1 wakelock. I guess I'll have to keep searching for any apps I have that are outputting sounds. I never listen to music but maybe Google Music or Apollo are doing something in the background? Anyway, thanks for confirming that I'm not the only one who followed everyone's advice yet still sees the AudioOut_1 wakelock.

I always kind of thought that whenever I saw those results for KWLs showing nothing that something got screwed up in the process of tracking them or calculating them. I was just under the impression that you could never have no KWLs; I figured it always had to be doing something. I know I read that KWLs are reported differently than PWLs in that they are always calculated from the time your phone is booted or something. I'll have to find the exact thing I read.

But the other reason I think this is because with the early releases of CM9, KWLs would always show me that screen of saying there were none. No matter what I did; and I read other reports of the same thing. Then finally a new build came out that allowed me to correctly view KWLs. So I duno, just a thought.
[Android General] T.J. Bender:
I had thought (and, to an extent, still think) that's true about KWLs always being present, but this happens so rarely (every five cycles or so, at most) with KWLs reported the rest of the time that I almost wonder if BBS is accurate. I'd like to see what you've read, because it would be nice to have an answer one way or another.
[Android General] DoctorQMM:
You may also find (at least this was the situation in my case) that everytime you open PlayStore or are actively using certain games, AudioOut_1 wakelocks occur. To test, just before opening PlayStore, write down your AudioOut_1 wakelock "count" and "time". Then open PlayStore for 30sec (time it exactly).. then close PlayStore and immediately open BBS and check your PWL for AudioOut_1. In my case, the count incremented by "1", and time incremented by 30 seconds. Same case for games. In all of these situations, the AudioOut_1 is not keeping your phone awake and draining battery as you already have your screen actively on (games, PlayStore) which is using battery. The trick is to find those pesky occurences of AudioOut_1 which are preventing deep sleep when your screen is off.
[Android General] phantomblu:
Any idea what causes NetworkStats? This one keeps popping up now and then.
[Android General] T.J. Bender:
99% sure it's network traffic, but this wakelock never held for more than a few seconds at a time. View the raw network stats in BBS and it will let you know what's been eating up your data.
[Android General] ceasee:
<off topic>

Is it weird that every time I read the thread title i see "The Total Newb's Guide to Warlocks"?

</off topic>
[Android General] Datron:
No. It's odd that you read three pages and didn't fully realize we've been discussing warlocks. ;)

Cheers to the OP.

Unclefest v2 alive and kicking - support SeanZ! http://xdaforums.com/showthread.php?t=1771446
[Android General] kishke:
I can't seem to get rid of the sdio and mmc family wakelock, even with formatting internal sd and taking the external out completely.

Trying a 7 pass format to the internal right now should take 2 hours but maybe then those annoying wakelocks will be gone.
[Android General] T.J. Bender:
I've done a little more digging on the mmc_detect wakelocks, and my best guess is that they're related to the Media process, as force-stopping it seems to stop them. You've checked your charger and made sure it's not type 6, right? A type 6 charger will cause the sdio_al wakelock.

How long are the wakelocks persisting for? If they're not eating up too much time and battery life, I'd just leave them be.
[Android General] kishke:
I'm using the OEM block chargers shouldn't be type 6 because it's charging at 0.9A.

Each wakelock is pretty short but its a really long list of those so it stacks up. It finished 1 and a half passes before my cat stepped on the cable and ended the proccess but I'm letting the phone stay idle and I'll check if they are still occurring.
[Android General] T.J. Bender:
Yeah, I have yet to see a type 6 Samsung OEM charger. iPhone-compatible chargers are the ones that cause 95% of the wakelocks (iPhone, y u no use normal charger type?!).

I think this may be a "Google is your friend" scenario. Those wakelocks were so short-lived for me that I hardly even worried about them outside of experimentation, and "experimentation" when trying to solve small-scale wakelocks occasionally meant throwing a bunch of fixes at the wall to see which one(s) stuck.
[Android General] kishke:
Checked my phone now, 3 hours idle was still showing 100% until I browsed BBS then it dropped to 99% seem to improve somehow, this time I forgot the wifi on and although wlan keeps my phone awake a lot(loud network noises from my dad's work computer...), this time it was about 7 minutes, the battery seems to go down less slowly the usual.

Still getting all the mmc wakelocks, sdio wakelocks although adio_al dropped on time, and I noticed all the way down there are rpc wakelocks.

Gonna let it idle from more see how it goes, usually after 100%-99% takes longer then any other percentage.
[Android General] mimart7:
I'd also recommend Autostarts from the the market. It can help with disabling some things that are causing wake locks . It's $1.50.
[Android General] kishke:
rom toolbox does it for free
[Android General] RAVEN6:
Back Up and Reset

Did you check the Back up my data (back up to google servers) under settings/back up and reset?
[Android General] T.J. Bender:
I leave that turned off. Causes headaches.
[Android General] kishke:
Well still couldn't get rid of this long list of small wakelocks, I'll try a fresh flash once sean upload the new bases. I think that if you have no kernel wakelocks something must be up, It just seems like I always had a few can't remember it ever being empty.
[Android General] T.J. Bender:
It was mentioned earlier in the thread and I've since all but confirmed that a cycle with 0 KWLs is impossible--KWLs happen during boot. If BBS is showing 0 KWLs, it's glitching.
[Android General] chinthekng:
i know that the facebook app is a huge cause for most wakelocks and battery drain but i was wondering if the same also applied for the facebook messaging app and if you knew any alternatives that dont cause wakelocks
[Android General] T.J. Bender:
If I created a ROM, we'd have a lot more bricks around here.
[Android General] Febby:
I completely agree with you. Some users just feel like they're entitled to be the judgement god. :rolleyes:

@ Op, Thank you for this wake up guide. I'll be studying it closely!
[Android General] KicknGuitar:
TJ,

I read over your first three posts just yesterday and would like to thank you for sharing your experience thus far. Not only was it layman enough it was also enjoyable to read as your gusto comes across perfectly. When I first used BBS I felt like I was lost in a jungle with all those weird terms. Soaked in the rain, I took a few logs and began to see the light after toying with it and autostarts and blablabla. Even though it's after my experimentation your thread seemed to be a perfect coming of full circle for me. Nonetheless I regret I didn't find it before my adventure.

Because of your experience and seemingly dedicated will to test the problem to it's end, I'm curious what you think of WiFi/Data utilities.

After filtering out pesky apps like Facebook (Why does anyone use this? It runs in the background but when you use it it never loads?!) and crunching settlings like Google Latitude and turning off hyperactive autostarts I tested CleverConnectivity. Not the most thorough or strictest test but my battery was 0.5%/h~ less than without the utility running. I reason this a result of already sliming down the quakes n wakes n' all from my phone so that it naturally runs on deep sleep with little background noise. Is it fair to test this when the phone isn't being used? I would think me runing it may encourage greater drain in general and thus rendering the utility practically useless for my habits. I'm just curious to know your thoughts about a data/wifi utilities. Cheers.

Here's my results:

4Hr Tests	14Hr Test

CleverConnectivity	Off	On	Off	On
=============
Time (h:m:s)	4:46:47	4:29:32	13:52:11	14:21:00
Batt Loss /h	01.0%	0.4%	0.9%	0.6%
Total Loss	05%	02%	13%	08%
=============
Deep Sleep	3:42:37	4:22:42	11:23:46	14:20:49
Awake	1:04:16	0:06:49	2:28:30	00:50:13
[Android General] Canadoc:
Your argument is weak. Your battery values you post are not particularly good.

Maps causes many wakelocks. It is a major PITA to freeze and unfreeze an app that you use often. Better to have it sleep only to waken when you want it.

Just because you don't think it helps you don't dismiss it as useless.

Using better battery stats I clearly have fewer wake locks. ....

---------- Post added at 03:41 PM ---------- Previous post was at 03:41 PM ----------

Maybe it doesn't work for clowns who call people lazy and fail to see merit in front of them. ...
[Android General] T.J. Bender:
I've never really used a specific wifi/data utility, to be perfectly honest about it. I know Juice Defender has a similar option, and that option is one of the reasons I grew to hate Juice Defender. It didn't handle the off/on all that well, so apps that were trying to update would just try to find another way around and create massive wakelocks--not to mention JD's own PWL that would trigger seemingly whenever it was keeping an app or service from doing its thing.

In terms of testing a wifi/data utility, my approach would probably be to test with for a full day of regular usage, then without for a full day of regular usage (using BBS to track drain and wakelocks). Then I'd repeat the test, only this time I'd leave it dormant overnight with and without the wifi/data manager. It's a pretty fair test for both apps as long as you try and keep your usage (screen-on time, apps used) similar from day to day.
[Android General] gaich:
As nobody`s got any ideas about mipi_link KWL, I`ve made some more tests, regarding sync, sim-card etc, read different things about MIPI alliance, it resulted in a guess, raised up in my humanitarian mind - could it be some chip, produced by MIPI alliance (I met in their site something that tells about the application processors), that is communicating with some other hardware (the wireless modem, maybe) via some link?
[Android General] T.J. Bender:
A general note: if a question is asked about a wakelock and I don't answer, it's because it's a wakelock I've never dealt with before. I'm a big fan of keeping your mouth shut rather than helping someone accidentally break something.
[Android General] gaich:
Well, I added it here.
[Android General] EzSqueezeCheese:
10+ wake ups an hour from com.android.phone. is this normal? I don't believe so, but it's hard to find info on it. I'm not asking for a fix, I just want to know if its a common one.
[Android General] T.J. Bender:
How long is android.phone holding you awake for? It's not unusual to see hundreds upon hundreds of system-based alarms; they're only an issue if your device is being held awake by them for an unusually-long time.
[Android General] EzSqueezeCheese:
At first it was staying awake for 10 minutest a time with the screen off. Now it seems to be leveling itself off. I've never noticed that sort of wake lock in previous ROMs before. Might just be that this is day two with this ROM. I'll give it a faw days before I start tearing my phone apart.
[Android General] T.J. Bender:
Oh yeah, never start tearing into wakelocks on a fresh install. You'll drive yourself nuts and probably break something.
[Android General] KicknGuitar:
I had no idea this existed! Thanks for mentioning it.
[Android General] T.J. Bender:
I've got this marked to add to the op when I have a few minutes to do so.
[Android General] yets:
I'm not sure if it has been mentioned, but I had been struggling with the Powermanagerservice wake lock. It was draining my battery even though for most parts, according to the battery indicator, the tablet was barely awake. BBS showed that it was always awake and running at 200mhz for hours on end with PMS running in concurrence but no other wakelocks that correlated in length of time. I was tearing my hair out, numerous factory restores, running skeleton apps, even had the nexus replaced by Google. Just by chance on one occasion I had popped into running services/apps and noted that throughout my tests the only constant was the Settings service/app. I force stopped it and cleared it from the recent apps drawer and the nexus 10 never has had that wakelock again, the battery doesn't drain and the tablet sleeps.

I don't know how it's treated in other devices but in the Nexus 10, its treated as an app and if you don't leave it and close it by pressing back on the soft keys or force stop it, it keeps running and draining in the backgroud. Maybe it's worth looking at and researching a bit more?
[Android General] dejanxxxx:
Then say us, that we know how solve problem.If you know then say, and dont talking in empty , say and we look this is true.That I know how solve problem, I say, and dont talk that I know.Ok?
[Android General] mrfeuss:
Aside from being incomprehensible, that was an unnecessary, antagonistic post. Please don't clutter up these threads picking fights for bickering that ended days ago.
[Android General] chrissurra:
Thanks for this I pulled another 2+ hours of battery life by going through your walkthru. My battery thanks you.
[Android General] JamesEh408:
Thanks for this..I needed it

Be yourself...no one else can.
[Android General] bso44:
Anyone know how I can stop this ScheduleNextAlarmWakelock?
[Android General] onealvideo:
Read this entire thread... We covered these wake locks.... I believe back around page 18 or 19... Usually Google Now is the culprit but read back a bit...
[Android General] T.J. Bender:
TBQH, I'd just FC Calendar and see if it comes back. I'll occasionally get weird, random, Google-caused wakelocks on my Note 2, and I've had a great deal of success just FC'ing the process when I do.
[Android General] gaich:
I shared some experience with my GTALK family wakelocks, if someone is interested.:)
[Android General] bpaulien:
Thanks so much for this thread! I saw this linked from a different forum, for LG Marquee, but there's so much in here NOT specific to the Galaxy SII that it's helpful for everybody. I have increased my battery life from about 12 hours a day to a little over 24, just by following some of the suggestions and killing the major offending wakelocks. Now when I go home from work, I've got closer to 60% battery remaining instead of the (formerly) typical 32% remaining. And that's without changing my usage patterns (if anything, using it MORE because I don't feel I have to conserve battery). Even though I have a charger at work, I haven't been using it lately, 'cause these tips really work well.

I just finished reading the entire thread. There's quite a lot to learn in here.

The biggest thing keeping it awake now is AlarmManager and something called *wifi* (asterisks included) Not sure what it is, but according to BBS, it appears to be taking up 2% of my time. The rest are relatively reasonable, I think so I'm not really too worried about them.

Just thought I'd put in my $.02 worth, and thank you again for all the great info on here!