@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

Posts
-
RE: VoLTE Implementation For Google Pixel 3a/3a XL
-
RE: VoLTE Implementation For Google Pixel 3a/3a XL
@AetheralMeowstic
in the new halium 12 port for sargo and bonito, VoLTE is configured, yes, but the port is not finalized. -
RE: VoLTE Implementation For Google Pixel 3a/3a XL
@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
-
RE: Partition not found error
@isidroarias
It looks like this error : https://forums.ubports.com/post/87147I suggest to reflash android 10 to restore all partitions (do not relock the bootloader).
Then reinstall Ubuntu Touch. -
RE: VoLTE Implementation For Google Pixel 3a/3a XL
- You have a retro-fitted super partition
- You have images
- You have the procedure to flash images in retro-fitted super partition : https://source.android.com/docs/core/architecture/bootloader/fastbootd#dynamic-partitions
What else ?
-
RE: VoLTE Implementation For Google Pixel 3a/3a XL
@atarilinux
AFAIK, these devices use a super partition, but not a retro-fitted one.
But, I don't think the build system is aware of the partition type. -
RE: VoLTE Implementation For Google Pixel 3a/3a XL
@atarilinux
I see same errors (cp and losesetup) in other ports.
For example:here's an example of flashing devel images on a device with a super partition :
https://gitlab.com/EricHeintzmann/ubuntu-touch/xiaomi-surya/-/wikis/fastboot-flashAbout fastbootd :
https://source.android.com/docs/core/architecture/bootloader/fastbootd -
RE: Ubuntu Touch 24.04, VoLTE, and Devices in the US
@atarilinux
It uses android 10 version with a repartitionedsuper.img
For more details : https://github.com/ubuntu-touch-surya/ubuntu-touch-surya/releases/tag/stable-repartition
About pixel 3a android 12 partitionning, i don't know.
-
RE: install ubutu touch on pocco x3 failed
@MrT10001
In order to update the installation guide, what are the requirements to install UT on poco X3 from windows 11 ?
Latest version of fastboot/adb ? Drivers ?
Where to download them ? -
RE: install ubutu touch on pocco x3 failed
@Blablub
After extracting the tgzipped MUI ROM, the flash_all.sh script is in the newly created folder. -
RE: install ubutu touch on pocco x3 failed
@Blablub
Yes, you can tryflash_all.sh
script.
If no error, retry UT installation -
RE: install ubutu touch on pocco x3 failed
@Blablub
The issue is probably due to the partition not found (in your first error).
I suggest to reflash android 10 with miaomi flash tool to restore all partitions (do not relock the phone).
Then reinstall Ubuntu Touch -
RE: install ubutu touch on pocco x3 failed
@Blablub
MIUI surya_global_images_V12.0.9.0.QJGMIXM is the correct android 10 version to use.Please take a look at troubleshooting section of https://forums.ubports.com/topic/10392/ubuntu-touch-installation-guide-for-xiaomi-poco-x3-nfc-x3
Some users report that they have not been able to install Ubuntu Touch from Windows (10 & 11), but that they have been able to do so with Linux.
-
RE: Ubuntu Touch 24.04, VoLTE, and Devices in the US
@atarilinux @wally
Maybe you will be interested in Daniel Pratt's tests with T-Mobile in the USA on a Poco X3 NFC ? -
RE: venv installation
@chaospredictor
One option I've tested is to useCrackle
to install the version of python you want
After that, you can use pip and venv. -
RE: VoLTE Implementation For Google Pixel 3a/3a XL
@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. -
RE: VoLTE Implementation For Google Pixel 3a/3a XL
@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)
-
RE: VoLTE Implementation For Google Pixel 3a/3a XL
@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.htmlOr...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.
-
RE: VoLTE Implementation For Google Pixel 3a/3a XL
@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
- click on