You did not. There are only two steps to enable VOLTE on 10II.
Should there is working config for your carrier it will work if not follow:
VoLTE on the Xperia 10 II - filling in the gaps
Missed the 4.4.0.64 to 4.4.0.68 update, that explains it. Thanks.
With my Xperia 10 II I can register VoLTE and use phone calls / incoming calls successfully. But sending SMS is not working anymore.
I’m using a SIM card from 1und1 with the provider D2 Vodafone DE.
I have successfully registered in Polkomtel operator (Plus GSM) - Poland. However I had to manually create modem.conf.
After that both voice and sms are working without problems while being connected to LTE network.
how does that apply to 4G/VoLTE when roaming?
I have a X10ii and live in France with Orange as provider - VoLTE works fine at home.
I’m currently in the US, therefore roaming - T-Mobile is the provider I am on.
When doing steps 1 and 2, I see that my provider is still Orange, as I’m getting S11.3 and the modem.conf file contains:
mcfg_sw/generic/euro/orange/vlvw/fr/mcfg_sw.mbn
I tried using the workaround suggested here but unsurprisingly, since the value for me is S11.3 and it already exists, that did nothing.
So I’m not quite sure if I’m supposed to do something? Or is roaming just not taken into account at the moment?
Oops, I accidentally posted in the wrong thread. moving my issue here:
So, I tried to enable VoLTE with Salt (Switzerland), but it just won’t work. The config looks fine:
[root@Xperia10II-DualSIM defaultuser]# getprop persist.vendor.somc.cust.modem0
S32.1
The modem config is in /vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/euro/salt/vw/ch/ and is correctly set:
[root@Xperia10II-DualSIM defaultuser]# cat /vendor/oem/modem-config/S32.1/modem.conf
mcfg_sw/generic/euro/salt/vw/ch/mcfg_sw.mbn
However, enabling VoLTE in the ‘mobile network’ settings just results in the dot blinking indefinitely, staying at status ‘Not registered’.
journalctl logs the following messages when I enable the setting:
Jul 24 08:36:43 Xperia10II-DualSIM ofonod[2755]: imsradio0 < 7 requestRegistrationChange
Jul 24 08:36:43 Xperia10II-DualSIM ofonod[2755]: 0000: 76 65 6e 64 6f 72 2e 71 74 69 2e 68 61 72 64 77 vendor.q ti.hardw
Jul 24 08:36:43 Xperia10II-DualSIM ofonod[2755]: 0010: 61 72 65 2e 72 61 64 69 6f 2e 69 6d 73 40 31 2e are.radi o.ims@1.
Jul 24 08:36:43 Xperia10II-DualSIM ofonod[2755]: 0020: 30 3a 3a 49 49 6d 73 52 61 64 69 6f 00 00 00 00 0::IImsR adio....
Jul 24 08:36:43 Xperia10II-DualSIM ofonod[2755]: 0030: 0a 00 00 00 00 00 00 00 ........
Jul 24 08:36:43 Xperia10II-DualSIM ofonod[2755]: imsradio0 > 4 requestRegistrationChangeResponse
Jul 24 08:36:43 Xperia10II-DualSIM ofonod[2755]: 0000: 76 65 6e 64 6f 72 2e 71 74 69 2e 68 61 72 64 77 vendor.q ti.hardw
Jul 24 08:36:43 Xperia10II-DualSIM ofonod[2755]: 0010: 61 72 65 2e 72 61 64 69 6f 2e 69 6d 73 40 31 2e are.radi o.ims@1.
Jul 24 08:36:43 Xperia10II-DualSIM ofonod[2755]: 0020: 30 3a 3a 49 49 6d 73 52 61 64 69 6f 52 65 73 70 0::IImsR adioResp
Jul 24 08:36:43 Xperia10II-DualSIM ofonod[2755]: 0030: 6f 6e 73 65 00 00 00 00 0a 00 00 00 00 00 00 00 onse.... ........
Those do not look pretty helpful to me. Is there any log where I can find more information about what’s going on?
It doesn’t look like there’s much else you can do on the SailfishOS side. Maybe contact Salt, or just leave it for a couple of days to see if it suddenly starts working.
Thank you so much for your experience, I am using 10 III and the paths for Polkomtel are slightly different.
devel-su
mkdir -p /vendor/oem/modem-config/S185.1
echo -n "/vendor/firmware_mnt/image/modem_pr/mcfg/configs/mcfg_sw/generic/EU/Polkomtel/VLVW/Poland/mcfg_sw.mbn" >> /vendor/oem/modem-config/S185.1/modem.conf
The weird thing is even after creating that and rebooting, I still can’t enable it. Any further steps I should do? I will wait and hope it will start working, I hope if X10II worked III will too, but this phone was never sold by them.
I don’t know if the same mapping can be done in case of xperia 10 III - I doubt that, but maybe someone else can shed some light on it . Nevertheless I suggest you to enable volte explicitly - if you haven’t done it already. It is done by sending SMS message ‘WlaczVoLTE’ to number 2601 (for postpaid) or by shord code *101*11*1317# (for prepaid).
Both xperia 10 II and III are not officialy volte supported phones by polkomtel according to their website. Xperia 10 II works with volte, so chances are the 10 III may also work.
No, the X10iii doesn’t look at those modem.conf files at all to my knowledge. The choice of config is automatically selected internally by the modem. So messing with those on a III won’t do anything.
Have you figured out which files are responsible for VoLTE on 10 mk II ? I would like to try to transfer files from 10II to the TAMA port for XZ 2 compact (works fine with android VoLTE) . I am grateful in advance .
I got Elisa EE working with:
mcfg_sw/generic/euro/elisa/vlvw/est/mcfg_sw.mbn
Elisa
Nice. I still haven’t gotten Telia EE to work.
This worked for me for Comviq (Sweden):
mcfg_sw/generic/euro/tele2/vlvw/swe/mcfg_sw.mbn
For completeness (since I refer to this page on the VoLTE provider support page)
This is what I did to make Telavox to work on my Xperia 10 II.
I put in my complete SIM card number since I don’t know if a particular prefix should be used but I think someone with more knowledge of these things can use this as a starting point at least.
[root@Xperia10II defaultuser]# diff -u /usr/share/sony-modem-switcher/service_provider_sim_configs.xml.org /usr/share/sony-modem-switcher
/service_provider_sim_configs.xml
--- /usr/share/sony-modem-switcher/service_provider_sim_configs.xml.org
+++ /usr/share/sony-modem-switcher/service_provider_sim_configs.xml
@@ -297,7 +297,7 @@
<service_provider_sim_config sim_config_id="S54.1">
<mcc>240</mcc>
<mnc>01</mnc>
- <sp>Telia</sp>
+ <imsi>^24001XXXXXXXXXX</imsi>
</service_provider_sim_config>
<service_provider_sim_config sim_config_id="S55.3">
<mcc>240</mcc>
[root@Xperia10II defaultuser]#@flypig The Jolla Shop still claims that Xperia 10 II does not have VoLTE beta, although it does. Shouldn’t it be updated?
You’re right, it should! Thanks for pointing it out; I’ll raise it on Monday.
This is still to be done, but I’ve not forgotten about it.