I think the XZ2 Compact (flagship hardware 2018) has the same speed as the 10III (mid-range hardware 2021). You can compare them by starting a YouTube video which shows a 10III with SFOS and pressing the icons on the launcher at the same time like in video. Thus, the C2 with its entry-level hardware performs well in comparison and is fast enough for the most common tasks. All above seems to be first world problems.
2 Likes
faster or not; the reason for me not to buy the c2 is 5g (which the phone doesnt have but sony xperia 10v does); plus the form factor of the xperia being more comfortable. Users tend to make independent decisions in the end. I guess the user base for the xperia 10v is not as big as the c2.
Yeah, 5g is available on 10 III already. I could go without it as I don’t really use that much mobile data. 3g is just enough for me, 4g&5g is in my case only a nice addition.
And form factor, C2 is big, to big to be comfortable device. I agree it is enough for common tasks but imo only for those.
Imo 10 III is slightly faster than XZ2, however C2 is years behind. Orginal Hardware which was adapted to be a C2 was make in turkey where bying a good phone is very expensive and people make there very little money. So C2 is made to be cheap, not fast as most phones from Reeder.
1 Like
We all know that C2 is nothing but a mediocre excuse for a real up to date phone, but I think we have to give it to Jolla, that they managed to do what they said, namely to give us a phone with a fully functionally SFOS, and a cheap developer unit.
I don’t even use my C2 as a daily driver, but still I can see that the actual OS is more or less flawless, give or take some minor issues. That is what we should expect from a future “High end” unit.
I am still waiting for my X10V to be fully functional.
14 Likes
the last message was positive but no dead line for a release - nothing new.
My pain stage is next os update. I will be not use fingerprint - I don’t need it but camera, battery indicator, bluetooth and stable connection by two sim cards were important.
When it will be not done = bye bye SFOS.
1 Like
I just flashed the zambezi 7b blobs. I will post my findings here once I tried it out.
It sucks. I had a working phone, now it freezes every 5 minutes or so.
It is not my main driver, so no worries. I’ll experiment on.
1 Like
Yes. And Xperia10III has started to slow down. A more powerful device is needed.
1 Like
Reflash. Youre hardware cannot become slower and SFOS updates are not seriously bloating up your device.
7 Likes
Web content, JS - is getting always heavier though, if not straight incompatible.
The combination of older hardware and older browser engine does not help, quite the opposite. Flashing won’t considerably improve anything in this area. So I wouldn’t dismiss his statement that categorically 
2 Likes
And what exactly is the fastest fully supported hardware for SFOS?
I guess a just reflashed 10 III would be a good choice.
1 Like
This. Especially when using Android apps.
1 Like
The hardware even from an old Xperia 10 is powerful enough for modern websites when using Fennec inside Appsupport.
So imho the culprit is mainly the outdated Sailfish browser.
4 Likes
So, to state again the most likely again leading to nowhere question from the author of this topic. With again new blobs from “September 23, 2025”: What is happening actually?
2 Likes
Here is the latest info, more will follow soon™: #sailfishos-meeting log
2 Likes
Have you used it heavily? I actually day drive a V and I honestly have different opinion on this. There are quite a few websites that will cause lag, for example the clouflare proof-of-work capatcha which is now widely used (which I consider a very good thing given how much it is better than google’s long-proven-not-working-only-data-harvesting shit)
Maybe this is due to the fact that the X10-IV and V aren’t yet ready developed. Furthermore, I did a lot of speed tweaks in Fennec’s about:config and also in SFOS. What I want to say: imho the culprit isn’t CPU speed but the software limitations.
2 Likes
Explains some things indeed, but yet changes absolutely nothing again on current situation 
There will be something eventually…something…somewhere…some time later…
Only leads me again to the question why only outdated and deprecated Sony devices for SFOS with bad support from Sony’s side while there are at least a few alternatives, but that’s off topic again.
1 Like
What you people want? You keep asking what Jolla is doing and when they tell you they are working on it and let you know when they have something ready, you say that doesn’t change anything, tell us what you are doing!
They use devices in the Sony Open Device Program, and the devices enter the program only after it has been already replaced by the newer “current year” model. After that Jolla is on the mercy of the Sony AOSP-team (which is different from the stock Android-team) and complaining on this forum about the slow progress doesn’t affect their work at all. The reason on sticking on these Sony devices probably lies in the fact, that Sony offers all these bootloader unlocking tools, AOSP blobs, limited support to Jolla behind the scenes etc. from official sources and that keeps the flashing process easy and clean.
13 Likes
I mean Pixels technically also count as open devices, unlockable bootloader, available driver blobs, though future is unknown with these as Google did not release Android 16 QPR1 source code while QPR2 has finishing touches being applied to it.
2 Likes