Skip to content

device-lynx 0.2.0: the device package, the Arch root and the Wi-Fi plan - #88

Merged
derekross merged 18 commits into
derekross:mainfrom
latentoperator:lynx-device
Oct 28, 2026
Merged

derekross merged 18 commits into
derekross:mainfrom
latentoperator:lynx-device

Conversation

@latentoperator

Copy link
Copy Markdown
Contributor

What and why

The Pixel 7a's device package, the notes from the Arch root, and the Wi-Fi plan asked for on #36. Tracking issue: #36. Rebased onto today's main; nothing stacked.

  • omamobile-device-lynx 0.1.0, then 0.2.0. The Pixel Fold's package without the lid drop-in: storage guard rule, USB address, power-key drop-in, mirrorlist, reboot-to, the descriptor. 0.2.0 adds the Pixel 7 Pro's omamobile-boot-success unit and omamobile-bootctl, because slot B has three retries after fastboot --set-active=b and every unmarked boot burns one; the fourth boot fell to slot A, where Android now stops at "Cannot load Android system" (shared userdata). devinfo is sdd1, layout 3.15, the same as the Pixel 7 Pro. Registered in tools/build-packages and tests/all. The descriptor's comment changes from "not written yet" to what the package does.
  • NOTES.md: UFS with cheetah's nodes (SK hynix 128 GB, HS-G4 L2, the storage guard leaving exactly six partitions writable), tools/install-phone putting an Arch root on userdata (needs --bootloader-slots-match: the bootloader reports only the current slot's version), the Goodix GT9895 touchscreen with 14-byte contact records and its two LDOs, the S2MPG12 RTC, the slot retries, and Wi-Fi as far as it got.
  • BRINGUP-M1.md: the recovery section you asked for after the Arch install. Buttons are the only way back now (Power about 30 s, then Volume Down + Power), fastboot --set-active=b from the bootloader menu, and never "Factory data reset" there.
  • WIFI-PLAN.md, as asked on Pixel 7a (lynx, gs201 IPOP) port: stock facts and first light #36: the facts, where the ROM stops (pbl_auth.c, with the image bisection and the iATU bisection), the ruled-out list from both phones, the stock-side read of WLAN_SECURE_BOOTN (0x0 under stock's cnss2, six reads over three states, not the 0x11111111 seen on mainline after the stall), both stop conditions as stop conditions, the open leads and the state to resume from. The published kernel has no PCIe node for lynx; the Wi-Fi branch stays local and the modules stay blacklisted on the phone. NOTES.md gets the short entry and points at it.
  • DEVICES.md: the Pixel 7a row. Boot, Storage and Touch say what the notes record (Storage and Touch on unpublished kernel branches, linked, as the Pixel 6 Pro row does); Wi-Fi and Bluetooth point at the plan. Drop this commit if you'd rather keep the row until the kernel branches are in.

The kernel side of UFS, touch and the sub-PMIC is on local branches on top of #44 (omamobile-gs201-lynx-ufs, -touch); they come as PRs next, UFS first. The package does not depend on them to install, but omamobile-boot-success needs UFS to find devinfo, and the storage guard has nothing to guard without it.

Device and build

  • Phone: Pixel 7a (lynx), MP1.0, bootloader lynx-17.0-15199429 on both slots
  • Kernel release (uname -r): 7.3.0-rc6-omamobile-push1-g38b5a04d67e0 (the local Wi-Fi branch tip; it carries the unpublished UFS, touch and sub-PMIC commits on top of omamobile-audio 0.5.0: a UCM profile and PipeWire rule for the Pixel 9a #44)
  • Packages changed, with versions: omamobile-device-lynx 0.1.0 (new), 0.2.0

Checks (no phone needed)

  • tools/pr-check origin/main passes
  • tests/all passes (186 ok; it now runs packages/omamobile-device-lynx/test/all)
  • tests/packages: the package I touched, packages/omamobile-device-lynx/test/all, passes (20 ok); the package built with tools/build-packages omamobile-device-lynx on 2026-10-24
  • Each changed package has its version bumped, and the new version is in the commit subject
  • Commits have area prefixes and bodies that say why; any AI help is a Co-Authored-By: or Assisted-by: trailer, never a Signed-off-by:

On the phone

  • I ran this on my own phone, booted into this build
  • Runbook steps passed (plan, step, result): none to run; WIFI-PLAN.md section 7 is unscheduled by design. BRINGUP-M1's recovery steps were walked twice (2026-10-24 after the fourth unmarked boot, and 2026-10-27 going to stock and back).
  • What I did not test: a fresh tools/install-phone from this exact head (the 2026-10-27 reinstall used images built before the rebase; the package files are unchanged since). The root image on the phone carries 0.1.0; 0.2.0's omamobile-boot-success and unit were copied in and enabled by hand on 2026-10-24 and have marked the slot after every boot since. The [omamobile] mirrorlist entry against the published repository. Anything radio. reboot-to was built but only omamobile fastboot was used.
  • Nothing in this change writes outside slot B and userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1). The one write elsewhere is the Pixel 7 Pro's own boot-success marker in devinfo: it opens that disk and partition read-write for the one omamobile-bootctl write and relocks them, unchanged from cheetah's package.

