I have done something wrong. I have ordered a sh Sony xperia 10 V, model xq-dc54 because I understood its the latest supported model, but after I purchased a licence sailfish os, i’ve seen there are versions that stop at Xperia 10 III . I do not regret paying the licence, as I know I contribute to Jolla , the wonderfull people and team and await the newly ordered Jolla Phone , but is there a way to install it on Xperia 10 V the model I will receive tomorow? I downloaded the latest Version for Xperia 10III sailfish OS. My mistake anyway …but thank you!
Thank you all for your quick support. You are right , I was not carefull enough but its a contribution and I feel welcomed and supported. It great to be a part of the comunity !!
Hi. There is one game-changing fix to make microphone work with anything besides standard phone calls. It has not been properly integrated into release images yet.
I am away from home, and not experienced with Discourse, so sadly I do not know how to properly link it. It is explained in the newest release notes - search my name there as I was the one who asked about the bug.
”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”.”
So guys my version of android is 14 . Is It necesare to roll back to android 13 and then flash sailfish or it works fine with android 14 too? It seems confusing the informations… and i am one step of flashing the image . Bootloader unlocked everything ok … can someone guide me thru the instalation process?
Thank you ! By the way the model is XQ-DC54
Does it work with sailfish image 4.6… or latest sailfish 5 ?
I have a 10 V and i flashed it with android 14. It does work but there are some bugs like camera does not work etcetera. Use V4 blobs to get the battery procentage to work.
hello, Sorry I do not understand my problem is with the microphone and camera. i tried to flash android 13 binaries onto partition a and b but nothing so far asuming that binaries 14 do not work . i upgraded OTA to sailfish os 5 still nothing … is there a workaround ?
You need to edit one of the system files, but you need to do it as root. The detail of the file and the line to edit was provided by @mal and is linked to here:
However, WARNING, you will be editing as the root Superuser, which can be very dangerous if you don’t know what you’re doing. You can quite easily damage your SFOS installation and make it unuseable - so be VERY careful.
You should start up the root file browser and then navigate to the file in Mal’s post. Then tap on the filename and you should get its properties displayed. Pull down on the top pulley menu and select ‘View Raw Contents’ That should display the contents of the file. Then pull down on the pulley menu again and select ‘Edit’. Change the line as directed by Mal, and then tap on ‘Save’. Exit the Root File Browser App.
Re-boot the phone (or use settings/utilities to restart the home screen and all running apps) and your mic should now be working.
This worked for me, but your situation may be different. But please be very careful if you know what you are doing. If you don’t know what you are doing then I would not recommend editing system files as root, but wait until the fix is released by Jolla, perhaps in 5.1.
Steve thank you so much and @mal too for making this possible i followed your advice to the letter and worked as magic . thank you all so much !! now, to cameras to make them work !! big hug to you as i do not have emojis in my keyboard !!
Settings → Developer Tools → Switch on Developer Mode (if not already done)
Go to app drawer and find Terminal
Input systemctl stop bluebinder and press Enter, then enter security code
The command doesn’t output anything when it has executed successfully. You will have to rerun it every time you restart the phone.
When you stop bluebinder, Bluetooth will break and you will need to run systemctl start bluebinder if you want to use it. Battery usage seems to be normal when there is a Bluetooth device connected; only when bluebinder is running and there is no device connected does the insane battery drain seem to happen.
Bluebinder failing to start correctly is also what causes the lengthy boot time.
Thank you so mych, I didn’t heard of it until now….but I had the impression that the microphone fix is causing the battery drain.. I will look into it . Thank you million times !!
