If I understand the technicalities correctly some protocol changed and requires more work on Jolla’s side and then there could be more bugs and back and forth between Jolla and Sony but AFAIK this was only hinted at.
1 Like
You are missing the point that the new binary release constituted many steps back due to Sony’s needless interface changes.
I can only imagine the outrage of non-technical people if some things worked worse than in the previous release even if some worked better.
2 Likes
Gotta say, it really is a disappointment.
I thought I’m going to pay for a commercial, well made Linux on a phone.*
Who chould have thought! In reality, I got nothing xD
Reminds me of when I bought a Windows Mobile 6.5 device, back when this system was competing. Same motives, same experience
* Obviously, I only expected to pay Jolla
1 Like
You do realize Jolla has never accepted money for the IV and V ports precisely because they are not ready, right?
Or did you post in the wrong thread?
13 Likes
That’s exactly what he said!
He thought he was going to pay for a working phone as Jolla promised more than a year ago. But he didn’t pay because Jolla never delivered what they promised, as usual… That’s why he is disappointed, as many others!
3 Likes
The way i read it, he paid believing he would get something that was never on offer.
This means “got nothing in return” - not “decided to not pay”.
Maybe if you run it back and forth through a translator it ends up meaning something different, but i can only read what is there, not what people think.
1 Like
This topic is temporarily closed for at least 4 hours due to a large number of community flags.
This topic was automatically opened after 24 hours.
A new binary, Software binaries for AOSP Android 14.0–Kernel 5.4–Murray (v7b), has been released.
3 Likes
And Jolla: Forgetaboutit 
Why should Sony care about the people who bought a XiV or V and want to install Sailfish on it? Thry didn’t care on all the other SFos phones.
The answer is simple. As long as device is listed in their Open Devices for AOSP they should but 10V was never listed 10IV is no more listed and only 10VI is listed. So it looks like SFOS for 10 VI is most likely to appear.
1 Like
What do you mean, exactly? All three mentioned devices are listed here in the dropdown menu:
I mean
10lV is stiil listed, my mistake. On the phone screen I missed this one.
1 Like
thank you, that is interesting.
to see that the vi is listed while the v is not.
I do have a 10vi acting as my android phone and it’s my fervent wish that this becomes a SFOS device in good time.
Someone must have forgot to update that, here it is listed: Kernel version for Maintained Devices | Developer World
3 Likes
Does anyone know how come that there are fully functional Lineage OS ports for both the 10 IV and 10 V (of production quality, with everything working perfectly fine) while Jolla can’t do anything without Sony providing some “new fixed” binaries?
3 Likes
Maybe because Lineage OS is basically Android and SFOS is not?
8 Likes
You are completely wrong. That hardware-related layer of Android (kernel, hardware drivers, HAL, etc). is 100% LINUX. And SFOS’ HAL uses those hardware drivers (e.g. from Sony blobs) DIRECTLY, just like an Android OS does.
So maybe you should start from learning what those Sony binaries / blobs contain, and how (and what for) SFOS uses them, rather than posting irrelevant and misleading answers. Please learn how Android (including Lineage OS) sits on top of a Linux kernel and Linux hardware drivers and HAL.
So, once again, my question was: how come that a few teenage geeks managed to create and then regularly maintain (perfectly working) Lineage OS ports for both the 10 V and 10 IV, which involved utilizing Sony 10 IV and V hardware drivers (no matter if directly from Sony blobs, or extracted from there, or compiled from source, or in any other form) just like SFOS X or any Android / AOSP-based project has to do, whereas Jolla (for over a year now - happy anniversary!) refrains to only blaming Sony for not providing readily-usable hardware drivers, which then they use as an excuse for doing absolutely nothing.
On a different note, considering that LineageOS is entirely open sourced (please correct me if I am wrong), why not utilize in SFOS those (perfectly fine working) 10 V and IV hardware drivers from those LOS ports instead of waiting for Godot, oh, sorry, for Sony?
6 Likes
Maybe they do use extracted blobs? At least in the past Sony had different teams working on their Android and AOSP, so it wouldn’t be the first time, the Android -side had things better than the AOSP project.
1 Like