Notification sounds stop working randomly - pixel XL android 8.1

gerrya

Member
Sep 9, 2013
30
3
0
Definitely related to making a phone call. I was just on the phone for 25 minutes I got off and notification sounds were no longer working
Were you using the handset or on Bluetooth during the call? I got a phone update yesterday, wondering if that could be a fix??

Sent from my BTV-W09 using Tapatalk
 

jskinvest

Member
Jul 10, 2016
27
3
0
Were you using the handset or on Bluetooth during the call? I got a phone update yesterday, wondering if that could be a fix??

Sent from my BTV-W09 using Tapatalk
I was on the handset, not bluetooth. My latest phone update was December 14...right around when the problem started. You got an update yesterday? What version of the phone app are you on?
 

gerrya

Member
Sep 9, 2013
30
3
0
I was on the handset, not bluetooth. My latest phone update was December 14...right around when the problem started. You got an update yesterday? What version of the phone app are you on?
Phone app Version is: 16.0.182967520. I have not had the problem since I got the January security patch about a week ago.

Sent from my BTV-W09 using Tapatalk
 

mrgale79

New member
Jan 26, 2018
1
0
0
Still having issues here. From a fresh reboot, I have all notifications. After connecting to any Bluetooth device and then disconnecting, I lose sound for certain notifications. I believe I still consistently get sound from the "Messages" app, but Hangouts is a no-go. Others seem to be inconsistent. It'll vibrate, but no sound. All settings are fine. It's clearly a glitch in the 8.1 update.
 

jskinvest

Member
Jul 10, 2016
27
3
0
Still having issues here. From a fresh reboot, I have all notifications. After connecting to any Bluetooth device and then disconnecting, I lose sound for certain notifications. I believe I still consistently get sound from the "Messages" app, but Hangouts is a no-go. Others seem to be inconsistent. It'll vibrate, but no sound. All settings are fine. It's clearly a glitch in the 8.1 update.
This morning the notification sounds stopped​ again, only 17 hours since my last reboot. Again, it happened right after a phone call. This is getting so annoying and frustrating I am really thinking of switching to an iphone god forbid. At least when they have an issue they correct it quickly. Google experts...please advise.

And yes, the problem started right after the 8.1 update.

---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------

Phone app Version is: 16.0.182967520. I have not had the problem since I got the January security patch about a week ago.

Sent from my BTV-W09 using Tapatalk
My phone app is still on version 15 from December. I wonder why it hasn't been updated.
 
Last edited:

gerrya

Member
Sep 9, 2013
30
3
0
This morning the notification sounds stopped​ again, only 17 hours since my last reboot. Again, it happened right after a phone call. This is getting so annoying and frustrating I am really thinking of switching to an iphone god forbid. At least when they have an issue they correct it quickly. Google experts...please advise.

And yes, the problem started right after the 8.1 update.

---------- Post added at 08:00 PM ---------- Previous post was at 07:57 PM ----------



My phone app is still on version 15 from December. I wonder why it hasn't been updated.
I just now got another phone app update from the play store, now the version is: 16.0.183307769

Sent from my BTV-W09 using Tapatalk
 

Candy[MAN]

Senior Member
Oct 7, 2009
639
170
0
Orangeville
I have the same issue on my Nexus 6P running 8.1 Jan 2018 release. This issue has been present since the 8.1 DP1.

I lose sound 4 to 5 a day as I am constantly on my phone for work. So I am constantly rebooting it to fix the issue.
Today I turned off bluetooth (which I use to connect my Huawei Watch) and i never lost sound. I notice that I lose it when I have BT on and I am on a longer phone call. But today with BT off, I was on short and long calls but never lost sound. Notifications and ringtone worked.

Something is wrong with bluetooth in 8.1.
 

jskinvest

Member
Jul 10, 2016
27
3
0
I have the same issue on my Nexus 6P running 8.1 Jan 2018 release. This issue has been present since the 8.1 DP1.

I lose sound 4 to 5 a day as I am constantly on my phone for work. So I am constantly rebooting it to fix the issue.
Today I turned off bluetooth (which I use to connect my Huawei Watch) and i never lost sound. I notice that I lose it when I have BT on and I am on a longer phone call. But today with BT off, I was on short and long calls but never lost sound. Notifications and ringtone worked.

Something is wrong with bluetooth in 8.1.

It just did it again. 19 hours after a reboot notification sounds stopped working. What is going on here? Why can't Google fix this? This is unacceptable.
 

exodus1337

Member
Jan 27, 2012
13
1
0
So I may have a temp fix.. It appears to work for me and the custom ringtones I have..

