I would choose 10 IV
The 10 IV is a better toy than the C2, for an irrelevant price difference if you are lucky on the second hand market.
I know Jolla announced future support for the xperia 10-iv and v, but I can’t find info for model numbers they will support. There are two different model numbers for each. Will Jolla support both models for these two devices?
I added zRAM (4GB) to the Xperia 10 III. Then the browser sometimes takes more than 1,5 GB from them but running all the time in the background without being killed.
It’s just like an old dinosaur 
Hi,
please can you tell who to do this in my sony 10III?
This should work. The whole thread is very interesting.
You totally left out the most important difference between C1 and 10 V for some of us:
C2 comes with SFOS preinstalled, while 10 V requires the buyer to start acting like a hacker and perform cumbersome actions that may possibly brick the whole phone.
For those who already are hackers, that may not be important. But one should anyhow realize that if SFOS shall obtain a larger penetration in the market, people will need to be able to just buy a phone and start using it.
After my preinstalled J1 and Intex phones died, I’ve been forced to install SFOS on the several subsequent Sony phones I’ve used, and normally there’s been some kind of snag that I’ve needed to consult others on for sorting out. For no-hackers one shall be really dedicated to the cause for an independent phoneOS to go through it.
I’ve a couple of 10 V waiting in reserve for the demise of my current 10 II daily driver, which I bought before I knew about C2. If C2 perform reasonably stable for basic operations, they may never have SFOS installed.
I believe there are more people than me who are privacy concerned, who may be willing to buy a simple and weaker non-android phone if relatively easily available. (As such I’m more concerned about SFOS marketing challenges than the technical prospects.)
I think the C2 is based on an existing android model. I would imagine there will be some sort of AOSP layer on C2 and SFOS will run on top. If that’s correct we have the same scenario with xperia models, the only difference is that users do not need to unlock the device, and flash the firmware, etc. Also the company that produces C2 is willing to collaborate more closely with Jolla, therefore some bugs at phone drivers will be addressed more easier compared to the sony ones?
Spoiler: that has been true for all previous models, except maybe the tablet.
Hmmm, it’s going to be interesting to choose between those two. I would like to get the C2 to give Jolla some support cash, but Xperia has one big advantage that I haven’t seen mentioned yet…IT HAS NO STUPID NOTCH ON THE DISPLAY (yes, it irks me THAT much) 
Oh yeah — the notch…
Every time I start considering the C2 for purchase the notch stops me.
I am curious whether the AndroidApp Support will be available on the Xperia day 1, or released later. That will influence my purchasing decision a bit. Shame it doesn’t have wireless charging, I got kinda used to it with Volla 22.
It has been already confirmed — released later.
Coolies. I might yoink it later then.
Does anybody know whether the C2 has a notifications LED like the Xperia 10 IV (and unlike the 10 V) ?
I’ve become pretty dependent on this little feature.
(Edit: confused the Xperia models)
I guess we will see when the OS arrives.
The phone itself doesn’t have a dedicated indicator LED. It doesn’t have to, because the AMOLED screen can function as an indicator. Just light a couple of LEDs on the screen in some color for notification. In LCD this would cost a lot of energy, because it needs backlight, but this is not the case with AMOLED. Android users did report to not have a noticeable energy drain because of this. So it has (or can possibly have) a good functioning LED indicator on android, although not dedicated. But I think it will need proper software support from SailfishOS to work. I don’t have experience in OS development or Sailfish hardware adaption and such, so I could be wrong about that.
Thank you for your thoughts!
Hard to believe different OS variants will be released for the Xperia IV (accessing its built-in LED) and the C2/Xperia V (with a screen-based notification area).
But we’ll see!
There are many variants, right? XA2 variants, 10, 10II, 10III, all different hardware. The IV and V are the least different of them all. There must be code to turn the pixels on and off, but after that, I think it should be very, very easy to implement. A small update in the subroutine, if dededicated_indicator_exists then … else … and point to the right code to display. Everything that needs the indicator can then just run indicator_blink() or something like that. No need for different OS variants, because no one will really notice those couple hundreds of bytes, and just push the code that lights pixels to phones that will never run it as well. But again, I might be wrong about this. It just intuitively feels pretty easy to change the existing code to let it run the code you need.
The phone doesn’t have to have a LED when
You think C2 has any of the above?
It doesn’t have to, because the AMOLED screen can function as an indicator.
Uh wow. Just realized that it indeed has AMOLED like the good old N9 had. So maybe we can get clock+indicators back even if screen is turned of. I think there was some tweak with /proc-system available to tunr it on, IIRC, wasn’t there?