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.
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.
Is there anything closed source in the Volte patch?
Yes, as has been stated before.
And i think calling it a patch is quite belittling for such a great effort.
I don’t care much about the voice over bit, just the LTE
What do you mean with that? This is just about the voice part.
As a software developer; patch generally means small.
Moving on…
LTE is very much supported, just not for calling (voice over…).
Previously voice calls would fall back to either 2G or 3G, and if you bought a plan where you are promised voice, the operator may not let a non VoLTE-capable device on a LTE-only network as to not give false pretenses.
Sailfish refusing to tell me what kind of data connection I’m using.
It’s right there in the status bar.
Note that none of this applies to any device other than the Xperia 10 II. The 10 III file structure is very different
So what is the analogous process / file structure on the 10 III?
Is there some way to go find the config ID on android, or from the MCC+MNC numbers?
The 10 III does the stuff we’ve been talking about here automatically in the modem, so those modem.conf files aren’t used (and their paths are actually incorrect on that device). I’m not even sure if that config id is used at all.
FYI all, VoLTE calling, SMS, MMS and Data working on T-Mobile USA and US Mobile using a Xperia 10 ii. Probably would work for Mint as well. See mbn conf details here: VoLTE provider support - #110 by hackman238
Hi! I’m having hard time to get my Xperia 10 II to register 4G calls (the toggle is just blinking, I’ll now leave it there trying for the rest of the day…).
I’m using a Telia SIM in Finland.
getprop persist.vendor.somc.cust.modem0
S255.1
a config file seems to be in place in:
/vendor/firmware_mnt/image/modem_pr/mcfg/configs/S255.1/
I double checked with operator that 4G calls are enabled for my phone subscription. SIM card is also new enough (from 2017 or 2018, I can check later).
Has it worked robust for everyone else who’s using Telia in Finland?
I also haven’t figured out Telia EE yet, maybe they’re using the same configuration, except we don’t know which one works.
I’ve tried emt/est
, telia/lv
, generic
but nothing has worked thus far.
There be easier ways to find/extract/construct newer configs, but those could never be merged.
Sony Xperia 10 II & T-Mobile in US
[root@sonyxperia defaultuser]# getprop persist.vendor.somc.cust.modem0
S264.8
Looking here: https://github.com/MarijnS95/SonyOpenTelephony/blob/master/ModemConfig/res/xml/service_provider_sim_configs.xml
Line 804:
I presume that is the config file that I need to map to.
How do I create / extract /construct, the config file for T-Mobile US ?
Thanx
You can use https://github.com/JohnBel/EfsTools to create Qualcomm modem config binaries. I don’t know if there will be signature or attestation issues though. For T-Mobile US the following works for now: VoLTE provider support - #110 by hackman238
I meant VoLTE and corrected it in my post.
I am not sure if I understood the instructions for enabling VoLTE on X10II (single sim) correctly. The first step I did was pasting the following command to the console:
dbus-send --system --print-reply --type=method_call --dest=org.ofono /ril_0 org.ofono.IpMultimediaSystem.SetProperty string:Registration variant:string:auto
which gave me the following output:
Error org.freedesktop.DBus.Error.UnknownMethod: Method "SetProperty" with signature "sv" on interface "org.ofono.IpMultimediaSystem" doesn't exist
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.