[HTC One S] he_stheone64:
Did you make a dumpsys of your battery stats via adb? That shows you more detailed information about app usage. I also would recommend to install betterbatterystats from playstore and watch wakelocks. In 99% of the cases drain is not ROM, but app related.

To dump detailed battery info, connect your device and open your console in your adb folder. Then type:

adb shell

dumpsys batteryinfo

This is an example of the information you get. Like in BetterBatterStats watch especially apps with extensive wake locks, this drains a lot of battery in standby.

Proc com.htc.laputa.HtcLaputaInstaller:
CPU: 0ms usr + 0ms krn
3 proc starts
Apk com.htc.laputa.HtcLaputaInstaller:
Service com.htc.laputa.HtcLaputaInstaller.HLIService:
Created for: 5s 37ms uptime
Starts: 1, launches: 1
#10109:
Wake lock SCHEDULE:1: 11ms partial (1 times) realtime
Wake lock MAILSERVICE_PWR_LOCK: 5ms partial (1 times) realtime
Wake lock ScheduleServiceLock: 57ms partial (1 times) realtime
TOTAL wake: 73ms partial realtime
Proc com.htc.android.mail:sync:
CPU: 130ms usr + 60ms krn
1 proc starts
Proc com.htc.android.mail:
CPU: 0ms usr + 0ms krn
1 proc starts
Apk com.htc.android.mail:
Service com.htc.android.mail.mailservice.MailService:
Created for: 94ms uptime
Starts: 1, launches: 1
Service com.htc.android.mail.mailservice.MailIntentService:
Created for: 1s 427ms uptime
Starts: 2, launches: 2
Service com.htc.android.mail.eassvc.EASScheduleService:
Created for: 17ms uptime
Starts: 1, launches: 1
Service com.htc.android.mail.eassvc.EASAppSvc:
Created for: 1m 20s 875ms uptime
Starts: 1, launches: 1
#10111:
Proc com.google.android.apps.uploader:
CPU: 0ms usr + 0ms krn
3 proc starts
#10112:
Wake lock StartingAlertService: 1s 429ms partial (2 times) realtime
Proc com.android.mms:
CPU: 700ms usr + 200ms krn
1 proc starts
Apk com.android.mms:
Service com.android.mms.transaction.TransactionService:
Created for: 240ms uptime
Starts: 1, launches: 1
Service com.android.mms.transaction.SmsReceiverService:
Created for: 4s 83ms uptime
Starts: 2, launches: 2
#10116:
Proc com.htc.task.gtask:
CPU: 0ms usr + 0ms krn
1 proc starts
Apk com.htc.task.gtask:
Service com.htc.task.gtask.syncadapter.SyncService:
Created for: 0ms uptime
Starts: 0, launches: 1
Service com.htc.task.gtask.accountservice.GoogleAccountManager:
Created for: 54ms uptime
Starts: 1, launches: 1
#10118:
Proc com.htc.pen:
CPU: 10ms usr + 20ms krn
2 proc starts
Apk com.htc.pen:
Service com.htc.pen.plugin.PenService:
Created for: 5s 457ms uptime
Starts: 2, launches: 2
#10121:
Wake lock StartingAlertService: 597ms partial (1 times) realtime
Proc com.htc.task:
CPU: 110ms usr + 40ms krn
3 proc starts
Apk com.htc.task:
Service com.htc.task.notification.NotifyService:
Created for: 2s 388ms uptime
Starts: 1, launches: 1
Service com.htc.task.TodoService:
Created for: 4s 858ms uptime
Starts: 6, launches: 6
#10123:
Proc com.google.android.onetimeinitializer:
CPU: 0ms usr + 0ms krn
1 proc starts
Apk com.google.android.onetimeinitializer:
Service com.google.android.onetimeinitializer.OneTimeService:
Created for: 32ms uptime
Starts: 1, launches: 1
#10125:
Proc com.android.vending:
CPU: 100ms usr + 20ms krn
3 proc starts
#10126:
Proc com.google.android.apps.plus:
CPU: 480ms usr + 80ms krn
3 proc starts
Apk com.google.android.apps.plus:
Service com.google.android.apps.plus.iu.ConnectivityReceiver$AsyncService:

