@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

It is possible to obtain a list of all devices in devel where VoLTE is enabled by conducting a search on Gitlab :

https://gitlab.com/search?group_id=54262841&scope=blobs&search=OfonoImplementsIms%3A+true&page=1

@uxes said in Working VoLTE reports, share your experience:

after some months of using, i know that after start using volte, 4G internet sometimes stop working, maybe after call/sms only thing that helps is to disable/enable data in indicators (no reboot required)
Eric from poco reported that adding new APN may help

For those interested in activating VoLTE on the Poco X3, here are the steps I followed:

• After enabling VoLTE, I noticed errors in the logs related to context 1 of ofono. To address this, I replaced this context with a new APN "Internet & MMS" using the commands available in /usr/share/ofono/scripts/.
• I also removed an unused connection using ncli connection.

While I can't guarantee that these modifications are the solution, I haven't encountered any issues since.

It's important to note that after exiting airplane mode, the poco often struggles to reconnect to VoLTE without a reboot.

@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

Hi @Jules

Have you tried to reset your APNs in System Settings?

@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=heads

deviceinfo_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

Xiaomi POCO X3 NFC (surya)
focal 20.04 devel (r581)
France, SFR

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

@snailc
The 12.5.9 global MIUI is available at http://xmfirmwareupdater.com/miui/vayu/stable/V12.5.9.0.RJUMIXM/

The fastboot error is probably because of system is a logical partition and you need to use fastbootD.

fastboot reboot fastboot
fastboot flash system ubuntu.img

@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

Hello,

Will it be possible to use the Alfred's browser engine instead of QtWebengine to create webapps for UT ?

Thanks

@mr_growl
Iirc, an android 12 phone must have a recovery partition unless it is a slot A/B device.

for example on my device

• to check recovery partition

  $ fastboot getvar all |& grep -i recovery
  (bootloader) partition-type:recovery:raw
  (bootloader) partition-size:recovery: 0x8000000
  

• to flash recovery partition

  fastboot flash recovery recovery.img
  

• to check slots, in fastbootD mode

  $ fastboot getvar slot-count
  slot-count: 0
  

If there is no recovery partition on your phone, you probably need a recovery ramdisk.
See ramdisk-overlay directory on Volla X23 for example:
https://gitlab.com/ubports/porting/reference-device-ports/halium12/volla-x23/volla-vidofnir/-/tree/main

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

The recovery doesn't work after flashing.

To make sure to understand

• is there a recovery partition on the android 12 pixel 3a ?
• or can't you boot in recovery mode with something like that : fastboot boot recovery.img

(building ubports recovery.img has to be enabled in device info)

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

nothing ususual in dmesg

pstore (console + ram) and last_kmsg should be enabled in your kernel config, then you will be able after a boot attempt, to get logs from either console-ramoops or last_kmsg in recovery mode.

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

I do not. It just sits at the bootloader.

It s expected. Doc says When your device boots it will likely stay at the bootloader screen.

@mr_growl
Don't you see messages about console ?
For example opening console: no such device

@mr_growl
If I had a pixel 3a, I'll try very quickly to flash/push Alfred's artifacts, and see the dmesg output.

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

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

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