@atarilinux
It uses android 10 version with a repartitioned super.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.

@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 ?

@Blablub
After extracting the tgzipped MUI ROM, the flash_all.sh script is in the newly created folder.

@Blablub
Yes, you can try flash_all.sh script.
If no error, retry UT installation

@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

@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.

@atarilinux @wally
Maybe you will be interested in Daniel Pratt's tests with T-Mobile in the USA on a Poco X3 NFC ?

https://codeberg.org/EricHeintzmann/UbuntuTouch/issues/23

@chaospredictor
One option I've tested is to use Crackle to install the version of python you want
After that, you can use pip and venv.

Crackle : https://gitlab.com/tuxecure/crackle-apt/crackle

@Futura Pipelines are launched in STEP 2

@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 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 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
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) :

1. on your phone flash stock android 12 ROM - use exactly the same version used by the developer.
2. flash the downloaded .img files with fastboot/fasbootD
3. test and report

@Nocflounder
Correction: acccording to the source code, yes, bonito is supported by the new android 12 port.

https://gitlab.com/ubports/porting/community-ports/android12/google-pixel-3a/google-sargo/-/blob/main/overlay/system/etc/deviceinfo/devices/halium.yaml#L21

Hi @Nocflounder
I’m not 100% sure. It’s better to ask the developer of the new port in the Pixel 3a Telegram group.

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)

@ikoz
true.
The .img files seems a bit outdated.
Not sure the VoLTE/binder qti plugin was stable 8 months ago.
But yes they can be flashed and tested.

@_Joao_
If you cannot find someone who has one, you will have to wait...

• wait for a fix from duckduckgo if they accept to do it. But someone will have to report this issue first.
• or wait for a new morph version. I think Morph Qt6 will fix this issue but i guess it will take several months at least.

@atarilinux
i checked the files in the UBports installer, and it seems that the new port is not (yet ?) supported.
You will need to install the .img files using fastboot/fastbootD.
However, I'm not sure where you can find these .img files or if they even exist. In the worst case, you may need to rebuild them.
I also suggest asking in the Telegram group for the Pixel 3a, as they might have useful insights.
https://t.me/ubports_pixel3a

@_Joao_
A workaround (tested in private mode, but should work in regular mode) is to use a keyboard to connect to duck.ai at first time.
Do you have an USB keyboard (bluetooth should work too) ?

If yes,

1. navigate to duck.ai
2. Pres ŧab several times until you see Give it a try button (partially hidden)
3. Press enter
4. Press tab several times until you see I agree button (partially hidden)
5. Press enter

you should now access to duck.ai