Second culprit: AudioOut_1 : I also had unchecked all the keytone and touch sound options in setup, however, I was still getting a boat-load of PWL for AudioOut_1. I tracked it down (trial-and-error) to PowerAmp. Even though PowerAmp was not actively running, I had checkmarks (in PowerAmp Settings… Headset) in “Pause on Headset Disconnect” and “Resume on Headset Connect”.. which were preventing Deep Sleep. By un-checking these, it stopped the PowerAmp AudioOut_1 PWLs… and allowed Deep Sleep.
Wanted to share some results with you. Screenshots below. No KWLs in 24 hours since being unplugged...not half bad. PWLs are within reason, especially considering that Alarm Manager is one of those PWLs that will hold even if your screen is on.
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.
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.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.
Any idea what causes NetworkStats? This one keeps popping up now and then.
<off topic>
Is it weird that every time I read the thread title i see "The Total Newb's Guide to Warlocks"?
</off topic>
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.
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.
Did you check the Back up my data (back up to google servers) under settings/back up and reset?
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.