I have a 10ii, and had to create the directory. In your case the command would be:
mkdir /vendor/oem/modem-config/S173.1
Tried to create: /vendor/oem/modem-config/S461.1/modem.conf
And put inside these lines, one by one and then reboot, then next one… (the third and fourth are based in what I see in other modem.conf files, trying to guess):
mcfg_sw/generic/EU/Telefonica/Commercial/Spain/mcfg_sw.mbn
mcfg_sw/generic/EU/Telefonica/NONIMS/Spain/mcfg_sw.mbn
mcfg_sw/generic/euro/telefonica/commercial/esp/mcfg_sw.mbn
mcfg_sw/generic/euro/telefonica/non_ims/esp/mcfg_sw.mbn
No sucess, and no useful info got with: journalctl -t ofonod -f
Trying on a 10iii, operator Nowo (Portugal). The operator says on their website that VoLTE is activated for all hardware that supports it.
in /vendor/firmware_mnt/image/modem_pr/mcfg/configs I don’t see anything that matches Nowo or MEO (according to Wikipedia, Nowo operates VoLTE through a commercial agreement with MEO).
getprop persist.vendor.somc.cust.modem0
S73.1
cd /vendor/oem/modem-config/
mkdir S73.1
cp S9999.9/modem.conf S73.1/
Does not register (after reboot); here are the logs when I try to activate VoLTE in the configuration:
journalctl -t ofonod -f
imsradio0 < 7 requestRegistrationChange
vendor.q ti.hardware.radi o.ims@1.0::IImsR adio....
imsradio0 > 4 requestRegistrationChangeResponse
vendor.q ti.hardware.radi o.ims@1.0::IImsR adioResponse.... ........
imsradio0 > 27 vopsChanged
vendor.q ti.hardware.radi o.ims@1.2::IImsR adioIndication.. ....
Edit: the table above says MEO works but does not register. @flypig, what modem.conf file should I use assuming MEO? I can’t see any relevant in the list, and S999.9 does not work (during a call, it switches from 4G to 2.5G).
On my 10III I have an issue with VoLTE. When VoLTE is activated I can not send sms, mms is ok. I have Telmore using TDC net.
On my 10V VoLTE there is no issues. BUT, I have tested it using a TDC SIM card that is on the TDC net.
I have just switched the sims and it gave the same result.
It means, TDC net have the one issue on 10III whereas it works on 10V.
Swapping the cards around would probably be an interesting data point… why haven’t you?
I got an SMS yesterday from Vodafone Australia: “From October 2024 new regulations will require devices not compatible with emergency calling on 4G networks to be blocked from using voice, SMS and data services. This applies across all mobile providers in Australia… We are now confirming that your device will be blocked on our network from 28th October 2024”
Until now my phone has been able to make 4G calls. Is there any way to add 4G emergency calling to a 10-ii running Sailfish OS?
1 Like
This is sad indeed. Does anyone have any newer Xperia 10 that they think will keep working in Australia after the shutdown?
@maynard In terms of your question - Jolla responded to a question about this at the 8th August community meeting:
07:06:24 rainemak #info We are testing with Finnish emergency call centre (hätäkeskus). On next round, we are focusing our testing to the Jolla C2 Community Phone. We answer to the forum as well.
I haven’t seen any public discussion about this since. Also, considering the C2 currently has no working VoLTE at all, I dare say it is not just around the corner for other models. Perhaps @rainemak can provide an update here?
They already write about that. In RC zero indeed there is no support but it’ll come with the next update.
@juz @filip.k Thank you for responding. After further investigation, it appears that Vodafone Australia would be blocking my Xperia 10-ii on 1 November even if it did in fact support 4G emergency calling, since the decision to block phones will be based on the IMEI, and that model is not on their list of approved devices.
@
I was the one who asked this question (or on the topic in general
We have our answer (via the aus govt)
The xperia 10 III like the 10II is also going to be blocked in Aus (i got that notification today) on the basis it does not support emergency calling on VoLTE/the E000 standard
@Jolla employees - given this i think an update is required to the support table at the start of this thread - since its more than just “not supported” Xperia 10 II/III devices trying to use local sim cards will be blocked from all access to the mobile networks including data over 4g/5g - I think its also safe to say that it would not be a good idea to supply C2s/ship C2s to Australia since there is a fairly high chance they will end up network blocked
I am not sure about the other phones officially supported by sailfish, but i think we need to work off a model of until we get absolute confirmation we need to view them as unsupported
This is a quote i got from an email from my provider today
"
Device - Sony XQ-BT52
Your mobile device will not have access to the Telstra network from 28 October 2024. Telstra is required by law not to supply services to mobile phones that cannot make calls to emergency services (including calls to triple zero). To comply with this requirement, Telstra will be blocking impacted mobile phones from accessing its network on 28 October 2024. Once a mobile phone is blocked, the handset will not be able to be used for voice or data and will not be able to make calls to emergency services (including to triple zero). In order for the service to continue to be used, the SIM must be removed and put into a compatible device. If your device is impacted, low cost mobile phone options are available."
Blockquote
Update
According to posts on the whirlpool forums Xperia 10V (https://whrl.pl/RgLiTA ) is going to be blocked as well, im looking for final confirmation for 10 IV (the emails are going out today mine arrived 1.5hrs ago)
What i think this will mean too is for any Jolla users with an Xperia family device, if they are tourists in aus, even if roaming with their international sim card they will be unable to call the emergency services while in the country since these blocks are being applied because the Xperia’s are using 3G to try to make emergency calls - This is perhaps something that needs to be warned about in the support table at the start of this thread - (this will also logically apply to anywhere else that has no 2G/3G service anymore)
It also on the face of it will mean no Australian’s will be able to use Sailfish as their supported by Jolla daily driver since no phones currently supported by sailfish appear to meet the VoLTE emergency calling requirements
4 Likes
In a last attempt to avoid changing network providers, could anyone provide information on getting the Xperia 10IV mcfg_sw.mbn files for Telstra (that I have a copy of), onto my Xperia 10V?
Can a flash them to somewhere?
Do I need to update more files?
Thanks very much,
Just an educated guess but you can copy or modify files in command line.
But OTOH I didn’t any such files in the root of C2 (don’t know if they should already be there or not in 5.0.0.21):
[defaultuser@JollaC2 ~]$ devel-su find "/" -type f -name "*.mbn"
[defaultuser@JollaC2 ~]$ devel-su find "/" -type f -name "*cfg_sw*"
EDIT: Added phone model C2 remark just in case!
Have a look at this thread over at Pine64, it may help point you in the right direction.
https://forum.pine64.org/showthread.php?tid=12560
I used it awhile ago to get my PPP working.
Thanks for the input. I can see the files, but I cannot modify or add to the filesystem.
These files are stored /vendor/firmwar_mnt/image/ but that file system is read only.
I think possibly the only way to change it is to reflash the modem image from Sony.
This seems possible. I can locate the modem_X-FLASH-ALL*.sin file in the sony flashing files I can convert that to an image, and that indeed has the information I want. I can add the additonal modem configs for Telstra, Vodafone and Optus.
But then I am stuck. There is no way that I can see to turn the modem image file back into the .sin file for flashing (signed by sony).
Is there a way to flash the .img file with fastboot? rather than having to turn the .img back to .sin?
Any input would be great.
In regards to the pinephone, I had a look, but feel the modem is probably to far away from the sony’s to be useful.
Thanks though.
You can check install script from official image for some inspiration.
Hi, I try to understand your investigations to active VoLTE on a XPERIA 10 II on Free Mobile, but I certainely missed a crucial step…
Can you synthesis all your process ? Thanks a lot !
I’ve basically followed what @abranson described in this thread for the 10 ii model.
As far as I remember the steps, they were:
-
devel-suto gain root privileges, -
cd /vendor/oem/modem-config/to change directory, -
mkdir S8683.1to create the missing directory for Free service, -
cd S8683.1to change directory, -
echo "mcfg_sw/generic/common/default/vl/global/mcfg_sw.mbn" > modem.confto indicate to the IMS to use the generic configuration, which seems to somehow work with Free mobile (I’ve the 2 € plan and I’ve checked in my account that 4G calling option is activated). - reboot the device and then check the VoLTE calling option in the phone settings.
5 Likes
When I started using it, sending SMS was broken and required to unsuscribe VoLTE to send the SMS and subscribe back after. I tried to change parameters by unpacking the mbn file change some random options and repack it, without success. Surprisingly enough, it started to work by itself after a month. I guess Free changed something on their side.
MMS are working also, as far as I remember (I don’t send or receive MMS very often).
About the calling status, my impression is mitigated. When on VoLTE, it’s perfect. But for reasons I still don’t understand, the phone tries sometimes to fallback to 3G, while the 3G signal is poor and the 4G one is strong. And the call quality becomes thus really bad. This happens quite often (sadly) when receiving a call. But not always…
not an expert, but i think this happens to android/iOS users pretty frequently, too. the caller happens to be on 3g, so you have to fallback to 3g to answer it.
1 Like