You haven't limited (see Post #2):
CONTEXT_MANAGER_ALARM_WAKEUP
analytics
Location alarms
If you don't need continuous instant FB updates, greenify it or experiment with limiting FB alarms. Non-system apps can be safely limited without affecting phone stability.
Widgets drain much more than their respective alarms would indicate.
NETWORK_LINGER_COMPLETE in the amount triggered in your log is not normal so I check to see if you're using a custom ROM and sure enough you are.
==========
CPU States
==========
1.25 GHz (): 4 m 25 s
CPU running at top speed for minutes in idle. I usually search for a near-corresponding time elsewhere in the log and find PowerManagerService.WakeLocks (): 4 m 9 s which BBS claims to be the sum of the partial wakelocks but a quick check in your Wakelocks section shows a total of exactly 2 m. So, either that's not the case or BBS calculations are wrong or there's a hidden wakelock not shown by BBS but calculated all the same.
Thanks for your reply!
I limited CONTEXT_MANAGER_ALARM_WAKEUP, analytics, Location alarms as posted in #2.
I would like to keep instant push messages since my goal isn't to achive 0%, i would be fine with 1-5% over 7-8h.
But I'm not using a custom rom.
I'm using the factory image of google with TWRP, SU, XPosed and ElementalX kernel.
I will take a look how the battery drain will develop with the latest settings.