eSIM related changes for 1IV are in the pipeline and will probably land soon. Right now I am planning to avoid vendor reflashing, we can probably apply same changes via overlay. overlays are rather well implemented in this port and makes sense to use it.
3 Likes
Noticed a missing AAS-related config in 10 V droid-configs. It didnāt help, but Iāll check if maybe there are more differences from 1 IV tonight.
1 Like
Can you please ask him if his device is also physical dual-sim, i.e. XQ-CQ72 or so? If so, it would mean that it only works on those.
I have Xperia 5 IV XQ-CQ54 with 1 physical SIM card and eSIM. It runs SailfishOS 5.0.0.76. I use physical SIM card and it is working in SailfishOS and AAS.
Also Iāve tried to use internal eSIM. LPAC/SimPro sees eSIM reader, but unfortunately it didnāt manage to download eSIM profile from my carrier operator.
3 Likes
That is what happend to me with Prixtel, after testing other esim providers..
You can run from commandline the lpac command to see the error, like
LPAC_APDU_GBINDER_UIM_SLOT=2 LPAC_APDU=gbinder lpac profile download
(see -h I donāt remember the exact parameters, I just have this command noted).
You can help warn others by updating the eSIM support wiki with your carrier..
(What I ended up doing because it was my main number, was to flash lineage back 
and sideload MindTheGapps so I can add the eSiM 
)
1 Like
hmm, I wonder where is in reaction to the message? only heart or maybe it warrants flagging it? 
I hear you Yes, there are multiple hurdles to get eSIM working, hw, providers, etc and this is not ideal.
(on the up side, I just registered a Lycamobile esim without issues today. So for me it worked 75% of the time 
)
Then Iām really out of ideas. I have the same LOS image as others with the 1 IV, same .71 testing SFOS image upgraded to .76, same AAS, etc., yet it just doesnāt work. AAS doesnāt see IMEI and SIM card, all that info is greyed out in Android settings. And, apparently, the same applies to @bundyoās 1 IV.
Forgive me if Iāve overlooked this info, but can the AAS packages from a licensed 10ii work?
I want to notice that - the mobile internet didnāt work in AAS with the first LOS image for xperia 5 IV. It started working in the next one
Yeah, but for the 1 IV that patched LOS image hasnāt been released yet, thereās only the original one from November 2025. Yet it still works for some 1 IV owners. Quite possibly, itās only those who manually patched and reflashed LOSā vendor.img, applying to it the same changes as what the updated 5 IV LOS image provides.
Iāve just broke SFOS on my 1 IV 
by directly editing manifest.xmlin /vendor/etc/vinft
I would suggest to have some patience . I am looking into enabling 2 SIM cards (with eSIM) using overlays and new configs. But, right now I get forever spinner on boot that is related to ofono and some others interaction. Looking into it as we would like to roll out eSIM support in a way that it will not block a phone when you install it.
7 Likes
BTW, I hope that we will not need to reflash vendor.img when it will be ready. But that would need some testing
2 Likes
I know I did a stupid thing, I already knew it when doing it I should have done it via overlays, and I really donāt know what stopped me. Laziness maybe
Now the question is: is it fixable? I can get to fastbootd without problems, adb works OK, I already reflashed vendor.img, I can mount /data and see the whole SFOS filesystem in /data/.stowaways/sailfishos/, I could see that modified file in /vendor and I replaced it with the one I backed up prior to modifying it, I checked its permissions and ownership and it looked OK (root/root, rw-rārā), I reflashed a couple of other LOS partitions just to make sure, yet SFOS still doesnāt boot - it stops and the bootlogo without lighting up the white led, then the screen gets black and thatās it.
When I originally modified that manifest.xml file on a live running SFOS, I did it in what in SFOS is seen as /vendor/etc/vintf/. But what partition is that, what image does that file originally come from? Is there a way to restore it to get back to a booting/working SFOS? Nothing else was modified but that file. Putting that original file into /overlays/etc/vintf/ doesnāt help, eitherā¦.
Wellā¦ā¦. installed LOS and SFOS from scratch. Flashed vendor.img with patched manifest.xml file - the one that works for others. Updated SFOS to .76, installed AAS, and the damn thing still doesnāt see mobile data (and SIM card in general). I give up.
1 Like
maybe the difference between 10mk3 and 10mk4/5 AAS is the culprit?
btw, I mightāve missed. Does current 1mk4 kernel include those kernel options that @vlagged included for 5mk4?
1 Like
Yes, rinigus added them.
2 Likes
I repatched that manifest.xml file again as I discovered that an eSIM entry was left in it. Repacked vendor.img using afsr, reflashed just vendor (which, to my surprise, made SFOS die upon boot again), so tested everything in LOS (SIM, mobile data etc. worked OK with that re-patched vendor) reinstalled SFOS (which then worked OK with that new vendor img), upgraded to .76 (which also applied new kernel with the required config options), installed AAS andā¦ f#*&! this thing just doesnāt want to see the SIM. Maybe there is still something else to change in that manifest to make it work on eSIM modelsā¦ Iām really out of ideas. Somehow I donāt believe that AAS version itself has something to do with itā¦
Have you managed to check the video recording volume in LOS?