What's going on with Snaps on Ubuntu Touch?
summary
Halium-based Android devices require vendor blobs, a Halium initramfs boot path and an LXC Generic Halium image that runs Android userspace inside Linux; supporting Snaps needs AppArmor, squashfs, cgroup v2, CONFIG_VT and CONFIG_SYSVIPC enabled in the vendor kernel and kernel-ABI padding for module reuse. snapd is patched to set up libhybris environments and pass mounts; binder IPC and an LD_PRELOAD TLS padding hack are used for graphics. Gadget snaps cannot yet build Android boot images; a snappi proof‑of‑concept is proposed and partially implemented but full device support still needs device‑maintainer kernels and per‑device overlays.
AI-written summary · about
chapters (7)
- 0:00Introduction and agenda
- 1:05Architecture and kernel
- 6:46Early boot processes
- 9:20Halium and hardware support
- 14:46Libhybris and system integration
- 18:05Snapd and app integration
- 21:05The future of all-snap
related talks
24mtalks Ubuntu Core on Dragonboard 410c
25mkeynote – Jane Silber
42mARM64 Linux Laptops Status Report
26mMy Journey from early Linux through Snap packaging to WSL
42mLLVMLinux: Compiling Android with LLVM
27mAn Ubuntu for a 10 ton steel press and your window shades
43mAndroid Internals for Developers
37mRunning Android on the Mainline Graphics Stack