unbounce-android
unbounce-android copied to clipboard
rsteckler
[1.1.6] Unbouncing com.google.android.intent.action.MCS_HEARTBEAT has no effect
com.google.android.intent.action.MCS_HEARTBEAT cannot be unbounced. Tried with 240, 480 and 600 but the alarm is not unbounced.
other Google Alarms unbounced: com.google.android.gms.nlp.ALARM_WAKEUP_LOCATOR (480 - working fine) com.google.android.gms.nkp.ALARM_WAKEUP_ACTIVITY_DETECTION (240 - working fine)
other Google Wakelocks unbounced: NlpWakeLock (240 - working fine) NlpCollectorWakeLock (240 - working fine)
- Bitbucket: https://bitbucket.org/cryptyk/nlpunbounce/issue/49
- Originally Reported By: Dragos Flo
- Originally Created At: 2014-09-29T04:56:24.964
this is the same on all devices and independent on the quality of connection. i think it's simply not possible to unbounce this wakelock and please let's remember that it's a questionable one from day one, means probably not recommended even if it would work :-)
Original Comment By: magna mentis
Also happens in 1.1.7. Seems that it is more proeminent on low internet connectivity. Testing this on WiFi triggers only 1 Alarm for this intent.
Original Comment By: Dragos Flo