Skip to content

omamobile-shell 0.2.63: the Pixel 8 Pro's panel in the board table - #251

Closed
Somnius wants to merge 1 commit into
derekross:mainfrom
Somnius:husky-device-name
Closed

Somnius wants to merge 1 commit into
derekross:mainfrom
Somnius:husky-device-name

Conversation

@Somnius

@Somnius Somnius commented Nov 1, 2026

Copy link
Copy Markdown
Contributor

What and why

My 8 Pro's home widget says "Pixel 7 Pro" and gs201. The package on my phone is omamobile-shell 0.2.45, the published development channel still has nothing newer, and 0.2.50 (W4HO's #115, which Derek put on main) already reads the model, maker, codename and SoC from the device tree, so on husky it gives Pixel 8 Pro, Google, husky and zuma. The one thing it can't know is the panel, because BOARDS only has cheetah and tegu, so android.system.display is null on husky. This adds husky's row: 1344x2992, 120 Hz, 489 ppi (the DT's 70 x 155 mm gives 488 to 490 ppi, 120 Hz is the panel's top rate, the same thing the other rows mean). One test line for boardFrom on husky's model and compatible.

Device and build

Checks (no phone needed)

  • tools/pr-check origin/main passes
  • tests/all passes
  • tests/packages: omamobile-shell's own tests pass except the call-watch one, which imports dbus, and omamobile-mmd and omamobile-sensors fail the same way on my desktop (no python dbus and gi here), none of them touched by this change
  • Each changed package has its version bumped, and the new version is in the commit subject
  • Commits have area prefixes and bodies that say why; any AI help is a Co-Authored-By: or Assisted-by: trailer, never a Signed-off-by:

On the phone

  • I ran this on my own phone, booted into this build
  • Runbook steps passed: n/a
  • What I did not test: the widget on the phone. The phone runs the published 0.2.45, so the new code isn't on it; I tested boardFrom on husky's model and compatible in the unit test only.
  • Nothing in this change writes outside slot B and userdata, weakens the storage guard, or reads registers from userspace (AGENTS.md §1)

tools/phone-smoke: not pasted, it would be a report of the battery kernel on my phone and says nothing about this change.

The board code already reads the model, maker, codename and SoC from the
device tree, so husky shows as "Pixel 8 Pro" on zuma. Only the panel's size,
density and top refresh rate come from the BOARDS table, which had cheetah and
tegu but not husky, so android.system.display was null there. Add husky:
1344x2992, 120 Hz, 489 ppi (the DT's 70 x 155 mm gives 488 to 490).

Test: boardFrom on husky's model and compatible.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@derekross

Copy link
Copy Markdown
Owner

Thanks, Lef. That's a tidy fix. I checked the numbers: 1344x2992 at 120 Hz is right for the HK3, and the 70 x 155 mm in the panel driver comes out at about 490 ppi, so 489 is fine. boardFrom keys on the compatible's codename, and google,zuma-husky is what our board file has, so the new row is picked up. The test line covers it, and both CI jobs pass.

The only problem is the version. omamobile-shell 0.2.63 is taken by my voice-bar release (#253), and #217 has 0.2.64. Git won't even flag the clash with #253, because both branches set the version file to the same text, so it would quietly ship two different packages as 0.2.63. You don't need to do anything: since you've allowed maintainer edits, I'll set the next free version when I merge (0.2.65 if those two land first), in the version file, the title and the squash subject.

On testing: a unit test is enough for a table row like this. Once a published shell with it reaches the development channel, a screenshot of the home widget on your 8 Pro would be a nice confirmation, but I won't hold the merge for it.

@derekross derekross closed this in 1bbd420 Nov 1, 2026
derekross added a commit that referenced this pull request Nov 1, 2026
0.2.64 went to the Pixel 8 Pro's panel row (#251).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…erekross#251)

The Pixel 8 Pro's HK3 panel (1344x2992, 120 Hz, about 490 ppi) in the shell's board table, keyed on google,zuma-husky, with a test (Somnius). Renumbered to 0.2.64 at merge; 0.2.63 went to the voice release.

Closes derekross#251

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants