Repository navigation
Conversation
Each cell was checked against its device's notes and plans, its device package, and the pull requests merged in the last two weeks. Only cells with a merged pull request or a notes entry behind the change move; the Pixel 7 Pro rows, rewritten today (#388, #398, #402), are untouched. Pixel 9a (tegu): - GPU: kernel #85 and #87 landed through kernel #96 (merged 11-01), so frequency scaling and the GPU thermal zone are no longer in review; the package sets the 890 MHz ceiling, and the 10-29 boot at a fixed 160 MHz stays the last record, so the cell says no scaling boot from the merged form is recorded yet. - GNSS: kernel #172 (the PERIC0 clock) is merged, kernel #185 (the GNSS link) is merged with its 11-02 first boot, #114 (Location on the 9a) is merged; CPIF stays kernel #187 in review. Still testing: the modem starts by hand. - Modem: the 11-02 evening record (#368) and TELEPHONY-PLAN (#360) say calls ran with speakerphone audio both ways through #367's route, from Phone and Messages (#371), with the modem started at boot by #372's opt-in unit; #364 is merged. Those PRs are in review or draft, so the cell stays WIP and says which part each one is. - Fingerprint: omamobile-fingerprint 0.1.14 (#358) starts the service by default on both phones (a vendor wants link; the chroot script has the 9a's guard), so "opt-in" no longer describes the package. The cell keeps the 10-29 evidence and says the default start has no 9a record yet. Pixel 8 Pro (husky): the display (gs-decon, HK3 at 120 Hz, brightness, device-husky 0.1.3, #228) and the GPU (Panthor, the clock to 890 MHz, device-husky 0.1.2, #221) were tested on the first phone on test kernels (kernel #160 and #157 in review), so both move from WIP/no to testing as the other husky cells are worded. The USB replug rescue (device-husky 0.1.4, #250) is noted, and kernel #163 is merged. Pixel 7 (panther): kernel #177 (the panel and DCS brightness) and kernel #171 and #170 (the fuel gauge) are merged, not in review; the flip-only KMS path is kernel #181 in review. Pixel 6 Pro (raven): the GPU DVFS series is in review as kernel #189 and the modem runtime as #389; the cells now point at them. Wanted: the 9a's board device tree is in the published kernel (kernel #81), so "isn't public yet" goes; the 6a row records the factory image's AVB facts from #350. A dated line after the introduction records the re-read. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
Owner
Author
|
Self-review notes before merging. The pass is careful, and the stale list is useful. Three cells need tightening against their records:
I'll also ask the husky owners for a NOTES entry for the display and GPU runs, and consider noting the 11-02 Wi-Fi re-attach failure in the 9a's Wi-Fi cell. This lands before the other open DEVICES PRs, which then resolve their row at merge. |
Owner
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An audit of
docs/DEVICES.mdagainst the repository's own records: each device'sNOTES.mdand plan status lines, itsomamobile-device-<codename>package, and the pull requests merged in the last two weeks in this repository and in linux-omarchy-mobile. A cell moves only where a merged pull request or the device's notes say so; "works" stays where the owner's report proved it on the phone, WIP/partial wording stays where the evidence is thin, and every cell keeps its plan link. The Pixel 7 Pro rows, rewritten today (#388, #398, #402), are untouched. No phone was touched.Changed cells
tegubranchChecked and left alone: Fold, 7a, 6, 4, 4 XL, OnePlus 13, Tablet, 8/8a, 10 and 11 rows, the 9a's Boot, Storage, Display, Touch, Buttons, USB, Wi-Fi, Bluetooth, Battery, Charging, Haptics, Torch, AoC, Speakers, Sensors, NFC, Cameras and Suspend cells (#347 already updated Suspend), the 7's Boot, Touch, USB and Suspend cells, and raven's Display (kernel #116 open). All local links and anchors resolve.
Stale on the evidence, but left for the maintainer or an open pull request:
tools/pr-check origin/mainandtests/allpass.🤖 Generated with Claude Code
https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d