VoLTE Implementation For Google Pixel 3a/3a XL

atarilinux

I put a question on the Q&A call about the Android version used. Please include any additional information needed. Thanks!

Futura

@atarilinux
There is a pretty good chance that this may never come to fruition. I read somewhere in my research in the last couple of days that this requires a kernel patch that possibly never happened for the 3a/XL. This could easily be outdated information, and there is a LOT of that on the internet about UT and it really makes it hard to get a solid grasp on what is what.

I'll be watching the Q&A call, but I am not exactly holding my breath for this to work. I have actually ordered a FP5, but if I can help this happen that would be amazing, I really love the Pixel 3a XL hardware.

atarilinux

@Futura

I've heard that the patch was made in the newer Android version, but that is not very specific (which one, etc.). I also heard that VoLTE was in the newer Android image file made by @fredldotme and that only testing was needed (but that hasn't been verified). Both of these statements could potentially be cleared up in the Q/A call I'm hoping.

Like you, I'm not holding my breath too much either. However, if both of these statements are indeed true, then we will be in a good place for the Google Pixel 3a hardware. Otherwise, I will also be considering a different phone capable of VoLTE and Ubuntu Touch.

If you don't mind me asking, how was shipping, etc. for the Fairphone 5 to the US? I'm assuming it is an expensive piece of hardware for us now, right? If you begin testing the Fairphone 5 in the US, I'd be happy to hear how it goes! It was my plan B as well, but I think I'd need to save up a bit before even considering it. That's part of the reason why I've been adament about trying to keep the Google Pixel 3a up to speed as a potential daily driver. I think it is at a great price point for someone to try out Ubuntu Touch....with a great port at that! Also, more daily drivers = more publicity. Let's see how the Q/A goes and then if we can't see a clear path forward, I will also be looking at the Fairphone 5. Thanks again for all your research and help!

atarilinux

@Futura

I found a support article and a news article that references the patch:

https://support.google.com/pixelphone/answer/12240791?hl=en

https://www.androidheadlines.com/2022/06/june-update-pixel-phones-enables-volte-roaming-many-carriers.html

Main thing of note here.... It is VoLTE Roaming only for the Pixel 3a. Is there anything in the Android Repository for June 2022? Android 13 wasn't released until August 2022, and support for Android 12 ended on March 2025.

atarilinux

@fredldotme @AppLee
Thanks for UBPorts for the great Q&A call and for featuring our question! I am going to post what I gathered from the call here.

On Android 12 port for the Google Pixel 3a on GitHub:
*Source Material - Not Image
*Information on image build process, but not how to install it
*Built on top of latest Android 12.1 version for the Google Pixel 3a, but build not completed

Issues with building/installing:
*Issue with getting image on phone
*Has retrofitted system super-partition, this means two partitions act as they are one
*Has not been installed in this type of environment, we would need to figure it out

Issues with Carriers for Google Pixel 3a:
*Some Carriers dropped VoLTE connection for Google Pixel 3a. This happened in Austria to @fredldotme. Check to see if your carrier still plans on suppoting the Google Pixel 3a.

Just a note from my research. Google only allowed VoLTE Roaming for the Google Pixel 3a. I'm wondering if this (and possibly age as well) has caused carriers to drop the Google Pixel 3a. If your carrier does not support the Google Pixel 3a or VoLTE Roaming, you can't test to see if anything works.

Should you wish to continue to try to get VoLTE on the Google Pixel 3a:
If old phones are regularly dropped from carriers, the Google Pixel 3a's VoLTE may no longer be supported even if the VoLTE code works. One would need to test with the latest Android build with the VoLTE Roaming patch to make sure one's carrier supports the Google Pixel 3a and VoLTE Roaming. This means using Android 12.1, not Ubuntu Touch. If one's carrier does, then you can join in trying to see if we can get VoLTE working on Ubuntu Touch for the Google Pixel 3a. However, keep in mind your phone's VoLTE could potentially be desupported in the future by your carrier.

Should you wish to abandon the Google Pixel 3a as a daily driver phone:
For those in a non-European country who may be affected, a port to another easily accessible phone in your area with current VoLTE support may be preferable. Otherwise, if the means are available, a Fairphone 5 will be officially supported by the great UBPorts team. Make sure to check if your carrier supports the Fairphone 5 before buying.

Nocflounder

@atarilinux can we boot UT based on android 12 now?

atarilinux

@Nocflounder

I could be wrong, but it sounds like a no for the Google Pixel 3a. The build is not install-ready. The super-partition issue has to be worked out first.

atarilinux

I found something interesting on a super-partition. Maybe this can help with getting the super partition issue for the Google Pixel 3a resolved? I'd need someone more technical in this realm to weigh in.

https://xdaforums.com/t/guide-universal-guide-for-making-your-partitions-inside-super-read-writable-again.4483933/

atarilinux

@Futura @Eric-H

Do you still want to try this? If so, I can kick off Step 2 on GitHub. From my notes, this is what you stated last.

Lineage 19.1
Android 12.1 (September build)
Side load via TWRP, Do not use fastboot

Based on the Q&A Call, I don't know if this is something you still want to try out because of the retro-fitted Super Partition issue and that the installation process is a bit unclear. Based on my reading, I'm assuming this is probably not an issue just to Ubuntu Touch or the Google Pixel 3a, but I could be wrong. I'm assuming this part has already been figured out somewhere and that we would just need to apply a similar fix to the Ubuntu Touch port.

Futura

@atarilinux
After attempting to use LineageOS to connect to my cell network and test VOLTE, I found that my device would not even get cell service at all. MVNO reselling att.
I think even if I got that to boot, it would still not activate on my carrier.

Futura

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

