[BetterBatteryStats] chamonix:
Your phone was indeed awake the whole time, suggesting that what you changed didn't have any impact as your phone didn't sleep at all:

Since 5 h 47 m 12 s
Awake (): 5 h 47 m 12 s (20832 s) Ratio: 100.0%

But!!!!

1. in this reading the total time of email wakelocks is smaller (even if the count is still a concern):

ImapFolderPusher (com.kaitenmail.Kaiten Mail): 1 s (1 s) Count:463 0.0%
ImapFolderPusher (com.kaitenmail.Kaiten Mail): 1 s (1 s) Count:39 0.0%
ImapFolderPusher (com.kaitenmail.Kaiten Mail): 1 s (1 s) Count:504 0.0%
ImapFolderPusher (com.kaitenmail.Kaiten Mail): 1 s (1 s) Count:566 0.0%
ImapFolderPusher (com.kaitenmail.Kaiten Mail): 1 s (1 s) Count:483 0.0%
ImapFolderPusher (com.kaitenmail.Kaiten Mail): 1 s (1 s) Count:544 0.0%
ImapFolderPusher (com.kaitenmail.Kaiten Mail): 1 s (1 s) Count:589 0.0%
ImapFolderPusher (com.kaitenmail.Kaiten Mail): 1 s (1 s) Count:20 0.0%
ImapFolderPusher (com.kaitenmail.Kaiten Mail): 1 s (1 s) Count:851 0.0%
ImapFolderPusher (com.kaitenmail.Kaiten Mail): 1 s (1 s) Count:444 0.0%
ImapFolderPusher (com.kaitenmail.Kaiten Mail): 1 s (1 s) Count:423 0.0%

and the number of wakeups has reduced as well:

So you wanna know what is wrong don't you?

=========
Wakelocks
=========
LocationManagerService (Android System): 2 h 41 m 29 s (9689 s) Count:184 46.5%
AlarmManager (Android System): 2 h 41 m 29 s (9689 s) Count:769 46.5%

#2 is easy: Lightflow is killing your battery by waking up your phone almost 10 times a second (!)

com.rageconsulting.android.lightflow (): Wakeups: 2271
Alarms: 1, Intent: 10122
Alarms: 2092, Intent: -3

#1 is a little more tricky and I must guess as that is caused by an app that is location aware. Now looking at the alarms I see something weird:

cloudtv.hdwidgets (): Wakeups: 141
Alarms: 111, Intent: cloudtv.hdwidgets.USB_TETHERING_STATE_CHANGED
Alarms: 1, Intent: cloudtv.hdwidgets.GPS_STATE_CHANGED
Alarms: 46, Intent: cloudtv.hdwidgets.3G_STATE_CHANGED
Alarms: 120, Intent: cloudtv.hdwidgets.AIRPLANE_MODE_STATE_CHANGED
Alarms: 27, Intent: cloudtv.hdwidgets.SILENT_STATE_CHANGED
Alarms: 113, Intent: cloudtv.hdwidgets.WIFI_STATE_CHANGED
Alarms: 51, Intent: cloudtv.hdwidgets.VIBRATE_STATE_CHANGED
Alarms: 46, Intent: cloudtv.hdwidgets.4G_STATE_CHANGED
Alarms: 35, Intent: cloudtv.hdwidgets.UPDATE_WEATHER
Alarms: 58, Intent: cloudtv.hdwidgets.SYNC_STATE_CHANGED
Alarms: 27, Intent: cloudtv.hdwidgets.RINGER_STATE_CHANGED
Alarms: 49, Intent: cloudtv.hdwidgets.AUTOSYNC_STATE_CHANGED
Alarms: 2, Intent: cloudtv.hdwidgets.WIDGET_CHANGED
Alarms: 45, Intent: cloudtv.hdwidgets.MOBILE_DATA_STATE_CHANGED
Alarms: 3, Intent: cloudtv.hdwidgets.WEATHER_UPDATED
Alarms: 22, Intent: cloudtv.hdwidgets.BATTERY_STATE_CHANGED
Alarms: 521, Intent: cloudtv.hdwidgets.UPDATE_TIME

a) from the package name it's a widget and a widget is not really supposed to wake your phone up (it will if it uses the wrong alarm type)

b) that app is interested in any kind of location stuff but does that in a weird way that I would call poor design: there is no reason to create an alarm to wake up the phone and check if the wifi state has changed, there are broadcast listener for that.

I can not guarantee that this app is the cause of location but I'd recommend removing it so see if it gets better. Additionally I would recommend thinking really hard if you need it as it is poorly designed.

Last remark regarding JD: I'd recommend not leaving it out till the rest is solved as JD influences the behavior of your phone. Worse case you may end curing problems that are caused by JD instead of removing the root cause. I would ask you to thing about doing this:

- let's finish this iteration without touching JD (rule #2: never change a system during an iteration)

- once we have verified that the above mentioned is gone you disable JD, take a reading and we compare the effect of that action alone