Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions packages/omamobile-device-husky/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,11 +28,15 @@ Not in this package: the boot-success marker, the charger, cameras, and the slot

## Firmware the phone needs

Nothing here is in the package. `tools/extract-vendor-firmware -d husky -s SKU` also stages the Bluetooth patch (`brcm/BCM.google,zuma-husky.hcd`, stock's `BCM.hcd`) and the five CS40L26 haptics files (`cs40l26.wmfw`, `cs40l26.bin` and the three tuning files) from the same image. Wi-Fi needs four files from Google's firmware for the BCM4398 D0, which `tools/extract-vendor-firmware -d husky -s SKU` takes from the owner's own factory image or OTA `vendor.img`. They're installed under `/usr/lib/firmware/updates/brcm`, with the board-suffixed names brcmfmac loads first:
Nothing here is in the package. Wi-Fi needs four files from Google's firmware for the BCM4398 D0, which `tools/extract-vendor-firmware -d husky -s SKU` takes from the owner's own factory image or OTA `vendor.img`. They're installed under `/usr/lib/firmware/updates/brcm`, with the board-suffixed names brcmfmac loads first:

- `brcmfmac4398d0-pcie.google,zuma-husky.bin`: the firmware;
- `.txt`: the NVRAM for the phone's region, which `-s` picks from the hardware SKU (`grep hardware.sku /proc/bootconfig`);
- `.clm_blob`: the regulatory data;
- `.txcap_blob`: the TX capabilities.

The kernel side is [kernel #156](https://github.com/derekross/linux-omarchy-mobile/pull/156) (a draft). Nothing in this package starts or configures Wi-Fi: NetworkManager finds `wlp1s0` on its own.
The kernel side merged on 2026-11-09 through [kernel #187](https://github.com/derekross/linux-omarchy-mobile/pull/187), which carried [#156](https://github.com/derekross/linux-omarchy-mobile/pull/156)'s commits. Nothing in this package starts or configures Wi-Fi: NetworkManager finds `wlp1s0` on its own.

The same run also stages the Bluetooth patch (`brcm/BCM.google,zuma-husky.hcd`, stock's `BCM.hcd`) and the five CS40L26 haptics files (`cs40l26.wmfw`, `cs40l26.bin` and the three tuning files) from the same image.

Since 0.1.13 the controller takes the phone's own address at boot (`omamobile-bt-addr`, above). Pairings made before 0.1.13, on the placeholder address, have to be made again once.
5 changes: 4 additions & 1 deletion tests/extract-vendor-firmware
Original file line number Diff line number Diff line change
Expand Up @@ -251,7 +251,10 @@ refuses "panther: a missing MFC firmware" "/vendor/firmware/mfc_fw.bin is missin
# husky's BCM.hcd names the module and board, not the chip: another phone's
# patch (here the 7 Pro's) is refused
rm -rf "$t/husky-otherbt"; cp -r "$t/husky" "$t/husky-otherbt"; echo "BCM4389C1 fictional" > "$t/husky-otherbt/firmware/brcm/BCM.hcd"
refuses "husky: another chip's Bluetooth patch" "BCM.hcd is not a" "$t/husky-otherbt" "$t/ext4.img" -d husky
refuses "husky: another chip's Bluetooth patch" "BCM.hcd is not a Pixel 8 Pro (G5SN_V<n>_HK3) Bluetooth patch" "$t/husky-otherbt" "$t/ext4.img" -d husky
# husky runs the haptics checks too: a Halo WMFW that isn't the CS40L26's is refused
rm -rf "$t/husky-otherhap"; cp -r "$t/husky" "$t/husky-otherhap"; halo "calib fictional" > "$t/husky-otherhap/firmware/cs40l26.wmfw"
refuses "husky: another part's haptics firmware" "cs40l26.wmfw is not a CS40L26 firmware" "$t/husky-otherhap" "$t/ext4.img" -d husky
rm -rf "$t/v2-missing"; cp -r "$t/v2" "$t/v2-missing"; rm "$t/v2-missing/firmware/aoc.bin"
refuses "a missing ext4 file with an older copy in OUT" "/vendor/firmware/aoc.bin is missing" "$t/v2-missing" "$t/ext4.img"
refuses "a missing EROFS file with an older copy in OUT" "/vendor/firmware/aoc.bin is missing" "$t/v2-missing" "$t/erofs.img"
Expand Down
5 changes: 4 additions & 1 deletion tools/extract-vendor-firmware
Original file line number Diff line number Diff line change
Expand Up @@ -130,6 +130,8 @@ FW_BASE="brcmfmac4389c1-pcie"
# and in BCM.hcd ("BCM<CHIP> <release>")
WIFI_CHIP="4389c1"
BT_CHIP="BCM4389C1"
# What the Bluetooth refusal calls the patch, where BT_CHIP is a pattern
BT_NAME=""
DEST_REL="usr/lib/firmware/updates"

# source path in the vendor partition -> path under $DEST_REL
Expand Down Expand Up @@ -258,6 +260,7 @@ case $DEVICE_OPT in
FW_BASE="brcmfmac4398d0-pcie"
WIFI_CHIP="4398d0"
BT_CHIP="G5SN_V[0-9]*_HK3"
BT_NAME="Pixel 8 Pro (G5SN_V<n>_HK3)"
# Google's SKU table (dhd_custom_google.c); husky's vendor has NVRAMs for
# MMW, ROW and NA only, so the others take the module's default, as on stock
case $SKU in
Expand Down Expand Up @@ -466,7 +469,7 @@ brcm="$dest/brcm"
grep -aq "$WIFI_CHIP-roml" "$brcm/$FW_BASE.$BOARD.bin" ||
die "fw_bcmdhd.bin is not a $WIFI_CHIP PCIe firmware"
[[ -z $BT_CHIP ]] || grep -aq "$BT_CHIP" "$brcm/BCM.$BOARD.hcd" ||
die "BCM.hcd is not a $BT_CHIP Bluetooth patch"
die "BCM.hcd is not a ${BT_NAME:-$BT_CHIP} Bluetooth patch"
grep -aq '^NVRAMRev=' "$brcm/$FW_BASE.$BOARD.txt" ||
die "bcmdhd.cal does not look like a Broadcom text NVRAM"
wmfw_halo() { # WMFW, Halo core (4): what cs_dsp accepts for this part
Expand Down