Offline
@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
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
@mr_growl said in VoLTE Implementation For Google Pixel 3a/3a XL:
Might just go back a step and try getting a halium 9 build working
The full system method will be discouraged/deprecated very soon
https://gitlab.com/ubports/docs/docs.ubports.com/-/merge_requests/675
@mr_growl
I think halium 12 is required for VoLTE.
according to the porting doc and the history of the porting group, without the systempart option you have to
adbadb shell mount /data; adb push ubuntu.img /data/
@mr_growl
Accordind to the deviceinfo file in your repo, you set systempart, thus you need to flash boot.img to boot and system.img to system (fastbootD might be needed).
And maybe flashing dtbo.img to dtbo is needed too...
Have you access to Telegram? You will find help in the group linked in the porting documentation.
@mr_growl said in VoLTE Implementation For Google Pixel 3a/3a XL:
New Build Method
It seems you used the standalone kernel method.
Then to install to your phone, you have to apply the process described in Building, installing and running
The 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.
About vendor blobs, in your case, they are already installed in a separate partition by android/lineage. UT will find this partition automatically (if you have not modified it)
@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
@_Joao_
I tested again, with Morph, under UT 24.04-1.X and duck.ai works.
@ds2k5
A workaround is to install Waydroid Helper app with OpenStore, and use Waydroid Stop.
@Jules
All I can suggest is first to send an SMS and then look in the logs if you see something that can help us understand what's going on.
journalctl -u ofono.service -r --no-hostname
Hi @Jules
Have you tried to reset your APNs in System Settings?
@lduboeuf said in Call for testing: Ubuntu Touch 24.04-1.0:
Don't worry, we will remove that popup for now.
thanks
@peat_psuwit said in Call for testing: Ubuntu Touch 24.04-1.0:
My understanding is that Ubuntu Touch now have a facility to retry retrieving MMS if downloading fails. So, in that case, you should get a notification, after which you can disable Wi-Fi and retry retrieving MMS (@lduboeuf please correct me on this if I'm wrong).
OK. I will test and report.
@peat_psuwit said in Call for testing: Ubuntu Touch 24.04-1.0:
You should not have to uninstall applications; once all applications are updated, you should be offered release upgrade. This is intentional, as many times application and system updates can solve compatibility issues with the new release before the new release is being upgraded to.
Got it.
I forgot to mention it, but first I tried to update these applications.
But, I don't know why, it failed, and the only solution I then found was to uninstall them.