I an using the latest release on an Xperia 10ii and cant find any Android apps that can successfully use Bluetooth for scanning . They all report that i must enable Bluetooth , which is enabled .
playing audio from Android apps works
Android App Support is not able to use Bluetooth other than for audio routing. More info here.
3 Likes
Thanks for confirming. I will hold off trying this until implemented
This is quite old thread but my question is, that do we have any options for using airtag kind of products?
How relevant is this without the network feature? Are there even any competitors with any usable size/density network of users?
Network there is, as, iiuc, it’s about Android tags.
To be used in AAS.
The NFC is only used to register/start the tag, then it’s all through BT. Or?
Even, why not an Android tag, which position could be accessed through an open API that Sailfish could access. (will not happen soon but technically spoken, I mean)
Thanks for replies. So situation is still the same basically.
Not quite the same. It has changed from “Not going to happen” to “at some point in the future”:
Official Jolla dev are thinking to bring Bluetooth into AppSupport, see this community news, might happen by the time SailfishOS 5.1 ships.
This is the main blocker to using stuff like AirTags.
Up until now, everything bluetooth is handled on the SailfishOS side using typical GNU/Linux API and libraries (bluez), and only high level stuff is forwarded to Android within AppSupport (audio strams, input devices, etc.)
What would be needed is something that translate from BlueZ to wather weird “not-invented-here syndrom” thing Google is using inside Android for bluetooth. That would allow Android Apps to directly talk to Bluetooth devices (would allow updating firmwares on Bluetooth speakers, etc.)
3 Likes
There is a work around that enables Bluetooth functionality in AAS, but it only works with one system (AAS or SFOS) at a time.
I’ve been playing around with the new 5.1 developer early access release and it doesn’t look as if Bluetooth has been added to AppSupport yet (outside of audio routing).
2 Likes
The announced that it will be available in the store as app and not part of an OS upgrade
2 Likes
Oh, that’s a nice trick!
“Not quite the same. It has changed from “Not going to happen” to “at some point in the future”:
Official Jolla dev are thinking to bring Bluetooth into AppSupport, see this community news, might happen by the time SailfishOS 5.1 ships.”
This would be awesome, if they would do it.
This is already being rolled out in the Jolla Store, as announced here:
Currently only available for those who have opted in to Early Access. Jolla’s plan is to get as much feedback from real-world usage as possible so they can get it in shape and make it generally available.
[Edit to remove CBeta, which is not the same as Early Access (EA).]
2 Likes
EA and CBeta are two different things. You can opt in for early access, but CBeta is invite only.
1 Like
You’re right, of course. I have corrected my post above.
Note that it relies on functionality that is shipped as part of an OS upgrade.
One can find and install the Bluetooth bridge from the Jolla Store, only once one is on SailfishOS 5.1.x.y, it’s not available for the currently shipped 5.0.0.78.
The bridge won’t work without some functionality that only appeared in that newer version.
And as pointed by jojomen, that new version is… :
So either we need to be okay with bleeding edge pre-release software (including some package from SailfishOS:Chum and Openrepos not yet being fixed/upgraded for it).
Or be a bit patient until 5.1.x.y hits official release.
2 Likes