VoLTE Implementation For Google Pixel 3a/3a XL

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.

Futura

@atarilinux Bonito here, in the US, ready to flash and test.
I noticed while digging around in the link Commit b93e8d44 it points to Lineage 19.1 repository.
That is built on Android 12.1 which I think would line up with this. I checked for install instructions for lineage 19.1 as the newer ones specifically say what version of stock android your phone should have before flashing and its not there. Looks like it used a different method of side loading with TWRP for 19.1 and not flashing via fastboot.

atarilinux

@Futura

Good info! Thanks! I saw this on the link you sent. It is in the device info file. Does this shed any light on your theory? Can we use this information to try to match up the right Android version?

deviceinfo_bootimg_header_version="3"
deviceinfo_bootimg_os_version="12"
deviceinfo_bootimg_os_patch_level="2022-09"

Also, it sounds like we have some additional questions on the install process, right?

Futura

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

@Futura

Good info! Thanks! I saw this on the link you sent. It is in the device info file. Does this shed any light on your theory? Can we use this information to try to match up the right Android version?

deviceinfo_bootimg_header_version="3"
deviceinfo_bootimg_os_version="12"
deviceinfo_bootimg_os_patch_level="2022-09"

Also, it sounds like we have some additional questions on the install process, right?

Assuming patch level="2022-09" is the build date of that android patch for bonita, that lines right up with:
12.1.0 (SP2A.220505.008, Sep 2022) Flash Link db19d2aaff36f29b7f58f11acad856f9382dafa1ae9160a692782e27cd7b0002

From Googles Factory Images page.

I would certainly like a run through of building this, I put a little time into reading up on it this morning but I like to be solid on what I am doing before attempting anything.

Futura

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

Hi @atarilinux
It is better to rebuild the images and it is easy.
This can be done is two step.
First step, fork the repository on gilab :

sign in/up to gitlab.com on your desktop

go to the new port repository : https://gitlab.com/ubports/porting/community-ports/android12/google-pixel-3a/google-sargo

click on fork button

click on fork project (keep the public visibility)

@atarilinux Have you done the above process yet? When I check for pipelines from your fork I just get "There are currently no pipelines. ".

@Eric-H First off thanks for the excellent info, if the above process was not carried out is the expected results no pipelines?

I can see the original build's and where some had failed...

Eric H

@Futura Pipelines are launched in STEP 2

Futura

@Eric-H My fault I had quoted the incorrect post!

atarilinux

@Futura @Eric-H

I haven't done Step 2 yet for building the pipelines. I was trying to figure out the Android Image and Installation Process. I wanted to include that in the description, so everyone knows the exact steps on what to do with the image. I may be getting ahead of myself though. I can certainly build out the pipeline if we feel we need it now.

Futura

@atarilinux
Not trying to pressure anyone into anything, just checked were we stand on this.

I will say after experimenting this morning with LineageOS for the 3a XL flashing 22.2 with the base version of 12.0.0 (SQ1A.220205.002, Feb 2022) was the most stable for me. I am not sure if 19.1 and 22.2 use the same base version of stock android, or if @fredldotme used a different specific version.

atarilinux

@Futura

No worries! I didn't feel any pressure! I was just holding off until I could feel more confident on the steps to install and test. However, it sounds like we are potentially further along with your help. I'm still new to this, so your help is much appreciated!

Just let me know when you feel confident enough to move forward, and I can build out a pipeline. I'll add the notes of what you are testing with and say that this is in Alpha build with a notice of potential risk. That way we don't have some random user installing it thinking it will work 100% or something. Sound good?

atarilinux

@Futura @Eric-H

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