Sometime during night silent mode goes on, and it's on when I wake up. Then I have to use the slider to get the phone back on normal state. Quite annoying. Slider was in normal mode all the night. Anyone else? How to stop that behavior?
This happened to me too. Did you have Do Not Disturb settings set on your prior device and then restore the back up to your OP3? I have read that this is the cause of the problem - the old setting transfers over and there is no way to change them. I went into the global setting for app notifications and reset all apps. This worked for others and appears to have worked for me as well.
Having the same issue here.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Yes, actually I had it on on my OPO and I transferred apps from it to the OP3 using the installation wizard's nfc method. I did the reset, let's see if it did help..
I tested resetting notifications, did not help
Me too. Migrated from my old phone using the NFC transfer wizard. Old phone was setup to go to silent 10pm - 7am. It appears the setting is transferred over but at 7am the OP3 doesn't exit silent mode. I then have to toggle the switch to take the phone out of silent but still seem to have issues with notifications sounds afterwards.
I solved it by installing new custom rom and I didn't use restore function this time..
i too am having this issue. i attempted resetting all apps settings but that didn't work.
has anyone figured out how to fix this without factory reset or installing a custom rom?
Add me to the list and I set it up as a new device. Only had the phone a day before I applied the 3.2.0 update so I can't say if was happening before. Hope there is a fix for this soon.
IMO this is because Google is syncing the DND preferences from your Google account, regardless of whether you used the the whole "set up nearby device" thing
I have this issue except Silent mode automatically turns on throughout the day for me. I have factory reset my device and setup the device as new and the issue continues. Now I'm really unsure how to fix this.
Same issue and updating to 3.2.1 didn't fix it.
I've the same issue!
I've noticed that the sound (also from the notifications) can be turned on again (for that day) by switching off, and on the Alert Slider, and then adjusting the volume-sliders in settings.
I don't think it's a Google issue as I have 4 different phones on my account in the last month and none have done this. Just ordered another 6P while they were 20% off in warehouse deals so I'll swap over to this phone Monday and see if the issue follows. For now I'm playing with Tasker to reset all the volumes at 7am.
I've got the same issue. But I did not transfer any settings to my op3.
There's nothing in my "do not disturb" menu, and nowhere to set up automatic silent mode, as far as I can see.
Same issue faced, no solution or fix found up till now.
Me too facing the same problem.. Even in day time it goes automatically to silent mode. So incoming calls doesn't sound and it solves only when I restart the phone.. And after sometime the problem is occurring again and again.. Does anyone found the solution?
I had the same problem in my opo too..
Same here. Since the 3.2.1 update my OP3 sets to Silent overnight. Some has said it's True Caller Spam Blocker, but as I don't have this it's not a solution for me. Tried the usual reset but no luck. Really need a fix for this as I need to get important calls/texts overnight. Not a hardware problem that I can see as fine before update; broken afterwards, and the physical switch works very well.
Also, I've not used any restore function whist setting up.
It would be useful if people experiencing this problem could mention it on the OP support forum. I'm using the threads...
https://forums.oneplus.net/threads/do-not-disturb-notifications-problem.451989/page-7
https://forums.oneplus.net/threads/possible-bug-with-oxygen-3-2-1.455413/
yes - please do and add @oneplus to your answer to adresse OP team directly. Thanks.
This is related to OOS only, i installed custom rom CM based nd didn't face this issue. Then installed.OOS no restore setup as new device still same issue with no ringtone.
The fix should come from Oneplus
Related
Vibration on Notifications (such as email) is no longer working. It definately used to and i have checked the email settings and it is definately set to vibrate but it has just stopped working. it vibrates fine for incoming calls so the vibration definately works
Has this happened to anyone else and anyone know what might be up with it?
Thanks
First: Have you rebooted the phone?
I've also had this issue. Unfortunately, I also did what is suggested somewhere: Hard-Reset. It's not THE solution, but a solution nevertheless.
yeah ive done many reboots but still the same. I really really dont wanna do a hard reset as ive got all my apps and themes set up just how i want them
I feel for you guys cause I was there yesterday. It was probably my post you read about hard reseting.
Just to reiterate, this is what I tried without success:
* repeated rebooting
* unticking all of the vibrate choices and reticking them
* unticking all of them, rebooting, reticking test and reboot and test
* uninstalling all of my apps, one by one
* hard reseting and choosing to reinstall the automatically saved backup from the SD card.
What worked for me in the end was a hard reset (I used the volume down-power button method), and opting NOT to reinstall the backup data from the SD card.
Do you guys remember what you did prior to noticing this? Some have said running the battery down low, but I suspect it's some app that was installed or updated that causes it. I'd like to know so as to avoid having to hard reset again (cause it is a real PITA).
For me, in the day or so before it occurred, I had run the battery down low, had several app updates and had wifi network problems causing my Exchange email to hang, so I can't really narrow down what the cause was.
hmm, i cant pin it down to any app i installed but i also let the battery run right down ( so that the phone turned itself off). This seems to be common amongst the few people that have had the problem but we cant be sure unless someone does it who currently doesnt have the problem
Ok, ive found a solution elsewhere in this forum which means you dont have to hard reset your phone to get the vibrate working. If you download a program called 'sound manager' you can change the phones notification vibration settings. I have tried this and it is now vibrating fine for me when i receive notifications. If you want it, heres the link to the thread:
http://forum.xda-developers.com/showthread.php?p=5982672
it seems from everyones experience that this issue is caused by the battery going real low and it electing to turn off vibration to save battery, but never turns it back on when the phone is charged.
This phone seems real buggy to me...
So this just started a few days ago, I noticed that the notification sounds stopped working. Locking the phone stops making a sound and all notifications are silent. Watching videos and incoming calls are audible however.
A reboot fixes the issue, but it returns soon after.
I didn't install any new apps recently. Updated some, but nothing new.
Any ideas?
Same thing happened to me upon upgrading to 8.1 If I reboot it solves it for a little, but shortly afterwards no notification sounds again. Not sure if anyone has found a solution or are having the same issue?
Same exact problem here. Very annoying. I'm thinking of trying a factory reset.
If you do a factory reset let us know if it works, I've been thinking the same, if I do I'll let you know.
I thought I was the only one having this issue. Randomly comes on and off.
Sent from my [device_name] using XDA-Developers Legacy app
crazyd1721 said:
I thought I was the only one having this issue. Randomly comes on and off.
Click to expand...
Click to collapse
I checked the sound settings after updating to 8.1. All of them had changed to silent or something else you couldn't hear. I reset every sound, alarm, ringtone, notifications, etc.
I have to do this after every update. This is due to the fact, that I use the factory image to update.
So, I think this happens when I use a bluetooth device.
I notice that after I disable Bluetooth after using a headset for a bit, that the sounds stop. Anyone else can test this theory out?
You may be on to something. I use the bt with my car everyday. Noticed the same thing.
Squatrack Curler said:
So, I think this happens when I use a bluetooth device.
I notice that after I disable Bluetooth after using a headset for a bit, that the sounds stop. Anyone else can test this theory out?
Click to expand...
Click to collapse
notification problem
Squatrack Curler said:
So, I think this happens when I use a bluetooth device.
I notice that after I disable Bluetooth after using a headset for a bit, that the sounds stop. Anyone else can test this theory out?
Click to expand...
Click to collapse
After 8.1 on my pixel XL notification sounds have stopped working. I determined that it has something to do with the bluetooth. After connecting bluetooth and then turning it off that is when the problem happens. But, oddly enough, notifications sounds do work again when bluetooth is turned back on and connected....but stop again after bluetooth is turned off. A reboot fixes the problem but it happens again once bluetooth is used and turned off again. Please fix it Google.
Same for me but I only lose the Google Voice text message notification and a reboot fixes it.
It happened to me connected and not connected to Bluetooth. It would also happen to calls as well, missed some important phone calls because of it.
I am having the same problem. I'll check to see if BT connectivity is the trigger.
Same thing happening to me.. I use bluetooth daily too.
I am having the same issue. Any fixes? Has Google acknowledged?
Still happening with me. I have to reboot every few days to fix it. Very annoying.
Happening to me as well, specifically for text notifications. Sometimes the sound is triggered, sometimes it isn't.
I rebooted more than a week ago and it hasn't returned and I use a Bluetooth headset and Bluetooth in my car daily. I haven't gotten the January security patch, wondering if they slipped a fix in there?
Sent from my BTV-W09 using Tapatalk
I was having the same issue. I think it started after one of the security patches. I contacted google's support. they had me put it in safe mode and then see if it comes back. I did that, and it seemed to not break in safe mode. In theory, that means it is not a google issue, (Im sure they will play it that way) but Im not sure if it is caused by bluetooth, or something else. Anyone having the issues using a smart watch connected to it?
This is very annoying. I am still having this issue that started shortly after 8.1. Notification sounds stop working. A reboot fixes is it but the problem comes back shortly thereafter,,sometimes within 24 hours. Interestingly, the notifications still work while bluetooth is connected...not sure what to make of that. I am loathe to do a factory reset but if anyone has done it with success please let me know. Thank you.
Same thing here. I'm contacting Google regarding the issue. I've noticed a similar symptom since I've been using an android watch:
my watch gets notifications on time but my phone doesn't react. When i clear the notifications from my watch, my phone sets off multiple notifications in a row. Example: text, text, email, email, email, email, email, text, calendar. It's very annoying.
Now my phone makes no notifications. I've changed all notification sounds to full volume, I turn off bluetooth completely and my phone only vibrates for calls and doesn't make notification sounds or turn on the display as they come in.
While connected to a bluetooth device, the notifications come through that device but nothing or vibrate only on my phone.
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
sb1893 said:
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
Click to expand...
Click to collapse
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
sb1893 said:
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
Click to expand...
Click to collapse
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
sb1893 said:
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
Click to expand...
Click to collapse
The saga continues. The issue occurs immediately after the first call I attempt when connected to my BMW bluetooth system. From that point on, I experience a 30 sec to 3 min delay between attempting to make a call and the Pixel XL actually initiating the call. The quickest way I have found to resolve the issue is to plug the phone into a charger for a few seconds and I am then again able to place calls. I have verified that the BMW bluetooth software is up to date and has not been updated in over a year. (Again - this issue just started happening yesterday...and I've been on Feb security patch for several weeks). I just cleared cache from within Titanium Backup. Will see if that improves the situation. Very weird. I also was just able to recreate the issue using just a simple Plantronics headset. So I continue to think it is something related to the Bluetooth stack on the phone. But I am not sure how to check to see if any of that has been updated via app update since I upgraded to Feb security patches. (I reproduced the issue at my desk using the headset after clearing cache.)
S
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Racermanz said:
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Click to expand...
Click to collapse
No - but I'm at least somewhat encouraged to know I am not the only one dealing with the issue. Today I flashed factory images (but preserved my data by removing the -w from the flash-all.bat)...that did not resolve. I've tried the reset app preferences, reboot suggestion I found elsewhere - no dice. Google pushed a new Phone app yesterday - that also did not resolve. I've even tried uninstalling Magisk completely and dropping back to 15.4 - also no help. I'm running out of ideas. I've taken to carrying a charging cable in my car...so if I absolutely need to make a call when the phone isn't behaving, I can just quickly plug it in...which does clear up the issue temporarily. Also keep a charging cable at my desk now...so I'm limping along..but for an issue that just appeared out of nowhere this week...it's been pretty frustating to deal with. Also - I no longer believe being currently connected to Bluetooth is related to the issue. I've been able to get the issue to occur today while not connected to any bluetooth devices.
Try
settings>system>developer options>media>disable USB audio routing
DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Thanks bros. This is such a strange bug. Right now it works before I have turned off USB audio routing. I have turned off USB audio routing. I will report back if this DOESNT work. If I don't post again we can assume this works.
Thanks DR3W5K1, great name bro.
DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Just tried to toggle on, which looks to mean Disable. Then rebooted. No luck. Issue still occurs. Thanks for the suggestion. Willing to try anything even to just eliminate as possibility at this point.
Well - I have found a better workaround. When you attempt a call, if you get no response, you can toggle Airplane mode "ON"....You will then see the call you attempted fail. When you turn Airplane mode back "Off" you can can successfully make calls again. Better than having to plug into a charger cable to get the attempted call "unstuck"....still no idea what is going on....but this workaround at least is more palatable, portable, and take a few seconds...hope someone can figure out root cause soon and a proper fix becomes available.
EDIT: Even better workaround. Toggling Mobile Data OFF and ON has the same effect of clearing the issue. And works better when connected to Bluetooth in car as those connections will be maintained vs. using Airplane mode toggle. So - issue seems to be related to Mobile Data somehow - but I have already had Advanced Calling / LTE, etc...turned off as one of my first steps in troubleshooting this issue.
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
The.Yield said:
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Click to expand...
Click to collapse
I have tried that. Sorry for not mentioning it in this thread. At one point I revoked "Phone" permission from all apps other than Phone, Carrier Services, and Contacts. Rebooted. Issue still occurred.
DR3W5K1 said:
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
Click to expand...
Click to collapse
Ahhh...I had forgotten about this secret menu. Looks like I could permanently toggle off VoLTE, WifiCalling, etc...here. But - not sure I want to go that route...I'm OK at present with Toggling Mobile Data via Quick Settings tile. And hopefully this issue eventually gets solved as mysteriously as it was introduced via some update.
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
tesla45 said:
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
Click to expand...
Click to collapse
Interesting....I'm on Verizon and I do believe that they route calls over Mobile data at times. I'm going to stay tuned, but likely done with much more deep investigation at the moment. I've spent enough time down this particular rabbit hole and the Mobile Data toggle is workable for me (not ideal, obviously)...hopefully a permanent fix materializes soon. Thanks to all for their suggestions and moral support. Much appreciated.
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Install the stock again clearing all the data. Don't restore anything with titanium or install any extra apps. Then make a call.
tesla45 said:
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Click to expand...
Click to collapse
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
sb1893 said:
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
Click to expand...
Click to collapse
Glad the workaround helps you too. My emphasis CAPS in my last post was clearly misleading, I was actually suggesting NOT to reinstall/factory reset because I don't believe that solves the problem long term and its a huge ask for a customer (when really Google should be solving this problem for us).
Based on this little workaround its clearly a software problem that Google needs to address, I've raised the issues on many threads in their product forums ... hope it gets to the right people ASAP because I believe lots of Pixel users are running into the problem (both Pixel 2 and 1st gen, another indication its NOT a HW problem).
Keep the workarounds coming folks!
Hello,
I'm from Morocco and currently using a XIAOMI REDMI NOTE 8, (64Go/4Go), running the latest version of MIUI 11.0.11.0 Global stable with Android 9.
So i'm having this really annoying problem whith the notification when the phone is closed. So basiclly the sound of the notification should come at the time of recieving the notification but in my case there is a delay of 2 to 3 min or even more than that sometimes. And even sometimes the sound is not heard at all even with the notification is recieved. Only the light bulbe for the notification is blinking.
This problem happened especially with the Whatsapp application. Everything in the notifications seetings is on, all permission are granted, locked the app in the recent app, turned on autostart, disabled battery saver even though i don't use it at all, put no restriction on the app, turned on background data. I've tried to use different network connection still the same problem. I don't seem to find a reason why would this happend and find a solution for that. I did perform a factory reset but doesn't seem to be fixed. Everything in the begining was working fine no issue at all. I don't seem to remember when it start to happend, I've asked my freinds owning the same device if they are facing the same issue all of them denied. So the question is if all the devices have the same software that they are operating on they should have the same bug or problem if i wan't to say. But not in this case. I have not installed any 3rd party app that has to do with the battery at all.
I do use my mom's phone to test this out. The phone is on everything works perfectly. I locked the phone and the problem start. It's like ther is something that shut the notifications immediately when i close the phone (dnd is not activated also battery saver as i mentioned earlier). So if there is any kind of solution to this problem please help me with or if there is a dev please let them know to fix this issue. I did reported it in the feedback section on the phone 10 times in the time of writing this thread. I'm currently waiting for the new update hoping that it will fix the problem otherwise this is really disappointing. The best selling phone in the market facing issue like this, that's not very acceptable at all. This made me miss a lot of important notifications. Hope that it will be fixed as soon as possible.
If you want to help me and you need any more info please leave me a comment and i will send them to you (screenshots of the settings etc....).
Thanks for your time.
Stay safe.
Have a nice day.
Hamza_note8 said:
Hello,
I'm from Morocco and currently using a XIAOMI REDMI NOTE 8, (64Go/4Go), running the latest version of MIUI 11.0.11.0 Global stable with Android 9.
So i'm having this really annoying problem whith the notification when the phone is closed. So basiclly the sound of the notification should come at the time of recieving the notification but in my case there is a delay of 2 to 3 min or even more than that sometimes. And even sometimes the sound is not heard at all even with the notification is recieved. Only the light bulbe for the notification is blinking.
This problem happened especially with the Whatsapp application. Everything in the notifications seetings is on, all permission are granted, locked the app in the recent app, turned on autostart, disabled battery saver even though i don't use it at all, put no restriction on the app, turned on background data. I've tried to use different network connection still the same problem. I don't seem to find a reason why would this happend and find a solution for that. I did perform a factory reset but doesn't seem to be fixed. Everything in the begining was working fine no issue at all. I don't seem to remember when it start to happend, I've asked my freinds owning the same device if they are facing the same issue all of them denied. So the question is if all the devices have the same software that they are operating on they should have the same bug or problem if i wan't to say. But not in this case. I have not installed any 3rd party app that has to do with the battery at all.
I do use my mom's phone to test this out. The phone is on everything works perfectly. I locked the phone and the problem start. It's like ther is something that shut the notifications immediately when i close the phone (dnd is not activated also battery saver as i mentioned earlier). So if there is any kind of solution to this problem please help me with or if there is a dev please let them know to fix this issue. I did reported it in the feedback section on the phone 10 times in the time of writing this thread. I'm currently waiting for the new update hoping that it will fix the problem otherwise this is really disappointing. The best selling phone in the market facing issue like this, that's not very acceptable at all. This made me miss a lot of important notifications. Hope that it will be fixed as soon as possible.
If you want to help me and you need any more info please leave me a comment and i will send them to you (screenshots of the settings etc....).
Thanks for your time.
Stay safe.
Have a nice day.
Click to expand...
Click to collapse
1. Turn off miui optimization under developer options
2. Give all permissions, no battery optimization to google play services and framework. Before doing this, clear data of those apps(removes google account!).
3. Check if it's added to game turbo or not
These are some more possible solutions. After checking all those, reboot once and check if the problem is solved or not.
Pavello said:
1. Turn off miui optimization under developer options
2. Give all permissions, no battery optimization to google play services and framework. Before doing this, clear data of those apps(removes google account!).
3. Check if it's added to game turbo or not
These are some more possible solutions. After checking all those, reboot once and check if the problem is solved or not.
Click to expand...
Click to collapse
Hello,
Thanks for you response. I've already done what you did sggest to me but still the samething always late notification sound.
It's not added to game turbo i don't even use it and it's disabled. Google play services and framework don't have any kind of restrictions whatsoever. I don't want turn off miui optimization cuz it mess up with a lot of visuals.
I think it's a software issue. Because sometimes when i want to change the ringtone and i tap on a different one it took a lit bit of time to play it same thing when changing the notification. This problem is happening when the phone is locked only.
I'm cuurently waiting for the new update with a hope that it will fix it.
Thanks again.
have a nice day.
Hi all,
Hoping someone brighter than me can figure this sound issue out.
THE PROBLEM:
Half of my sounds don't work, rendering my phone useless in the current state. As the title says, Ring, Notification, & Alarm sounds do not work. You know, as in the important stuff that makes your phone, a phone? And makes you wake up in the morning? None of these respective sliders under Sound & Vibration settings make any noise when making adjustments. By contrast, my Media and Call volume sliders DO make noise when adjusting. And sure enough, once on a phone call, I hear things just fine (Call). And YouTube, Spotify, et al. (Media) also work just fine.
Because some sounds work but others don't, this has to be a software issue, right? This would be easy if it was hardware and 0% of sounds worked, but nope, it's partial.
BACKGROUND:
This pixel 3 xl is relatively new to me, but has ran A10 and A11 with a few different ROMs with 100% of sound working flawlessly. But out of nowhere, sounds suddenly stopped working correctly as described above. And it didn't occur immediately or shortly after a new rom flash or update or anything like that. Just stopped working, months into a well-running ROM.
I've tried a couple different ROMs now to fix the issue from a completely clean install (/format data + flash latest google factory image as 1st step) but none have fixed the issue. Specifically, pixeldust (A11) and evolutionX (A11) were my latest troubleshooting attempts with no avail. Pixeldust was the ROM that was formerly working and then after months of 100% sounds working, suddenly stopped.
It's odd that searching throughout the ROM threads that no one else seems to be having this issue. Again, this would be easy if it was a hardware failure. But that doesn't explain how it works for Youtube/Spotify but not for other things, so it has to be software.... I think?
I figured I'd start a thread here rather than start posting in each and every ROM I've tried to troubleshoot this. Thank you!
This might not be relevant because I'm using stock Android on a Pixel 4a but my notifications have gone silent and this report was the only similar search result I found. I tried changing the notification tone and none of them played a short snippet so I'm wondering if the problem is there.
I have not found a solution for this issue.
One thing I noticed recently is that when I'm on a call using the regular "earpiece" or whatever it's called (which works fine), if I switch to speaker phone, I can't hear anything. I have to switch back to the non-speaker ear mode and I can hear the call again.
xdateddybear said:
This might not be relevant because I'm using stock Android on a Pixel 4a but my notifications have gone silent and this report was the only similar search result I found. I tried changing the notification tone and none of them played a short snippet so I'm wondering if the problem is there.
Click to expand...
Click to collapse
ManImCool said:
I have not found a solution for this issue.
One thing I noticed recently is that when I'm on a call using the regular "earpiece" or whatever it's called (which works fine), if I switch to speaker phone, I can't hear anything. I have to switch back to the non-speaker ear mode and I can hear the call again.
Click to expand...
Click to collapse
I think I may have finally found the solution!! Sometimes it's the simple things in life that work, rather than reflashing a billion different ways that finally gets things working again.
In this case, I simply cleared the cache and storage for the 'Sounds' apps under Settings -> Apps & notifications -> See all apps -> Click 3 dots in upper right corner -> Show system. Then, I deleted cache and storage for TWO apps, both called 'Sounds' with 2 different icons. I'm not sure which is the system app and which is not nor do I know if clearing only one of them was necessary, but this is what has worked for me and has survived several restarts thus far. Good luck!