Share your experience!
Hello one and all,
I see many of us have suffered issues after upgrading to Marshmallow. I've mangaged to sort out most by tinkering and blind luck, but I have an issue with the Alarm clock, and was wondering if anyone else had encountered a similar problem and found a solution.
Let's say Alarm clock is set for 06.45am. Since upgrade it has gone off at 06.46, 06.49 and 06.46 again. The 10 minute snooze went off at 06.59 (13minutes), 07.00 (11 minutes) and 06.59 (14 minutes) respectively.
I note that one other member of the forum has reported issues with the time not being displayed correctly, so is it a display issue, e.g. the alarm is operating at the right time but displaying incorrectly, or is it actually working at the wrong time?
PS also suffering with reduced battery life and increased heat during operation.
Regards,..........Dean (Amazingmin)
Solved! Go to Solution.
@Amazingmin wrote:Hello one and all,
I see many of us have suffered issues after upgrading to Marshmallow. I've mangaged to sort out most by tinkering and blind luck, but I have an issue with the Alarm clock, and was wondering if anyone else had encountered a similar problem and found a solution.
Let's say Alarm clock is set for 06.45am. Since upgrade it has gone off at 06.46, 06.49 and 06.46 again. The 10 minute snooze went off at 06.59 (13minutes), 07.00 (11 minutes) and 06.59 (14 minutes) respectively.
I note that one other member of the forum has reported issues with the time not being displayed correctly, so is it a display issue, e.g. the alarm is operating at the right time but displaying incorrectly, or is it actually working at the wrong time?
PS also suffering with reduced battery life and increased heat during operation.
Regards,..........Dean (Amazingmin)
Sounds like the Alarm app wasn't updated to handle the Doze mode. I haven't have this problem though.
Try adding the Alarm/Clock app into the whitelist.
Hi,
I've had the same problem for the last 6 months (maybe more), i've taken my phone in to be repaired 4 times and they've even replaced the phone as they couldn't figure out how to fix it, only to find the exact same issue on the replacement phone.
It's definitely something wrong with the Sony update - my guess is we'd have to wait until the next update until this is rectified. In the mean time, downloading a different alarm app should do the trick 
Hope this helps and spares you stress.
Yes, same problem on new M5 upated to Build Number 30.2.B.1.21.
But the alarm appears to have settled down to sound at the correct time.