VoLTE Implementation For Google Pixel 3a/3a XL

Eric H

@mr_growl
Accordind to the deviceinfo file in your repo, you set systempart, thus you need to flash boot.img to boot and system.img to system (fastbootD might be needed).
And maybe flashing dtbo.img to dtbo is needed too...

Have you access to Telegram? You will find help in the group linked in the porting documentation.

mr_growl

@Eric-H I tried a build without the systempart section (the droidian porting doc said to remove it) and then tried flashing just the boot.img and rootfs.img in fastbootd mode using these commands:

fastboot flash boot boot.img
fastboot flash userdata rootfs.img

Also tried flashing the sytem.img using

fastboot flash system system.img

But that always fails saying it can't resize the partition.

If anyone wants to play with the boot.img, it's in the artifacts from my latest build: https://gitlab.com/mr-growl/ubports-ubuntu-touch-google-bonito-volte/-/jobs/11808428371

But it doesn't seem to do anything useful.

I'll try to get on to telegram (it's not letting me in currently). I'm just guessing on the android stuff at the moment. Trying various combinations of images and commands, re-flashing android 12 inbetween attempts.

Thanks all for suggestions on things to try. Much appreciated.

mr_growl

Might just go back a step and try getting a halium 9 build working, since I know that should actually work. Then maybe increment from there.

Eric H

@mr_growl
I think halium 12 is required for VoLTE.

according to the porting doc and the history of the porting group, without the systempart option you have to

flash boot img to boot, that's ok.
rename root.img to ubuntu.img
push ubuntu.img to userdata with adb
adapt and launch these command in recovery mode
```
adb shell mount /data; adb push ubuntu.img /data/
```
maybe flash dtbo.img to dtbo is required (I suggest to test first without flashing, then flash it if phone does not boot.
do NOT flash system.img

Eric H

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

Might just go back a step and try getting a halium 9 build working

The full system method will be discouraged/deprecated very soon
https://gitlab.com/ubports/docs/docs.ubports.com/-/merge_requests/675

atarilinux

@mr_growl

To verify, you want me to see what I can find out on a Halium 12 stand-alone kernel method port. Is that correct? Again, thanks for all your hard work on this!

atarilinux

@Eric-H

Your comments and insight are always appreciated! Thanks for all the help!

Eric H

For information, documentation has been updated.
The "install“ page can be found at
https://docs.ubports.com/en/latest/porting/build_and_boot/standalone_kernel_install.html

mr_growl

@Eric-H Thank you for the detailed instructions. I very much appreciate it.

Here's what I did:

boot into android recovery and do factory reset (to remove encryption)
boot into twrp (fastboot boot twrp.img) and go into terminal
unmount /data (/dev/block/mmcblk0p72)
format /data as ext4 (mk2sfs -t ext4 /dev/block/mmcblk0p72)
remount /data (mount /dev/block/mmcblk0p72 /data)
confirm it is now mounted at ext4 (mount)
push renammed rootfs.img to /data (adb push ubuntu.img /data/)
reboot into bootloader from twrp
boot into fastbootd (fastboot reboot fastboot)
flash boot (fastboot flash boot boot.img)
reboot... this takes me straight to the boot loader
flash dtbo (fastboot flash dtbo dtbo.img)
reboot... still goes back to boot loader

I'm doing the formatting to ext4 bit as I read somewhere that it is required (please let me know if this was a mistake)

I'm pushing ubuntu.img before flashing boot.img because flashing boot.img gets rid of recovery and fastbootd.

I'm still feeling like there's a problem with my boot.img, as if I flash the boot.img from my halium build, it actually boots to recovery and fastbootd.

Eric H

@mr_growl
userdata
yes formating /data to ext4 is required at first installation
Just in case maybe retry with fastboot

fastboot format:ext4 userdata

you can wipe cache partition too

fastboot format cache

What does dmesg -w return on your host computer ?

https://docs.ubports.com/en/latest/porting/build_and_boot/Boot_debug.html

When your device boots it will likely stay at the bootloader screen.
[...]
To confirm that your device has booted correctly, on your host computer, run dmesg -w and watch for “GNU/Linux device” in the output. This confirms that you can establish an ssh connection to the device (see below). If you instead get something similar to “Halium initrd Failed to boot”, skip to telnet connection.

mr_growl

@Eric-H Thank you again!

Here's what dmesg has to say after my last flash attempt:

[ 9780.171034] usb 1-2: new high-speed USB device number 40 using xhci_hcd
[ 9781.164612] usb 1-2: New USB device found, idVendor=18d1, idProduct=4ee0, bcdDevice= 1.00
[ 9781.164633] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 9781.164641] usb 1-2: Product: Pixel 3a XL
[ 9781.164648] usb 1-2: Manufacturer: Google
[ 9781.164654] usb 1-2: SerialNumber: XXXXXXXXX

I'll wipe it again and try again with your last message in mind later. I completely forgot to check to boot debug documentation, so I'll have a read through that again as well.

Eric H

@mr_growl
Which kernel do you use ?
in device info,on one of your gitlab repositories, I see
deviceinfo_kernel_source="https://github.com/mr-growl/android_kernel_google_msm-4.9.git"