Repository navigation
extract-vendor-firmware: the Pixel 8 Pro's Bluetooth patch and haptics files - #722
Conversation
…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>
|
Thank you, this is a clean change and the description says exactly what ran and what didn't. I checked it here: One question, because the tool publishes all or nothing: from now on a husky image without Small things for a follow-up, none urgent:
Thanks for testing the pairing and the rumble as well as the extraction. |
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>
… 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>
… 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>
tools/extract-vendor-firmware -d huskystaged the four Wi-Fi files only, with the note that Bluetooth and the rest "wait for drivers". Those drivers are onomamobilenow (kernel #199 Bluetooth, #200 haptics), so an installed Pixel 8 Pro has the drivers and not the files:That is from my unit (G1MNW, Samsung 128 GB UFS) on plain
omamobileat 5c8b9e542 withomamobile-device-husky0.1.10: no haptics input device, and a Bluetooth scan that finds nothing.What changes
brcm/BCM.hcdasbrcm/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.G5SN_V<n>_HK3), because thisBCM.hcddoesn't carry a chip name: on CP3A.261005.005 it readsG5SN_V17_HK3 REL BR:0169 FW:b8718197dc, the release Pixel 11 Pro XL (kodiak) — stock facts #199's dmesg shows.BCM_174.hcd(a BCM4398 B0 patch),BCM_181.hcd,BTFW_B.hcd, andcs40l26-dbc.bin(cs40l26-vibra doesn't request it). The header says so.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'sBCM.hcdfor husky.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-t1tag plus the RTC commits, 7.3.0-rc6), one restart:cs40l26-vibra 1-0043: Firmware 0x1800d4 rev 7.2.91 running, thecs40l26_vibrainput device appears, and two 500 msFF_RUMBLEeffects were felt;BCM 'brcm/BCM.google,zuma-husky.hcd' Patch, thenBCM4398D0 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 thea2dp-sinkprofile, and a quiet 440 Hz tone played through them was heard.Not tested, not covered
omamobile-bt-addrit stays at the placeholder (as Pixel 11 Pro XL (kodiak) — stock facts #199 says); that is a separate change to the device package.