Coming soon, just sayin’ …
https://www.notebookcheck.net/Sony-Xperia-10-VII-specs-outed-in-leak-ahead-of-launch.1006000.0.html
Coming soon, just sayin’ …
https://www.notebookcheck.net/Sony-Xperia-10-VII-specs-outed-in-leak-ahead-of-launch.1006000.0.html
Interesting, I reached the requirement of 8gb on one game, I checked on the internet and apparently that and 10 VI are the only xperia 10 with 8gb of ram.
I hope, Jolla will not continue this path (with the recent difficulties for X10VI and V) and either switch to continue the “community phone” path with better Hardware from Reeder or develop a porting agreement with Fairphone, Gigaset or someone alike finally.
Jan 2025:
Jan 2025:
Nov 2024:
Nov 2023:
Jan 2023:
Mar 2022:
My 10vi stands ready!
does it support sailfish through some community builds at least? I would be interested on the performance of that phone since I love to squeeze the hardware but I don’t want to wait till is officially supported (if ever).
My concern - shown in the history trail above - is not that Jolla use Sony mid-range phones, rather; that Jolla is taking on too many commitments to be able to support [any] model within the commercially available lifespan of that handset.
Me years ago:
“I have doubts that Jolla can support both the 10iv and 10v at the same time…”
Jolla:
“Hold my beer! We’re gonna do the 10iv and 10v, create an entirely new C2 device with a different business model. And they’ll all be fully supported devices in 2026 before the 10viii is announced…”
As someone that follows the development closely, the evidence (=repo activity) does not line up with that (especially not as a full, only or even main explanation). I am sure i said this several times before, but yet here this theory is being paraded around again.
The main driver of the amount of work are the generational updates. Skipping every other does not substantially reduce work, since the changes are cumulative. I very rarely see model specific impact creeping outside the model specific repos.
For a strict definition of commercial availability; that ship has already always sailed on Sony’s side of things with when the driver binaries become available.
What is theoretical here?
We’re about to see the retail launch of the Xperia 10vii at the same time we have yet to see commercial licence support for the 10iv and 10v.
At the same time as we’re a year deep into the launch of the C2 - which is still an ‘early access’ device.
We all accept that SFOS arrives late in the lifecycle of an Xperia 10 device, due to availability of AOSP blobs and dev time on the back of that, however…
There is a useful commercial window for Jolla where the devices they sell licences for remain widely available to potential SFOS customers. That window is rapidly closing.
It is not unreasonable to question whether in biting off more than they can chew Jolla are actually damaging the potential available market share for its ‘product’.
10iv
10v
C2
And all the while; the widely available and very affordable 10vi begins its own journey into obscurity…
Maybe the upcoming Reeder S919 would be an better option then every Sony. Once again another SOC and Modem (MediaTek), but a much better Hardware equipment than the C2 and features like 5G, NFC, Fingerprint etc., which are really missing on the C2.
The specs I found for that phone are: 16gb Ram, AMOLED FHD+, 200Mp camera, MediaTek Dimensity 9300…
quite impresive…
And as we all know, the delay on those is due to Sony binary quality - not Jolla.
The 10 VI looks to have only gotten somewhat properly released in AOSP in Nov/Dec. The VII is completely uninteresting until it is.
The C2 being a completely different chipset does add extra work of course. I’m not convinced ultra-low-end was the right choice. As can be seen on other smaller Chinese domestic platforms (i’m looking at you Pine64), they usually have a very long tail of quality issues in their adaptations.
The question isn’t unreasonable - but flaunting this as the only explanation is. Lots of fixes go in to both devices - and again the work required for the latest version is, and i cannot stress this enough, cumulative over all generations.
So let me do a slightly more distilled version of the (counter-)argument i’m making: dropping the IV would be all but marginal in time savings.
Surely the continued work on Sony phones has been helpful for rinigus, and especially Thaodan’s ports - and their work to Jolla.
There is certainly a point at which the adaptation work is too big to manage - but there is no repo evidence that we are at that end of things! On the other side exists the case where people only do adaptations every 3 years and have even bigger changes to handle - and are out of practice when they do. Fortunately we don’t seem to be at that end either.
I dont hope that… “please limit our choice as much as possible” is nothing I am going to ask for. They may, but I am very happy to have other options available.
But anyway, that is not my decission in any case.
That does look like a more interesting device than the C2. I’d buy it.
me too… I’m afraid of the price for such specs…
No, agreed. I am entirely persuaded that the iv and v have such great similarity that supporting one is defacto supporting 95%+ of the other. Why not have both!
That said, my argument isn’t limited to iv and v, rather it is iv and v and the entirely different C2.
Accepted, and support can’t begin until Sony have dropped decent quality binaries.
My concern is that iv, v, and C2 will still be sucking up primary device development time well into (and past!) the commercial availability of the vi. Over and beyond the availability of decent binaries…
This is where the argument goes off the rails.
Nobody could foresee that the binaries would not work, let alone for this long,
And are you seriously suggesting Jolla to walk back on their promise of support (however premature it may have been)?
But perhaps most importantly; if we agree that the IV is somewhat of a bonus to the V - how can you then seriously argue that the V-VI relation is so different that it warrants a completely different approach [i.e. would have been better off not having done any work at all on the IV and V]?
again, you’re kinda dodging the part of the C2 in all this.
it is the totality of the of the commitments that are the problem.
given how ‘recently’ 10iv and 10v support was announced, if Jolla knew at that point they were going to commit to the C2 as an entirely separate device class would it not have been better to say:
“Chaps, we have plans, and that doesn’t leave us development bandwidth to do these current generations of 10 devices. Lets face it, they’ve already been superceded in Sony’s annual device release schedule, the 10iv is already hard to find anywhere as “new”, and we’d be looking at another year before we could provide commercial SFOS support for them. We’re going to come back to the 10vi when commercial support for the C2 is squared away to the satisfaction of our customers; you.”
Nov 2024:
And you are tacking the number of Xperias on to the argument. This same tired argument was being made far and wide already before the C2 came around - and sure, i’m bunching you in with those instances of it. “Just port to Fairphone every 4 years and Sailfish OS will rule the world before long” was an all too common sentiment.
With 20:20 hindsight that might have been the better option - but that changes nothing now. And again, nobody could have foreseen such a big delay from shoddy binaries.
But let’s also be real here - the work spent on them will significantly help the VI/VII. So where exactly is it that you are seeing this big amount of time that could magically be freed up? Watching the repos i’m at least not seeing massive amounts of device-unique (non-reusable) effort being spread left right and center. Maybe i’m wrong - but then point to it.
no way
I don’t wanna use another look-alike phablet from these … mfgs
Regarding 10mk7, 120Hz is a nice addition, though I really hope to see a wireless charging, because it’s long overdue and especially since there’s no 5 model anymore to compete with. Upgrade of the shitty camera would be nice, too.
PS after all these years starting from N9 I’m thinking about pixel fold with grapheneOS
if only Google would make it narrow like samsung fold.