Skip to content

device/tegu: GNSS G3's fifth to forty-fourth tries, the CP link hang, and GNSS parked - #153

Merged
derekross merged 27 commits into
derekross:mainfrom
W4HO-ham:tegu-gnss-g3-night
Oct 30, 2026
Merged

derekross merged 27 commits into
derekross:mainfrom
W4HO-ham:tegu-gnss-g3-night

Conversation

@W4HO-ham

@W4HO-ham W4HO-ham commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

What and why

Split out of #138 at the maintainer's suggestion, so that one merges as fingerprint F6c-F10 plus G3's third and fourth tries, and the GNSS night gets its own review. This is MODEM-PLAN's GNSS section from the night of 10-28 into the morning of 10-29: G3's fifth to forty-fourth tries, the CP link hang, and the decision to park GNSS. Docs only. The ten commits of the night come from #138's branch and sit on its G3 third and fourth try text, so the diff shows those thirty lines too until #138 merges; after that they are identical to main.

What the night found. The "KEP M7 HARDFAULT" at every engine start is not Kepler's own fault. With gnssd's debug log on, the engine tracks satellites within about ten seconds of the start, and the fault that follows is gnssd's soft watchdog resetting Kepler and asking it for a hard fault, because the CHPP link over the GNSS SPI loses packets. Two causes were in the kernel: USI3's clock was stuck on the 399.36 MHz parent, so the SPI ran at 6.24 MHz instead of stock's 3.07 MHz, and mainline spi-s3c64xx cut every 64-byte transfer into 63 + 1 bytes. Both are in derekross/linux-omarchy-mobile#138, in review (the signed-off replacement of #135, which is closed). With those in, mode 0 is marginal at every feedback delay (the reads flip between on time and one bit late within a session), and mode 1 reads are intact but lose the first byte of every block after the first in a back-to-back message. That is a question for a logic analyzer on SPI21, not for more module-level guessing, so GNSS is parked at my decision, without a hardware probe. The two kernel changes stay and the as-ported modules run on the palmtop.

Still open: the CP link hang. After Kepler's watchdog resets, gnssd reloads the image over the CP's PCIe link, and the SoC reset within a second three times (02:43, 03:15, 05:02). Reading CPIF's source found no unguarded BAR access. The trace that would find it is now a gated step, G3-L1: attended, on the charger, with Expect, Stop (two resets or any ufshcd_err_handler line), a cap of two resets per session and three sessions, Rollback, risk medium-high, and the tracing change on a kernel branch before it boots. It runs only if GNSS is resumed.

The maintainer's points from #138, as they stand here:

  • Point 2, the duplicated paragraph and the headings: done. The twenty-fourth try is in once, and the small hours' section is split into "fifteenth to twenty-third tries", "twenty-fourth to thirty-fourth tries" and "The CP link hang".
  • Point 3, the link-hang step: done, as G3-L1 above.
  • Point 4, the test code behind the night: done. Every variant is its own commit on the bring-up branch, Bring-up, not for merge: the Pixel 9a's GNSS SPI test code behind MODEM-PLAN G3 linux-omarchy-mobile#137, and the plan links each try to its commit. The tool that wrote slot B is named once: our bin/omamobile push, run by a local wrapper after bin/omamobile images.
  • Point 5, the partition check: done, recorded M0.1-style at 10:20 on 10-29. All six partitions match the 10-28 backup, read-only and unmounted. The morning's tries ran before the check, so it covers them too.
  • Not blocking: the two resets at about 34 s right after Bluetooth started are now a dated entry at the top of device/tegu/NOTES.md, pointing at the plan.

Device and build

