[Qualcomm} VoLTE call for testing

rik

@mariogrip we are collaborating on the North America Carrier Issues telegram group, and are not certain how to determine if a call we make is indeed with VoLTE or instead 2G. @tigerpro and @Inali are there and set for testing, as am I.

If we use the list-contexts ofono script and it shows the IMS context is not active, does that mean it is not able to do VoLTE yet? Or instead, @fredldotme gave us this command to check:

gdbus call --system --dest org.ofono --object-path /ril_0 --method org.ofono.IpMultimediaSystem.GetProperties

Is this the most definitive way to tell if the phone is VoLTE capable or not?

If you could give your input on what is the best way to know if we have done all the magic to have the device capable of VoLTE it would help us know what we are dealing with. Thank you for everything along the way!

kuailexs

@mariogrip
There is no "android.hardware.radio@1.5::IRadio" library file in mi6。
The largest version is 1.4

uxes

@kuailexs 1.5 seems not to be available for miatoll with Android 10 also (only 1.4 is available),

btw which property enables 5G in the list? adding following flags showed 2G/3G/4G/5G even though device does not support it
OfonoPlugin: binder
OfonoImplementsIms: true

rik

gdbus call --system --dest org.ofono --object-path /ril_0 --method org.ofono.IpMultimediaSystem.GetProperties
Is this the most definitive way to tell if the phone is VoLTE capable or not?

We did get confirmation from @Inali that with this command their device does show "VoiceCapable": <true> so I think it is a good command to confirm if the phone is IMS registered and active. They did have issues making or receiving calls as it was starting a double call (one in 2G, one maybe with VoLTE we think?) and also SMS is broken with VoLTE enabled, but this also showed in the command. So a few steps forward at least!

kuailexs

@uxes thank you
I tried to set this option.

phablet@ubuntu-phablet:~$ gdbus call --system --dest org.ofono --object-path /ril_0 --method org.ofono.IpMultimediaSystem.GetProperties

({'Registered': <false>, 'Registration': <'auto'>, 'VoiceCapable': <false>, 'SmsCapable': <false>},)

Inali

Still testing.

-Fresh install of Fairphone 5's dev r43 build.
-Installed ofono plugin with the previously stated instructions and changed qti.conf.

Phone still shows LTE + VoLTE icons. If I call my voicemail it still shows LTE + VoLTE, so I assume no 2G calling. During my voicemail calls, I cannot register any button press such as entering my voicemail PIN. It shows the button press on my screen and makes the sound, but the call does not register input on their end, thus I could not listen to my voicemails.

Also I was unable to hangup, I had to reboot the phone. Opening the dialer app without reboot showed it immediately "calling" the last number without telling it too, but it never actually calls. Reboot is what fixes this.

"gdbus call --system --dest org.ofono --object-path /ril_0 --method org.ofono.IpMultimediaSystem.GetProperties"

shows:

({'Registered': <true>, 'Registration': <'auto'>, 'VoiceCapable': <true>, 'SmsCapable': <false>},)

Eric H

I'm working on the POCO X3 NFC (surya) port with the maintainer and I tried Marius' changes, without success.
The device is 4G only, and there is no android.hardware.radio@1.5.so (android 10).

@mariogrip
Is there a way to make VoLTE work with radioInterface = 1.4 ?

*Enrico13011978*

Interestingly, these Miatool devices also have Qualcom chipsets. However, Xiaomi and their questionable Android 10 versions wherever the difference is. Partly the telephony does not work then it is no wonder that somehow there is no porter for Miatool devices at the moment. So should work exactly like this method presented by Mario. However, I am not a porter and no longer on Ubuntu Touch.

Eric H

Is there a way to make VoLTE work with radioInterface = 1.4 ?

Finally, after commenting on the IMS services lines in the file init.disabled.rc the VoLTE works with radioInterface = 1.4 on POCO X3 NFC.

Some features don't seem to work properly anymore.
I will report on the issues encountered after a few days of testing.

wilfridd

VoLTE enabled on RN9P (joyeuse) too.
Despite most the issuing or receiving VoLTE calls failed, it's very promising! When calling, oFono shows 2 dials at the same time and hanging up is not possible. The callee has not call indication.
I was able to make a successful VoLTE call somehow. I could hear ringing then could talk for about 20sec and all of a sudden the call dropped itself, leaving oFono unresponsive.

