VoLTE Implementation For Google Pixel 3a/3a XL
-
-
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:
-
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
-
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_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
-
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.