My wife and I recently got new S6 phones to replace our S3/S4 phones. We loved using the Alarm Clock Extreme app on our old phones because it worked perfectly for the longest time. It woke the screen up in the morning and with a quick shake of the phone it snoozed our alarms (a gentle crescendo of our favorite song) once or twice after which we eventually dismissed it by solving a simple math problem.
What we have experienced so far on our S6 phones is very unpredictable behavior for which I have tried various workarounds to no avail.
What happens in the morning is that the alarm will start to crescendo (as expected) but shaking it does not dismiss it. The screen also does not wake as it should. In order to snooze the alarm it is necessary to FIRST unlock the phone (thumbprint) THEN snooze any calendar notifications that may have popped up overnight (another subject I will address below) and then snooze the phone with a shake once the alarm screen shows up.
After communicating back and forth with AVG tech support via email, they acknowledged that there are issues they need to resolve and are currently addressing them. In the mean time I decided yesterday to uninstall the app and instead try the Alarm Clock Plus app. I intentionally did not enable "shake to snooze" on the new app just to see what would happen. After testing out the alarm SEVERAL TIMES before bedtime it seemed like it would work (even if a calendar notification triggered just before the alarm time). Well this morning the alarms on our phones triggered as expected however the screen did not wake up and to snooze the alarm it was ONCE AGAIN necessary to unlock the phones, snooze the calendar reminder that triggered before the alarm time, then finally snooze the alarm by pressing the snooze button on the screen.
So what it comes down to is that basically two of the best alarm clock apps do not work very well with Lollipop.
I haven't tried any other app because at this point I believe the behavior would be similar.
Regarding the particular Google Calendar event that triggered this morning.....the event in our "shared family event calendar" was set to start at 550pm with a notifcation time of 12 hours (i.e. 550am). My wife's alarm was set for 530am (i.e. 20 minutes prior to the calendar event). Even though we both have the DO NOT DISTURB setting on our phones to ON between the hours of 11pm and 630am (with an exception for allowing calls & texts) the calendar event triggered AT LEAST 20 MINUTES EARLY. So it would also appear to be the case that both the Do Not Disturb feature AND Google Calendar notification times are flaky as well.
I would be interested in your our personal feedback if you've experienced these same issues and any workarounds you may have discovered. Thanks in advance!
What we have experienced so far on our S6 phones is very unpredictable behavior for which I have tried various workarounds to no avail.
What happens in the morning is that the alarm will start to crescendo (as expected) but shaking it does not dismiss it. The screen also does not wake as it should. In order to snooze the alarm it is necessary to FIRST unlock the phone (thumbprint) THEN snooze any calendar notifications that may have popped up overnight (another subject I will address below) and then snooze the phone with a shake once the alarm screen shows up.
After communicating back and forth with AVG tech support via email, they acknowledged that there are issues they need to resolve and are currently addressing them. In the mean time I decided yesterday to uninstall the app and instead try the Alarm Clock Plus app. I intentionally did not enable "shake to snooze" on the new app just to see what would happen. After testing out the alarm SEVERAL TIMES before bedtime it seemed like it would work (even if a calendar notification triggered just before the alarm time). Well this morning the alarms on our phones triggered as expected however the screen did not wake up and to snooze the alarm it was ONCE AGAIN necessary to unlock the phones, snooze the calendar reminder that triggered before the alarm time, then finally snooze the alarm by pressing the snooze button on the screen.
So what it comes down to is that basically two of the best alarm clock apps do not work very well with Lollipop.
I haven't tried any other app because at this point I believe the behavior would be similar.
Regarding the particular Google Calendar event that triggered this morning.....the event in our "shared family event calendar" was set to start at 550pm with a notifcation time of 12 hours (i.e. 550am). My wife's alarm was set for 530am (i.e. 20 minutes prior to the calendar event). Even though we both have the DO NOT DISTURB setting on our phones to ON between the hours of 11pm and 630am (with an exception for allowing calls & texts) the calendar event triggered AT LEAST 20 MINUTES EARLY. So it would also appear to be the case that both the Do Not Disturb feature AND Google Calendar notification times are flaky as well.
I would be interested in your our personal feedback if you've experienced these same issues and any workarounds you may have discovered. Thanks in advance!