Repository navigation
device-bluejay 0.1.3: publish the persistent accelerated Pixel 6a bring-up - #543
Closed
latentoperator wants to merge 4 commits into
Closed
latentoperator wants to merge 4 commits into
latentoperator wants to merge 4 commits into
Conversation
Check the ext4 label before repair or writable mounting, stop on unsafe fsck results and retain a pending marker until installed SSH is ready. Keep development roots at image size until their first persistent boot works, and leave an unknown development selector in RAM rescue. Honor an explicit descriptor AUTO_WRITE policy and optional fastboot serial pin. Existing descriptors retain the automatic-write default. Stage both persistent and RAM-rescue Bluejay selectors through the image tool, optionally applying an overlay to both silicon variants. Exercise actual boot_arch ordering and failure holds, installer policy, and synthetic vendor images through independent CPIO/device-tree tools. Co-Authored-By: Codex <noreply@openai.com>
Record persistent Arch/Omarchy, polling ALIX touch, BCM4389 station reconnect and Mali-G78 rendering on the owner's Pixel 6a. Add the pinned development package, guarded startup and renderer fallback, bring-up overlays, kernel fragment and source/reproduction limitations. Keep hardware, Wi-Fi and GPU behind explicit opt-ins, preserve the storage guard and leave automatic boot writes/success marking off. Include no firmware, credentials, images or per-device captures. This shares a tested development milestone, not a self-contained release installer. Native panel, full DVFS, suspend and other untested hardware remain marked unfinished. The kernel changes are submitted separately. Co-Authored-By: Codex <noreply@openai.com>
Use the existing FAKE prefix convention so the publication identifier gate recognizes the deliberately mismatched test serial. Co-Authored-By: Codex <noreply@openai.com>
Check both embedded silicon variants before creating repacked output, including a forged sidecar regression case. Verify the board and the four qualified stripped Wi-Fi module hashes before any load; their bytes match canonical build outputs after strip-debug. Co-Authored-By: Codex <noreply@openai.com>
This was referenced Nov 9, 2026
Merged
Merged
Owner
|
Thank you, Chris — getting a Pixel 6a to a persistent, accelerated Omarchy desktop with touch and Wi-Fi is a real milestone, and the notes, the smoke report and the honest "not tested" list make it easy to follow. Since this is a draft, here's what I think it needs to get out of draft:
Thanks again — this is a great base for the 6a. |
This was referenced Nov 9, 2026
7 of 9 tasks
latentoperator
added a commit
to latentoperator/omarchy-mobile
that referenced
this pull request
Nov 10, 2026
Split experimental services, overlays and probe tools from derekross#543. Retain the exact old development-kernel pins and explicit enable gates; these helpers refuse the revised kernel topics. Remove userspace display-register access and use the descriptor/init trigger contract. The proposed SSH-ready helper clears the neutral root marker only when USB and sshd are ready. No new phone run or automatic installation is claimed. Co-Authored-By: OpenAI Codex <noreply@openai.com>
latentoperator
added a commit
to latentoperator/omarchy-mobile
that referenced
this pull request
Nov 11, 2026
Split experimental services, overlays and probe tools from derekross#543. Retain the exact old development-kernel pins and explicit enable gates; these helpers refuse the revised kernel topics. Remove userspace display-register access and use the descriptor/init trigger contract. The proposed SSH-ready helper clears the neutral root marker only when USB and sshd are ready. No new phone run or automatic installation is claimed. Co-Authored-By: OpenAI Codex <noreply@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
The Pixel 6a now boots a persistent Arch Linux ARM/Omarchy desktop from slot B, with automatic polling ALIX touch, BCM4389 station reconnect and Mali-G78/Panfrost rendering. Upstream still describes Bluejay as unbooted. Publish the development source, guarded startup, installer/root protections and measured results so the port can be reviewed and continued. Tracking issue: #2; earlier first-light package proposal: #346.
Draft development milestone, not a release installer. The working phone uses a locally built kernel/module set, privately extracted firmware and a native patched Aquamarine library. These dependencies and the build-specific provenance pins are documented in
device/bluejay/UPSTREAM.md. No firmware, credentials, images, captures or per-device addresses are included.Changes:
BOOT_UPDATE_AUTO_WRITE=noin the installer and an optional fastboot serial pin; other descriptors retain the existing default.omamobile-device-bluejay0.1.3: passive storage/USB checks, watchdog policy, blacklists, bounded subsystem startup and GPU software fallback. Hardware/Wi-Fi/GPU require explicit opt-ins; automatic boot-image and boot-success writes stay disabled.Kernel companion source
The exact tested source at c934e316b starts at published
omamobilecommit29a7a9326bf0. It is not a released kernel. All fourteen author DCO sign-offs have now been added locally by the author and verified. The signed topic PRs based on1a9d1d4e9are open as drafts below:The common review integration passes W=1 builds of all nine changed C files, ten device trees with no new warnings, and all four binding checks. The seven signed topic publication gates now pass. Their code was verified unchanged by sign-off rebasing; the Wi-Fi DT topic is stacked on the signed PCIe/PHY dependency with identical own patch IDs. DT/MAINTAINERS reminders remain disclosed, and merge qualification is separate from these publication checks. The review correction adds PCI identity plus the generic fmac fallback and incorporates the already qualified INTx indices. That compatible-list correction and the newly rebased stack have not been flashed. The tested source is retained separately.
A later kernel review also confined the extra BCM4389 ring limits and changed bus-master ordering to Bluejay (
c41e0aeba, unchanged from the reviewed narrowing); the changed object rebuilt with W=1 and the reviewer verified that other boards retain their original path. The intentionally generic NCM retry still needs reference-device runtime validation before merge. The Wi-Fi DT topic must follow its separate PCIe/PHY bindings. These are kernel merge conditions, not claims that the new rebased stack has run on another phone.Device and build
bluejay), owner-tested.7.3.0-rc6-omamobile-bluejay-input-gated0.omamobile-device-bluejay0.1.3. The installed database still says 0.1.1 because later qualified startup files were staged directly; a freshly packaged/final rebased release install is not claimed.Checks
tools/pr-check origin/mainpasses at6ad4651(identifiers, blobs, AI trailers and parsing).tests/allpasses at the submitted head; rootfs-image smoke skips because this review worktree has no root image.packages/omamobile-device-bluejay/test/allpasses; independently rerun in the repository-required review.boot_archtests cover foreign/unlabelled roots, fsck status handling, marker persistence and stale-attempt rescue; the existing growth/installer/image/storage suites pass.On the phone
remote wakeup not configuredline. The earlier full-boot capture also contains an inherited trace-format WARN and the intentional USI hold; the later dmesg ring has wrapped. These observations are disclosed, not filtered away or presented as a clean full-boot log.devmemhelper at the audited GS101 display addresses; the blanket no-userspace-register-access checkbox would be inaccurate. No PMU userspace access is added. No bootloader/calibration/NV/vbmeta write occurs in this source; the original qualified install used the existing project boot-control helper once to mark B successful, with automatic marking still masked.tools/phone-smokereport after the FUSE repairphone-smoke: bluejay
Kernel
7.3.0-rc6-omamobile-bluejay-input-gated0, tools atdevelopment, 2026-11-08T23:40Z.Packages: hyprland 0.57.0-3.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.2-1, omamobile-apps 0.2.2-1, omamobile-device-bluejay 0.1.1-1, omamobile-firstboot 0.1.3-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.32-1, omamobile-owl-widgets 0.1.2-1, omamobile-shell 0.2.100-1, omamobile-voice 0.1.0-1, omaphone 0.2.3-1, omarchy 4.0.6-1, omatel-agent 0.2.4-2, quickshell 0.3.2.r7.g2b4501a-1