I told him to turn things off to help identify the culprit, not to leave them off permanently. I probably didn't clarify that. He is on Android Central, not XDA. A lot of the people here are not power users. They don't have root, they don't flash ROMs and if they stare at an app like Better Battery Stats they simply don't know what they're looking at. They are not familiar with troubleshooting and identifying a particular partial wake lock may or may not make a difference for them, especially when dozens of things can use the same process. He has yet to post what partial wake locks he has, rather just stating that his wake locks are minimal. Are they? We don't know. That's his opinion, and maybe they are. He seems like a pretty smart guy. Even if they are, that doesn't help us with his partial wake locks. They are two different things. You and I know that, but from the way I read these posts, I'm not sure he does (maybe he does and I'm just reading him wrong). The way I read things, he's a "regular" user trying to troubleshoot his device.
Just because you've never noticed it, it doesn't mean that haptic feedback and touch sound problems don't run rampant. Search
https://code.google.com/p/android/ sometime. Read
this handy guide on XDA as one of many tips. In my experience, the most common partial wake locks I have personally experienced on
several devices have been AudioOut_1/2 and ConnectivityService (the latter because I travel extensively, usually in rural areas for work). The most common, by far, relates to Google Services which is expected. Identifying a partial wake lock is half the problem. Lots of things use AudioOut_2. In my experience, and the experiences of friends across all different devices from Froyo to JellyBean, turning off haptic feedback and touch sounds vastly cuts down on AudioOut_2 partial wake locks, again, a common battery draining partial wake lock for all of us. It doesn't solve them entirely, but it's not suppose to. PWL's are a part of life.
He doesn't have to cripple his device to troubleshoot it, he can merely start by turning off haptic feedback and touch sounds, give it a day and see if it makes a difference. He doesn't have to to do anything else. He can do something that takes 30 seconds, then put the phone down and walk away. This was my
first suggestion, the suggestion which
you ranted over and discounted as being a possible solution. You stated my suggestion was spreading incorrect information so I'm going about documenting why it is, in fact, correct information so the next person that comes along and finds this thread in a search doesn't pass over a simple fix. I never claimed to know everything about Android, but I do know a thing or two about partial wake locks just from personal experience alone.
Without knowing what his specific partial wake locks are, we have to make guesses and the best guesses are to look at what the common problems are. Based on that, my suggestions are possible solutions to unknown specific problems. AudioOut_2 and MediaScanner are big time partial wake lock issues for all Android devices, regardless of manufacturer or specific framework. My suggestions help eliminate those problems if you're a basic user trying to trouble shoot blind. Some of them ARE lengthy (like backing up your SD, formatting it, and copying everything back over) but that's a part of blind troubleshooting. A lot of other partial wake locks are related to Google Services, which like you said, shutting off cripples your phone. Or they are partial wake locks tied back to your network quality and there's not a whole lot that can be done about that. Still, that doesn't change the fact that if someone's phone is in a locker for hours at a time, there's literally no reason for it to be syncing email and other updates that you aren't there to see anyway. It's not something that I care to turn off, but that doesn't mean someone else that becomes informed of the option may not choose to take advantage of it.
Look dude, it's nothing personal, you can talk about whatever else you want to talk about in regards to me. I really don't care. But claiming that my first suggestion is so stupid that it completely discounts anything else I say is like saying I'm crazy for claiming that the Earth rotates around the Sun. And if you think you can toss an insult at me and not get something snarky in response, well, sorry man, but that's not reality. The only person in this thread not offering suggestions is you. If I've said something directed to you in the past that you interpreted as an attack out of no where, then you've misinterpreted my intent and take this as an apology. The only thing that really matters is that I'm not going to sit idly by and let anyone imply that a common fix isn't a fix just because they have a beef with me. That said, we're both derailing this thread and I for one am done derailing it, and hopefully you are too.
Facebook
Twitter
Instagram