VoLTE Implementation For Google Pixel 3a/3a XL

Eric H

@Nocflounder
Correction: acccording to the source code, yes, bonito is supported by the new android 12 port.

https://gitlab.com/ubports/porting/community-ports/android12/google-pixel-3a/google-sargo/-/blob/main/overlay/system/etc/deviceinfo/devices/halium.yaml#L21

Nocflounder

@Eric-H thanks for the answer

atarilinux

@Nocflounder

It is. Hahaha

atarilinux

@Eric-H @Nocflounder

Thanks! I will need bonito as well! Good to hear it is supported! Also, thanks for the information on Gitlab!

atarilinux

@Eric-H @Nocflounder @AppLee
The project has been forked on GitLab. Here is the link:
https://gitlab.com/atarilinux/ubports-ubuntu-touch-google-sargo-volte

Now how do I get it from here to the phone to begin testing? Would that be this:
https://docs.ubports.com/en/latest/porting/build_and_boot/index.html

Or...has this already been done?

I have the newest Ubports-installer on my Debian Linux computer. Thanks!

Eric H

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

Next steps (make sure your phone bootloader is unlocked) :

on your phone flash stock android 12 ROM - use exactly the same version used by the developer.
flash the downloaded .img files with fastboot/fasbootD
test and report

Eric H

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

Now how do I get it from here to the phone to begin testing? Would that be this:
https://docs.ubports.com/en/latest/porting/build_and_boot/index.html

Or...has this already been done?

build step have been done in you fork - at step 2

I have the newest Ubports-installer on my Debian Linux computer. Thanks!

Currently, the new port cannot be installed by the the UBports installer.

atarilinux

Next steps (make sure your phone bootloader is unlocked) :

on your phone flash stock android 12 ROM - use exactly the same version used by the developer.

flash the downloaded .img files with fastboot/fasbootD

test and report

@Eric-H
I'm trying to locate the exact Android 12 version used by @fredldotme. Is this listed somewhere in the files and/or documentation? Perhaps I'm overlooking it.

Keep in mind I use bonito, and the code in the device info file only mentions sargo. I'm not sure if that would need to be updated. Some files include bonito, but this specific file only mentions sargo. Perhaps bonito and sargo share some files?

Eric H

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

I'm trying to locate the exact Android 12 version used by @fredldotme. Is this listed somewhere in the files and/or documentation? Perhaps I'm overlooking it.

Usually, this is documented on the device page of the port.
But not in this case...

Keep in mind I use bonito, and the code in the device info file only mentions sargo. I'm not sure if that would need to be updated. Some files include bonito, but this specific file only mentions sargo. Perhaps bonito and sargo share some files?

Yes, some ports share repo ( see surya and karna , or miatoll, or android 9 sargo and bonito).

For all your questions I recommend asking on UBports Telegram (Pixel 3a and Porting groups)

atarilinux

@fredldotme @AppLee
Do you have any insight on this? We are wanting to help with testing. Thanks!

atarilinux

@Eric-H

Thanks! Good to know I wasn't missing anything in the documentation. Sorry, I don't use Telegram.

Eric H

@atarilinux
Without Telegram, it might be complicated, as almost all discussions regarding UT take place there.
If you use Matrix, I believe there are bridges to these Telegram groups.

atarilinux

@Eric-H

I looked into Matrix, and it looks good so far. I'll research it more and see if I can get it set up. Thanks for the recommendation!

kyleh

@atarilinux I have a Pixel 3a and am happy to help test with this, too.

atarilinux

@kyleh

Great! Thanks so much! We are currently waiting to know what Android version the image is built for. Once we hear that, it sounds like we can begin testing.