Using the Alarm Clock Plus app, since I got the Marshmallow update, alarms in the morning have been hit or miss. Seems like it used to go off within a minute (which is also not really very accurate). This morning it was 4 minutes late. Yesterday, the alarm didn't go off at all. Has Marshmallow gone too far with power savings or something? Anyone else having alarm problems?
Using stock alarm app, works fine herw
Sent from my Nexus 5 using Tapatalk
I've been using Timely for its "early rise" function which kicks in 30 minutes before the alarm time with a very quiet tone rising over the course of the 30 minutes. I'm a light sleeper, so I've been setting the alarm time for 30 minutes later so that it goes off very quietly; if "early rise" is off it starts at full volume, which I don't like.
But since I upgraded to Marshmallow the function doesn't work - regardless of whether "early rise" is ticked or not it goes off at the alarm set time.
Coincidence...?
There's obviously something going on with time settings in Marshmallow, since Clocksync doesn't work properly either - a fact recogised by the developer, who has posted a note on his Google Play entry asking for help or advice:
"WARNING: Android 6.0 devices may not work correctly at the moment, even with custom permissive kernel and SuperSU installed. I'm looking for the solution at the moment. Please contact me if you know how to fix it."
Doze will be cutting it's sync times down. Just use stock alarm clock
Sent from my Xperia z5 by Tapatalk
Stock ^^ ☝?
This morning, it didn't go off at all again. Only when I waked up on my own 20 minutes late, wondered what time it was, and turned on the phone did the alarm go off. The Med Helper app reminder also didn't go off till I turned it on, so now two different apps with alarms have failed to work. I think I need to read up on how to re-install Lollipop .
Have you tried turning doze off for your alarm based apps?
What they said ^^^^ tap the 3 dots in battery setting and pick optimizations the select all apps and un-optimize your alarm app.
Sent from my SHIELD Tablet using Tapatalk
OK, I'm trying with battery optimization turned off for the two apps I had a problem with, but I see battery optimization is turned on for the stock "Clock" app, and an alarm I set with it went off on time, so there must be some magic apps can do to make timers work on Marshmallow even if they are battery optimized. If I knew what it was I could write the developers and ask them to include it .
dahawthorne said:
I've been using Timely for its "early rise" function which kicks in 30 minutes before the alarm time with a very quiet tone rising over the course of the 30 minutes. I'm a light sleeper, so I've been setting the alarm time for 30 minutes later so that it goes off very quietly; if "early rise" is off it starts at full volume, which I don't like.
But since I upgraded to Marshmallow the function doesn't work - regardless of whether "early rise" is ticked or not it goes off at the alarm set time.
Coincidence...?
There's obviously something going on with time settings in Marshmallow, since Clocksync doesn't work properly either - a fact recogised by the developer, who has posted a note on his Google Play entry asking for help or advice:
"WARNING: Android 6.0 devices may not work correctly at the moment, even with custom permissive kernel and SuperSU installed. I'm looking for the solution at the moment. Please contact me if you know how to fix it."
Click to expand...
Click to collapse
I use timely and haven't had or noticed any issues. Just this morning I used Smart Rise with alarm set for 11:45am, and on time the music started very quietly at 11:15 am. I love the smart rise feature, however it is terrible if you are already kinda awake, because it's so soothing it will put you to sleep! However to be woken up by it after it had been slowly increasing in volume is a good way to wake up.
Sent from my Nexus 5 using Tapatalk
The Alarm Clock Plus alarm I set after disabling battery optimization for that app just went off on time, so perhaps that is a work around for now, but I'd still love to know how the stock Clock app manages to work even though it has battery optimization enabled.
Nope, it was a false alarm. This morning Alarm Clock Plus did not go off at all, even with the battery optimization turned off for it. However, the Med Helper notification did go off, so the battery optimization change seemed to work for it. Perhaps it has something to do with Med Help using notifications, and Alarm Clock Plus trying to completely wake the phone and display on the full screen?
Alarm Issues
I've experienced the same issues with Alarm Clock Plus. I don't have any battery optimization turned on. It seems to be tied to silent mode and not being able to be silent without do not disturb turned on for me.
For the second time since I've installed marshmallow, my alarm didn't go off. I'm a very light sleeper and today, as with most days, I woke up before my alarm. So I checked my alarm and it was set for just about an hour from then. I drifted back off and woke a half hour after my alarm was set to go off. Everything was set right and I took a couple minutes to reset my alarm two minutes after the current time. It went off. I did the same thing the first time my alarm didn't go off, same results. I've actually tested it several times and it always went off, maybe from not being asleep for that long. I've also been waiting for text replies a few times before and not hear anything, then I check and see I have two or three. Volumes checked, everything's right. Either I'm going crazy or something is wrong with the new update. Just thought I'd add my two cents.
---------- Post added at 10:33 PM ---------- Previous post was at 10:02 PM ----------
Aaronroni said:
For the second time since I've installed marshmallow, my alarm didn't go off. I'm a very light sleeper and today, as with most days, I woke up before my alarm. So I checked my alarm and it was set for just about an hour from then. I drifted back off and woke a half hour after my alarm was set to go off. Everything was set right and I took a couple minutes to reset my alarm two minutes after the current time. It went off. I did the same thing the first time my alarm didn't go off, same results. I've actually tested it several times and it always went off, maybe from not being asleep for that long. I've also been waiting for text replies a few times before and not hear anything, then I check and see I have two or three. Volumes checked, everything's right. Either I'm going crazy or something is wrong with the new update. Just thought I'd add my two cents.
Click to expand...
Click to collapse
androidauthority dot com
I should have read the dates but Google brought this up first. So if anyone happens upon this thread, the above link explains it. The fix is 6.0.1 and is being worked on and even released for some phones already. :good:
Ok can't post links yet but that website has answers
Having the same issue with S7 edge on 6.0.1 using Alarm Clock Xtreme. Won't wake the phone even tho power save is off and auto power save for the at app is off as well. Works if I set it for only a few min from now, doesn't work after the screen being off all night.
I have the exact same problem. It's been three times now that I've been late to class because the alarm didn't go off. Last time Itried setting two alarms five minutes from each other and the iPad alarm. iPad worked, phone didn't. It seems to happen especially often of I place the alarms earlier than usual for some reason, and I only do that when I have an exam to study for, so It's been a fun couple of days.
At first I shrugged it off convincing myself that I had rose in the middle of the night somehow, turned it off and continued on sleeping, without remembering anything in the morning, but after using the iPad to check on the third time I'm pretty sure that it isn't my problem.
Anyway, I use the STOCK alarm clock ALWAYS. I haven't tried it with the doze mode off, I'll try it today, but still. The fact that I might have to purchase an analogical clock because Android isn't working properly it's just disappointing.
I've been having the same problem on my Galaxy Note 5 since updating to 6.0 Marshmallow, and it persists even with today's update to 6.0.1.
The notification tab for the alarm seems to indicate that it thinks it's still 5:28PM, two minutes before the 5:30 alarm time, even though it's well past 6PM now. The last couple missed alarms DID notify me that I'd missed an alarm, about an hour after the alarm time had come and gone. It won't sound the alarm though.
At first I thought it might have just lost touch with the custom tone I've set for my alarms, but now it seems to be that the alarm clock gets stuck a couple minutes before the alarm, even while the system clock goes on as normal.
This is the default clock's alarm feature, not a third party app, so it should not need any developer updates to work right, if Google is doing their job before pushing out system updates.
UncleSim said:
I've been having the same problem on my Galaxy Note 5 since updating to 6.0 Marshmallow, and it persists even with today's update to 6.0.1.
The notification tab for the alarm seems to indicate that it thinks it's still 5:28PM, two minutes before the 5:30 alarm time, even though it's well past 6PM now. The last couple missed alarms DID notify me that I'd missed an alarm, about an hour after the alarm time had come and gone. It won't sound the alarm though.
At first I thought it might have just lost touch with the custom tone I've set for my alarms, but now it seems to be that the alarm clock gets stuck a couple minutes before the alarm, even while the system clock goes on as normal.
This is the default clock's alarm feature, not a third party app, so it should not need any developer updates to work right, if Google is doing their job before pushing out system updates.
Click to expand...
Click to collapse
I had been using darker themes since the update, not liking all the whiteness of the new default theme, but I reverted to the default long enough to test, and the alarm went off today as normal. So it seems that , at least in my case, the themes are impeding the default clock's alarm function somehow, even those I've used that say they're Marshmallow compatible.
Even with CM13's or OmniROM 6's system alarm app, the alarm will not start and be shown as missed when the phone is longer in standby..alarm clock is set as "non optimized" under the battery settings...I hate doze!
Well, since reverting to the default theme, I've enjoyed the calendar widget keeping the current date. But every time since the first time, the alarms still don't go off.
Again, I am using the STOCK alarm and calendar app that came with the Samsung Galaxy Note 5 and its updates, NOT any third-party app. I had been using third-party themes to avoid the stupid whiteness of the new Marshmallow icons (What if I don't want Marshmallow to look like a bunch of marshmallows? What if I liked the Lollipop icons and colors just fine? Eff me.) but reverted to default in a mostly vain attempt to avoid the alarm issues, but the issues persist.
There remains a notification in my taskbar that there is an upcoming alarm at 5:30, even though it's now well past 5:30. The time on the right of the notification is 4:40. So it seems that the clock/calendar's alarm feature is getting stuck in time a little less than an hour before the alarm, and sticks there for hours sometimes, until well past the alarm time. Then sometime far later in time it will suddenly catch up, and HELPFULLY (haha) notify me that I've missed an alarm.
Am I the only one on xdadev that is having this problem with the default app, and default theme? I really wish I could easily revert to Lollipop, since Marshmallow really seems to be a hot mess. I also miss having ADB to push stuff to my FireTV.
Anyone else seeing delayed by some minutes or non existent notifications on the S3?
This is true for text and email notifications
I can not see any settings for controlling the sync rate or anything else that might impact this.
The phone is a note 4
Yeah. There are times that emails never arrive on the watch.
There is a setting that if you are on the phone, you will not get notifications on the watch. You can set this to receive notifications when on the phone.
Notifications will not show if you have "Do not disturb" enabled or if you are using the phone at the time the notification arrives (though this can be disabled)
Also if you are not wearing the watch, you won't get notifications.
I have noticed very odd behavior with my watch as well. I have the LTE version of the Frontier, with NumberSync enabled, but my watch is mostly connected via Bluetooth which I have found means it is disconnected from cellular. It seems that if the Bluetooth is disconnected and reconnected that I no longer receive any notifications, messages, phone calls, etc from my phone (nor NumberSync) until I reboot my watch. According to the Gear Manager on the phone everything is connected and it shows battery stats and such, but nothing gets sent to the watch until I reboot it.
Having same problem!
Since raising this a couple of weeks ago it seems to be a lot more consistent now, in fact I have only noticed one late notification in the last few days.
I have not changed any options on the phone or watch - go figure.
apprentice said:
Notifications will not show if you have "Do not disturb" enabled or if you are using the phone at the time the notification arrives (though this can be disabled)
Also if you are not wearing the watch, you won't get notifications.
Click to expand...
Click to collapse
So DND on the phone will block the notifications on the watch, is that correct? Any way to disable that feature? I often put my phone in DND but would like to get notifications on the watch.
Laban said:
So DND on the phone will block the notifications on the watch, is that correct? Any way to disable that feature? I often put my phone in DND but would like to get notifications on the watch.
Click to expand...
Click to collapse
No, sorry, I meant if you had DND set on the watch.
.
Very strange but since I don't have a notification sound for my stock email app in my phone when I receive an email, the watch is not vibrating when I get an email. If I set a sound notifications I n in the phones mail app the clock vibrates. Feature or bug?
I have noticed that notifications are not recieved on my watch when it doesn't detect its on your wrist, same for always on display, it only works when it detects its on your wrist. It is very annoying as I constantly struggle to get my frontier to detect a heart rate and know it is on my wrist, so therefore the screen is always turning off and I never get notifications going to the watch.
Might be a fix
Been having the same issue for a couple of weeks since purchasing my s3 frontier. While looking through the notifications setting in gear app on phone. I noticed the notifications are only sent when watch is being worn. I was wearing the watch so disabled this feature. Texts began coming in just as fast as on apple watch. Apparently, the gear s3 is not very good at telling if it's being worn. Might be related to inconsistent fitness tracking.
Hey all! I just got the S3 Frontier a few days ago and I love it! Just one complaint:
The other night I had my watch on while I was sleeping. As always, I put my phone on complete silence. However, while I was sleeping, I was woken up a few times by my watch vibrating.
It's kinda silly that I would have to silence the watch, too (in my opinion). Is there any way to "link" the two? I also want my watch to vibrate even when completely off by means of my cell phone's alarm time, even if I have the watch and phone on silent. Is there a way to "link" the two? My phone is a rooted Google Pixel if it matters.
Thanks in advance!
daddylonglegs said:
Hey all! I just got the S3 Frontier a few days ago and I love it! Just one complaint:
The other night I had my watch on while I was sleeping. As always, I put my phone on complete silence. However, while I was sleeping, I was woken up a few times by my watch vibrating.
It's kinda silly that I would have to silence the watch, too (in my opinion). Is there any way to "link" the two? I also want my watch to vibrate even when completely off by means of my cell phone's alarm time, even if I have the watch and phone on silent. Is there a way to "link" the two? My phone is a rooted Google Pixel if it matters.
Thanks in advance!
Click to expand...
Click to collapse
I kind of agree it would be nice if I'm in some setting (doc's office, etc) where I want to silence my phone I have to remember to also put the watch into do-not-disturb.
This is what's missing, and really needed. But there's no way to do it.
the_scotsman said:
This is what's missing, and really needed. But there's no way to do it.
Click to expand...
Click to collapse
Wow, that's crazy! What an oversight! Thanks for the reply though!
Hate revive an old thread, but this does my head in.
I've got a gear s3 classic, I think it makes absolutely no sense for it to no sync the notification volume etc..
Has anyone found a workaround?
#boosamsung
I agree. With Android Wear when You put watch into "do not disturb" phone also switches the same.
I've also noticed that there is no any watchface that shows battery level from phone and watch at the same time..
I like Tizen, but in some cases Android Wear was better. The second is more integrated with phone.
You can set the time for auto do not disturb on the watch. I have mine set from 10:30 until 6:30. The watch doesn't vibrate or notfy me.
Located on watch under Do Not Disturb: set schedule.
You can set different times for different days of the week.
Other way around, just use Tasker to add task like: if phone in silent state, disable bluetooth (to stop connection with gear s3) and exit task is reverse to turn on bluetooth in which reconnect gear s3 automatically
I to wish they would just add a feature to the Gear app for, "Silent Mode Syncing"!
I would think that it would be easy to add such a simple feature compared to all the Samsung Health stuff that they can sync between the Gear and the connected smartphone. But sheesh, guess it's never easy...
Sent from my SM-T800 using Tapatalk
Now does this after update to 4.0?
I think in the latest update for the gear (4.0) it now does this by default! Last night after the update I put my phone on silent. The next morning I had a few missed calls that usually woke me up due to the watch vibration.
Can anyone confirm?
I couldn't find a detailed list of new features for the latest update to check.
samburner3 said:
I think in the latest update for the gear (4.0) it now does this by default! Last night after the update I put my phone on silent. The next morning I had a few missed calls that usually woke me up due to the watch vibration.
Can anyone confirm?
I couldn't find a detailed list of new features for the latest update to check.
Click to expand...
Click to collapse
How are you putting your phone on silent, Do Not Disturb or using the volume? I have Do Not Disturb set to automatically enable on my phone every night but I still get notifications on my watch. I haven't tried it by pressing the volume key and cycling through Ring, Vibrate and Silent though.