[Qualcomm} VoLTE call for testing

Lakotaubp

Inali

@mariogrip I will give this a go, but I noticed something first...

I already am on devel, and today I put in my SIM card (I am in USA with TMobile) and I noticed my Fairphone 5 will drop from 5G to "L" (which I assume is short for LTE) during calls and calls work. Is this a fair assumption that VoLTE is already working? The switch in the carrier settings is already enabled.

This was all without me doing anything aside from updating to the devel branch. Why does this work without your additional above instructions?

Either way, great work so far!

EDIT: Forgive me, maybe the interface glitched. I see it shows 2G when in calls. I will try the above instructions.

tigerpro

@mariogrip I copied the configs from the FP5 gitlab from about 24 hours ago and that got LTE working, when I tried calling the cell icon didnt show it dropped out of LTE, to install ofono-binder-plugin-qti is there a link or something to install it? Im bit rusty on some of this.

edit: I tried to install with apt as I saw you mention that in another post but it gave me an error saying it couldnt find ofono-binder-plugin-qti

On another note, glad to have ya back, missed ya

Inali

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

edit: I tried to install with apt as I saw you mention that in another post but it gave me an error saying it couldnt find ofono-binder-plugin-qti

I used UT Tweak Tool to unlock the system to be writable, then ran "sudo apt update" to update list of apps, then installed ofono-binder-plugin-qti, then modified the file as stated, then rebooted to reapply read only.

tigerpro

This post is deleted!

tigerpro

@Inali this is what I keep getting after I do a apt update then try to install

root@ubuntu-phablet:/android/vendor/lib64/hw# apt install ofono-binder-plugin-qti
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package ofono-binder-plugin-qti
root@ubuntu-phablet:/android/vendor/lib64/hw#

EDIT:

I just figured it out, the package is ofono-binder-plugin-ext-qti Ill test it now

Inali

@mariogrip

I have tried this and it appeared to work for VoLTE calls briefly. Sometimes I could see the VoLTE logo, other times it was not there. I only called my voicemail so it wasn't anything ground breaking.

Also after an hour or so (or when I noticed) my SMS stopped allowing texts to send completely and only received texts if I toggled Airplane mode on and off for some reason, and reverting the steps to disable VoLTE did not fix this. I am unsure how or why this happened or if it is relevant, but absolutely nothing else changed on the phone since enabling VoLTE per the instructions since I was using the phone purely to test this feature.

I ended up wiping the device with a fresh copy of dev channel v30 image and immediately enabled VoLTE again with your instructions. I will put my SIM back in the Fairphone 5 tomorrow as I need it to work at home for now

I will keep everyone posted.

kuailexs

Thank you for your work.
I will try to test it on xiaomi mi6. Use a China Mobile SIM card. After I successfully upgraded mi6 to 20.04.

*Enrico13011978*

@mariogrip Thank you very much, I will do that.

alagirialagiri

@mariogrip i understand that ,the message you posted is specially for porters of other devices .They have to put their effort to make the devices work in VoLTE.We have to wait for them to finish it.Thanking you.

Luksus

@mariogrip could you please explain a bit, the different settings in qti.conf, for porters of other devices?

For example the "radioInterface" number, what is it and is that device specific?
How is the syntax for two slots in "ExpectSlots", slot1,slot2?

Then, for activating, I suspect OfonoPlugin: binder must be set in deviceinfo file.
What about OfonoImplementsIms? Is that needed in any way? From the MR, I understand, that it activates/displays the VoLTE switch in SIM-settings, but at least, it already gets displayed without the deviceinfo setting.

And, what are the first places to have a look, when using the ofono-binder-plugin and nothing works?

Thanks and best regards,
Lukas

Inali

@mariogrip

As of this morning, I have tried dev build 33 with this VoLTE config.

If I call my phone number with a different phone, my Fairphone 5 will open the dialer immediately and show that it is trying to call the incoming caller, but nothing ever happens. It will stay on this screen forever even with airplane mode on. I am forced to pull the battery out. (shutdown and reboot no longer work on the phone, both show a black screen and the power button is unresponsive.)

I have noticed although I have full bars for 5G and LTE, the phone will frequently drop to LTE.

I have also noticed that the VoLTE logo constantly disappears. I saw the logo saying VoLTE, made a test call, noticed VoLTE was gone, and my signal instantly went to nothing as this test area has no 2G coverage. The call then is frozen on, even if you close the dialer and I again am forced to remove the phone battery since I cannot shutdown or reboot correctly.

Hopefully these tests mean something to you are are helpful.

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.