VoLTE Implementation For Google Pixel 3a/3a XL
-
It looks kind of similar. Here is one from a UB Ports sample file that I am using for reference.
deviceinfo_kernel_cmdline="console=ttyMSM0,115200n8 earlycon=msm_geni_serial,0xA84000 androidboot.console=ttyMSM0 printk.devkmsg=on androidboot.hardware=qcom video=vfb:640x400,bpp=32,memsize=3072000 androidboot.configfs=true loop.max_part=7 msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 androidboot.memcg=1 cgroup.memory=nokmem androidboot.usbcontroller=a600000.dwc3 swiotlb=2048 androidboot.boot_devices=soc/1d84000.ufshc systempart=/dev/mapper/system"
-
Please see below. Does this look like what you need for device_info_kernel_cmdline? Will this complete the device_info file?
@JayH said in VoLTE Implementation For Google Pixel 3a/3a XL:
@atarilinux From the boot.img on lineageOS 22.2-20250817 with working Verizon SIMM:
console=ttyMSM0,115200n8 androidboot.console=ttyMSM0 printk.devkmsg=on msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 firmware_class.path=/vendor/firmware cgroup.memory=nokmem lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.boot_devices=soc/7c4000.sdhci androidboot.super_partition=system
-
@atarilinux Here's the one extracted from the lineage 19.1 signed zip that I used to flash the phone:
deviceinfo_kernel_cmdline="console=ttyMSM0,115200n8 androidboot.console=ttyMSM0 printk.devkmsg=on msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 firmware_class.path=/vendor/firmware cgroup.memory=nokmem lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.boot_devices=soc/7c4000.sdhci androidboot.super_partition=system buildvariant=userdebug"That is lineage 19.1 (android 12.1) on bonito.
-
@atarilinux And a lineage 19.1 sargo for good measure
deviceinfo_kernel_cmdline="console=ttyMSM0,115200n8 androidboot.console=ttyMSM0 printk.devkmsg=on msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 firmware_class.path=/vendor/firmware cgroup.memory=nokmem lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.boot_devices=soc/7c4000.sdhci androidboot.super_partition=system buildvariant=userdebug" -
Great! Thanks so much!
-
@atarilinux @mr_growl @JayH
There is a script to extract command line args and other needed fields.
See at https://docs.ubports.com/en/latest/porting/build_and_boot/standalone_kernel_build.html#extracting-values-from-stock-boot-img-vendor-boot-img -
The GitLab has been updated. It looks like we are ready for the build now, right?
https://gitlab.com/atarilinux/ubports-ubuntu-touch-google-sargo-volte/-/blob/main/deviceinfo
-
I'm performing this step now. I'm currently waiting on it to complete.
@Eric-H said in VoLTE Implementation For Google Pixel 3a/3a XL:
Now that the project has been forked, you can proceed to step 2.
In the new fork, in the left menu, go to Build->Pipelinesclick on new pipeline button. confirm. Wait - the build process might take several tens of minutes. .img files can be downloaded from the devel-flashable artifactI'm assuming the step you listed above handles this part from the documentation, now?
Building, installing and running
After you’ve completed your deviceinfo and filled in all needed stuff, its time you get to the main part, the build. For this just run: ./build.sh -b workdir
That should download all the needed toolchains and then the kernel, and finally build everything. This process may take about 5 to 50 minutes to build the kernel.
After your kernel is done building, you will have to build the rootfs. For this, just execute this:
./build/prepare-fake-ota.sh out/device_<your device's codename>_usrmerge.tar.xz ota This will download the rootfs, extract it and pack it into tarballs for our final script to create flashable images.
Next up, run:
./build/system-image-from-ota.sh ota/ubuntu_command images This will convert the tarballs into flashable images, and your images will be stored in the images/ directory. There will be a number of files depending on how you configured your deviceinfo. But the basic file structure will be as given:
images/
├── boot.img
├── rootfs.img
└── system.imgThe boot.img will be flashed onto the boot partition of the phone. The system.img and rootfs.img are interchangable. rootfs.img is pushed to the data partition as ubuntu.img if you didn’t include systempart in deviceinfo’s cmdline. Otherwise, system.img is flashed to your system partition.
-
It looks like the pipeline is stuck. I'm getting this on GitLab:
"This job is stuck because of one of the following problems. There are no active runners online, no runners for the protected branch , or no runners that match all of the job's tags: ubports
Go to project CI settings" -
I got a runner and tried to run it, but the build failed. I may need some assistance with Gitlab as I haven't used it before. I'm more used to building on a local machine. It will take me a while to read up on it, and I don't want to slow anyone down.
Here are the changes I made to deviceinfo if someone wants to fork and try it on their own:
deviceinfo_kernel_cmdline="console=ttyMSM0,115200n8 androidboot.console=ttyMSM0 printk.devkmsg=on msm_rtb.filter=0x237 ehci-hcd.park=3 service_locator.enable=1 firmware_class.path=/vendor/firmware cgroup.memory=nokmem lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.boot_devices=soc/7c4000.sdhci androidboot.super_partition=system buildvariant=user"deviceinfo_bootimg_header_version="2" deviceinfo_bootimg_os_version="12.0.0" deviceinfo_bootimg_os_patch_level="2022-05"This was taken from sargo-sp2a.220505.008-factory-071e368a which is the September 2022 build -
12.1.0 (SP2A.220505.008, Sep 2022). -
@atarilinux I haven't done much with gitlab but have experience with github runners. I'll try to get something going this weekend. I gather the error in your last build is due to not running as the root user. Maybe try putting a "sudo" in front of the apt commands in .gitlab-ci.yml ?
-
@atarilinux
unsure but maybesystempart=/dev/mapper/systemis missing in cmdlinefrom porting Telgram Group :
system.img and rootfs.img are the same thing from a fastboot POV. your userdata should be freshly formatted as ext4, but yes that's what the bottom of the doc also explains, which one you need and how to flash it depends on if you included e.g. systempart=/dev/mapper/system on cmdline for devices with super partition
also unsure about other fields
-
@atarilinux
it seem this this file should be updated too :
https://gitlab.com/atarilinux/ubports-ubuntu-touch-google-sargo-volte/-/blob/main/.gitlab-ci.yml -
That's what I'm thinking too. When I looked at it again today, it looked like permission was denied because it wasn't running as sudo. I was using the runner on my local machine. I noticed it didn't prompt me for my password which was interesting. So, yes, we probably need to add sudo to the file.
-
Thanks for the info! Just to verify, should work for a retro-fitted partition too, right? I'll check this out in the file and see if I can find anything else that may need to be added.
-
Thanks! I was looking at that one when I was messing with the runner. Good to know we are on the right track with thinking something was going on with that part!
-
-
Thanks! This is a great post! Very helpful!
-
I added Sudo to the Apt statements in .gitlab-ci.yml. I also added systempart=/dev/mapper/system to the deviceinfo file.
For this part,
https://lucaweiss.eu/post/2023-03-30-retrofit-dynamic-partition/I'm trying to figure out where to add this on github. The code on github is referencing a number of other githubs by "clone." I'm trying to untangle it to get a since of what happens when and where. I want to make sure I'm not missing anything.
-
@atarilinux said in VoLTE Implementation For Google Pixel 3a/3a XL:
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 completedSo....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.)
...snip...
I think this, at the very least, is what you're running into. For one thing, the LLVMgold library isn't referenced correctly by the build system. I was able to correct that but my make skills are simplistic and old and rusty. Am currently looking at a problem with the device tree.
- 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.)
