Juz, there was some discussion a while ago on the 10 IV thread about enabling dual sim. I was sure I’d read someone had managed it but couldn’t find the steps or the results. Was that you? Would you mind sharing what you had to do to make it work?
Edit: Found it! Thanks!
That’s great!!
I gave up in July/August and have just come back (I bought it in May)
Do you have any recommendations or a link to follow?
I will get it out the box & try today (no updates & android 13 i think).
That link was good. I’ve never done a SF install (only bootloader unlock & change to global for mi mix 3 when i bought new).
Has someone posted a link for instructions for 10v 72 (dual sim)?
I’m not a coder and arm worried about wrong android, binaries and editing the config.
You need to download the SFOS 4.6.0.15 files from here. Then follow the below steps to patch the installer to work with the 72 variant.
After that you can follow the steps in the appropriate PDF from the link above to flash SFOS as normal.
Thanks very much.
Hahaha good old Telstra. I remember them when i lived in Aust (& their high prices).
Hey guys are you using Android 13 or 14?
Downloaded SF image
I have been learning about TA partition & DRM keys.
Downloaded Xperifirm & downloading 68.0.A.0.829 firmware (72 for SEAsia)
Then putting NewFlasher.exe into firmware directory created by XperiFirm tool.
Then follow
After I have DRM I will follow PDF instructions
You do not have to worry about the TA partition and DRM keys, they get restored if you revert to Android.
Really?
Hours of learning (people said they’re deleted once u unlock the bootloader and if u revert back to android u won’t have them).
I have the firmware and just put Flasher in there, deleted the 4 sin files (https://xdaforums.com/t/flashing-firmware-with-newflasher-on-xperia-1-iii-without-losing-data.4341413/)
and was just about to start.
So just forget about it?
I reflashed multiple times between Sailfish and Xperfirm / Newsflasher my 10 V.
Currently it is with a rooted version of Android without Google Play and stuff, for Magisk I needed tge SIN files for Kernel patching.
If you keep these files, they are rather small anyway, based on my experience it should be safe to switch back and forth between Sailfish and Android flashing
I am really sad, but have to say it’s getting time to look for another OS. There is no visible progress again and that for this not even new device.
Months passing by, at first Sony has been blamed for the missing blobs (not that there wouldn’t be other devices with better support for open development as well), then again plain nothing and that for almost 2 months now since they have been released.
Again no feedback, no reports, no sign that they even care.
There has been a lot of complains about the missing feedback and about that there are no progress reports and in between it seemed to become better, but it didn’t stay this way.
My impression that this entire project is dead is very much confirmed. I started this topic in Sep’ 23…!
Can’t say I’m angry or something but plain disappointed and tired.
What OS are you thinking about?
What or who confirmed this? And where?
What OS are you thinking about?
Not sure yet, need to investigate. Ubuntu Touch came a long way it seems.
No one, just my conclusion due to not getting proper feedback or any other visible/noticeable progress in over more than a year of waiting and it appears not to be only when it comes to Xperia 10V.
Doesn’t the Jolla C2 use Android 13 (API 33) and it doesn’t seem to be negatively affecting anything? Aren’t Android 11 or 12 blobs still the recommended ones for the 10 III, and Jolla doesn’t seem to wish to do much about it, even though Android 13 (and even 14) blobs have been available from Sony for the 10 III for a long time? Clearly, none of those devices actually really need Android 14.
If so, then how come that SOLELY for the 10 IV and V Android 14 blobs (rather than readily available Android 13 blobs) were so important, that they were chosen even though it was well known that Android 14 blobs from Sony had been broken in many ways (battery level reading, power consumption issues, camera, etc.) and it might take ages (if ever) to have them fixed, whereas Android 13 blobs have been much more mature and finished, readily available? What was the real benefit of choosing to use Android 14 rather than Android 13, if even the kernel versions are the same, and A14 isn’t even anymore the latest Android version, as A15 managed to come out in the meantime (and quite likely Sony will focus on releasing and polishing A15 binaries rather than 14)?
Please, tell me that it wasn’t only to have a cheap excuse not to have to do much about the 10 IV and V support in any foreseeable future, just keep blaming Sony for not providing fixed A14 binaries and focus on the C2 and Mind2 instead… Because, sadly, that’s how it’s been looking like since summer 2024.
If it turned out that it was the actual reason then I’d be really… disappointed, to call it in a polite way.
I’m using an xperia 10 v with sailfish os right now to write this comment. It’s my daily driver now. Although camera and hotspot would be nice and android support maybe. Also jolla employees were on holiday and came back only the end of last week, so i guess they’re busy right now and any day or week there will be updates to the os.
I would be brave enough to do the same, use the beta as daily driver, but in Portugal I can use the 10 V only indoors, for outdoor use the display is too dim (only in Sailfish)
Try to use one of the light ambiences like glacial or create a light ambience yourself
Does not make a real difference, my X10 iii must continue to do the daily driver work. It is much brighter, problem of the beta software (hopefully)…eagerly anticipating the final image for the 10V
Yes. And i forgot the audio Jack. It would also be nice if that was working. But this way i use my iPod more for listening to music