Order A Phone and not heard from the company / Jolla communication and expectation management

To me it was clear that Jolla wanted to change policy, so the 10 III was the last Sony I bought.

Don’t understand the problem or the question yet, but I will assume you got the 99€ voucher. In this case you will be asked to pay the rest and use the discount code (the 99€ you paid are deductible from the full price you’ll pay later).

Just in case I will advise you to read the email you will receive probably later this summer cause you’ll have to pay attention that time to receive your device without issues or delays.

For the rest, I don’t know how this convo shifted to Xperia 10 V but I’m sure it will help this confused guy figure out what’s happening with his order.

1 Like

2 Likes

Personal attacks I can agree with but valid criticism, I think is still important and I don’t think we should refrain from that just becasue some people might not like it. Otherwise how are you gonna have a discussion in a discussion forum?
When it comes to how other people feel about how you write something, thats just very subjective

A commitment based on empty promises by Sony which they never managed to deliver.
While it’s a bad situation you can hardly expect Jolla to fix issues that Sony wasn’t able or willing to solve.

2 Likes

This “Jolla can’t do anything because they’re waiting on new binary blobs from Sony” thing seems to be rapidly becoming an urban myth.

What specific promises from Sony to Jolla regarding the Xperia 10 iv and v do you have knowledge of?

As far as I know from Jolla’s statements and what’s been discussed on this forum this is not how it works.

Sony releases new vendor blobs from time to time under their open devices programme to anyone who wants to use them. Blob users can report bugs to Sony, who may or may not decide to fix them. I also understand that blob users can contribute/propose code changes upstream as well, again which may or may not be incorporated in future versions of the blobs.

Unless you can confirm otherwise (for example, that Sony has a contract with Jolla to supply vendor blobs to a specific specification that will work with SFOS images) I think it is highly unlikely that a giant corporation like Sony will promise Jolla that they will change their blobs specifically for a tiny company like Jolla for a phones that are already 3 to 4 years old and no longer even produced.

