2 ms·
I bought Jolla Phone 2026. Was thinking about Pixel 10 and another round of GrapheneOS, but changed my mind. Was using Sailfish OS on Sonys phone but drove me
by stiray 2mo ago
I bought Jolla Phone 2026. Was thinking about Pixel 10 and another round of GrapheneOS, but changed my mind.
Was using Sailfish OS on Sonys phone but drove me nuts for two reasons:
- had to reverse banking up to kick out the checks each time when new version came out and I became quite proficient at it (decompiled into git and each new version over it, then git diff, and fix the checks, committed the changes)
- worse part was that there was no bluetooth to android bridge and local bus company required it for contactless paying
There was nothing I missed from the phone, even reversing banking app was not really an issue, but bluetooth was just needed.
I defected to GrapheneOS after two years, now I am moving back, I hope for good. The fixed the bluetooth while for hardware I dont care.
I have solved the banking app issues by changing the bank and getting cheap old pixel just for banking app. It doesnt even have SIM, only wifi and used Automatize to turn on airplane mode on lock screen and turning it off for unlock.
I dont care about NFC payment or any other android junk, for photos I have EOS and phone just doesnt cut it, while camera is good enough for taking shots at everyday things like shopping list.
I really hope I wont need to see android ever again.
- user2722 2mo agoBluetooth now works with Waydroid? Seamlessly or you have to "disconnect" from host and "connect" it to Waydroid? AFAIK, Camera (V4L) is also broken on main repo, to anyone else wondering.
- poetaster 2mo agoBluetooth support is for Jolla's android support. 5.2 for ports and waydroid is awayz out. My guess,18 months.
- stiray 2mo agoJust to clarify bluetooth situation: https://forum.sailfishos.org/t/release-notes-pispala-5-1-0-11/29751 https://forum.sailfishos.org/t/release-notes-pispala-5-1-0-1... /* The AppSupport Bluetooth Bridge shares the phone’s Bluetooth controller between Sailfish OS and AppSupport. It acts as a router, so each Bluetooth device can be handled by either Sailfish OS or AppSupport without handing the whole controller over. For most devices this is controlled through pairing. BLE devices are more complicated, and that is one of the areas where broader testing will be useful. For now, you should reboot after installing. The Bluetooth settings page now has an extra option to route incoming pairing requests to AppSupport. Devices found during scanning also have a long-press context menu option to pair them with AppSupport. You can see devices paired with AppSupport on the same page, and you should also unpair them from there when needed. Turning Bluetooth on and off in Sailfish also turns it on and off in AppSupport. You should not try to turn it on or off from Android apps. Android apps that are designed to pair with devices internally should be able to do so. If you have previously handed Bluetooth completely over to AppSupport as described elsewhere on the forum, revert those changes first. Otherwise things are likely to break." */ I hope it helps.