Two things I hit, in case they are worth a look: tools/phone-smoke run from the laptop came back empty here (the report below is --here on the phone, with the output to a file; run through phone-ssh the session also outlived the script until a timeout), and packages/.gitignore ignores src/, so the package's two C sources needed git add -f, as the other device packages' did.

tools/phone-smoke report

phone-smoke: lynx

Kernel 7.3.0-rc6-omamobile-push1-g38b5a04d67e0, tools at b17370c, 2026-10-27T16:54Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-g38b5a04d67e0, slot b, up 1208s
storage guard (required) ok 55 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 99G free
kernel health (required) ok no oops or BUG; 0 WARN, 8 error lines in dmesg
systemd units ok none failed
USB gadget (required) ok bound to 11210000.usb
display ok card0-Unknown-1 connected, 1080x2400
GPU not ok no render node
session (required) ok Hyprland and the Omarchy shell running
lock ok PAM file present, the shell can lock (passwordPam true, locked false)
touch ok Goodix Berlin Capacitive TouchScreen
buttons skip no key input device found by name
Wi-Fi skip no wireless interface
Bluetooth skip no controller
battery skip no battery power supply
sound cards skip none
sensors skip no sensor proxy
cameras skip no libcamera tools

Packages: hyprland 0.56.2-7, libcamera 0.7.2-4, mesa 1:26.2.5-1, omacam 0.3.3-1, omamobile-apps 0.2.0-1, omamobile-device-lynx 0.1.0-1, omamobile-firstboot 0.1.0-1, omamobile-keyring 20261013-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.6-1, omamobile-owl-widgets 0.1.1-1, omamobile-shell 0.2.15-1, omarchy 4.0.6-1, quickshell 0.3.2.r7.g2b4501a-1

I used an AI assistant (Claude Code) for this; the commits carry a Co-Authored-By: trailer.

🤖 Generated with Claude Code

latentoperator and others added 8 commits October 27, 2026 11:41
The board file's UFS nodes bring the link up at HS-G4 on two lanes, as
on stock, and the storage guard leaves only slot B's boot images and
userdata writable. Record the part, the LUN layout and the guard's
result.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add omamobile-device-lynx, a copy of felix's first package without the
lid drop-in: the storage guard rule, the USB address, the power-key
drop-in, the mirrorlist and reboot-to. It marks no slot successful and
starts no hardware. tools/build-packages builds it after felix, and
tests/all runs its tests.

With it, tools/install-phone put a root image built for lynx on
userdata, and the phone booted into Arch and Hyprland on simpledrm.
Record the install, the missing RTC and what it does to the keyring,
and the lock screen without touch in NOTES.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The bootloader gives slot B three retries after set-active and takes one
on every boot that is not marked. Pushing new images four times in a row
used them up and the phone fell back to slot A's Android.

omamobile-device-lynx 0.2.0 ships the Pixel 7 Pro's boot-success unit and
omamobile-bootctl unchanged. lynx's devinfo is sdd1 with the same 3.15
layout. The test checks both copies match the cheetah package and runs a
bootctl dry run against a synthetic devinfo.

NOTES records the touchscreen, the PMIC RTC, and the slot retries.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The QCA6490 enumerates and reads host memory, but its boot ROM stalls
before checking the first firmware hash. Notes cover the power pins,
the image bisect, what is ruled out, and the stock differences left to try.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The descriptor dropped BRINGUP_PROBE and gained the rollback-index
comment; the package ships a byte-identical copy, which its test
checks.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Record the last verified integration state and distinguish historical first-light behavior from the current installation. Android slot A cannot boot with Arch userdata, so physical buttons are the recovery route.

