Boom! Even after explicitly saying VoLTE 10x at the store counter, ladies at the counter somehow couldn’t get me signed up with it activated - even though they said «all new SIMs have it auto-activated» etc.
After I complained to my business plan rep in email, he said «it doesn’t look like VoLTE was activated, so try now».
Victory! Elisa EE S253.1 works 
Calls are really fast to make now (even though I never call anyone, and noone calls me), this is quite nice. 
Updated to 4.5.0.16 on FEB 14.
To me getprop persist.vendor.somc.cust.modem0 gets empty answer
Provider: POSTEMOBILE in Italy.
I tested also with TIM in Italy: it shows up in S132.1. The folder S132.1 is present in “modem-config” VOLTE is not working yet.
Tested today with VODAFONE in Italy: it says S135.1. There is no folder S135.1 in “modem-config”.
I created S135.1 folder and modem.conf file.
I tried different mcfg_sw.mbn files to point at, but not worked yet.
Hi, could you update to 4.5.0.19, please?
Hi! I updated to 4.5.0.19 but same results.
I also found the correct mcfg_sw.mbn file in /vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/euro/vodafone/vl/it/
and wrote in the modem.conf the line “mcfg_sw/generic/euro/vodafone/vl/it/mcfg_sw.mbn”
Not working yet
A few people have reported not getting mobile data either on Vodaphone IT. Is that the case for you? It sounds like something’s very wrong with SFOS on that network.
Thanks for the question: VODAFONE mobile data works fine, it’s the best provider (imho).
I tested also postemobile, Iliad and TIM with mobile data and everything works fine in internet connection.
I will try again postemobile and Iliad as soon as I can do it with some simcards
if my provider not in firmwares, how to I can manually add mcfg_sw.bin to sailfish? I have this mfcg_sw.bin for my provider from another site
Update: Elisa EE home network continues to work fine, but roaming in EU, no provider allowed me VoLTE in Frankfurt Airport, nor in Lissabon. In PT I tried all available: vodafone, NOS, MEOS.
Got my Xperia 10 ii set up but it’s not registering 4G Calling (Beta) on the 3UK network
I’ve attempted to follow the tutorial in the initial post of this thread.
When doing the:-
getprop persist.vendor.somc.cust.modem0
I just get $ without numbers.
Maybe I’m missing something - SIM config ID? Where do I find it?
I’ve also gone to:-
/vendor/oem/modem-config/
and found 100’s of folders but not sure which one I’m looking for.
So now I’m in stuck city.
Any ideas on moving forward?
Thanks 
All credit due to @flypig a fellow “3” user in the UK:
https://forum.sailfishos.org/t/volte-on-the-xperia-10-ii-filling-in-the-gaps/12322/15?u=aspergerguy
[root@Xperia10II modem-config]# mkdir /vendor/oem/modem-config/S21.1
[root@Xperia10II modem-config]# echo -n "mcfg_sw/generic/euro/hutch/vlvw/uk/mcfg
_sw.mbn" >> /vendor/oem/modem-config/S21.1/modem.conf
Here is result: https://i.postimg.cc/k5jBh6xY/Enabled-Vo-LTE-3.png
Thanks for digging that out of the many posts on here.
I’ll have a look see at this in due course. 
Works like a charm on my xpera 10ii. I used the global one. Nd got the VoLTR registered after rebooting. Does Xperia 10iii work out of the box? I am using them in the U.S where thr VoLTE is mandatory.
Editing my own response. So even the 4g is registered, but the call drops instantly when I pick up or call to other people. Then the signal refreshes itself from 2.5g to 4g again, I can only make calls when the 4g is not registered. I am using T-mobile
Hi all! I smashed up my screen on my (otherwise working perfectly) 10iii and wanted to use my 10ii as a backup while I wait for the new screen to show up. But despite upgrading to 4.5.0.25, S. Ketju, I still can’t get VoLTE registration and have trouble getting on the network at all. I haven’t followed the VoLTE threads since I got my 10iii working in spring of 2022 and clearly a lot has changed since then, so I’m wondering what I’m doing wrong.
So far,
I tried:
getprop persist.vendor.somc.cust.modem0
Returns nothing.
/vendor/oem/modem-config/
Does not exist.
dbus-send --system --print-reply --type=method_call --dest=org.ofono /ril_0 org.nemomobile.ofono.SimInfo.GetSubscriberIdentity
Returns:
method return time=1711070519.048808 sender=:1.9 -> destination=:1.251 serial=340 reply_serial=2 string "310260260707690"
I tried following VoLTE on the Xperia 10 II - filling in the gaps - #15 by flypig from @flypig :
mkdir -p /vendor/oem/modem-config/S21.1
echo -n "mcfg_sw/generic/euro/hutch/vlvw/uk/mcfg_sw.mbn" >> /vendor/oem/modem-config/S21.1/modem.conf
But I substituted in the files I found for TMobile USA instead. Still didn’t work.
Then I tried following VoLTE provider support - #110 by hackman238 from @hackman238 and I managed to get one text message out before it all stopped working.
I am literally sitting underneath the repeater. I can’t send or receive messages and even when the indicator on Netmon shows I have signal and am registered on the LTE network, nothing. And nothing is showing up on the MMS engine log either, other than that the bus is connected, org.ofono is owned by 1:6 and there is a modem onlinee at /ril_0.
What should I try next?
Not seeing a setting sounds like you migbt not have a license. The checkbox is definitely still there.
I purchased the OS and upgraded through the Settings/Sailfish OS updates menu. Would the license not transfer as it has always done?
These two are pretty shocking, and suggest something very wrong on that phone. Is there anything in /vendor at all? Is it even mounted? Also sounds like you’re missing at least one package if the volte switch isn’t being displayed. Did the upgrade go ok?
A while ago there were problems with the adaptation repos being lost which might cause missing volte packages. if you do ‘ssu lr’ do you see ‘adaptation0’ and ‘adaptation-common’ in the list? Does the camera work?
Good to hear you say that, @abranson, I was tearing my hair out… There could be something wrong, it’s hard to know. As far as I recall there weren’t hardware issues when I flashed it from Android 2-3 years ago (tested camera, calls, etc, pre- and post- flash)
ssu lr
returns:
- adaptation0 ... https://store-repository.jolla.com/releases/4.5.0.25/jolla-hw/adaptation-qualcomm-sony-ganges/armv7hl/
- aliendalvik ... https://store-repository.jolla.com/features/4.5.0.25/appsupport/armv7hl/
- apps ... https://releases.jolla.com/jolla-apps/4.5.0.25/armv7hl/
- customer-jolla ... https://releases.jolla.com/features/4.5.0.25/customers/jolla/armv7hl/
- hotfixes ... https://releases.jolla.com/releases/4.5.0.25/hotfixes/armv7hl/
- jolla ... https://releases.jolla.com/releases/4.5.0.25/jolla/armv7hl/
- sailfish-eas ... https://store-repository.jolla.com/features/4.5.0.25/sailfish-eas/armv7hl/
- xt9 ... https://store-repository.jolla.com/features/4.5.0.25/xt9/armv7hl/
Enabled repositories (user):
- openrepos-Karry ... https://sailfish.openrepos.net/Karry/personal/main
- openrepos-aa13q ... https://sailfish.openrepos.net/aa13q/personal/main
- openrepos-abranson ... https://sailfish.openrepos.net/abranson/personal/main
- openrepos-kan ... https://sailfish.openrepos.net/kan/personal/main
- openrepos-unmaintained ... https://sailfish.openrepos.net/unmaintained/personal/main
- store ... https://store-repository.jolla.com/i3113/armv7hl/?version=4.5.0.25
The camera shows an image on the screen when you launch the app so it looks like it’s working – but it won’t snap a photo or record a video. Pressing the toggle for the front camera appears to reverse the image feed and freezes the app.
Maybe it’s a lemon? should I try reflashing the whole thing?
(constantly refreshing the tracking status on the new 10iii screen in the meanwhile)
Oh sorry also in /vendor there is:
adreno_symlinks-timestamp firmware_mnt
bin lib
bt_firmware lib64
build.prop
default.prop qca_cld3_symlinks-timestamp
dsp rfs
etc tftp_symlinks-timestamp
firmware ueventd.rc
firmware_folders-timestamp
Omitted from this list is oem but only because I made that directory yesterday and put relevant material in it as requested, in case something was making calls to that directory and coming up short.
Well you’re definitely missing your adaptation-common repo, so you probably have a few missing or old packages on there. Remove /var/cache/ssu/repos.ini then ssu ur should recreate it with the full set. Then do zypper ref && zypper dup and hopefully a lot of packages will install. If that oem is still missing then you’ll have to reinstall the droid-system package but I’d have to look up which one that is.