@AppLee
Hello all. I'm new here and love all the work you all are doing on Ubuntu Touch. In the United States, the Google Pixel 3a is cheap and readily available. Some of the other phones I've been looking at to run Ubuntu Touch are quite expensive to get in the United States, especially the Fairphone 5. I'd imagine the prices of any phone requiring imports could continue to increase.

Currently, I have been testing with the Google Pixel 3a. Alfred's work on this has been amazing. I'm sure all users of this device will agree! The only thing preventing me from using it as a daily driver is the lack of VoLTE. I'm able to get data over 4G, but I can't get phone calls. Phone calls only occur on 2G. On 4G mode, I can call out, but people can't call in. On 2G mode, I can call out and people can call in. For data priority, I have to switch it to 4G mode. For phone call priority, I have to switch it to 2G mode. 2G is important because I can only receive calls in this mode. The 2G/3G/4G mode won't swap the call down to 2G for me to receive it. I doubt swapping down to 2G is possible, but I could be wrong.

I may need to be pointed in the right direction on how to test. I'm not sure where the project left off and who all may be interested in continuing the development further. However, I want to show my appreciation for all the work done so far and see if this could potentially be taken further by a small group. I know Alfred is incredibly busy and can't dedicate as much time for it. However, for people in the US, the Google Pixel 3a presents a low bar of entry and great accessibility into the world of Ubuntu Touch for those who may want to try it out, learn more, etc.

If any notes can be left and a maybe a direction of where to go with incorporating VoLTE, that would be helpful! I don't know how I can help other than potential testing. I don't know anything about scripting for VoLTE, etc. However, maybe with some notes and research, a group can gather to learn more and help out!

In the worst case scenario that VoLTE won't come to the Google Pixel 3a, another phone recommendation may be needed for users in the US. If there is a phone recommendation that can run VoLTE, 5G, MMS, and Ubuntu Touch 24.04 that is in US, please let me know. I'd like to continue trying to see if I can make Ubuntu Touch a daily driver for me. Again, thanks for all you do!

@AetheralMeowstic

We have confirmed VoLTE is possible with Ubuntu Touch for the Google Pixel 3a. The VoLTE patch is included in this port. We just need to finish this port to get everything up an running. Currently, we need to get the device info file built.

The Ubuntu Touch community does see the need to get VoLTE up and running for those in the US and elsewhere. A number of phones are already running VoLTE. However, a number of these may be hard to get in the US or expensive. For example, the Fairphone 5 can run VoLTE in the US. Trying to find one in the US may be difficult or expensive. That is part of the reason why we are trying to get this port up and running. This could also help our European friends and others if their carrier has not dropped the Google Pixel 3a or does not include VoLTE Roaming.

Unfortunately, the original developer's carrier dropped the Google Pixel 3a, and this is the main reason why this port is unfinished. We already have confirmed that some carriers in the US still support the Google Pixel 3a and VoLTE Roaming. Therefore, we can continue this project for the original developer. We are always looking for people to help test and contribute!

@wally

Thanks! Yes, that is the main reason why I created this post. I wanted to assist anyone in the United States who may be interested in Ubuntu Touch as a potential daily driver and wanted to test VoLTE capability.

There's some great information in your post. I've been searching for some phones in case we can't get VoLTE working on it, it gets dropped by the carrier, etc. I'd definitely like a workable backup, but finding one that I know has official support has been a bit difficult.

I will keep looking and see what I can find out. If I come across anything, I will post here too!

I got a runner and tried to run it, but the build failed. I may need some assistance with Gitlab as I haven't used it before. I'm more used to building on a local machine. It will take me a while to read up on it, and I don't want to slow anyone down.

Here are the changes I made to deviceinfo if someone wants to fork and try it on their own:

deviceinfo_kernel_cmdline="console=ttyMSM0,115200n8 androidboot.console=ttyMSM0 printk.devkmsg=on msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 firmware_class.path=/vendor/firmware cgroup.memory=nokmem lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.boot_devices=soc/7c4000.sdhci androidboot.super_partition=system buildvariant=user"

deviceinfo_bootimg_header_version="2"
deviceinfo_bootimg_os_version="12.0.0"
deviceinfo_bootimg_os_patch_level="2022-05"

This was taken from sargo-sp2a.220505.008-factory-071e368a which is the September 2022 build -
12.1.0 (SP2A.220505.008, Sep 2022).

I got a runner and tried to run it, but the build failed. I may need some assistance with Gitlab as I haven't used it before. I'm more used to building on a local machine. It will take me a while to read up on it, and I don't want to slow anyone down.

Here are the changes I made to deviceinfo if someone wants to fork and try it on their own:

deviceinfo_kernel_cmdline="console=ttyMSM0,115200n8 androidboot.console=ttyMSM0 printk.devkmsg=on msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 firmware_class.path=/vendor/firmware cgroup.memory=nokmem lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.boot_devices=soc/7c4000.sdhci androidboot.super_partition=system buildvariant=user"

