The one on XDA or you know about some newer port for 10 IV?
As far I understand right:
You’ll only flash only blobs *). After that you’ll just update the SFOS 4.6.0.15 to SFOS 5 as OTA. But things can be more complicated of course outside my understanding. Or vise versa.
*) fastboot flash oem_a SW_binaries_for_Xperia_Android_14_5.4_v?a_zambezi.img
yep, the OTA part is clear but what about if there is new blob? should I flash it and reinstall SFOS on top again or somehow I can keep my SFOS installation? Pictures, etc…
You do not have to reinstall SFOS, you can keep everything.
What’s the support for WPA3 Wifi Networks at the moment is it just not working on the Xperia 10V or in general on Sailfish OS?
As far as I know, it is in general not supported on SailfishOS
See also here: Does SailfishOS not support WPA3? - #2 by pvuorela
1 Like
Thanks for the Info i will ask about it in the next Community meeting.
Hi, guys!
Jolla promised 10 IV and 10 V Sailfish OS for August 2024 as well as working Jolla C2 and non of this is happening. Also no update for the 10 III or XA2 for looooong time.
Isn’t it possible for Jolla to get info on the upcoming Xperia 10 VII from Sony and as soon as Sony release it we get (WORKING)Sailfish OS for it?
2 Likes
What answer do you expect from the community?
1 Like
Why don’t you drop Sony a line? 
2 Likes
I’m just puzzled.
Either Jolla business model is broken or their engineers can’t maintain what they got gifted from Nokia flawless N9 project.
https://blog.jolla.com/ is also not maintained so I was just looking for an answer here because almost 2 year old Xperia 10V is supposedly the newest “supported” device. Thats all.
4 Likes
Jolla can’t do much before the phone enters the Xperia Open Devices program and the AOSP blobs becomes available.
4 Likes
I would be interested in hearing the answer, could you maybe post it in the mentioned WPA3-thread then?
I can’t post them there because the thread for that is locked.
Oh right. Well then I guess you can post it here
So, it here is installed SFOS I can freely (re)flash underlying Android(?) blobs and all the SFOS install remains the same? Is it so well HAL works? 
Yes, you can reflesh blobs on oem partition independent from OS :
2 Likes
Here ist the part about WPA3 from the meeting logs.
Meeting Log
08:05:36 #topic WPA3 Support any plans/news? (5-10 mins – asked by tfinn)
08:05:44 #info <tfinn> Support for WPA3 in Sailfisch OS are there any plans for it at
08:05:44 #info <tfinn> all? Would be useful to know, because the use of WPA3 is increasing.
08:05:44 <rainemak> #link Does SailfishOS not support WPA3?
08:06:03 <rainemak> #info <Jolla> The WPA3 support has not been worked on actively. However,
08:06:03 <rainemak> #info <Jolla> Simultaneous Authentication of Equals (SAE), WPA3-Personal is
08:06:03 <rainemak> #info <Jolla> enabled in the wpa_supplicant. It is not yet supported in connman.
08:06:03 <rainemak> #info <Jolla> On top of that we need user interface integration.
08:06:03 <rainemak> #info <Jolla>
08:06:06 <rainemak> #info <Jolla> As you are rightfully noting that use of WPA3 is increasing, we
08:06:08 <rainemak> #info <Jolla> should consider finalizing WPA3 support. Good input for planning.
08:06:10 <rainemak> #link wpa_supplicant/rpm/build-config at master · sailfishos/wpa_supplicant · GitHub
08:09:51 <direc85[m]> I have a WPA2+WPA3 mixed config on my home WLAN, and will have for a long time…
08:10:22 <tfinn> Yeah I also have it configured this way after finding out that WPA § is not supported
08:10:36 <tfinn> *3
08:12:39 <flypig> How much of this could be contributed to by the community? Is it fair to say that the connman support could be (all open source), but the UI changes maybe not (some non-QML closed source)?
08:13:09 <rainemak> flypig, that’s a correct assessment
08:14:05 <rainemak> I didn’t manage to get details regarding what’s missing from connman
08:14:21 <flypig> It would be interesting to know if it’s supported by upstream connman.
08:14:33 <flypig> The connman side could be looked at without the UI I think (can probably be tested using dbus), so there’s scope to do something as a community here. Given time and energy!
08:15:57 <rainemak> correct… I think it’s exactly like that. D-Bus version could already be used for testing but surely UI could show misleading infos… but testable
08:17:06 <rainemak> we should open more details in Does SailfishOS not support WPA3? on what’s actually missing and what kind of an approach could be taken
3 Likes
my gf still asking me when will be working release of SFOS and reminding all the time that i said that it should be until Christmas 2024… well at first place she complaining about battery status so instead of listening that she rebooting phone again and again and how stupid it is I better made simple battery info app, to let her see something what is better than nothing…
https://openrepos.net/content/kozaobecna/battinfo-xperia-10v
17 Likes
Nice one!
But are you sure that the maximum voltage is 4.2V? While charging, it goes up to some 4.5 - 4.55V and when you disconnect the charger near 100% the voltage is around 4.37 Volts. It goes down to 4.2V only around 90% battery level. They add some chemistry to their Lithium cells to allow such higher voltages being safely used and this way artificially increase capacity. It’s not only on the 10 V but also on the 10 III.
I am recharging my 10 III right now and the voltage (at 88% battery level) is reported as 4.427V and increasing.
and at 95% it is reported as 4.482V
And even after being disconnected from the charger, i.e. in a normal discharging state, the voltage at 98% remains at 4.35 - 4.37 Volts.
I observe the same phenomenon on the 10 V, so I guess that you should check it as it’ll probably take using some higher value than 4.2 Volts as the max voltage corresponding with 100% charge level to get more precise battery level percentage calculation. At least on the 10 III (while normally discharging), 4.2 Volts seem to correspond with battery level of 90% or so, so with 4.2V used as max voltage you actually “lose” some 10%.