Do Not Disturb Mode Turns Off By Itself - Samsung Gear S3

I'm using the scheduled Do Not Disturb function to activate at night, but sometimes, I need to enable it manually during the day. When I do, sometimes, the function turns off by itself and I start getting notifications again. This didn't happen before I started using the schedule function. Does anyone know why this happens and how I might go about fixing it?

I´ve experienced the same problem. Sometimes it occurs, and sometimes not. Didn´t find an answer yet.

Related

Strange thing related to notifications

Ive noticed that sometimes, mostly while connected to wifi, i receive notifications like facebook or whatsapp after i touch the phone which can be in a big delay sometimes, if i dont touch the phone for a while.
it doesnt happen all the time but something like half of the time.
sometimes i get them instantly.
anyone else experiencing this?
pookipsy said:
Ive noticed that sometimes, mostly while connected to wifi, i receive notifications like facebook or whatsapp after i touch the phone which can be in a big delay sometimes, if i dont touch the phone for a while.
it doesnt happen all the time but something like half of the time.
sometimes i get them instantly.
anyone else experiencing this?
Click to expand...
Click to collapse
I'm experiencing the same problem. Happens with Gmail/Gtalk for me (those are the only things I really use those, so I suspect it would happen with other things too). My wifi works completely fine and normal as long as screen as on, but when screen is off, notifications become delayed by at least 5-10 minutes (sometimes more, I imagine). I do not have the problem while on regular mobile data.
Yea I noticed my phone likes to suddenly receive a bunch of notifications after I unlock the phone and do something, or when I get a push notification, suddenly it receives everything else. I think this has to do with the wifi sleep policy/screen-off power management.
Try setting your wifi to stay on when charging, and leave the phone connected to the charger for a while. If your delay goes away then that is one explanation.

[Q] Settings Not Being Saved

I'm wondering if anyone else is has this problem. Every time I plug in my phone, the USB debugging option turns on. I turn it off in developer settings, but it turns back on as soon as I plug it in.
Also, I change my screen timeout to 1 minute but when I restart the phone, it turns back to 30 seconds. I already tried the fix permissions option in Recovery and it didn't work. I'm using the Viper ROM if that helps.
Also, I always turn Auto Sync "on" under settings but it turns itself back off.
Anyone else with the same problem?
Anyone?
There's a known bug with some settings not sticking on reboot if I recall but what your describing does not seem to be this bug. Typically when weird little issues like this are happening, step one is to redownload and check md5 wipe everything and do a fresh flash. Obviously this would be a big issue, well documented for a ROM as popular as Viper XL so I would say no, other people are not experiencing this issue.
Thanks anyway. I'll Google it some more and see if I find something

[Q] Not Receiving Calls/SMS Bug Update

There are a couple threads on this subject but they are all little detail and dead. The links below describe in detail this bug. Is anyone else experiencing/fixed this issue? I am currently running a Tasker task to disable wifi when my screen goes off, which lets calls/sms in most of the time. Every now and then I have to make a call to force texts to come through still.
http://www.androidpolice.com/2014/0...p-receiving-calls-and-text-messages-for-some/
http://www.pocketables.com/2014/03/nexus-5-bug-causes-phone-stop-receiving-calls-text-messages.html
https://productforums.google.com/forum/#!category-topic/nexus/nexus-5/3gVF5Dm-yG0
There seems to be a lot of people with the issue but nothing is coming of it.

[Q] Phone only rings for about one second and then stops.

After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
c4sh said:
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
Click to expand...
Click to collapse
Are you using a custom ringtone?
Aerowinder said:
Are you using a custom ringtone?
Click to expand...
Click to collapse
No, just the stock tones. I find it happening sometimes with my SMS messages as well but not all the time.
Update: I have since unlocked my bootloader (wiped) and rooted my phone and the problem still persist. Seems like I'm not alone, I have starred this so hopefully someone can see it. https://code.google.com/p/android/issues/detail?id=81178#makechanges
Anyone have any suggestions that I could try?
update
I had thought I had fixed the problem by re flashing the stock image of lollipop, the problem went away and my phone started to ring again but shortly its back to only vibrating. I noticed that the little vibrate symbol was popping up in the status bar whenever I received a call, even when I turned off the also vibrate for calls option. I then remembered that when I use the volume butler app and set it to my vibrate profile that symbol would also pop up. I uninstalled volume butler and everything seemed to be working fine. Next I Checked the play store for comments regarding the issue and I noticed two things: There was a recent fix "ringtone changing to silent upon first install" and it said that the app was installed onto my device and not requiring an update even though I had just uninstalled it. So I decided to open it up and it was as if I was starting the app for the first time as none of my previous data was in there for testing purposes I decided to set up the same profiles that I had before and try calling my phone and my phone rang like it should, weird. Perhaps I had two versions and that was the one that I originally uninstalled is that even possible?( I could have sworn I had updated it,as it was under the up to date app list) Regardless, I uninstalled it again and everything is still working as it should. Hoping that this was was the culprit I will continue to test my phone and see.

Android 7- trouble with receiving phone calls

I am new to xda, I hope I found the right place for this problem.
I have a phone which is running android 7, the phone is supposed to be a Samsung s8, but I bought it second hand and it seems to be a mix of many things
Anyway, the problem I am having is that for no apparent reason sometimes when a call is received the phone does show the incoming call and does not ring. The call appears only as a missed call.
The way to reset that works is to delete the cache of the phone app. But that works only for a few minutes and then the problem recurs
It doesn't seem to be consistent, however sometimes it seems like setting the phone to do not disturb or silent mode triggers this behavior, and then even after returning to normal mode, the calls do not appear.
Another thing this that it seems like in safe mode I do not have enough this issue
I am not %100 sure about that either
Any idea what setting could cause this problem?
Thamk you to all who have ny suggestions

Categories

Resources