Thank you very much, I will, but just waiting for the Jolla support to confirm if there is any risk to break anything on this phone using the other image. But it seems the helpdesk jolla support is not working anymore, several weeks without any reply …
5 Likes
Yeah sorry, you’re right, it seems I’ve gone too far by thinking that big companies like Sony, or other big companies like Intel, Google, Meta, Apple …etc could do anything to break the user’s privacy. Anyway it never happened till now, so I’ve got to stop being paranoid.
1 Like
All versions use proprietory blobs, so making do with the older, less functional blobs doesn’t make sense
1 Like
It makes sens, as more users (the owners of DC72) will use it and give more feedback and eventually debugging. Instead of waiting for the new blobs to give them the chance to try it, we are waiting for several months now for these famous blobs, maybe more to come …
1 Like
On the off-chance that you are still struggling with this, the solution is to uninstall opt-* stuff. It was pulled in as a dependency of some package but did not get removed. You can check to see what you have installed with:
pkcon search opt- --filter installed
Then you can remote that unwanted stuff. I had to run:
pkcon remove opt-qt5-qtbase
pkcon remove opt-kf5-kconfigwidgets
Then I checked again with the --filter command above to see that everything was removed. After that, the update to 4.6.0.15 was successful. I had confirmed with Jolla support that opt-qt5/kf5 are not part of the standard Sailfish installation before running those pkcon remove commands.
2 Likes
You can also do something like
find /opt -type f -exec rpm -qf {} \; | sort -u
3 Likes
I am trying to reflash my Xperia 10 V using the latest Sony files etc.
I have reverted my Xperia 10 V to Android using the Sony Emma tool but when attempting to reflash Sailfish still get the dreaded FAILED (remote: ‘GetVar Variable Not found’) error message.
If I try and use the individual fastbook commands listed above, the Xperia comes out of fastboot mode (Blue star) after the first fastboot.
I’m clearly doing something wrong. Do I need to contact support or is there something I’m missing please?
TIA
Maybe the well known problem of USB3 ports?
It may be well know to some but I am afraid those words don’t offer any solution.
What exactly is the answer please?
Try to connect your phone to a USB2 port.
1 Like
You need an USB hub with USB2 jacks (white) if you only have (blue) USB3 ports on your computer. Flashing using USB3 ports on computer doesn’t work.
I tried using a hub with ports marked as USB2 but this failed and I ended up using an older laptop with native USB2 ports. (I can certainly confirm that flashing using USB3 doesn’t work!)
I’ve now successfully flashed my Xperia 10 V 
but not before having to reinstall Android twice using the Sony Emma tool and attempting to flash using a Windows 11 laptop. The latter didn’t like the Sony fastboot driver sa0114adb.inf
Other than being a frustrating process it has now worked though so many thanks @phklrz and @Seven.of.nine and apologies if I appeared tetchy.
I’m now hoping that Jolla can fix the Camera, Fingerprint and other issues with the Xperia 10 V without requiring us to flash again! App support is now working but without the camera some Banking Apps won’t work because the registration process relies on it.
4 Likes
Congrats! And, after the first flash from Android to SFOS, further SFOS reflashes are much much easier! You will not need EMMA tool any more.
1 Like
I don’t have opt-* packages, but upgrade still fails and says it needs 6MB more space in /opt.
You can also try what @nephros posted which will get you all of the packages that have files in /opt. It’s more generic than what I posted.
I think it should be \; instead of ; in that command though. It will also take quite a while! For even better output where it ignores unowned files, try this:
devel-su find /opt -type f -exec rpm -qf {} \; | sort -u | grep -v "is not ow
ned by any package"
Actually, I think some unowned files were my problem. I had been developing a package, so I had a lot of stuff in /opt/sdk filling space. Update went through after cleaning that up.
1 Like
Dear Sailfish team (@jovirkku) in April 2025 I bought a Xperia 10 V with the intention to send my up to now used Xperia XA2 into retirement soon. To do the switchover XA2 to 10 V as as soon as these known issues are solved.
By today these issues are still present after you announced them one year ago.
Please share your plans to update Sailfish X for Xperia 10 V and solving these issues.
Looking forward for your reply!
Kind regards
Finlandia
10 Likes
Support for Xperia 10 V is dead, obviously.
They will never admit it publicly, but the only somewhat supported device is the fugly joke of a phone called Jolla C2.
If you want to have a somewhat usable Sailfish OS phone, get the Jolla C2.
1 Like
Any facts or just larmoyant blabla?
1 Like