@atarilinux
After attempting to use LineageOS to connect to my cell network and test VOLTE, I found that my device would not even get cell service at all. MVNO reselling att.
I think even if I got that to boot, it would still not activate on my carrier.

I might be mistaken here and thinking about my old old P2 XL, I did a LOT of device flip/flopping over the last month or two. My 3a XL was supposedly refurbished and was having battery issues so I sent back to the seller. I have been focusing time and finances into the Fairphone 5 since.

atarilinux

@Futura

If it doesn't work with Lineage OS, I think one of the following is probably happening:

The VoLTE patch for the Google Pixel 3a might not be in the Android image.
Lineage OS might not be picking it up.
Lineage OS supports VoLTE, but not VoLTE roaming. I read somewhere that the VoLTE patch only allows VoLTE roaming on the Google Pixel 3a.
The roaming setting might not be turned on in the Lineage OS settings.
The carrier doesn't support VoLTE roaming.
The carrier dropped support for the Google Pixel 3a.

I completely understand on the device switching and focusing on the Fairphone 5. No issues or worries there! I'm also on the market for a new phone as I'm certain this device is on borrowed time. I'm still looking to get a Fairphone 5 if I can. However, any progress made on the Google Pixel 3a would be good I think as it seems a number of users were using this phone in the US. So, until I can get a new phone, I'm going to be seeing what I can do with this one. Enjoy the Fairphone 5! I heard it is great with Ubuntu Touch on it!

atarilinux

Just checking in to see if anyone is willing to help test to see if we can get VoLTE to work on the Google Pixel 3a with any version of Lineage OS. This will help determine if VoLTE is even remotely possible for the Google Pixel 3a. We will need to look at several carriers. If you try this out, please list the following:

Android Version (We currently think the VoLTE patch is in Android 12.1.)
Lineage OS Version
Phone Version (sargo or bonito)
Phone Carrier
Country

If Lineage OS can detect VoLTE, this can give some hope that we may be able to get VoLTE working in the Google Pixel 3a for Ubuntu Touch.

atarilinux

Some more info on the VoLTE Patch. It looks like it only supports Verizon and Unlocked Google Pixel 3a models in the US. Not sure about international models. Similarly, the patch only enables VoLTE Roaming which has to be allowed by the carrier. The patch was available as an OTA update to Android 12 on June 2022.

https://www.xda-developers.com/google-pixel-3a-june-2022-update/

Additional information on installing and testing the Google Pixel 3a with Android 12 to see if your carrier supports VoLTE Roaming.

https://www.androidinfotech.com/37846-install-google-pixel-3-xl-volte-roaming-support-update/

If VoLTE works for you with Android 12, then we know we can move forward with seeing if we can get this incorporated into Ubuntu Touch. If this does not work for anyone, then we will need to switch to a different device if we want VoLTE. It has already been confirmed that not all carriers support this update. Even though VoLTE roaming is enabled on the phone with the Android update, the carrier will drop the calls down to 2G, even with the Android 12 VoLTE patch. It is important to ensure both the phone and the carrier is supported with VoLTE Roaming capabilities for the Pixel 3a. Even if we get everything to work, we will probably be looking at a much smaller population than all Google Pixel 3a/3a XL Ubuntu Touch users getting VoLTE because of this nuance.

ElliotLurie

I'm willing to help test. I have Verizon, live in the USA, and have VoLTE working on the latest version of LineageOS for MicroG. How can I help?

Also, can I get some elaboration on the super partition problem? It doesn't seem to be an issue for Postmarketos on a mainline kernel.

ElliotLurie

After forking and building myself, I assume these lines have something to do with it?

cp: cannot stat 'partitions/*': No such file or directory
System image: Applying update: halium_halium_arm64.tar.xz
cp: cannot stat 'partitions/*': No such file or directory
System image: Applying update: device_sargo.tar.xz
System image: Applying update: version.tar.xz
cp: cannot stat 'partitions/*': No such file or directory
losetup: /dev/loop0: detach failed: No such device or address

Can these be fixed by tinkering with the build script or the kernel?

mr_growl

@atarilinux I've been using a pixel 3a with volte for several months on lineage with no problems.

Android version: 15
LineageOS version: 22.2-20250607-NIGHTLY-sargo
Phone Version: Sargo
Phone Carrier: Amaysim (Optus)
Country: Australia

atarilinux

@ElliotLurie

I think that's the error. The issue was brought up on the QA call. Please see the link below.

https://m.youtube.com/watch?v=Ox9HLXrOkIg&pp=0gcJCa0JAYcqIYzv

More info on the Ubuntu Touch porting process can be found below.
https://docs.ubports.com/en/latest/porting/introduction/index.html

If the super partition issue can be addressed, I'm assuming the rest will follow as that was the main issue stated on the call. Unfortunately, I'm new to this, so it will take me a while to read up, fiddle with the code, take notes, and make any necessary changes. Any help with this is greatly appreciated!

atarilinux

@mr_growl

Good to know! Thanks so much! The current Ubuntu Touch VoLTE port in development left off on Android 12.1. The current production-ready Ubuntu Touch port (without VoLTE) is based around Android 9. We can certainly use this information as a reference for any new Google Pixel 3a Ubuntu Touch ports!

atarilinux

@ElliotLurie

I have some more info on the error message and the super partition.

On the cannot stat error:
https://stackoverflow.com/questions/34254164/getting-an-error-cp-cannot-stat-when-trying-to-copy-files-from-one-folder-to-an

Postmarket OS has some info on the super partition and dynamic partitions:
https://wiki.postmarketos.org/wiki/Android_dynamic_partitions

From the Android documentation:
https://source.android.com/docs/core/ota/dynamic_partitions/implement

Now we just have to see how we can put this all together for Ubuntu Touch.