View Single Post
Posts: 959 | Thanked: 3,427 times | Joined on Apr 2012
#557
Originally Posted by rinigus View Post
Its also a 64-bit device. I don't know what's the current status of 64-bit devices now among ported devices, but getting SFOS ported to this architecture is a major success and we should not underestimate it. When done, it should open many current devices for all of us through the ports.

I do wonder if the port for Xperia X would be made available as a community port image / sources as well. That would allow for curious user to test SFOS before getting full version of it. If not, porters would probably know or would get help to get SFOS running on X Compact and other variants.
I'd also be curious about app compatibility for any SFOS apps with binary components - will we as developers need to recompile everything for this device? What about apps like CuteSpot, which depends on a third-party library (libspotify) which might not be already compiled for ARM64?

Originally Posted by rinigus View Post
As for the pure ports, if you don't need Android stack, the current main problem is the absence of text prediction (jolla-xt9 is proprietary). So, would be great to get someone to work on it and get open-source solution for text predictions. Port from Ubuntu Touch, for example?
I was working on a keyboard a while back; I should dust off that code and see what can be done with it.

Originally Posted by Feathers McGraw View Post
Check out OKboard if you haven't already - continuous input /predictive keyboard for Sailfish that is fully open. I can't remember whether it does predictions for normal typing (I think it currently uses xt9 for that) but it clearly could, because it does its own predictions for continuous input. That's something open versions of Android are missing BTW - if you want CI on Android you have to use something like Swype or Swiftkey.
I've been testing OKboard on Jolla and on OPX (third-party port without xt9). On the OPX it's pretty terrible; not just for the lack of predictions in normal typing, but because it tries to use xt9's predictions bar for its own predictions when swiping, meaning that without xt9 there are no predictions whatsoever. And no ability to correct a word; you have to swipe and hope you nailed it.
 

The Following 7 Users Say Thank You to taixzo For This Useful Post: