[BetterBatteryStats] chamonix:
Here we go. This reading confirms what was present in the first reading but the longer period puts things in a better perspective. Here are the parts I will refer to. I changed the sorting for a better unerstanding

Since 9 h 52 m 30 s
Awake (): 1 h 28 m 12 s (5292 s) Ratio: 14.9%
Screen On (): 31 m 21 s (1881 s) Ratio: 5.3%
Wifi On (): 9 m 33 s (573 s) Ratio: 1.6%
Phone On (): 1 m 21 s (81 s) Ratio: 0.2%

Potential: 1 hour ot of 10, that's 10% and worth the effort

3gw.ServiceLifeCheckr (net.rgruet.android.g3watchdog.3G Watchdog): 3 m 14 s (194 s) Count:39 0.5%
3gw.Service (net.rgruet.android.g3watchdog.3G Watchdog): 15 s (15 s) Count:40 0.0%

3G watchdog is an app that obviouly misbehaves and from what google says it's known to cause wakelocks. My recommandation: get rid of it.

ImapFolderPusher Hilmesh - CEE:INBOX (com.fsck.k9.K-9 Mail): 29 s (29 s) Count:89 0.1%
ImapFolderPusher Hilmesh - CEE:Trash (com.fsck.k9.K-9 Mail): 24 s (24 s) Count:60 0.1%
ImapFolderPusher Hilmesh_RFE:Trash (com.fsck.k9.K-9 Mail): 11 s (11 s) Count:54 0.0%
ImapFolderPusher Hilmesh - EZN:INBOX (com.fsck.k9.K-9 Mail): 11 s (11 s) Count:46 0.0%
ImapFolderPusher Hilmesh - EZN:Trash (com.fsck.k9.K-9 Mail): 9 s (9 s) Count:7 0.0%
ImapFolderPusher Hilmesh_RFE:Drafts (com.fsck.k9.K-9 Mail): 7 s (7 s) Count:36 0.0%
ImapFolderPusher Hilmesh_RFE:INBOX (com.fsck.k9.K-9 Mail): 5 s (5 s) Count:96 0.0%

Maybe not high in sum but high from the overhead is the fact that you use k-9 with push on multiple levels (accounts, folders). My suggest here: k-9 allows you to limit the folders that you want to sync so give it a thought if syncing your trash is required. Alternative: switch to poll and decide of a frequency that works for you. I noticed some wakelocks from gmail too. You should check if that's a redudancy that you need or not.

NetworkLocationLocator (com.google.android.apps.maps.Maps): 3 s (3 s) Count:2 0.0%
NetworkLocationCallbackRunner (Google Services): 2 s (2 s) Count:1585 0.0%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 14 s (14 s) Count:3 0.0%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 14 s (14 s) Count:22 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 58 s (58 s) Count:802 0.2%
GpsLocationProvider (Android System): 44 s (44 s) Count:675 0.1%
NetworkLocationLocator (Google Services): 40 s (40 s) Count:788 0.1%

All those wakelocks are related to gmaps. If you use Latitude turn it off (there are good latitude updaters). If it's not the case please do following:

- make sure you update to the latest gmaps as this problem is known to be heavy in late 6.0x version but 6.02 fixes a little of that

- make sure gmaps cache settings are "wifi only"

- make sure your wifi policy (advanced wireless seetings) is set to off when "screen turn off"

- turn wifi off when you don't use it

ActivityManager-Launch (Android System): 1 m 13 s (73 s) Count:393 0.2%
AlarmManager (Android System): 1 m 12 s (72 s) Count:2937 0.2%

AlarmManager may be interesting if still high in next round, we leave it out for now as the above is probably part of the pretty high count

*backup* (Android System): 2 s (2 s) Count:957 0.0%

May not look high but as a general rule: sync of accounts and google backup have pretty negative impact when connection is bad. Therefore turn off backup if you use another backup method (my favorite is titanium).

Hope that this insight make you curious. You will like the result, I'm pretty sure