ringtone sound not routed to speakers while bluetooth device connected

asked 2018-06-04 13:21:19 +0300

DameCENO gravatar image

updated 2018-06-07 15:09:48 +0300

Ahoy Sailors! I have noticed this bug of late, a little too late as it caused me some issues of missed calls. It started with the OS update 2.1.4.X that had this sound not routed through bluetooth headset issue, I think the fix used was a little too aggressive and led to this bug. While connected to Apple Airpods bluetooth devices, the ringtone is not routed to the loudspeaker anymore, only heard on the bluetooth devices. It is a problem because if the devices are not in-ears you could have missed calls right under your nose and not even notice unless your device is in your line of sight or on vibration which I only use when on silent mode. As I earlier mentioned this bug was not present until the upgrade. My device is a Jolla 1. Any suggestions would be greatly appreciated. And yes I did search the forum and no one is talking about this, and I really need help fixing it and normally expect it handled by Jolla.

I just find out that notification sounds like email or sms are played via the phone's speaker while connected to Bluetooth devices, but the ringtone still isn't. Now I don't see how this isn't a bug, even if I was to ascribe to the idea that it was an implementation from Jolla, still the user should have a choice, a setting maybe under ringtone to choose the appropriate behavior? 2.2 has been released to all users and still this issue has barely been noticed. Is the issue fixed in the new release? Anyone? Thanks in advance.

edit retag flag offensive close delete


Thanks for pointing those out, I missed them, but still I am making the point of it starting only after the bug of audio no longer being routed through bluetooth headphones on was reported and rectified. Maybe in the steps jolla took to fix the issue is the solution to this issue of mine being rectified?

DameCENO ( 2018-06-04 16:45:52 +0300 )edit

Just glance through them both @Edz and there isn't a single meaningful output, and that those threads point to Sailfish OS 1.x is kind of scary, this is a bug that just keeps coming back and won't go away...

DameCENO ( 2018-06-04 16:58:23 +0300 )edit