VoLTE on the Xperia 10 II - filling in the gaps

thigg · 15 July 2022 16:07

It looks like a conf for S77.2 already exists, thus this is another issue entirely? How can we help with that? Did someone already contact O2 (Germany only?)?

abranson · 15 July 2022 16:21

Which modem config path does it point to? Is it correct?

Mohjive · 15 July 2022 17:04

I have virtual operator Fello (https://www.fello.se), which uses Telia’s network, but I get no id. How can I solve this?

In secondary slot I have Telenor SE (S58.1), but haven’t had any luck in register to VoLTE there.

Both operators support VoLTE according to their information.

Edit: and looking at operator support (VoLTE provider support) Fello is supported on the Xperia 10 III, so there has to be something I can do to fix this

jetset · 15 July 2022 17:09

Thanks, li fixed it he typo

thigg · 15 July 2022 17:31

It links to …/de/… But only …/cz/… available. (is there a nice way to copy something from the terminal?)

flypig · 15 July 2022 23:05

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.

abranson · 16 July 2022 06:25

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?

Mohjive · 16 July 2022 07:29

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.

abranson · 16 July 2022 07:56

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.

Mohjive · 16 July 2022 12:59

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.

thigg · 16 July 2022 15:46

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

Mohjive · 16 July 2022 17:12

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:

Both screenshots above are with Fello in primary and Telenor in secondary slot.

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.

tw1 · 17 July 2022 09:26

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.

Mohjive · 17 July 2022 12:47

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)?

tw1 · 17 July 2022 14:54

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:

github.com

sonyxperiadev/SonyOpenTelephony/blob/master/ModemConfig/convert_from_stock.py

#! /usr/bin/env python3

import sys
import os
import os.path
import argparse
from pathlib import Path


from androguard.core.bytecodes.apk import APK
from androguard.core.bytecodes.axml import AXMLPrinter, AXMLParser, END_DOCUMENT


parser = argparse.ArgumentParser(
    description="Extract operator mappings to modem firmware from stock OEM overlays"
)
parser.add_argument("oem_dir", type=Path, help="oem root dir containing the overlay")
parser.add_argument(
    "mcfg_dir",
    nargs="?",

This file has been truncated. show original

abranson · 17 July 2022 15:11

Looks like Halebop already has one in some later version:

github.com

Alcatraz323/android_device_sony_yoshino-common/blob/be57f7555f86cc204b3e1aa752a68a88e253e6c5/overlay/device/sony/yoshino-common/hardware/OpenCustomizationSelector/res/xml/service_providers.xml#L310

    
      
              <sp>Telia</sp>
          </service_provider_sim_config>
          <service_provider_sim_config sim_config_id="S55.3">
              <mcc>240</mcc>
              <mnc>07</mnc>
              <imsi>^24007\s?(([0-5]|[7-9])|600).*</imsi>
          </service_provider_sim_config>
          <service_provider_sim_config sim_config_id="S57.1">
              <mcc>240</mcc>
              <mnc>01</mnc>
              <sp>halebop</sp>
          </service_provider_sim_config>
          <service_provider_sim_config sim_config_id="S58.1">
              <mcc>240</mcc>
              <mnc>08</mnc>
          </service_provider_sim_config>
          <service_provider_sim_config sim_config_id="S59.1">
              <mcc>240</mcc>
              <mnc>02</mnc>
          </service_provider_sim_config>
          <service_provider_sim_config sim_config_id="S59.2">

tw1 · 17 July 2022 15:28

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.

plemil · 17 July 2022 16:04

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.

Mohjive · 17 July 2022 16:20

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.

abranson · 17 July 2022 17:49

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.