Happens if your do not disturb was set to start at 12:00AM/midnight. Just change it to 11:59 or 12:01 and problem solved.
Also happens if its scheduled 1:00 am to 6:45 am. :-(
Happens if your do not disturb was set to start at 12:00AM/midnight. Just change it to 11:59 or 12:01 and problem solved.
Regular old clock radio user here. Never ever had a problem.
The other day google maps told me it would take 17 minutes to travel to my destination and it took 19 minutes. Google really needs to get their act together. Totally ridiculous. I'm calling this googlemapsGate.
Imagine that. Somebody just turned it off.
What will be next, everybody doing this, instead of whining here?
Also happens if its scheduled 1:00 am to 6:45 am. :-(
Galaxy S3 user reporting in....no clock issues here
i actually turned off the "do not disturb" last nights so my kids in America could call me. However this morning at 11 AM I see the crescent moon in the top even though I'm set to not be disturbed between 10:30 PM and 7 AM. Hopefully they get this fixed soon. I thought maybe the phone was on California time, but it is set to the Rome TimeZone and my clock is correct.
Mine was scheduled from 3 am to 7 am but was still on long after 7...
I'm in Singapore and I had no problems this morning. So I wouldn't say it's everyone.
Happens if your do not disturb was set to start at 12:00AM/midnight. Just change it to 11:59 or 12:01 and problem solved.
remember a few years ago alarms stopped working on a specific date and caused a bunch of people to miss their jobs lol. I wish Apple could test and error proof their software more. I bet android don't make these silly mistakes and I am an apple fan.
I can start to see why so many people are switching to android lately. Cheaper, just as good if not better and seems to be more talk of the town than iPhone is these days too.
Out of all the advertisements for phones i see these days 80% of them are for android devices.