Checks (no phone needed)

  • tools/pr-check origin/main passes
  • tests/all passes
  • tests/packages passes (or the packages I touched: none touched, docs only)
  • Each changed package has its version bumped, and the new version is in the commit subject (no package changed)
  • 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): MODEM-PLAN G3, fifth to forty-fourth tries: the engine tracks satellites, the link loses bytes, the watchdog resets Kepler; the clock and the cut fixed in the kernel; G3-L1 not run (parked)
  • What I did not test: G3-L1; suspend with the modem on; any try at a stock capture of SPI21; the rebase onto main after device/tegu: fingerprint F6c-F10 (works) and GNSS G3's third and fourth tries #138 merges, which conflicts in MODEM-PLAN and resolves with this branch's file
  • Nothing in this change writes outside slot B and userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1). The soft-watchdog RAM dump and kepler.bin stay private.
tools/phone-smoke report

To be added before merge.

The engine tracks satellites and gnssd's watchdog does the rest. The link garbles single bytes at the 6.24 MHz the SPI really runs at, and stock's OSCCLK clock, 32-bit words and auto CS break the framing.
Stock's OSCCLK clock breaks framing here. Reading in mode 1 lines every frame up on the as-ported clock, but the first bytes after each chip select still arrive damaged, and Kepler resets can take the SoC down.
Kepler resends frames, so the copies can be compared. In mode 1, long frames lose the same bytes at every 64-byte read boundary.
Holding chip select between Kepler's reads ends long frames in zeros, so Kepler wants it released between reads, as stock does.
With feedback delay 3 Kepler's frames are intact but one bit late. A per-read realignment gives clean short frames and satellites; long frames still lose data at each chip-select release.
At stock's clock Kepler's frames are intact but its bit offset drifts with every transfer, more as the clock slows. The CP link hang came back with the slower watcher, so it remains open.
The doorbell writes into the CP's BAR with no lock held across its link check, and the PCIe power-off clears pcie_powered_on outside the transmit lock, so a doorbell can land while the PHY goes into isolation.
The doorbell path is serialized with the PCIe power-off after all; no unguarded BAR access found by reading.
Two kernel changes give the GNSS SPI stock's 3.072 MHz and one uncut 64-byte read per block. Mode 0 reads stay marginal, mode 1 reads lose one byte per back-to-back block; a logic analyzer is the next tool.
…or the night, the link-hang trace gated

The paragraph on the twenty-fourth try was in twice; the second copy goes. The small hours' section held tries 24-34 and the CP link analysis under the "fifteenth to twenty-third tries" heading, so they get their own. The trace at each BAR access in CPIF, written as a hands-free next step, is now G3-L1: attended, on the charger, with Expect, Stop, a cap on resets, Rollback and risk, and the tracing change on a kernel branch before it boots. It only runs if GNSS is resumed; the status line now says GNSS is parked. Placeholders mark where the bring-up branch and the partition check go.
They came before any GNSS step on the night of 10-29, so they belong in NOTES rather than inside MODEM-PLAN's GNSS section, where the maintainer found them hard to find.
W4HO-ham added a commit to W4HO-ham/omarchy-mobile that referenced this pull request Oct 29, 2026
The ten commits with G3's fifth to forty-fourth tries, the CP link hang and GNSS parked are reviewed on derekross#153 now, so this pull request goes back to fingerprint F6c-F10 and G3's third and fourth tries: MODEM-PLAN is the file as of 6fe8313 again.
M0.1's checksum check, run after the night's modem sessions and resets: all six protected partitions match the 10-28 backup, read-only and unmounted. Also how the test DTBs reached slot B.
…ile#138 now

