[Galaxy S 4 Q&A, Help & Troubleshooting] omniwolf:
that seems pretty reasonable drain now, I'd say your problem is fixed.

how to read the BBS file. All of this info can be gleaned from the BBS app, you don't have to dump the file unless you want to share you stats with others.

Not all of the BBS dump is useful. here's the stuff i look for:

Since 8 h 52 m 55 s <- how long this BBS session has gone for.

Level lost [%]: Bat.: -9% (100% to 91%) [1,0%/h] <- 9% lost over the above time, which equates to 1%/hour. 1%/hour is a reasonable amount for idling, the best i have got it to is about 0.6%/hour, but this is with a rooted debloated ROM, and custom undervolted kernel

Deep Sleep (): 8 h 20 m 16 s (30016 s) Ratio: 93,9% <- 94% deep sleep. this means that for the BBS session (~9 hours in this case), 6% of the time the phone was awake due to some process (wakelock) bringing the phone out of deep sleep. You want as much deep sleep as possible - the phone is in a super low power state (having shut down various components to reduce battery usage) when in deep sleep. 94% deep sleep is excellent. If you look at your previous deep sleep, it was 36% - shocking

Awake (): 32 m 39 s (1959 s) Ratio: 6,1% <- as i mentioned above - 6% awake, or 32 minutes

Screen On (): 7 m 33 s (453 s) Ratio: 1,4% <- 7 minutes of the session time you had the screen on. if you subtract 7 minutes from the awake time (32 - 7 = 25mins), it'll give you the amount of awake time you have with the screen off. the phone MUST be awake when the screen is on - this is obvious. However, when the screen is off, you're aiming for the least amount of awake time (or another way of putting it - the most amount of deep sleep). for 25 mins of screen off time your phone was awake instead of in the deep sleep state. You'll never get it to 0, the phone has to wake up for various tasks. 25 mins of awake time over 9 hours is totally acceptable IMO. This stuff is just "proving" your deep sleep %. It's not really giving you any new info.

Wakelocks <- this section describes all the user level applications that are keeping your phone awake when it could be in deep sleep. In the BBS app, this section is called Partial Wakelocks. I would probably pay attention to entries that are 10% and higher. in your case your worst Partial Wakelock is:

NetworkLocationLocator (com.google.android.apps.maps.Mapas): 9 m 21 s (561 s) Count:114 1,8% <- so 1.8% (9 minutes). totally acceptable IMO. you'd probably have to uninstall Maps to remove this, i don't think there's any settings you can do to get it lower.

Kernel Wakelocks <- these describe kernel wakelocks - so system wakelocks. You will have much less ability to affect these without rooting the phone and hacking away at it. Your worst is:

PowerManagerService (): 12 m 1 s (721 s) Cnt:(c/wc/ec)627/25/0 2,3% <- PowerManagerService is a grouping of all the Wakelocks - all the partial wakelocks in the above section form this single kernel wakelock. So you can mostly ignore this entry, because you'll be dealing with it in the above section.

The next 4 kernel wakelocks are to do with wifi and network, and are all tiny and insignificant (2% and less).

If you'd like to thank me, feel free to click the Thanks button on my posts :)