Yes, I can see how your provider has a “volte_wifi” variant MBN available. Unfortunately my provider does not have that.
Here: lilac
Sorry, post is too late now. Got suspended for a short time cause they had to check the link I posted I guess.
Anyway, I got this link bookmarked and check now and again to see if anything new came up. Meanwhile hoping to see a 6.x version.
Don’t hold your breath, There is an Android 15 /LOS 22.1 build of LineageOS for lilac available in XDA Forums, but it is still experimental and not ready for use as a daily driver. I don’t see that changing any time soon, so my builds (of LineageOS for microG and IodéOS) will be sticking to Android 15 / LOS 21.0 for th foreseeable future
3 Likes
Can I get changelogs somewhere?
Sorry - not really!
Alternatively: basic changelogs for IodéOS are available in the News app on the device, but there is not a lot of detail
The build also includes the changes in upstream LineageOS that happened between the date of the previous build and the date if this build. There’s no easily available list of this either 
1 Like
I’ve done the new update 5.12 (25 may), evrything seems fine.
Thank you
There should be a 5.13 update along in the next few hours: I started a lilac build but the v5 .13 sources had not been pushed. Sorry
3 Likes
Thanks, I did the 5.13 everything seems ok.
Thanks a lot
Are we any closer to V6 on lilac now maybe? 
Edit: and is the update to 5.13 supposed to be found by the updater yet?
Mine doesnt show it…
Thanks for al your efforts Iode Team and especially @petefoth !
The stable, working LOS code for this device is still 21.0 which is Iodé 5. I don’t see any signs that the LOS 22.1 code will ever be stable and I won’t make Iodé builds with unstable code. If you need Iodé 6, then you should buy a different device.
None of my unofficial Iodé builds get OTA updates: it’s on the wishlist but no ETA yet and it may not ever happen. If you need OTA updates get a device that is officially supported by IodéOS.
3 Likes
Didnt want to complain, I am really greatful!
I am used to not having OTA upgrades on most of my devices, no problem!
1 Like
I just updated to Iode 5.13. I had some issues, but I could solve it.
- I backuped my apps with android_backup_project and sideloaded Iode 5.13 with wipe cache / Dalvik cache as usually
- When I rebooted the phone, my EFS was corrupted. SIM was not detected and Settings → About Phone → IMEI did not show my IMEI anymore
- I first tried to restore the corrupted EFS with the adb method from here, however this did not work even with root debugging activated and adb in root mode (the command was running successful, but the IMEI still did not show up after reboot)
- I then tried fixing EFS with the TWRP method as described here and that has worked for me before.
- EFS was fixed then, the SIM card was detected again. However, IMS features (VoLTE / VoWIFI) did not work even though in Settings → Xperia Parts the right modem seemed to be used for my provider
- I could fix this by Settings → Xperia Parts → deactivate IMS Features → restart → Settings → Xperia Parts → activate IMS Features → restart
I am now in Iode 5.13. with latest security patch from May 2025 and VoLTE / VoWIFI is working again. Thank you @petefoth for the build.
@MaxO
I also understood that Android 15 / IodeOS 6 is very unlikely to be ported for our device as the available ports are very buggy. However, I am fine with the device now with Android 14, there are regular security updates thanks to the builds from @petefoth (you need to install them manually with adb sideload), unless of the corrupted EFS problem occuring occasionally (where I know the workaround to fix it again now) the ROM is super stable, and it is expected that Android 14 will be supported until March 2027 with security patches, so I am happy at the moment.
2 Likes
Interesting, is the build for the “compact” version of XZ1, XZ2 that much different then the “non-compact” one?
Anyway, I am grateful for every build for these devices that came out, thanks a lot!
The compact devices use a lot of the same code as the full size versions built on the same : e.g. this repo for common device tree code and this repo for common vendor blobs for XZ2 and XZ2C (and also XZ3 I think), all built on the Sony tama hardware platform. But each device also has separate, device-specific repos e.g
- device tree code and vendor binary blobs for XZ2
akari, - device tree code and vendor binary blobs for XZ2 Compact
xz2c.
Similar story for devices built on the Sony yoshino platform: XZ1 poplar and poplar_dsds, XZ1 Compact lilac, and XZ Premium maple and maple_dsds.
You can see the actual differences in the code by e.g cloning both the device tree code repos, and diffing them. Probably not worth bothering doing hat for the vendor binary blobs repos - diff will just report a lot of binary file differs.
I am quite interested in the answer to your question, but I won’t get round to doing diffs until I have a free day with nothing better to do (i.e. all the LineageOS for microG issues are fixed, the weather is too bad for the golf course to be open or to go out for a run , and I have finished reading all the books in the pile beside my bed. Don’t hold your breath! 
)
I wish you all the weather you like and to keep your priorities clear.
In the end we all have a life to live!
2 Likes
Ok I still frequently run into the corrupted EFS partition issue. I have no idea what actually is causing it. However, it can be fixed using the method from here: How to Fix Empty IMEI, Corrupted EFS, No SIM, Unknown Baseband and WiFi/Bluetooth issues after restoring a TWRP Backup
While that works reliably it is quite cumbersome to type in the erase commands in the tiny little terminal window. Therfore I have just written the commands in a little script saved on the sdcard, so that in the future I just need to run the script.
Here is how this can be done:
in the terminal window type:
echo '#!/system/bin/sh' > /sdcard/imeifix.sh
echo 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1' >> /sdcard/imeifix.sh
echo 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2' >> /sdcard/imeifix.sh
chmod +x /sdcard/imeifix.sh
now you can always run the script from the terminal:
/sdcard/imeifix.sh
Hope this helps others with the same problem.
4 Likes
Hi IamJoosy.
I had it only three times so far in 10 month usage of my XZ1C with IodeOS. One time was after dirty flash upgrade of the IodeOS rom and the other times apparently “random” after booting the phone in the morning.
Thank you for your instructions with the terminal script. How do you run it? Via TWRP Recovery and the Terminal in TWRP? I did not manage to fix EFS via adb shell, but with TWRP it worked every time so far.
I had it two times in two days, that’s why I came up with the script.
Yes, I run it in the TWRP Terminal. The upside of this is, that even on the go I can fix my phone - I just need to remember the script name ;-). And since the script is stored on the SD card, it is even save when things break after a rom upgrade.
Thanks for the script but like @rom4nb I don’t know how to run it. But I wrote it on a notebook that I have with me 
.
I had this problem again this morning. I made two updates on may 25th and then on may 26th, so maybe that’s why. I don’t know…
Thanks again