Alarm no longer works on Priority Mode after T-mobile Note 3 update 1/11/16

[Feoen]

I installed this update on my stock T-mobile Note 3. Now, alarms do not sound while in "Priority Mode" (the star at the top of the screen). Alarms will only sound if I am in Vibrate Mode, or if I have the volume up. (Obviously, nothing sounds if in Mute mode, as expected)

I had always used this phone in Priority Mode at night so that I would not be bothered by texts/emails/calls but could be woken if needed in emergency using emergency contacts, and woken by my alarm. I was late to work by an hour this morning because my alarm didn't go off, and I just assumed that I silenced it in my sleep (odd, since I have never done that in the 2+ years I've owned this phone). Glad I tested the alarm before going to bed tonight.

Can others please test whether Alarms are broken in Priority mode after this update?

 

[B. Diddy]

Welcome to Android Central! Have you already tried a cache wipe, which can be helpful after system updates? https://support.t-mobile.com/docs/DOC-11017

 

[Feoen]

Unfortunately, I have already tried a cache wipe. I have subsequently completed a System Format on my phone, and I continue to have this issue.

It appears that the recent update has broken this feature. This is very frustrating and I hope that T-mobile listens and can roll out a patch as soon as possible. I rely on Priority mode.

 

[digihorse]

I also have the exact same issue, and have tried the cache wipe as well. No go. Frustrating.....

 

[DJGru]

Feoen,
I too suffered the same situation. I took it one step further. Yesterday I called Tmobile and explained how my alarm no longer works in priority mode. Tmobile didn't know much about the situation and said we'll just send you a new refurbished Note 3 which i got today. WELL same problem on a fresh Note 3 with no installed 3rd part apps. (No Conflicts). The only thing i did was update the phone as directed to the new update...I guess it was from Samsung. Called Tmobile again to get "you can call Samsung" so here's the number to Samsung which I will call in the Morning 888-987-4357.
I will report after this discussion with Samsung.

Not happy about having something then having it removed without my permission. I use my alarm EVERYDAY, more than any feature of the phone. I know Tmobile tested this update from Samsung but seems to take zero responsibility other that here's an 800 number go figure it out. I wonder how Tmobile would react if they didn't get my monthly payment and I blame the non payment on my bank and I give them a 800 # and tell them to figure it out. Not a cool way of doing business!

More to come tomorrow.....

 

[DJGru]

Just talked with Samsung. Here is THE solution for your alarm not making a sound after the update. Samsung told me to go to Best Buy and have the phone "flashed". What he meant was I need to go back to Kit Kat and I will have my alarm back. Samsung said they were unaware of this issue.....hard to believe because its all over the internet. After too much time for research, I have come up with the thought that NO ONE at Samsung or Tmobile cares about this issue. Nor will they.....sounds like planned obsolesce to me! Why would they take away a Major feature and then have ZERO plan to replace it. Samsung / Tmobile you just lost a VERY loyal customer, not good enough. Today, I will buy the Nexus 6 and be done with the crap filled non-functioning Samsung.

Good luck

 

[digihorse]

Yeah... I'm a bit curious about the fact that for me... the update came exactly 1 day after the phone was paid off. Hmmm.... Would seem to be a good way to try to force a customer to upgrade. I wonder how many other experiencing the same problem had it occur shortly after pay off.

 

[recDNA]

If you were flashed back to kitkat wouldn't you just get the update again in a few days?

 

[Rukbat]

You would - unless you disabled the updater app, which you'd have to be rooted to do. (Or you flashed a KitKat ROM that had the updater app removed, which most of them do.)

 

[JRBC]

Alarm still didn't ring in Priority Mode despite wiping Cache partition as you suggested.

I therefore installed the app 'Alarm Clock Plus'* and the alarms still work with 'Priority' in force. The app even has the option to speak the time just before the alarm. One thing it doesn't do is show the 'alarm' symbol at the top of the screen when an alarm is set, but not a huge deal.

I also cancelled any alarms in 'Clock' for safety. The only thing that doesn't work with Alarm Clock Plus is changing the alarm ringtone. Whatever you choose it always gives you the default 'Morning whatever'...which is ~OK, but not very jarring which I would prefer, so I set all the volumes to 'High' and it seems ok. Let's see if it wakes me up tomorrow!

*It comes with Ads for Free, or with No Ads for $0.99. The app is a red circular symbol with a '+' in the middle.