Originally Posted by swatzombies
I think Google Services is the one causing wakelocks ... Please help me fix this issue.
Been there, done that. I can confirm that Google is an excessive drain when in airplane mode. Google derives their income from advertising and is very invested in keeping you online and building a profile of what you do there. They are a lot less concerned about the impact that the constant traffic has on your battery life.
There are many ways that you could reduce this problem. The following is optimal with respect to battery life, but there are less aggressive approaches if you want some intermediate balance of Google background activity vs. battery. You shouldn't find it difficult to search for alternatives in that case.
It's not actually Google /Play services that is instigating the wakelocks. It's the Google search app aka Google Now frequently pinging the GP services app for location that sets up all the wakelocks for NlPCollectorWakeLock. Android or GSAM labels it as "GP services" though which is a bit misleading.
Fix this behaviour by using Xprivacy or a similar permissions app e.g. App Ops or probably even the Android App Privacy menu to remove the Google Now permissions for:
Keep device awake
This eliminates almost all of the wakelocks and Google Now remains or appears to remain functional. Probably screws up Google's profile of your online activity though. Alternately you could try turning off location history and reporting (untested by me).