When Jolla originally released the beta images for the Sony Xperia 10 v, the recommended blobs were v3a. Over the last year and a half Sony have released many new versions of the blobs (https://opendevices.sony.net/aosp-on-xperia-open-devices/downloads/software-binaries):

  • Version 4a in early August 2024
  • Version 4b in late August 2024
  • Version 5a in late November 2024
  • Version 6a in late March 2025
  • Version 7a in late May 2025
  • Version 7b in late September 2025

To date, since September 2024, Jolla has not released any further adapted SFOS installations for the Xperia 10 v (or the equivalent Murray images for the Xperia 10 iv) based on any later binary blobs than v3a. Whether they have even tested SFOS against any of the later blob releases I don’t know.

Various community members have tried using later versions of the blobs with the original (unchanged) flashable SFOS images for these phones with varying levels of success and/or failure. For example v4b for the Xperia 10 v does make the battery indicator work and mobile data more stable, but all of the other issues remain.

From this thread here (New binaries / blobs for Xperia V and IV : What is happening actually?) you can read that one of the biggest problems to get SFOS properly working on these phones is that Sony have changed some of the protocols/interfaces that the blobs use to communicate with the higher software layers (e.g. bits of SFOS). This means that to get some of the things that currently don’t work to work Jolla have got to do some re-engineering of whatever SFOS layer communicates with the blobs. They have not done this work and are now focussing on the new Jolla Phone adaptation, so perhaps this is something Jolla could fix with time and effort but have currently chosen not to.

In the November 2025 community meeting Jolla suggested that the community might want to take over the hardware adaptation of the Xperia 10 iv and v based on a Lineage base, rather that asop Android base. Obviously that hasn’t happened.

So, as you see, its not just a simple case of being all Sony’s fault because they broke their promises.

2 Likes

Of course they have - and made adaptations to them.

A lot of this work has been done.

So it is not as simple as you make it out to be either.

5 Likes

What I get from this is that we have so many experts on the topic, but no one is capable of using Los as base for a simple port.
Either trust the Jolla engineers or fix it if you know how would be an approach that makes sense to me.

But still it doesn’t make sense to me why this thread is being hijacked with Xperia V complaints.

5 Likes

Well, I did say that I didn’t know whether they had or whether they hadn’t. All I said was that they had never released anything further beyond the initial beta release a year and a half ago,

My point exactly - its not a simple situation, so again I agree with you.

1 Like

Yeah, that’s probably my fault. I was just using this as an example in response to the OP’s post. Then another question was asked which I responded to.

It just seemed easier to respond in the same thread. Probably we should all shut up about this now!

1 Like

You pretty much gave the reason yourself why Jolla is not pursuing 10 iv and v.
Sure, they could spend (or waste) uncountable man hours on chasing a moving target. Similar story with a lot of other Jolla decisions made a long time ago. They could (and probably can) fix things but with the resources they have, they cannot tackle them all at once (or ever).
Sucks for those who bought a 10 iv or v in the hope that it would be fully supported at a given point in the future - but at least they should have known that they were gambling since the product was not final.
At least they didn’t have a product that was reliant on SFOS. Now that would have suc2ked.

You were insinuating that they had done absolutely nothing. That’s spreading FUD.

2 Likes

source? or you are a jolla employee?

1 Like

I have see them with my own eyes, on github. They have also been discussed on the community meetings.

2 Likes

What specific promises from Jolla to us regarding the Xperia 10 IV and V do you have knowledge of?
I might be wrong, but how I remember it, Jolla told us they are working on these devices, have made good progress, and they had confidence to continue this. I remember to have bought the Xperia 10 V knowing it was a gamble.
This was around the time the C2 came out. I know this because I was choosing between these devices. I did not trust the C2 to be an upgrade over my 10 II that broke, and I knew support for the 10 V was not sure yet. I ended up buying both, just to be sure, planning to sell the one I wouldn’t end up using. I am very sure of this.
I am not sure about the exact words used for the report about 10 V support, and I am not sure they didn’t make any promises after this that I could have missed.

tldr;
As I remember it, Jolla never made a promise about 10 IV and 10 V support.

4 Likes

They should have made everyone sign a disclaimer or something :laughing: because people will forget they never promised it will 100% work.

2 Likes

Ultimately both Jolla and those of us who have a IV or V device have lost out. Jolla ported Sailfish to both devices and still have yet ro make a penny for those efforts as they can’t call those ports complete. And the consumers have lost out due to not having a complete port.

I do think they did all they reasonably could though, and releasing their ports for free was a nice touch. And this is another tough lesson we have to learn about events outside our control. As with the tablet situation, I don’t for a second think that Jolla acted with any malice.

I suspect the poor state of Sony’s IV adaptation led to Jolla’s decision to restart their device program and release the C2.

Relying on Sony was always far from ideal. By the time a Sailfish release was ready for a ‘new’ device, those devices were harder to buy, and accessories even harder.

3 Likes

I completely agree

Without wanting to sound ungrateful: I think they had to. It is damage control. And they don’t lose much releasing software they are unable to sell anyway.
And to go even further. Although they did not make promises, they did set expectations. So I think it was the only right thing to do.

The 10 V is my daily driver, and I like it very much. It is a very usable device, as long as you don’t require to make pictures. As a non-camera phone, I would certainly recommend it.

From the April 2024 Community News:

From the August 2024 Community News:

Never happened of course.

From Jolla’s list of Supported Devices on their website listing the Sony Xperia 10 iv and 10 v as officially supported:

Seems a pretty clear promise to me - not Jolla might support these devices or maybe could support these devices, but Jolla will support these devices and confirmed support for the different variants.

But then, the ‘de-emphasising’ of support for these models.

From the community meeting minutes of 6th November 2025 (Oops, there’s that non-existent promise again!):

and:

Nov 2025

And of course finally from the Community Meeting on the 4th June 2026:

Now we can all argue what ‘supported’ means in practice, but whatever the nuances I think we’d all agree that at least the basics need to work in practice for the device to be usable. Both the !0 iv and the 10 v are a long way from being in this state at the moment as we all know.

1 Like

I stand corrected. Thank you for the information. I did not remember correctly the parts I wasn’t sure about, and:

I was wrong about the part I was sure about. They did promise it. I think I didn’t they would do it in time, and acted as though it was not a promise. And that’s why I misremembered. But you are entirely correct.

2 Likes