@Lakotaubp
I am not using Noble. I had no idea it was even around yet until today.

Regardless, on build 177 for FP5, I have successfully registered 5G and VoLTE and was able to call my voicemail, but the older issues persist.

Those being dialing my voicemail PIN doesn't register, and I cannot hang up the call and am forced to restart the phone.

After rebooting the phone, VoLTE comes back but as soon as I make a call, cellular shows 0 bars and after a moment it comes back with full LTE with no VoLTE. Rebooting the phone again shows LTE with VoLTE but calling again drops cellular entirely and it comes back with LTE and no VoLTE.

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

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

Maybe this should be moved to outside the FP5 forum? It's chocked full of people who aren't using the FP5.

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>},)

@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.

@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.

@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.

@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.

I would be able to test on a Fairphone 5.

@x2u said in Best way to support Porting / Checking Status for the Fairphone 5:

@kingu

thanks mr.

Do you mean that Ubuntu Touch will be released this month?

Suposedly the person working on it had some health situation come up so it's been a lesser priority versus getting better.

I hope they are better. I don't know much about it to give further detail, nor is it my business.

Certainly explains the lack of recent news regarding the build.

@rocket2nfinity
Sadly I have noticed this

My Nexus 6P isn't maintained anymore, my PinePhone Pro is just bad, and my Fairphone 5 doesn't have a public release yet. I can't win lol

@Fizz
Does this mean I can use my Nexus 6P using 16.04 in USA since no VoLTE?

@arubislander said in 6P not installable anymore?:

@Inali said in 6P not installable anymore?:

-Install TWRP recovery
-Boot TWRP and delete ALL partitions

Is this a required step based on the instructions? If so, what instructions are you following?

As far as I know the UBports installer does not create partitions, it expects them to be laid out in the correct way as in the stock install.

I found it on other posts regarding the installer not working correctly. I also tried this without wiping partitions and the result is always the same. It runs the script, boots to UT recovery, and does nothing forever. Cannot figure out why. Seems to be a common issue as there are tons of threads about the exact same issue on the same phone.

@flohack said in 6P not installable anymore?:

Seems smth was wrong on my side, a second attempt worked then

How did you fix this? Mine won't install past the recovery screen like in your first post.

-Unlock bootloader
-Install Android 7.1.2
-Enable Developer mode
-Enable USB Debugging
-Install TWRP recovery
-Boot TWRP and delete ALL partitions
-Boot to bootloader
-Run UBPort installer
-Get stuck on Ubuntu recovery screen forever.

I repeated this multiple times, doesn't work.
What gives?

@bbiw
Have you looked at this at all?
https://github.com/waydroid/waydroid/issues/680

@kugiigi
Ah, perfect. This is what I wanted to know. I suppose I'll just continue to impatiently wait and open the installer every day to check lol

So, will the image magically show up in the installer application when ready, or will we need to update the installer app?

I keep checking the installer app every day with my fingers crossed.

@CatWithUT I hope it works out well.

Honestly I give 0 cares for Waydroid. I doubt I'll even enable it.

I've run horribly unoptimized software releases on numerous devices, I wouldn't be opposed to being a tester for the FP5, regardless if it's an open public release or not. Sadly there seems to be no way to sign up for such a test.

Gosh I really want this to release. I'm so excited for it. VoLTE is 100% mandatory for me though, since I'm in the USA which requires VoLTE on literally all carriers for a phone to work at all. Hopefully there is a working beta sooner than later!

Fingers crossed.

VoLTE is a minimum requirement for all three USA carriers. None of the 3 carriers will activate a phone if it doesn't support VoLTE.
Super sucks for me since I'm in USA and itching to dump Android.