Closed GeoffTearle closed 3 years ago
Thank you very much for your work on this. Literally waiting since 3 years for Jolla to move and a hero like you to appear <3
I also have a AsteroidOS device in my drawer waiting to get into action!
Sailfish 4.2.0 has passed the (first) translation round, so it is getting closer :)
right, SFOS 4.2 is available to EA subscribers, and includes:
bluez 5.58: CVE-2020-27153
With 4.2 being officially released, we now have a compatible bluez5!!!
I've personally upgraded and verified that the gatt cache segfault is no longer occurring.
I am noticing some weirdness with notifications not always being sent, but I don't believe that that's reason enough to keep this issue open.
@GeoffTearle does that mean that Starfish now works with SFOS? If so, do you have a RPM to share? :)
I built my test packages and posted them here.
Now that 4.2.0.21 is officially out, I should build the new ones...
I can look at doing a fresh master build later today? (if @direc85 hasnt beat me to it ;) )
My laptop is just in an interesting state at the moment, so doing anything on it is a touch inconvenient
That would be super nice! :)
On Sunday, 19 September 2021, GeoffTearle wrote:
I can look at doing a fresh master build later today? (if @direc85 hasnt beat me to it ;) )
My laptop is just in an interesting state at the moment, so doing anything on it is a touch inconvenient
-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/AsteroidOS/starfish/issues/9#issuecomment-92254039
-- Sent from my Sailfish device
@ncartron Sorry for the delay, but here are builds of the latest master using 4.2.0.19EA (jolla tends to lag behind with releasing the new sdk after a Sailfish release)
harbour-starfish-1.0-1.aarch64.zip harbour-starfish-1.0-1.armv7hl.zip
Excellent, thanks @GeoffTearle !
I just bought a used LG Urban Watch , will install Starfish (or whatever new name it'll have ^^) as soon as I receive it and get Asteroid working on it - thanks again!
There's currently an incompatibility between the versions of bluez5 that are used on AsteroidOS and SailfishOS (4.0, & 4.1) :(
Currently Sailfish is using bluez5 5.54 which has a flaw in the code that caches GATT information. This results in the bluetoothd service segfaulting, on the phone, when you try to connect your watch.
This should be resolved in the next SailfishOS update as they have recently upgraded their bluez5 fork to 5.58. https://git.sailfishos.org/mer-core/bluez5/merge_requests/47
I’ve personally installed the new bluez5 package to my phone and I can confirm it does resolve the issue.
I'll resolve this issue when the new version of Sailfish, containing the update bluez5 packages, is released.