You don’t need Bluetooth to register bank id. Skandiabanken had special tech support for bank id and that guy could guide me through the process. I used my bank PIN instead of the bluetooth method. Bluetooth is just the primary method. Check with your bank.
*edit - might be that i also had to send in a paper form. In the thread about this, someone with Handelsbanken reported going in to the bank office to verify his identity. Skandia doesn’t have offices.
*edit 2 - In fact, I already gave you this info in that other thread.
Well, My bank is ICA Bank, and I’m having big trouble getting away from them. There is no Swedish bank accepting new customers without bending over and giving them your whole life in paper weight…. and I’m not prepared to do do that. I am a fucking libertarian, and I will never ever give my liberty away.
That said, ICA bank will not allow me to move-/new create my BankID to another device without bluetooth or the NFC passports.
Best of luck, then. I thought I was screwed with Skandia too, until I found the tech support person, who knew something and didn’t just read from flowcharts.
Same here on Alfa Giulia. This is not an AAS issue, it’s basic SFOS Bluetooth since I have an Xperia 10 V and no Bluetooth AAS support. Looks like a regression.
I have been using Polar Vantage M3 with Polar Flow app with AppSupport Bluetooth and I can sync it but sometimes it needs more than one attempt. I have noticed that if the data appears to be partially synced then syncing again one or more times can help, also sometimes swiping down in app refresh the view can help.
Could you try the obex restart mentioned in the known issues of the release thread and see if it works after that? That only mentions bluetooth filesharing but if it blocks phonebook access as well then it might be a bigger problem.
100% of the times I connect the phone without restarting obex after a reboot, the contact list and call history are not available.
100% of the times I connect the phone after restarting obex, the contact list is available. (I didn’t check call history, but I guess that’s not the point.)
Thanks to the Bluetooth support in AAS, I’ve finally defeated the final boss: DHL (Germany). They have this annoying habit of redirecting packages to a specific type of parcel locker (Packstation) that doesn’t have a control panel (so there’s no way to use a QR code to pick the package up) and only works with their own app via Bluetooth. In the past, packages were regularly returned after the storage period expired because I couldn’t retrieve them from these stupid parcel stations. Yesterday I was finally able to get a package out of that stupid thing! One less reason to have a backup Android smartphone
Thank you, Jolla!
Xperia 10IV SFOS 5.1.0.8. Pairing Jabra Evolve2 85 in SFOS. Headset audio OK in android and SFOS apps. Install Appsupport Bluetooth + reboot OK. Install Jabra Sound + android app OK. Not able to connect to headset. Deleted SFOS paring and try paring headset with long press, Ok. Enabled paring request for android. No audio through headset in SFOS nor android. Start Jabra Sound +. Not able to connect to headset.
As I said before, I don’t think it’s a good idea to try to pair sound devices with AppSupport. Android audio is already routed through to BlueZ to those with Sailfish audio. Each device can only be paired with Sailfish or AppSupport - and can only talk to one of them. So you might end up losing audio or getting some really strange behaviour.
Unless you have a clear reason to do so. For example, you might need to adjust some advanced configuration of a device, or pair your car key with your account to access connected services for Stellantis vehicles.
Obviously, you would then have to switch back to native BT. So, it’s a bit of an extra hassle.
By the way, I failed to pair with my car through AAS despite several attempts (Xperia 10 III, recent C5 Aircross). Luckily, I had a spare Android phone to complete the one-off key pairing step.
The first thing that happened when I connected the Sennheiser headset to my wife’s iPhone was a firmware update. That couldn’t be handled on my C2.
The app also comes with preferable settings that are not available outside the app, like when you listen to specific music genre you can choose a Equaliser preset for that genre.
For any pairing failures, it would be helpful if you could send us some debug logs, gathered as described in the OP. You can turn debug logs on just before you first start to pair, and off again when you’ve stopped. Make sure you extract the logs fairly soon while they’re still available, as they might get rolled if you wait too long, especially if you wait too long.