[BetterBatteryStats] husaam:
Just a note on how I managed to get rid of StartingAlertService causing partial wakelocks.

This has been causing me a lot of pain trying to resolve as it involved loads of diff apps. Here is an alarm dumpsys I did a while ago (without GTalk and no notification for calendar reminders, yet you still get gsf and android.calendar wakelocks)

-----

Alarm Stats:

com.google.android.gsf

6792ms running, 153 wakeups

46 alarms: flg=0x4

28 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4

79 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4

com.anod.calendar

348ms running, 0 wakeups

3 alarms: act=android.appwidget.action.APPWIDGET_UPDATE dat=com.anod.calendar://widget/id/335 flg=0x4

com.android.vending

362ms running, 0 wakeups

2 alarms: act=com.android.vending.FORCE_UPDATE_CHECK flg=0x4

android

174580ms running, 97 wakeups

1 alarms: act=android.intent.action.DATE_CHANGED flg=0x20000004

53 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4

1040 alarms: act=android.intent.action.TIME_TICK flg=0x40000004

133 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4

44 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4

com.whatsapp

33840ms running, 32 wakeups

1 alarms: act=ALARM_REPORT_SYNCS flg=0x4

1 alarms: act=ALARM_MESSAGES_DB_BACKUP flg=0x4

1 alarms: act=ALARM_ROTATE_LOGS flg=0x4

8 alarms: act=ALARM_AVAILABLE_TIMEOUT flg=0x4

27 alarms: act=ALARM_ACTION flg=0x4

22 alarms: act=com.whatsapp.MessageService.RECONNECT flg=0x4 cmp=com.whatsapp/.messaging.MessageService

com.android.email

6230ms running, 129 wakeups

4 alarms: flg=0x4

92 alarms: dat=Box-1 flg=0x4

20 alarms: dat=Box140 flg=0x4

2 alarms: dat=Box141 flg=0x4

4 alarms: dat=Box142 flg=0x4

2 alarms: dat=Box169 flg=0x4

5 alarms: dat=Box145 flg=0x4

com.android.providers.calendar

336ms running, 7 wakeups

1 alarms: act=android.intent.action.EVENT_REMINDER dat=content://com.android.calendar/1320133500000 flg=0x4

1 alarms: act=android.intent.action.EVENT_REMINDER dat=content://com.android.calendar/1320072300000 flg=0x4

3 alarms: act=com.android.providers.calendar.SCHEDULE_ALARM flg=0x4

1 alarms: act=android.intent.action.EVENT_REMINDER dat=content://com.android.calendar/1320104700000 flg=0x4

1 alarms: act=android.intent.action.EVENT_REMINDER dat=content://com.android.calendar/1320140700000 flg=0x4

com.gau.go.launcherex

8967ms running, 50 wakeups

46 alarms: act=com.jiubang.intent.action.ACTION_STATISTICS_DATA flg=0x4

2 alarms: act=com.jiubang.intent.action.AUTO_CHECK_UPDATE flg=0x4

1 alarms: act=com.jiubang.intent.action.SCAN_APPS flg=0x4

1 alarms: act=navigation_time flg=0x4

com.android.phone

16ms running, 1 wakeups

1 alarms: act=com.android.internal.telephony.gprs-reconnect flg=0x4

------

I have been able to get rid of StartingAlertService wakelock completely from BBS by freezing Calendar 1.1 on Titanium Backup and installing an alternative calendar app. Am using Gemini Calendar, it might not be to everyone's taste, but there are quite a few alternatives out there. My setup with Gemini means that my widgets such as Simple Calendar and Go Calendar work automatically without reconfiguring etc.

Yet again, it looks like its a Samsung app that's the cause of all the trouble, so use an alternative if you can.