VoLTE Implementation For Google Pixel 3a/3a XL
-
Thanks! I'll see what I can find out on that. I'm new to this, so it may take me a while. However, looking at the older port and some other ports, I may be able to piece something together.
-
Agreed. I do see some retro-fitted partiton ports with other alternative OS's. There could be one with Ubuntu Touch too, but I'm not fully aware of one at the moment. Mainly I see Super Partition ports or older Android 9 based ports. There is some documentation that we currently have available for retro-fitted partitions. Any knowledge on this can be shared across the Ubuntu Touch community.
Right now, it looks like we need to figure out what is going on with the deviceinfo file.
-
I got some information on the deviceinfo file, the Fastbootd process, and Retrofit partitions. Now I need to piece everything together, look at the code in the port, and see why some data is lost in the DeviceInfo file after the build process.
Android API for DeviceInfo
https://developer.android.com/reference/androidx/media3/common/DeviceInfo.BuilderDeviceInfo file reference from PostMarket OS
https://wiki.postmarketos.org/wiki/Deviceinfo_referenceDeviceInfo Flash Methods
https://wiki.postmarketos.org/wiki/Deviceinfo_flash_methodsUsing Fastbootd and Retrofit Partitions
https://wiki.postmarketos.org/wiki/Android_dynamic_partitions -
@atarilinux
The UT deviceinfo file for the new port of sargo/bonito can be found here : https://gitlab.com/ubports/porting/community-ports/android12/google-pixel-3a/google-sargo/-/blob/main/deviceinfo?ref_type=headsdeviceinfo_kernel_cmdlineis empty and should probably be completed.The documentation is available at https://docs.ubports.com/en/latest/porting/build_and_boot/standalone_kernel_build.html#filling-in-your-deviceinfo
There is also a sample file : https://gitlab.com/ubports/porting/community-ports/halium-generic-adaptation-build-tools/-/blob/main/deviceinfo.sample?ref_type=heads
-
Thanks! I'll take a look at this!
-
Well, since all US carriers require VoLTE and Android's about to implode in 2027, we kinda need to get at lease one device with Ubuntu Touch to support VoLTE.
-
@Eric-H But does the Halium 12 port have VoLTE?
-
@AetheralMeowstic There are several devices that support VoLTE. However the Pixel 3a / XL is not (yet?) among those.
-
@AetheralMeowstic
in the new halium 12 port for sargo and bonito, VoLTE is configured, yes, but the port is not finalized. -
Do you still have Lineage OS on your phone? We are looking at completing the device info file for this port. The kernel cmdline part is missing. Please see below from the KB Knowledge base. I'm thinking we can pull this info from Lineage OS and use it here if I am understanding correctly.
The kernel cmdline is one of the key things that is required to make the kernel boot. It has special parameters that allow the kernel to determine which features/things need to be enabled, and which need to be disabled. The Ubuntu Touch rootfs also relies on some key cmdlines which is required to boot, most specifically “console=tty0”. To adapt this to your device, try unpacking your boot image (section 8.3) and copying the cmdline from there, or take the help of a LineageOS device tree if it is available. “console=tty0” is a must for cmdline and should not be removed no matter what. Rest of the things can be removed and you can adjust these to your device. console=tty0 is a requirement for the rootfs to properly boot. systempart is added if you want to boot your rootfs from your system partition. It is supposed to point to your system partition.
deviceinfo_kernel_cmdline="console=tty0 bootopt=64S3,32N2,64N2 systempart=/dev/mapper/system" -
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!
