[ONE Android Development] himanagendra:
nope.....i checked everything several times. notifications are not effected. i didn't block the wakelocks for the notifications of gmail and whatsup. i took care of the notifications.

Those who are interested can try the following as i checked them for RR ROM and everything works fine as i don't like messing with my phone all the time. I'm using them from 20 days and it's good.

I'm not responsible

And in Amplify, search function works great. Try using search rather than checking everything.

Allow every 7200 seconds for the following:

- com.whatsapp.alarm.AVAILABLE_TIMEOUT

- com.cleanmaster.service.ACTION_UPDATE_CLOUD_CFG

- com.google.android.sidekick.shared.a.a.UPDATE_CALE NDAR_ACTION

- com.google.android.apps.sidekick.SCHEDULED_REFRESH

- android.net.ConnectivityService.action.PKT_CNT_SAM PLE_INTERVAL_ELAPSED

- com.sonymobile.superstamina.gateway.GatewayControl ler

- com.android.vending/com.google.android.finsky.services.ContentSyncServ ice

- ALARM_WAKEUP_CACHE_UPDATER

- com.whatsapp.MessagingService.RECONNECT

- com.google.android.apps.gsa.kato.ACTION_ALARM

- com.google.android.googlequicksearchbox/com.google.android.sidekick.main.TrafficIntentServ ice

u can block the following also for 43200 but please check whether the notifications are getting effected or not.By blocking the following Alarms...wtsup notifications may get effected. try them one by one. and regarding gmail i took care and searched everything. No probs

Things may get delayed if the phone has been idle for a while for the following(43200) only. Turning on the screen, connecting to a new WiFi or any event that wakes up the phone can trigger push notifications.

- com.whatsapp.messaging.MessageService.LOGOUT.ACTION(can be blocked -43200 sec. No probs )

- com.whatsapp.alarm.CLIENT_PING_TIMEOUT

- com.whatsapp.messaging.MessageService.CLIENT_PINGER_ACTION

- com.google.android.intent.action.SEND_IDLE

- com.facebook.push.mqtt.keepalive.KeepaliveManager. ACTION_INEXACT_ALARM.com.facebook.katana

- com.facebook.common.executors.WakingExecutorServic e.ACTION.ALARM.com.facebook.katana.Mqtt_Wakeup

- com.facebook.common.executors.WakingExecutorServic e.ACTION.ALARM.com.facebook.katana

Things may get delayed if the phone has been idle for a while for the above(43200) only

Allow every 86400 seconds or 24 hours

- android.app.backup.intent.RUN

- com.google.android.gms/.checkin.EventLogService$Receiver

- com.google.android.gms/checkin.CheckinService%Receiver

- com.cleanmaster.security.ACTION_BATTERY_CHANGED

Allow every 9999999 seconds

- com.facebook.analytics.service.AnalyticsEventUploa der.ACTION_ALARM

- com.google.android.gms.common.receiver.LOG.CORE_AN ALYTICS

- com.google.android.gms.common.receiver.LOG_CORE_AN ALYTICS

- com.google.android.gms.analytics.ANALYTICS_DISPATCH

Wakelocks :

Allow every 7200 seconds:

- *net_scheduler*

- ConnectivityService

- StartingDockService

- wake:com.whatsapp/.AlarmService

- AlarmService#updateNTP

- QcConnectivityService(86400 sec.)

Allow every 9999999 sec:

- *job*/com.facebook.katana/com.facebook.analytics2.logger.LollipopUploadService

- JobSchedulerHack-com.facebook.analytics2.logger.LollipopUploadService

- UploadServiceLogic-com.facebook.analytics2.logger.LollipopUploadService

Try the above and don't mess with the others.

In order to block that 1013 wakelock i'm trying it from RR Wakelock blocker in the configuration settings. I tried to block

*alarm* and dono the result yet.

NOTE: PLEASE INSTALL THE AMPLIFY APP & KEEP A FULL CHARGE AND LET IT DRAIN TO 5%, THEN BLOCK THE ABOVE(AFTER plugging in :p)

i'm not responsible for any loss:(. But make sure that you took care while blocking the above wake locks:cyclops: as they don't mess your phone:D. But to be in a safe side take a backup in twrp:o i mentioned the wakelocks carefully. so you will not face any problem. Give them a try;):):D

Please don't change the service unless you know them. Blocking the services will bring a great risk to you.