[Samsung Galaxy Nexus] osm0sis:
*Cough* ;)

Haha I'm honored you thought of me! ;)

You're right, they have nothing to do with the kernel. I don't even think it has to do with the ramdisk, though I could be mistaken. The cleaner script in the recovery flashable zips franco builds does clear the dalvik cache, but as he's said many times, it's not necessary for kernel flashing. If it were then the franco.Kernel Updater app should also cause the rebuild after flashing to Stock and back, but it doesn't. As I understand it, the cache partition is app cache storage and the dalvik is optimized "runtimes" built from apks to help them open more quickly on the Dalvik ("Java") VM. So if you're mucking around with theming/modding system apks/files, then yeah you need to wipe, and ROM flashing, most definitely. Kernel or radio? Nah. :p

It should be almost nothing, but if you have rogue apps waking up your phone all the time it could turn into quite a bit. I used to have like 3hrs of wlan_rx_wake locks in 14 hours; very bad, I had to change the wifi policy to "off when phone sleeps" to work around it. Now that I wiped and switched to takju, then restored my apps from TiBU, I don't have that problem anymore. :good: :D

You have wakelocks. Idle drain should be 1% or less and Deep Sleep percentage should be somewhere in the 90s. When you're looking at wakelocks look at the count as well as the %, also remember to check Alarms; some apps might not hold your phone awake a long time but wake it up often. Also, since someone else in this thread with battery issues did a few days back, do you have Touch sounds enabled in the Sound menu? If so, disable it. Causes a huge AudioOut_1 wakelock. Do you have a wlan_rx_wake wakelock? If so, you've got an app to hunt down but can work around it for now with the sleep policy as I said above. Also if you don't use Latitude disable all the automatic location tracking from within the Maps app, as others have just recently posted about. People also **** all over the Facebook app since it has like 50 background service threads due to poor app coding/construction and can cause a large number of wakes if you don't properly close it. Exchange email accounts can also go bat**** crazy and have enormous counts, if you see Exchange with a massive wakelock try removing that account, clearing data on Exchange and Email under Apps and then readd. Hmm what else? Don't use push for any syncing, set it to a time interval. I have email at 1hr, and facebook at 2hr. Also take care to disable all push notifications from apps like Facebook as well. Try to find a setting in the app to disable the push notifications, there should at least be one with the new Play Store rules coming into effect soon, otherwise you can disable it from that app's App Info.

Absolutely zero problems here on stock. My guess would be you fall in with the wakelock/rogue app problems of most of the above. Get BetterBatteryStats, paid version is worth it to support the dev.

Google Now is handy, but if you mostly just care about the cards and Voice Search all that stuff still works with Google Now disabled even, including call making, SMS, etc., so not losing too much at the moment.