Skip to content

omamobile-shell 0.2.34: home widgets see the phone they run on - #115

Closed
W4HO-ham wants to merge 8 commits into
derekross:mainfrom
W4HO-ham:shell-device-info
Closed

W4HO-ham wants to merge 8 commits into
derekross:mainfrom
W4HO-ham:shell-device-info

Conversation

@W4HO-ham

Copy link
Copy Markdown
Contributor

Stacked on #99 (omamobile-shell 0.2.33); only the last commit is new.

The home screen's OWL host answered every device and system query with fixed values: a Pixel 7 Pro, SoC gs201, 1440x3120 at 512 dpi, codename cheetah. On the Pixel 9a, or any other port such as the OnePlus 13 in #111, a widget that shows the phone or sizes itself from the display got the wrong answer.

The model and the compatible list now come from the device tree (/proc/device-tree/model and compatible). The codename and SoC come from the first compatible (google,zumapro-tegu gives tegu and zumapro). A small table adds what the device tree doesn't say for the two Pixels we run on: the panel's size, refresh rate and density. Any other board reports its model, codename and SoC, with display: null rather than a guess.

Tests: test/owl-core.js covers the 9a, the 7 Pro, a non-Google board and an empty device tree, plus systemFrom with and without a board. test/all and tools/pr-check pass.

A poll loop is the NFC radio searching for cards. On the Pixel 9a it costs
about 60 mA with the screen off (252 mA against 315 mA, awake, 10-27),
and stock Android polls only while the screen is on. omamobile-nfc-open
now stops neard's poll loop once every display connector has been DPMS
off for 4 s, and starts it again when the screen lights, unless the NFC
switch is off. Tested on the 9a: no controller interrupts with the screen
off, polling again within 2 s of it lighting.
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

The red Tests run was the flaky audio watchdog test; it has nothing to do with this change. The fix is #107. I've put its three commits on this branch too, as on #100 and #101, so CI can pass.

mrlund added a commit to mrlund/omarchy-mobile that referenced this pull request Oct 28, 2026
Move the OnePlus 13 row into the main matrix (it had landed under the
cheetah detail table with a missing column) and replace blanket WIP
cells with legend words backed by NOTES evidence. Correct Adreno 830
(was A740), WCN7860 naming, USB replug and Bluetooth A2DP gaps, and
point Wanted plus README at derekross#111 / kernel derekross#115.

Signed-off-by: Martin Lund <mrlund@hotmail.com>
Assisted-by: Grok Bot
@derekross

Copy link
Copy Markdown
Owner

Thanks, @W4HO-ham. A widget on the 9a being told it runs on a Pixel 7 Pro was clearly wrong, and taking the model and compatible from the device tree, with a small table only for what the device tree can't say, is the right split. I checked the 7 Pro's device tree (Google Pixel 7 Pro, google,gs201-cheetah): device and system answer exactly as before there.

One question, not blocking: the 9a's entry says 120 Hz, but the published kernel only offers 60 Hz until the 120 Hz PR lands. If display.hz means what the panel can do, that's fine; if widgets read it as the current rate, it's wrong today.

This sits on #99, so it merges right after that one.

…ays dark

The stop was a single shot on the lit-to-dark transition, so anything that started polling afterwards kept it on until the next screen cycle: the unblock path's start_polling retries, the 9a's sleep hook after a wake, or neard restarted by systemd. Now every 2 s check stops any poll loop once the screen has been dark for 4 s, and start_polling powers the adapter but leaves the loop off while it's dark. The one-shot stop after an unblock is gone. test/nfc-screen.py checks screen_lit() against temporary sysfs trees.
The OWL host answered every device and system query as a Pixel 7 Pro (gs201, 1440x3120, codename cheetah), so a widget on the Pixel 9a or any other port showed the wrong phone. The model and the compatible list now come from the device tree; known boards add the panel's size, rate and density, and an unknown one reports its model and SoC with no display.
…atomically

The watchdog's jump test changes a control from a background job while the watchdog reads the fake mixer's state file, and CI once caught the read halfway through the write (JSONDecodeError, the test failed). Both fakes now write a temporary file and rename it over the state.
The flake had a second writer: JsonCtl, the json: control backend the tests run the speaker code against, rewrites the fake mixer's state on every heartbeat read, in place. The fake mixer reading at that moment saw an empty file. JsonCtl now writes a temporary file and renames it, as the fakes do. Nothing changes on the palmtop: JsonCtl is used only with OMAMOBILE_CTL_BACKEND=json:.
…s first reading

