SailfishOS on Xperia 10 VI

As some of you may have noticed, support for the Xperia 10 IV and V is somewhat behind schedule due to Sony being slow releasing working blobs and Jolla being a bit busy with the C2 and SailfishOS 5.0.

Hence the Xperia 10 V isn’t really available anymore unless you want a second hand example.

So the question is; Wouldn’t it make more sense to not bother getting the IV and V to completion and just focusing on the VI, which you can still go out and buy, instead? It’s a very similar device to the V and is probably barely any more work than what’s needed to get the newer Android blobs for the older device fully working.

2 Likes

Really? What about the few thousands people that are already sitting with their 10 IV/10V in their hands, waiting for a working OS?
Please rethink your proposal.

9 Likes

These postings could be made more efficiently using a yearly cronjob

8 Likes

I’m not sure there are more than a few dozen…

Mind you, up until relatively recently I was one. Then my main phone broke (original Xperia 10), I had to put my Xperia 10 V to use with Android still on it, dropped it literally the same day, the service shop broke it even worse and replaced it with a VI because they simply couldn’t find a replacement V.

Mind you, they stopped selling the V for the VI last May so with the current pace of development the best solution may even be to skip the VI as well and just focus on the VII when it replaces the VI next Spring.

3 Likes

Well, it’s a known fact that Jolla can’t focus on any Xperia phone before they are made available in the Sony open devices program.

5 Likes

I think this is a problem that can never be solved - the release of new phones annually and the ability of a small company like Jolla to keep up with this pace before those phones become difficult to obtain new is something that has been going on for years.

Furthermore, this approach also inevitably results in ‘never quite finished’ adaptations - for example the Xperia 10 iii phone (the latest in the Xperia line to be anything other than early access) is now a near 4 year old phone, originally released in 2021, which continues to suffer from basic issues like loss of sound, disappearing fingerprint unlocking, mobile network access from Android apps, memory management issues (OOM killer), and so on.

Sadly, in my opinion, the most recent properly reliable adaptation in my opinion is the Sony XA2, but that’s now a seven year old phone and now unusable in many geographies (no VoLTE support).

I think the Jolla C2 was perhaps a way to break this cycle, but the adaptation on this device doesn’t appear to be any better than what came before, and nobody knows how long Reeder will go on producing the hardware. Even if Reeder do keep producing it it will quickly become outdated (some have already said that it is outdated now).

So, how to break this vicious circle?

3 Likes

That’s easy… stop demanding the very latest hardware at all times. You really don’t need it. It’s just a stupid prestige thing.

4 Likes

i think it was a valid worry when a company with limited resources to support external hardware:
a) release a new out of cycle device (c2) from a different vendor and very different hardware
b) then says that it will support both the 10iv and 10v - after too long a delay into either devices sales lifecycle

without either one of the problems above we have the usual nail-biting wait for each new annual 10 release, with both of them…

put it this way, I use a 10iii for SFOS and have a 10vi as my android banking device until SFOS arrives for it.

2 Likes

I don’t think this is the real problem per se … I believe most people will be quite happy with a phone a few years old so long as it works - in other words not all of us are demanding the latest hardware. That’s not the problem in my opinion. The problem is twofold - firstly the older the phone is the harder it is to obtain it - even on the second hand market, and secondly advances in technology often render older phones unusable after a period of time even if their hardware, battery life, etc is still working flawlessly.

The latter is a Jolla problem. For example, I loved my XA2 Plus (from 2018) and used it up until October last year. I would have kept on using it as well, but for the fact that everybody is switching off 2G and 3G and, since this phone does not support VoLTE under SFOS I can no longer use it as … well, a phone. So, I am forced to get something newer (X10 iii) that does support VoLTE. If Jolla cannot keep up with newer standards (e.g. modern authentication in IMAP, WPA3, VoLTE, changing APIs, and so on) then SFOS phones will become less and less functional even if the hardware still works just fine.

9 Likes

Why not wait a bit and concentrate on VII? Or even better wait one more year, during which they can fix the C2, and concentrate on VIII?!?

1 Like

Again this false dichotomy. Two phones is not double the work of one, especially not close relatives like iterations of the 10-series. Add to this that with one release each year, you match the Android cycle, and can deal with one set of differences at a time - much like uplifting the browser one ESR at a time.

2 Likes

true in principle, but is it proving to be true in practice?

if everything comes good i’ll be delighted.

but i really hope the existing development load doesn’t backlog into the time period where jolla devs would normally be considering the next device.

in an ideal world we’d want to see jolla bring device support forward into the actual sales lifecycle of the device in question, not push it back further…

1 Like

Or just drop 10’s line and focus on 1 and 5 instead. That would be even better option.

Coming back to 10 V, there are still available, maybe not plenty of them but still new devices.

Every sailor should consider buying newer device from Xperia as soon as possible and keep it safe until sailfish is availabe.

2 Likes

indeed. I use with 10iii with SFOS as the daily driver. I have a 10vi as my banking phone until SFOS is supported, at which point it will become the new daily driver - and i will then purchase a 10viii as the replacement banking phone.

2 Likes

Not here in Finland… I’ve only found a few unsold at Elisa stores in Joensuu and Imatra, pickup only. When the V I actually had was broken worse by the repair shop and they couldn’t fix it they offered to replace it with a VI, I asked them to try find a replacement V instead. What did I end up with? Simple. A VI because they simply couldn’t find one in the Helsinki area.

You know you can freely buy stuff all over Europe? Finland is a member of EU.
Well, you can actually buy things all over the world, but it might cause some extra trouble outside EU. :wink:

1 Like

If there isn’t really an option to get 10 V in finland (which I don’t believe, as eson said, you can buy it anywhere outside FL) I can help with buying one from polish sites.

Good morning everyone,
but is there really a real risk that Jolla will not move forward with the Xperia 10 IV?

The Risk is always there. We don’t really know, which decisions will be meet. What happens, when the situation with blobs will not move forward? than the whole adaptation will not move forward.
I really hope, that this will not happened, because i really want to buy Xperia 10 V as a next phone.
I also wait, that the Dual-SIM-Model with 8GB RAM will be supported…

2 Likes