Skip to content

device/husky: display, GPU, DVFS and Wi-Fi are merged; a boot of merged omamobile - #741

Merged
derekross merged 1 commit into
derekross:mainfrom
greenbrettmichael:husky-docs-merged-20261113
Nov 15, 2026
Merged

derekross merged 1 commit into
derekross:mainfrom
greenbrettmichael:husky-docs-merged-20261113

Conversation

@greenbrettmichael

Copy link
Copy Markdown
Contributor

Kernel #160 (display) merged on 2026-11-10, #157/#158 (GPU, CPU DVFS, thermal zones) on 2026-11-13, and Wi-Fi landed through #187 on 2026-11-09, but the 8 Pro's docs/DEVICES.md row and device/husky/ROADMAP.md still listed them as open test-tree PRs.

  • device/husky/NOTES.md: a new 2026-11-13 entry for a boot of merged omamobile (82f31d3a7, 7.3.0-rc6-omamobile-push1-g82f31d3a7a35) on my phone, with the kernel as the only change. It covers the three cpufreq-dt policies at the battery limiter's caps with the energy model, the four TMU zones, panthor, gs-decon with the HK3 and a clean tools/phone-smoke. 120 Hz isn't re-measured: it says so and links the t1 measurement on kernel docs/review: lessons from review round 29 #160.

  • docs/DEVICES.md, husky row:

    • Display: WIP → works;
    • GPU: testing → works;
    • Wi-Fi: testing → partial (no P2P, reloading after a firmware crash untested, as NOTES says).

    Each links its notes entry. Bluetooth, Battery and Haptics/Torch are also out of date (Pixel 11 Pro XL (kodiak) — stock facts #199, device-oriole: record native boot and RTC status finding #200 and device-cheetah 0.1.34: prefer Wi-Fi over the USB gateway #205 merged on 11-07), but those aren't my rows, so I left them.

  • device/husky/ROADMAP.md: the display, GPU, DVFS and Wi-Fi rows and bullets, the merge order and the credits line now say merged, and the next steps in those rows are what's left (the black blink at the handover, a GPU load with the zone watched, P2P and crash recovery, a skin temperature source and cpuidle). The header says only those rows were updated.

tools/pr-check passes. I grepped the diff for MAC-like strings, serials and SSIDs: none.

🤖 Generated with Claude Code

…ed omamobile

Kernel derekross#160 (display) merged on 2026-11-10 and derekross#157/derekross#158 (GPU, CPU DVFS,
thermal zones) on 2026-11-13; Wi-Fi landed through derekross#187 on 2026-11-09.
The 8 Pro's DEVICES row and roadmap still listed them as open test-tree
PRs.

NOTES records a boot of merged omamobile (82f31d3a7) on Brett's phone,
with the kernel as the only change: three cpufreq-dt policies at the
battery limiter's caps with the energy model, the four TMU zones, panthor,
gs-decon with the HK3, and a clean tools/phone-smoke. DEVICES moves the
husky display and GPU to "works" and Wi-Fi to "partial" (no P2P, crash
recovery untested), each linking that entry. The roadmap's display, GPU,
DVFS and Wi-Fi rows and bullets follow; the other rows are left to their
owners.

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

gitColinX commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

@Somnius, about the rows Brett left on #741 because they're yours (Bluetooth, Battery, Haptics/Torch): in case it helps, here's what my unit (G1MNW, Samsung 128 GB) shows on the published omamobile at 82f31d3a7 with omamobile-device-husky and the firmware from tools/extract-vendor-firmware (#722):

  • Bluetooth: the patch loads (BCM4398D0 G5SN_V17_HK3 REL BR:0169); a pair of AirPods Pro paired from the Settings page; a tone played over a2dp-sink was heard. With omamobile-device-husky 0.1.13: the Bluetooth controller gets the phone's address #752 the controller also takes the phone's own address, at every boot, and the AirPods paired and played again on it.
  • Haptics: cs40l26-vibra 1-0043: Firmware 0x1800d4 rev 7.2.91 running, the input device is there, and two 500 ms FF_RUMBLE effects were felt.
  • Battery: the gauge reads capacity, voltage, current and temperature, and the phone charges at about 0.9 A from a PC port with nothing loaded by hand.
  • Torch: white:torch is there and was driven to its maximum and back with no kernel message, but nobody looked at the LED at the time, so I don't count that as verified.

How would you like to handle those cells? Happy to leave them to you. Or, once #741 is in, I can send a PR with a NOTES entry for my unit and those cells (Bluetooth and Haptics to "works", Battery as you think right), with you and Brett tagged to review. I don't want to step on your rows.

@Somnius

Somnius commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

@gitColinX, thank you. A notes PR for your unit once this one is in sounds good to me, with @greenbrettmichael and me tagged. I don't mind you filling in those rows with what you tested on your unit, and the Torch cell as not verified, since nobody looked at the LED.

For Battery, put what you measured; I haven't looked at the charge rate on the published kernel, so I can't judge it better than you.

On mine, what I have checked so far on the published kernel (82f31d3a7): hci0 is there and the BCM .hcd file is in /usr/lib/firmware/updates/brcm, and the haptics driver loads its firmware (cs40l26.wmfw on DSP1) and the input device is there. I haven't paired anything, felt the haptics, checked charging or looked at the torch on that kernel yet, so your results are the better ones for those cells. If I get to them I'll add a line in your PR.

@derekross

Copy link
Copy Markdown
Owner

Thank you, Brett. This brings the 8 Pro's row and roadmap up to what has actually merged, and the NOTES entry is the kind of record I like: one change (the kernel), the release, how slot B was written and what the retry count did, and an honest "not re-measured here" for 120 Hz. I checked the merges it names: #160 and #158 merged, #157's commits landed through #158, and Wi-Fi came in through #187, with the BCM4398, GPU and DVFS nodes on omamobile and your tested 82f31d3a7 an ancestor of today's tag. The status words fit the legend, and the anchors resolve. CI is green.

I'll merge it. Two small things for a later pull request, none for this one:

One heads-up: #724 edits the Suspend row right above your Thermal row, so it will need a small rebase after this lands; keeping both rows as they are is the whole resolution.

@derekross
derekross merged commit 17c7dd1 into derekross:main Nov 15, 2026
2 checks passed
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.

4 participants