Jolla1: audio not routed over bluetooth in 2.1.4.13

"takes a tone in his suggestions that belittles others concerns" ... I cannot follow you in this point. That needs explanation.

@lpr - Here's one obvious example, spelled out for your benefit: "What the comment above said. If you are stupid enough to force a command-line update to an unsupported early release that was postponed because of bugs, don't come here to complain about it" (second comment to the OP).

What's wrong with it, other than the obviously derogatory language? It ignores the fact that this website exists specifically for giving feedback on issues the crop up on the SFOS/Jolla devices – something which is especially important to do after releases to early-access subscribers (like the 2.1.4.13 release was).

In other words, that message is not only needlessly (and pointlessly) impolite, it's also the exactly wrong message to give because it seeks to stop feedback during a period when feedback is especially valuable. Discouraging feedback like this isn't only negative in general, but especially regressive behaviour in the current situation. The message betrays it's author's ignorance about basic open source community behavior and the actual situation behind the original poster's report.

Therefore, that message (and it's like) deserve not only critique but also derision, and it's author should be urged to conduct some serious introspection about how they behaved here.

@sjn : tell that @bocephus and not at my address, thx

You asked for an explanation, I offered one ;-)

@sjn My comment - and lpr's original post - was about 2.1.4.12, which was NOT an EA release. I stand by what I said.

Thank you so much for this, this would be the main reason for me to upgrade when it is made available for all users. Can an EA user confirm this?

It's out now :)

In early access, I mean.

@DameCENO I just upgraded my Jolla 1 from 2.1.3.13 to 2.1.3.14 now. I confirm that the bug has been corrected. I can enjoy my music on my bluetooth speaker again!

Thank you Jolla for the fix!

@jovirkku - as previously commented to you in another bluetooth question, update 2.1.4.14 has still not fixed bluetooth audio routing to my laptop. Sending images and documents is not a problem. It's not a deal breaker for me, but it has worked with previous SFOS versions, so it would be nice to still have the option.

Confirm BT Headset functioning as expected again, I don't remember how the jack+BT scenario played out in the past but now sound does not route to the jack while BT is connected, to me this is a minor issue but 'logically' there should probably be either a prompt asking where you want sound to go or it should go both to analog speakers and headset.

@Edz just curious what is the usecase to route sound from a phone to a laptop?

Thanks for your temporary solution that will definitely help someone, but as you said sad it is not a permanent solution, lets hope Jolla resolves this for good, There are more Jolla 1 users than you might think

@Keeper-of-the-Keys You know what I'll do with my Xperia X tonight ;)

Thanks for the mad trick!

EDIT: I know that was for Jolla 1, but I'm giving it a shot anyways.

...and I failed miserably :(

(a2dp_sink was already active, but still no sound, even after the commands)

@Keeper-of-the-Keys you can also fire it off directly from CLI as

pacmd move-sink-input 443 4

which makes it possible to be included in a custom script. Will work on that. For my own reference, and maybe other's: https://www.mankier.com/5/pulse-cli-syntax

@lakutalo as I recall I always was parsing the output manually to find the right values, but it may be very well be scriptable (haven't needed to use this trick in a while now)

this is only worth a comment not an answer. XperiaX is a different device using different pulseaudio and bluez version than jolla1

Ok. Pardon me for my input, then. I was letting people know that it doesn't affect everyone.

@lpr This thread wasn't worth posting to begin with, so who are you to say what the replies are worth? And in any case, if we're keeping score, deprecated's info was more valuable to me than yours.

there is no need to apologize, but it reads jolla1 in the question text, doesn't it? And this was worth posting but not as an answer. That's all

@lpr I will thank you for your question as a whole, because the info you provided is vital for the Jolla 1 user I am especially since I decided to completely switch to Apple's Airpods. Meaning this issue you pointed out will stop me from upgrading to 2.1.4 unless it is resolved, this is a bug that is intolerable. Moreover there is this tendency to prioritize other devices running Sailfish at the expanse of Jolla 1 is becoming annoying. So if this works flawlessly on Xperia X is not an answer as it doesn't in anyway address the question raised. But it is note worthy that the OS has been taken down from the forum as they plan addressing some fixes first as far as I read, so we can hope this issue is one of them. I maintain my stance this question is as valid as any and should be given as much attention by Jolla as any other issue raised here