Skip to content

extract-vendor-firmware: the Pixel 8 Pro's Bluetooth patch and haptics files - #722

Merged
derekross merged 1 commit into
derekross:mainfrom
gitColinX:husky-bt-haptics-firmware
Nov 13, 2026
Merged

derekross merged 1 commit into
derekross:mainfrom
gitColinX:husky-bt-haptics-firmware

Conversation

@gitColinX

@gitColinX gitColinX commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

tools/extract-vendor-firmware -d husky staged the four Wi-Fi files only, with the note that Bluetooth and the rest "wait for drivers". Those drivers are on omamobile now (kernel #199 Bluetooth, #200 haptics), so an installed Pixel 8 Pro has the drivers and not the files:

cs40l26-vibra 1-0043: Cirrus Logic CS40L26 ID 0x40a260, revision 0xa1
cs40l26-vibra 1-0043: Direct firmware load for cs40l26.wmfw failed with error -2
cs40l26-vibra 1-0043: probe with driver cs40l26-vibra failed with error -2
Bluetooth: hci0: BCM4398D0
Bluetooth: hci0: BCM: firmware Patch file not found, tried:
Bluetooth: hci0: BCM: 'brcm/BCM.google,zuma-husky.hcd'
Bluetooth: hci0: BCM: 'brcm/BCM.hcd'

That is from my unit (G1MNW, Samsung 128 GB UFS) on plain omamobile at 5c8b9e542 with omamobile-device-husky 0.1.10: no haptics input device, and a Bluetooth scan that finds nothing.

What changes

  • husky's map gains stock's brcm/BCM.hcd as brcm/BCM.google,zuma-husky.hcd (the name btbcm tries first, and the file kernel Pixel 11 Pro XL (kodiak) — stock facts #199 was tested with) and the five CS40L26 files under the names the 7 Pro and the 9a already use.
  • The Bluetooth sanity check for husky looks for the module and board string (G5SN_V<n>_HK3), because this BCM.hcd doesn't carry a chip name: on CP3A.261005.005 it reads G5SN_V17_HK3 REL BR:0169 FW:b8718197dc, the release Pixel 11 Pro XL (kodiak) — stock facts #199's dmesg shows.
  • Not copied: BCM_174.hcd (a BCM4398 B0 patch), BCM_181.hcd, BTFW_B.hcd, and cs40l26-dbc.bin (cs40l26-vibra doesn't request it). The header says so.
  • The haptics checks (Halo WMFW, FIRMWARE_CS40L26, the buzz generator, WMDR tunings) now run for husky too.
  • tests/extract-vendor-firmware: husky's fixture has the new files, the reuse test expects ten files, and a new case refuses another chip's BCM.hcd for husky.
  • The device package's README names the new files.

Tested

  • tests/extract-vendor-firmware: all pass, including the real-ext4 cases.

  • tools/pr-check origin/main: all ok.

  • The tool on my own factory image (husky CP3A.261005.005, -s G1MNW): ten files staged, the four Wi-Fi files byte-identical to the ones already installed on the phone.

  • The six new files installed on the phone (same unit, Brett's husky-test-20261109-t1 tag plus the RTC commits, 7.3.0-rc6), one restart:

    • haptics: cs40l26-vibra 1-0043: Firmware 0x1800d4 rev 7.2.91 running, the cs40l26_vibra input device appears, and two 500 ms FF_RUMBLE effects were felt;
    • Bluetooth: BCM 'brcm/BCM.google,zuma-husky.hcd' Patch, then BCM4398D0 G5SN_V17_HK3 REL BR:0169 FW:b8718197dc CFG:66e1413cd1 [Baseline: 1370], and a 15 s scan finds 37 devices (none before). A pair of AirPods Pro paired from the Bluetooth settings page: paired, bonded and trusted, with the Audio Sink and Handsfree services listed. Connected, they came up as a PipeWire sink on the a2dp-sink profile, and a quiet 440 Hz tone played through them was heard.

Not tested, not covered

…s files

`-d husky` staged the four Wi-Fi files only, with Bluetooth and the rest left "for drivers". Kernel derekross#199 (Bluetooth) and derekross#200 (haptics) are on `omamobile` now, so an installed Pixel 8 Pro had the drivers and not the files: cs40l26-vibra stopped at "No cs40l26.wmfw" and btbcm at "firmware Patch file not found" (a scan found nothing). husky's map gains stock's `BCM.hcd` as `brcm/BCM.google,zuma-husky.hcd` and the five CS40L26 files the 7 Pro and the 9a take. This `BCM.hcd` names the module and board ("G5SN_V17_HK3 REL ..."), not the chip, so husky's Bluetooth check looks for that; the haptics checks run for husky too. The test's husky fixture has the new files and a case refuses another chip's patch.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@derekross

Copy link
Copy Markdown
Owner

Thank you, this is a clean change and the description says exactly what ran and what didn't. I checked it here: tests/extract-vendor-firmware passes on your head, the new refusal really bites (with husky's Bluetooth check switched off, both of your new tests fail), the lists stay sorted in the C locale as #712 requires, and the Bluetooth and haptics nodes are in zuma-husky.dts on omamobile. The line you quote from your BCM.hcd is the same one kernel #199's author saw on his phone. CI is green, so I'm merging it.

One question, because the tool publishes all or nothing: from now on a husky image without BCM.hcd, without one of the five CS40L26 files, or with a BCM.hcd that doesn't carry G5SN_V<n>_HK3, stops the run, and the owner gets no Wi-Fi files either, where before they got four. Which factory builds have you looked at besides CP3A.261005.005? If you have an older one to hand, a run of the tool on it (just its ==> lines) would tell us whether the check is safe for owners who haven't updated stock in a while.

Small things for a follow-up, none urgent:

  • The refusal prints the pattern: "BCM.hcd is not a G5SN_V[0-9]*_HK3 Bluetooth patch". A readable name next to the pattern would be kinder.
  • No test feeds husky a wrong cs40l26.wmfw: with husky taken out of the first haptics check, the suite still passes.
  • In the device package's README the new sentence comes before the Wi-Fi paragraph it says "also" about.
  • Until the 8 Pro has its own address step, Bluetooth comes up on the placeholder address, the same on every unit, and a pairing made now won't survive the change. A line in the README would warn owners. (No need to post the address.)

Thanks for testing the pairing and the rumble as well as the extraction.

@derekross
derekross merged commit c95e46f into derekross:main Nov 13, 2026
2 checks passed
gitColinX added a commit to gitColinX/omarchy-mobile that referenced this pull request Nov 15, 2026
Derek's review of derekross#722 asked for three small things:

- The refusal named the pattern ("is not a G5SN_V[0-9]*_HK3 Bluetooth
  patch"). BT_NAME gives it a readable name where BT_CHIP is a pattern:
  "BCM.hcd is not a Pixel 8 Pro (G5SN_V<n>_HK3) Bluetooth patch". Other
  devices keep their chip name.
- No test fed husky a wrong cs40l26.wmfw. A Halo WMFW that isn't the
  CS40L26's is now refused for husky; with husky taken out of the
  haptics check, that test fails.
- The device README said "also" before the Wi-Fi paragraph it referred
  to. The sentence follows it now, with a line that pairings made on the
  placeholder Bluetooth address won't survive the address step.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross pushed a commit that referenced this pull request Nov 15, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gitColinX added a commit to gitColinX/omarchy-mobile that referenced this pull request Nov 15, 2026
… a third phone

A NOTES entry for the third unit (Samsung 128 GB UFS 3.1) on merged
omamobile at 82f31d3a7 with the firmware from extract-vendor-firmware
(derekross#722): AirPods paired and played over A2DP, two rumble effects felt,
the torch seen, and the gauge reading at boot with no overlay (the bus
on by default since kernel derekross#205). The husky row's Bluetooth, Battery,
Haptics and Torch cells move from testing to works and link it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gitColinX added a commit to gitColinX/omarchy-mobile that referenced this pull request Nov 16, 2026
… a third phone

A NOTES entry for the third unit (Samsung 128 GB UFS 3.1) on merged
omamobile at 82f31d3a7 with the firmware from extract-vendor-firmware
(derekross#722): AirPods paired and played over A2DP, two rumble effects felt,
the torch seen, and the gauge reading at boot with no overlay (the bus
on by default since kernel derekross#205). The husky row's Bluetooth, Battery,
Haptics and Torch cells move from testing to works and link it.

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