The jump tests changed the estimate 0.4 s after starting the watchdog. On a slow CI runner the watchdog wasn't reading yet, took the raised value as its baseline, saw no jump and didn't mute. The jump now waits for the watchdog's start line and a few intervals, and the watchdog runs 60 iterations.
…top rate

As asked on the pull request: display.hz is what the panel can do, not the rate it runs at now (the 9a's published kernel still runs it at 60 Hz).
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Thanks. display.hz is meant as what the panel can do, the same as width, height and dpi: fixed facts about the panel, not its current state. I've said so in the table's comment. A widget that wants the current rate should read the mode, and if one asks for it I'd add it as its own field rather than overload this one.

I've also rebased this onto #99's new head (the level-triggered screen-off stop).

derekross added a commit that referenced this pull request Oct 28, 2026
…ry work

Open PRs hold device-cheetah 0.1.35 (#102) and omamobile-shell 0.2.33
to 0.2.36 (#99, #115, #117, #124); this branch takes the next free ones.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Oct 28, 2026
0.2.33 to 0.2.37 are held by #99, #115, #117, #124 and the low-battery
branch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Oct 28, 2026
…ry work

Open PRs hold device-cheetah 0.1.35 (#102) and omamobile-shell 0.2.33
to 0.2.36 (#99, #115, #117, #124); this branch takes the next free ones.

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

Copy link
Copy Markdown
Owner

Thanks, @W4HO-ham. I've been through this once more. The table comment now says display.hz is what the panel can do, and that answers my question. I ran the old and the new phone.js on the Pixel 7 Pro's device tree strings (Google Pixel 7 Pro, google,gs201-cheetah), and device and system answer exactly as before, field for field. The package tests pass here, also with #117, #124 and my touch batch (#123) merged on top.

There's nothing more to change in this PR. It's waiting only on #99: the try/except around start_polling's Set, the line from the 9a I asked for there, and my own run on the 7 Pro.

One practical thing for when #99 lands. I squash-merge, so #99's commits won't reach main under their own ids, and this branch will then conflict on packages/omamobile-shell/version (0.2.33 on main, 0.2.34 here). A plain git rebase origin/main won't go cleanly either, because the three omamobile-audio commits from #107 are already on main as one squashed commit, so their intermediate steps no longer apply. The simplest fix is to put just your two commits on main:

git fetch origin
git checkout -B shell-device-info origin/main
git cherry-pick 891ecb977c e1f3e73175
git push --force-with-lease origin shell-device-info

I tried exactly that on main with #99 merged: both commits apply cleanly, and the result matches this branch's omamobile-shell tree. If it's easier, say so and I'll do it myself, since the branch allows edits from maintainers.

@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Thanks. #99 has the try/except and the 9a line now. Once it's squash-merged I'll put the two commits onto main with the cherry-picks you listed and force-push.

mrlund added a commit to mrlund/omarchy-mobile that referenced this pull request Oct 29, 2026
Status cells are testing (kernel in review, derekross#115). No Wanted-line or
README edit.
Signed-off-by: Martin Lund <mrlund@hotmail.com>
Assisted-by: Grok Bot
mrlund added a commit to mrlund/omarchy-mobile that referenced this pull request Oct 30, 2026
The ~07:46 gpu2 stage-2 smoke stays as recorded. A later tip boot of
the derekross#115 head hung on the console (dual memory map); re-smoke pending.

Signed-off-by: Martin Lund <mrlund@hotmail.com>
Assisted-by: Grok Bot
mrlund added a commit to mrlund/omarchy-mobile that referenced this pull request Oct 30, 2026
BRINGUP §6 now notes the derekross#115 tip re-smoke after the dual-memory fix
(booted; SSH ~26 s; storage/root/USB/Hyprland ok; module-backed drivers
skipped for the tip uname). NOTES states the shared init is still
untested on dodge. BRINGUP also says this PR has no in-tree day-2 path.

Assisted-by: Grok Bot
Signed-off-by: Martin Lund <mrlund@hotmail.com>
mrlund added a commit to mrlund/omarchy-mobile that referenced this pull request Oct 30, 2026
Status cells are testing (kernel in review, derekross#115). No Wanted-line or
README edit.
Signed-off-by: Martin Lund <mrlund@hotmail.com>
Assisted-by: Grok Bot
mrlund added a commit to mrlund/omarchy-mobile that referenced this pull request Oct 30, 2026
The ~07:46 gpu2 stage-2 smoke stays as recorded. A later tip boot of
the derekross#115 head hung on the console (dual memory map); re-smoke pending.

Signed-off-by: Martin Lund <mrlund@hotmail.com>
Assisted-by: Grok Bot
mrlund added a commit to mrlund/omarchy-mobile that referenced this pull request Oct 30, 2026
BRINGUP §6 now notes the derekross#115 tip re-smoke after the dual-memory fix
(booted; SSH ~26 s; storage/root/USB/Hyprland ok; module-backed drivers
skipped for the tip uname). NOTES states the shared init is still
untested on dodge. BRINGUP also says this PR has no in-tree day-2 path.

Assisted-by: Grok Bot
Signed-off-by: Martin Lund <mrlund@hotmail.com>
derekross added a commit that referenced this pull request Oct 30, 2026
The matrix and the Wanted list against what has merged since #140, with
each pull request's state checked on GitHub today:

- Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were
  closed because they landed unchanged through kernel #134, merged with
  the touchscreen node and s2idle by default; device-panther 0.1.1 (#145)
  carries the GPU's always-on rule, the feedbackd rule and the sleep.conf
  drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the
  2026-10-28 notes. Touch stays WIP: kernel #134's body records touches
  driving Hyprland and the PIN screen, but the driver fixes (kernel #133)
  and the kernel option with the touch notes (#149) are still in review.
  Suspend: "no" with the s2idle default named, since the notes say it
  hasn't run.
- Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5
  passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel
  #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names
  its open kernel PR, #116.
- Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133)
  records it scanning through its own UART; kernel #98 and #98 are in
  review. The Wanted line says so too.
- Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained
  vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes
  the merged tier 1 auto-sleep (#64, off by default behind the
  omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old
  "until S8" text. Nothing from the open #171, #172, #174-#176.
- Wanted: coral's #52 is merged, so its line no longer says "in review";
  flame gets a line for its native install in review (#55, #56, #58,
  #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and
  kernel #115, both open.

The Pixel 9a row and the Pixel 9 family line are left to #165. Every
status word still parses with the website's parseCell.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts:
#	packages/omamobile-shell/plugins/omamobile.home/owl/phone.js
#	packages/omamobile-shell/version
@W4HO-ham

Copy link
Copy Markdown
Contributor Author

Merged tonight's main, version to 0.2.49 (this PR sits on #99, which is now 0.2.48). One real conflict, in the home plugin's phone.js export list: your 0.2.45 added CLOCK, frameInterval, frameSlow, frameSkipped and tickDelay where this branch had added boardFrom, DEVICE_COMMAND and BOARDS, so the resolution keeps both lists. Nothing dropped. pr-check passes and all 238 package checks pass.

mrlund added a commit to mrlund/omarchy-mobile that referenced this pull request Oct 31, 2026
Status cells are testing (kernel in review, derekross#115). No Wanted-line or
README edit.
Signed-off-by: Martin Lund <mrlund@hotmail.com>
Assisted-by: Grok Bot
mrlund added a commit to mrlund/omarchy-mobile that referenced this pull request Oct 31, 2026
The ~07:46 gpu2 stage-2 smoke stays as recorded. A later tip boot of
the derekross#115 head hung on the console (dual memory map); re-smoke pending.

Signed-off-by: Martin Lund <mrlund@hotmail.com>
Assisted-by: Grok Bot
mrlund added a commit to mrlund/omarchy-mobile that referenced this pull request Oct 31, 2026
BRINGUP §6 now notes the derekross#115 tip re-smoke after the dual-memory fix
(booted; SSH ~26 s; storage/root/USB/Hyprland ok; module-backed drivers
skipped for the tip uname). NOTES states the shared init is still
untested on dodge. BRINGUP also says this PR has no in-tree day-2 path.

Assisted-by: Grok Bot
Signed-off-by: Martin Lund <mrlund@hotmail.com>
@derekross derekross closed this in 05e645e Oct 31, 2026
@derekross

Copy link
Copy Markdown
Owner

Thanks for keeping it current. The branch still carried an older #99 underneath, so I rebuilt it on main as one commit from your own three files (phone.js, OwlPhoneHost.qml, owl-core.js) at 0.2.50; package tests pass. It's on main authored by you (the PR shows as closed because the commit went in directly).

derekross added a commit that referenced this pull request Oct 31, 2026
… rounds

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

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross added a commit that referenced this pull request Nov 1, 2026
linux-omarchy-mobile #115 was closed on 2026-11-01: the sm8750 SoC series stays in the contributor's fork, so the dodge cells no longer say it's in review.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
derekross added a commit that referenced this pull request Nov 1, 2026
… 13 notes (#270)

#227 added CONFIG_PCIE_ZUMAPRO=m, a symbol no published or integration
kernel has (it belonged to kernel #168's driver, now superseded by #178's
shared zuma-family host), so merge_config dropped it silently; remove it.

#227 also made sec_acpm built in for the Pixel 9a's USB PHY. On the 7 Pro
that registers the S2MPG13's GNSS rails before the regulator core's 30 s
cleanup, and turns the G1 blacklist into a no-op. That is harmless (the
rails are GNSS-only), but AGENTS and GNSS-PLAN described load timing the
shared kernel can no longer give; they now say so.

device/dodge/NOTES.md still called kernel #115 "in review"; it is closed
and the kernel stays in the contributor's fork, as DEVICES says (#264).


Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
derekross pushed a commit that referenced this pull request Nov 2, 2026
Same pattern as Pixel 4 XL: the SoC stack stays in the contributor
fork, and the device docs link the exact tag
(mrlund/linux-omarchy-mobile dodge-v3-20261101). #115 stays as the
closed review history.

Assisted-by: Grok Bot

Signed-off-by: Martin Lund <mrlund@hotmail.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
The matrix and the Wanted list against what has merged since derekross#140, with
each pull request's state checked on GitHub today:

- Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were
  closed because they landed unchanged through kernel derekross#134, merged with
  the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145)
  carries the GPU's always-on rule, the feedbackd rule and the sleep.conf
  drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the
  2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches
  driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133)
  and the kernel option with the touch notes (derekross#149) are still in review.
  Suspend: "no" with the s2idle default named, since the notes say it
  hasn't run.
- Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5
  passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel
  derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names
  its open kernel PR, derekross#116.
- Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133)
  records it scanning through its own UART; kernel derekross#98 and derekross#98 are in
  review. The Wanted line says so too.
- Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained
  vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes
  the merged tier 1 auto-sleep (derekross#64, off by default behind the
  omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old
  "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176.
- Wanted: coral's derekross#52 is merged, so its line no longer says "in review";
  flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58,
  derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and
  kernel derekross#115, both open.

The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every
status word still parses with the website's parseCell.

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
…ross#115)

The home screen's OWL host answered every device and system query with
the Pixel 7 Pro's fixed values. The model and codename now come from the
device tree (model and the first compatible), with a small table for what
the device tree doesn't say about the two Pixels we run on (panel size,
top refresh rate, density); any other board reports display: null rather
than a guess. On the Pixel 7 Pro the answers are unchanged.

Rebuilt on main by the maintainer from the pull request's own three files,
since the branch carried an older derekross#99 underneath; renumbered to 0.2.50.

Closes derekross#115

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
… rounds

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

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
linux-omarchy-mobile derekross#115 was closed on 2026-11-01: the sm8750 SoC series stays in the contributor's fork, so the dodge cells no longer say it's in review.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…e OnePlus 13 notes (derekross#270)

derekross#227 added CONFIG_PCIE_ZUMAPRO=m, a symbol no published or integration
kernel has (it belonged to kernel derekross#168's driver, now superseded by derekross#178's
shared zuma-family host), so merge_config dropped it silently; remove it.

derekross#227 also made sec_acpm built in for the Pixel 9a's USB PHY. On the 7 Pro
that registers the S2MPG13's GNSS rails before the regulator core's 30 s
cleanup, and turns the G1 blacklist into a no-op. That is harmless (the
rails are GNSS-only), but AGENTS and GNSS-PLAN described load timing the
shared kernel can no longer give; they now say so.

device/dodge/NOTES.md still called kernel derekross#115 "in review"; it is closed
and the kernel stays in the contributor's fork, as DEVICES says (derekross#264).

Claude-Session: https://claude.ai/code/session_01BeEcdVeSfyLCbijF8XQF1d

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
…ross#328)

Same pattern as Pixel 4 XL: the SoC stack stays in the contributor
fork, and the device docs link the exact tag
(mrlund/linux-omarchy-mobile dodge-v3-20261101). derekross#115 stays as the
closed review history.

Assisted-by: Grok Bot

Signed-off-by: Martin Lund <mrlund@hotmail.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