What if it was only fixed last week - is it still so bad that it wasn’t released yet?
What if it breaks more other things than it fixes - do you still want it?
What if more things get fixed next week and then can also be included?
Seems 5.1 is planned for ~March.
March. But which year?
Jolla is marching fast at the moment, so Mars is with you if you join the star fleet with pure thoughts in mind.
Yes, give me an easy way to test - it’s pre alpha quality anyways at the moment.
OT:
Can a good soul post the output (from terminal) of:
getprop persist.vendor.somc.cust.modem0
on a X10 IV?
Thanks!
nada
[defaultuser@Xperia10V ~]$ getprop persist.
vendor.somc.cust.modem0
[defaultuser@Xperia10V ~]$ getprop persist.
vendor.somc.cust.modem0
Same as root
I confirm.
(twenty chars)
Sorry, I thought he mentioned Xperia 10 IV ? You seem to have Xperia 10 V ?
You are right, my mistake. Sorry about that I overlooked the I in IV
I have 10 IV (5.0.0.68). After finishing SSH, the mobile remained frozen, I had to restart it.
May I please ask, just for interest:
Why does Jolla / SFOS so heavily depend on these Sony blobs?
How do other phone OS’es deal with this problem?
TLDR: When I started with SFOS on Xperia 10 in 2020 I had 3 devices. They all still work. One of them I flashed to LineageOS for curiosity a few weeks ago, and now I have on this 6 yrs old device: VoLTE, VoWIFI, a working camera, 3 days battery time without recharging, a semi-normal working GPS (not like a Garmin but much better than SFOS), and others.
For flashing LineageOS I didn’t need any Sony blobs.
How do other Phone OS’es achieve this, while Jolla can’t?
Please let me know the holy secret, too, if someone knows the answer.
![]()
They are literally Android.
Don’t call them OSes.
This may have slipped by some people, but there is a fix for the microphone which works with the v4b blobs. Its not been included in any release (don’t know why as its only a small change to a text config file), but it solves the issue where the mic only works with traditional voice calls. After the config file change the mic will work with other apps as well (so you can make voice calls with Yottagram for instance).
The fix (from Mal) is:
The fix wasn’t included in this release yet but in case you need it you can fix it manually. Only change needed is to change the first line in /etc/pulse/arm_droid_card_custom.pa to be “load-module module-droid-card rate=48000 hw_volume=false source_format=s24-32le”.
I’ve tried it and it works fine.
I have an Xperia 10 V (XQ-DC54) with Android 15. Now I would like to flash with this Jolla’s instruction manual “How_to_install_Sailfish_X_on_Xperia™_10_V_on_Windows__The_Privacy_Respecting_European_OS_and_AI_Solution_Provider.pdf” and the blob "SW_binaries_for_Xperia_Android_13_5.4_v4b_zambezi " SFOS on it.
At what point in time with regard to Jolla’s instruction manual do I have to flash the v4b blob file with which tool under Windows 10?
What is the right source of that file? Is this the right link: Software binaries for AOSP Android 13.0– Kernel 5.4- Zambezi (v4b) | Developer World?
Do I need to consider anything else?
I would also like to write down all the necessary steps in a small howto_flash_Xperia10_IV/V.md manual.
Especially to give others in this channel good guidance.
What the heck is that?
The normal installation instructions are here and most definitely not in PDF.
It is not a manual step. Just follow the guide.
If it gets you the correct file, then yes. Otherwise no.
Please don’t. The official guide is fine.
@Attah Thank you very much for your answers.
I understood. I downloaded the How_to_install_Sailfish_X_on_Xperia™_10_V_on_Windows__The_Privacy_Respecting_European_OS_and_AI_Solution_Provider.pdf document when I purchased the Sailfish_OS-Jolla-5.0.0.72-xqdc54-1.0.0.47.zip from Jolla. It contains the same content as the internet page what you mentioned.
If I’m right I must only exchange the name SW_binaries_for_Xperia_Android_14_5.4_v3a_zambezi.zip by
SW_binaries_for_Xperia_Android_13_5.4_v4b_zambezi.zip
at point 5.1 in Jolla’s Instruction page.
If the instructions say v3a, that’s what the script will expect.
If you want to flash some other binaries, you can of course do that (and this is manual) - but there is no “have to” involved. It can be done at any time, including after having used the phone for a while.
You can always read the script to find the command to flash binaries.
Hello everyone so if I understand right, does any of the above solve the fingeprint or camera option ? Than you !
The short answer is: No.
The long answer is: Nooooooooooooo