Kernel derekross#135 went up without a sign-off and is replaced by derekross#138 with the same two commits; the parked paragraph links the live one.
Every variant that ran during G3's tries is now a commit on the owner's fork of the kernel (linux-omarchy-mobile#137, a draft), linked by commit from the plan so each try can be read next to its code.
@W4HO-ham

W4HO-ham commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor Author

Both of the points carried over from #138 are in now. The partition check is recorded (all six protected partitions match the 10-28 backup, read-only, unmounted), and the test code behind G3's tries is public as derekross/linux-omarchy-mobile#137 (draft, branch tegu-gnss-spi-bringup on my fork, head 8d77391d9), on top of the two kernel fixes (now #138 there): the gnssif_spi driver as ported, then one commit per variant in the order of the tries, the pdma1 probe and memcpy modules, the four test overlays, and the g7 scripts with the offline CRC checks. The plan links each by commit (cf9ff1c). One correction to what I wrote before: there was no separate USI3 mux-and-divider module; that code is the osc and div parameters inside gnss_spi, and the commit messages say so. Each test DTB went onto slot B through the kit's omamobile images and omamobile push; the palmtop is back on the gn3 DTB with the as-ported modules.

…derekross#113)

* device-raven, tools: haptics through feedbackd on the CS40L25A

The kernel side is derekross/linux-omarchy-mobile#114 (cs40l25-vibra, its
binding and raven's node). This is the rest:

- device/raven/kernel.config builds cs40l25-vibra as a module.
- extract-vendor-firmware -d raven stages the CS40L25A's files from the
  owner's factory image: the CLAB RAM firmware and the default wavetable,
  which the driver loads, and the CLAB configuration (braking), not
  loaded yet.
- device-raven's 72-omamobile-feedbackd.rules makes the motor a feedbackd
  vibra, as cheetah's CS40L26. The motor's input device appears only once
  its firmware has loaded, about 5 s into the boot, and feedbackd (D-Bus
  activated) only looks for it when it starts, so on a boot where
  something asked for feedback first there were no haptics until
  feedbackd was restarted. The motor's arrival now starts
  omamobile-feedbackd-rescan.service, which stops a running feedbackd;
  the next request starts it again with the motor.

HAPTICS-TORCH-PLAN records H5 and the boot race.

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

* device-raven 0.1.27: the haptics version bump

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Derek Ross <derekross@gmail.com>
@derekross

Copy link
Copy Markdown
Owner

Thank you for this. It's a remarkable night's work, written up so the next person can follow every step. Finding that the "hardfault" is gnssd's own watchdog, then tracing the link problems to USI3's clock and the 63 + 1 cut, turns GNSS on the 9a from a mystery into one well-defined SPI question. Parking it there, with the two kernel fixes posted, is a sensible call.

All the round 29 points carried over from #138 are in:

The policy check and CI pass. I found no identifiers and no vendor files, and nothing here writes outside slot B.

A few small things before merge:

  1. The rebase after device/tegu: fingerprint F6c-F10 (works) and GNSS G3's third and fourth tries #138. The description says the third and fourth try lines become identical to main once device/tegu: fingerprint F6c-F10 (works) and GNSS G3's third and fourth tries #138 merges. I tried it: I squashed device/tegu: fingerprint F6c-F10 (works) and GNSS G3's third and fourth tries #138 onto main and merged this branch on top, and MODEM-PLAN conflicts in two places (the status line, and where the fifth try starts). The fix is easy, because your MODEM-PLAN.md already contains everything device/tegu: fingerprint F6c-F10 (works) and GNSS G3's third and fourth tries #138 adds there. After device/tegu: fingerprint F6c-F10 (works) and GNSS G3's third and fourth tries #138 merges, rebase and resolve with your version of the file (git checkout --theirs device/tegu/MODEM-PLAN.md during the rebase). Or tell me, and I'll resolve it the same way when I merge.
  2. The status line says the clock and the cut "are fixed in the kernel (2026-10-29)". spi: s3c64xx, clk: zumapro: the Pixel 9a's GNSS SPI at stock's clock, without the 63+1 cut linux-omarchy-mobile#138 isn't merged yet, and I've asked for one change there, so please write "in spi: s3c64xx, clk: zumapro: the Pixel 9a's GNSS SPI at stock's clock, without the 63+1 cut linux-omarchy-mobile#138 (in review)". In the morning section, "commits on tegu-spi-word-pieces (kernel PR)" should name device/tegu: fingerprint F6c-F10 (works) and GNSS G3's third and fourth tries #138 too, since omamobile-fingerprint 0.1.11: touches in panel pixels, the circle lit before the capture, the refresh rate the HAL parses #135 is closed.
  3. The morning's kernel release. The morning's tries ran images built from the gn3 source with the two changes. Please add their uname -r, as the night's section has it.
  4. The partition check and the morning. The check at 10:20 covers the night. The morning's tries (35th to 44th) also ran modem sessions and had a few hard resets with nothing in pstore. If they came after 10:20, please run the same check once more and record it. If they came before, one line saying so is enough. The next modem session starts from this baseline, so it's worth having.
  5. The leftover private paths. Now that AGENTS: on the 9a, NFC needs the ST54L's NFC mode on (linux-omarchy-mobile#131), not a power-off hook #137 is public, a few places still point at copies nobody else can read. Please swap them for the commit ids you list at the end:
  6. A question about slot B. One bullet says the test DTBs went on through "the kit's omamobile images and omamobile push". The next says "bin/omamobile push (the kit's repo-push: dd into the _b partitions, sha256-verified, then reboot-to omamobile)". bin/omamobile has no repo-push, and our tools/repo-push publishes packages, so I'm not sure what "the kit" is. If it's our bin/omamobile push, please say so plainly, once. If it's a wrapper of your own, please say what it runs. The description matches push, so I don't expect a problem. I'd just like the plan to name the tool that wrote the phone.

Not blocking: the description still mentions the two placeholders as unfilled. It doesn't land on main, but an update would help anyone reading the PR later.

derekross and others added 3 commits October 29, 2026 14:51
Twenty-six lessons (L-318 to L-343) from the round 29 omamobile-reviewer
runs, and three corrections: C-20, our kernel derekross#109 advice that the
Pixel 7's SPI controller DMAs the touch report (it polls; gs201's spi_0
has no dmas); C-21, asking for FT3658=m in panther's device
kernel.config against RELEASES; C-22, a Bluetooth address in kernel
derekross#98's thread that the first review missed. Five candidates were dropped
as already covered.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…rary and the CP state it waits for (derekross#141)

* omamobile-modem 0.1.8, extract-vendor-chroot: gnssd's custom GNSS library and the CP state it waits for

On the 9a gps.cfg sets GlueLayer_IsUseCustomGnssLib, and gnssd dlopen()s libcustomgnss.so, which waits for ONLINE at /sys/bus/platform/devices/cpif/modem_state and then opens RIL's GPS channel through libsitril-gps and libsitril-client. The extractor left all three out, since nothing links them, and the chroot's /sys had only the device path, not its bus link. Neither fixes Kepler's engine-start fault yet.

* omamobile-modem 0.1.8: the extractor re-run, and the shared /sys bind

The extractor was run once more with this change on the owner's BP3A factory image: 195 files against the previous 188, nothing removed, every library resolved, nothing new to stub. The seven new paths are the three GNSS libraries and their closure (libbinder, libbinder_ndk, libapexsupport and the Samsung radioExternal NDK library). MODEM-PLAN's G3 section records that, and that an existing 9a chroot gets the libraries only when its owner re-extracts.

The second /sys bind is shared by every phone's modem profile. It is harmless on the 7 Pro and the 6 Pro: cbd never looks there.
The clock and the cut are in linux-omarchy-mobile#138, in review, not yet in the kernel; the status line and the morning's section say so. The morning's tries ran images with the night's release string, since the build fixes LOCALVERSION, so the plan names the Image files and their sha256 prefixes instead. The partition check at 10:20 came after the morning's tries, so it covers them. The private paths that were left (the realign tree on maclab, the g7 script, the drafted clock change, the offline tools on the laptop) now point at the public commits of linux-omarchy-mobile#137 and derekross#138. The tool that wrote slot B is named once, plainly: our bin/omamobile push, run by a local wrapper after bin/omamobile images.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Done in 9ec37d7, points 2-6; the rebase (1) waits for #138 to land and I'll resolve MODEM-PLAN with this branch's file then, or you resolve it the same way at merge, whichever comes first.

  1. The status line and the morning's section say the clock and the cut are in linux-omarchy-mobile#138, in review; omamobile-fingerprint 0.1.11: touches in panel pixels, the circle lit before the capture, the refresh rate the HAL parses #135 is mentioned only as the closed one it replaced.
  2. The morning's uname -r was the same string as the night's, 7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty, because the build fixes LOCALVERSION; the plan says so and names the Image files with their sha256 prefixes so the builds can be told apart.
  3. The morning's tries ran about 08:15-09:20 local, before the 10:20 check, so one line says the check covers them and their resets too.
  4. The four private paths are replaced by the commits of linux-omarchy-mobile#137 (the g7 scripts and the offline checks in 8d77391d9, the realign series b5229f35d..a0877abc3) and a "(later: device/tegu: fingerprint F6c-F10 (works) and GNSS G3's third and fourth tries #138)" for the drafted clock change.
  5. It was our bin/omamobile push every time, run by a wrapper of mine that first runs bin/omamobile images with the base DTB and the overlays; the plan says that once and the "repo-push" wording is gone.

The description is updated too: the placeholders are filled and the kernel fixes are #138 in review.

…th tries (derekross#138)

FINGERPRINT-PLAN F6c-F10: on the Pixel 9a the under-display sensor
captures GOOD frames once touches reach the HAL in panel pixels and the
circle is lit before the capture; the enrolled finger matches and other
fingers are refused. MODEM-PLAN G3: the third and fourth tries at the
GNSS SPI link. The later GNSS tries moved to derekross#153.

Co-authored-by: W4HO-ham <87742609+W4HO-ham@users.noreply.github.com>
…unter (derekross#157)

--suspend systemd runs the A/B drain cycles through systemctl suspend, so
sleep hooks (the 9a's NFC stop-poll) run; it refuses unless s2idle is the
mode that will actually run, and rejects unknown --suspend values, so a
phone without mem_sleep_default=s2idle can't enter deep with the cable out.
A gauge without charge_counter (the 9a's) is read through charge_now. The
default rtcwake mode is unchanged.

Co-authored-by: W4HO-ham <87742609+W4HO-ham@users.noreply.github.com>
…s hangs

Read offline from the ramoops consoles the palmtop keeps: the seven watchdog resets all end on the cp2ap_wakeup handler's toggle with the link cycling twice a second, one shows an RCU stall of three CPUs right as gnssd starts, one a doorbell parked because the link was down. That puts the hang in the window between the wake request and the link coming back, from a path that reads the modem's BAR while the PHY is isolated. G3-L1 gets a cheaper first step (hold the link up through a cpif parameter) and named trace points.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

One more commit, df8d568, from reading the morning's consoles offline (the palmtop keeps every ramoops console, and each one ends with the next bootloader's [PRE] RST_STAT). The 24 boots between 07:34 and 09:19 sort into eight curated-start fault resets, two dead-man reboots, six pushes and seven real hangs (CLUSTER0_NONCPU_WDTRESET). All seven hangs end on the same line: CPIF's cp2ap_wakeup handler flipping the line's trigger, with the link cycling twice a second before it, and the PHY out of isolation that should follow 5 ms later never comes. One console caught an RCU stall of three CPUs with no backtrace right as gnssd starts, another a doorbell parked with "PCI not powered on" just before. So the hang sits in the window between the wake request and the link coming back, from something that reads the modem's BAR while the PHY is isolated, as the cheetah gotcha says. It's written up before G3-L1, and G3-L1 now starts with a cheaper step: hold the link up through a cpif parameter for three sessions, which says whether the link is the cause before any trace is built. This also answers the question on #154: in the rfsd stage the watcher's open would wake a link with the CP off, which is this shape.

device/tegu/MODEM-PLAN.md conflicted on the status line: this branch's
file already carries everything derekross#138 added. It is resolved to this
branch's file, plus the "gnssd's custom GNSS library (2026-10-28,
omamobile-modem 0.1.8)" bullet that derekross#141 added on main, which this branch
never had and a plain checkout of its file would have dropped.
@derekross

Copy link
Copy Markdown
Owner

Thank you for 9ec37d7 and for the extra hours on the consoles. Points 2 to 6 from my last comment are all in: the status line and the morning section name derekross/linux-omarchy-mobile#138 as in review, the morning's images are told apart by their sha256 since the release string can't do it, the 10:20 check covers the morning's resets, the four private paths now point at the #137 commits, and the plan names bin/omamobile push plainly as the tool that wrote slot B. Thanks for updating the description too.

The rebase. #138 is on main now, and I've resolved the conflict as we agreed, with one change. When I suggested git checkout --theirs device/tegu/MODEM-PLAN.md, I had tested against a main from before #141 merged. #141 added a bullet to MODEM-PLAN, "gnssd's custom GNSS library (2026-10-28, omamobile-modem 0.1.8)", and your branch doesn't have it, so taking your file as a whole would delete it. Sorry for the bad advice. I'll push a merge commit to your branch that takes your file and puts that one bullet back where main has it. Nothing else changes, and the only conflict was the status line. Please pull it before you add anything, rather than rebasing with --theirs.

df8d568 is excellent detective work. Sorting the 24 consoles by RST_STAT and finding that every hang ends on the cp2ap_wakeup toggle, before "PHY out of isolation", narrows the hang down a lot. Two small things in it before I merge:

  1. The count. The line says "CLUSTER0_NONCPU_WDTRESET (seven, at 07:37, 07:42, 07:48, 07:51, 08:45, 08:52, 08:56, 09:09)". That's eight times, and eight plus two plus six plus seven only comes to 23 of the 24 boots. So I think it's eight hangs. If one of those times doesn't belong there, please drop it instead.
  2. The hold-link step and G3-L1. The new section says G3-L1 should start with a cheaper step: a cpif parameter that keeps the link up, then three 12-second sessions. The G3-L1 paragraph itself still describes only the trace, though. That step boots a changed modem kernel and runs sessions that might hang the SoC, so please say in G3-L1 that it runs first under the same frame: M0.1 before and after, attended on the charger, kmsg to the laptop with --watchdog, the same stop rule and rollback. Please also say whether its sessions count toward the cap of three. One sentence will do. GNSS is parked, so nothing runs soon, but this is the text the next person will follow.

Not blocking:

After those two, this merges, and #154 follows right after it. Thanks again for a record this thorough.

…from the sources

Stock's node (swap-mode, 3.125 MHz, feedback delay 0, no chip-select-mode property) and Google's driver default of automatic chip select mean stock drives nCS from the controller with a two-clock gap, in PIO, with 32-bit words and the controller's swap; our port uses manual native chip select and feedback delay 2, and auto chip select was tried only at the wrong clock with 32-bit words. The next boot when GNSS resumes is that combination at stock's clock, 8-bit first.
…L1's frame

The count was wrong by one (eight watchdog resets, the eight times listed). G3-L1 now says its first step, the link held up through cpif's keep_link_up, runs under the same frame and counts toward the same cap; the watcher is named as derekross#148 in review, and the partition check's span is the consoles' (07:34 to 09:19).
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Thanks for the merge commit; I pulled it before adding anything, and the #141 bullet is intact. Both points are in at d46d6de: eight hangs (the eight times listed; the count was the typo), and G3-L1 now opens with the hold-the-link step under the same frame (M0.1 before and after, attended on the charger, kmsg with --watchdog, the same Stop and Rollback), its sessions and any hang counting toward the same caps. The two small ones too: the watcher is named as #148 in review, and the partition check's span is the consoles' (07:34 to 09:19). One more paragraph went in just before (4f1e95a): stock's SPI configuration for this link read from the sources, which turns out to be automatic chip select, feedback delay 0 and 32-bit words with the controller's swap, in PIO; our port runs manual chip select and delay 2, and auto chip select was tried only at the wrong clock, so that is the first boot when GNSS resumes (G3-A). The cpif keep_link_up build for G3-L1's first step is on my fork (tegu-cpif-keep-link, 3f76f123b) and staged on the palmtop; nothing boots until the owner is at it.

The reset boot's last 34 s match the surviving boots around it to the tenth of a second and end right after bluetoothd and hostnamed start; the 120 s Bluetooth dead-man was not it and the audio script had not acted yet. The journal has nothing more, and the console of that reset is gone.
@derekross
derekross merged commit df072c7 into derekross:main Oct 30, 2026
2 checks passed
@derekross

Copy link
Copy Markdown
Owner

Thank you, both points are in at d46d6de, and thanks for pulling the merge commit first.

  • The count: the line now says eight, which matches the eight times listed and brings the boots to 24.
  • G3-L1: the paragraph now starts with the hold-the-link step, under the same frame as the trace: M0.1 before and after, attended on the charger, kmsg with --watchdog, the same Stop and Rollback. It also says its sessions and any hang in them count toward the same caps. I read 3f76f123b on your fork as well. keep_link_up is off by default, and it skips only the power-off the CP asks for, so a forced power-off still runs. That's the right shape for a bring-up parameter.
  • The two small ones are in too: omamobile-modem 0.1.9: watch the CP state on one open file #148's watcher is named as in review, and the partition check now covers the 07:34-09:19 boots.
  • omamobile-modem 0.1.8, extract-vendor-chroot: gnssd's custom GNSS library and the CP state it waits for #141's "gnssd's custom GNSS library" bullet is still there. Against main, the only line the file removes is the old status line.

The stock SPI paragraph (4f1e95a) is a useful read. Automatic chip select, feedback delay 0 and the controller's swap explain why no earlier try matched stock, and G3-A is a sensible first boot when GNSS resumes. The journal read of the 03:03 reset in NOTES is careful too.

One optional wording point, for whenever you next touch the file. The hold-the-link step runs three sessions, and those count toward a cap of three, so on paper the trace has nothing left. And "waits for the next day" reads differently from the Cap line's "then the step is closed". If you meant the cap per day, saying so in the Cap line would settle it. Nothing runs while GNSS is parked, so this doesn't hold the merge.

CI is green on 1600fc6, and it merges cleanly with main. I'm merging this now, with a squash message I've written by hand, so the early commit lines ("the clock and the cut fixed") don't land as if the fixes were in the kernel. #154 follows straight after. Thanks again for such a thorough record.

derekross pushed a commit that referenced this pull request Oct 31, 2026
Power, volume keys and the touchscreen run on the Pixel 8 Pro with the zuma ALIVE pin controller, gpio-keys and the touch stack from linux-omarchy-mobile #148 and #153 (test tags b, b2, c5, c6 on the author's fork). DEVICES marks them testing.
greenbrettmichael added a commit to greenbrettmichael/omarchy-mobile that referenced this pull request Oct 31, 2026
kernel derekross#156's Wi-Fi needs CONFIG_PHY_ZUMA_PCIE, a zuma-only PHY, so it
goes in husky's fragment. On a kernel without derekross#156, olddefconfig drops
the unknown symbol and nothing else changes (checked on omamobile with
derekross#153).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Brett-Michael Green <brett@bmgvisualtech.com>
derekross added a commit that referenced this pull request Oct 31, 2026
… rounds

L-348 to L-361: shared drivers judged against every int-line user (#150),
board pins against every stock user (#151), ownership flags under the
consumer's lock (#152), /chosen children and Google's panel constants
(#154), same-day notes PRs on one device (#208/#209), merge simulations for
DEVICES rows, ours included (#165), stacked PRs that merged main (#115/#117),
titles behind renumbered versions, a contributor merge that dropped the PR
(#99), smoke package lists as provenance and "owner-authorized" writes
(#200), promised fixes and named tags checked on the remote (#153/#157/#158),
and file swaps into old packages (#193). C-23 (usbc-deadman's device scope,
kernel #107) and C-24 (BNEP in a lynx-only fragment, #98).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Nov 1, 2026
…s on the 7 Pro (#254)

Kernel #153 (husky touch), #166 and #133 and omarchy-mobile #149 (panther touch) merged on 2026-10-31 and 11-01, and omamobile-audio 0.5.8 raised the 7 Pro's default speaker gains under verified protection. The website's device pages are built from this file.

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
…th tries (derekross#138)

FINGERPRINT-PLAN F6c-F10: on the Pixel 9a the under-display sensor
captures GOOD frames once touches reach the HAL in panel pixels and the
circle is lit before the capture; the enrolled finger matches and other
fingers are refused. MODEM-PLAN G3: the third and fourth tries at the
GNSS SPI link. The later GNSS tries moved to derekross#153.

Co-authored-by: W4HO-ham <87742609+W4HO-ham@users.noreply.github.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
… and GNSS parked (derekross#153)

MODEM-PLAN's GNSS section from the night of 10-28 into 10-29. The "KEP
M7 HARDFAULT" at every engine start is gnssd's soft watchdog resetting
Kepler because the CHPP link over the GNSS SPI loses bytes. Two kernel
causes were found, USI3 stuck on the 399.36 MHz parent and spi-s3c64xx
cutting a full-FIFO transfer into 63 + 1 bytes; both are in
derekross/linux-omarchy-mobile#138, in review. With them, mode 0 is
marginal and mode 1 loses the first byte of each back-to-back block.
Stock's SPI setup, read from its device tree and Google's driver, is
automatic chip select, feedback delay 0 and the controller's byte swap,
in PIO; no try has run that at stock's clock, so it is the first boot
(G3-A) when GNSS resumes. GNSS is parked at the owner's decision. Every
try links its commit on derekross/linux-omarchy-mobile#137.

The CP link hang stays open. The morning's 24 ramoops consoles hold
eight watchdog hangs, each ending between the cp2ap_wakeup edge and the
link coming back, while the link cycles quickly. G3-L1 (attended, on the
charger, capped, M0.1 before and after) first holds the link up with a
bring-up cpif parameter, then traces CPIF's BAR accesses. The six
protected partitions matched the 10-28 backup after the night's and
morning's boots. NOTES records two resets at about 34 s after Bluetooth
started, the 03:03 one read back from the journal.

Test images reached slot B through bin/omamobile push only.

Co-authored-by: W4HO-ham <87742609+W4HO-ham@users.noreply.github.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…ross#208)

Power, volume keys and the touchscreen run on the Pixel 8 Pro with the zuma ALIVE pin controller, gpio-keys and the touch stack from linux-omarchy-mobile derekross#148 and derekross#153 (test tags b, b2, c5, c6 on the author's fork). DEVICES marks them testing.
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
… rounds

L-348 to L-361: shared drivers judged against every int-line user (derekross#150),
board pins against every stock user (derekross#151), ownership flags under the
consumer's lock (derekross#152), /chosen children and Google's panel constants
(derekross#154), same-day notes PRs on one device (derekross#208/derekross#209), merge simulations for
DEVICES rows, ours included (derekross#165), stacked PRs that merged main (derekross#115/derekross#117),
titles behind renumbered versions, a contributor merge that dropped the PR
(derekross#99), smoke package lists as provenance and "owner-authorized" writes
(derekross#200), promised fixes and named tags checked on the remote (derekross#153/derekross#157/derekross#158),
and file swaps into old packages (derekross#193). C-23 (usbc-deadman's device scope,
kernel derekross#107) and C-24 (BNEP in a lynx-only fragment, derekross#98).

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
…s on the 7 Pro (derekross#254)

Kernel derekross#153 (husky touch), derekross#166 and derekross#133 and omarchy-mobile derekross#149 (panther touch) merged on 2026-10-31 and 11-01, and omamobile-audio 0.5.8 raised the 7 Pro's default speaker gains under verified protection. The website's device pages are built from this file.

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.

3 participants