Created for: 823ms uptime
Starts: 4, launches: 4
Service com.google.android.picasasync.ConnectivityReceiver$AsyncService:
Created for: 176ms uptime
Starts: 5, launches: 5
Service com.google.android.apps.plus.service.PackagesMediaMonitor$AsyncSer
vice:
Created for: 2s 837ms uptime
Starts: 5, launches: 5
#10128:
Proc com.android.packageinstaller:
CPU: 0ms usr + 0ms krn
3 proc starts
#10136:
Proc com.htc.sdm:
CPU: 30ms usr + 40ms krn
2 proc starts
Apk com.htc.sdm:
Service com.htc.sdm.service.ReceiverIntentService:
Created for: 17s 146ms uptime
Starts: 2, launches: 2
#10144:
(nothing executed)
#10145:
Proc com.htc.wifidisplay:
CPU: 0ms usr + 0ms krn
1 proc starts
#10149:
Proc com.android.updater:
CPU: 0ms usr + 0ms krn
1 proc starts
Apk com.android.updater:
Service com.android.updater.service.UpdaterInitService:
Created for: 170ms uptime
Starts: 1, launches: 1
#10150:
Proc com.google.android.videos:
CPU: 0ms usr + 0ms krn
1 proc starts
Apk com.google.android.videos:
Service com.google.android.youtube.videos.DownloadJanitorService:
Created for: 148ms uptime
Starts: 1, launches: 1
Service com.google.android.youtube.videos.transfer.VideoDownloadService:
Created for: 112ms uptime
Starts: 1, launches: 1
#10156:
Proc com.qualcomm.wiper:
CPU: 10ms usr + 0ms krn
1 proc starts
Apk com.qualcomm.wiper:
Service com.qualcomm.wiper.Wiper:
Created for: 1m 32s 168ms uptime
Starts: 1, launches: 1
#10157:
Proc com.htc.android.worldclock:
CPU: 0ms usr + 10ms krn
3 proc starts
Apk com.htc.android.worldclock:
Service com.htc.android.worldclock.alarmclock.AlarmService:
Created for: 1s 738ms uptime
Starts: 3, launches: 3
Service com.htc.android.worldclock.timer.TimerService:
Created for: 136ms uptime
Starts: 4, launches: 4
Service com.htc.android.worldclock.stopwatch.StopwatchService:
Created for: 92ms uptime
Starts: 1, launches: 1
#10161:
Proc eu.chainfire.supersu:
CPU: 0ms usr + 0ms krn
1 proc starts
#10166:
Proc com.rerware.android.MyBackupPro:
CPU: 0ms usr + 0ms krn
1 proc starts
#10167:
Proc com.rdr.widgets.core:
CPU: 20s 320ms usr + 1s 290ms krn
1 proc starts
Apk com.rdr.widgets.core:
164 wakeup alarms
Service com.rdr.widgets.core.base.pager.HoneycombWidgetService:
Created for: 0ms uptime
Starts: 0, launches: 2
Service com.rdr.widgets.core.facebook.FacebookUpdateService:
Created for: 10s 320ms uptime
Starts: 11, launches: 11
Service com.rdr.widgets.core.people.PeopleUpdateService:
Created for: 9s 126ms uptime
Starts: 9, launches: 9
Service com.rdr.widgets.core.calendar.CalendarUpdateService:
Created for: 10s 376ms uptime
Starts: 9, launches: 9
#10169:
Wifi Running: 0ms (0,0%)
Full Wifi Lock: 11s 606ms (0,9%)
Scan Wifi Lock: 0ms (0,0%)
Wake lock WakeLockManager: 3s 14ms partial (6 times) realtime
Proc dk.tacit.android.foldersync.full:
CPU: 180ms usr + 30ms krn
4 proc starts
Apk dk.tacit.android.foldersync.full:
7 wakeup alarms
#10173:
Proc com.springpad:
CPU: 40ms usr + 0ms krn
1 proc starts
#10174:
Proc com.sharpcast.sugarsync:
CPU: 300ms usr + 110ms krn
1 proc starts
Apk com.sharpcast.sugarsync:
Service com.sharpcast.sugarsync.service.SugarSyncService:
Created for: 1m 26s 639ms uptime
Starts: 1, launches: 1
#10175:
Proc com.touchtype.swiftkey.phone.beta:
CPU: 880ms usr + 130ms krn
1 proc starts
Apk com.touchtype.swiftkey.phone.beta:
Service com.touchtype_fluency.service.FluencyServiceImpl:
Created for: 1s 672ms uptime
Starts: 1, launches: 1
Service com.touchtype.KeyboardService:
Created for: 0ms uptime
Starts: 0, launches: 1
#10176:
Proc com.touchtype.swiftkey:
CPU: 0ms usr + 0ms krn
3 proc starts
#10177:
Proc com.quoord.tapatalkpro.activity:
CPU: 0ms usr + 0ms krn
1 proc starts
#10181:
Proc org.adaway:
CPU: 10ms usr + 0ms krn
1 proc starts
#10191:
Proc com.asksven.betterbatterystats:
CPU: 0ms usr + 0ms krn
1 proc starts
#10192:
Wake lock com.bellshare.beweather.WidgetIconContentProvider: 1s 305ms partia
l (16 times) realtime
Proc com.bellshare.beweather:
CPU: 1s 820ms usr + 180ms krn
4 proc starts
#10205:
Proc mobi.mgeek.TunnyBrowser:DolphinNotification:
CPU: 0ms usr + 0ms krn
1 proc starts
Apk mobi.mgeek.TunnyBrowser:
Service com.dolphin.browser.message.C2DMService:
Created for: 30s 374ms uptime
Starts: 1, launches: 1
#10213:
Proc com.google.android.music:main:
CPU: 90ms usr + 40ms krn
2 proc starts
Apk com.google.android.music:
Service com.google.android.music.store.MediaStoreImportService:
Created for: 253ms uptime
Starts: 1, launches: 1
#10214:
Proc com.google.android.apps.reader:
CPU: 730ms usr + 230ms krn
2 proc starts
Apk com.google.android.apps.reader:
Service com.google.android.apps.reader.appwidget.NewsListWidgetRemoteViews
Service:
Created for: 0ms uptime
Starts: 0, launches: 2
Service com.google.android.apps.reader.appwidget.NewsListWidgetUpdateServi
ce:
Created for: 24s 288ms uptime
Starts: 2, launches: 2
#10215:
Proc com.fd.httpd:
CPU: 0ms usr + 0ms krn
1 proc starts
Apk com.fd.httpd:
Service com.fd.httpd.FDHttpdSvc:
Created for: 0ms uptime
Starts: 1, launches: 1
#10248:
Proc tunein.player.pro:
CPU: 0ms usr + 0ms krn
1 proc starts
#10249:
Proc de.tvspielfilm:
CPU: 0ms usr + 0ms krn
1 proc starts
#10258:
Proc com.j4n87.tweaks:
CPU: 0ms usr + 0ms krn
1 proc starts
#10261:
Proc com.android.gallery3d:
CPU: 0ms usr + 0ms krn
3 proc starts

Also this is a "must have" app:

https://play.google.com/store/apps/...sImNvbS5hc2tzdmVuLmJldHRlcmJhdHRlcnlzdGF0cyJd

---------- Post added at 09:57 AM ---------- Previous post was at 09:42 AM ----------

Wiping batterystats is as useless as reading a football magazine and hoping to become a better player as result :D

The .bin only contains info about processes, that use the battery. An overwiev of this collected information will then be displayed in settings. It has ZERO impact on battery life or the display of the remaining battery in statusbar, this is just an old myth. Just read my post above, then you know whats in this .bin. It will be resetted anyway automatically after every full charge. So better watch what`s happening on your phone via an app, in your battery settings or via dumpsys (which shows more details, then in the settings UI). Most of the time apps are causing extra drain, sometimes it`s also the radio - but then devs here can`t solve it anyway. But since most guys here are fine with battery life, I`m confident you can track it down to an app causing too many wakelocks.