Assisted-by: LLM
The QCA6490's boot ROM reads the ELF header and the hash segment of an
image byte-identical to stock's, then stops at stage 0x0a of
0xef0a0002, which the ROM's own source names put in pbl_auth.c. Every
host-side difference two testers could act on was tried one change per
boot, all negative, so the maintainer and both testers agreed on derekross#36 to
park it and write it up where the next person starts.

WIFI-PLAN.md holds the facts, where it stops, the ruled-out list, the
stock-side read of WLAN_SECURE_BOOTN (0x0 under stock's cnss2, not the
0x11111111 seen on mainline after the stall), both stop conditions as
stop conditions, the open leads and the state to resume from. NOTES.md
gets the short entry and points at it; the 2026-10-24 "next" line is
marked superseded. The published kernel has no PCIe node for lynx; the
Wi-Fi branch stays local and the modules stay blacklisted on the phone.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Boot: an Arch root on userdata from slot B, with the device package
marking the slot successful. Storage and Touch: WIP on unpublished
kernel branches, linked to the notes that record them, as the Pixel 6
Pro row does. Wi-Fi and Bluetooth: still no, now pointing at the plan
that says why.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
latentoperator and others added 3 commits October 27, 2026 12:12
FlorencioJP re-read the register set after a stall on 2026-10-27: the
WLAON and TLMM neighbours match the stock column exactly, so the window
lands, and the three registers that differ are the three the ROM's
authentication stage consults. Their caveat on our stock column stands:
cnss2 on lynx never drops the buck, so "pre-BHI after a cycle" is after
a good PBL run. The open leads now say what a cold stock read takes on
this build and what each outcome would mean.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The maintainer's reading of the stock trace, checked against the
2026-10-27 dmesg here and FlorencioJP's full-Android log: the buck comes
up once, the probe asserts WLAN_EN, enumerates and powers the link off
without a BHI, and the first image download follows the second assert,
7.7 s later. Google's minimal diagnostic on the stock kernel stalls like
mainline when the BHI follows the probe cycle by 13 ms, so the wait is
the variable. The open leads are reordered on that: the stock-shaped
power sequence with the wait first (FlorencioJP's phone), the cold stock
read only if it fails. Both phones' pin states at power-up are in a
table, and the hang difference (stock's pre-BHI reads against a read
right after ath11k's SoC reset) is noted beside the stop condition,
which stays as written.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
FlorencioJP read the stock-side register list at the stall: 132 of 147
match the warm pre-BHI column, the power sequencer included. Beyond the
stall's own trace, one more register differs from a warm chip,
WLAON_MEM_SVS_CFG_REG, 0x1 warm and 0x0 at the stall, so it joins the
cold-read list. The JTAG id reads the same on both phones, which puts
both register windows in the same place.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@derekross

Copy link
Copy Markdown
Owner

Thank you, @latentoperator. This is a clean first package and a very good plan. The package is the Pixel 7 Pro's files byte for byte where it says so (omamobile-boot-success, its unit, omamobile-bootctl with Google's notice, reboot-to, the storage rule, the power-key drop-in, the mirrorlist and the install hook), and its test checks each of those with cmp, so a drift on either side shows. It enables nothing at boot except the boot-success unit, and nothing that loads a driver. WIFI-PLAN.md is what I hoped for: the ROM stage, the ruled-out table with who tested what, both stop conditions written as stop conditions, and the hang difference kept as "not a licence". Here tools/pr-check origin/main, tests/all and the package's own test pass on this head. CI is green on it, and it merges cleanly onto today's main.

Two things before it merges:

  1. The devinfo evidence for lynx. A package that writes devinfo at every boot is the one write outside the storage guard, so I'd like the same record the Pixel 6 Pro gave, in BRINGUP-M1 or NOTES. Lynx is gs201 like the Pixel 7 Pro, but its bootloader is a different build (it needs the AVB footers the Pixel 7 Pro's doesn't), so the bytes need checking against what the bootloader itself reports. Next time the phone is in fastboot anyway, please add omamobile-bootctl dump's bytes 0x30-0x37 (only those, plus the version) next to fastboot getvar slot-successful, slot-unbootable and slot-retry-count for both slots, in three states: slot B marked; after fastboot --set-active=b, before booting; and after one boot with the unit masked, so the bootloader has spent a retry itself. Please also note that the first marks on 2026-10-24 and 2026-10-27 were made by hand from the running system, outside the guard's rules. The Pixel 6 Pro's notes word it that way too.
  2. WIFI-PLAN.md after step 6. This head predates FlorencioJP's 18:10Z result on Pixel 7a (lynx, gs201 IPOP) port: stock facts and first light #36. Section 2's "the 7.7 s ... is the variable" and section 7's item 1 now have their answer: negative at 8 s and 30 s, with the four registers unchanged. The stock-kernel diagnostic also answers item 5. Google's own host stack, SysMMU translating, stalled the same way, so "SysMMU translating as stock" can move to the ruled-out table with that as its evidence. Please also mark the "[V]" on the 7.7 s line as an inference that failed rather than delete it. And add the open question from my reply on Pixel 7a (lynx, gs201 IPOP) port: stock facts and first light #36 (what full Android does to the chip between the probe and the first BHI, Bluetooth first) as the next item.

And some smaller things. None of them holds the merge, though the first is worth doing in this PR:

  • Sleep. The Pixel 7 Pro ships vendor/systemd/sleep.conf.d/10-omamobile.conf (MemorySleepMode=s2idle, no hibernation), and its bootargs carry mem_sleep_default=s2idle. The firmware offers PSCI system suspend, so the kernel offers deep, which on gs201 never wakes. Lynx has neither, so Omarchy's "Suspend" menu entry, or the sleep toggle, could put the phone into a sleep that only a held power key ends. Could you check cat /sys/power/mem_sleep on the phone, and add the Pixel 7 Pro's drop-in to this package with a cmp in the test like the others? (Suspend on lynx is untested either way; this only keeps it on the kind that wakes.)
  • tests/storage-guard checks cheetah's, felix's and oriole's allowlists but not lynx's. Lynx's is the same as cheetah's, so adding lynx:"$cheetah_rw" to its loop is a one-word change.
  • docs/DEVICES.md has lynx twice. The "Wanted" list (line 65) still says first light with USB and SSH, so please bring it in line with the row. Once linux-omarchy-mobile omamobile-audio 0.5.4: the speaker filter flat with 6 dB of drive by default #91 is in, the Storage cell can link it instead of saying "unpublished kernel branch".
  • BRINGUP-M1's status line says 2026-10-25, while NOTES has the 2026-10-27 reinstall.

On merge order: this doesn't depend on #91, and #91 doesn't depend on it, since the storage guard's allowlist for lynx is already on main. If #91 merges first, the Storage cell can say so in this PR. It will be squashed under your title, which already has the right prefix and version.

latentoperator and others added 5 commits October 27, 2026 16:54
docs/DEVICES.md conflicted on the Pixel 7a row (derekross#95 updated it). Keep this branch's row; the Storage cell now links kernel derekross#91, merged, and the Touch cell kernel derekross#93, in review.
The firmware offers PSCI system suspend, so the kernel offers deep sleep,
and the phone reads `s2idle [deep]`. On gs201 deep never wakes, so the
desktop's Suspend entry could leave the phone in a sleep only a held
power key ends. Ship the Pixel 7 Pro's drop-in (MemorySleepMode=s2idle,
no hibernation), byte for byte, with a cmp in the test like the other
shared files. Suspend on lynx is still untested.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Lynx's allowlist is cheetah's, so it joins the loop with the same list.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DEVICES: the Wanted line now matches the matrix row (UFS in the
published kernel, touch in review, Wi-Fi parked). BRINGUP-M1: the status
line from the 2026-10-27 reinstall, with the mem_sleep reading. NOTES:
the 2026-10-24 BT_EN test was the pin only, with no Bluetooth firmware.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Step 6 (FlorencioJP, 8 s and 30 s of WLAN_EN low with the buck held,
on mainline) is negative, so the 7.7 s line's [V] is marked as an
inference that failed. Google's calibration handler sleeps 5 s before
the first load, both stock boots here show it, and the stock-kernel
diagnostic skipped it: no run has had Google's host stack and the wait
together, which makes the fs_ready boot the next item. Bluetooth is
ruled out by FlorencioJP's reference 2. 0xef150600 shows up before the
first BHI on a chip that never passed, so section 5's warm/cold reading
is withdrawn. The stock-kernel diagnostic moves SysMMU translating to
the ruled-out table, on its own. The 2026-10-24 BT_EN test is described
as what it was, the pin only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@latentoperator

Copy link
Copy Markdown
Contributor Author

Thanks @derekross. Pushed:

The devinfo record needs the phone in fastboot, so it comes in the next push, with the note that the 24 and 27 Oct marks were made by hand.

Bytes 0x30-0x37 from omamobile-bootctl dump next to fastboot's
slot-successful, slot-unbootable and slot-retry-count, in three states:
slot B marked, after --set-active=b, and after one boot with the marker
masked. Byte 0 is the retry count and byte 1 the flags, as on the
Pixel 7 Pro and Pixel 6 Pro. The first marks on 2026-10-24 and
2026-10-27 were made by hand, outside the storage guard's rules; that
is recorded too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@latentoperator

Copy link
Copy Markdown
Contributor Author

@derekross, the devinfo record is in BRINGUP-M1 (pushed), from the phone this evening on g38b5a04d67e0 with device-lynx 0.2.0. Bytes 0x30-0x37 next to fastboot getvar for both slots, in your three states:

State slot a bytes slot a fastboot slot b bytes slot b fastboot
B marked 00 0a 00 00 yes / no / 0 02 06 00 00 yes / no / 2
after --set-active=b, before booting (unchanged) yes / no / 0 (not readable) no / no / 3
after one boot with the unit masked 00 0a 00 00 yes / no / 0 02 04 00 00 no / no / 2

(fastboot columns are successful / unbootable / retry-count.) Same meaning as on the Pixel 7 Pro and 6 Pro: byte 0 is the retry count, byte 1 the flags (0x04 active, 0x02 successful). After the test the unit was unmasked and slot b is marked again (02 06). One extra: a forced restart on the marked slot didn't spend a retry. The section also says the 24 and 27 Oct marks were made by hand, outside the guard's rules, and how.

The two test phones carry different revisions of the chip: stock cnss
logs major/minor 0x12/0x11 here and 0x2/0x10 on FlorencioJP's, with the
Bluetooth SOC version to match. Both stall the same way and read the
same JTAG id. FlorencioJP's full-Android logs also show the calibration
handler's 5 s wait before the first load, as this phone's do.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross

Copy link
Copy Markdown
Owner

Thank you, @latentoperator. All of it is in, and the devinfo record is exactly what I hoped for. Every byte agrees with what the bootloader reports, in all three states: byte 0 is the retry count (2, then 3 after --set-active=b, then 2 after one unmarked boot), and in byte 1, 0x04 is active and 0x02 successful. That's the layout the Pixel 7 Pro and 6 Pro have, now checked against lynx's own bootloader. The forced-restart observation and the account of the two hand-made marks, with the --setrw and the trap, are good to have on record too.

The rest is done as well: the sleep drop-in, byte for byte with a cmp in the test, lynx in tests/storage-guard, both DEVICES lines, the BRINGUP-M1 status line, and WIFI-PLAN.md after step 6, with the failed inference kept visible rather than deleted. tools/pr-check, tests/storage-guard and the package's own test pass on this head here, and CI passed on it after main's last commit. I'll squash-merge it under your title. Merging it is also my go for the package writing devinfo at every boot.

A few things for a later plan update, none of them for this PR:

  • FlorencioJP's fs_ready boot (Pixel 7a (lynx, gs201 IPOP) port: stock facts and first light #36, 23:32Z) came in after your last push and stalled. Section 7's first item now has its answer, and the status line's "that is the next step" is out of date.
  • Bluetooth now works on FlorencioJP's lynx (linux-omarchy-mobile device-lynx: Bluetooth on the APM UART #98). On a kernel with that node, a regulator owns gph2-5: it raises it a few seconds into boot and drops it whenever Bluetooth turns off. So section 5's "at every Linux boot gph2-5 reads output low" and the "Bluetooth waits on the same question" line need updating once that lands. Your local Wi-Fi branch can't drive the pin as well while Bluetooth holds it. I've raised the details on device-lynx: Bluetooth on the APM UART #98.
  • Section 2 says gpp16-2 is on PERIC1 (0x10840000), "which our tree does not describe". 0x10840000 is PERIC0, and the published gs201-pinctrl.dtsi does describe gpp16 there. The Pixel 7 Pro's Bluetooth uses it.

@derekross
derekross merged commit 27e9eaf into derekross:main Oct 28, 2026
2 checks passed
derekross added a commit that referenced this pull request Oct 28, 2026
The Pixel 7a's touch is in the published kernel (kernel #93) and its
device package is merged (#88); the Pixel 4 XL's notes and results
merged with #52, so its cells drop the "in review" qualifier; the
Pixel 7's board device tree, touch driver and package are in review.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robotosaith added a commit to robotosaith/omarchy-mobile that referenced this pull request Oct 28, 2026
lynx's package (derekross#88) ships the same 20-usb-gadget.network as the
others, with the laptop as usb0's Gateway= at metric 0, a route that
outlives an unplug. It gets the same fix: the gateway is a [Route] at
metric 2000, after Wi-Fi (600) and mobile data (700), and the same
test. Not tested on a Pixel 7a.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross pushed a commit that referenced this pull request Oct 29, 2026
The plan merged in #88 as it stood before the fs_ready diagnostic boot
(run 17, 2026-10-27, #36). Record its result and what follows from it:

- status line: the boot with Google's host stack, Google's own trigger
  and full Android's 5 s wait ran and stalled the same way, so that pair
  is ruled out and the variants are stopped; the cold stock read is the
  one measurement left;
- section 7 item 1: the run as reported on #36 (Google's kernel and
  vendor_dlkm modules, 68 modules, Bluetooth off, fs_ready at 10.8 s,
  IN_COLD_BOOT_CAL, the power-up 5 s later, BHI from 16.0 s, 0xfad00000
  on every dump, -110 at 76.8 s), and the module count that matches it;
- section 7 item 2: the module comparison as background, with the
  caveat about first-stage loads, and the CNSS profile's 16 modules on
  top of the USB profile's 52, in load order;
- section 8: the ramoops console survives only a warm return, so the
  diagnostic's init writes warm to /sys/kernel/reboot/mode first;
- section 5 and the pin table: gph2-5 reads output low at every Linux
  boot only on a kernel without the Bluetooth node
  (linux-omarchy-mobile #98); with it a regulator owns the pin, so
  unbind the serdev first and record which kernel a run used.

Assisted-by: LLM

Signed-off-by: Jean-Paul Florencio <jpflorencio@version-tracker.app>
Co-authored-by: Jean-Paul Florencio <jpflorencio@version-tracker.app>
derekross added a commit that referenced this pull request Oct 31, 2026
The Pixel 9a's SoC and board device tree, 120 Hz, the touchscreen and its
sleep fix, NFC's ST54L mode and poll stop, and the panel's local high
brightness mode are merged (kernel #80/#81, #88, #82, #131, #71, #126;
#155). The Pixel 8 Pro's buttons are in the published kernel (kernel
#148). The OnePlus 13's device package is merged (#111), mustang has stage
0 notes (#198), and kodiak joins the Pixel 11 row (#201).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
The plan merged in derekross#88 as it stood before the fs_ready diagnostic boot
(run 17, 2026-10-27, derekross#36). Record its result and what follows from it:

- status line: the boot with Google's host stack, Google's own trigger
  and full Android's 5 s wait ran and stalled the same way, so that pair
  is ruled out and the variants are stopped; the cold stock read is the
  one measurement left;
- section 7 item 1: the run as reported on derekross#36 (Google's kernel and
  vendor_dlkm modules, 68 modules, Bluetooth off, fs_ready at 10.8 s,
  IN_COLD_BOOT_CAL, the power-up 5 s later, BHI from 16.0 s, 0xfad00000
  on every dump, -110 at 76.8 s), and the module count that matches it;
- section 7 item 2: the module comparison as background, with the
  caveat about first-stage loads, and the CNSS profile's 16 modules on
  top of the USB profile's 52, in load order;
- section 8: the ramoops console survives only a warm return, so the
  diagnostic's init writes warm to /sys/kernel/reboot/mode first;
- section 5 and the pin table: gph2-5 reads output low at every Linux
  boot only on a kernel without the Bluetooth node
  (linux-omarchy-mobile derekross#98); with it a regulator owns the pin, so
  unbind the serdev first and record which kernel a run used.

Assisted-by: LLM

Signed-off-by: Jean-Paul Florencio <jpflorencio@version-tracker.app>
Co-authored-by: Jean-Paul Florencio <jpflorencio@version-tracker.app>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
The Pixel 9a's SoC and board device tree, 120 Hz, the touchscreen and its
sleep fix, NFC's ST54L mode and poll stop, and the panel's local high
brightness mode are merged (kernel derekross#80/derekross#81, derekross#88, derekross#82, derekross#131, derekross#71, derekross#126;
derekross#155). The Pixel 8 Pro's buttons are in the published kernel (kernel
derekross#148). The OnePlus 13's device package is merged (derekross#111), mustang has stage
0 notes (derekross#198), and kodiak joins the Pixel 11 row (derekross#201).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants