VoLTE Implementation For Google Pixel 3a/3a XL

Eric H

@atarilinux
I see same errors (cp and losesetup) in other ports.
For example:

here's an example of flashing devel images on a device with a super partition :
https://gitlab.com/EricHeintzmann/ubuntu-touch/xiaomi-surya/-/wikis/fastboot-flash

About fastbootd :
https://source.android.com/docs/core/architecture/bootloader/fastbootd

atarilinux

@Eric-H

Thanks! I do see these same errors from the logs of the other device ports you sent me...so maybe that isn't the problem mentioned in the QA call? Also, thanks for the fastbootd link!

Quick question... for any of these devices you sent, are we looking at a retro-fitted partition? The reason why I ask is that I'm trying to match some of this up to the issue presented on the QA call. That way we can see if this part can be resolved.

Eric H

@atarilinux
AFAIK, these devices use a super partition, but not a retro-fitted one.
But, I don't think the build system is aware of the partition type.

atarilinux

@Eric-H

Unfortunately, the Google Pixel 3a uses a retro-fitted partition for Android 12.1 and not the common super partition used in newer Android devices. According to the QA call:

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

Also, the build was not completed.

It very well possible that this was figured out with these other device ports. However, these issues would need to be worked out with this Google Pixel 3a build as I understand it. I'm assuming that is why this build is not considered complete.

Eric H

@atarilinux

You have a retro-fitted super partition
You have images
You have the procedure to flash images in retro-fitted super partition : https://source.android.com/docs/core/architecture/bootloader/fastbootd#dynamic-partitions

What else ?

mr_growl

I flashed lineage 19.1-20231014-nightly-bonito-signed (which the wiki said should have android 12.1):

Android Version: 12 (according to the running system on the phone)
Lineage OS Version: 19-20231014-NIGHTLY-bonito
Phone Version: bonito
Phone Carrier: Amaysim (Optus)
Country: Australia

VoLTE is working just fine.

atarilinux

@Eric-H

What you have stated above is correct to the best of my knowledge. Here is the other part from the QA call:

*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

So....it looks like we need to:

Finish the build (This part is the least specific. Finish what? This is the main issue due to it not being specific. Maybe it is only the retro-fitted partition issue? A lot of data may need to be checked to see what is complete. Here is the bottleneck in completing development.)
Build the image from source
Install image on the Google Pixel 3a

What we have currently:

Information on the retro-fitted partition and possible install process
Confirmation on VoLTE access for the Google Pixel 3a from other alternative OS's and carriers (It is possible!)
Specifically what to look for to see if the carrier supports your Google Pixel 3a (VoLTE Roaming is supported, Hardware check from carrier)

atarilinux

@mr_growl

Great news! Thanks for sharing! I think we are closer. Please see my last post to @Eric-H to see where we are now and the remaining items we will need to figure out.

ElliotLurie

@atarilinux

It seems like some data is lost from the deviceinfo file during the build process... Here's the output of unpack_bootimg after the build:

kernel_size: 18686554
ramdisk size: 6267912
os version: 12.0.0
os patch level: 2022-09
boot image header version: 3
command line args:

FPSensor

when the retrofitted partitions were implemented by pixel 3a stock rom? someone knows that? also would be nice to see if there are more devices that have retrofit to see how they merged it in the build system or what they adapted to get it working, i don remember what loop0 is to be honest

atarilinux

@ElliotLurie

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.

atarilinux

@FPSensor

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.

atarilinux

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

DeviceInfo file reference from PostMarket OS
https://wiki.postmarketos.org/wiki/Deviceinfo_reference

DeviceInfo Flash Methods
https://wiki.postmarketos.org/wiki/Deviceinfo_flash_methods

Using Fastbootd and Retrofit Partitions
https://wiki.postmarketos.org/wiki/Android_dynamic_partitions

Eric H

@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=heads

deviceinfo_kernel_cmdline is 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

atarilinux

@Eric-H

Thanks! I'll take a look at this!

AetheralMeowstic

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.

AetheralMeowstic

@Eric-H But does the Halium 12 port have VoLTE?

arubislander

@AetheralMeowstic There are several devices that support VoLTE. However the Pixel 3a / XL is not (yet?) among those.

Eric H

@AetheralMeowstic
in the new halium 12 port for sargo and bonito, VoLTE is configured, yes, but the port is not finalized.

atarilinux

@mr_growl

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"