Now, you only need the free trial-licence. And for what comes in future we still have to wait.
3 Likes
The xqdc54 image works for the xqdc72, at least for all the people that have tried and I have read about on the forums. It also worked for me.
You do have to change the model number in the install scripts (and the md5 checksum). Search these forums for more specifics.
4 Likes
I finally spent some time over the weekend flashing 5.0.0.62 on the Sony Xperia 10 v which has been languishing in the drawer for the last six months. I followed Jolla’s instructions and flashed over Android 13.
The flashing went without any problem and I have been using the phone in anger over the last day or so. Here are my observations:
The Bad
- Battery percentage does not update (as advertised)
- Fingerprint doesn’t work (as advertised)
- Headphone jack doesn’t work (as advertised)
- Cameras don’t work (as advertised), including the flash as a torch
- A reboot takes up to 5 minutes. At first I though the phone had bricked it took so long, so I did the Power+Vol-up key combination (which appeared to do nothing) but later, when I just got fed up with it and left it alone it really did successfully re-boot after all that time
- Mobile data often, and randomly, simply stops working (as others have reported). In settings it says it is connected, and even the mobile data icon in the status bar is present, but nothing can connect - native or Android. I’ve found no single reliable way of getting it back again - toggling mobile data on/off doesn’t work, restarting networking in settings/utilities doesn’t work, selecting the network manually doesn’t work. Rebooting the phone mostly does work, but obviously this takes far too long. Sometimes it comes back of its own accord (when it reconnects to the cell it was originally connected to, after moving out of and then back into range, I wonder?), but this is a serious problem for Jolla to resolve before there is any chance it can be used as a daily driver.
- Screen is supposed to be almost twice the nits brightness of my Xperia 10 iii, but with Sailfish on it, it isn’t - in fact its much dimmer than the 10 iii. As others have remarked, this must be a software problem.
- Battery life seems OK (using battInfo for Xperia 10V | OpenRepos.net — Community Repository System which is a great little app to use until Jolla can fix the proper battery usage display with new blobs), but I think this app understates remaining battery capacity a little (which is better than overstating it!)
The Good
- GPS fix time out of the box is very good and way better than the Xperia 10 iii (even with the SUPL modifications). For the first time I am getting a fix indoors in just a couple of minutes. Looking at the gps.conf file this seems to be almost totally different from previous incarnations - lots of extra ‘A-GPS-Inject’ parameters but no SUPL server entries. Perhaps a different method is now used to get a first fix?
- Memory management seems to be way better than on the Xperia 10 iii (which I don’t understand - both have 6Gb, both are on 5.0.0.62, etc). So far I haven’t had a single OOM situation with apps killed. I’ve really gone at it as well - lots of long web pages scrolling with photos and videos, loads of apps open (including others with webviews) but, as yet, not a single app closed. Using Crest the difference seems to be that the Xperia 10 v is actually using the swap memory to its full advantage, where as on the X10 iii swap is minimally used in exactly the same situation on the same release with the same apps open doing the same things - so the X10 iii runs out of main memory much faster and more often. Why these differences exist I don’t know. Could it be that the X10 v is freshly flashed (so perhaps newly flashed memory management settings), whilst the 10 iii has been upgraded OTA over many releases since the 4.x’s (so perhaps old lingering memory management settings)? Whatever the reason, I have gone from an X10 iii with irritatingly daily OOM issues to an X10 v with none. Good news indeed.
- Android support works well. With MicroG installed and the upgraded API level to 33 my banking app (Santander UK) now works fine, as do some other apps which didn’t previously
- Sound has not disappeared yet either - as it frequently does on my X10 iii. Maybe another consequence of better memory management?
- The whole experience (other than ‘The Bad’ of course) is very smooth and fast. Of course the 10 v is a more pwerful phone than the 10 iii, but it seems well suited to SFOS if Jolla can get the blobby bugs and mobile data issues ironed out.
16 Likes
Also, Aurora store in some cases lost connection, don’t know why. Switch between wifi and data didn’t help. After some acrions it turned that back 
Why wouldn’t predictive text input work specifically on the 10 IV or V? It has literally zero to do with hardware. And it does work in the very same 5.x OS on the 10 III.
Isn’t it rather some money-related issue, i.e. that it takes paying some licence fees for using XT9? Wasn’t it former Nuance Communications, now acquired by Microsoft, who owns copyrights and needs to be paid? Clearly, Jolla does not want to pay it and decided to drop XT9, despite increasing their own licence prices at the same time.
2 Likes
I’m sure someone will correct me, but my understanding is that since the Microsoft acquired Nuance Communications, they haven’t made any new XT9 agreements with anyone and the old Jolla agreement was lost when the old Jolla Oy went bankrupt and new JollyBoys Oy was formed, so they can’t legally provide the XT9 on new products.
1 Like
As XT9-Replacement or alternative I suggest the Presage-System/Keyboards.
Open Terminal and enter:
zypper install keyboard_presage-de_de
This will install the german Presage-Keyboard or replace the last 5 chars with your language shorts like (en_us, sv_se, hu_hu, ru_ru, es_es, et_ee, fi_fi, taken from Openrepos.net, maybe there are more and not listet like en_en…etc)
!!! Follow this Thread for more Instructions and if you have Questions! !!!
5 Likes
Presage and Okboard combined seems to work well too for those that like swiping.
1 Like
Some more testing of mobile data today. If you stay stationary mobile data seems to work fine. However, driving around and stopping at various locations on my journey to retest, mobile data always disappears and is very difficult to get back again. So perhaps there may be a problem when moving between cells?
as there is no tap to wake, magnetic sensor for flip covers is important to me too 
AFAIK there is no magnetic sensor in V. I didn’t noticed it in Andy.
But I do recall that tap to wake workaround was mentioned here somewhere.
for wake and suspend display. so does it work under android? in SFOS i have no option for that like on 10II (settings - display)
If one have Xperias 64-bit devices like Xperia 10 II or 10 III with paid sailfish licence XT9 can be extracted using this command:
You need to install zypper first: pkcon install zypper
mkdir -p xt9-rpms; for i in $(zypper pa -r xt9 | fgrep xt9 | cut -s -f 3 -d ‘|’); do pkcon download xt9-rpms $i; sleep 1; done
1 Like
Thanks! Any hope that you’d publish it on Jolla Store as well? Maybe a little stripped down version (without priviledges) sure, but that’d be great…
Are the new blobs from Sony out?
This was released on Mar 25.
Yes, it was discussed at the end of this thread a bit
1 Like
I tested these _6a blobs. Nothing changed. And lately my 10 V SFOS 5.0.0.62 froze totally. Just pressing vol down + power buttom 10 V long time helped phone to get alive. My phone was also very hot. Returned after start up and shutdown (to be able to start fastboot mode!) back to _3a blobs again. Had time to note that 10V lose its mobile connection / sim card totally. Only wifi worked.
2 Likes
Can confirm exactly this behaviour. Jolla needs make some adjustments on SFOS
3 Likes
Not sure if anyone’s noticed this before, but I’ve had issues with the phone gradually slowing down to a halt before freezing for a few minutes.
Problem only seems to occur with AppSupport running. Appears to possibly be an issue with the v4b blobs, can’t remember this being a problem before I flashed them. When the phone is frozen, it doesn’t respond to touch or the side buttons. So far I’ve just had to force a restart every time with Volume Up + Power.
This is a small issue but it is starting to get annoying to the point where I might switch back to the old, worse blobs (mobile data issues and no battery indicator) in order to have the phone be usable.