Skip to content

Droidian bookworm (snapshot 25 - March 2023)
Compare
Choose a tag to compare
@github-actions github-actions released this 25 Mar 15:52
· 19 commits to bookworm since this release
droidian/bookworm/25
bd7e4d7

The Droidian project is pleased to announce the release of the 25th snapshot.

Debian bookworm is now in hard freeze, and it's the perfect time to release a new
point-in-time snapshot!

As usual, if you are already running Droidian bookworm there is no need to reflash.

We want to thank everyone who has been running Droidian bookworm for the
past few months.

Highlights

  • Based on Debian 12 bookworm, with Mobian repositories on top
    • GNOME 43 (except some non-essential packages)
    • phoc 0.25.2
    • phosh 0.25.2
    • squeekboard 1.21.0
  • Google Pixel 3a returns to the official builds roster
  • Halium 11: Enabled camera stack
  • Fixed HW acceleration in WebKitGtk+ apps
  • Fixed Flutter apps
  • Fixed keyring unlock at login
  • Multiple display support is now available for everyone, provided the device itself supports it
  • Numerous bug fixes and improvements through the whole stack

Supported devices

These devices are officially supported by Droidian:

  • F(x)tec Pro1 (qx1000) - fastboot-flashable, recovery-flashable
  • F(x)tec Pro1-X (qx1050) - fastboot-flashable
  • Google Pixel 3a/3a XL (sargo, bonito) - fastboot-flashable
  • Sony Xperia 5 (bahamut) - fastboot-flashable, recovery-flashable

The following previously supported device is unmantained, and is not
part of the new unified build system introduced with the last snapshot:

  • Volla Phone (yggdrasil)

You can still get the adaptation bundle for this device from the legacy
rootfs-api28gsi-all repository: https://github.com/droidian-images/rootfs-api28gsi-all/releases/tag/nightly

Please note that that adaptation is untested, and no support will be
provided.

Known issues

Generic

Onboarding process issues

The initial set-up wizard doesn't fit well with the small mobile phone screens. The user
should also reboot the device to load the eventual new locale configuration.

This will be fixed in a later release

Unable to add Google account from the Settings app

The Google Account login page doesn't allow text input. The only known
workaround for now is to press the "Next" button and then insert the account
credentials via the clipboard.

Broken sensors

Due to a configuration issue, the sensorfwd daemon doesn't detect any
sensor. This has been already rectified, and a System Update will put
things in place.

Older installations aren't affected.

F(x)tec Pro1

Encryption unlock UI doesn't rotate

The encryption unlock UI doesn't rotate if the keyboard has been opened.
It's still possible to enter the unlock passphrase via the physical keyboard.

Keyboard backlight disabled in encryption unlock UI

The keyboard backlight is disabled in the encryption unlock UI.

F(x)tec Pro1-X

Haptic feedback slow to appear

In some circumstances, it has been observed that it might take ~1 and a half minute
for haptic feedback to start working after a fresh boot.

Unstable camera stack

The camera stack in the Droidian side is unstable and it might take some tries to properly
load. We're looking at ways to fix this.

Encryption unlock UI doesn't rotate

The encryption unlock UI doesn't rotate if the keyboard has been opened.
It's still possible to enter the unlock passphrase via the physical keyboard.

Slow offline slot switch

During offline kernel updates (i.e. triggered via the Software app), the device
might take some minutes to reboot after doing a "slot switch". When this happens,
the display stays black until it eventually reboots.

In this case, it's possible to trigger an hard reboot by pressing Vol-Down and Power.

Google Pixel 3a and 3a XL

Full-disk encryption is not supported

The sargo port doesn't support full-disk encryption at the moment.

Sony Xperia 5

Slow offline slot switch

During offline kernel updates (i.e. triggered via the Software app), the device
might take some minutes to reboot after doing a "slot switch". When this happens,
the display stays black until it eventually reboots.

In this case, it's possible to trigger an hard reboot by pressing Vol-Up and Power.

Assets 21
Loading