deviceinfo_bootimg_header_version="2"
deviceinfo_bootimg_os_version="12.0.0"
deviceinfo_bootimg_os_patch_level="2022-05"

This was taken from sargo-sp2a.220505.008-factory-071e368a which is the September 2022 build -
12.1.0 (SP2A.220505.008, Sep 2022).

It looks like the pipeline is stuck. I'm getting this on GitLab:

"This job is stuck because of one of the following problems. There are no active runners online, no runners for the protected branch , or no runners that match all of the job's tags: ubports
Go to project CI settings"

@Eric-H

I'm performing this step now. I'm currently waiting on it to complete.

@Eric-H said in VoLTE Implementation For Google Pixel 3a/3a XL:

Now that the project has been forked, you can proceed to step 2.
In the new fork, in the left menu, go to Build->Pipelines

click on new pipeline button.
confirm.
Wait - the build process might take several tens of minutes.
.img files can be downloaded from the devel-flashable artifact

I'm assuming the step you listed above handles this part from the documentation, now?

Building, installing and running

After you’ve completed your deviceinfo and filled in all needed stuff, its time you get to the main part, the build. For this just run: ./build.sh -b workdir

That should download all the needed toolchains and then the kernel, and finally build everything. This process may take about 5 to 50 minutes to build the kernel.

After your kernel is done building, you will have to build the rootfs. For this, just execute this:

./build/prepare-fake-ota.sh out/device_<your device's codename>_usrmerge.tar.xz ota This will download the rootfs, extract it and pack it into tarballs for our final script to create flashable images.

Next up, run:

./build/system-image-from-ota.sh ota/ubuntu_command images This will convert the tarballs into flashable images, and your images will be stored in the images/ directory. There will be a number of files depending on how you configured your deviceinfo. But the basic file structure will be as given:
images/
├── boot.img
├── rootfs.img
└── system.img

The boot.img will be flashed onto the boot partition of the phone. The system.img and rootfs.img are interchangable. rootfs.img is pushed to the data partition as ubuntu.img if you didn’t include systempart in deviceinfo’s cmdline. Otherwise, system.img is flashed to your system partition.

@Eric-H

The GitLab has been updated. It looks like we are ready for the build now, right?

https://gitlab.com/atarilinux/ubports-ubuntu-touch-google-sargo-volte/-/blob/main/deviceinfo

@mr_growl

Great! Thanks so much!

@ElliotLurie @Eric-H

Please see below. Does this look like what you need for device_info_kernel_cmdline? Will this complete the device_info file?

@JayH said in VoLTE Implementation For Google Pixel 3a/3a XL:

@atarilinux From the boot.img on lineageOS 22.2-20250817 with working Verizon SIMM:

console=ttyMSM0,115200n8 androidboot.console=ttyMSM0 printk.devkmsg=on msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 firmware_class.path=/vendor/firmware cgroup.memory=nokmem lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.boot_devices=soc/7c4000.sdhci androidboot.super_partition=system

@JayH

It looks kind of similar. Here is one from a UB Ports sample file that I am using for reference.

deviceinfo_kernel_cmdline="console=ttyMSM0,115200n8 earlycon=msm_geni_serial,0xA84000 androidboot.console=ttyMSM0 printk.devkmsg=on androidboot.hardware=qcom video=vfb:640x400,bpp=32,memsize=3072000 androidboot.configfs=true loop.max_part=7 msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 androidboot.memcg=1 cgroup.memory=nokmem androidboot.usbcontroller=a600000.dwc3 swiotlb=2048 androidboot.boot_devices=soc/1d84000.ufshc systempart=/dev/mapper/system"

@JayH @mr_growl

Thanks! This looks like what we need! Is this from a Google Pixe 3a? Also, I wonder if there is any difference in the output between this and Lineage OS 19.1.

@mr_growl

Thanks for checking! Unfortunately, I don't think that's it. I don't see the output beginning with console=.
Did this come from deviceinfo_kernel_cmdline?

@AetheralMeowstic

We have confirmed VoLTE is possible with Ubuntu Touch for the Google Pixel 3a. The VoLTE patch is included in this port. We just need to finish this port to get everything up an running. Currently, we need to get the device info file built.

The Ubuntu Touch community does see the need to get VoLTE up and running for those in the US and elsewhere. A number of phones are already running VoLTE. However, a number of these may be hard to get in the US or expensive. For example, the Fairphone 5 can run VoLTE in the US. Trying to find one in the US may be difficult or expensive. That is part of the reason why we are trying to get this port up and running. This could also help our European friends and others if their carrier has not dropped the Google Pixel 3a or does not include VoLTE Roaming.

Unfortunately, the original developer's carrier dropped the Google Pixel 3a, and this is the main reason why this port is unfinished. We already have confirmed that some carriers in the US still support the Google Pixel 3a and VoLTE Roaming. Therefore, we can continue this project for the original developer. We are always looking for people to help test and contribute!