I unwittingly obtained the 10 V Hong Kong version with 8BG RAM. I’ve left it sealed and considered returning. But I’m willing to test for the benefit of the greater community.
Thank you @Ras72! Testing these global variants are super difficult for us for example due to bands – we love the community. We do our best. We continue discussing here at the forum & irc meetings but global landscape is super difficult. With you, Sailfish Community, we have a chance to deliver Sailfish OS for folks around the globe – we’re not yet there whilst you’re fee order. Let’s work together and utilise forum & irc for discussions
Good to heard, I’ve got XQ-DC72 waiting for flashing with boot-loader already unlocked.
I had to downgrade from android 14 to 13 but wasn’t able to do it with Emma, I had to use newflasher.
(TW_68.0.A.0.829)
Why don’t you just post in the proper topic?
Sorry I saw that the latest posts were dc72 and thought i would add, and also volunteer to be a tester
Judging by #sailfishos-meeting log it would be a good thing to verify my Xperia 10 IV is on Android 13?
I was trying to find something on the release schedule, like [Release notes] Sauna 4.6.0.11 - #119 by wetab73 , but everything’s a bit vague.
Are there any news on when one might get even the earliest possible access to install Sauna on an Xperia 10IV?
It’s a bit worrisome how soon vacations start, and there was a mention about the paid components like Android AppSupport coming in August, but do we have to wait that long to try out the phone without paid components?
And will it be possible to get paid components afterward without reinstalling/reflashing the phone?
Yes, it’s Android 13 based.
Free version will be published as soon as possible.
Free version would come first and paid components later.
Yes, similarly as it has been thus far. You can install let’s say AppSupport from the Jolla Store on the device after flashing.
I am looking for a new phone, and i consider Xperia 1 VI. Is that a bad choice for SFOS?
The Xperia models i can choose between are: 1 VI, 1 V, 5 V, 10 VI or 10 V
Does the community versions of SFOS lack important features?
Right now i have a short list of 2 phones: Xperia 1 VI, in case i will install SFOS, or Pixel 8 Pro to install GrapheneOS.
Well if you want offical support then the 10 V or 10 IV.
Also the Community version does not have any of the paid components like Android App Support or Exchange Connector …
Also the 1 VI is so new that its not in Open Devices yet so no porting Sailfisch OS also you have to port Sailfisch OS yourself to the Xperia 1 VI.
TLDR the Xperia 1 VI is a bad choice chose the 10IV or 10V
Xperia 1 vi is currently not supported by sfos. Officiak support ( with androud app support ) is only for 10 series, with uocoming support for iv and v. For 1 series there is only a Community port (meaning no android app support, only waydroid). This lags behind a bit, I think at the moment version ii is in the works
All community ports lack VoLTE support, plus all the paid features: Predictive Text/spelling, Android App Support and the MS Exchange stuff.
Individual ports will also have various specific limitations/bugs/features. And they may not have more recent version of SFOS yet (or ever). There a list of ports with feature grid, but it hasn’t been updated in a year and doesn’t include any devices released less than ~4 years ago.
I found some official-looking instructions for AOSP 13! Sailfish X Xperia Android 13 Build and Flash | Sailfish OS Documentation
Currently it seems fingerprint doesn’t work (very low-prio for me) and neither does the camera (somewhat low-prio for me).
If the Xperia 10 IV is otherwise generally testable, as my old 10plus is really, really bogged down, is there perchance a similar official-looking page with SFOS build instructions, or is that something to figure out yourself if you wanna?
Or if someone in the community has something?
Isn’t it so that one can just re-flash the AOSP build and that’s the only destructive operation? Which doesn’t matter because no SFOS data will be destroyed in a re-flash?
And then any SFOS RPM builds or upgrades can be installed with zypper so it should be generally safe to run a community build already (if you’re ok with those two things not working and Android support not existing), right?
Thanks everyone!
Official support for the 10 IV and 10 V was announced on the Jolla Love Day 2 (May 20th) to come out within “1 - 2 months” (i.e. by July 20th at the latest). And that’s the last time we’ve heard any news about it. There’s 12 days left until it becomes delayed.
10 € on Fri July 19.
With pleasure But I’m afraid it may rather be late August
Without functioning camera and all that, I really wouldn’t expect that to be such a literal month. Much less with the vacation season ramping up in June, having everything shut down in July, and slowly brushing off in August.
That’s why I’d be curious about running anything that resembles the end product, even without camera or fingerprints.
Of course this enthusiasm is somewhat slowed down if installing the official Jolla release requires a complete reinstall also of the base system, not just switching repositories and doing a zypper upgrade. On the other hand, that’s what backups are for, and just running the OS does not necessarily make it your daily driver either.
But until someone says “sure, here’s a community build script” or instructions for making one, I’ll stick to my belief that we won’t see anything until maybe late September.
That would be a shame. The screen of my actual phone is smashed since the beginning of March and looses bits of it day by day. I tried now to stop this process with windscreen resin. But I’m not sure if that keeps it alive until September.
I have two Xperia 10V here waiting eagerly for SF and I pre-ordered the community phone. My hopes are high that I can hold one of them in my hand running SF before my rephone has dissolved. Believe me, it’s no fun to use it at the moment.
I bet Jolla is delayed as usual. But I hope that they can deliver at least until mid of August. What scares me a little bit is, that they didn’t communicate how the progress goes on. They could have written a short sentence about it like they did in the community news before. Keeping silent on that point isn’t a good omen I think.
What scares me a little bit is, that they didn’t communicate how the progress goes on.
Don’t be scared! Look at it positively: They put every ounce of effort into the product.