@fubuntu
To Clarify
FP4 comes with anti rollback protection and it will only trigger if your bootloader is LOCKED.
If your bootloader is UNLOCKED, then anti rollback protection is ignored

From what you read in the /e/OS installation instructions

Caution: The FP4 comes with an anti-rollback feature. (...) If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device.

That is true if you try to relock your bootloader, as in the detail of /e/OS installation instructions caution section

• Rollback protection errors trigger if you install an update whose version number is LESS than the rollback index’s value stored on device.
• (...)
• Rollback protection errors are FATAL when the bootloader is LOCKED.
• Rollback protection errors are IGNORED when the bootloader is UNLOCKED.

In short, if you unlock your bootloader and downgrad your FP4, you won’t trigger anti-rollback protection as long as you don’t relock the bootloader.

Also, you cannot relock your bootloader with Ubuntu Touch installed anyway.

@Keneda It's safe to downgrae FP4 to FPOS11 as long as you don't relock your bootloader. My FP4 came with FPOS13 from the factory, and I successfully downgraded to FPOS11 and install Ubuntu Touch in April 2024. Just DON'T relock your bootloader, as the FP4 will reset get_unlock_ability to 0 after the first FPOS11 boot. If you accidentally relock your bootloader with get_unlock_ability: 0, then there is no way to unlock your bootloader again.

If you want to retain get_unlock_ability: 1 after the downgrade, just don't boot FPOS afterwards. (Source: https://forum.fairphone.com/t/how-do-i-obtain-get-unlock-ability-set-to-1-on-an-unlocked-fairphone-4/105018/4)

As of 4/25, you can now try Lomiri with Ubuntu 24.04 LTS on Ubuntu Unity
They have testing iso for Ubuntu Lomiri 24.04 LTS and comes with installer.

I'm now switch my Surface Go 3 tablet from Debian Sid to Ubuntu Lomiri 24.04 LTS

@Keneda
It should be the same as described in the /e/OS installation instructions for Fairphone FP5 (Especially in the detail of caution section) and the Manage the Bootloader guide. However, I would suggest asking others who have successfully downgraded their FP5 or conducting further research first, as only the FP4 is available in my country (Sadly the sales representative in my country does not introduce FP5), and I cannot test with the FP5.

Regarding get_unlock_ability, I can’t confirm if the FP5 also has this issue where get_unlock_ability resets to 0. However, I would recommend checking this after the downgrade.

said in Waydroid crashes in Desktop Mode over HDMI:

Maybe report to Waydroid on UT first, since the problem seems to be related on Ubuntu Touch system (or lomiri desktop). Does not happened on other distro for phone like Droidian (phosh desktop) or other distro like Ubuntu (GNOME desktop)

Done. I’ve filed a bug report on GitLab. Hopefully, the developers will see it and provide a fix.

said in Waydroid crashes in Desktop Mode over HDMI:

@bbiw said in Waydroid crashes in Desktop Mode over HDMI:

This isn't really a solution

You can try to file this issue to developer, but not sure which one to report? Waydroid, UT, or both?

Maybe report to Waydroid on UT first, since the problem seems to be related on Ubuntu Touch system (or lomiri desktop). Does not happened on other distro for phone like Droidian (phosh desktop) or other distro like Ubuntu (GNOME desktop)

Desktop distro like Ubuntu(not lomiri), Fedora, Arch, etc... are not tested yet because I didn't install Waydroid on those system.

