No notification sound on phone when connected to Bluetooth?!

djlee0314

Well-known member
Jun 7, 2010
219
1
0
Just got my S10+ yesterday (love it btw) and this is my first time using Android Pie (9.0) as I'm coming from a Note 8. I use a bluetooth headset at work for calls and noticed that when I'm connected to bluetooth that all my notifications go to the headset and no notification sound comes from my phone. I was able to get notification sounds through both on my Note 8.

I did some research and it appears to be a limitation of Android Pie. Am I missing something? I'd really like to have my notification sounds come through my phone AND my bluetooth headset as I don't have my ear buds in all day. Any work around or setting I'm missing?
 
I have the same problem with my new Galaxy S10+. Found this fix, you just have to switch back and forth using SmartThings by swiping down the notification panel. Worked for me.



Once Bluetooth is connected, swipe down notification panel on the main screen. There you see SmartThings, Audio Output. Under it, you will see your bluetooth and My Phone (Galaxy S10) options. Chose My Phone (Galaxy S10) option. Then close the screen.

Swipe down the notification panel again, far right to SmartThings, there are two icons and the right one opens the SmartThings panel. Open it, turn ON all the three options that says Always Show, Audio Output & Bluetooth device. Close the screen.

Go to settings, Connections, Bluetooth, open the settings wheel for the connected bluetooth and make sure both Calls & Audio are turned ON.

This should help with hearing the notification sounds without the need to keep the bluetooth ear buds all the time. You can continue to use the bluetooth for calls.

The only problem with these settings is, when playing Youtube or any media file or streaming video, the audio comes of the phone. All you have to do is go to step 1 above and switch to Bluetooth. When done, switch back to My Phone (Galaxy S10) for calls, notifications etc. It is a very step to switch.
 
Same here I hope a firmware update will fix it I thought it was my phone Verizon replaced it same on this one
 

Forum statistics

Threads
954,080
Messages
6,960,531
Members
3,162,920
Latest member
mespeedie3