Skip to content

device-panther: the radio partitions for tools/nv-backup, and the second unit's notes - #418

Merged
derekross merged 4 commits into
derekross:mainfrom
angelrenefm:pr-panther-nv-parts
Nov 5, 2026
Merged

derekross merged 4 commits into
derekross:mainfrom
angelrenefm:pr-panther-nv-parts

Conversation

@angelrenefm

Copy link
Copy Markdown
Contributor

Two commits for the Pixel 7, as asked on #342.

1. NV_PARTS for panther. The same list as cheetah (efs efs_backup modem_userdata persist modem_a modem_b, with devinfo as NV_BACKUP_EXTRA), in both copies of the descriptor (device/panther/device.conf and the package's), which the package test compares. On a second Pixel 7 each partition is found once by PARTNAME; tools/nv-backup -d panther took a read-only backup and --check read all seven as SAME. Before, --list stopped with "names no NV_PARTS".

2. device/panther/NOTES.md: the second unit's devinfo version (3.15) with its slot bytes next to getvar, the Lishen battery pack and why it must not run flat yet, the stock PANTHER MP overlay against CHEETAH MP (MAX77759, Wi-Fi and Bluetooth lines, charger tables), the backup and the haptics.

The package version is left as it is, for you to set when merging.

Checks: packages/omamobile-device-panther/test/all passes; tools/pr-check origin/main passes.

Not checked: a tools/nv-backup after a stock boot (Android hasn't completed a boot on slot A since the install; the backup was taken before any radio or PMIC work, and a new one will follow the next stock boot).

I used AI help (Claude) to work on this.

angelrenefm and others added 4 commits November 3, 2026 23:42
The Pixel 7 has the 7 Pro's seven partitions, each found once by
PARTNAME. A read-only backup with this list, and --check against the
phone, both passed on a second Pixel 7.

I used AI help (Claude) to work on this.
A second Pixel 7 (derekross#342) differs from the first in two ways that matter
later: its devinfo is version 3.15, not 3.19, and its battery is the
Lishen 3 kOhm pack, which the current board file's Coslight model would
be written onto after a gauge reset. Its stock PANTHER MP overlay has the
Pixel 7 Pro's MAX77759, Wi-Fi and Bluetooth lines and the same charger
tables. All read-only; values as read on 2026-11-03.

I used AI help (Claude) to work on this.
@derekross

Copy link
Copy Markdown
Owner

Thank you, @angelrenefm. Both commits are what we discussed on #342. NV_PARTS is in both copies of the descriptor, and I ran tests/nv-backup and panther's package test on your branch: both pass, and tools/nv-backup -d panther --list shows the six partitions plus devinfo. Only the laptop tool reads that list, so nothing changes on the phone. The notes are useful as well: the devinfo bytes next to getvar (exactly the comparison we needed), the Lishen pack with a clear "keep it from running flat", and the stock overlay comparison.

CI is waiting for my approval because this is your first pull request here, so I ran the checks it would run myself. All pass.

A few things I'll do when I merge, so nothing is needed from you:

One optional suggestion: Google publishes the Pixel 7's device tree (kernel/devices/google/pantah, branch android-gs-pantah-6.1-android16). Its gs201-panther-common.dtsi includes the same gs201-cloudripper-wlan.dtsi and gs201-cloudripper-bluetooth.dtsi as the Pixel 7 Pro's, and no panther file overrides those pins. That confirms your dtbo comparison from a source anyone can read, so it would make a good citation next to it whenever you next touch these notes.

Thanks for the careful work on the second unit.

@derekross
derekross merged commit 0e5fd9e into derekross:main Nov 5, 2026
2 checks passed
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…kup, and the second unit's notes (derekross#418)

The Pixel 7 has the 7 Pro's radio partitions, each found once by
PARTNAME: NV_PARTS and NV_BACKUP_EXTRA (devinfo) in both copies of
panther's descriptor, so tools/nv-backup and --check work on it; both
passed on a second Pixel 7. NOTES records that unit's devinfo (version
3.15, not 3.19), its Lishen 3 kOhm battery pack (the board file's
Coslight model would be written onto it after a gauge reset, so it must
not run flat until the model is chosen by pack ID), and its stock
overlay's MAX77759, Wi-Fi and Bluetooth lines, all read-only.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants