Ask / Submit
19

Jolla1: audio not routed over bluetooth in 2.1.4.13

Tracked by Jolla (In release)

asked 2018-02-16 20:00:08 +0300

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2018-09-03 10:57:36 +0300

lakutalo gravatar image

On my jolla1 device, since update to 2.1.4.12 and 2.1.4.13 lapuanjoki bluetooth audio routing - jolla1->BTdevice - doesn't work anymore, internal speaker is used for playback² (tested with three¹ BT devices - pairing does work). Was no problem in 2.1.3.7...

¹BTdevice1: a2dp
BTdevice2: a2dp, avrcp
BTdevice3(opensuse notebook - bluez5): sync, opp, ftp, a2dp, avrcp, pbap, map, did,

² even if analogue 3.5 mm connection is established internal speaker is used in case of an active a2dp BT pairing...

EDIT: sorry guys, but the bug seems partly still present in 2.2.0.29, e.g. [here] -> a2dp/avrcp (if this is of any relevance)

edit retag flag offensive close delete

Comments

2

Basically, it's still too early to report 2.1.4.xx issues. The EA release has been postponed for serious reasons. Please wait and see.

objectifnul ( 2018-02-16 21:25:39 +0300 )edit

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.

bocephus ( 2018-02-16 21:46:48 +0300 )edit
11

it is not stupid. it is only postponed because of repo issues.

lpr ( 2018-02-16 21:51:49 +0300 )edit
1

@lpr Not stupid indeed. Just risky. You must know this is an unsupported, buggy, unreleased product.

objectifnul ( 2018-02-16 23:46:52 +0300 )edit
6

not at all. Not riskier than being in EA release mode. You just should be able to edit repository urls with ssu . Update itself went smooth. No other issues so far. I am not complaining, just filing a bug

lpr ( 2018-02-17 00:40:16 +0300 )edit

5 Answers

Sort by » oldest newest most voted
14

answered 2018-02-20 12:43:48 +0300

jovirkku gravatar image

Unfortunately Bluetooth audio does not really seem to be routed from Jolla Phone to Bluetooth devices. JollaC and Xperia do work ok in this case, though. Thank you for reporting. A bug was filed on this.

edit flag offensive delete publish link more

Comments

This makes my phone near-useless as I'm dependent on a hands-free setup and the 3.5mm stereo jack on my device is broken. :-(

sjn ( 2018-02-20 22:21:49 +0300 )edit

@jovirkku Jolla C and Xperia never worked in my case. Informed Jolla after the launch of the Jolla C but got only the feedback: "It is only a community device, don't espect that we will fix that." Also the Xperia X is not working in conjunction with my car entertainment system (see also here: https://together.jolla.com/question/169519/sony-xperia-bluetooth/) Will appreciate when Jolla can fix that in the very near future.

JonnJonz ( 2018-02-21 23:34:09 +0300 )edit
2

Is there going to be an interim fix release before GA? Any fixes we can do ourselves? Not having my BT audio is terrible for me, no podcasts or radio while on the move.

Keeper-of-the-Keys ( 2018-02-22 11:25:30 +0300 )edit
1

@Keeper-of-the-Keys if you really need it that much, you may try downgrading pulseaudio & pulseaudio-modules-droid-sbj to 8.0.61 (sfos-2.1.3.7-version) and share your experience, here...

lpr ( 2018-02-22 18:36:29 +0300 )edit
9

There is a fix for the BT audio issue on Jolla 1 now. We will make another 2.1.4 release candidate. The fix is included in update 2.1.4.14.

jovirkku ( 2018-02-23 10:25:12 +0300 )edit
10

answered 2018-02-22 19:52:55 +0300

Keeper-of-the-Keys gravatar image

updated 2018-02-22 19:54:28 +0300

This is not an answer but after reading all the discussions on this thread I can't hold my piece.

The level of discourse here is below all level of decency, someone is attacking another user for testing the new release, another user (who I think asked this originally) also takes a tone in his suggestions that belittles others concerns.

Yes BT audio stopped working on the Jolla 1 and that is a major regression in user experience we aren't complaining for the sake of complaining.

I don't know about everyone here but probably most people here are power users who want to help this product along, we open bugs/report problems in new releases ahead of time and there is absolutely no acceptable excuse to attack people who are trying to help.

Hopefully people will do some serious introspection about how they behave here.

edit flag offensive delete publish link more

Comments

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

lpr ( 2018-02-22 21:58:08 +0300 )edit
3

@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 ( 2018-02-23 01:30:06 +0300 )edit

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

lpr ( 2018-02-23 14:50:25 +0300 )edit

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

sjn ( 2018-02-23 16:39:05 +0300 )edit

@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.

bocephus ( 2018-02-23 17:32:01 +0300 )edit
8

answered 2018-02-28 11:45:32 +0300

jovirkku gravatar image

updated 2018-03-01 10:12:12 +0300

This issue is fixed in OS update 2.1.4.14 which is available for early access subscribers now. We will roll it out for all users a week later, typically.

edit flag offensive delete publish link more

Comments

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?

DameCENO ( 2018-02-28 13:56:21 +0300 )edit

It's out now :)

In early access, I mean.

Direc ( 2018-02-28 18:45:06 +0300 )edit
3

@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!

tg ( 2018-03-01 09:42:23 +0300 )edit

@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.

Edz ( 2018-03-01 13:20:46 +0300 )edit

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?

Keeper-of-the-Keys ( 2018-03-01 13:51:04 +0300 )edit
4

answered 2018-02-28 03:59:03 +0300

Keeper-of-the-Keys gravatar image

Since Jolla is taking their time I delved a miniscule bit into pulseaudio (barely scratched the surface).

It is possible to manually route sound to your headset, however it is a pretty involved process, nice for a long podcast but no good if you're listening to a non-contiguous stream.

Login/Open to the command line.

pacmd

You're in the pulse audio cli, no arrow support, tab completion or command history so a bit annoying.

list-sinks

Note the index of the output you want (4 in my case)

list-sink-inputs

Note the index of the program you want (443 in my case)

move-sink-input 443 4

Now program 443 is routed to my BT headset.

Sadly set-default-sink does not seem to work properly otherwise it could be a permanent solution.

edit flag offensive delete publish link more

Comments

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

DameCENO ( 2018-02-28 13:59:40 +0300 )edit

@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.

Direc ( 2018-02-28 18:47:51 +0300 )edit

...and I failed miserably :(

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

Direc ( 2018-03-01 18:43:04 +0300 )edit
1

@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 ( 2018-08-29 14:34:30 +0300 )edit

@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)

Keeper-of-the-Keys ( 2018-08-30 10:56:20 +0300 )edit
1

answered 2018-02-17 01:12:23 +0300

deprecated gravatar image

updated 2018-02-17 01:13:00 +0300

It works for me on 2.1.4.12 on Sailfish X when connecting to my Mass Fidelity Relay on my home audio rig. Works perfectly, in fact.

edit flag offensive delete publish link more

Comments

3

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

lpr ( 2018-02-17 01:23:57 +0300 )edit
3

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

deprecated ( 2018-02-17 03:57:15 +0300 )edit
1

@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.

bocephus ( 2018-02-17 10:20:40 +0300 )edit
3

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 ( 2018-02-17 11:03:07 +0300 )edit
4

@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

DameCENO ( 2018-02-19 17:29:52 +0300 )edit
Login/Signup to Answer

Question tools

Follow
12 followers

Stats

Asked: 2018-02-16 20:00:08 +0300

Seen: 2,099 times

Last updated: Sep 03 '18