[BetterBatteryStats] VictorC666:
Here is my todays bbs log, did what you adviced

- disabled all *.fitness.* and *.wearable.* services as adviced in this thread

- disabled boot recievers SystemUpdateService$ActiveReceiver, SystemUpdateService$Receiver, SystemUpdateService$SecretCodeReceiver, rebooted, wiped dalvik cache, rebooted, as adviced by vaisakh7 guide

- installed System Tuner and killed Google Play Services process once.

Deep Sleep (): 3 h 13 m 69,5%

Awake (): 1 h 24 m 36 s 30,5%

Screen On (): 4 m 44 s 1,7%

SystemUpdateService wakeup is gone

BUT that terrible allarms from proces

com.google.android.gms

still there and even more...

com.google.android.gms (): Wakeups: 529 (1,9 / min)

======================
Alarms (requires BATTERY_STATS permissions)
======================
com.google.android.gms (): [COLOR="Red"][B]Wakeups: 529 (1,9 / min)[/B][/COLOR] [B]OMG[/B]
Alarms: [B][COLOR="Red"]293[/COLOR][/B], Intent: [B][COLOR="Red"]ALARM_WAKEUP_LOCATOR[/COLOR][/B]
Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.lockbox.LockboxAlarmReceiver}
Alarms: [B][COLOR="Red"]110[/COLOR][/B], Intent: [COLOR="Red"][B]ALARM_WAKEUP_ACTIVITY_DETECTION[/B][/COLOR]
Alarms: 57, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 19, Intent: com.google.android.intent.action.GCM_RECONNECT
Alarms: 0, Intent: com.google.android.gms.location.STATUS_ALARM
Alarms: 9, Intent: {com.google.android.gms/com.google.android.gms.checkin.EventLogService$Receiver}
Alarms: 0, Intent: com.google.android.gms.gcm.ACTION_CHECK_QUEUE
Alarms: 26, Intent: ALARM_WAKEUP3141367
Alarms: 5, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 1, Intent: ALARM_WAKEUP_ACTIVE_COLLECTOR
Alarms: 0, Intent: {com.google.android.gms/com.google.android.gms.common.download.DownloadAlarmReceiver}
Alarms: 2, Intent: ALARM_WAKEUP_BURST_COLLECTOR
Alarms: 0, Intent: {com.google.android.gms/com.google.android.libraries.social.mediamonitor.MediaMonitorIntentService}
Alarms: 3, Intent: com.google.android.location.reporting.ACTION_UPDATE_WORLD cmp={com.google.android.gms/com.google.android.location.reporting.service.DispatchingService}
Alarms: 2, Intent: ALARM_WAKEUP_BURST_COLLECTION_TRIGGER
Alarms: 0, Intent: com.google.android.gms.fitness.aggregate cmp={com.google.android.gms/com.google.android.gms.fitness.store.maintenance.StoreMaintenanceService}
Alarms: 0, Intent: ALARM_WAKEUP_CACHE_UPDATER
Alarms: 0, Intent: com.google.android.gms.reminders.REFRESH_NOTIFICATION cmp={com.google.android.gms/com.google.android.gms.reminders.notification.NotificationReceiver}
Alarms: 1, Intent: ALARM_WAKEUP_PASSIVE_COLLECTOR
Alarms: 0, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE cmp={com.google.android.gms/com.google.android.gms.icing.service.IndexWorkerService}
Alarms: 0, Intent: com.google.android.gms.common.receiver.LOG_CORE_ANALYTICS cmp={com.google.android.gms/com.google.android.gms.common.receiver.InternalBroadcastReceiver}
Alarms: 0, Intent: com.google.android.gms.fitness.trim cmp={com.google.android.gms/com.google.android.gms.fitness.store.maintenance.StoreMaintenanceService}
Alarms: 1, Intent: ALARM_WAKEUP_VEHICLE_EXIT_DETECTOR

Even this didnt helped...

But this article is interesting, its about ALARM_WAKEUP_LOCATOR

And here goes some info from Amplify author