Car (Audi) bluetooth connection problem and other issues in latest Sailfish Os 5.2.0.17

UPDATE: originally this topic contained multiple topics but I marked bluetooth problem as “main” where solution is also found. Leaving other stuff also to post because some comments related to them.

Bluetooth; having hard times connecting my phone to my car (Audi Q4 e-tron). I can help debugging this also if you give me some guidelines where to start. One time noticed that phone tried to ask pairing pin code but notification were wierd, it was something like “from null” don’t remember exactly anymore.

But usually no popup asking to type pin code which car generates to form pairing. I have set my phone visible but that doesn’t help.

Stability issues:

I have feeling that stability has gone somewhat worse after latest update (finlayson)

My device is Jolla Phone 2026 and after latest upgrade I have started to experience following issues:

Native Browser just stops starting, it starts loading but then just crash.

Today noticed that every native app had crashin/stuck problem (Clock, native browser), just loading icon in home view (where running apps are shown). I had nothing running but suddently just stopped start even Clock…

If you give me commands how to collect logs from command line I can give more logs when next time this happens.

Usability:

Not related to latest update but still, when booting, sequence is somewhat unclear, it asks first security code and then just blank, after pressing buttons and after some period it asks sec code again and then after that sim code. Makes user think what f* :smiley:

Looks like Jolla team has still lot of work to do make this phone regular user ready.

And sorry if this is in wrong category, not sure where this fits.

Thanks

1 Like

So you post about the latest update - but tack on two other topics that you, yourself, say is not relate to it?
Seriously, come on!

You have also completely misunderstood “problem” 3, but i will not reward this multi-topic thread with a link.

1 Like

Maybe related: The AAS bluetooth (if installed) can seemingly block bluetooth of native side, and I believe this is a known issue. Hopefully fixed in a future update.

If you don’t pair any Android apps, then try uninstalling AAS bluetooth support, otherwise I found that restarting the phone temporarily seems to help bluetooth.

SFOS automatically uses 0000. Change your cars pin to 0000.

1 Like

AUDI already has four zeros on its grille…?! :thinking: :face_with_monocle:
Around here, the fifth zero is often behind the wheel. :wink: :winking_face_with_tongue: :folded_hands: I’m so sorry… He had to go :dove:

hmm, I’m not sure if pin code is possible to set manually. Looks like audi generates new pin code everytime automatically. But I will check

Ah, so first step to try would be to disable “send incoming pairing requests to AppSupport”

yeah, its also killing me how much time I need to spend reporting and asking so many different things because product is just so buggy! Come on!

Sorry!

2 Likes

If you don’t split these issues, then when are you going to mark the issues as solved? When first one is solved, when two out of three are solved or when all three are solved? If you mark it as solved when two or three are solved, then what message you mark as the solution if they all aren’t in one post?

1 Like

You have like one thread (albeit with 3 “issues”) on that?

So some web page caused you to run out of memory. Shit happens.
This is the best native browser we ever had.
Yes, some of its bugs are a bit spicier than last version - but when i see all the work happening on the next version, i’m quite content.

And i repeat; your third supposed issue is a outright misunderstanding on your part.

1 Like

Yes, tested. Disabling “Send pairing request to AppSupport” works and pairing request is correctly shown in SFOS UI and I can successfully pair phone with car. Thanks for tip!

1 Like

Yeah, it’s true that I should have splitted this to multiple topics, sometimes time is just so limited and still want to try to solve these issues but anyway bad call.

2 Likes

So, thread solved? :thinking:

2 Likes

Let me plug to this topic, as I cannot connect to my car too – and it’s Volkswagen ID.3, which is the same platform as Q4 e-tron.

  • AppSupport with BT installed and enabled. Tried disabling, restarting my phone etc.
  • Passing incoming pairing codes to AppSupport disabled.
  • When both devices are visible, phone sees the car, but the car doesn’t see the phone (also, while the phone sees lots of devices, car sees only my other phone – Samsung).
  • When I try to pair from the phone, I correctly see the pairing monit with matching code on both car and phone. Phone still doesn’t appear on car’s device list.
  • After I accept pairing on both side, phone lists car as paired, tries to connect and immediately disconnects.

Any ideas? I guess it shouldn’t be the legacy 1234 vs 0000 PIN when the paring codes are used, can it?

I usually get my car - phone connection working by restarting bluetooth services via “Utilities” in Settings and of course “Passing incoming pairing codes to AAS” need to be disabled (actually not tested this in newest SFOS 5.2.0.22)

Also setting “Visibility” to On in Bluetooth settings may help.

OK – the actual answer was to insert a SIM card into Jolla Phone. Probably car rejected a phone without an active plan.

So now I have it connected, but no contacts and messages are imported. Also, car reports phone battery as always full. Any ideas for this?

No, I have tried to list contacts maybe once but gave up. No high hopes its gonna work. Not sure how contact sharing works over bluetooth, does it require some android specific stuff or what.

For me its enough that I can answer/make calls and listen spotify via car’s speakers

I’ll file it as bug report then.