[HTC Sensation] Skipjacks:
(Confirmed working on Android 4.1 through 4.2.2 on both the 121212 GApps and the 30113 GApps)

About this constant wakelock issue.....

Tobitege and I have been using a trial and error process to completely eliminate the Google Services Wakelocks.

The Android Alarms Manager is still being a pest. It is my opinion that the Android System AlamManager wakelock is a fault of the Android Framework provided by the CM Team. This is a normal part of development and is in no way a comment against the wonderful work done by the CM Team, but I think the Android System caused wakelocks are something they have to fix. No amount of disabling elements of the framework or uninstalling apps showed me any improvement in the wakelocks caused by the Android System.

This is a good old fashioned dirty fix, as it breaks some things. GTalk and GNow (and maybe a few other things) will not work after doing this. They are casualties of the dirty fix. But if you're like me and never use GTalk or GNow this will help. I'd bet that contacts sync and calender sync are also broken by this, but I don't use those so I don't know.

It's also a work in progress and we welcome someone else to improve upon it.

We used System Tuner Pro to disable some of the start up items in the Google Services Framework. Additionally we froze GTalk and Gnow (Google Search). And no, you can't just freeze those two apps without touching the GSF. The GSF will still create wakelocks when trying to activate them even if they are not there. So you have to modify the GSF as well.

These are the things that I disabled in the GSF using System Tuner Pro. (List updated 10/30 to be a littl emore refined. Has less diabled to prevent breaking of unrelated stuff)

gtalkservice.diagnostits.gtalkdiagnostics

gtalkservice.connection autherrordialog

talk.talkprovider

checkin.checinservices$reciever

checkin.checkinservices$triggerreciever

checkein.eventlogservices$receiver

gtalkservice.diagnostics.gtalkdiagnosticsbroadcast reciever

gtalkservice.serviceautostarter

gtalkservices.datamessagereciever

gtalkservice.sendxmppreciever

gtalkservices.packageinstalledreciever

gtalkservice.xmppendpointreciever

checkin.evenlogservice

gtalkservice.service.stalkservice

gtalkservice.pushmessagingregistar

You can freeze the GSF entirely with 1 easy step and that will also kill the wakelocks. But the Play Store becomes another casualty if you do that. Disabling the events above will stop the Google Services wakelocks dead in their tracks, and allow the Play Store to continue working. (Though I haven't tried purchasing a paid app yet)

Other minor quirks...when installing an app from the Play Store after making these changes you may not get the notifications in the status bar showing that it's downloading or installing. It still works, you just don't get the notifications.

Also, when you turn on wifi or mobile data, the signal bars don't turn colors. They stay gray because you aren't connecting to the google servers anymore. (They normall change color to indicate that you are connected to the Google servers)

I highly recommend making a Nandroid backup before trying any of this. Once you go that, go nuts! Try to activate or disable more events and see what your results are. You can't hurt too much when messing with the GSF because it will just shut down google elements. Worst case, you can always just reactivate everything, reboot, and it'll all work like it did before you messed with it.

When screwing with the Android Services on the other hand, you can disable all function of the ROM. So if you want to mess with that, again, be sure to have a Nandroid. And worst case, if you totally louse up your ROM, just restore the Nandroid and it'll all be back to normal in a flash. (Get it? In a 'flash'...haha I crack myself up)

This should have the same effects on any CM10 based ROM.

It's not perfect, but it's something. I feel like battery life has improved.