Исследования
На что смотрели, прежде чем действовать: вопрос, что нашли и на чём это стоит.
How should a device declare what it needs (its pieces, [host]) so the compiler and rust-analyzer check it: typed Rust per device, TOML with a generated schema, or serde as now?
The author's question (2026-11-18, via the coordinator): no config files if possible - declarations rust and LSP-workable, relatable by machine, not in someone's head or a drifting manual. What is: device.toml is read by three crates in three shapes - devlab/src/device.rs (no deny_unknown_fields at the top or in flash, overlay, provision, install, connection: a misspelled [[flash.overlays]] is silently ignored, though the template's header says unknown fields are refused), host/src/lib.rs ([device] codename, [host] strictly, [tools] lpoco and [fastboot] serial loosely from a toml::Value) and bringup/src/boot.rs ([boot] only); no one declaration says what the file may hold. argenv (rust-with-argenv) declares an input once in code as the accessor and projects it to a published contract; its README names a hand-written sidecar schema as what drifts. Research bringup-home-follow-and-rhizoid: a tool is followed by a pin, device parts live beside it as data, hooks, or a rust-script on the pinned library; decision 2026-11-17-the-phone-is-data keeps device labs data only. Options. (A) A typed Rust declaration per device (a crate of consts the tool links, or a rust-script on the pinned lpoco library): rename and go-to-definition across devices, errors at build - but every device change becomes a build of the device's code at the lab, the device crate pins a 0.x library, the lab would run code from each device repository, and the-phone-is-data is reversed. (B) TOML whose schema is projected from one set of Rust types (schemars, draft-07; deny_unknown_fields becomes additionalProperties false, doc comments become hover text), published per lpoco release, named on the file's first line (#:schema, taplo / Even Better TOML: completion, validation, hover), checked in CI of lab-tools (the committed schema equals the types) and of each device repository (its device.toml against the pinned schema) - the argenv way for a file: declared in code, projected, never written twice. No jump from a TOML key to its Rust field (JSON Schema carries no source location); x-taplo links can point at the field's docs. confique adds a template generated from the types (the device-template file cannot drift) but no schema, and would rewrite the types. Kconfig is the same split (typed schema, plain values, a checker); Nix modules check at evaluation. (C) Today: caught at load time, on the lane, after merge - or not at all where no deny_unknown_fields stands. Finding: B gives the machine-checked part of the author's ask at a day's cost and keeps device repositories data; A gives rename at the price of a build and foreign code per device change. What is a piece (its files, path, version) belongs in Rust in the roof; a device only names roof pieces by token, as argenv's allowed TOKENS.
- schemars: JSON Schema from Rust types - orchestration-renewed deny_unknown_fields becomes additionalProperties false, doc comments become descriptions; draft07 setting; already in lab-tools' Cargo.lock through rmcp
- taplo: #:schema directive and schema association - orchestration-renewed a TOML file names its JSON Schema on its first line; editors complete and validate it; x-taplo links on keys
- Kconfig language - orchestration-renewed a typed schema in one place, values in defconfig, checked by the tool: schema and values apart, checked together
- confique: typed config with a generated template - orchestration-renewed a commented template TOML generated from the Rust type: the template cannot drift; no JSON Schema
- argenv README: the approaches, and why this one - orchestration-renewed declare in code as the accessor, project to a published contract; a sidecar schema written by hand drifts
2026-11-18
Where does orchestration's work stand, for a fresh orchestration session to take it up without this session's long context?
ROLE: orchestrator (brief ideal-agent-linux-phone-oco/orchestration.md). This session (orchestration-lpoco-roof) ran 2026-11-17 evening to 2026-11-18 morning; it hands over at its size. DONE, each landed and read back from main: - The lpoco roof (decision 2026-11-17-bringup-in-lab-tools): dispatcher (lab-tools #83), bringup image v0 (#85), rename to lpoco-lab/lpoco-tone with the old names kept as second [[bin]] (#86), one MCP door (#87), pin and hooks (#88), install from tag (#90). - lpoco host (decision 2026-11-17-lpoco-host, amended: 51-android.rules kept): #91, --help (#93), script tools by rev stamp (#95), reads device.toml from origin/main (#108). lab.toml in grenudi/lab-machine (#36, pins in #37-#43). - Then: lpoco-lab argenv (#98) and env through the contract (#103); tone argenv (#101); names sweep (lab-tools #99, #100, #104; docs #400; device-template #12; surya-lab #166; google-walleye-lab #100); suspend-irq-quiet check (#106, the surya lane's item); bringup image swap (#110), initramfs (#114), bisect (#123). - Releases: the family is one version. Changelog-only releases and the release loop are fixed (#112, #116, #119), and one release PR writes every changelog (#121). Proven live: v0.3.8 #122 and v0.4.0 #124, main green, no follow-up. - The lab: lpoco host prepare now installed the family at 0.3.8, land at 66a3144 and agent-env with rev stamps; devlab-watch@surya-lab was restarted in surya's window; lpoco host check has no FAIL. Rollback copies: ~/.local/bin/devlab-0.1.0, devlab-0.2.1, devlab-0.2.2, land-7e740e2. - land (lab-machine): refuses to run traced (#35), and every stop says why, with a rebased change branch pushed with a lease (#41). - docs: lane queries retired (decision 2026-11-17-docs-serves-no-lane); waits naming items became blocked_by; backlog-status and backlog-needs refuse a write that matches no item (sign status-write-matched-no-row); briefs in head form (patrol.md, builder.md, phone-keeper.md with walleye folded in, feature-research.md; #389); surya's watchdog in phone-keeper.md; the patrol's stored prompt rewritten (no ocoeco, read-only, signs to the owning base, reports to the Top Coordinator). HOW THE LINE RUNS: the coordinator's stored task lab-tools-builder takes the open lab-tools row with needs=build, its blocked_by done, lowest rank then oldest; it builds test-first, lands, records and reports. Rank the rows, run_scheduled_task, read each landing back from main, then land --release in a lab-tools worktree of your own and watch main's CI. A lanes-waker every 30 minutes nudges when the queue has work and nothing runs. A run often ends without a report: read main and the row yourself. The lab host is orchestration's to keep (the coordinator, 2026-11-18): change it only by bumping lab.toml's pins and running lpoco host prepare now (plan first; stop on any root command) in a surya idle window that the surya coordinator names, then restart devlab-watch@surya-lab. OPEN: lpoco-host waits on its tty half (walleye's pk5l, then the keeper opens /dev/ttyACM0 as the lab user; the block half passed, walleye lab #70). The lab-tools build queue is empty. Walleye's bisect series and retiring build-bisect.sh/check-bisect.sh are the walleye lane's; I offered a 0.4.0 move in a walleye window. The lab is at 0.3.8, release v0.4.0 is out. oco-work has no living repository to pin. The older owed items of orchestration-2026-11-17-late (derive-parts-in-base, about-across-bases, device-template-follow, docs-phone-items-to-lanes) still stand. SIGNS: a launcher run's status write once never reached main (fixed in the record); a launcher run counted as running while it waited on lanes (tell it to end); cargo warns that devlab and tone main.rs are in two bin targets (gone with the aliases); two sessions answer to "orchestration", so a builder could not message it; the lab host has a stray ~/.local/.crates.toml from cargo --root ~/.local, which is expected. DO NOT UNDO: release-plz.toml's release_commits and changelog_include (one release PR per version, no loop); the devlab and tone aliases while the lanes' scripts call them; 51-android.rules.
2026-11-18
Where do phone-side pieces stand, and what is next?
How it stands, 2026-11-18. Decided, not built: decision 2026-11-18-phone-side-pieces-under-the-roof (research phone-side-pieces-landscape) and decision 2026-11-18-device-manifest-schema-from-rust (research device-declaration-typed-landscape, the author's question of declarations a machine relates). Inventory of 20 pieces and the failing test's full text: research/phone-side-pieces/2026-11-18/inventory.md. Queue, unranked, for the author: lab-tools phone-side-pieces (umbrella), phone-pieces-drift-named (its test host/tests/phone_pieces.rs written first - not landed, lab-tools has no ignored-test convention and it cannot compile before the function), health-reports-pieces, lpoco-awake, manifest-one-schema, bringup-generic-init; surya-lab surya-awake-from-package (phone, after lpoco-awake), surya-manifest-schema; google-walleye-lab walleye-manifest-schema, walleye-init-from-roof; device-template template-manifest-schema; upstream items sxmo-autosuspend-backoff, sxmo-suspend-stop-by-profile, qcom-wdt-armed-in-suspend (each waits on the author's word). device-template's own dt-usb-awake is answered by lpoco-awake and left to its owner. Today surya still runs the hand-put copy of PR 205/208; nothing names it stale until phone-pieces-drift-named and health-reports-pieces land. Not known: whether walleye's kernel has CONFIG_PM_WAKELOCKS (the awake piece needs it when walleye runs a rootfs); whether taplo takes schemars' draft-07 output for [[array]] tables unchanged (a ten-minute try in manifest-one-schema).
- surya-lab PR 195: hold the devlab-usb wake lock always; autosleep-off check - orchestration-renewed the keep-awake changed on main while the phone ran the 2026-11-10 flashed copy
- surya-lab PR 205: devlab-usb-awake provisioned on surya, hand-over - orchestration-renewed the fix reached the phone by hand, with nothing to tell the next change it stays current
2026-11-18
What phone-side pieces exist across surya-lab and google-walleye-lab, which belong under lpoco's roof, how is an installed copy kept in line with main, and what goes upstream (sxmo, postmarketOS)?
What is (origin/main of surya-lab, google-walleye-lab, lab-tools, device-template, 2026-11-18; neither phone touched). Phone-side pieces reach a phone by five routes, only one versioned: [[flash.overlay]] into the image at flash, [[provision.install]] over ssh, [health] checks copied by suite put, lpoco lab phone put or by hand, and the lpoco-health apk from the signed lab-tools repository (the only one with a version - and nothing compares that version to a pin). walleye's pieces live in its boot image (fastboot boot, nothing written), so they cannot drift on the phone. Inventory, 20 pieces, in the material: roof-worthy are surya's keep-awake (lab/devlab-usb-awake + unit), its autosleep-off check, the way back (already lpoco-health suspend), walleye's bring-up init (configfs gadget ECM/ACM/mass storage, udhcpd, telnetd) and its FunctionFS ACM console (ffs-acm-rs), and the gadget host checks; per device stay the call uplink, PD mapper softdep, UCM and q6voiced files, tas2562 module, edge repository line, mobile connection, sensors helper, masks, and the phone's own checks. Today's case: surya ran the 11-10 flashed copy (PR 40, lock only while configured) after PR 195 made it held always; a USB blip let sxmo_autosuspend.sh suspend the idle phone; PR 205 put the fix by hand; PR 208 changed it again, and autosleep-off.sh's only drift check is grep bt_unsafe on the installed file. Others: sxmo blocks suspend by any kernel wake lock (the wakeup_count handshake) and by sxmo_hook_block_suspend.sh (ssh on port 22, calls, hotspot, a nosuspend file; no USB-gadget reason); a failed suspend is retried every 1 s with no backoff - the loop that drops the link; sxmo_suspend.sh stops hexagonrpcd sensorspd for one device by name; sxmo stamps each installed hook with a configversion hash and compares at migrate. postmarketOS: device packages carry device config, not lab tools; pmbootstrap sideload is its route for an unrepositoried package; apk audit sees edits only to packaged files. Mobian: logind inhibitors for the session's life. Kernel: wake_lock NAME [timeout] blocks autosleep and sxmo alike; a dwc3 gadget registers no wakeup source, so a cable alone does not keep a phone awake. Finding: what makes an installed piece checkable is that it has an identity the host can compare - a package version against a pin, or the git blob id of the file against origin/main's; a stamp written beside a piece says what was written, not what is there. The keep-awake must be held by the phone itself (the link is what fails), so a host-renewed timed lock cannot replace it.
- sxmo-utils scripts/core/sxmo_autosuspend.sh, sxmo_suspend.sh, sxmo_wakelock.sh (868b5c9) - orchestration-renewed wakeup_count handshake blocks on any wake lock; a failed suspend is retried after sleep 1 with no backoff; sxmo_suspend.sh stops hexagonrpcd-adsp-sensorspd for google,b4s4-sdm670 by name
- sxmo-utils configs/default_hooks/sxmo_hook_block_suspend.sh and the hooks PATH (sxmo_init.sh, sxmo.7) - orchestration-renewed suspend blocked by ssh on port 22, calls, hotspot, sxmo.nosuspend; no USB-gadget reason; hooks overridden per device by ~/.config/sxmo/hooks/DEVICE
- sxmo-utils setup_config_version.sh and sxmo_migrate.sh: configversion stamp - orchestration-renewed a hash stamped on line 2 of each installed hook, compared at migrate: sxmo's own drift check of installed copies
- Linux ABI: sysfs-power wake_lock, wake_unlock, autosleep - orchestration-renewed wake_lock NAME [TIMEOUT_NS], needs CONFIG_PM_WAKELOCKS and CAP_BLOCK_SUSPEND; autosleep and the wakeup_count handshake both refuse to suspend while one is held
- apk-audit(8) - orchestration-renewed installed files compared with the package database (U changed, X deleted); an unpackaged file in /usr/local cannot be audited
- pmbootstrap usage: sideload - orchestration-renewed build a package and apk add it on a phone over ssh: pmOS's route for a package not in a repository; no test-provisioning package exists in pmaports
- Mobian wiki: Tweaks (gnome-session-inhibit for ssh) - orchestration-renewed Mobian keeps a phone awake for ssh with a logind inhibitor that lives as long as the session: no kernel wake lock
- surya-lab PR 195: hold the devlab-usb wake lock always; autosleep-off check - orchestration-renewed the keep-awake changed on main while the phone ran the 2026-11-10 flashed copy
- surya-lab PR 205: devlab-usb-awake provisioned on surya, hand-over - orchestration-renewed the fix reached the phone by hand, with nothing to tell the next change it stays current
2026-11-18
Which watchdog can bring back a phone whose suspend never returns, and in what form upstream (linux-watchdog) would take it
Question: a way back from a suspend that does not return - the phone resets instead of hanging - that holds on the real suspend path and that upstream would take. What is. qcom-wdt (the APSS watchdog) stops in its late suspend callback since 2019 (to avoid resets when resume comes late). surya-lab's lab-only module parameter keep_armed_in_suspend skips that stop: it bit in s2idle cycles started by rtcwake -m freeze (proven 3+ times) but not in try 4, a real systemctl suspend, where the phone stayed down an hour with no reset (surya-unreachable-after-try4). The vendor's GPL drivers, read as observed behaviour, say why: the APSS watchdog counter freezes when all cores are suspended / the deepest low-power mode is entered (watchdog_v2.c 'qcom,wakeup-enable' commit; Sony qcom_wdt_core.c). So the APSS watchdog catches a CPU stuck while running, not a system asleep with nothing waking it. Upstream's stance. The same idea for imx2_wdt (fsl,wdt-continue-in-low-power, Dec 2025 / Jan 2026) was refused: Guenter Roeck - a watchdog reset of a suspended system makes no sense, a system that must not suspend must not suspend; Krzysztof Kozlowski - it is OS policy, not for DT. A module parameter is the same policy in another form. What has precedent: a running watchdog whose early (pretimeout) interrupt is a wake IRQ (stm32_iwdg, ma35d1_wdt: wakeup-source + dev_pm_set_wake_irq). The better watchdog. The PMIC's own (pm8916_wdt, qcom,pm8916-wdt, child of the PON) counts on the PMIC's sleep clock outside the sleeping SoC, and its bark is a PMIC interrupt, which wakes the system as the power key does. The second-generation PON (pm8998, pm6150 = surya, pm8998 = walleye, compatible qcom,pm8998-pon) keeps the same registers 0x54-0x58 in PON_HLOS and moves POFF_REASON1 to 0xc5 (vendor qpnp-power-on.c); qcom,pon.yaml already allows a watchdog child for every PON. Mainline uses it only on pm8916; no one proposed it for gen2. Vectors: (A) PMIC watchdog kept running through suspend only when its bark may wake the system (DT wakeup-source = capable; power/wakeup = the user's policy, off by default) and a pretimeout is set: the bark wakes the system, the driver pets it, a system that cannot come back is reset by the bite pretimeout seconds later - a sleeping system that can wake is never reset, which answers Roeck; the policy is in sysfs, which answers Kozlowski. (B) the same on qcom-wdt with its bark as a wake IRQ - useless if the counter freezes. (C) keep the module parameter, lab only - does not cover the real path (try 4). (D) first learn what try 4 was (a sleep with no wake vs a wedged resume) - free at the next attended window, and (A) answers both. Chosen (A), (C) stays for s2idle tries until (A) is proven, (D) folded into the proof (the PMIC bark wakes a sleep with no wake; the bite resets a wedged one). Written (fork-linux, local worktree ~/Projects/linux-phone-oco/linux-topics, branch topic/pmic-wdt-wake-in-suspend on v7.3): 1 dt-bindings qcom,pm8998-wdt + wakeup-source; 2 pm8916_wdt gen2 POFF reason via match data; 3 keep running through suspend when may wake (wake IRQ, pet in suspend, pet a bark while suspended instead of notifying the pretimeout governor, pet on resume); 4 pm6150/pm8998 dtsi nodes, disabled (bark interrupt <0x0 0x8 6>, the pm8916 index - unverified on gen2). Built with LLVM W=1 clean, checkpatch --strict clean but for the trailer, binding passes dt-doc-validate and yamllint; RFC until the phone proves it. Unknowns, each settled by the proof: can HLOS write PON_HLOS 0x854-0x858 (or is it secure-owned); the gen2 bark bit and interrupt index; POFF_REASON1 bit 2 on gen2; whether the bark wakes from suspend through PDC. Test: tests/pmic-wdt-way-back.sh (check, bite, wake) in this folder, tests pmic-wdt-bites and pmic-wdt-wakes-in-suspend.
- watchdog: qcom: Add suspend/resume support (Sai Prakash Ranjan, 2019) - upstream-forks-research, 2019 Why qcom-wdt stops in late suspend: unwanted resets when resume comes after a long time
- Guenter Roeck on imx2_wdt fsl,wdt-continue-in-low-power (Dec 2025) - upstream-forks-research, 2025 A watchdog reset of a suspended system makes no sense to the watchdog maintainer; a system that must not suspend must not be let suspend
- Krzysztof Kozlowski on the same series (Jan 2026) - upstream-forks-research, 2026 Keeping a watchdog running in suspend is OS policy, not for DT: refused as a DT property
- Vendor GPL watchdog_v2.c, LineageOS sm6150 tree - upstream-forks-research Observed behaviour: qcom,wakeup-enable leaves the APSS watchdog enabled in suspend, petted once; its commit says the counter freezes when all cores are in suspend
- Vendor GPL qcom_wdt_core.c, Sony K.P.4.0 - upstream-forks-research The APSS watchdog counter freezes when the deepest low power mode is entered - why it cannot catch a suspend that never wakes
- Vendor GPL qpnp-power-on.c, LineageOS sm6150 tree - upstream-forks-research Gen2 PON keeps the PMIC watchdog at 0x54-0x58 (S2_CTL2 BIT(7) enable) and moves POFF_REASON1 to 0xc5; its bark is the pmic-wd-bark interrupt
- Linux drivers/watchdog stm32_iwdg.c and ma35d1_wdt.c: the early interrupt as a wake IRQ (wakeup-source) - upstream-forks-research Accepted shape: a watchdog bark (pretimeout) declared wakeup-source, set as the device's wake IRQ, so a running watchdog wakes the system instead of being stopped
- Linux Documentation/process/coding-assistants.rst - upstream-forks-research An AI agent adds no Signed-off-by; the human adds his and an Assisted-by: LLM tag; say what could not be built or tested
2026-11-18
The best fix for sxmo's 1 s suspend retry and for its device-named service stop around suspend, as upstream would take them
Upstream now (sxmo-utils master 1fd7822): sxmo_autosuspend.sh reads /sys/power/wakeup_count (blocks until no wakelocks), runs the block-suspend hook (cached 10 s), writes the count, calls sxmo_suspend.sh; on failure it sleeps 1 s and loops - no backoff, while sxmo_hook_block_suspend.sh already backs off its own blockers 1..45 s. sxmo_suspend.sh stops hexagonrpcd-adsp-sensorspd only when SXMO_DEVICE_NAME is google,b4s4-sdm670 (921fa1e, 2024, its message: not fond of device code in core, the generic solution was not recommended); it is never started again. A presuspend hook existed until 89a77e6 (2023, the move to /sys/power/wake_lock). Prior art. Backoff after failed suspends: nothing on sxmo-devel or in the history (2691b8c, 2023, made the slow checks run rarely for the same reason: they made suspend fail). Services around suspend: proycon's 2024 patch (SXMO_SUSPEND_SERVICES stopped in sxmo_suspend.sh, started after wake) was turned down by Aren Moynihan the same day because the stop runs after the wakeup count is read: any wakelock meanwhile (the LED blink takes one every 2 s) makes the written count stale and the suspend abort, so a slow stop means never suspending; device code in sxmo_suspend.sh is a last resort citing its bug. pmaports fixed the Pixel 3a for elogind with a system-sleep hook (MR 5400) and pmOS's systemd unit conflicts with suspend.target, but Sxmo suspends with rtcwake past both, so neither runs under Sxmo. surya (systemd) has its sensors daemon stopped by suspend.target and started by the lab's devlab-sensors-resume hook; under Sxmo nothing does either. Ways: (a) a profile list stopped inside sxmo_suspend.sh - turned down 2024; (b) suspend through logind/systemd (rtcwake -m no for the alarm, then systemctl/loginctl suspend) so distro sleep hooks run - generic, but asynchronous (sxmo measures the time slept and runs postwake after rtcwake returns), the same wakeup-count race for the hooks' time, and the lab's systemctl suspend path is the one surya never came back from (try 4); (c) the profile list stopped by sxmo_autosuspend.sh after the blockers and before a SECOND read of the wakeup count, so the stop's time cannot make the count stale, started again after the suspend whether it succeeded or not - answers the 2024 objection exactly, moves the Pixel 3a case into its profile and needs a doas rule per service. Chosen (c). Backoff: double from 1 s per failure in a row to SXMO_SUSPEND_RETRY_MAX (64 s), reset after a success. Written (fork-sxmo-utils, local clone ~/Projects/linux-phone-oco/sxmo-utils-topics): topic/sxmo-autosuspend-backoff 2bb2500, topic/sxmo-suspend-stop-by-profile 1156bb6 (on the backoff), topic/sxmo-surya-sensors-suspend 6432ef9, lab = 6432ef9; series files in this folder's patches/sxmo-utils. Test: spec/scripts/core/sxmo_autosuspend_spec.sh, 6 examples driving the loop with mocks (waits 1 2 4 .. 64 64; cap; reset after success; stop, second read, write, suspend, start; start after a failed suspend; no services: one read) - all 6 fail on master's script and pass on the series; shellcheck and editorconfig clean (the suite's 27 other failures are the host's, the same without the series).
- sxmo-utils scripts/core/sxmo_autosuspend.sh, sxmo_suspend.sh, sxmo_wakelock.sh (868b5c9) - orchestration-renewed wakeup_count handshake blocks on any wake lock; a failed suspend is retried after sleep 1 with no backoff; sxmo_suspend.sh stops hexagonrpcd-adsp-sensorspd for google,b4s4-sdm670 by name
- sxmo-utils configs/default_hooks/sxmo_hook_block_suspend.sh and the hooks PATH (sxmo_init.sh, sxmo.7) - orchestration-renewed suspend blocked by ssh on port 22, calls, hotspot, sxmo.nosuspend; no USB-gadget reason; hooks overridden per device by ~/.config/sxmo/hooks/DEVICE
- sxmo-devel 2024: allow stopping system services prior to suspend (proycon), turned down by Aren Moynihan - upstream-forks-research, 2024 A service list stopped inside sxmo_suspend.sh was refused: after the wakeup count is read any wakelock (an LED blink every 2 s) aborts the suspend, so slow stops make it never suspend; device code in sxmo_suspend.sh is a last resort citing its bug
- pmaports !5400 and !7303: stop sensorspd before suspend (Pixel 3a) - postmarketOS, 2024 The helper is needed only while the ADSP asks for its registry; the units Conflicts=suspend.target, stop-only: nothing restarts them after resume, by design.
- pmaports, google-sargo: hexagonrpcd's sensors helper stopped before suspend, the DSP crashing otherwise -
- Sxmo: contributing - upstream-forks-research git send-email to ~mil/sxmo-devel@lists.sr.ht, rebased on master, prefix PATCH sxmo-utils, vN for resends; CI runs make test (shellcheck, shellspec, editorconfig) on each mailed patch
2026-11-18
What forks of the projects we patch exist, what git-rhizoid needs to carry them without rebase pain, how postmarketOS phones would run them, and each list's patch etiquette
The author's direction (via the coordinator): forks of each project we patch "under grenudi", used instead of upstream, the best fixes worked there per project, and only then mailed upstream as concrete working patches; git-rhizoid weighed again. What exists. Under the user grenudi: no phone fork at all (gh repo list grenudi: ideal-agent, ideal-knowledge-base, lab-machine and personal repos). Under the org linux-phone-oco (the author's): sxmo-utils, a mirror of git.sr.ht/~mil/sxmo-utils (sourcehut cannot be forked on GitHub; branches master and deviceprofile/xiaomi-surya, the latter upstream since 1fd7822 'accepted, thank you'), sxmo-deviceprofiles (the sxmo place with its records in docs), and linux, a GitHub fork of sm7150-mainline/linux carrying fix/, dt/ and test/ branches (tas2562, WCD, LPI) with the series kept in ~/Projects/linux-phone-oco/upstream-queue. surya-lab carries a lab-only patch file (patches/qcom-wdt-keep-armed-in-suspend.patch) built as an out-of-tree module by sleep/build-wdt.sh. So the forks the direction asks for exist; what is missing is a rule for their branches and a way for the phones to run them. git-rhizoid. Concepts fit: a cutting is an owned fork; the tracking branch mirrors upstream and is never edited; customisation lives on a branch merged from it (no rebase); metadata additive; patch-vs-tracking is a clean patch back; status reports drift. State: rhizoid CLI typed, add/import/update/status/refresh stubbed, parked 2026-11-11; open items design-consumption-side, cutting-as-cargo-dependency, send-back-writes-the-upstream-item, slice-consumption, rhizcut. What these forks need of it beyond those: (1) a cutting of a non-GitHub upstream (sr.ht, kernel.org): tracking by git fetch + push, not gh merge-upstream; created by gh repo create + push, not gh repo fork; (2) one topic branch per upstream item off tracking, a series of its own - mail lists take a series rebased on current master, so the topic is rebased only before a send (it is ours until sent) while the lab branch that merges topics is never rebased and is what consumers pin; (3) send-back by mail: git format-patch/b4 prep of tracking..topic with cover letter and recipients, never sending, returning the files for an upstream item (the existing send-back item is PR-only); (4) retire a topic when upstream carries it (git cherry / patch-id against tracking) and say so to the follower's record (state landed, carried-in none); (5) consumption by a distro package: write the pin where APKBUILD reads it (source tarball of a lab tag + sha512sums), the cargo item generalised. Until it has them: plain git with the branch rule below, the base's carried query (tad q carried) as the record. How the phones run a fork. sxmo-utils reaches pmOS from Alpine (community/sxmo-utils 1.18.1-r5, the sr.ht tag tarball; -common depends on the exact version). Routes: an own APKBUILD (pmbootstrap aportgen --fork-alpine) with source at our lab tag, built and signed into our own repository and installed with a repository tag (sxmo-utils@lab): the only route an apk upgrade does not undo; pmbootstrap build --src for quick tries (pkgver _pDATE beats 1.18.1-r5 until Alpine moves); make install into /usr is undone by the next upgrade. The kernels: surya's pmOS kernel is linux-postmarketos-qcom-sm7150 (sm7150-mainline tarball); walleye's msm8998 package is archived and the lab runs kernel.org v7.3 with its own dts; both labs already build and flash their own kernels from branches (surya-lab test kernels from branches), so a fork's test/ branch reaches the phone by the lab's existing kernel route, no pmaports change. Etiquette. sxmo-devel: git send-email to ~mil/sxmo-devel@lists.sr.ht, rebased on master, format.subjectPrefix 'PATCH sxmo-utils', vN for resends, CI runs make test on each mailed patch; the applying maintainer adds Signed-off-by. Kernel: b4 prep, checkpatch --strict, get_maintainer; the sender's Signed-off-by; an AI agent adds none and the tag is 'Assisted-by: LLM' (Documentation/process/coding-assistants.rst); dt-bindings first in a series.
- rhizoid: fork, own and sync git dependencies - git-rhizoid Cutting (a fork owned and pinned), tracking branch pristine, patch branch merged from it, additive-only metadata: the model for patching a tool before upstream takes the change. CLI boundary typed, add/update/status stubbed.
- git-rhizoid.github.io: design log and backlog of rhizoid (tad-kept) - git-rhizoid Concepts (additive file structure, tracking vs patch branch, clean patch back) and open items: design-consumption-side, slice-consumption (2026-11-17) and the three items this research added.
- Alpine aports community/sxmo-utils APKBUILD - upstream-forks-research sxmo-utils reaches postmarketOS from Alpine (1.18.1-r5), source the sr.ht tag tarball; -common depends on the exact pkgver-pkgrel, so a fork ships every subpackage from one build
- Alpine wiki: Repositories, tagged repository - upstream-forks-research Tagged (@tag) repositories: apk add pkg@tag prefers the tagged repository for that package even when a later version is elsewhere - the route that survives upgrades
- pmaports linux-postmarketos-qcom-sm7150 - upstream-forks-research surya's pmOS kernel: the sm7150-mainline/linux tag tarball (7.1_rc3) and its config; pmbootstrap build --src or --envkernel builds it from a local tree
- Sxmo: contributing - upstream-forks-research git send-email to ~mil/sxmo-devel@lists.sr.ht, rebased on master, prefix PATCH sxmo-utils, vN for resends; CI runs make test (shellcheck, shellspec, editorconfig) on each mailed patch
- Linux Documentation/process/coding-assistants.rst - upstream-forks-research An AI agent adds no Signed-off-by; the human adds his and an Assisted-by: LLM tag; say what could not be built or tested
- pmbootstrap: pmb/config/sudo.py, helpers/run.py, chroot/binfmt.py, chroot/shutdown.py - postmarketOS, 2026 root by doas/sudo/run0 with an override; check-then-act; a teardown verb; no udev rules, no dry plan
2026-11-18
How is clean-room reverse engineering best done with AI agents, and how should walleye's bring-up apply it?
Agents are now near-human at reading binaries (arXiv 2610.14960; 2608.11469 SRE-Bench: best agents solve ~27-32% of realistic ones), but no paper yet covers clean-room hardware bring-up; the practice does. AI "clean rooms" (ArtCraft: a rule on inputs; chardet 7.0: disputed) cannot prove the wall by the model's mind, only by what it was shown - so use an INPUT wall: observer (traces on the stock system, GPL vendor kernel source, public specs) writes spec rows with evidence kind + hash; a separate scrubber checks them for expression; the implementer sees only accepted rows, public specs and mainline; commits cite spec ids; per-session input log and taint register. Tools: mmiotrace/ftrace/dynamic debug/regmap/QMI logs/debugfs on the running stock system (Nouveau, Asahi m1n1 tracing, freedreno), never disassembly or vendor binaries (Asahi: 'without looking at the code'). Walleye: most MSM8998 parts are upstream and need no clean room; likely only panel init, sensor hub, audio calibration/topology, camera, vendor protocols. GPL vendor kernel (android-msm-wahoo, kcxt/linux-wahoo) is read and ported with licence kept - no clean room. EFF: clean room is good practice, not a legal requirement; no court has ruled on AI clean rooms. Not legal advice. Full proposal, table of parts and record design in the material.
- EFF Coders' Rights: Reverse Engineering FAQ - research-cleanroom-agents Clean room is good practice, not a legal requirement; least intrusive technique first; EULAs can bind
- Asahi Linux progress report, August 2021 (m1n1 hypervisor tracing) - research-cleanroom-agents Trace hardware accesses on the real system without looking at the vendor code; disassembly would endanger copyright status
- Nouveau: Memory Mapped I/O Trace - research-cleanroom-agents mmiotrace plus envytools register database; one person documents, another implements
- Clean-room reverse engineering process manual v1 (Kyvero-Vexus) - research-cleanroom-agents A/B/C team roles, access matrix, taint register, spec-to-test traceability, evidence bundle (not peer reviewed)
- storytold/wordcraft AGENTS.md (ArtCraft clean-room house rules) - research-cleanroom-agents Clean room as a rule on inputs: black-box observation plus public specs; never read the app bundle
- Reversa: reverse documentation engineering for AI agents (arXiv 2605.18684) - research-cleanroom-agents Spec shape: claims with confidence, gaps, traceability, parity scenarios; no clean-room discussion
- When Binaries Talk Back: Representation-Confusion Attacks on LLM-assisted RE (arXiv 2607.12507) - research-cleanroom-agents Captured data is data, never instructions; count evidence by origin
- Humans vs. Machines: AI agents in software reverse engineering (arXiv 2610.14960) - research-cleanroom-agents Agents competitive but need persistent analysis state
- Chardet dispute shows how AI will kill software licensing (The Register, 2026-03-06) - research-cleanroom-agents An AI clean room is not yet a defence; the wall cannot be shown by the model's mind
- postmarketOS: Qualcomm mainline porting - research-cleanroom-agents Downstream vendor kernel is the reference; device tree plus mainline drivers
2026-11-17
How do SM6150/SM7150 'bolero' boards and their siblings (SM7125 atoll, SM6115 bengal, QCS615 talos) record their microphones on mainline and open stacks, and what does the vendor's own model say?
Working on mainline, legacy q6afe firmware: SM7150 davinci (sm7150-mainline PR 60, open, -62 dBFS floor) and surya (pulpoff/linux-surya; and linux-phone-oco since 2026-11-17), both through analog mics on the WCD9375 -> TX SoundWire -> TX macro DEC (SWR_MIC) -> TX_CODEC_DMA_TX_3. The SM7150-specific trap: its TX SoundWire controller has one dout port, which shifts both the master port numbers (inputs from port 2) and the controller's DAIs (capture is DAI 1); SM7125, the template, has none, so its <&swr2 0> is right there. Nobody streams the VA port on SM6150/SM7150; both trees declare a VA link and leave out the DCODEC vote this ADSP refuses. The vendor (sm6150 bolero, qcom,va-without-decimation) uses the VA block only for MCLK, the fs counter and DMIC clocks, clocked from the TX macro's MCLK through bolero's mclk mux, and routes every TX and RX path to VA_MCLK; mainline gives the same through the VA macro's fsgen clock on the TX macro. No open implementation of va-without-decimation exists - only a board with real DMICs on this family would need it. SM6115/QRB4210 (Linaro RB2 v3) records DMICs through VA_CODEC_DMA_TX_0 with the DCODEC vote: not a template here. QCS615 upstream (2026-05) is AudioReach with an external DA7212, headset mic only. postmarketOS ships no microphone support for SM7150 (wiki: N, UCM speaker-only).
- sm7150-mainline/linux PR 60: working WCD9375 microphone capture on davinci (open) - , 2026 The four faults of SM7150 WCD capture: swr_tx_data mux 3, the TX bus wakeup IRQ, port numbering shifted by the TX controller's one dout port, and the capture link's DAI 1; plus MultiMedia2 for capture. The place to contribute surya's fixes upstream, beside it rather than in a parallel series
- pulpoff/linux-surya: mainline 7.2.15 for the POCO X3 NFC on Mobian, both microphones and call audio - , 2026 surya's microphones are analog on the WCD9375 (bottom AMIC1 on ADC1, top AMIC3 on ADC2); capture link on <&swr2 1>; qcom,tx-port-mapping <2 3 4 5> gives ADC2 its own master port 3; LPI gpio7-11 NC (no DMIC pins in use); q6voice call uplink needs a running mono capture on TX_CODEC_DMA_TX_3
- LineageOS sm6150 kernel: the vendor bolero codec (tx-macro, va-macro, bolero-cdc) and sm6150 machine driver - , 2019 sm6150/sdmmagpie use qcom,va-without-decimation: the VA block gives only MCLK, the fs counter and DMIC clocks, clocked from the TX macro's MCLK through bolero's mclk mux; TX decimators record everything; TX AIF1 is TX_CDC_DMA_TX_3 (AFE 45111 = 0xB037)
- sm7125-mainline/alsa-ucm-conf: miatoll HiFi (TX macro, TX_CODEC_DMA_TX_3 mic entries) - , 2025 SM7125 records through the TX macro on TX_CODEC_DMA_TX_3 with q6afe and WCD937x; its TX controller has no dout port, so <&swr2 0> is right there - the template sm7150 copied. Whether miatoll's mic records is unverified
- [PATCH v3 00/12] qrb4210-rb2: wsa audio playback and capture (Alexey Klimov, Linaro) - , 2025 SM6115/QRB4210 records its DMIC through the VA macro on VA_CODEC_DMA_TX_0 with the DCODEC vote on q6afe - both refused by surya's ADSP, so not a template for SM7150
- [PATCH v5 0/2] QCS615 Talos EVK audio support (Le Qi) - , 2026 Upstream QCS615 audio (merged 2026-05) is AudioReach with an external DA7212 over MI2S, headset mic only: no LPASS macro, WCD or DMIC work for talos yet
- postmarketOS wiki: Qualcomm Snapdragon 730/730G/732G (SM7150) - Microphones marked not working on SM7150 devices; the shipped alsa-ucm-conf-qcom-sm7150 is speaker-only
2026-11-17
How should docs split general knowledge from per-device work, and how does it learn each device's progress?
Read and summarised in grenudi/ideal-knowledge-base (research commons-and-unit-bases-world, material research/commons-bases/2026-11-17/): Linux MAINTAINERS, devicetree bindings vs board dts, Debian ports wiki, Renovate, GitHub templates and Copier agree on a commons with schema and process and units that declare their own status; the commons pulls and derives, a status typed twice drifts. Measured here: test_results 1.3 MB of 2.0 MB; 40 of 81 docs backlog items, 34 of 49 research rows and 14 of 28 decisions name a device. Not read: postmarketOS, Fedora ARM.
2026-11-17
Where does the coordinator's work stand, for a fresh coordinator to take it up without the old session's 840k tokens?
ROLE: the author's one session for linux-phone-oco - relays his words to the working sessions, keeps docs' records true through tad, routes work by the weakest link; does not build. SESSIONS (list_sessions linked): orchestration local_325ef65d (devlab, the queue, the face, the agent folder, the patrol and the waker); the phone keeper, started by the waker (surya dispatcher) - the one holder of the phone; ideal-agent-ikb local_05818060 (general agent know-how: practices, skills, hooks, housekeeping); idealkb build local_b8ca2fb5 (ideal-knowledge-base; docs and ideal-agent follow it, 0.5.0); phone lover local_f93a213b (bring-up, retired to the upstream queue). IN FLIGHT: deep sleep - after a timed s2idle test surya showed the initramfs gadget (18d1:d001); the author force-rebooted it and the keeper was to check health and record it; the wake IRQ 157 is the Bluetooth UART. Next on the queue: the sensor hub (sensors-and-the-mask, sensors-without-crash), off-state charging; gps-measurable waits on a research session; telegram-at-provisioning waits on Alpine v3.24; upstream-alpine-tqftpserv is a request in the author's name. Ask: tad q phone-queue, tad q next. WAITING ON THE AUTHOR: hands for any phone reboot or physical test; his word before anything goes upstream in his name; whether to start a GPS or sensors research session. STANDING WORDS: nothing depends on ocoeco; everything through tad in docs, idealkb the layer on top; deep sleep first, hard features researched first; a small look around before any change, with sources; summaries kept current; Gmail and Claude Docs off by default; quiet test sounds; fewer, longer-lived roles renewed by hand-over; sign as grenudi upstream; patches by git send-email. DON'T: widen ocoeco for another project; send HTML mail to lists.sr.ht; let a session re-read history to start; devlab kernel remove on entries sharing a release; treat idealkb as tad. Read from the old coordinator's transcript (7007ce97, 12.9 MB, 1,222 turns) by a subagent that returned 2.5 KB; corrected against main: docs follows idealkb 0.4.0 and the bring-up brief is folded into the keeper's.
2026-11-17
Which public number can an automated call reach from a German mobile, that plays back what it hears, free or at the national rate?
Only one German public echo line is attested across sources and years: blueSIP's echo test, +49 89 721010 99701, a Munich landline number (landline rate: inside any German allnet flat, about 9 ct/min on plain prepaid), named in forums in 2005 and 2013, recommended in 2021, and still on Placetel's list (which gives no warranty). It plays back what it hears at once (an echo, not record-then-playback); no length limit is stated. The same provider's +49 89 721010 99702 plays a signal tone: a downlink-only control that needs no working uplink. sipgate's echo (10005) and test (10000) are SIP-internal short codes, not dialable from a mobile, and sipgate serves only business customers since 2025-06. Other European lines (portunity's 0211 237099929 from 2005, sip2sip's +31 20 8005161, a Dutch C*NET echo) are old and unconfirmed, and abroad costs more. No source confirms any line works from a mobile today, so the first supervised call settles it. Fallback that is certain to exist and free on German tariffs: the SIM's own mailbox (record a message, play it back by DTMF; slower and operator-specific).
- Testrufnummer gesucht? Vollständige Liste für alle Zwecke - Placetel blueSIP's echo test +49 89 721010 99701 and its signal-tone line 99702; no warranty given for the list
- Testrufnummern gesucht (IP Phone Forum) - , 2005 blueSIP 99701 echo, 99702 tone, 99703 song; portunity's 0211 237099929 echo
- Telefonnummer für Testanrufe (IP Phone Forum) - , 2013 089 72101099701 still given as the BlueSIP echo test in 2013
- BlueSIP Echotest, +49 89 721010 99701 (Festnetztarif) - , 2021 the echo still recommended in 2021, at the landline rate
- Sipgate (prepaid-wiki) - , 2025 sipgate's echo 10005 and test 10000 are SIP-internal; sipgate serves only business customers since 2025-06
- SipTesting - SIP2SIP (AG Projects) - an EU PSTN test number +31 20 8005161; echo only on SIP (4444)
2026-11-17
How can the phone itself decide that a call carried sound both ways?
Acoustically, through the paths a person uses, with the analysis in Rust: during the call the uplink capture that the call needs anyway (1 channel on TX_CODEC_DMA_TX_3, the bottom mic) is written to a file instead of thrown away. The phone plays a pattern of three short tones (e.g. 800, 1300, 1900 Hz, 200 ms each, 300 ms apart - inside the 300-3400 Hz every voice codec keeps) on the loudspeaker at the manifest's quiet level; the bottom mic hears it at once (proves the injection) and sends it up the call; the echo comes back down and plays on the earpiece, and the same mic hears it again 150-1500 ms later (the network's round trip; acoustic reflections are under 20 ms). A Goertzel envelope per frequency finds the pattern twice; the echo counts when the same order of tones recurs at one delay, 15 dB above the noise, and the delay is reported. Before the echo call, a call to the tone line (99702) proves the downlink alone, so a missing echo says uplink (or the line) rather than everything. Cost: one call of at most 25 s (dial, about 8 s to answer, 5 s of pattern, hang up; a hard timeout), at most once a day, a landline-rate number: inside a flat, or under 10 ct per day on prepaid. Skips cleanly, as unknown: no modem, no SIM, not registered, no voice interface, no call path (call-audio-path failing), the daily call already made, or the number unset in the manifest. A pass proves works for modem-calls. If q6voice exposes in-call record/playback ports (downstream's VOICE_RECORD_RX, incall music), a digital loop could replace the acoustic one later; unknown on this driver.
- pulpoff/linux-surya: mainline 7.2.15 for the POCO X3 NFC on Mobian, both microphones and call audio - , 2026 surya's microphones are analog on the WCD9375 (bottom AMIC1 on ADC1, top AMIC3 on ADC2); capture link on <&swr2 1>; qcom,tx-port-mapping <2 3 4 5> gives ADC2 its own master port 3; LPI gpio7-11 NC (no DMIC pins in use); q6voice call uplink needs a running mono capture on TX_CODEC_DMA_TX_3
- Testrufnummer gesucht? Vollständige Liste für alle Zwecke - Placetel blueSIP's echo test +49 89 721010 99701 and its signal-tone line 99702; no warranty given for the list
2026-11-17
Should linux-phone-oco keep standing expert sessions, one per hard domain (audio, modem, sleep...), with the orchestrator routing questions to them - or keep expertise somewhere else?
The world has tried it under several names - specialised workers under a supervisor, hierarchical teams, blackboard systems, stateful agents - and converges on one split: the expert is a role and a body of written knowledge; a session is a disposable worker that takes the role up. Gas Town says it outright (an agent is a persistent identity, sessions are cattle; any session can hand off and restart from its hook). Anthropic's long-running harness found compaction alone not enough and had every fresh session get up to speed from a progress file, git and a feature list; its context-engineering guide names notes outside the window as the tool for iterative work with milestones. Claude Code itself moved this way: subagents may keep a per-role MEMORY.md, and agent teams start each teammate from project context and a spawn prompt, never the lead's history, and do not restore teammates on resume. Against expertise held in a long context: models recall worse as input grows (Chroma, context rot; Anthropic's attention budget), repeated summarising erodes detail (ACE: context collapse, brevity bias), and a session of 1000-1800 messages re-reads all of it each turn - after an idle hour without the cache, at full price - so a standing expert answering an occasional question is the costliest and not the most reliable way to answer it. Against a central router: a supervisor that relays every message plays telephone - lower scores and more tokens than agents handing off directly (LangChain); misalignment between agents (lost context, withheld information) is one of the three failure groups in 1600 traces (MAST). What works (Cognition, 2026): one writer per thing, other agents adding intelligence not actions; a consult works best given a fork of the asker's full context. Blackboard systems route by a shared record agents read, not by a relay. For us: most of the audio expertise is already rows in docs (5 research, 2 decisions, 27 backlog items name the microphone); what is not written is the tacit part - dead ends, where the experiment patches are, what hung the phone - and it now lives in hand-over notes outside any repository.
- Effective context engineering for AI agents - , 2025 Context rot and an attention budget: more tokens, worse recall. Three tools for long work - compaction (risks losing what matters later), structured notes outside the window (NOTES.md), sub-agents that return 1-2 thousand token summaries; load knowledge just in time by reference.
- Effective harnesses for long-running agents - , 2025 Compaction alone was not enough: each fresh session gets up to speed from a progress file, the git log and a feature list, works one item, commits and writes its progress. Whether specialised agents beat one general agent is left open.
- Orchestrate teams of Claude Code sessions - , 2026 Teammates message each other directly, not only through the lead; 3-5 teammates; each starts from project context and a spawn prompt, never the lead's history; in-process teammates are not restored on resume; for routine or sequential work one session is cheaper.
- Claude Code agent memory frontmatter - , 2026 Since v2.1.33 a subagent can keep its own MEMORY.md (project scope in .claude/agent-memory/NAME/), its first 200 lines put in its prompt each time: the field writes expertise down per role rather than keeping it in a session; each role's memory is siloed from the others.
- Multi-Agents: What's Actually Working - , 2026 A narrower class works: writes stay single-threaded and extra agents contribute intelligence, not actions. Consulting a 'smart friend' works best by sharing a fork of the asker's full context; unstructured swarms of negotiating agents are a distraction.
- Benchmarking Multi-Agent Architectures - , 2025 A supervisor that relays every message plays telephone: it scored lower and spent more tokens than agents handing off directly; removing routing chatter from the workers' context closed much of the gap.
- Agentic Context Engineering: Evolving Contexts for Self-Improving Language Models - , 2025 Knowledge kept by rewriting one summary erodes (context collapse) and drifts toward the terse (brevity bias); itemised, incremental additions to a playbook keep the detail. ICLR 2026.
- Why Do Multi-Agent LLM Systems Fail? - , 2025 1600+ traces, 14 failure modes in three groups: system design, misalignment between agents (lost context, ignored input, withheld information), task verification. Gains from multi-agent systems are often minimal. NeurIPS 2025.
- Context Rot: How Increasing Input Tokens Impacts LLM Performance - , 2025 Models do worse as input grows, even on simple tasks and well below the window's size; focused inputs beat full ones.
- Exploring Advanced LLM Multi-Agent Systems Based on Blackboard Architecture - , 2025 Agents share one blackboard instead of private memories; a control unit picks who acts from what is on it. With 2510.01285 (agents volunteer for requests posted to the board): routing by a shared record, not by a central relay.
- Sleep-time Compute - , 2025 Stateful agents keep editable memory blocks; a separate agent rewrites them between tasks into clean, concise learned context, so the working agent need not re-derive it.
2026-11-17
How does the Pixel 2 XL (taimen) stand?
Far from surya. Nothing is measured here. By community report it boots mainline 5.10-rc2 on a basic device tree from an out-of-tree fork (kcxt/linux-wahoo, last push 2022-02-27), USB networking and flashing work, there is no display, the battery does not work. No mainline device tree, no pmaports package, no one has reported touch, audio, modem, wifi or the rest. Worth a lab test one day only as the cheap member of the pair, after surya's list: it is the one with a documented boot.
- Nura (postmarketOS) wiki: Google Pixel 2 XL (google-taimen) - Mainline boots with a basic DT (5.10-rc2), USB networking and flashing work, no display; the only wiki page of either phone (walleye has none). Revised 2026-09-05 and 2026-09-27 (bot); status by Casey/kcxt.
- kcxt/linux-wahoo: Mainline Linux for the Google Pixel 2XL (And 2?) - Out-of-tree mainline port, created 2020-07-20, last pushed 2022-02-27: msm8998-google-taimen.dts, -walleye.dts and wahoo.dtsi (branch wahoo/5.17), panel and DPU/DSC work, a 5.11 submission branch.
- Linux mainline: arch/arm64/boot/dts/qcom (MSM8998 device trees) - No Pixel 2 / 2 XL device tree in mainline (checked 2026-11-17); MSM8998 boards there: OnePlus 5/5T, Xiaomi Mi 6, Sony yoshino, F(x)tec Pro1, HP Envy x2, Lenovo Miix 630, Asus NovaGo; msm8998.dtsi still edited (2026-09-17).
- Nura pmaports: device packages of Google phones (device/community, device/testing) - device-google-walleye and device-google-taimen are absent from device/main, community and testing (listed 2026-11-17); Google packages there are sargo/bonito (community), blueline, flame, oriole, raven (testing).
2026-11-17
What does Android on the Pixel 2 give, by public specifications, that a Linux phone is measured against (sensors, sleep, audio, battery)?
Public sources only (table in research/google-walleye/2026-11-17/android-reference-public-specs.md). Android reference: 5.0 in AMOLED 1080x1920, 2700 mAh, two front stereo speakers about 89 dB(A), no 3.5 mm jack (USB-C audio, Bluetooth 5 with aptX HD), 12.2 MP rear with OIS and laser focus, 8 MP front, LTE Cat. 15, NFC, eSIM plus nano-SIM, rear fingerprint, Active Edge squeeze. Sensor set to count: accelerometer, gyro, magnetometer, barometer, proximity, light, Hall, squeeze, step counter and detector, behind a sensor hub. Chips (only from the Pixel 2 XL teardown, so likely not stated for walleye): LSM6DSM IMU, AK09915C magnetometer, BMP280 barometer, AK8789 Hall, TMD4903 light, VL53L0X ranger, TAS2557 amp, DRV2624 haptics; the vendor kernel confirms TAS2557, DRV2624 and a ranger for walleye. Android battery runs (Notebookcheck): idle Wi-Fi off 24 h 17 min, web 9 h 35 min, video 9 h 24 min; field 15 to 17 h unplugged a day. Doze (when unplugged, still, screen off): network suspended, wake locks ignored, alarms and jobs deferred, maintenance windows spread out. Last software Android 11, build RP1A.201005.004.A1, support ended October 2020. Not known yet: standby current per hour (none published), real sensor list and rates on walleye, charger wattage, speaker level under a test tone. Only Android booted on our phone can give these (backlog google-walleye-lab/android-reference-walleye; needs the author).
- Wikipedia: Pixel 2 - walleye-research-vendor Cameras (rear IMX362 12.2 MP, front IMX179 8 MP), Pixel Visual Core, eSIM, software versions (Android 8.0 to 11).
- Notebookcheck: Google Pixel 2 review - walleye-research-vendor, 2017 Measured display (426 cd/m2 peak, PWM about 245 Hz), speaker level, battery runtimes on Android (idle Wi-Fi off 24 h 17 min), GPS walk test.
- iFixit: Google Pixel 2 XL teardown - iFixit, 2017 Chip names (IMU LSM6DSM, magnetometer AK09915C, barometer BMP280, Hall AK8789, light TMD4903, ToF VL53L0X, amp TAS2557, haptics DRV2624, charger SMB1381, NFC PN81A, Pixel Visual Core). Pixel 2 XL only: likely, not stated, for walleye.
- LineageOS wiki data file for walleye (devices/walleye.yml) - walleye-research-vendor Public spec as LineageOS lists it: SoC, 4 GB, 2700 mAh, stereo front speakers, Bluetooth 5, branches 16.0 to 22.2, kernel repo, fastboot install.
- 9to5Google: Pixel 2 final update (December 2020) - walleye-research-vendor, 2020 End of Pixel 2 support: last build RP1A.201005.004.A1, Android 11.
- Droid Life: Pixel 2 battery life - walleye-research-vendor, 2017 Field figures: 4 to 5+ h screen-on, 15 to 17 h unplugged a day.
- Android developers: Optimize for Doze and App Standby - walleye-research-vendor What Android does when idle: network suspended, wake locks ignored, alarms deferred, maintenance windows; the sleep behaviour a Linux phone is measured against.
2026-11-17
How does the Pixel 2 (walleye) stand?
Nothing reported on mainline: no wiki page, no pmaports package, no mainline device tree. Only the out-of-tree fork kcxt/linux-wahoo has a walleye device tree (wahoo/5.17), and nobody says it boots. Android (LineageOS 22.2) and an old Ubuntu Touch 16.04 port exist. Everything is unknown; test it only after taimen has shown the way, since both share the SoC and the kernel fork.
- kcxt/linux-wahoo: Mainline Linux for the Google Pixel 2XL (And 2?) - Out-of-tree mainline port, created 2020-07-20, last pushed 2022-02-27: msm8998-google-taimen.dts, -walleye.dts and wahoo.dtsi (branch wahoo/5.17), panel and DPU/DSC work, a 5.11 submission branch.
- Ubuntu Touch: Google Pixel 2 (walleye), old releases - Only the 16.04 (xenial) release exists; the current release does not support the phone. A Halium/Android-kernel port, not mainline.
- LineageOS wiki: Google Pixel 2 (walleye) - Android, current LineageOS 22.2 (Android 15) on kernel 4.4 for walleye; taimen has the same page shape. Shows the phones stay alive on Android, not on mainline.
- Nura pmaports: device packages of Google phones (device/community, device/testing) - device-google-walleye and device-google-taimen are absent from device/main, community and testing (listed 2026-11-17); Google packages there are sargo/bonito (community), blueline, flame, oriole, raven (testing).
2026-11-17
How did others boot Linux on the Pixel 2 family (boot image, A/B, fastboot boot, dtbo), what boots, and how did they reach a phone with no display?
Only the Pixel 2 XL (taimen) is reported to have booted mainline, by kcxt (Caleb Connolly) on an out-of-tree 5.10 to 5.17 fork, 2020 to 2022: black screen, USB networking to a shell, flashing works; a March 2021 mainline submission shows no sign of being merged. Walleye has a 13-line tree in the same fork and no report that it boots; neither phone is in pmaports (Pixel 3, 3 XL, 3a are). Ubuntu Touch (Halium 9, Android 4.4 kernel) has only an abandoned 16.04 port for walleye, with boot loops and no USB networking in the forum threads read. How the no-display phone was reached: USB peripheral mode only (SuperSpeed dropped), kernel console on a USB serial gadget ttyGS0 plus ttyMSM1 earlycon, clk_ignore_unused; a UART through the USB-C sideband pins ('Android Debug Cable', 115200 baud) which the pmOS wiki lists as tested with walleye - enabled with `fastboot oem uart enable`; pstore only partly worked. What the bootloader wants (XL only, read): a dtbo partition holding an overlay with id 2704 (0xa90) or the bootloader refuses to boot; pmaports' Pixel 3 packages append the dtb to the kernel (4096-byte pages, kernel offset 0x8000, ramdisk 0x1000000), LineageOS uses Image.lz4-dtb with recovery in the boot partition and A/B, 8 MB dtbo. Detail and URLs in research/google-walleye/2026-11-17/how-others-booted-wahoo.md. Not known yet: whether this phone's bootloader accepts `fastboot boot` of our image; the dtbo id walleye needs (the README is XL only; changing dtbo writes to the phone); whether `fastboot oem uart enable` only sets a RAM flag or writes something (until known, it is a change to the phone); the boot header version; slot handling for a Linux boot; any report for the small Pixel 2 booting mainline. Ways forward: (1) read walleye's dtbo overlay ids without writing (from Android if it boots, or Google's factory image, a proprietary download - decision needed); (2) try a first `fastboot boot` of a kernel with appended dtb and a USB-gadget serial console once devlab's fastboot mode exists; (3) build the USB-C debug cable and enable the UART only after a decision on the oem command.
- Nura (postmarketOS) wiki: Google Pixel 2 XL (google-taimen) - Mainline boots with a basic DT (5.10-rc2), USB networking and flashing work, no display; the only wiki page of either phone (walleye has none). Revised 2026-09-05 and 2026-09-27 (bot); status by Casey/kcxt.
- kcxt/linux-wahoo: Mainline Linux for the Google Pixel 2XL (And 2?) - Out-of-tree mainline port, created 2020-07-20, last pushed 2022-02-27: msm8998-google-taimen.dts, -walleye.dts and wahoo.dtsi (branch wahoo/5.17), panel and DPU/DSC work, a 5.11 submission branch.
- kcxt/linux-wahoo branch wahoo/5.17: msm8998-google-walleye.dts and the shared wahoo dtsi - walleye-research-vendor, 2022 What mainline can already express for wahoo: UFS, USB peripheral, one DSI, GPU, Wi-Fi, SLPI/ADSP, regulators; walleye file is 13 lines and sets no panel; boots with console on ttyMSM1 and USB-gadget ttyGS0, ramoops at 0xa1810000.
- kcxt/dtbo-google-wahoo-mainline: minimal dtbo for the Pixel 2 XL - walleye-research-vendor, 2020 The Pixel 2 XL bootloader refuses a kernel unless dtbo holds an overlay with id 2704 (0xa90); stock cmdline has androidboot.dtbo_idx=12. XL only; walleye's id not known.
- LKML March 2021: [PATCH] arm64: dts: add support for the Pixel 2 XL, with review - walleye-research-vendor, 2021 Boots with USB networking, panel needs DSC, dtbo overlay id required, clk_ignore_unused, Wi-Fi needs diag-router; no sign it was merged.
- postmarketOS (Nura) wiki: Serial debugging / Cable schematics, Google Pixel Android Debug Cable - walleye-research-vendor USB-C sideband UART cable tested with Pixel 2 (walleye), 2 XL, 3 and later; fastboot oem uart enable; Suzy-Q is the wrong cable.
- Peter-Easton/android-debug-cable-howto - walleye-research-vendor How to build the Pixel USB-C debug UART cable (A1 GND, SBU1 RX, SBU2 TX, 115200 baud).
- Nura pmaports: device packages of Google phones (device/community, device/testing) - device-google-walleye and device-google-taimen are absent from device/main, community and testing (listed 2026-11-17); Google packages there are sargo/bonito (community), blueline, flame, oriole, raven (testing).
- LineageOS wiki: Install LineageOS on walleye - walleye-research-vendor Latest Android 11 firmware first; OEM unlock then fastboot flashing unlock; recovery flashed into boot; no set_active step, no fastboot boot step.
- Ubuntu Touch: Google Pixel 2 (walleye), old releases - Only the 16.04 (xenial) release exists; the current release does not support the phone. A Halium/Android-kernel port, not mainline.
- UBports forum: walleye install threads (topics 5639, 6251, 12600) - walleye-research-vendor Halium 9 on walleye: boot loops, Slot Unbootable, no RNDIS after flashing halium-boot; Pixel 2 XL Ubuntu 24.04 claim Sept 2026, unverified.
- Halium docs: debug build over USB networking - walleye-research-vendor Telnet at 192.168.2.15 from the initrd, host 192.168.2.1; useless when the kernel does not start.
2026-11-17
Which chip is each part of the Pixel 2 (walleye) and how is it wired, by Google's GPL wahoo kernel device tree and the mainline port's tree?
Read from the LineageOS copy of Google's wahoo kernel (4.4, branch lineage-22.2) and kcxt/linux-wahoo wahoo/5.17; observed facts only, nothing copied; table in research/google-walleye/2026-11-17/vendor-kernel-hardware-inventory.md. Walleye is the HTC-built half of the pair: its files are under dts/htc/ and called "muskie"; one base plus one of two overlays by board revision (xa/xb/xc or xd/xe/a; our MP1 maps to one of them - not known yet). SoC MSM8998 v2.1 with PM8998, PMI8998 and PM8005. Parts: panel Samsung S6E3FA5 5.0 in 1080x1920 command mode, 4 DSI lanes, reset GPIO94, TE GPIO10, rails PM8998 L14 1.8 V and L22 3.0 V, backlight by DCS (no WLED), always-on modes. Touch Synaptics DSX at I2C 0x20 on the BLSP1 QUP5 bus (GPIO87/88), IRQ GPIO125, reset GPIO89. Audio: WCD934x "Tavil" codec on SLIMbus, TI TAS2557 stereo speaker amp at I2C 0x4d, no jack; NXP TFA98xx amps are in the tree but disabled. Haptics TI DRV2624 (LRA 155 Hz, I2C 0x5a, reset GPIO95). LED: TI LP5562 on early revisions, PMI8998 RGB on later. Charger: PMI8998 SMB2 with Type-C PD, TPS61099 for USB host power, NXP PTN36241G redriver. Fuel gauge: PMI8998 FG gen3 with HTC battery module, 2700 mAh, 4.4 V. NFC: NXP NQ-class at 0x28 plus PN81A secure element on SPI. Fingerprint FPC1020 family (IRQ GPIO86, reset GPIO128). Wi-Fi and Bluetooth: Qualcomm WCN3990 (Bluetooth HCI on BLSP1 UART3). Cameras: two CCI sensors, rear with autofocus, OIS, EEPROM and flash, laser ranger at I2C 0x29; the sensor chips are not named in the tree (public specs: Sony IMX362 rear, IMX179 front). Pixel Visual Core ("Easel") on PCIe 0 with a BCM15602 PMIC and SPI. Storage UFS. Sensors (IMU, magnetometer, barometer, light, Hall) are not in the application processor's tree: the SLPI sensor-hub DSP owns them, firmware proprietary. For a phone with no display: stock describes a RAM console (ramoops) at 0xa1100000, 2 MiB, plus an alternate at 0xa3800000; the mainline port uses 0xa1810000 instead and boots with console on ttyMSM1 (BLSP2 UART1) and a USB-gadget serial ttyGS0 - which address survives a reset on this phone is not known yet. The mainline port's walleye file is 13 lines and sets no panel (the shared file's panel is taimen's LG one), and enables UFS, USB peripheral, one DSI, GPU, Wi-Fi, SLPI and ADSP, regulators - nothing for touch, audio, haptics, NFC, gauge, charger, cameras, sensors. Not known yet: camera and sensor chips on walleye itself, touch controller model, codec exact part, fingerprint wiring, Active Edge sensing, UART test pads, which overlay MP1 uses.
- LineageOS android_kernel_google_wahoo (lineage-22.2): device-tree sources of walleye and taimen - Google, HTC, LG, Qualcomm; kept by LineageOS, 2025 GPL-2.0 Linux 4.4 kernel of both wahoo phones. Walleye (HTC-built, project name muskie) is under arch/arm64/boot/dts/htc: panel, touch, audio amp, haptics, NFC, camera, battery, memory map. Read as facts for a hardware table; ports of code keep copyright and licence.
- kcxt/linux-wahoo branch wahoo/5.17: msm8998-google-walleye.dts and the shared wahoo dtsi - walleye-research-vendor, 2022 What mainline can already express for wahoo: UFS, USB peripheral, one DSI, GPU, Wi-Fi, SLPI/ADSP, regulators; walleye file is 13 lines and sets no panel; boots with console on ttyMSM1 and USB-gadget ttyGS0, ramoops at 0xa1810000.
- iFixit: Google Pixel 2 XL teardown - iFixit, 2017 Chip names (IMU LSM6DSM, magnetometer AK09915C, barometer BMP280, Hall AK8789, light TMD4903, ToF VL53L0X, amp TAS2557, haptics DRV2624, charger SMB1381, NFC PN81A, Pixel Visual Core). Pixel 2 XL only: likely, not stated, for walleye.
- AOSP: Build Pixel kernels (legacy branches) - Pixel 2 and 2 XL share one kernel, device/google/wahoo-kernel, branch android-msm-wahoo-4.4-android10-qpr3.
2026-11-17
How should hardware for debugging and bring-up (cables, adapters, meters) be kept for every phone, claimed versus confirmed, and read by the lanes?
Read: Snipe-IT (model vs asset; status labels deployable/pending/archived; purchase_cost with purchase_date), Part-DB (part vs lot by location; supplier price details with quantity breaks; a needs-review flag), KiCad (custom fields MPN/Manufacturer by convention; no status or price date), OpenBOM (item vs usage), the kernel's serial-console doc (software contract only), and for the Pixel UART cable bacon.dev (2020, updated 2022), Peter-Easton's howto (title says Pixel 2/3/4, body details the 3), xairy's pixel-kgdb (FT232R supports break, CP2102N does not), google/usb-cereal (DIP 1.8/3.3 V, archived 2023-01-10). Not read: postmarketOS Serial_debugging (301 to nura.eco, then Anubis denial), iFixit (404), LineageOS device pages (403), Part-DB parts page (503).
2026-11-17
How should the phones' health suites be organised to cover every part and feature, stay quick to change and dependable, and avoid Python?
What is: devlab-health, a static Rust runner (lab-tools/health), runs shell checks on the phone after every boot in two layers (base, shell): 11 generic in lab-tools and 5 of surya's own in surya-lab; each prints 'pass|fail|skip TEST COMPONENT detail' and docs' tests table says what each pass proves. The weak spot is computation in shell: three of surya's checks carry a Goertzel filter written in awk and a tone made byte by byte with printf, because lab-tools' tested tone crate never reaches the phone. The phone has no Rust toolchain (it has python3, which the lab refuses), so rust-script (stable, 0.36 on the lab) cannot run there and would need a toolchain and network on the phone; Cargo's own single-file scripts (frontmatter, cargo PR 16569) are still nightly-only in Cargo 1.99. KTAP is the kernel's test output (ok/not ok, SKIP, nested suites) - a format our lines map onto if LAVA-style tools are ever wanted. Shape that fits: shell stays for what is a reading (sysfs, a command's output; ten readable lines), and anything with numbers, timing or a state machine (tones, echoes, calls, sleep counters) is a subcommand of one static multi-call Rust binary shipped with devlab-health (e.g. devlab-health tone find, devlab-health call echo), built with its unit tests and recorded fixtures on the lab and cross-built by health/build.sh; rust-script is the lab's prototyping and one-off analysis tool against recordings fetched from the phone, a prototype becoming a subcommand once it is kept. Coverage is read off the data: a query of every device's components with no test that proves works, and a layer per cost - base, shell, then telephony (calls and data, gated by budget and once a day) and witnessed (needs a person).
- rust-script: run Rust files and expressions as scripts - stable today on the lab (0.36): a single .rs file with its dependencies, compiled and cached on first run
- Rust project goal 2026: cargo-script - Rust project, 2026 single-file Cargo packages with frontmatter, unstable for years, stabilisation in progress (cargo PR 16569); Cargo 1.99 on the lab still asks for -Zscript
- The Kernel Test Anything Protocol (KTAP), version 1 - Linux kernel the kernel's test output: ok/not ok with SKIP, nested suites; a format our one-line reports could be converted to
2026-11-17
What in the commons already does part of an ideal knowledge base, and would idealkb be one nature under a second name?
tad (creation-guidelines/tad-engine) is the engine: tables declared as data after Frictionless Table Schema, checked rows, canonical files, SQL, named queries and records with their header line as their description (tad statements is already an index of every question and record a base keeps). text-as-data-template is the template for a base kept as tad data - the same nature as idealkb - and has drifted: last changed 2026-11-04, still the vendored Python engine on a DuckDB schema that every base left on 2026-11-11 (as the vendored engines had drifted, three of four behind). ideal-project-playbook is how to run a software project - the loop, guards, CI, honesty - whose own docs/ is a tad base; its kit/templates for backlog, development log and idea page are records a base keeps as tables, and its findability test (real questions, the answer within the first three) is the measure a base needs. software-engineering-canon is a base itself (the spike the template came from). ideal-agent (grenudi/ideal-agent, 2026-11-17) is how agents work: practices, skills, hooks, and its own tad base; it keeps only what is general and leaves a project's domain in the project's data. ocoeco's marks (oco.toml exports, holds) and lenses say how a base fits the observatory's picture - its face, not its organisation. linux-phone-oco/docs is one tad base for every linux-phone place (2026-11-17-one-database), with prompts/ (role briefs), research/ (long prose), and rendered docs/ the face reads. Overlap: idealkb would be text-as-data-template under a second name; nothing else holds how knowledge is organised. Gap: no base links a record to what it is about, and no base has an entry that routes questions to queries.
- text-as-data-template - , 2026 The commons' template for a knowledge base kept as data; last changed 2026-11-04 and still describing the vendored Python engine on a DuckDB schema (bin/adopt-engine.sh, .tad/), which every base left for tad on 2026-11-11.
2026-11-17
How do open practice and agent makers organise a knowledge base so that people and agents reach what they need without reading all of it?
They agree. (1) One small entry that is always read and routes onward, saying what each target is for: llms.txt, the root AGENTS.md (nearest wins), PhotoCraft's Read/Why orientation table, Johnny.Decimal's index, datapackage.json. (2) What is always loaded is kept small: CLAUDE.md under 200 lines, no more than ten per level, llms.txt's skippable Optional. (3) Detail in stages: Skills' name and line, then body, then linked files; Claude Code loads nested CLAUDE.md only when its subtree is touched; context engineering keeps lightweight identifiers - paths, stored queries - and loads content just in time. (4) Small units with stable addresses: evergreen notes whose titles work like APIs, numbered ADRs, Wikidata's Q and P ids. (5) Facts apart from explanation: Diátaxis' reference against explanation, Wikidata statements and infoboxes beside prose. (6) One decision per record, superseded rather than deleted (Nygard, MADR). (7) Every statement is about an item by its id and cites who says so (Wikidata). (8) Views are generated from the source data (PhotoCraft's scorecard, Mintlify's llms.txt). Tensions: hierarchy against association (fixed buckets vs dense links - a small fixed index with free links beneath answers both); one file against many (concatenation does not save context; loading on demand does). No source measured how much any of it speeds an agent - the measure here is docs' own (kb-navigation-measured).
- Diátaxis: a systematic approach to technical documentation - , 2021 Four kinds by the reader's need - tutorial, how-to, reference, explanation - never mixed on one page. Reference is neutral and looked up: in a tad base, the tables; how-to is the named records and briefs; explanation is decisions, concepts and the occasional essay.
- The /llms.txt file - , 2024 One Markdown file at a fixed path: a title, a one-line summary, then sections of links with a note each, and an Optional section an agent may skip when short of context. A router, not the content.
- AGENTS.md - , 2025 A README for agents; the nearest AGENTS.md to the file being edited wins. The one file every agent already looks for - the place for a base's single entry.
- Documenting Architecture Decisions - , 2011 One significant decision per record, numbered and never reused; a reversed decision is kept, marked superseded, pointing at what replaced it. docs' decisions table is this, with rejected beside it.
- MADR: Markdown Architectural Decision Records 4.0 - , 2024 Adds considered options with pros and cons and a status that says superseded by which. What docs' decisions already keep as decision, why, rejected.
- Data Package (Frictionless Data) - , 2017 datapackage.json at the top is the descriptor and index of the data's resources, each with a stable name and a schema. tables.toml follows its Table Schema; tad statements is the same kind of index for questions.
- Docs as Code - , 2024 Documentation in plain text, in git, reviewed and tested like code. What every tad base already is.
- Evergreen notes - , 2020 Atomic, concept-oriented, densely linked notes whose titles work like APIs; outline notes link many notes. One row is one such note; a checked link is the dense link; a query is the outline note.
- Johnny.Decimal - , 2024 A fixed small index - no more than ten at each level - kept as a first-class record of every id. A base's entry should be that small.
- The PARA Method - , 2023 Organise by actionability: projects, areas, resources, archives. In a base, what is actionable is read off status (open backlog), not filed by folder.
- Help:Statements (Wikidata) - , 2024 Every statement is about an item, by its id, with references saying who says so. The missing piece in docs: records say which place they are of, but not checked which thing they are about.
- Help:Infobox (Wikipedia) - , 2024 A fixed-format summary of facts beside the prose that explains them; the facts must stand in the prose with citations too. Tables for facts, prose for reasons.
- Effective context engineering for AI agents - , 2025 Context rot and an attention budget: more tokens, worse recall. Three tools for long work - compaction (risks losing what matters later), structured notes outside the window (NOTES.md), sub-agents that return 1-2 thousand token summaries; load knowledge just in time by reference.
- Equipping agents for the real world with Agent Skills - , 2025 Three levels: a name and one line always loaded, the body when relevant, linked files only when needed; scripts run without being read. The shape of a base's entry: AGENTS.md, tad statements, a query's rows, one row.
- Manage Claude's memory (Claude Code) - , 2026 CLAUDE.md up the tree loads at start, nested ones when their subtree is touched; under 200 lines; imports organise but do not save context; procedures go into skills. CLAUDE.md is @AGENTS.md, one source.
- PhotoCraft AGENTS.md - , 2026 Root AGENTS.md: who it is, then an Orientation table (Read / Why) of about 14 docs pages, the workspace map, golden rules, how to pick work, and where each thing is tracked and which pages are generated from which data. ArtCraft (storytold/artcraft) routes by nested AGENTS.md and .claude/rules instead.
- Simplifying docs for AI with /llms.txt - , 2024 llms.txt as the slim index and llms-full.txt as the whole site in one file, both generated. For a base's published site, generated from the data - not the agent's entry.
2026-11-17
Which microphones does surya have, and on which inputs?
Two built-in analog microphones on the WCD9375: the bottom one on AMIC1 (mic bias 1) into ADC1, the top one on AMIC3 (mic bias 3) into ADC2 with its input mux at INP3; the headset mic is AMIC2 (bias 2) on the same ADC2 at INP2. ADC1 comes back over the TX SoundWire bus on master port 2, ADC2 needs its own master port 3 (qcom,tx-port-mapping <2 3 4 5>): sharing port 2 with ADC1 lost the top mic and turned the bottom one to full-scale noise (pulpoff). No digital mics: pulpoff names LPI gpio7-11 NC, among them gpio8-11, the DMIC clock and data pins (vendor gpio26-29), and records both mics through ADC1/ADC2 on mainline. The TX DMIC1-3 routes read on 2026-11-17 come from sdmmagpie-qrd-overlay.dts, Qualcomm's QRD reference board kept in Xiaomi's tree, which declares the SWR_ADC0/ADC2 routes beside them. Measured on the phone (bring-up, 2026-11-17 04:37 UTC, test/surya-mic with <&swr2 1>): mic-records pass and mic-hears-speaker pass, a 1 kHz tone at -19.4 dBFS against -76.3 dBFS of noise through ADC1. The DMIC experiment (pins at mux 1, VA DMIC clocks on a switch) answered a question surya does not ask and is to be dropped.
- pulpoff/linux-surya: mainline 7.2.15 for the POCO X3 NFC on Mobian, both microphones and call audio - , 2026 surya's microphones are analog on the WCD9375 (bottom AMIC1 on ADC1, top AMIC3 on ADC2); capture link on <&swr2 1>; qcom,tx-port-mapping <2 3 4 5> gives ADC2 its own master port 3; LPI gpio7-11 NC (no DMIC pins in use); q6voice call uplink needs a running mono capture on TX_CODEC_DMA_TX_3
- sm7150-mainline/linux PR 60: working WCD9375 microphone capture on davinci (open) - , 2026 The four faults of SM7150 WCD capture: swr_tx_data mux 3, the TX bus wakeup IRQ, port numbering shifted by the TX controller's one dout port, and the capture link's DAI 1; plus MultiMedia2 for capture. The place to contribute surya's fixes upstream, beside it rather than in a parallel series
- Xiaomi's GPL kernel (surya-q-oss): sdmmagpie-qrd-overlay.dts, the sound card routing Xiaomi kept from Qualcomm's QRD board - , 2020 Declares TX DMIC1-3 (bias 1/3) and AMIC2 together with TX SWR_ADC0/ADC2 from ADC1/ADC2: a reference board's routing, not proof of DMICs on surya; every TX/RX path is routed to VA_MCLK
2026-11-17
How can mobile data be checked after every boot within about 3 GB?
Per run: the modem registered and its bearer connected (mmcli), the bearer's interface found from ModemManager, then over that interface only (curl --interface, so Wi-Fi cannot pass for it): a DNS lookup, five pings to a fixed address (round trip, loss), and a 100 kB HTTPS download timed (speed.cloudflare.com/__down?bytes=100000 or a file the project hosts), about 150 kB with overheads. Boots run up to ~45 a day in bring-up, so about 7 MB on a heavy day; once a week a 5 MB download measures throughput. That is under 0.3 GB a month even on busy months: the 3 GB lasts most of a year at the worst rate and years at an ordinary one. A check also reads the bearer's own byte counters (the interface's /sys/class/net/IFACE/statistics before and after) so each run states what it used, and skips when the month's total passes a budget set in the manifest. Skips without a SIM, as the modem checks already do.
2026-11-17
Where does orchestration's work stand, for a fresh orchestration session to take it up without this session's long context?
ROLE: orchestrator (ideal-agent card; brief ideal-agent-linux-phone-oco/orchestration.md, which now opens with Role/Name). Owns the conveyor - lab-tools (devlab; lpoco-health's packaging and the Alpine path are the conveyor's, its code is lpoco-health's), device-template, docs' face and its queries - and tends the agents. Notes: side-session-notes/local_325ef65d-55c6-44bd-85b9-53de24869d6e/orchestration-3.md. LIVE: surya lane - waker scheduled task linux-phone-keeper-waker (hourly) only nudges the surya coordinator (local_0ecf107e), reading tad q phone-next; the coordinator starts keepers, which take tad q phone-next (one row). Walleye lane - walleye coordinator (local_7fb92f70); google-walleye (FA81N1A00790) sits in fastboot; devlab fastboot state|getvar|boot now|reboot now, by serial. devlab-watch@surya-lab runs ~/.local/bin/devlab built from ~/Projects/linux-phone-oco/lab-tools at main (1b35fc6); suite put --runner builds in that tree, so build devlab only from it. lpoco-health 0.1.7 published by the conveyor (lpoco-health-v tags); #78's provides + old-name links ship with the next release. LANDED THIS TURN OF THE ROLE (2026-11-17): lab-tools 71 (kernel try reads the booted entry off cmdline initrd=initramfs-NAME), 72 (suite put --runner builds the runner), 79 (fastboot by serial; flash only with [fastboot] writes = true; guard refuses raw fastboot but devices/getvar/help); device-template 3; docs 202 (queries/phone-next.sql, 603 B vs 14.9 KB), 224 (decision 2026-11-17-fastboot-by-serial-writes-by-manifest). OWED: (1) the read-weight of the first keeper the surya coordinator starts with Role: keeper / Name: lines (it was asked to send the session id) -> ideal-agent-roles local_dd7369b2, backlog measure-a-role-start; the 12:33 scheduled keeper read 75,649 tok / 39 KB, not comparable (route, connectors). (2) trim the briefs of what the role cards now say (renew thresholds, the read-only-when shape, recording rules said three times); start-weight after docs 230: phone-keeper 25.6 KB, surya lane 21.1, coordinator 22.4, orchestration 27.5. (3) lab-tools backlog by the weakest link: kernel-orphan-modules next (health-*, hear-* are lpoco-health's). WAITS ON OTHERS: surya-lab surya-fastboot-serial (phone queue: devlab flash refuses surya until its manifest says [fastboot] serial, likely dc21014b unread, and writes = true); google-walleye-lab [fastboot] serial line (walleye coordinator's). The author's: dispatcher permission mode/model, gather.yml in five repos, archiving linux-phone-oco/lens, cards for charging, GPS, programs on argenv. DO NOT UNDO: suite put takes the Alpine package and reads the lab at main; gather lands only after 15 quiet minutes; a kept kernel sorts 1-kept-* after tries; remove keeps shared modules; every fastboot call names its serial and nothing is written over fastboot without writes = true; kernel try trusts LoaderEntrySelected, then the running initramfs, then the release name. SIGNS: land is killed (143) when its wait outlives the caller's timeout - run it in the background; make verify refreshes docs/ and IKB.md, run it twice or render first; a hook from before 0.3.2 re-roles a running session on any quoted Role: line - do not quote Role lines to older sessions.
2026-11-17
Where does orchestration's work stand, for a fresh orchestration session to take it up without this session's long context?
ROLE: orchestrator (brief ideal-agent-linux-phone-oco/orchestration.md). Notes and the move scripts (move-lane.sh, replay.sh, select.sh): side-session-notes/local_7d95b264-ad32-49ad-932a-7f19e9f9806d/move/. DONE 2026-11-17 (decision 2026-11-17-commons-and-device-bases, all landed and read back from main): google-walleye-lab #14 and surya-lab #134 got their own tad bases from device-template; walleye's rows moved (google-walleye-lab #15, docs #353) and surya's (surya-lab #136 with all 143 runs identical row for row, docs #360), each under the lease orchestration-move, by the rule of decision 2026-11-17-moving-a-lane; the lane briefs (walleye-coordinator, surya-coordinator, phone-keeper), the five launchers and the waker read the lab's own base (phone-next, lane-next --needs, phone-stands) and record with ikb; device-template got lane-next and phone-stands; lab-tools #82 (gather files into the base; devlab-watch@surya-lab restarted on it); tad 0.7.1 (references by a table's key; pins bumped in the template and both labs); feed-device-bases (#355, #356) pulls each base's parts daily and devices.base names both labs (#361); the face rendered from the pulled parts. move-device-rows, gather-into-device-base, launchers-per-device done. OPEN (commons-only): derive-parts-in-base (a base derives parts.measured from its own runs; until then surya's measured fields stay as seeded at the move), about-across-bases (abouts naming the device, a milestone or another base's subject were left empty in the move), device-template-follow; the older owed items of orchestration-2026-11-17-night (keeper read-weight, trimming briefs, kernel-orphan-modules) still stand. WAITS ON OTHERS: the walleye coordinator closes docs PRs 335, 337, 310 and settles 316 (two unlanded s0n-try rows contradicting main; to be recorded in the lab if they hold). SIGNS: a shared ~/.local/bin/tad was overwritten by another project's make setup (0.5.0) - install-tad.sh defaults to ~/.local/bin on a shared lab; jq's index(.) inside a pipe evaluates . against the array (bind $x first); the ideal-agent guard now refuses writing tad sql (TAD_SQL_WRITE_OK=1 for a recorded one-time migration); a refused command skips its git checkout too - read the branch before committing; land refuses a branch that puts back lines main changed; a pages build is not triggered by the feeds bot's push (the 3-hourly schedule catches up). DO NOT UNDO: the previous hand-overs' lists; no walleye or surya rows land in docs any more - a lane records in its lab.
2026-11-17
Where does orchestration's work stand, for a fresh orchestration session to take it up without this session's long context?
ROLE: orchestrator (brief ideal-agent-linux-phone-oco/orchestration.md, which opens with its Role/Name lines). Owns the conveyor - lab-tools/devlab, device-template, the Alpine path, docs' face and queries - and tends the agents. Notes: side-session-notes/local_325ef65d-55c6-44bd-85b9-53de24869d6e/orchestration-3.md (state, signs, every landing of 2026-11-17). LIVE: surya lane - surya coordinator (local_0ecf107e) starts keepers with Role: keeper / Name: surya-keeper-N / Also practices: 42 and phone-keeper.md by path; waker linux-phone-keeper-waker only nudges it, reading tad q phone-next --device xiaomi-surya. Walleye lane - walleye coordinator (local_7fb92f70); google-walleye in fastboot on slot b with slot a unbootable (its bootloader's doing in a RAM boot try); slot_switch stays false until its decision and the author's word. ~/.local/bin/devlab is built from ~/Projects/linux-phone-oco/lab-tools at main (d510232); devlab-watch@surya-lab restarted on it. LANDED SINCE THE EVENING HAND-OVER: lab-tools 80 (fastboot boot reads the slots' flags before/after and says where the phone went; set-active gated by [fastboot] slot_switch); docs 242 (the eight briefs restored after 226 reverted 230's role start), the slots item closed, gather-into-device-base recorded; reviewed: device-template 4 (each device's own tad base: parts contract, phone-next/phone-queue/next without --device), docs 260 (backlog.device, lane-next; kept until the split moves rows). DECIDED (the author, via the Top Coordinator): docs holds only what helps every device; each device has its own base from device-template; docs pulls parts and derives support_status (decision 2026-11-17-commons-and-device-bases; backlog tad q next --about commons-only). Next links: feed-device-bases (docs), move-device-rows (with each keeper), then lab-tools/gather-into-device-base (orchestration's, waits on the move) and launchers-per-device (roles). OWED: the clean 'after' read-weight - the first keeper started with Role lines on ideal-agent 0.3.6+ (keeper-6: 80,864 tok/30 KB; keeper-7: 79,870 tok but every practice, the hook then skipped started sessions) -> ideal-agent-roles local_dd7369b2; trimming the briefs of what the role cards say; tad-engine sign: a conditional rule (needs requires device), after the split; lab-tools kernel-orphan-modules. lab-agent's future is the Top Coordinator's research (research-lab-agent); devlab's root-exec/board uses move only on its word. WAITS ON OTHERS: surya-lab surya-fastboot-serial (devlab flash refuses surya until its manifest has [fastboot] serial, likely dc21014b unread, and writes = true); walleye's slot decision. DO NOT UNDO: the previous hand-over's list; every fastboot call names its serial; no partition write without writes = true, no slot switch without slot_switch = true; a boot's verdict is where the phone went and the flags, not fastboot's exit. SIGNS: rebase and read diff --stat origin/main...HEAD before land (226 reverted 230); land's commit title is at most 100 characters and a research brief at most 200; a hold sent after a yes may arrive after the landing - say hold before yes when a direction is open.
2026-11-17
Where does orchestration's work stand, for a fresh orchestration session to take it up without the old session's long context?
ROLE: owns the conveyor - lab-tools (devlab: phone, kernel try/keep/--dtb/remove, suite put from the Alpine package and the lab's main, gather once quiet, watch, guard for the phone, hazards, keeper lease), device-template, the package conveyor's Alpine path (alpine.yml, v1), docs' face (bin/face-data + engine, no ocoeco) and derive/queries - and tends the agents. Brief: ideal-agent-linux-phone-oco/orchestration.md; method: ideal-agent orchestrate-agents. LIVE: phone keeper flow (phone-keeper.md; lease devlab keeper; queue tad q phone-queue in the author's rank order, deep sleep first; waker = scheduled task linux-phone-keeper-waker titled surya dispatcher, hourly; patrol every 6 h). surya-keeper-2 held the lease at 12:49 UTC. OPEN, the author's: the dispatcher task's permission mode/model (its runs stall on the first prompt; Sonnet 5.5 medium proposed); whether dispatcher runs start from orchestration instead (visible in the left pane); gather.yml in five repos and land's observatory pings (passive ocoeco links, his call); archiving linux-phone-oco/lens; cards waiting: research charging, research GPS, programs on argenv. OPEN, orchestration's: run read-weight on surya-keeper-2's transcript and send ideal-agent its read and first-turn tokens (where read-weight lives was asked of ideal-agent); add read-weight to the patrol round; backlog start-weight-on-the-face, kernel-orphan-modules, health-carry-old-checks, guard items moved to ideal-agent. DO NOT UNDO: suite put reads the lab at main (a stale clone once regressed the phone); gather lands only after 15 quiet minutes; the face's data sorts like observe did and maps a non-linux-phone project field to docs; a kept kernel sorts 1-kept-* after tries; remove keeps shared modules. Notes: side-session-notes/local_12b18c70-.../orchestration-2026-11-17.md.
2026-11-17
What works on the Google Pixel 2 (walleye) and Pixel 2 XL (taimen) on Linux today, by published sources, and how does their SoC (MSM8998) relate to surya's SM7150?
A survey from published sources only (nothing touched, nothing measured here; every part of both phones is unknown, the reports sit in support_status notes and wiki_claims). (1) Nura (postmarketOS) wiki: only the Pixel 2 XL has a page (kernel field 5.10-rc2; 'Boots but no display output'; usbnet Y, flashing Y, screen N, battery N; page by Casey/kcxt, edited 2026-09-05, bot edit 2026-09-27); the Pixel 2 has none. (2) pmaports: neither device-google-walleye nor device-google-taimen exists in device/main, community or testing (listed 2026-11-17). (3) Mainline Linux: no Pixel 2 device tree; arm64/qcom has MSM8998 boards (OnePlus 5/5T, Xiaomi Mi 6, Sony yoshino, F(x)tec Pro1, HP Envy x2, Lenovo Miix 630, Asus NovaGo) and msm8998.dtsi was still edited on 2026-09-17. (4) The port lives out of tree: kcxt/linux-wahoo, created 2020-07-20, last pushed 2022-02-27; branch wahoo/5.17 has msm8998-google-taimen.dts, -walleye.dts and wahoo.dtsi, plus panel and DPU/DSC work (unfinished), and a taimen-5.11-submit branch whose mainline submission is not found upstream. (5) Other distributions: Ubuntu Touch has only a 16.04 (Halium, Android kernel) release for walleye, the current release does not support it (taimen page exists, not read); LineageOS 22.2 runs both on Android (kernel 4.4, AOSP branch android-msm-wahoo-4.4-android10-qpr3 shared by both). Not found for either: Mobian, Droidian, Sailfish, a pmOS issue or MR (search only; absence is not a report). SoC and surya: MSM8998 (Snapdragon 835, 2017) vs SM7150 (Snapdragon 732G). Per mainline msm8998.dtsi it has Adreno 540, DPU/MDSS with 10 nm DSI PHY, UFS 2.0, DWC3 USB with QMP PHYs, ADSP/SLPI/modem remoteprocs, Venus and the older RPM (rpm-msm8998, glink-smd-rpm), so what surya's SM7150 shares is the kind of block (UFS, DWC3/QMP USB, DSI/DPU display, remoteproc DSPs, SPMI PMIC) but not the drivers or tables: SM7150 itself is not in mainline Linux (surya runs the sm7150-mainline fork; the nearest mainline Qualcomm sibling is sdm670, the Pixel 3a), and MSM8998 has Adreno 5xx and RPM where SM7150 has Adreno 6xx and RPMh (our reading of the trees, not a source's claim). Sibling evidence for the SoC: the wiki's OnePlus 5 (archived, kernel field 6.0) reports touch, screen, wifi, Bluetooth, 3D, GPS Y and audio, mobile data, calls, SMS, sensors N: a different phone, stale, context only. Distance: surya has 12 of 20 parts working by its own tests; the Pixel 2 XL has 1 community 'works' (flashing), 1 'broken' (screen) and 19 unknown; the Pixel 2 has nothing reported.
- Nura (postmarketOS) wiki: Google Pixel 2 XL (google-taimen) - Mainline boots with a basic DT (5.10-rc2), USB networking and flashing work, no display; the only wiki page of either phone (walleye has none). Revised 2026-09-05 and 2026-09-27 (bot); status by Casey/kcxt.
- kcxt/linux-wahoo: Mainline Linux for the Google Pixel 2XL (And 2?) - Out-of-tree mainline port, created 2020-07-20, last pushed 2022-02-27: msm8998-google-taimen.dts, -walleye.dts and wahoo.dtsi (branch wahoo/5.17), panel and DPU/DSC work, a 5.11 submission branch.
- Linux mainline: arch/arm64/boot/dts/qcom (MSM8998 device trees) - No Pixel 2 / 2 XL device tree in mainline (checked 2026-11-17); MSM8998 boards there: OnePlus 5/5T, Xiaomi Mi 6, Sony yoshino, F(x)tec Pro1, HP Envy x2, Lenovo Miix 630, Asus NovaGo; msm8998.dtsi still edited (2026-09-17).
- Nura pmaports: device packages of Google phones (device/community, device/testing) - device-google-walleye and device-google-taimen are absent from device/main, community and testing (listed 2026-11-17); Google packages there are sargo/bonito (community), blueline, flame, oriole, raven (testing).
- Ubuntu Touch: Google Pixel 2 (walleye), old releases - Only the 16.04 (xenial) release exists; the current release does not support the phone. A Halium/Android-kernel port, not mainline.
- LineageOS wiki: Google Pixel 2 (walleye) - Android, current LineageOS 22.2 (Android 15) on kernel 4.4 for walleye; taimen has the same page shape. Shows the phones stay alive on Android, not on mainline.
- AOSP: Build Pixel kernels (legacy branches) - Pixel 2 and 2 XL share one kernel, device/google/wahoo-kernel, branch android-msm-wahoo-4.4-android10-qpr3.
- Nura wiki: OnePlus 5 (oneplus-cheeseburger), the MSM8998 phone best supported in mainline - Same SoC family; category archived, kernel field 6.0; touch, screen, wifi, bluetooth, 3D, GPS Y; audio, mobile data, calls, SMS, sensors N. A claim about a different phone: context for the SoC, not a status of the Pixels.
2026-11-17
Where do linux-phone-oco's founding principles live, and how do briefs and guides cite them without restating?
Read: Debian Social Contract and DFSG (5 and 10 numbered points, versioned 1.0-1.2, cited as DFSG #n), Mozilla Manifesto (10 principles, anchors principles-01..10), Wikipedia five pillars (shortcuts WP:5P1..5, redirects keep citations after renames), Rust API guidelines (54 items with ids such as C-CASE that are the anchors), RFC 7282 and PEP 20 (cited by section or wording), the kernel's Developer's Certificate of Origin 1.1 (the version is part of the name), MADR decision drivers (local to one record). Not read: Arch principles (blocked), PEP 1, Nygard's ADR post, the Rust RFC process. Locally: the idea table holds the story (as good as Android, counted), conveyor concepts are five rows, restating lines sat in phone-keeper and device AGENTS.md; overlay-check (ideal-agent) flags a brief that restates ideal-agent's words by 6-word runs, 15 percent limit.
2026-11-17
What keeps a Qualcomm SoC out of its lowest state on mainline?
Any processor or bus vote left up: on a QCS8550 handheld, aosd, cxsd and ddr stayed at 0 until the USB controller's interconnect vote and the PCIe and LPASS (audio) votes were released, then it reached the floor at about 23 mA (2026-10). A DSP that never sleeps holds CX up; on surya the audio DSP has not slept once. FastRPC helpers attached across suspend crash the audio DSP: postmarketOS stops hexagonrpcd's helper before suspend on the Pixel 3a, as we saw on surya (24 of 24 attempts with rootpd attached). Wi-Fi (ath10k) floods the modem's IPC interrupt and blocks or breaks suspend on SDM845; surya is reported to wake at random while asleep, cause unknown.
- PortareOS issue 62: aosd/cxsd/ddr stuck at 0 on QCS8550 until the USB, PCIe and LPASS votes were released (2026-10) -
- pmaports, google-sargo: hexagonrpcd's sensors helper stopped before suspend, the DSP crashing otherwise -
- pmaports 4783: with the modem wakeup on, every modem event wakes the phone; Wi-Fi blocks suspend -
- pmaports 4823: surya wakes at random while asleep (open) -
2026-11-17
How does a Qualcomm phone reach its lowest power state on mainline?
Through s2idle and CPU idle, not suspend to RAM: the firmware offers no PSCI system suspend, so with userspace frozen the CPUs enter their idle states, the last one down takes the cluster power domain to its deepest state (PSCI OS-initiated mode, hierarchical CPU idle), and as the cluster powers off the application processor's RPMh sleep votes are flushed to the always-on subsystem (rpmh-rsc attached to the cluster domain). The always-on subsystem then lowers CX and DDR when no processor votes for them: CX collapse (cxsd), then AOSS sleep (aosd), the floor. The SoC counts each in its own memory (rpmh-stats, read through qcom_stats), so reaching the floor is measured, not inferred. Without OS-initiated mode the cluster domain would stay always on and the votes would never flush; surya's firmware has it.
- LWN: hierarchical CPU idle and PSCI OS-initiated mode (Ulf Hansson's series) -
- rpmh-rsc: attach RSC to the cluster PM domain - sleep votes flushed when the cluster powers off (Ulf Hansson, 2022) -
- The qcom-stats binding: the SoC's sleep counters (aosd, cxsd, ddr, per subsystem) -
- Qualcomm: SoC power-saving states (CXSD, AOSD) on QCS6490 -
- Nura (postmarketOS) wiki, SDM845: s2idle only; waking for calls through the modem's IPCRTR glink wakeup -
2026-11-17
How does a Qualcomm phone on mainline wake for a call or a message?
The modem's messages (QMI over QRTR on glink) are handled even in s2idle (IRQF_NO_SUSPEND), but userspace is frozen, so nothing rings. The kernel cannot tell a call from a signal-strength update: there is one switch, the IPCRTR glink device's wakeup (/sys/bus/rpmsg/devices/4080000.remoteproc:glink-edge.IPCRTR.-1.-1/power/wakeup), which wakes for every modem message. postmarketOS (now Nura) pairs it on the OnePlus 6 with ModemManager's quick suspend/resume, which quiets the modem's notifications before suspend and resyncs after; that fixed calls signalled late or lost. It is still not dependable: on OnePlus 6/6T and the Pixel 3a waking for calls is reported not working (with the switch on the phone wakes at once; open since 2026-10), and with it on every modem event wakes the phone. surya's modem sits at the same address (remoteproc 4080000), so the same path applies; a SIM card is needed to prove it.
- Nura (postmarketOS) wiki, SDM845: s2idle only; waking for calls through the modem's IPCRTR glink wakeup -
- Nura (postmarketOS) wiki, OnePlus 6: ModemManager's quick suspend/resume and the IPCRTR wakeup -
- pmaports 4194: calls signalled late or lost across suspend - fixed by ModemManager's quick suspend/resume -
- pmaports 4989: waking from suspend for calls does not work (OnePlus 6/6T, Pixel 3a; open) -
- pmaports 4783: with the modem wakeup on, every modem event wakes the phone; Wi-Fi blocks suspend -
2026-11-17
How else have phones got deep sleep that still rings?
Android's own kernel: Ubuntu Touch runs officially on surya through Halium with the vendor's 4.14 kernel and Android's opportunistic suspend (wakeup sources and autosleep, which mainline also has), claiming a day and more - deep sleep that works, at the price of the vendor's kernel and blobs and nothing upstream. A separate power-management core: Crust on the PinePhone sleeps the whole Allwinner SoC (about 80% less power) and the separate modem wakes it through its RI line; Qualcomm's always-on subsystem runs signed firmware, so nothing like Crust can be written for it, and its modem is inside the SoC. Push through sleep: only partly solved anywhere (PinePhone: WoWLAN pattern matching plus an RTC wake as a safety net). The postmarketOS SM7150 page lists suspend as working with no measurement behind it; we found no published standby current for mainline Qualcomm phones.
- Ubuntu Touch on surya: Halium 10 with the vendor's 4.14 kernel -
- LWN: Android's opportunistic suspend in mainline - wakeup sources and autosleep -
- Crust on the PinePhone: deep sleep on a separate power-management core -
- Push notifications through suspend on the PinePhone: WoWLAN and an RTC safety net (2023) -
- Nura (postmarketOS) wiki, SM7150: suspend listed as working, no detail -
2026-11-17
What must a fresh linux-phone session read before its first useful action, per role, and is it within ideal-agent's budget (practice 45-keep-the-start-light: 32 KB a role, 3 KB a front file, 8 KB a brief)?
Measured 2026-11-17 on docs' main (495bbc6) with ideal-agent 0.2.1's scripts/start-weight, in bytes. Every role reads: the session start 14,353 (the practices without their reasons, and the inbox - 22.5 KB before ideal-agent #13 put the reasons a command away), skill and agent descriptions 4,057, lab-session-start 2,012, AGENTS.md 2,141, ideal-agent-linux-phone-oco/README.md 2,306 - 24,869 in all. Then the brief: bring-up 13,313 (38,182 in all: over the 32 KB budget, and the brief over 8 KB), orchestration 6,248 (31,117), phone-keeper 4,559 (29,428), feature-research 2,417 (27,286). Before #13 the same roles read 35-46 KB. The front files are within 3 KB. Whether summaries are due cannot be read yet: docs pins idealkb 0.1.0, whose about query has no summaries (0.3.0 comes with the weekly pin).
2026-11-17
What does a first mainline boot of the Pixel 2 need, and what can and cannot fastboot boot do on this bootloader?
Image: boot header v0, base 0x0, kernel offset 0x8000, ramdisk 0x1000000, tags 0x100, page 4096 - verified by porthole against the stock TAIMEN boot.img; LineageOS's wahoo board config says tags 0x01E00000 / ramdisk 0x02000000 instead: two sets are reported, walleye's own stock boot.img header decides (not read yet). Boot partition is 32 MiB (getvar boot_a 0x2000000), max-download-size 0x20000000: size is no limit. The DTB is appended to the kernel; it must carry qcom,msm-id = <0x124 0x20001> (taimen has it, kcxt's walleye does not). Cmdline (porthole): clk_ignore_unused ignore_loglevel panic=10 earlycon=msm_serial_dm,0xc1b0000 qcom_wdt.arm_on_probe=1 watchdog.open_timeout=300 reboot=w; kcxt adds console=ttyGS0,115200. No bootargs/stdout-path in the DTS: ABL appends the boot.img cmdline with fdt_appendprop_string, and a pre-existing bootargs hides it. Display: command-mode panels, so no scanned-out framebuffer for simple-framebuffer; the first sign of life must be USB. Path: dwc3 peripheral, high-speed only, SuperSpeed PHY dropped, qcom,select-utmi-as-pipe-clk, assigned-clock-rates 19.2/60 MHz (works on taimen); initramfs with a configfs gadget (ACM console + RNDIS/ECM) and telnet/ssh on 172.16.42.1 (devlab's address). pstore: ramoops 0xa1810000/0x200000; a cold reset scrambles it, so the warm-reset/watchdog parameters matter. UART: the Pixel debug cable (see google-walleye-how-others-booted; fastboot oem uart enable is a change to the phone, undecided). Bootloader (keeper's read-only getvar, google-walleye-bootloader-first-look): mw8998-003.0085.00, hw-revision MP1, unlocked, A/B both slots successful, avb_version 1.0.0, kernel:uefi, no fastbootd. fastboot boot: TWRP's own instructions for walleye use it (xdaforums), but another report could not boot TWRP that way, and nobody reports a mainline kernel booted from RAM on any Pixel 2: NOT known. Also not known: whether ABL applies the stock dtbo of the active slot to a mainline DTB (taimen's bootloader refuses a kernel unless dtbo holds overlay id 2704 - kcxt's README, taimen only; porthole flashes its own stub into slot b), and what vbmeta/AVB does to an unsigned image on an unlocked phone. One try through devlab (walleye-first-fastboot-boot) answers all three; a refusal is an answer, and the stub dtbo is a write (the author's decision; backlog walleye-dtbo-overlay-id).
- porthole-dev/pmaports (branch taimen-bringup): mainline 7.2.2 + 263 patches, device-google-taimen, walleye board patch 0029 - porthole-dev, 2026 The one maintained mainline Pixel 2 family kernel: taimen proven, walleye board file untested. deviceinfo gives the boot image header (v0, offsets, appended dtb); the dtbo stub (id 2704) and cmdline are the first-boot facts.
- Nura (postmarketOS) wiki: Google Pixel 2 XL (google-taimen) - Mainline boots with a basic DT (5.10-rc2), USB networking and flashing work, no display; the only wiki page of either phone (walleye has none). Revised 2026-09-05 and 2026-09-27 (bot); status by Casey/kcxt.
- kcxt/linux-wahoo wahoo/5.17: msm8998-google-wahoo.dtsi, taimen and walleye dts, 2022 - kcxt, 2022 The first Pixel 2 family device tree; walleye dts is a 13-line stub on the taimen base; USB 2.0 peripheral, regulators, ramoops, UART facts.
- kcxt/dtbo-google-wahoo-mainline: minimal dtbo for the Pixel 2 XL - walleye-research-vendor, 2020 The Pixel 2 XL bootloader refuses a kernel unless dtbo holds an overlay with id 2704 (0xa90); stock cmdline has androidboot.dtbo_idx=12. XL only; walleye's id not known.
- LineageOS android_kernel_google_wahoo (lineage-22.2): device-tree sources of walleye and taimen - Google, HTC, LG, Qualcomm; kept by LineageOS, 2025 GPL-2.0 Linux 4.4 kernel of both wahoo phones. Walleye (HTC-built, project name muskie) is under arch/arm64/boot/dts/htc: panel, touch, audio amp, haptics, NFC, camera, battery, memory map. Read as facts for a hardware table; ports of code keep copyright and licence.
- TWRP 3.2.3-1 for Pixel 2 (xdaforums): temporary boot with fastboot boot - TWRP / XDA community, 2018 fastboot boot of a recovery image works on the unlocked walleye, so a boot image can be held in memory without a flash.
- kerneltoast/android_kernel_google_wahoo (11.0.0-sultan): Google's GPL wahoo kernel, device-tree sources under htc/ (Pixel 2) and lge/ (Pixel 2 XL) - Google, HTC, LG (GPL-2.0), 2020 Walleye's parts from GPL device-tree sources: Samsung S6E3FA5 command-mode panel, Synaptics RMI touch on i2c5, DRV2624 haptics, TFA98xx/TAS2557 amps, keys, battery; read for facts, not copied.
- LKML March 2021: [PATCH] arm64: dts: add support for the Pixel 2 XL, with review - walleye-research-vendor, 2021 Boots with USB networking, panel needs DSC, dtbo overlay id required, clk_ignore_unused, Wi-Fi needs diag-router; no sign it was merged.
2026-11-17
What does the Pixel 2 bootloader dislike in our boot images (Load Error), from public sources, and which variants should be tried next?
What is: four images, one kernel/dtb/initramfs, all v0 with the dtb appended to a gzipped Image (Image.gz+dtb). a (taimen offsets, os word 0) got "Booting OKAY" then silence; b (LineageOS offsets) first left fastboot (Android came back on slot b), later Load Error; c and d (a, b plus os_version 8.1.0 / patch 2020-01) both Load Error. The only difference between a and c is that header word. What others show (not the Pixel 2 itself - nobody reports a mainline fastboot boot there): 1. The format is the accepted one. Stock ABL on the same line (Pixel 3) takes a gzipped kernel with the dtb appended in a v0 boot image (U-Boot's board doc), and postmarketOS boots blueline with exactly base 0 / kernel 0x8000 / ramdisk 0x1000000 / tags 0x100 / page 4096 / dtb appended (pmaports deviceinfo). Two differences from our images: pmaports sets second offset 0 (we use 0xf00000; second is empty, so it should not matter) and no os_version/patch level at all. So "header v0 vs what ABL expects" and "Image.gz-dtb vs Image+dtb" are not the likely cause; the os word is, if anything, the one thing we added that pmaports does not have. 2. ABL, not the kernel, picks and patches the dtb (Inoki, MSM8998 Nokia 8): DeviceTreeAppended scans the appended blobs and DeviceTreeCompatible matches qcom,msm-id, qcom,board-id and qcom,pmic-id. Our dts carries only msm-id (0x124 0x20001, as kcxt's taimen, which boots with msm-id alone); it has no board-id or pmic-id. Whether walleye's ABL accepts that is not known; the stock walleye dtb's ids are not read yet (not in the public sources reached today). 3. The bootloader merges a dtbo overlay into the dtb before the kernel starts (AOSP DTO). kcxt found the taimen bootloader refuses a mainline kernel unless the dtbo partition holds an overlay with id 2704, and flashes a stub. Stock overlays patch downstream nodes a mainline base does not have, so a failed merge is the best-fitting reading of an immediate "Load Error" that comes from the bootloader after the transfer. Not proven for walleye: the dtbo of slot b is an older LineageOS build's, its overlay table not read. 4. "Load Error" is not proof the image is bad. Known-good TWRP for walleye got the same words from fastboot boot (Android SE), and one XDA report says it appeared randomly and went away on restart. Our slot flags (a unbootable, current b) were left by the first try; whether they feed the refusal is not known. 5. "Booting OKAY" then silence (a) means the bootloader sent its OK and a later step failed or the kernel died before any sign of life; it is a different outcome from Load Error, and a is the only image that got it. The os word turning OKAY into Load Error says the refusal is sensitive to the header word - the likeliest reason is the bootloader comparing the os_version/patch level with the active slot's recorded one (not read anywhere; unknown). Ranked causes (each has a try that tells it apart): (H1) overlay merge fails against a mainline base, so a stub dtbo or a dtb that survives the stock overlay is needed - only fixable by a write (dtbo_b stub) or by finding that slot b's dtbo is not the cause; (H2) dtb ids: msm-id only, no board-id/pmic-id; free to test on the host; (H3) state: slot flags or random Load Error; test with a control image; (H4) header word: only os word 0 passes, so keep 0. Control first: a stock-format image known to boot on walleye (LineageOS or TWRP recovery for walleye, public) through the same fastboot boot path. If the control also gets Load Error, the cause is the phone's state and no image change helps; if it boots, the cause is in our image and the variants below tell which part. The control is a try, not a write. Not read yet and worth reading without writing: walleye's stock boot.img header and dtb ids from a public LineageOS wahoo build (host only), slot b's dtbo overlay ids (pstore/Android adb read - keeper only).
- U-Boot doc: Qualcomm generic boards (booting through ABL on Pixel 3) - walleye-research, 2024 Stock ABL (Pixel 3 family, same ABL line as walleye) expects a gzipped kernel with the dtb appended, packed as an Android boot image; U-Boot mimics Linux to satisfy it.
- pmaports device-google-blueline deviceinfo (Pixel 3, booted on stock ABL) - walleye-research, 2025 A working recipe on a sibling Pixel ABL: base 0, kernel 0x8000, ramdisk 0x1000000, second 0x0, tags 0x100, page 4096, dtb appended, cmdline console=ttyMSM0,115200 only, no os_version.
- Android Bootloader and Linux Internal based on Nokia 8 (NB1): DT loading in ABL - walleye-research, 2022 On an MSM8998 phone ABL's DeviceTreeAppended scans every dtb appended to the kernel and DeviceTreeCompatible picks the best by qcom,msm-id, qcom,board-id, qcom,pmic-id; the ABL, not the kernel, chooses and patches the dt.
- Android: Use multiple DTs (device tree overlays in the bootloader) - walleye-research, 2026 The bootloader loads the SoC dtb, identifies the board, loads the matching dtbo overlay from the dtbo partition and merges them before starting the kernel: a failed merge is a bootloader refusal.
- Android SE: Pixel 2 bootloader loop, fastboot boot of TWRP walleye gives Load Error - walleye-research, 2019 A known-good walleye TWRP image also gets 'Failed to load/authenticate boot image: Load Error' from fastboot boot when the phone's slot state is odd: the message is not proof the image is bad.
- XDA: Troubles reinstalling TWRP [Failed to load/authenticate boot image: Load Error] - walleye-research, 2020 One report fixed Load Error by restarting the device: it appears randomly when flashing - state, not content, can cause it (excerpt read in search results only).
- kcxt/dtbo-google-wahoo-mainline: minimal dtbo for the Pixel 2 XL - walleye-research-vendor, 2020 The Pixel 2 XL bootloader refuses a kernel unless dtbo holds an overlay with id 2704 (0xa90); stock cmdline has androidboot.dtbo_idx=12. XL only; walleye's id not known.
- porthole-dev/pmaports (branch taimen-bringup): mainline 7.2.2 + 263 patches, device-google-taimen, walleye board patch 0029 - porthole-dev, 2026 The one maintained mainline Pixel 2 family kernel: taimen proven, walleye board file untested. deviceinfo gives the boot image header (v0, offsets, appended dtb); the dtbo stub (id 2704) and cmdline are the first-boot facts.
- kcxt/linux-wahoo branch wahoo/5.17: msm8998-google-walleye.dts and the shared wahoo dtsi - walleye-research-vendor, 2022 What mainline can already express for wahoo: UFS, USB peripheral, one DSI, GPU, Wi-Fi, SLPI/ADSP, regulators; walleye file is 13 lines and sets no panel; boots with console on ttyMSM1 and USB-gadget ttyGS0, ramoops at 0xa1810000.
2026-11-17
What exists for the Pixel 2 (walleye) on mainline: kcxt/linux-wahoo, the other trees, which nodes work, what is missing?
Mainline (v7.3, v7.4-rc3 out) has no msm8998-google-* file and nothing was submitted to the lists that a search finds. kcxt/linux-wahoo (last push 2022-02-27, branch wahoo/5.17 = 5.17 fork of the MSM8998 community tree): msm8998-google-wahoo.dtsi (shared) + taimen.dts (LG SW43402 panel, qcom,msm-id 0x124 0x20001) + walleye.dts, which is 13 lines: model and compatible only, no qcom,msm-id, no panel or battery. The shared dtsi enables: UART (blsp2_uart1 earlycon), Bluetooth, pm8998/pm8005/pmi8998 regulators, qusb2phy + dwc3 as USB 2.0 peripheral only (SuperSpeed does not work), UFS + PHY, Wi-Fi, adsp/slpi/mss remoteprocs with wahoo firmware names, mdss/dsi0/DSC panel, Adreno 540 (GPU voltage raised as a hack), ramoops at 0xa1810000. Its bootargs in the dts is wrong with this bootloader (see walleye-first-boot-recipe). Per the Nura wiki (taimen, kernel 5.10-rc2): boots, USB networking works enough for a shell, needs clk_ignore_unused; display broken, battery broken, everything else untested. porthole-dev/pmaports taimen-bringup (2026-10): kernel = kernel.org v7.2.2 + 263 numbered patches; taimen is a daily-driver port (display, GPU, touch, haptics, amps, wifi, modem, sensors, camera, suspend). For walleye only patch 0029: a 33-line board dts with a 2700 mAh battery taken from the published spec, "nobody has run this branch on an actual walleye device yet"; "no dedicated display or camera overrides" - walleye's panel and touch are not in it. pmaports/Nura masters: no walleye or taimen package. Missing for walleye (all unknown on the phone): display (S6E3FA5 command-mode panel: no mainline driver), touch (Synaptics RMI: driver in mainline, node missing), USB (taimen only), UFS (taimen only), Wi-Fi, modem, sound (amps differ from taimen), haptics (DRV2624, no mainline driver), fuel gauge (out of tree).
- kcxt/linux-wahoo wahoo/5.17: msm8998-google-wahoo.dtsi, taimen and walleye dts, 2022 - kcxt, 2022 The first Pixel 2 family device tree; walleye dts is a 13-line stub on the taimen base; USB 2.0 peripheral, regulators, ramoops, UART facts.
- kcxt/linux-wahoo: Mainline Linux for the Google Pixel 2XL (And 2?) - Out-of-tree mainline port, created 2020-07-20, last pushed 2022-02-27: msm8998-google-taimen.dts, -walleye.dts and wahoo.dtsi (branch wahoo/5.17), panel and DPU/DSC work, a 5.11 submission branch.
- porthole-dev/pmaports (branch taimen-bringup): mainline 7.2.2 + 263 patches, device-google-taimen, walleye board patch 0029 - porthole-dev, 2026 The one maintained mainline Pixel 2 family kernel: taimen proven, walleye board file untested. deviceinfo gives the boot image header (v0, offsets, appended dtb); the dtbo stub (id 2704) and cmdline are the first-boot facts.
- Nura (postmarketOS) wiki: Google Pixel 2 XL (google-taimen) - Mainline boots with a basic DT (5.10-rc2), USB networking and flashing work, no display; the only wiki page of either phone (walleye has none). Revised 2026-09-05 and 2026-09-27 (bot); status by Casey/kcxt.
- Linux v7.3 (mainline): arch/arm64/boot/dts/qcom msm8998 boards, drm/panel, input/rmi4, power/supply - kernel.org mainline, 2026 What mainline already has for MSM8998 (DPU, DSI PHY, Adreno 540, UFS, dwc3, qusb2, wifi, charger, rmi4) and what it lacks for the Pixel 2 (no Google board, no S6E3FA5, no fuel gauge, no DRV2624, no TAS2557).
- Nura pmaports: device packages of Google phones (device/community, device/testing) - device-google-walleye and device-google-taimen are absent from device/main, community and testing (listed 2026-11-17); Google packages there are sargo/bonito (community), blueline, flame, oriole, raven (testing).
2026-11-17
Which MSM8998 boards are in mainline, and which nodes and drivers can walleye reuse; what do its parts need?
Boards in v7.3: msm8998-mtp, OnePlus 5/5T (cheeseburger/dumpling, common dtsi), Xiaomi Mi 6 (sagit), Sony Xperia XZ Premium/XZ1/XZ1 Compact (yoshino lilac/maple/poplar), F(x)tec Pro1, HP Envy x2, Asus Novago, Lenovo Miix 630. Best templates: OnePlus common dtsi (blsp1_i2c5 touch, gpio-keys, ufs, usb3 peripheral, wifi, ramoops, zap shader region, qcom,msm-id 292 0x20001 "required for bootloader to select correct board") and the Mi 6 (same i2c5 touch bus). SoC pieces already in msm8998.dtsi: ufshc+ufsphy, dwc3+qusb2, mdss/dpu/dsi0+10nm PHY, adreno-540.1, gpucc, wcn3990 wifi, smmus, mss/adsp pas remoteprocs, pinctrl; pmi8998 charger + rradc + wled + lpg + flash; drivers rmi_i2c, rmi_f1a, qcom_smbx, stmfts. Walleye parts (GPL downstream dtsi): Samsung S6E3FA5 5.0" 1080x1920 DSI command mode (TE on, reset gpio94, rails PM8998 L14 1.8 V and L22 3.0 V, DCS backlight: no WLED and no LAB/IBB, which taimen needs) - mainline has s6e3fa7/fc2x01/ha2/ha8 but no fa5, an out-of-tree fa5 driver exists (OnePlus 5, Jami Kettunen) and porthole's sw43402 shows the command-mode + DPU work that is needed; touch Synaptics RMI on i2c5@0x20, irq gpio125, reset gpio89, l6/l28 rails -> node only; haptics DRV2624 (driver out of tree, porthole 0018); speaker amp TI TAS2557 as on taimen (TFA98xx is in the tree but disabled, an older revision); codec WCD934x on SLIMbus; keys gpios 40/126/121; battery 2700 mAh/4.4 V; NFC PN81A, fingerprint FPC1020 later. Fuel gauge qcom_fg out of tree (porthole 0022). Reuse rule: take the board file from the GPL wahoo dtsi (Caleb Connolly, Giuseppe Maggio; licence kept), patches from porthole one at a time when a part needs one.
- Linux v7.3 (mainline): arch/arm64/boot/dts/qcom msm8998 boards, drm/panel, input/rmi4, power/supply - kernel.org mainline, 2026 What mainline already has for MSM8998 (DPU, DSI PHY, Adreno 540, UFS, dwc3, qusb2, wifi, charger, rmi4) and what it lacks for the Pixel 2 (no Google board, no S6E3FA5, no fuel gauge, no DRV2624, no TAS2557).
- kerneltoast/android_kernel_google_wahoo (11.0.0-sultan): Google's GPL wahoo kernel, device-tree sources under htc/ (Pixel 2) and lge/ (Pixel 2 XL) - Google, HTC, LG (GPL-2.0), 2020 Walleye's parts from GPL device-tree sources: Samsung S6E3FA5 command-mode panel, Synaptics RMI touch on i2c5, DRV2624 haptics, TFA98xx/TAS2557 amps, keys, battery; read for facts, not copied.
- LineageOS android_kernel_google_wahoo (lineage-22.2): device-tree sources of walleye and taimen - Google, HTC, LG, Qualcomm; kept by LineageOS, 2025 GPL-2.0 Linux 4.4 kernel of both wahoo phones. Walleye (HTC-built, project name muskie) is under arch/arm64/boot/dts/htc: panel, touch, audio amp, haptics, NFC, camera, battery, memory map. Read as facts for a hardware table; ports of code keep copyright and licence.
- kcxt/linux-wahoo wahoo/5.17: msm8998-google-wahoo.dtsi, taimen and walleye dts, 2022 - kcxt, 2022 The first Pixel 2 family device tree; walleye dts is a 13-line stub on the taimen base; USB 2.0 peripheral, regulators, ramoops, UART facts.
- porthole-dev/pmaports (branch taimen-bringup): mainline 7.2.2 + 263 patches, device-google-taimen, walleye board patch 0029 - porthole-dev, 2026 The one maintained mainline Pixel 2 family kernel: taimen proven, walleye board file untested. deviceinfo gives the boot image header (v0, offsets, appended dtb); the dtbo stub (id 2704) and cmdline are the first-boot facts.
2026-11-17
What is the shortest honest path to a mainline fastboot boot of the Pixel 2, and which kernel is built first?
Path: (1) kernel.org v7.3 + a new msm8998-google-walleye.dts (own file, GPL, from the wahoo dtsi, carrying qcom,msm-id) with only what a USB-reachable initramfs needs: reserved memory, pm8998/pm8005/pmi8998 RPM regulators, qusb2phy + dwc3 peripheral, ramoops, UART; UFS, display, GPU, wifi, remoteprocs disabled (no firmware, no storage touched). (2) v0 boot.img with the dtb appended. (3) initramfs with a USB gadget. (4) one fastboot boot through devlab; proof = host sees the gadget and answers on 172.16.42.1. Display, touch, UFS, charger follow, each by the bring-up method. Rejected: starting from porthole's 263-patch kernel (taimen-shaped, hard to tell what a walleye failure comes from; kept as the fallback and the patch source); kcxt's 5.17 (old, bootargs in the dts, no msm-id, unmaintained); a display-first or simple-framebuffer start (command-mode panel: no framebuffer to reuse); flashing dtbo/boot first (breaks decision walleye-fastboot-first; only if the one try shows ABL needs the stub dtbo, and then the author decides). Unknown: see walleye-first-boot-recipe (walleye boot.img header, dtbo/ABL with a mainline dtb, vbmeta, whether a mainline kernel boots from RAM on a Pixel 2 at all).
- porthole-dev/pmaports (branch taimen-bringup): mainline 7.2.2 + 263 patches, device-google-taimen, walleye board patch 0029 - porthole-dev, 2026 The one maintained mainline Pixel 2 family kernel: taimen proven, walleye board file untested. deviceinfo gives the boot image header (v0, offsets, appended dtb); the dtbo stub (id 2704) and cmdline are the first-boot facts.
- kcxt/linux-wahoo wahoo/5.17: msm8998-google-wahoo.dtsi, taimen and walleye dts, 2022 - kcxt, 2022 The first Pixel 2 family device tree; walleye dts is a 13-line stub on the taimen base; USB 2.0 peripheral, regulators, ramoops, UART facts.
- Linux v7.3 (mainline): arch/arm64/boot/dts/qcom msm8998 boards, drm/panel, input/rmi4, power/supply - kernel.org mainline, 2026 What mainline already has for MSM8998 (DPU, DSI PHY, Adreno 540, UFS, dwc3, qusb2, wifi, charger, rmi4) and what it lacks for the Pixel 2 (no Google board, no S6E3FA5, no fuel gauge, no DRV2624, no TAS2557).
- TWRP 3.2.3-1 for Pixel 2 (xdaforums): temporary boot with fastboot boot - TWRP / XDA community, 2018 fastboot boot of a recovery image works on the unlocked walleye, so a boot image can be held in memory without a flash.
2026-11-17
How are tests organised, shipped and provisioned on Linux phones (postmarketOS, bootrr, LAVA, CI-tron, systemd), where do rust-script tests plus a bundle crate fit, and should we build fully on postmarketOS upstream?
postmarketOS (postmarketos-test subpackages, initramfs hook), bootrr, LAVA and CI-tron share one shape: a test is a small executable, a thin runner prints one pass/fail/skip line per case, the lab collects the lines, device facts live as data. Nobody compiles on the device. rust-script compiles on first run and needs rust+cargo on the phone (Alpine aarch64: 72 MiB download, 206 MiB installed plus gcc/musl-dev/llvm-libs, network for crates): fine on the lab, poor on a phone. A bundle crate that depends on tests (nextest discovery, inventory/linkme) is sound as design but unproven on aarch64 musl; one binary per test found by directory gives the same independence. Provisioning: an apk gives versions, uninstall and signatures at the price of a key and a repository (ours is published); a lab push is fast and leaves no version record. UPSTREAM (checked 2026-11-17; their sites now redirect to nura.eco): MRs on their GitLab with Alpine-style commit rules and approval rules; on-device tests are postmarketos-test-* subpackages run by an initramfs hook that halts the boot; only kernel/initramfs tests work today, boot and system tests (modem, Wi-Fi, audio, sleep - what we need) are not built; their farm is a CI-tron gateway with one OnePlus 6T, joining is token-gated and undocumented; Python is host-side only (pipeline generation, pmbootstrap) and costs nothing on the phone. Whether rhizcuts handle a GitLab subfolder is not known. Weighed: fully upstream (A), our runner with upstreamable shell files in their shape (B), a different shape (C). Chosen B. Not known yet: pmaports licence/CLA, fork-sync cost, bootrr contribution policy, rust-script cache path, inventory/linkme on aarch64 musl, the systemd claims (memory only).
- pmaports MR 4420: initial on-device CI support - A test package installing scripts into known directories plus an early-boot hook; seen only through search summaries (page behind a bot wall).
- postmarketOS hardware CI and on-device CI docs (nura.eco) - On-device tests are postmarketos-test subpackages run by an initramfs hook; only kernel tests work; farm is CI-tron with one OnePlus 6T.
- bootrr: sanity checks for boards on LAVA (linux-msm) - Board descriptions as data, generic helpers, board detection, an explicit skip: the shape our shell checks already have.
- LAVA test definitions - One line per test case with pass/fail/skip, a fatal abort; set aside the YAML wrapper and server.
- CI-tron components (freedesktop) - A stored record of what a device should look like, and qualifying by repeated boots.
- rust-script (fornwall) - Compiles on first run and caches the executable; needs a Rust toolchain on the machine that runs it.
- Alpine edge aarch64 package: rust - 71.7 MiB download, 205.5 MiB installed: the cost of a toolchain on a phone.
- cargo-nextest: how it works - List tests per binary, run each in its own process: a runner that depends on the tests, not the tests on it.
- Alpine wiki: abuild and package signing - An apk gives versions, dependencies, uninstall and signatures at the price of a key and a repository.
2026-11-17
Should linux-phone-oco's tools share one prefix (lpoco-bringup, lpoco-health; devlab, tone renamed or not), or none?
What is: lab-tools has devlab (host command, built from the clone, named in about 450 files of linux-phone-oco and in the MCP door's tool names), tone (a library crate and its command, not installed anywhere) and lpoco-health (a package shipped to phones, renamed from devlab-health when it became one, the old name kept as another name). Collisions checked 2026-11-17: crates.io already has a crate named tone (0.0.1); devlab, bringup and lpoco-bringup are not taken as crates, none is on the lab's PATH or in the Arch repositories. How others do it: git-* and cargo-* are discovered by the prefix itself (a subcommand is any git-NAME or cargo-NAME on PATH) and complete at the prompt; pmbootstrap and pmaports carry pm for postmarketOS across the whole family; systemd uses a suffix (*ctl) for the same purpose. In each, the prefix marks the tools others install, and it names whose they are. Finding: share the prefix where the tool is installed or pinned by others (lpoco-health, lpoco-bringup); keep the short names of the lab's own commands (devlab, tone) until they are installed elsewhere - renaming them now costs about 450 references, the installed path and the MCP tool names for no reader's gain, and the alias precedent (devlab-health kept as another name) makes the later rename cheap. A mixed family is acceptable when the rule is one sentence. Not known yet: when devlab is first pinned by a device repository (that triggers its rename).
- rhizoid: fork, own and sync git dependencies - git-rhizoid Cutting (a fork owned and pinned), tracking branch pristine, patch branch merged from it, additive-only metadata: the model for patching a tool before upstream takes the change. CLI boundary typed, add/update/status stubbed.
2026-11-17
How do device repositories use, extend, send back to and update from a tools home, side by side with no rebase, and where does rhizoid fit?
The question: a home for bring-up tools must also let device repositories use them, extend them with device-specific parts, send useful changes back and pull updates in, their own changes side by side with no rebase each time (the author's words, relayed by the coordinator; the problem git-rhizoid was started for). Extends research bringup-tools-landscape. What is: the chain already decided (idealkb decision 2026-11-17-chain-follow-by-slice, research chain-follow-world): one pin-and-follow mechanism for data and briefs - a source names its generic files, a follower pins a release and keeps its own files, a changed generic file ends follow.sh with exit 3 and goes back as an upstream item (ikb upstream-item, form patch), weekly update-pins and a release gate; device bases follow idealkb and device-template that way. It lays a slice of files. Rhizoid (git-rhizoid.github.io, rhizoid repo) is for whole forks: a cutting is a fork owned and pinned, tracking branch pristine, patch branch merged from it, rhizoid's own metadata additive-only, so a diff of patch against tracking is a clean patch back; its CLI is typed but add/update/status are stubbed, its consumption side is open (design-consumption-side) and slice-consumption was added 2026-11-17 by the idealkb chain. devlab and lpoco-health already reach consumers as released packages (release-plz tags, the packaging conveyor), not as copied files. Finding: a tool is not a slice. Compiled logic is followed by a version pin, not by files laid into the follower, so the rebase trouble does not arise for the tool at all as long as a device never edits the tool's tree: its own parts live in its own repository, beside the tool, in three levels. (1) Data: device.toml [boot] and the files it names (initramfs skeleton, dtb variants). (2) Hooks: executables the manifest names for a step (shell where stupid simple), called with the paths in arguments, a nonzero exit stops the job. (3) Logic: a rust-script file (or a small crate) in the device repository whose header depends on bringup's library at the pinned tag (rust-script and cargo take a git tag as a dependency). Only two things then need the follow machinery: the pin (a version line the follower owns) and the slice of files that go with the tool in device-template (the [boot] skeleton, hook examples). Sending back: a generic improvement is a pull request to lab-tools from the device's branch, recorded in the device base as an upstream item (form patch) against a lab-tools upstream row seeded beside idealkb and device-template; an update comes by a pin bump (the weekly job, a pull request per source). Side by side: the device's changes are files of its own, so a pin bump touches none of them; when a device must patch the tool itself before upstream takes it, that is a cutting of lab-tools consumed as a git dependency (Cargo [patch]) - rhizoid's exact case, rare because the three levels cover most. Where rhizoid carries it, and what it lacks (recorded on its own backlog, git-rhizoid.github.io PR 28, not worked around): a cutting consumed by a language manager - writing and bumping the pin where cargo or rust-script reads it (cutting-as-cargo-dependency); one pin file, one bump, one verdict for slices, cuttings and tool versions together (followers-one-pin-bump); sending a patch back as a pull request on the person's word with the follower's own record of it (send-back-writes-the-upstream-item); and slice-consumption (already open) for the template files. Until rhizoid has them: idealkb's follow.sh and update-pins for the slices, a plain fork with a [patch] line for the rare cutting, recorded as a problem. Not known yet: whether bringup's library API can stay stable enough for the third level while it is 0.x (the first builder's test of pin refusal tells); whether a host binary release (asset) or cargo install --git is the simpler install for a device lab (bringup-release settles it).
- rhizoid: fork, own and sync git dependencies - git-rhizoid Cutting (a fork owned and pinned), tracking branch pristine, patch branch merged from it, additive-only metadata: the model for patching a tool before upstream takes the change. CLI boundary typed, add/update/status stubbed.
- git-rhizoid.github.io: design log and backlog of rhizoid (tad-kept) - git-rhizoid Concepts (additive file structure, tracking vs patch branch, clean patch back) and open items: design-consumption-side, slice-consumption (2026-11-17) and the three items this research added.
- ideal-knowledge-base: decision 2026-11-17-chain-follow-by-slice, research chain-follow-world, bin/follow.sh - grenudi One pin-and-follow mechanism: a source names its generic files, a follower pins a release and keeps its own files, a changed generic file exits 3 and goes back as an upstream item; rhizoid is left for whole forks, and its missing slice mode is on rhizoid's backlog.
- rust-script: dependencies in a script's cargo header, run single-file Rust - fornwall A device-specific step can be one file that names bringup as a pinned dependency (git tag) in its own header: logic beside the device, no edit of the tool.
- Cargo: dependencies from git, and overriding dependencies with [patch] - Rust A git dependency pinned by tag or rev is the pin; [patch] is how a patched fork stands in for the source until upstream takes the change, side by side with no vendored copy.
2026-11-17
Does abootimg-oxide write header v0 byte-exact, or must pack wrap mkbootimg?
Measured 2026-11-17 with a scratch program against mkbootimg (android-tools, header v0, base 0, kernel 0x8000, ramdisk 0x1000000, tags 0x100, page 4096): the crate's header write gave bytes identical to mkbootimg for the whole length it wrote. Two gaps, both ours to fill: (1) full_write only seeks to boot_image_size, so the image ends before the last page's padding (15288 of 16384 bytes) - pack pads itself; (2) the header id: mkbootimg's v0 id is SHA-1 over kernel, ramdisk and second, each followed by its u32 size (three parts), while the crate's compute_hash_digest hashes five (adds recovery dtbo and dtb) - so for v0 the id is computed in our code. With both, pack equals mkbootimg for the plain header and with os_version/os_patch_level words (tests/pack_v0.rs, two cases). mkbootimg writes second address 0 when there is no second image, whatever second_offset says. Header::parse reads v0..v2 and v3/v4; this tool reads v0 only for now. Cost: binrw and thiserror come with the crate. Not known yet: v1/v2 write parity, vendor_boot.
2026-11-17
Should all lpoco tools sit under one command, one pin and one release (the author: one roof), and in what form?
Asked by the author after the prefix amendment: the point was to gather all tools of lpoco under one roof. Forms: (a) one lpoco command with subcommands, as git and cargo do - a dispatcher that runs lpoco-NAME found beside it or on PATH; (b) every tool renamed lpoco-* now, released together; (c) the prefix rule with devlab and tone deferred (the first amendment). What a roof buys: one install, one pin in device.toml [tools], one completion and man page, one MCP server, one place agents look. What it costs: ~450 references to devlab and the MCP tool names, softened by keeping the old names as other names (the lpoco-health precedent). Constraint: lpoco-health ships to phones as a small static binary (opt-level s, no tokio, no rmcp), so a single fat binary would grow the phone's program; a dispatcher keeps every tool its own crate and binary, testable and runnable alone. Finding: (a) as a dispatcher over lpoco-* programs, family released together with a version lockstep check, the new tool born as lpoco-bringup under it; devlab becomes lpoco lab (devlab kept as another name), tone lpoco tone, the MCP door becomes lpoco mcp. Not known yet: whether release-plz makes one family tag easily (the builder of lpoco-dispatcher settles it); whether a feature-gated single binary would later be simpler.
- rhizoid: fork, own and sync git dependencies - git-rhizoid Cutting (a fork owned and pinned), tracking branch pristine, patch branch merged from it, additive-only metadata: the model for patching a tool before upstream takes the change. CLI boundary typed, add/update/status stubbed.
2026-11-17
What exists to build, unpack, swap and check Android boot images and initramfs for a phone bring-up, and what does walleye's shell do today?
What is: walleye's bring-up is 8 POSIX shell scripts (~520 lines) in google-walleye-lab/build plus tests/host/gadget-up.sh; they call mkbootimg, unpack_bootimg and avbtool (Python from android-tools), the kernel's gen_init_cpio, lz4, fdtget/fdtdump, with their own checks (check-bootimg, check-bisect count fields and fail). Their knowledge is worth keeping: header v0 offsets by variant, the appended dtb, the lz4 frame shape of the stock kernel, the AVB hash footer (algorithm NONE, padded to the control's size), the NET=43 address rewrite, xz because the 4.4 kernel has no gzip. surya's bring-up had no scripts (by hand). Earlier records already decided the family: backlog rust-toolset (one Rust toolset in lab-tools, rust-script for small scripts, pmbootstrap read as reference) and decision 2026-11-17-health-checks-shell-and-rust (shell for plain readings, Rust for logic, rust-script for prototypes and one-offs). Others: nothing covers the whole job. Android's mkbootimg/unpack_bootimg/repack_bootimg and avbtool (Python) are the authoritative oracles; magiskboot (Rust+C++, GPL) has the model of swapping one part (unpack to a directory, change, repack with the original as template) but is aimed at rooting; abootimg-oxide 0.5.2 (Rust, MIT/Apache, 2026-06) reads and writes header v0-v4 and vendor_boot; abootcrafter has an update flow, no AVB; abl-exorcist (Rust, GPL) shells out to mkbootimg; no AVB crate exists on crates.io (avbroot, GPL, does vbmeta, is no library). Rust crates for the rest: cpio 0.4.2 (newc writer), flate2, lz4_flex (maintained), dtoolkit 0.5.0 (Google, dtb read/edit, young), fdt (read). pmbootstrap is Python, ~24k lines in 129 files; its deviceinfo names (header_version, base, kernel_offset, ramdisk_offset, tags_offset, pagesize, cmdline) are the vocabulary to reuse; the boot image is not built there. Mobian, Droidian (initramfs-tools-halium: shell hooks for an initramfs only), lk2nd (a bootloader, no host tooling): nothing to take. No tool checks an image against expected header fields; unpack_bootimg plus a comparison is all there is, which is what our check scripts do. Not known yet: whether abootimg-oxide writes byte-identical v0 images; dtoolkit's maturity; whether cpio 0.4.2 reads; whether boot-deploy, Mobian and Halium scripts add anything (not read; the outside look was done by a read-only researcher from page summaries, so counts are weaker than a source read). Where tools live today: lab-tools (its README: tools for bringing up and testing Linux phones, not tied to one device) is the one place already: devlab (the phone: fastboot, flash, kernel try, provision, keeper, health, MCP; 5.4k lines with rmcp and tokio), health (runs on the phone) and tone. Device repos hold data and thin scripts.
- AOSP system/tools/mkbootimg (mkbootimg, unpack_bootimg, repack_bootimg; rust/bootimg.rs header layout) - Google The reference for header v0-v4 and vendor_boot: the oracle our Rust packer is tested against byte for byte; its unpack prints the fields we compare.
- AOSP avbtool (external/avb) - Google info_image and add_hash_footer: wrapped as a tool on PATH for the footer; no AVB crate exists on crates.io.
- Magisk magiskboot (native/src/boot, Rust and C++, GPL-3.0) and its tools.md - research-bringup-tools The model for swap one part: unpack to a directory, change a part, repack with the original image as the template. Not a dependency: GPL, cxx-bound, aimed at rooting.
- abootimg-oxide 0.5.2: Android boot image parser (Rust, binrw) - research-bringup-tools Header v0-v4 and vendor_boot read and write, MIT OR Apache-2.0, released 2026-06; the Rust header layer to wrap, if its v0 write is byte-exact (unknown, the first test settles it).
- Rust crates for the rest: cpio, cpio-archive, flate2, lz4_flex, dtoolkit, fdt - research-bringup-tools cpio 0.4.2 (newc writer, MIT), flate2 and lz4_flex (maintained), dtoolkit 0.5.0 (Google, dtb read/edit, young), fdt (read). Nothing covers AVB; wrap avbtool.
- pmbootstrap pmb/parse/deviceinfo.py and bootimg.py (Python, ~24k lines in all) - postmarketOS Only the vocabulary: deviceinfo's header_version, base, kernel_offset, ramdisk_offset, tags_offset, pagesize, cmdline names for our device.toml [boot]. The build step is not in pmbootstrap; the rest is Python and shell sprawl we leave.
- abl-exorcist (Rust, GPL-3.0): wrap a mainline kernel for Pixel ABL, then call mkbootimg - research-bringup-tools A Rust tool that shells out to mkbootimg and does the one thing a Pixel bootloader needs; evidence that wrapping mkbootimg is what Rust tools do, and a lead for the Pixel 2 Load Error.
- abootcrafter 1.1.0 (Rust boot image tool) - research-bringup-tools Its update flow (replace kernel/ramdisk of an existing image) is our swap; no AVB, no vendor_boot, ramdisk repack unfinished: idea only.
2026-11-17
What already exists for measuring a phone's health on the phone, shipping it there, and letting agents work with it - in postmarketOS and in our own commons?
postmarketOS (docs.postmarketos.org/pmaports/main/ci/hardware-ci.html): tests ship as small shell files in postmarketos-test-* packages (suspend by an RTC wake alarm; bootrr, which checks per board, keyed by the device tree's compatible, that every expected driver probed) and run in the initramfs CI hook on their hardware CI (CI-tron gateway); surya has no bootrr board file yet. In the commons: the package conveyor (linux-package-distribution-oco/conveyor) already builds static aarch64-musl binaries with signed provenance and plans signed Alpine repositories for postmarketOS (cv-apk) and machines that receive updates, the phone next (cv-machines-refresh); agent access (creation-guidelines/agent-access-oco) plans every tool's structured door offered over MCP, in Rust with rmcp, naming devlab among the first (aa-two-doors). In lab-tools itself: devlab test ran surya's checks from the lab over SSH, health kept a baseline of what ever passed, watch ran health after each boot from the lab - nothing ran on the phone by itself, and the checks were one surya-specific file.
2026-11-17
How does the lab host get prepared for the devices it serves, from each device repository's device.toml, by a tool under the lpoco roof, with no manual step outside a tool - and how do others do it?
INSIDE. Nothing prepares the lab host from declarations today; each part got there by hand or by a one-machine script. Measured read-only on the lab (grig, systemd 262): the lab user (uid 1000) is in neither disk (/dev/sdX) nor uucp (/dev/ttyACM* on Arch), so walleye's gadget nodes were unreadable after the reboot; uaccess would reach that uid while it holds the active seat0 session (it does: Plasma on tty2), but nothing tags our gadget. /etc/udev/rules.d/51-android.rules (MODE 0666 for vendors 18d1, 05c6, 2717; group plugdev, absent here) came from lab-agent's connect.sh, run by hand; android-udev and systemd 262's own hwdb tags already cover adb and fastboot, and none of it covers block or tty. usb_storage and cdc_acm could not load today until the host was rebooted into its installed kernel (the running kernel's modules were gone). The aarch64 musl Rust toolchain in ~/.local/share/devlab-cross (health/build.sh) is unrecorded hand work. devlab-watch@ units come from lab-machine setup/devlab-watch.sh, enabled by hand per device (surya yes, walleye no). The host's own tools are hand copies: ~/.local/bin/land (from grenudi/lab-machine bin/land), oco-work (its only tracked home is creation-guidelines/lab-agent oco-agent/tools/oco-work, a place that is retiring), devlab and its .before-* copies; agent-env is sourced from the ideal-agent clone or plugin; tad and ikb by their install scripts; nothing names their versions. Root is only `sudo -n lab-agent root-exec --` (devlab reads DEVLAB_ROOT); ideal-agent's 2026-11-17-lab-agent-retires-by-parts part 6 moves it to a lab-root wrapper in lab-machine or narrower per-command grants, written by the author and root. walleye's device.toml already declares [host] modules usb_storage, cdc_acm and [[host.gadget]] serial walleye-first-boot, access block and tty (lab PR 54); devlab ignores the table (no deny_unknown_fields at the top). Session logs show root-exec used by hand today for fastboot devices, pacman -S (git send-email's perl modules), the host reboot, and ssh to the phone. OUTSIDE. Nobody derives host rules from per-device declarations. LAVA declares per-device serials in data but ships one static rule calling a privileged helper; labgrid matches udev properties at run time and leaves rules to the administrator; pmbootstrap writes no rules and runs flashers as root in its chroot (whole-command doas/sudo/run0, no dry plan, a teardown verb); android-udev-rules grants MODE 0660, GROUP adbusers and TAG uaccess in one line at 51; NixOS merges rule files from many modules by name and puts extraRules at 99, too late for uaccess; Ansible's check mode is the dry plan with a diff. systemd (source and NEWS): uaccess grants only the seat's active session, so ssh-only users and services get nothing; a rule setting it must sort before 73 and must not be add-only since 258; 258+ tags ADB and fastboot by itself; 260 adds xaccess-debug-appliance for headless sessions asking through PAM; only GROUP/MODE covers services. `udevadm trigger --action=change` re-applies GROUP, MODE and uaccess to present nodes, no replug. TAKEN. A rule file per device below 73, ACTION!="remove", matching the gadget serial on the parent (ATTRS{serial}), TAG+="uaccess"; a lab group with MODE 0660 later for a headless host; nothing by vendor for adb/fastboot (systemd covers it, a check proves it); a plan that is a content diff per file plus the exact root commands, the verb writing, reloading and triggering change only where it touched; modules-load.d only for declared modules, with "the running kernel has no modules: reboot" said by the plan; root by one prefix and a printed fixed list of commands, the list a narrow grant is written from.
- android-udev-rules: 51-android.rules, sysusers.d adbusers, install.sh - M0Rf30, 2026 group plus uaccess on one grant; sysusers.d for the group; its add-only guard and replug are what not to copy
- systemd: udev-builtin-uaccess.c, 70-uaccess/71-seat/73-seat-late rules, hwdb 60-usb-interface, NEWS 258 and 260 - systemd, 2026 uaccess reaches only the seat's active session; rules setting it sort before 73 and are not add-only; 258+ tags ADB and fastboot; 260 adds xaccess-debug-appliance
- pmbootstrap: pmb/config/sudo.py, helpers/run.py, chroot/binfmt.py, chroot/shutdown.py - postmarketOS, 2026 root by doas/sudo/run0 with an override; check-then-act; a teardown verb; no udev rules, no dry plan
- LAVA: lava_dispatcher_host udev.py and device dictionaries (device_info board_id) - Linaro, 2026 per-device USB serials declared in data; one static rule and a privileged helper; rules install writes only when content differs
- labgrid: udev matching in exporter configuration, exporter unit, raw-interface helper - labgrid-project, 2026 match by ID_SERIAL_SHORT; group access for a headless service; narrow root by sudoers lines for fixed helpers
- nixpkgs: nixos/modules/services/hardware/udev.nix, boot/kernel.nix, rename.nix (programs.adb removed) - NixOS, 2026 rules from many sources merged by file name; extraRules at 99 is too late for uaccess; modules merged into modules-load.d
- Ansible check mode and community.general.modprobe - Ansible, 2026 a dry run that changes nothing and reports per resource, with a diff
- google-walleye-lab device.toml [host]: modules and gadget serial walleye-first-boot with access block and tty (lab PR 54) - linux-phone-oco, 2026 the first device declaration the tool reads; its shape kept and settled
- ideal-agent decision 2026-11-17-lab-agent-retires-by-parts, part 6 (root-exec), backlog lab-agent-6-root-exec-grant - grenudi, 2026 root moves to a lab-root wrapper or a narrower grant per command, written by the author and root; the tool must print the exact root commands it runs
2026-11-17
Where does preparing the lab host stand, and what is next?
How it stands, 2026-11-17 night. Decided, not built: lpoco-host (`lpoco host plan | prepare now | check`), a new crate in lab-tools under the lpoco roof (decision 2026-11-17-lpoco-host, research lab-host-prepare-landscape). Next for the lab-tools builder: backlog lpoco-host, rank 1, needs build, device google-walleye - its first test host/tests/plan.rs plan_grants_gadget_serial_and_changes_nothing does not exist yet and must fail first, then plan_lists_host_tools_at_pins_and_installs_nothing; acceptance is the tool's first real use on the lab: prepare now grants walleye-first-boot, the walleye keeper reads /dev/sda and /dev/ttyACM0 as the lab user. The walleye lane waits on it (its base: walleye-host-access-via-lab-prepare and the two retry items). Declared already: walleye device.toml [host] (lab PR 54). Not yet: a lab.toml in grenudi/lab-machine (the builder proposes it there with the tools at today's versions); a living home for oco-work (today only in the retiring creation-guidelines/lab-agent); the narrow root grant (ideal-agent lab-agent-6-root-exec-grant, the author's) - meanwhile root goes through LPOCO_ROOT/DEVLAB_ROOT/root-exec. The host on 2026-11-17: systemd 262, lab user on seat0, no rule for our gadget, 51-android.rules a hand leftover, usb_storage loaded, cross toolchain in ~/.local/share/devlab-cross by hand, devlab-watch@surya-lab only, land and oco-work hand copies. Later: lpoco-host-rest (headless group, watchers, cross targets, host commands, foreign rules named, NCM).
- google-walleye-lab device.toml [host]: modules and gadget serial walleye-first-boot with access block and tty (lab PR 54) - linux-phone-oco, 2026 the first device declaration the tool reads; its shape kept and settled
- ideal-agent decision 2026-11-17-lab-agent-retires-by-parts, part 6 (root-exec), backlog lab-agent-6-root-exec-grant - grenudi, 2026 root moves to a lab-root wrapper or a narrower grant per command, written by the author and root; the tool must print the exact root commands it runs
2026-11-17
What must a phone have, structurally, to be a daily driver - judged from everything the open and proprietary platforms already built, learned and failed at?
Nine structural concepts, from ten projects, two operating systems and one firmware: Two Minds (a small always-on processor beside the main one, proven by Crust), Radio Wall, Notification Sovereignty, Consolidation Path, Platform Compatibility, Security Substrate, Update Covenant, Power Covenant, and the Observatory that maps every project against them. The open ecosystem's hard gaps are standby with push, a hardware security processor and long-term updates; Android and iOS solved them in closed ways. The model, its map and the prior-art files for Android/AOSP, iOS and GrapheneOS are the material; it is the why layer of the grand picture. (Moved into the dated layout on 2026-11-17.)
2026-11-10
Другие источники
- Qualcomm AOSS QMP driver v7 (Bjorn Andersson) - surya-research, 2019 qmp_send acks only when the AOP clears the length word after a kick; the timeout path is the one surya hits
- armada-os/armada#274: s2idle never enters AOSD/CXSD on Odin 2 (SM8550), measured - surya-research, 2026 Same symptom on a sibling SoC found by reading: an SD-controller IRQ storm (30/s) during suspend woke CPU0 for the whole cycle, the USB PHY kept a CX vote, CPU0 deep idle disabled; counters read 0 after a suspend that reported success
- Enabling serial port (console UART) on Pixel 2 and other Pixels - ikb-cli, 2020 Pixel 2 UART on USB-C SBU1/SBU2 at 1.8 V, 115200 8N1, fastboot oem uart enable; the stock cable lacks the lines; orientation differs between Pixels
- drivers/cpuidle/cpuidle-psci.c and cpuidle-psci-domain.c: the s2idle path into the cluster domain - surya-research s2idle enters through dev_pm_genpd_suspend, not runtime PM; the CPU domains get pm_domain_cpu_gov only when they have idle states
- drivers/usb/dwc3/dwc3-qcom.c (interconnect enable/disable around suspend) - surya-research USB_MEMORY_AVG_HS_BW is 240 MB/s - the 240000 in surya's icc read; dwc3_qcom_suspend sets the path to 0, so USB's tag-7 vote is gone before the last CPU flushes the sleep set
- firmware-xiaomi-surya (sensors configs and pre-parsed registry) - sm7150-mainline, 2024 Ships 46 sensor configs and a pre-parsed registry of 193 files (stk3a5x light and proximity included) whose sns_reg_config records every config with data 1230768000, Android's fixed vendor mtime; no sns_reg_version.
- Pixel 4 downstream sm6150-pm.dtsi, lpm-levels, system_pm (GPL, read for observed behaviour) -
- OnePlus 6 qcom_stats counts, aosd 0 cxsd 0 (stats node patch thread) -
- RFC on s2idle behaving like s2ram on pre-Hamoa SoCs, reply by Bjorn -
- pocknix-os PR 161: Retroid Pocket 5 s2idle aosd/cxsd stay 0 -
- Sleep stats driver v12 thread (all subsystems must power down) -
- Split up TF-A related PSCI configuration for sc7180 (counts ddr, cxsd, aosd) -
- archiso-aarch64-sp11 issue 38: s2idle reaches CXSD/DDR/AOSD after removing votes -
- drivers/pmdomain/core.c: genpd_sync_power_off and the s2idle usage counter - surya-research usage_s2idle increments only when a power-down governor ran in genpd_sync_power_off, and that path needs suspended_count == device_count and sd_count == 0
- usb-cereal - ikb-cli SBU1 = TX, SBU2 = RX, DIP 1.8/3.3 V (a wrong setting can damage the target), orientation-specific, archived 2023-01-10, not an official Google product
- hexagonrpc #19: sensor registry writes refused (Milos; SC8280XP, SM8650 and SG6275P reports) - linux-msm, 2026 The DSP writes the registry when sns_reg_version is missing; fwrite/fremove stop the crash; a writable state dir (-S) gave streaming sensors that survived a 15 s suspend on SG6275P (2026-11-06).
- hexagonrpc PR #27: write support for the sensor registry (closed unmerged) - linux-msm, 2026 fopen in write modes, fwrite, fsync, fremove, ftrunc, frename, methods above 30 by escape, large in-buffers; branch sp11-sensors 40e5041; withdrawn by its author.
- hexagonrpc #29: sns_registry_sensor.c assert takes the ADSP down (X1P42100) - linux-msm, 2026 The same assert as surya's, with hexagonrpcd 0.4.0 -s -R; a local ~700-line patch writing only under /persist/sensors/registry fixes it; on X1E #27 stopped the reboot but found no sensors.
- hexagonrpc source (rpcd_builder.c, apps_std.c, hexagonfs_mapped.c), v0.4.0 to v0.5.0 - linux-msm, 2026 Writes are refused by design (fopen w/a: AEE_EUNSUPPORTED); stat passes the file's real mtime to the DSP; persist/sensors/registry maps only its registry subdirectory, so sns_reg_version beside it is never served; v0.5.0 (2026-08-13) changes none of this; Alpine edge ships 0.4.0-r3.
- iio-sensor-proxy !409: ssc-accel and ssc-proximity udev tags - freedesktop, 2026 libssc support merged in 3.9 (!381); the accel and proximity tags still open upstream; surya's v26.06 carries them in its own rule.
- lab-agent: the pull-based agent that runs jobs on the real phone and reports back through git - , 2026
- libssc: Qualcomm Sensor Core sensors for Linux - libssc, 2026 accelerometer, gyroscope, light, proximity, magnetometer, compass; ssccli reads one; #70: the same SNS_REG_INIT assert on SM8250 from missing configs; #120 ADSP fatal SNS_SEE near screen lock.
- LineageOS device tree and vendor blobs for surya - Xiaomi, 2025 Sensors only through sensors.ssc; no ultrasound parts (no elliptic, mius or ro.vendor.audio.us), unlike sibling sweet; stk3a5x I2C instance 5 0x46 polled, ak0991x and adux1050 (SAR) on I2C 1, the motion chip on SPI 3; Android serves the registry as user system with persist writable, and resolves property= lines through an apps-side sns_registry get_property hexagonrpcd lacks.
- LKML: SSC-bound I2C driven from the application processor (X1E) - Linux kernel, 2026 Bit-banging an SSC QUP's pins from Linux works on X1E, but the DSP may drive the same bus; the DSP route is preferred for power.
- pmaports #4674: davinci sensors rarely work on v26.06 - postmarketOS, 2026 SM7150 sibling: sensors rarely work and iio-sensor-proxy spins at 100% CPU (libssc #130).
- pmaports#4846: motorola-dubai in idle consumes 17x more than a droidian device (SM7325 near-mainline) - surya-research, 2026 Closest peer: a Qualcomm phone on near-mainline, with standby current measured by current_now (mainline 150 mA then 60 mA / 0.2-0.3 W, Droidian downstream 9 mA), where regulator_summary and genpd idle_states are the tools, USB runtime PM and WLAN BB are CX holders, and removing all the known holders left the drain unchanged
- pmaports !5941: miatoll (SM7125, ADSP only) sensors - postmarketOS, 2024 An ADSP-only sibling with working proximity through hexagonrpcd, libssc and iio-sensor-proxy; its registry's sns_reg_config records 1720791834, a registry rebuilt on Linux.
- pmaports !8203: mount persist for hexagonrpcd (closed unmerged) - postmarketOS, 2026 Aimed at davinci's ADSP crash loop (#3871) by serving the real persist registry; closed the same day, reason not visible.
- device-xiaomi-{davinci,surya}: Move from testing to community -
- Qualcomm Linux Power guide: Debug high sleep current - Qualcomm Vendor's own order when aosd is zero: suspend with the display off and USB disconnected, then check the CPU suspend success count, then wake locks
- drivers/soc/qcom/qcom_stats.c (rpmh-stats layout: aosd, cxsd, ddr read by name from the AOSS message RAM) - surya-research stat names are read out of the RAM (type word at 0x48 + n*size), so a file named aosd/cxsd/ddr existing proves the layout; ddr_stats needs its magic key; subsystem entries come from SMEM
- [PATCH v4 0/3] Output debug information from RSC (Maulik Shah): cmd_db_read_name address-to-name lookup - surya-research, 2026 Names an RPMh address (0x30000 -> cx.lvl) so a dump of remaining votes can say who; not merged as read - a later tool, not a first step
- drivers/interconnect/qcom/bcm-voter.c (keepalive BCMs, sleep bucket) - surya-research keepalive forces x=y=1 (or enable_mask) only in the AMC and WAKE buckets; the SLEEP bucket is aggregated from consumers' tags alone
- drivers/interconnect/qcom/sm7150.c (bcm_sh0, qns_llcc) - surya-research SH0 is a keepalive BCM on qns_llcc, the same definition as sdm845, sm8150, sc7180
- sm7150-mainline's sm7150.dtsi (branch v7.2): CPU and cluster idle states, PSCI domains, apps_rsc on the cluster domain, rpmh-stats -
- linux-postmarketos-qcom-sm7150: the sm7150-mainline kernel fork and its changelog across releases - , 2026
- sm7150-mainline: the community org hosting the kernel fork, nightly builds, and firmware repos -
- Danila Tikhonov: the SM7150 upstreaming series (v1, 2025-04-22) -
- sm8150.dtsi in mainline: one cluster sleep state, PSCI parameter 0x4100c244 -
- lab-tools: the soc-sleeps check - the SoC's own sleep counters after every boot -
- sm7150-mainline/downstream-fdt: the device trees of the phones' own Android kernels (fdt-surya: lpm-levels, rpm-stats) -
- postmarketOS wiki, POCO X3 NFC: revision 56784 'SSC works' - postmarketOS community, 2024 The one report of surya sensors working on Linux: accel, magnet, light, proximity set Y on 2024-03-11 on mainline 6.7.4 (hexagonrpcd 0.3.x then); setup unwritten, never re-checked.
- Pixel KGDB over UART - ikb-cli USB-Cereal at 1.8 V and 115200 on a Pixel 8; an FT232R supports break (KGDB sysrq), a CP2102N edition did not
- The vendor-derived WCD937x driver (LineageOS sm6150 kernel) - LineageOS, from Qualcomm's GPL audio techpack Bring-up: supplies, a reset pulse, 5 ms for enumeration, then bind; the reset is touched only at bind and on DSP restart; nothing in headset detection touches reset, supplies or SoundWire. Insertion debounce 256 ms (mainline uses less).
- qcom-sm7150 (xiaomi-surya) unable to unlock sim: QMI protocol error (3) - root cause tqftpserv 1.1.1 (pmaports #4441) - , 2026 tqftpserv 1.1.1 never writes the modem's short state files, so the modem stays in shutting-down and the SIM reads as missing; fixed in tqftpserv 1.2 (9ef11c0). On surya the SIM works in slot 2.
- modem/tqftpserv: upgrade and add patches for rsize & seek option handling (pmaports !4747) - Luca Weiss A modem's file transfers with rsize and seek options need a tqftpserv that handles them; it made the modem work on two close Qualcomm phones (sm6350, qcm6490).
- Xiaomi POCO X3 NFC (xiaomi-surya) - device wiki page - postmarketOS community What the community reports working, part by part. The address is as the claims recorded it, to be confirmed as the current wiki.
- Programmable voice (a number that answers and plays a tone) - Twilio and others, 2010 A telephone number driven by a program can answer a test call and play a known tone - a fully automatic call check without a second phone.
- Xiaomi's GPL kernel for surya: the WCD937x node - Xiaomi (GPL release, surya-q-oss) Supplies: L10A rxtx and px and BOB mic bias always on, L15A buck only on demand; micbias 1-3 at 2.7 V; a plain 3.5 mm jack with both MBHC switches set (hphl-swh, gnd-swh), no USB-C audio switch.
- Xiaomi's GPL kernel for surya: the LPASS pin states - Xiaomi (GPL release, surya-q-oss) The SoundWire pins' functions (TX data1 gpio19 func3, data2 gpio20 func2, RX data gpio22/23 func2) - mainline's corrected table agrees; the WCD937x reset is gpio24, active state driven high, sleep state low.