kuailexs

This post is deleted!

kuailexs

On the Mi 6. radioInterface = 1.1
VoLTE cannot be used
Although he has already executed the following code
b67ccdc4-a196-4440-803a-237bd41de3c0-图片.png
https://github.com/mer-hybris/ofono-binder-plugin/blob/9ad094cbf772e0796015ad517b727d8577174b74/src/binder_ims.c#L276

phablet@ubuntu-phablet:~$ gdbus call --system --dest org.ofono --object-path /ril_0 --method org.ofono.IpMultimediaSystem.GetProperties

({'Registered': <false>, 'Registration': <'auto'>, 'VoiceCapable': <false>, 'SmsCapable': <false>},)

*Enrico13011978*

@wilfridd said in [Qualcomm} VoLTE call for testing:

VoLTE enabled on RN9P (joyeuse) too.
Despite most the issuing or receiving VoLTE calls failed, it's very promising! When calling, oFono shows 2 dials at the same time and hanging up is not possible. The callee has not call indication.
I was able to make a successful VoLTE call somehow. I could hear ringing then could talk for about 20sec and all of a sudden the call dropped itself, leaving oFono unresponsive.

Congratulations on this successful VoLte attempt on Joyeuse. Exactly my device. May I ask you a question? Do you know which Android 10 version you used before you installed Ubuntu Touch (Xenial, Focal)? If you don't know anymore, no problem, at least now I have hope to get back to Ubuntu Touch at some point. If VoLte works better I think I will come back. Does it work with dual SIM or only on 1 SIM? I might have to install Ubuntu Touch again myself to test it. Only with this script or code from Mario I would definitely need help I'm not that good on the terminal

*Enrico13011978*

I have now installed Ubuntu Touch especially for this VoLte test. I have probably done everything wrong that can be done wrong. Installed the Ubuntu Tweak Tool because of the write permissions. Then off to the terminal and installed the system with sudo apt update&&sudo apt full-upgrade and the Ofono stuff. What can I say, suddenly there were no more SIM cards available and my WLAN data volume was used up, so that went down the drain

JDee Intl

@tigerpro I'm getting the same thing and I'm sure I've got the package spelled correct. When I do an apt update, I get an error:

Archives directory /var/cache/apt/archives/aprtial is missing. - Acquire (30: Read-only file system)

I new here, so apologies if I'm asking an obvious questions.

Platform: Latest Ubuntu Touch installed on Google Pixel 3a XL with AT&T Prepaid service in the U.S. and planning to purchase a FP5 in the near term.

AppLee

HI and welcome @JDee-Intl

You might be in the wrong place.
This post is about testing out the VoLTE plugins for the Fairphone5 and I surmise you just tried to install some deb packages like it would be a regular debian based OS.
This is a common mistake, but the rootfs is readonly on Ubuntu Touch and apt is not supported, it is restricted to developers for creating the image we can later use.

Keneda

@AppLee
He is not mistaking, see there :

https://forums.ubports.com/topic/10484/qualcomm-volte-call-for-testing/25?_=1733537347588

Well, he is mistaking because he tries to install VoLTE on the wrong device, but installing it on the good one, Fairphone 5, needs installing via apt.

AppLee

@Keneda
I realized ; see there: https://forums.ubports.com/post/83786

Using APT is expected in the "porting phase" so to speak.
And I wasn't sure they realized that testing VoLTE is not something any user can do but needs porting skills...

JDee Intl

@Keneda My mistake...I thought I read the port may work for GP3aXL (<- Oh, that's a horrible abbreviation), so I was experimenting.

JDee Intl

@AppLee Now I see, said the blind man! I could not figure out why I couldn't write to the filesystem as root and sudo didn't work with the phone PIN. It's read-only because the entire filesystem is laid down during the porting process and thus only modified by the developers and then included in the port by the porters.

I'll get back to learning the porting process and waiting for the FP5 to go on sale! LOL. Thank you and I hope I'm not stating the obvious, but this is definitely helping me and hopefully others who get involved and read these forums.