You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Jolla 1 uses bluez 4, so the way contrac accesses the BLE API will need to be re-written.
The Jolla C runs bluez 5, but has a more restricted BLE 4.0 chip. In testing, it didn't work and bluez returned errors when sending multiple beacons. it's possible this could be worked around.
The text was updated successfully, but these errors were encountered:
I'd be willing to support a capable developer with knowledge on the BLE API (is there someone like that in the Sailfish community?) with a decent donation (and beta-testing), if that'd make it more worthwile for someone to spend time on it. I hate having to carry an additional Android device around for the Corona-Warn-App, so a port for Jolla Phone's BlueZ 4 (if feasible) would provide great utility for me, and others, and would be greatly appreciated.
Addendum: Since Jolla stopped the support of the Jolla Phone ahead of the upcoming Sailfish 4 release, I've decided to upgrade to a Sony Xperia XA2, therefore I am no longer in need of a port for the BlueZ4 architecture, and rescind my offer.
I'd also love to have this fixed, and if someone from the community were to take a look and contribute a solution, that would be very welcome. Anyone with a bit of knowledge (or willingness to learn) about the Bluez 4 and 5 APIs would be in a position to help. I know there are people in the SFOS community with experience (e.g. @piggz and I'm sure others) so one approach might be to post a request on forum.sailfishos.org.
The Jolla 1 uses bluez 4, so the way contrac accesses the BLE API will need to be re-written.
The Jolla C runs bluez 5, but has a more restricted BLE 4.0 chip. In testing, it didn't work and bluez returned errors when sending multiple beacons. it's possible this could be worked around.
The text was updated successfully, but these errors were encountered: