Repository navigation
device-panther 0.1.10: Wi-Fi at boot with the Pixel 7 Pro's guarded start, unloaded around suspend (from #419) - #475
Merged
Merged
Conversation
The Pixel 7 has the 7 Pro's BCM4389 on the same PCIe controller, and its bootloader writes the same wlan_mac1 into the device tree. So the package takes the 7 Pro's Wi-Fi guard, its unit and autoload blacklist, and the MAC address helper with its udev rule, byte for byte; test/all checks the copies against device-cheetah, as it does for the other shared files. Bluetooth's files come with nesmeck's Bluetooth change. omamobile-wifi.service is enabled, as on the 7 Pro. That changes the test's old rule that nothing here starts hardware: Wi-Fi is now the one radio started at boot, and only through its guard (hang marker, modules blacklisted for autoload, no SysMMU firewall, and the unit only runs when the DTB enables 14520000.pcie). On a kernel without the Wi-Fi node it is skipped. The test now fails on any other wants link, and still fails on the boot-success marker, the charge guard, AoC and cameras. On a Pixel 7 the files, copied by hand, have the same sha256 as these. On 7.3.0-rc6-omamobile-push1-g4446f52aefe8 (omamobile fe9627c00 with linux-omarchy-mobile#181's series and the 7 Pro's Wi-Fi and Bluetooth nodes), Wi-Fi was started by hand: wlp1s0 came up with the phone's own firmware and saw networks. On the next boot (the same kernel plus a CMA change, g3631214cc15a) the enabled unit brought wlp1s0 up about 5 s into boot, and it connected. I used AI help (Claude) to work on this.
Copy the Pixel 7 Pro's bin/omamobile-sleep and its system-sleep link unchanged, so the Pixel 7 keeps the 7 Pro's default: Wi-Fi unloads before every suspend and reloads through the guarded service after, unless /etc/omamobile/wifi-keep-across-sleep exists, and goes back to unloading for the rest of the boot after a wake that fails in the Wi-Fi device. Before this, Wi-Fi would have stayed loaded through every suspend on the Pixel 7, which hasn't run there yet. The package test compares the script and the link with cheetah's, like the other copied files, and checks that both are staged. Checked that the test fails when either copy drifts. Not run on the phone: no suspend has been done with this package. I used AI help (Claude) to work on this.
Resolves the README, install and test/all conflicts with the camera work (#443). The test's list of allowed boot-time links also takes main's omamobile-camera.timer. 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
…tart, unloaded around suspend (derekross#419) (derekross#475) The Pixel 7's Wi-Fi (BCM4389 on PCIe) starts at boot through the Pixel 7 Pro's guarded start: the PCIe controller, then brcmfmac, behind a hang marker, with the modules blacklisted for autoload and the unit run only when the DTB enables the controller. The link gets the bootloader's MAC before NetworkManager takes it. The Pixel 7 Pro's sleep hook, copied byte for byte, unloads Wi-Fi around suspend unless /etc/omamobile/wifi-keep-across-sleep exists. Three attended suspend cycles with the package installed all woke and reconnected. Merged onto main with the conflicts against the camera work (derekross#443) resolved; the test's list of boot-time links also takes omamobile-camera.timer. Co-Authored-By: Ángel René <17342133+angelrenefm@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
angelrenefm's #419, merged onto main with the conflicts against the camera work (#443) resolved, as promised on #419. The resolution is the one from the review. The only non-obvious line: the test's list of allowed boot-time links also takes main's
omamobile-camera.timer. The panther package test passes.Once this is published, linux-omarchy-mobile#195 (the Wi-Fi device-tree node) can merge.
Co-authored by @angelrenefm; the squash keeps the credit.
🤖 Generated with Claude Code