Repository navigation
flame 0.1.0: hooks for shell 0.2.24 and firstboot 0.1.3 - #55
wirelessjoe wants to merge 1 commit into
Conversation
Package the guarded native runtime and marker-gated hooks independently of boot metadata writes. Keep Wi-Fi startup owner-gated and preserve upstream agent selection. Refresh versions over main and require the versions supplying these hooks. Host package fixtures pass; a fresh package deployment remains a hardware gate. Co-Authored-By: Codex <noreply@openai.com>
…lags as a named exception Two decisions the Qualcomm ports (#17/#55-#59 flame, #52 coral, #25 alioth) were waiting on: - AGENTS.md said never to run an unsuffixed fastboot flash, but our own tools/install-phone already flashes userdata that way behind its guards. The rule now says so: userdata has no slots, and it is flashed only through install-phone. - On the Pixel 4 family the A/B slot flags live in GPT attributes, so marking slot B bootable is a partition-table write the storage guard can't block. It is allowed only as a narrow exception named per device in CONTRIBUTING §3.1 (LUN, sectors, bit, CRCs), done by hand once per boot-image install, with the flags recorded before and after, a rollback for a corrupted GPT and a way back. Never automatic. No device has an entry yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thanks! The package is well scoped. Only the storage guard is enabled, Wi-Fi ships disabled behind your own manifests, rmtfs only ever gets RAM copies that are checked against the real partitions first, and the shell and first-boot hooks do nothing unless the flame marker is there. I ran the flame, first-boot and setup-user suites on all five PRs merged together, and they pass. One thing to change: the shell version. Main is at 0.2.23, but I have a batch of shell changes going in as 0.2.24 to 0.2.27. If mine lands first, a different 0.2.24 would satisfy Smaller things, none blocking:
|
…lags as a named exception (#60) * AGENTS, CONTRIBUTING: userdata through install-phone; Qualcomm slot flags as a named exception Two decisions the Qualcomm ports (#17/#55-#59 flame, #52 coral, #25 alioth) were waiting on: - AGENTS.md said never to run an unsuffixed fastboot flash, but our own tools/install-phone already flashes userdata that way behind its guards. The rule now says so: userdata has no slots, and it is flashed only through install-phone. - On the Pixel 4 family the A/B slot flags live in GPT attributes, so marking slot B bootable is a partition-table write the storage guard can't block. It is allowed only as a narrow exception named per device in CONTRIBUTING §3.1 (LUN, sectors, bit, CRCs), done by hand once per boot-image install, with the flags recorded before and after, a rollback for a corrupted GPT and a way back. Never automatic. No device has an entry yet. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * DEVICES: the PinePhone Pro's codename and starting point The Wanted row had "-" as its codename, which omamobile.org prints next to the SoC ("-, Rockchip RK3399S"). It takes mainline's board name, pinephone-pro, and names that device tree, already in our kernel, as the starting point (promised on #47). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The matrix and the Wanted list against what has merged since #140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were closed because they landed unchanged through kernel #134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the 2026-10-28 notes. Touch stays WIP: kernel #134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel #133) and the kernel option with the touch notes (#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names its open kernel PR, #116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133) records it scanning through its own UART; kernel #98 and #98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes the merged tier 1 auto-sleep (#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open #171, #172, #174-#176. - Wanted: coral's #52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (#55, #56, #58, #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and kernel #115, both open. The Pixel 9a row and the Pixel 9 family line are left to #165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ing (#307) The 9a's row after today's merges, with a NOTES entry for the evening's boots that the new cells link to. - **Wi-Fi, testing to works.** `omamobile-device-tegu` 0.2.4 (#238) starts it at boot now, through the shared gs201 host and zuma PHY (kernel #178 on #156, both in review) and brcmfmac (kernel #56, in review), with only the extractor's firmware. The NOTES entry has the boot, and the three rebinds with Bluetooth up after #178's FLR commit. The kernel parts are still in review, and the cell says so, as the display cells did. - **Suspend, WIP to testing.** The power key now lights the lock screen on the first press (#268, #275). Thirty attended sleeps and a day of real use with auto-sleep on all woke (SLEEP-PLAN, #284). The cell still says that three test sleeps on 10-28 to 10-30 never woke and that sleep tests stay attended. If you'd rather keep WIP until that hang is understood, I'll revert just the word. - **Display:** the display DT is merged, and brightness, DPMS off and on and the 60/120 Hz switch now have a dated record (kernel #125's boot, which also checks the panel ID). - **Charging, Haptics, Torch, NFC:** kernel #161, #96, #104 and #105 are merged. - **USB net:** the rescue also handles a replug the gadget didn't see (#280). The NOTES entry lists each boot with its release: Wi-Fi from the package, the power-key wake, the replug, storage idle (kernel #99), the panel ID (kernel #125), the RTC without the PMIC interrupt (kernel #55), and the auto-sleep day. GNSS and Modem stay as they are until the SIM test on Tuesday. Docs only; `tools/pr-check` passes, and the diff has no identifiers. Closes #307 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
A friendly check-in: this has had no activity for about 11 days and now conflicts with main. If you're still working on the flame port, a rebase onto main will get it moving again, and I'm happy to review. If I don't hear back within a week I'll close it to keep the queue tidy; it can be reopened any time. |
The matrix and the Wanted list against what has merged since derekross#140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were closed because they landed unchanged through kernel derekross#134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the 2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133) and the kernel option with the touch notes (derekross#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names its open kernel PR, derekross#116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133) records it scanning through its own UART; kernel derekross#98 and derekross#98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes the merged tier 1 auto-sleep (derekross#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176. - Wanted: coral's derekross#52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58, derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and kernel derekross#115, both open. The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…ing (derekross#307) The 9a's row after today's merges, with a NOTES entry for the evening's boots that the new cells link to. - **Wi-Fi, testing to works.** `omamobile-device-tegu` 0.2.4 (derekross#238) starts it at boot now, through the shared gs201 host and zuma PHY (kernel derekross#178 on derekross#156, both in review) and brcmfmac (kernel derekross#56, in review), with only the extractor's firmware. The NOTES entry has the boot, and the three rebinds with Bluetooth up after derekross#178's FLR commit. The kernel parts are still in review, and the cell says so, as the display cells did. - **Suspend, WIP to testing.** The power key now lights the lock screen on the first press (derekross#268, derekross#275). Thirty attended sleeps and a day of real use with auto-sleep on all woke (SLEEP-PLAN, derekross#284). The cell still says that three test sleeps on 10-28 to 10-30 never woke and that sleep tests stay attended. If you'd rather keep WIP until that hang is understood, I'll revert just the word. - **Display:** the display DT is merged, and brightness, DPMS off and on and the 60/120 Hz switch now have a dated record (kernel derekross#125's boot, which also checks the panel ID). - **Charging, Haptics, Torch, NFC:** kernel derekross#161, derekross#96, derekross#104 and derekross#105 are merged. - **USB net:** the rescue also handles a replug the gadget didn't see (derekross#280). The NOTES entry lists each boot with its release: Wi-Fi from the package, the power-key wake, the replug, storage idle (kernel derekross#99), the panel ID (kernel derekross#125), the RTC without the PMIC interrupt (kernel derekross#55), and the auto-sleep day. GNSS and Modem stay as they are until the SIM test on Tuesday. Docs only; `tools/pr-check` passes, and the diff has no identifiers. Closes derekross#307 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What and why
Part (b) of the requested split of #17, following Derek's current review. Based directly on current main
671b089; conflicts with the old proposal have been resolved.Device-flame runtime 0.1.0 plus marker-gated shell 0.2.24 and first-boot 0.1.3 hooks, rebased over main's newer packages. Explicit dependencies require those hook versions. Wi-Fi stays owner-gated; the upstream agent chooser remains. The runtime must be available before native root/build use.
Device and build
flame) for the historical bring-up; this revision is host-validated. No phone is contacted by these tests.7.0.0-sm8150; no new hardware boot claimed.Checks
tools/pr-check origin/maintests/allHost policy/tests/all and all three touched package suites passed, including staging, guard behavior, owner configuration and USB-only firewall fixtures. The refreshed package set has not been installed on the phone.
The full unrelated package run in the older Debian/root harness has four failures also reproduced on unmodified main (mirror, mmd, sensors and speaker-tuning). Touched package suites pass with current jq behavior. Optional QML/Lua/root-image/provisioning fixture checks report skips. This is not a claim that every package test passed in that harness; CI uses Arch and a normal user.
On the phone
No hardware changes in this review refresh. A read-only attempt to collect a current
tools/phone-smokereport could not reach the connected USB endpoint, so no fresh report is attached. Historical results stay explicitly separate from the exact new source/build. Native boot and runtime deployment remain owner-approved gates; the signed complete root and Android rollback cycle have not been repeated.The original #17 retains the historical discussion and an immutable source snapshot; companion links and merge ordering are listed there. No firmware, calibration, identifiers, credentials or binary images are published. The earlier intermittent runtime reset remains unexplained.
Companions: runtime #55, boot #56, ssh #57, metadata #58, docs #59. Runtime #55 must be available before native boot/root use; the metadata proposal #58 stays held for policy.