Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion device/bluejay/NOTES.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,12 @@ The question the notes left open, and that the maintainer wants settled before a

From a retail 6a, read-only, before anything is written (CONTRIBUTING §5.1 first): `getvar all` (product, slot state, the partition list and sizes, `hw-revision`), `ro.boot.dtbo_idx`, the build id and security patch; with root or `bin/omamobile capture`, the live DT (which `soc_id`, `/chosen/bootargs`, every `reserved-memory` region against `/proc/iomem`). Post facts, never the files. Then the board DTS's DTB in a kernel build (`DEVICE=bluejay bin/omamobile images`, which now adds `boot`'s footer), the oriole initramfs path, and a human at the phone with the way back to slot A.

## 2026-11-02: the device package, 0.1.0, built but not run (no phone)

- **`packages/omamobile-device-bluejay` 0.1.0 is the package `device.conf` names.** It is felix's first-light shape without the fold's lid and cover-touch parts, plus the suspend-to-idle drop-in: the storage udev rule, the usb0 address with USB as the last gateway, NetworkManager off usb0, logind ignoring the power key, `[Sleep]` on s2idle with no hibernation, the `[omamobile]` mirrorlist and pacman hook, `reboot-to` and a copy of the descriptor; `provides`/`conflicts=(omamobile-device)` and `depends` on `omamobile-keyring`, so `tools/build-rootfs` can build a 6a image with the repository configured. It enables no service, ships no modprobe policy and no `omamobile-bootctl` (marking slot B on the gs101 phones is on hold, [#252](https://github.com/derekross/omarchy-mobile/issues/252)), so `bin/omamobile initramfs` builds its freestanding helpers, as for oriole.
- **Why the sleep drop-in** [V]: raven's firmware advertises PSCI SYSTEM_SUSPEND, so the kernel offers `deep`, and Linux has no gs101 sleep sequence, so the phone doesn't wake from it ([raven's package](../../packages/omamobile-device-raven/vendor/systemd/sleep.conf.d/10-omamobile.conf), device/raven/SUSPEND-PLAN.md). Bluejay's `/chosen/bootargs` (kernel #179) don't set `mem_sleep_default=s2idle`, as oriole's don't, so the file is what keeps `systemctl suspend` on s2idle; the maintainer asked for it in the kernel #179 review. The file is raven's, byte for byte, and the package's test checks it.
- **What was checked** [V]: `test/all` (every copied file against cheetah's or raven's, the descriptor against `device/bluejay/device.conf`, no register write or probe in it, the staged tree with nothing that marks a slot, loads a driver or starts hardware) and `tests/packages`, on the laptop. Not checked: a build with `makepkg` on aarch64, an install on a 6a, and `tools/phone-smoke`, which wait for the first boot.

## 2026-11-01: stage 0, part 1: facts from Google's GPL device trees (no phone, no factory image)

### Base DTB and `soc_id`
Expand Down Expand Up @@ -160,7 +166,7 @@ The descriptor carries no comments; this table is its provenance.
| --- | --- | --- | --- |
| `CODENAME`, `NAME`, `SOC` | bluejay, Pixel 6a, gs101 | [V] | G/, the kernel binding |
| `COMPATIBLE` | `google,gs101-bluejay` | [V] | the first-light DTS and its binding entry |
| `PACKAGE` | `omamobile-device-bluejay` | the package doesn't exist yet; `bin/omamobile initramfs` falls back when its `omamobile-bootctl.c` is missing, as for oriole | |
| `PACKAGE` | `omamobile-device-bluejay` | [V] | [`packages/omamobile-device-bluejay`](../../packages/omamobile-device-bluejay) 0.1.0 (2026-11-02 above); it has no `omamobile-bootctl.c`, so `bin/omamobile initramfs` builds its freestanding helpers, as for oriole |
| `DTB` | `exynos/google/gs101-bluejay.dtb` | [V] | the Makefile line in [kernel #179](https://github.com/derekross/linux-omarchy-mobile/pull/179), merged; `DEVICE=bluejay bin/omamobile images` builds from a kernel after it |
| `SOC_IDS` | `b0:0x9845001 a0:0x9845000` | [V] | S/ `gs101-b0.dts`, `gs101-a0.dts` |
| `DTBO_SOURCE`, `DTBO_BOARD_ID`, `DTBO_BOARD_REV` | the empty overlay, 0x20506, 0x10000 | [V] for the MP 1.0 entry (index 9 of stock's `dtbo.img`), [I] that retail boots it | G/ `gs101-bluejay-mp1_0.dts`; F/ `dtbo.img` (2026-11-02) |
Expand Down
2 changes: 1 addition & 1 deletion docs/DEVICES.md
Original file line number Diff line number Diff line change
Expand Up @@ -71,7 +71,7 @@ Devices we'd like to support, with the closest starting point. Open an issue to
| Pixel Tablet | tangorpro | gs201 | as panther; no modem |
| Pixel 6 | oriole | gs101 | **WIP, community port: [#2](https://github.com/derekross/omarchy-mobile/issues/2)**; our preferred second device. Upstream mainline `gs101-oriole.dts` |
| Pixel 6 Pro | raven | gs101 | upstream mainline `gs101-raven.dts`; shares oriole's port ([#2](https://github.com/derekross/omarchy-mobile/issues/2)). Boots our kernel from slot B to Omarchy's Hyprland on the Mali-G78 ([kernel #2](https://github.com/derekross/linux-omarchy-mobile/pull/2), [#3](https://github.com/derekross/linux-omarchy-mobile/pull/3)); its device package and plans ([#41](https://github.com/derekross/omarchy-mobile/pull/41)) and provisioning tools ([#22](https://github.com/derekross/omarchy-mobile/pull/22)) are merged |
| Pixel 6a | bluejay | gs101 | **WIP, community port: [#348](https://github.com/derekross/omarchy-mobile/issues/348)**; persistent Arch/Omarchy desktop on a development kernel ([notes](../device/bluejay/NOTES.md)); polling touch ([kernel #229](https://github.com/derekross/linux-omarchy-mobile/pull/229)), station Wi-Fi ([#227](https://github.com/derekross/linux-omarchy-mobile/pull/227), [#228](https://github.com/derekross/linux-omarchy-mobile/pull/228), [#230](https://github.com/derekross/linux-omarchy-mobile/pull/230)) and Panfrost GPU are development-kernel results, not release support; display is retained simpledrm, native panel modesetting unqualified; source/reproduction limits in [UPSTREAM](../device/bluejay/UPSTREAM.md) |
| Pixel 6a | bluejay | gs101 | **WIP, community port: [#348](https://github.com/derekross/omarchy-mobile/issues/348)**; persistent Arch/Omarchy desktop on a development kernel ([notes](../device/bluejay/NOTES.md)); polling touch ([kernel #229](https://github.com/derekross/linux-omarchy-mobile/pull/229)), station Wi-Fi ([#227](https://github.com/derekross/linux-omarchy-mobile/pull/227), [#228](https://github.com/derekross/linux-omarchy-mobile/pull/228), [#230](https://github.com/derekross/linux-omarchy-mobile/pull/230)) and Panfrost GPU are development-kernel results, not release support; display is retained simpledrm, native panel modesetting unqualified; source/reproduction limits in [UPSTREAM](../device/bluejay/UPSTREAM.md); its device package 0.1.0, nothing enabled, is in review ([#346](https://github.com/derekross/omarchy-mobile/pull/346)) |
| Pixel 8, 8 Pro, 8a | shiba, husky, akita | zuma (Tensor G3) | **WIP, community port: [#1](https://github.com/derekross/omarchy-mobile/issues/1)**. 8 Pro (husky): WIP, in the matrix above; its device package and UFS plan are merged ([#42](https://github.com/derekross/omarchy-mobile/pull/42)), and its bootloader picks the base DTB by `/soc_compatible`, not `/soc_id`. 8a (akita): stage 0 stock facts and a descriptor from a retail phone ([notes](../device/akita/NOTES.md)); this phone's bootloader picks the IPOP base DTB where husky's picks FOPLP. WIP, in the matrix above: the first-light board file is merged ([kernel #192](https://github.com/derekross/linux-omarchy-mobile/pull/192)) and boots from slot B with USB networking, SSH and the framebuffer console ([BRINGUP-M1](../device/akita/BRINGUP-M1.md)); UFS is merged too ([kernel #206](https://github.com/derekross/linux-omarchy-mobile/pull/206)), and the device package with its storage plan is in review ([#456](https://github.com/derekross/omarchy-mobile/pull/456)) |
| Pixel 9 family | tokay, caiman, komodo, comet, tegu | zumapro (Tensor G4) | 9a (tegu): in the matrix above; its SoC and board device tree is merged ([kernel #81](https://github.com/derekross/linux-omarchy-mobile/pull/81)), with the rest of its kernel work merging into linux-omarchy-mobile; tracking [#28](https://github.com/derekross/omarchy-mobile/issues/28) |
| Pixel 10 family | mustang (10 Pro XL) | laguna (Tensor G5) | 10 Pro XL (mustang): stage 0 stock facts ([notes](../device/mustang/NOTES.md)), contributors welcome ([#18](https://github.com/derekross/omarchy-mobile/issues/18)) |
Expand Down
21 changes: 21 additions & 0 deletions packages/omamobile-device-bluejay/LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2026 Derek Ross

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
26 changes: 26 additions & 0 deletions packages/omamobile-device-bluejay/PKGBUILD
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
# SPDX-License-Identifier: MIT
pkgname=omamobile-device-bluejay
pkgver=$(cat "${startdir:-.}/version")
pkgrel=1
pkgdesc="Omarchy Mobile support for the Google Pixel 6a (bluejay): storage guard, USB networking, power key and suspend-to-idle"
arch=(aarch64)
url="https://github.com/derekross/omarchy-mobile"
license=(MIT)
depends=(bash systemd omamobile-keyring)
provides=(omamobile-device)
conflicts=(omamobile-device)
backup=(etc/pacman.d/omamobile-mirrorlist)
install=omamobile-device-bluejay.install
makedepends=(gcc)

build() {
"$startdir/build" "$srcdir/build"
}

check() {
"$startdir/test/all"
}

package() {
"$startdir/install" "$pkgdir" "$srcdir/build"
}
22 changes: 22 additions & 0 deletions packages/omamobile-device-bluejay/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
<!-- SPDX-License-Identifier: MIT -->
# omamobile-device-bluejay

Omarchy Mobile's first userspace package for the Google Pixel 6a (codename bluejay, Tensor / gs101), the package `device/bluejay/device.conf` names. It hides the Android partitions from desktop tools, holds the USB address, keeps suspend on suspend-to-idle, and gives pacman the same `[omamobile]` repository as the Pixel 7 Pro. It does not drive the radio, the charger, or a camera, it enables no service, it loads no driver, and it does not mark a boot slot successful.

**No Pixel 6a has run it.** Its board DTS ([kernel #179](https://github.com/derekross/linux-omarchy-mobile/pull/179)) is merged without a boot, and this package follows the same way: every file is a copy of one that runs on the Pixel 6 Pro (raven, the same SoC) or the Pixel 7 Pro, and `test/all` checks the copies. The first boot's `tools/phone-smoke` report goes to [issue #348](https://github.com/derekross/omarchy-mobile/issues/348), the 6a's own thread, and [device/bluejay/NOTES.md](../../device/bluejay/NOTES.md).

| Path | Installs to | What it does |
| --- | --- | --- |
| `vendor/udev/rules.d/10-omamobile-storage.rules` | `/usr/lib/udev/rules.d` | Hides `sda` and every Android partition except `userdata` from desktop tools. Same rule as the Pixel 7 Pro. The initramfs stops its guard loop before `switch_root`; the kernel's read-only flags are what remain |
| `vendor/systemd/network/20-usb-gadget.network` | `/usr/lib/systemd/network` | Sets usb0 to 172.16.42.1/24 after handover, as the last gateway. A replug may need a reboot: this package does not close the Type-C chip's USB2 switch again (raven's package does for its MAX77759, through a service; the 6a's chip, bus and address are unread) |
| `vendor/systemd/logind.conf.d/10-omamobile-power-key.conf` | `/usr/lib/systemd/logind.conf.d` | A short power press does not power the phone off. Same drop-in as the Pixel 7 Pro. The long press stays the PMIC reset |
| `vendor/systemd/sleep.conf.d/10-omamobile.conf` | `/usr/lib/systemd/sleep.conf.d` | Suspend means suspend-to-idle: the firmware advertises PSCI SYSTEM_SUSPEND, so the kernel offers `deep`, but Linux has no gs101 sleep sequence and the Pixel 6 Pro doesn't wake from it. No hibernation. Same drop-in as the Pixel 6 Pro package; bluejay's bootargs don't set `mem_sleep_default`, as oriole's don't, so this file is what keeps a `systemctl suspend` on s2idle |
| `vendor/NetworkManager/conf.d/10-omamobile-usb.conf` | `/usr/lib/NetworkManager/conf.d` | Keeps NetworkManager off that link |
| `etc/omamobile-mirrorlist` | `/etc/pacman.d/omamobile-mirrorlist` | Where pacman finds the `[omamobile]` repository. Same file as the Pixel 7 Pro package |
| `omamobile-device-bluejay.install` | pacman hook | Adds `[omamobile]` to `pacman.conf` before `[omarchy]`, once. Same script as the Pixel 7 Pro package |
| `src/reboot-to.c` | `/usr/bin/reboot-to` | Reboot with a reason the bootloader understands. On a first boot the reason most likely isn't stored: the descriptor lists no `INITRAMFS_MODULES`, and raven's records that without its PMIC and reboot-mode modules `reboot-to bootloader` just boots slot B again, so fastboot is by the buttons. Same bytes as the Pixel 7 Pro package; the test checks |
| `device.conf` | `/usr/share/omamobile/device.conf` | The descriptor, the same bytes as `device/bluejay/device.conf` |

`./build [DIR]` compiles `reboot-to` from this directory, `./install DESTDIR [DIR]` stages the files, and `test/all` checks the copies when it is run from the repository.

Not in this package: `omamobile-bootctl` and the boot-success marker (marking slot B on the gs101 phones is on hold, [#252](https://github.com/derekross/omarchy-mobile/issues/252); without the source, `bin/omamobile initramfs` builds its freestanding helpers, as for oriole), the USB rescue, Wi-Fi, the charger, haptics, the display's module options, cameras, any modprobe blacklist, and the slot-B image hook. Each comes in when a booted 6a has given it a runbook and the evidence.
7 changes: 7 additions & 0 deletions packages/omamobile-device-bluejay/build
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
#!/bin/bash
# SPDX-License-Identifier: MIT
set -euo pipefail
cd -- "$(dirname -- "${BASH_SOURCE[0]}")"
out=${1:-build}
mkdir -p "$out"
${CC:-cc} ${CFLAGS:--O2} -Wall -Wextra -o "$out/reboot-to" src/reboot-to.c ${LDFLAGS:-}
22 changes: 22 additions & 0 deletions packages/omamobile-device-bluejay/device.conf
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# SPDX-License-Identifier: MIT
CODENAME=bluejay
NAME="Pixel 6a"
SOC=gs101
COMPATIBLE="google,gs101-bluejay"
PACKAGE=omamobile-device-bluejay
DTB=exynos/google/gs101-bluejay.dtb
SOC_IDS="b0:0x9845001 a0:0x9845000"
DTBO_SOURCE=bluejay-m1-overlay.dts
DTBO_BOARD_ID=0x20506
DTBO_BOARD_REV=0x10000
VENDOR_CMDLINE="console=tty0 earlycon=exynos4210,0x10A00000 clk_ignore_unused pd_ignore_unused printk.devkmsg=on bootconfig"
VENDOR_PAGESIZE=0x800
OS_VERSION=17.0.0
OS_PATCH_LEVEL=2026-10
AVB_FOOTERS="boot:0x4000000"
AVB_ROLLBACK_INDEX=1791158400
AVB_SECURITY_PATCH=2026-10-05
BOOT_IMAGES="boot vendor_boot dtbo"
UFS_RW="boot_b vendor_boot_b dtbo_b userdata"
INITRAMFS_INIT=/initramfs/init
PANEL_SIZE=1080x2400
18 changes: 18 additions & 0 deletions packages/omamobile-device-bluejay/etc/omamobile-mirrorlist
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# SPDX-License-Identifier: MIT
# Where pacman gets Omarchy Mobile's packages ([omamobile] in /etc/pacman.conf).
#
# The one active Server line is the channel this phone follows:
# stable what has run on the Pixel 7 Pro; phones installed from a
# release follow it
# development every day's build, first; for builders and testers
# local the repository on the phone itself, /var/lib/omamobile/repo,
# filled from a build machine by tools/repo-push
#
# Switch with: sudo omamobile-update channel development (or stable, local)
# See which: omamobile-update check
#
# pacman keeps a changed copy of this file across upgrades (backup= in the
# device package); a new default then arrives as omamobile-mirrorlist.pacnew.
Server = https://pkgs.omamobile.org/stable/$arch
#Server = https://pkgs.omamobile.org/development/$arch
#Server = file:///var/lib/omamobile/repo/$arch
24 changes: 24 additions & 0 deletions packages/omamobile-device-bluejay/install
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
#!/bin/bash
# SPDX-License-Identifier: MIT
set -euo pipefail
cd -- "$(dirname -- "${BASH_SOURCE[0]}")"
destination=${1:?Usage: ./install DESTDIR [BUILDDIR]}
build=${2:-build}
[[ $destination == /* && $destination != "/" ]] || { echo "Use an absolute staging directory" >&2; exit 1; }
install -Dm755 "$build/reboot-to" "$destination/usr/bin/reboot-to"
install -Dm644 vendor/udev/rules.d/10-omamobile-storage.rules \
"$destination/usr/lib/udev/rules.d/10-omamobile-storage.rules"
install -Dm644 vendor/systemd/network/20-usb-gadget.network \
"$destination/usr/lib/systemd/network/20-usb-gadget.network"
install -Dm644 vendor/systemd/logind.conf.d/10-omamobile-power-key.conf \
"$destination/usr/lib/systemd/logind.conf.d/10-omamobile-power-key.conf"
install -Dm644 vendor/systemd/sleep.conf.d/10-omamobile.conf \
"$destination/usr/lib/systemd/sleep.conf.d/10-omamobile.conf"
install -Dm644 vendor/NetworkManager/conf.d/10-omamobile-usb.conf \
"$destination/usr/lib/NetworkManager/conf.d/10-omamobile-usb.conf"
install -Dm644 device.conf \
"$destination/usr/share/omamobile/device.conf"
install -Dm644 etc/omamobile-mirrorlist \
"$destination/etc/pacman.d/omamobile-mirrorlist"
install -Dm644 LICENSE "$destination/usr/share/licenses/omamobile-device-bluejay/LICENSE"
install -Dm644 version "$destination/usr/share/omamobile/device-bluejay/version"
62 changes: 62 additions & 0 deletions packages/omamobile-device-bluejay/omamobile-device-bluejay.install
Original file line number Diff line number Diff line change
@@ -0,0 +1,62 @@
# SPDX-License-Identifier: MIT
# Add the [omamobile] repository to pacman.conf, before [omarchy] so its
# builds (e.g. Mesa with Mali-G710 support) win. Added once; never removed
# automatically, so a user's edits stay.
add_repository() {
local conf=/etc/pacman.conf
grep -q '^\[omamobile\]' "$conf" && return
local entry='[omamobile]\nInclude = /etc/pacman.d/omamobile-mirrorlist\n'
if grep -q '^\[omarchy\]' "$conf"; then
sed -i "0,/^\[omarchy\]/s//${entry//\//\\/}\n[omarchy]/" "$conf"
elif grep -q '^\[core\]' "$conf"; then
sed -i "0,/^\[core\]/s//${entry//\//\\/}\n[core]/" "$conf"
else
printf '\n[omamobile]\nInclude = /etc/pacman.d/omamobile-mirrorlist\n' >>"$conf"
fi
}

# --- the [omamobile] channel (identical in every device package) ---
# The mirrorlist names the channel (stable, development or local). It is a
# backup= file, so pacman keeps a changed copy; an unchanged one, though, is
# replaced by the new default. Phones from before 2026-11-01 read the
# repository on the phone (file:///var/lib/omamobile/repo, filled by
# tools/repo-push), unchanged, and would silently move to stable: such a phone
# keeps reading its own repository, and is told how to switch.
OMAMOBILE_MIRRORLIST=/etc/pacman.d/omamobile-mirrorlist
OMAMOBILE_LOCAL_MARK=/var/lib/omamobile/.mirrorlist-was-local
OMAMOBILE_LOCAL_SERVER='Server = file:///var/lib/omamobile/repo/$arch'

remember_local_channel() {
[[ -f $OMAMOBILE_MIRRORLIST ]] || return 0
if grep -qxF "$OMAMOBILE_LOCAL_SERVER" "$OMAMOBILE_MIRRORLIST"; then
mkdir -p "${OMAMOBILE_LOCAL_MARK%/*}" && : > "$OMAMOBILE_LOCAL_MARK"
fi
}

keep_local_channel() {
[[ -e $OMAMOBILE_LOCAL_MARK ]] || return 0
rm -f "$OMAMOBILE_LOCAL_MARK"
[[ -f $OMAMOBILE_MIRRORLIST ]] || return 0
grep -qxF "$OMAMOBILE_LOCAL_SERVER" "$OMAMOBILE_MIRRORLIST" && return 0
# Comment out every Server line, then turn the local one back on
sed -i -E 's|^([[:space:]]*Server[[:space:]]*=)|#\1|' "$OMAMOBILE_MIRRORLIST"
sed -i 's|^#Server = file:///var/lib/omamobile/repo/\$arch$|Server = file:///var/lib/omamobile/repo/$arch|' "$OMAMOBILE_MIRRORLIST"
grep -qxF "$OMAMOBILE_LOCAL_SERVER" "$OMAMOBILE_MIRRORLIST" ||
printf '%s\n' "$OMAMOBILE_LOCAL_SERVER" >>"$OMAMOBILE_MIRRORLIST"
echo "==> [omamobile] stays on this phone's own repository (/var/lib/omamobile/repo)."
echo " Installed phones follow the stable channel at pkgs.omamobile.org; switch with"
echo " sudo omamobile-update channel stable (or development)"
}

pre_upgrade() {
remember_local_channel
}

post_install() {
add_repository
}

post_upgrade() {
add_repository
keep_local_channel
}
Loading
Loading