I tested with Three UK. For anyone else using or thinking about going with Three, on the Xperia 10 III it worked immediately, but on the 10 II it required a modem.conf mapping:
devel-su
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
After doing this, calls and SMS messages work nicely on 4G.
Ok, this is a lot harder. There’s a big XML file mapping all of the MCC and MNC ids to those config IDs that you can find in /usr/share/sony-modem-switcher/service_provider_sim_configs.xml. I’m not entirely sure where you get those two values from, but I think they can be coaxed out of ofono somehow. Then I reckon mcfg_sw/generic/euro/telia/vlvw/swe/mcfg_sw.mbn might be what you need. Telenor already seems to be configured correctly, but I guess you could try it in the other slot?
Ok, I used to have access to a modem with AT-interface, where I could find out those numbers, but unfortunately I don’t have that currently. But at least I now know what I’m looking for. When I found them out, how do I know what “S”-number to map it to?
And I’ll try to swap the Telenor SIM to another slot to see if that works better.
Yeah the S id is a pain. I think I found some other similar files on Github. Might have some extra entries, especially in more recent versions.
Edit: if you do dbus-send --system --print-reply --type=method_call --dest=org.ofono /ril_0 org.nemomobile.ofono.SimInfo.GetSubscriberIdentity then the MCC should be the first three digits, and the MNC (MCRN??) the second two. I think.
Yes, seems correct, but looking at the numbers the Fello use are Telia’s (“240 01”), so it should work out of the box.
[root@Xperia10II-DualSIM defaultuser]# dbus-send --system --print-reply --type=method_call --dest=org.ofono /ril_0 org.nemomobile.ofono.SimInfo.GetSubscriberIdentity
method return time=1657973867.099315 sender=:1.12 -> destination=:1.610 serial=4713 reply_serial=2
string "24001XXXXXXXXXX"
[root@Xperia10II-DualSIM defaultuser]# dbus-send --system --print-reply --type=method_call --dest=org.ofono /ril_1 org.nemomobile.ofono.SimInfo.GetSubscriberIdentity
method return time=1657973893.461479 sender=:1.12 -> destination=:1.611 serial=4717 reply_serial=2
string "24008YYYYYYYYYY"
Wonder why I don’t get an S number for my Fello SIM.
okay, I don’t know what I found earlier, but the diagnose, that there is only configuration for tef_o2/cz seemed to be wrong.
All files are apparently there, but it is still not working yet:
$ ls /vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/euro/tef_o2/vlvw/de/
mcfg_sw.mbn -lah
-r--r----- 1 system system 45.0K Mar 30 2021 /vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/euro/tef_o2/vlvw/de/mcfg_sw.mbn
$ cat /vendor/oem/modem-config/S77.2/modem.conf
mcfg_sw/generic/euro/tef_o2/vlvw/de/mcfg_sw.mbn
Edit: Netmon shows its working now… (after a reboot, including hard reset with power+vol up). Doesnt work when i call my mailbox however
I have done some more testing.
After switching cards (primary/secondary) both SIMs (Fello&Telenor) works with VoLTE, as long it’s the card selected to be used for mobile internet connection. I guess it’s due only one modem is able to connect to LTE at the same time?
When primary SIM is used for internet:
When secondary SIM is used for internet:
The strange thing is that my Fello SIM gets (retains?) the same S-number as the Telenor SIM, but VoLTE works anyway. This behavior remains no matter which slot each SIM is in.
I have Fello Sweden and same problem as Mohjive (but with only 1 SIM card).
I think the sp line in the switcher config is a filter that only matches Telia.
And indeed after removing the line and rebooting, VoLTE registers and works for me.
--- service_provider_sim_configs.xml.ORIG
+++ service_provider_sim_configs.xml
@@ -297,7 +297,6 @@
<service_provider_sim_config sim_config_id="S54.1">
<mcc>240</mcc>
<mnc>01</mnc>
- <sp>Telia</sp>
</service_provider_sim_config>
<service_provider_sim_config sim_config_id="S55.3">
<mcc>240</mcc>
edit: this will collide with the halebop config, which also shares the same mmc and mnc. The correct fix would be to allocate a new S-number and create a new config for Fello.
Good info. Though should there be new S-numbers allocated or should Telia, Halebop and Fello use the same ( and Tre and Hallon, Tele2 and Comviq, Telenor and Vimla etc)?
I don’t think everything in Sweden can be merged, I found four different modem configs in “swe” directories, and their checksums are different (hutch is probably Tre):
43be0f8b354d35a034403d034d1797e7 /vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/euro/hutch/vlvw/swe/mcfg_sw.mbn
a7228cdfb669c71341971b9a8032cf95 /vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/euro/tele2/vlvw/swe/mcfg_sw.mbn
4fff8c8393b75734e5f1bec6c3a3997a /vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/euro/telenor/vlvw/swe/mcfg_sw.mbn
aba38f3ea22de0d299fba6006a69f24b /vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/euro/telia/vlvw/swe/mcfg_sw.mbn
But unless this file is used for other things, there can probably be some consolidation.
I think the file has been generated by this script, from the original firmware:
Looks like Halebop already has one in some later version:
Telia and halebop is already in the Sailfish file with mcc 240 and mnc 01. But we need something defined for Fello, which also shares mcc 240 and mnc 01.
Following the guide from @cypherpunks with the “hutch” hint from @tw1
I manage to get my Hallon SIM (uses Tre network) to get registered after a reboot.
getprop persist.vendor.somc.cust.modem0
Gives ID S9105.1
No current config for this ID exist.
But modem file for hutch exists, so followed @cypherpunks from here.
Don’t know where you able to get your screenshots but at least 4G calling states registered in the Mobile network.
That’s not what I was trying to say, but to merge the virtual operators with their “real” operators, i.e use same config for Telia, Halebop and Fello and another config for Tele2 and Comviq, a third for Telenor and Vimla etc.
But at the same time the Telenor config worked for Fello, so I guess it can probably be unified. 
Maybe it’s best to ask the Sony guys about this somehow, as I’m sure those numbers have to come from them somewhere. Iirc they’re based in Sweden, so they might be encouraged to sort out their local operators.
Yes, if Sony upstream does not come trough the easiest solution might be to merge the Telia, halebop and Fello ones, since they all end up in the same place.
Since VoLTE is a standard, I guess it is not that strange that the Telenor binary worked with Telia. Maybe Xperia 10 III have unified them, and that is why they did not have this problem.
My telco operator is “Telecom Slovenija” and it offers both VoLTE and VoWIFI. I followed instruction to swith VoLTE on for my account (sorry only in Slovenian language: volte-vowifi).
My daily driver phone is Sony Xperia 10 II. SFOS 4.4.0.68.
Command getprop persist.vendor.somc.cust.modem0returns “S202.1”.
Ofc, there is no entry for any telco operator in Slovenia in “/vendor/firmware_mnt/image/modem_pr/mcfg/configs/”. All files in here are about 1 year old.
Is there a method to update it with latest version? I hope such update might bring entries for telco operators on Slovenia.
These configs are part of the base firmware of the device, and as far as I know officially you’d have to use Sony’s Emma tool to reflash it with a more recent version of Android than when you installed SailfishOS originally to get newer ones.
There be easier ways to find/extract/construct newer configs, but those could never be merged.
Wouldn’t it be an option to extract further configs from more recent Sony firmwares and just copy them to SfOS?
Of course it’s possible. Whether it’s probable is another matter. Is there anything closed source in the Volte patch?
Edit: Was confused about LTE vs VoLTE. Deleting posts as it was a bit off-topic to begin with.