Someone is incorrect here, I’m not able to download MS Exchange support from the Jolla store on my 10 V, it just says there has been an error (as Jolla mentions). Is it possible you are confusing Exchange and personal accounts?
1 Like
Hi. I tested MS 365, not MS Exchange. These are different account types
Yes, that’s what I meant, the problem lies with Exchange, nobody is doubting that 365/personal accounts work: 10V Exchange install failing - repo issue?
I could’ve sworn that Jolla mentioned this problem somewhere, but I can’t find anything.
1 Like
In my phone, MS Exchange shows as already installed (probably was installed automatically when I sign in the Jolla account just after install)
1 Like
Greetings. If I am understanding correctly, I believe there is a single “app” from Jolla that is named “Microsoft Exchange” that one may install. That one “app” provides Sailfish with the ability to connect to two types of Microsoft’s email solutions: 1) M365, 2) an Exchange server.
Once that app is installed, when one goes to add an account, the two Microsoft-related options are available. If I am understanding @catonyourcomputer correctly, they are unable to get that app from the Jolla Store. This was the very problem that I encountered and by persistence and treading far past what I have done before, I was able to resolve, and about which I posted in that other thread that Catonyourcomputer linked two posts above this one.
I was reasonably certain that I must have done something to cause the Jolla app of “Microsoft Exchange” to not install correctly and that no one else would encounter this problem anymore since Jolla made it available to all in Beta period, IIRC. However, if someone else is receiving the same indications, then perhaps I can post more detailed instructions of how I resolved the problem and they can guide others who may be encountering this.
Furthermore, if Jolla sees the manner in which the configuration in SFOS was flawed, and someone within Jolla knows how that file is created, then perhaps the details of my phone’s misconfiguration can provide them insight for resolving some outlier case that perhaps I am not the only one to encounter?
Please let me know if you would like assistance. I suppose proper forum etiquette would be to post that in the other message thread about 10V Exchange install failing rather than going too far in this thread. I’m happy to help wherever, though.
5 Likes
After try to charge, I lose the functionality of battery indicator: the value is only update after a reboot.
I’m trying to change blobs to v4a, but fastboot shows an error
$ sudo fastboot flash oem_a SW_binaries_for_Xperia_Android_13_5.4_v4a_zambezi.img
Sending ‘oem_a’ (2097152 KB) FAILED (remote: 'Requested download size is more than max allowed
')
fastboot: error: Command failed
FIXED:
$ sudo fastboot flash -S 256M oem_a SW_binaries_for_Xperia_Android_13_5.4_v4b_zambezi.img
Warning: skip copying oem_a image avb footer (oem_a partition size: 2147483648, oem_a image size: 140733760284448).
Sending sparse ‘oem_a’ 1/2 (260092 KB) OKAY [ 9.110s]
Writing ‘oem_a’ OKAY [ 0.002s]
Sending sparse ‘oem_a’ 2/2 (204008 KB) OKAY [ 7.169s]
Writing ‘oem_a’ OKAY [ 0.001s]
Finished. Total time: 16.303s
Battery indicator works both in-charge and discharging, showing updated battery level.
NOTE: I flashed v4b binaries
Decided to take the plunge and installed SFOS in my XQ-DC72, unfortunately it doesn’t recognize any sim card or wifi. I am sure some people mentioned how they installed it and it worked for them and there was a mod to turn on the 2nd SIM which I read in the forum.
Did anyone else have the same issue - i.e. no SIMs + no WIFI detected with the XQ-DC72?
PS I used the Android_13_5.4_v4a_zambezi blobs
Hi. The current supported model is XQ-DC54, not the XQ-DC72. Maybe this is the problem.
Anyway, you can try with v4b blobs instead v4a.
no i flashed sfos on xq-dc72 too, it worked after that. although i used the recommended binary blobs from sony, so battery indicator doesn’t work
Then try with the v4b blobs. This fixed the battery indicator for me.
I could flash it without reinstall using fastboot
$ sudo fastboot flash -S 256M oem_a SW_binaries_for_Xperia_Android_13_5.4_v4b_zambezi.img
Thank you both, with Android_13_5.4_v4a_zambezi blobs the battery indicator was working for me but I had more fundamental problems –> no WiFi + no SIM cards 
Thanks for the fastboot flash, I will try it. Currently after flashing SFOS I can’t get the fastboot mode to load - I need to go back to android and start from scratch.
You can go back to Android and update until the latest Android 15 release. This is the version which I used before flash Sailfish. Reminder that you need to re-lock the bootloader to get OTA Android updates (if the bootloader is unlocked, Android doesn’t shows any update notification).
I installed the latest sailfish to dc72 by using v4b blobs, battery indicator works fine. So far quite happy.
Added MicroG without problems
- Installing microG on Sailfish OS
Added 2nd sim without problems
- Sony 10 V Sailfish images - #51 by chris_bavaria
-> but phone is missing ‘sim cards’ menu from settings.
Is it possible to add it? Or add in a command line to part ‘use SIM card’ => both
edit: cons, calling with sim2 works without audio. Sim1 works without any issues.
3 Likes
Quite sure the way above is not right way for adding 2nd sim.
Has anybody able to get 2nd sim to work?
Was cheking from my dual sim xperia III (bt52) and file ‘Dual-sim.conf’ are missing from folders
etc/ofono/binder.d
etc/ofono/ril_subscription.d (this does not exist at all)
I tried to fix it, broke my OS and reinstalled everything with v4a blobs.
This is a work in progress. I think SFOS for Xperia IV will never be available. Jolla will be ready when it’s ready.
In the meantime, switch to either Ubuntu Touch or Droidian. I think the community has migrated to that.
1 Like
Now, we can start the next part of “Jolla is working on SFOS for 10IV/V”
new blobs have been released - for zambezi, muray and sagami. - v7b
7 Likes
same as in v7a: simcard not found … + just all issues from previous versions remains.
!JOLLA BOYS ARE ON THE TURN!
after boot:
/vendor/bin/macaddrsetup /data/vendor/wifi/wlan_mac.bin
and bluebinder drains the cpu/batt (enanble/disable bluetooth solving bluebinder as in previous blobs)
strace for macaddrsetup producing infinite loop:
getuid() = 100000
writev(3, \[{iov_base=“\\3\\265\\23\\260\\255\\323h\\243\\2529\*”, iov_len=11}, {iov_base=“\\6”, iov_len=1}, {iov_base=“tadif\\0”, iov_len=6}, {iov_base=“Failed to connect to tad.\\n\\0”, iov_len=27}\], 4) = 45
socket(AF_UNIX, SOCK_STREAM, 0) = 4
connect(4, {sa_family=AF_UNIX, sun_path=“/dev/socket/tad”}, 18) = -1 ENOENT (Folder or file does not exist)
close(4)
5 Likes
Interesting.. still same..
@rainemak are you going to make some progress with this? 
Guys.. my birthday is comming.. come on.. 
Of course is the same. Sony changed protocol for intercommunication. So new firmware can’t be better without implementing that change.
5 Likes
that is why we desperately asking Jolla for some status if they work or p1ss on it …
2 Likes