Droidian bookworm (snapshot 24 - 2022-08-04)
The Droidian project is pleased to announce the release of the 24th snapshot.
This release comes after 9 months since the last one, and is the first
being based on Debian 12 bookworm
.
Since late last year, nightlies have switched to bookworm
. This release
is just a point-in-time snapshot of a known good state. 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 42 (except some non-essential packages)
- phoc 0.10.0
- phosh 0.17.0
- squeekboard 1.16.0
- Experimental Halium 11 support
- New unified image build system
- Support for the creation of flashboot-flashable images
- Two new official supported devices: F(x)tec Pro1-X and Sony Xperia 5
- Opt-in, online full disk encryption
- Support for devices shipping with a
super
partition - Many bugfixes 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
- Sony Xperia 5 (bahamut) - fastboot-flashable, recovery-flashable
The following previously supported devices are unmantained, and are not
part of the new unified build system:
- Google Pixel 3a (sargo)
- Volla Phone (yggdrasil)
You can still get adaptation bundles for these two devices from the legacy
rootfs-api28gsi-all repository: https://github.com/droidian-images/rootfs-api28gsi-all/releases/tag/nightly
Please note that those adaptations are untested, and no support will be
provided.
Known issues
Generic
Gnome keyring woes
The initial startup creates a broken, not-unlockable, login
keyring.
You can remove it with the following command:
rm -f .local/share/keyrings/login.keyring
Whenever an application will try to unlock the keyring again, you will
be prompted to create one from scratch.
Unable to add online accounts from the Settings application
This is unfortunately an issue of the new gnome-control-center
paired
with the older wlroots
we are currently shipping.
You can workaround for now by running the Settings app via XWayland:
env GDK_BACKEND=x11 GSK_RENDERER=cairo gnome-control-center
KDE/Qt apps
This is not an issue per se, but due to how Qt is packaged in Debian, Qt
apps will not pull in the required wayland
platform abstraction.
This can be installed manually via
sudo apt install qtwayland5
Some devices might have trouble in running recent KDE/Qt apps. Installing
a patched version of libhybris might help:
sudo -i
cat > /etc/apt/sources.list.d/droidian-libhybris-testing.list <<EOF
deb http://droidian-libhybris.repo.droidian.org/bookworm-libui-gralloc-eglcreateplatformwindowsurface/ bookworm main
EOF
apt update
apt dist-upgrade
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.
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.
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.