I received my brand new Jolla Phone 2026 yesterday, I was very excited.
Today I was setting up some apps, and, since I drive a Tesla, I installed the Tesla android app.
I know bluetooth is beta level, but I was expecting it at least to pair, like it should do with some bluetooth headphones, instead nothing worked.
The phone reports the car paired, while the car reports the pair as failed.
I tried both with the pairing request redirected to AppSupport and without it, multiple times (the option doesn’t seems to take effect immediately).
The android app, instead, worked after a few tries and a phone reboot.
So, unexpectedly, what I considered the most difficult thing, using the phone as a car key, works, and what I considered merely a chore, using the car to listen to music, didn’t worked.
I’m a developer and I really want to get this working, so if any SailfishOS dev needs anything to help troubleshoot this, just ask me.
Hello and welcome! Love your attitude Pinging the goat himself @abranson. I don’t personally know if the bluetooth stack is fully open source and could be developed by community effort? Is the new AAS bluetooth open source?
AFAIU things have changed with the newish update to bluetooth in AppSupport.
Previously we only had native bluetooth support, so you could pair your device and have audio routed through bluetooth to your car, but obviously your android apps wouldn’t work.
There has been some progress with native support for Tesla, as discussed here.
When they brought bluetooth to AppSupport, this allowed Android apps to work, with the exception of audio which again AFAIU, is only supported natively, and maybe that’s the issue you’re having.
Bluetooth can be quite fiddly at the best of times, but perhaps you need to make all devices forget each other, and stop AppSupport completely to be sure. Then pair just the car media centre with your phone. Then once you get it working, try to play with getting the Android side going
As part of AppSupport, the Bluetooth bridge is not open-source yet I’m afraid, but the scope of the routing is per-device, not per-service, so being able to pair a device with both at the same time is not currently possible and I can’t see how we’d do it either. Maybe the way forward would be to allow audio to be sent through the Android pairings, but that would be a large amount of work too.
Well, I don’t really need the audio to go to the android VM, I just need it to work… I’ll try later disabling AppSupport and rebooting and let you know.
Thanks everybody for the replies, I already love this community
Can you point me to it? I’ve searched on the store, without luck. I’ve seen something in the thread linked by @rgp, but, as far as I’ve seen, it has no been published
@rgp@abranson I’ve made a short video of the process, sorry for everything being Italian…
You can see AppSupport is disabled, I set the phone as visible via bluetooth, then start the search from the car and select the phone, it gets the pairing code correctly, but then the phone throws an error, the car tries to reconnect with PBAP and this time it’s the car throwing an error.
Pinging the goat himself