Go to Battery – Settings (three vertical dots top right) – Battery Optimization, open the All apps section from the drop down menu, go to the relevant apps anything that says ringtone, txt, sms, call, etc..., and tap on “Don’t optimize.” Then reboot your phone..

So far, users have reported that this doesn’t affect battery life significantly either.
 

jskinvest

Member
Jul 10, 2016
27
3
0
So I may have a temp fix.. It appears to work for me and the custom ringtones I have..

Go to Battery – Settings (three vertical dots top right) – Battery Optimization, open the All apps section from the drop down menu, go to the relevant apps anything that says ringtone, txt, sms, call, etc..., and tap on “Don’t optimize.” Then reboot your phone..

So far, users have reported that this doesn’t affect battery life significantly either.
That does not work
 

rhaag71

New member
Nov 25, 2010
2
1
0
Same issue here, first my girlfriend's Pixel XL started having this issue for about 6 weeks give/take a little. Now mine started doing it this morning, I noticed when my alarm was vibrating only. We both have the Pixel XL from Verizon. This evening I realized I have the same issue as she does (and the others in this thread) when I missed text sounds and call sounds. We both have the Jan 5th update, I think it was the security patch. Sure would be nice to find a solution to this :good:
 

rkingsparx81

Senior Member
Sep 13, 2010
212
55
58
Well guys I side loaded the new Feb update and it completely fixed the sound bug issue. Everything works as it should no more reboots to get the sound back working
 

seangeezy12

Senior Member
Oct 25, 2011
680
77
0
Orbit City
its not the bluetooth, its a Jan security issue i believe. i noticed it after the update. i would have to reboot to get sound back for my texts and etc. Feb update should fix this.
 

jskinvest

Member
Jul 10, 2016
27
3
0
Same issue here, first my girlfriend's Pixel XL started having this issue for about 6 weeks give/take a little. Now mine started doing it this morning, I noticed when my alarm was vibrating only. We both have the Pixel XL from Verizon. This evening I realized I have the same issue as she does (and the others in this thread) when I missed text sounds and call sounds. We both have the Jan 5th update, I think it was the security patch. Sure would be nice to find a solution to this :good:
I am happy to say that I have not had the problem since I disabled doze mode for the phone and message app in the battery settings and then rebooted It has been a week since i did it and I have not had a problem. Let's hope it stays that way.

---------- Post added at 03:41 PM ---------- Previous post was at 03:21 PM ----------

I am happy to say that I have not had the problem since I disabled doze mode for the phone and message app in the battery settings and then rebooted It has been a week since i did it and I have not had a problem. Let's hope it stays that way.
DIsregard my last post. Wouldn't you know it, right after I posted that it was fixed the problem resurfaces right after a long phone call. Unbelievable.
 

rhaag71

New member
Nov 25, 2010
2
1
0
I am happy to say that I have not had the problem since I disabled doze mode for the phone and message app in the battery settings and then rebooted It has been a week since i did it and I have not had a problem. Let's hope it stays that way.

---------- Post added at 03:41 PM ---------- Previous post was at 03:21 PM ----------



DIsregard my last post. Wouldn't you know it, right after I posted that it was fixed the problem resurfaces right after a long phone call. Unbelievable.
Dang :) I had disabled doze for phone, messages, and the clock app, at least from a high level view it makes since that doze would cause such a behavior. I'll put them back. @rkingsparx81 says the Feb update fixes it, that is good news. I'll probably just wait at this point unless it gets too awful then I'll try sideloading it too. Thanks!
 
  • Like
Reactions: rkingsparx81

0ri0n

Senior Member
Feb 27, 2007
129
35
0
Attleboro, MA
Dang :) I had disabled doze for phone, messages, and the clock app, at least from a high level view it makes since that doze would cause such a behavior. I'll put them back. @rkingsparx81 says the Feb update fixes it, that is good news. I'll probably just wait at this point unless it gets too awful then I'll try sideloading it too. Thanks!
Im on the February 5th update, and it still happened to me today.
 

jskinvest

Member
Jul 10, 2016
27
3
0
Got the Feb. security patch yesterday. Exactly 24 hours later the notification sounds stopped working. I am beyond frustrated.
Just lost notification sounds again. 86 hours after the last reboot and once again immediately after a phone call. Google are you paying attention?
 

jskinvest

Member
Jul 10, 2016
27
3
0
Same issue here, first my girlfriend's Pixel XL started having this issue for about 6 weeks give/take a little. Now mine started doing it this morning, I noticed when my alarm was vibrating only. We both have the Pixel XL from Verizon. This evening I realized I have the same issue as she does (and the others in this thread) when I missed text sounds and call sounds. We both have the Jan 5th update, I think it was the security patch. Sure would be nice to find a solution to this :good:
It did it again. 48 hours after a reboot. C'mon Google...what is the deal?