EDIT: Tested on my Surface Go 3 running Ubuntu Lomiri 24.04 LTS. After installed latest Waydroid image. It crashed when moving mouse cursor over to Waydroid window on Lomiri as expected. But if I install ubuntu-desktop (The vanilla Ubuntu desktop which use GNOME) on the same Surface Go 3 and switch to GNOME, Waydroid works perfectly without crashing while moving mouse cursor on Waydroid window. (Thought taps not showing when touch for some reason despite "Show Taps" has been enabled on developer menu, maybe it's GNOME side minor issue?) So the problem seems to be on Lomiri side.

@bbiw said in Waydroid crashes in Desktop Mode over HDMI:

This isn't really a solution

You can try to file this issue to developer, but not sure which one to report? Waydroid, UT, or both?

I'm pretty sure this happened after May 03 update. As I have enabled show taps on developer options. It will crash when I tries to touch anything in Waydroid. And same goes to moving mouse cursor in Waydroid. If I stay on Apr 26 image, it won't crash.

As it turns out. It only seems to happened on Ubuntu Touch system. As I have another device running Droidian. It runs fine with no crash after May 03 update (show taps on developer options enabled). But with another laptop running Ubuntu Lomiri 24.04 (via Ubuntu Unity) with Waydroid installed. After May 03 update. it start crashing again when I hover mouse cursor over Waydroid window.

So I guess the problem seems to be related with Lomiri and Waydroid with show taps enabled or using mouse after May 3 update. And This problem seems happened on all Ubuntu Touch device (Though most user use touchscreen instead of mouse.)

Which platform are you using UBPorts Installer?
If it's on Linux, try with USB2.0 port or USB 2.0 cable.
Or try UBPorts Installer on Windows.

For me, I have the same problem

stuck at "Asserting unlocked bootloader variable".

when reflashing Ubuntu Touch on my FP4 via UBPorts Installer on Ubuntu 20.04/22.04. But I'm pretty sure it used to be working when I flashing Ubuntu Touch first time. They must to be the update (maybe kernel, android-tools or fwupd describe here: https://unix.stackexchange.com/questions/684494/fastboot-recognizes-device-but-unable-to-flash-stuck-with-no-output-on-ubuntu/747584#747584) breaks it. After pinpoint down the problem, it seems to be stuck at fastboot command. Since I have already tries different cable, usb ports, etc...

My solution? by using windows 10/11 to flash Ubuntu Touch via UBPorts Installer. After install the driver, it works out of the box.

@Keneda
It should be the same as described in the /e/OS installation instructions for Fairphone FP5 (Especially in the detail of caution section) and the Manage the Bootloader guide. However, I would suggest asking others who have successfully downgraded their FP5 or conducting further research first, as only the FP4 is available in my country (Sadly the sales representative in my country does not introduce FP5), and I cannot test with the FP5.

Regarding get_unlock_ability, I can’t confirm if the FP5 also has this issue where get_unlock_ability resets to 0. However, I would recommend checking this after the downgrade.

@fubuntu
To Clarify
FP4 comes with anti rollback protection and it will only trigger if your bootloader is LOCKED.
If your bootloader is UNLOCKED, then anti rollback protection is ignored

From what you read in the /e/OS installation instructions

Caution: The FP4 comes with an anti-rollback feature. (...) If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device.

That is true if you try to relock your bootloader, as in the detail of /e/OS installation instructions caution section

• Rollback protection errors trigger if you install an update whose version number is LESS than the rollback index’s value stored on device.
• (...)
• Rollback protection errors are FATAL when the bootloader is LOCKED.
• Rollback protection errors are IGNORED when the bootloader is UNLOCKED.

In short, if you unlock your bootloader and downgrad your FP4, you won’t trigger anti-rollback protection as long as you don’t relock the bootloader.

Also, you cannot relock your bootloader with Ubuntu Touch installed anyway.

@Keneda It's safe to downgrae FP4 to FPOS11 as long as you don't relock your bootloader. My FP4 came with FPOS13 from the factory, and I successfully downgraded to FPOS11 and install Ubuntu Touch in April 2024. Just DON'T relock your bootloader, as the FP4 will reset get_unlock_ability to 0 after the first FPOS11 boot. If you accidentally relock your bootloader with get_unlock_ability: 0, then there is no way to unlock your bootloader again.

If you want to retain get_unlock_ability: 1 after the downgrade, just don't boot FPOS afterwards. (Source: https://forum.fairphone.com/t/how-do-i-obtain-get-unlock-ability-set-to-1-on-an-unlocked-fairphone-4/105018/4)

@Bouleetbil said in Update devel pixel3a:

I find this log into recovery

Have you modify system partition before the update? (E.G. remount system partition as read-write then do some modification on system partition, install package directly to system without using libertine container)

@thedeafenguy said in Libertine on Pixel 3a XL?:

Is there any other workaround to get libertine working?

As far as I know, there isn't any other workaround to get Libertine working. Your Libertine container crashed when entering the second stage (chroot to container):

I: Base system installed successfully:
/usr/sbin/chroot.fakechroot: line 105: 78709 Segmentation fault      env -u FAKECHROOT_BASE_ORIG FAKECHROOT_CMD_ORIG= LD_LIBRARY_PATH="$fakechroot_chrot_paths" FAKECHROOT_BASE="$fakechroot_chroot_base" "$fakechroot_chroot_chroot" "${@:1:$(($fakechroot_chroot_n - 1))}" "${fakechroot_chroot_newroot#$FAKECHROOT_BASE_ORIG}" "${@:$(($fakechroot_chroot_n + 1))}"

I would suggest reflashing the 20.04 stable image via ubports-installer without checking 'Wipe Userdata'. Additionally, you can always change the channel from stable to development or vice versa without losing your data.

While this operation shouldn't erase your data, it's still recommended to back up your data before flashing. You can use TWRP 3.3.1 to back up your data partition to a USB-C drive. If you need to wipe userdata, you can restore the data partition via TWRP after a clean UT flash. I have already done this on both Fairphone 4 and Pixel 3a.

If the problem persists after the reflash or channel change, consider restoring back to the factory Android 9.0 image PQ3B.190801.002 and then flashing UT again. After the clean flash, test immediately to see if Libertine works or not, and then decide whether to restore the data partition.

If Libertine still doesn't work after a clean flash, there may be a bug specific to the Pixel 3a XL. In this case, consider file a bug report to UBports by following the bug reporting process.

I hope this information helps.

@thedeafenguy Is this your fresh 20.04 install, or have you upgrade from 16.04 before?
If you upgraded from 16.04 before, it is recommended to start from fresh due to various changes in 20.04