this wakelock cause the battery drained. i didn't affected with any adverse effects. blamed play store + android cos ios & itunes app store got not such wakelock. i'm waiting my phone dead only change to iphone.
battery is more important than those play services. privacy guard implemented for a reason & y don't u fully utilize? u sound like privacy guard is pretty useless. disable wakeup & keep awake is more than enough.
I don't doubt that Privacy Guard works. Privacy guard isn't implemented into the system so that you can use such a heavy handed approach to deal with the problem.
Let me draw a parallel from this wakelock to a faucet leak. Your faucet is leaking and dripping. The root cause may be a gasket or o-ring that needs to be replaced. But instead of dealing with the faucet leak or even plugging the leak (band-aid fix), you shut off the water main. Sure, you resolved the leak. Now you can't flush the toilet, shower, or do the dishes in the kitchen.
That's exactly what you're doing by blocking Play Services entirely. The recent issues with Play Services are about SystemUpdateService alone. So why not deal with that problem alone?
This is XDA, and honestly I expect a bit more critical thinking. It's important to know what Play Services does. One important thing it has is the location API that developers of 3rd party apps can leverage. It handles location calls from 3rd party apps--so when your favorite weather widget, or Yelp or Foursquare/Swarm or Facebook wants background location updates, Play Services is responsible. Play Services is also responsible for Google Now location updates--background weather, traffic info.
Now this doesn't mean Google Now can't work, but if you disallow Play Services to work in the background, a lot of things could potentially be broken. Just because you might not notice the adverse effects you may have created doesn't mean you didn't create any. There are hundreds of bugs being fixed daily with app updates--do we notice all of those? Likely not.
