From the project’s GitHub page, this is the link: https://github.com/erkserkserks/openboard/tree/46fdf2b550035ca69299ce312fa158e7ade36967/app/src/main/jniLibs
(If you have a modern phone, you’ll want the arm64-v8a build)
From the project’s GitHub page, this is the link: https://github.com/erkserkserks/openboard/tree/46fdf2b550035ca69299ce312fa158e7ade36967/app/src/main/jniLibs
(If you have a modern phone, you’ll want the arm64-v8a build)
The latest release hints towards F-Droid availability: https://github.com/Helium314/HeliBoard/releases/tag/v1.2
Just updating 1.1 APKs would have created issues with incoming F-Droid build.
HeliBoard has been my chosen SwiftKey replacement: https://github.com/Helium314/HeliBoard
Features I value:
It does suck to see an app that I loved and paid for (yes, I used it for THAT long) get enshittified and try push AI* down my throat.
Not to mention M$ owning my typing history (which I kinda could live with).
RIP SwiftKey.
This is the best summary I could come up with:
When your phone becomes unusable and unrepairable, buy a Fairphone.
If you wanna stick to Fairphone, they maintain a de-googled version of the OS, the Fairphone Open (only open source code): https://code.fairphone.com/projects/fairphone-2/fairphone-open.html
Appears to be a useful app, with a plaetora of features, but gathers your personal data, including voice, just to sell it to the highest bidder, all under the umbrella of an ads platform (which is also a very sketchy business).
Yup, sounds like a virus to me.
Me washing $200 worth of groceries in 2023
Alt: it’s a simple spell but quite unbreakable.
Just thinking out loud: could you move the yuzu data folder to a place that Syncthing can access and create a symlink from the original to the new location?
I think the biggest problem would be file ownership/permissions, but otherwise should work.
Additionally, you would have to uninstall and reinstall the app after you’re effectively out of beta.
I don’t think that the Play Store would ever downgrade an app version, as Android doesn’t allow that.
Yup, very likely that.
My crystal ball says that your client is trying to parse the response of a failed request as it was a successful one.
A successful request would return a valid JSON object, while a failed on would probably return an error message.
Report a bug with your client devs saying that they should check that request’s status code says it’s successful before trying to parse its response as JSON.
If you’re interested in Lineage, just check their device page and filter for set top box:
https://wiki.lineageos.org/devices/