Repository navigation
omamobile-device-husky 0.1.13: the Bluetooth controller gets the phone's address - #752
Conversation
…e's address The BCM4398 comes up on its placeholder address (43:98:D0:..), the same on every 8 Pro, while the bootloader writes the phone's own address into /chosen/config/bt_addr at every boot, as on the 7 Pro and the 9a. This takes the 9a's omamobile-bt-addr, its udev rule (hci_uart_bcm) and its unit, with the chip named: the script powers the controller on once, sets the public address with btmgmt, waits for the index to come back and checks the address. The test compares the three files with the 9a's when run from the repository. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Thank you, Colin. This is the right way to bring the address step over: the 9a's script, unit and rule with only the chip's name changed, a test that keeps them that way from the repository and still lets the package build alone, and a phone run that covers the boot path, the address check and a pairing on the new address. I checked the three files against the 9a's (only the names in comments differ), ran the package's test on main with this merged, and found no address in the diff or the description beyond the shared placeholder. The version is free and CI is green, so I'll merge it. One thing for later, which isn't yours to fix here: the rule's On #746: once this is in, the README paragraph there about pairing again "until this package has its own Bluetooth address step" can go, as you offered. |
derekross#752 gave the package its Bluetooth address step, so the paragraph that said a pairing wouldn't survive "until this package has its own address step" now says that pairings made before 0.1.13 have to be made again once. The Wi-Fi line named kernel derekross#156 as a draft; it merged through kernel derekross#187 on 2026-11-09. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 8 Pro's BCM4398 comes up on its placeholder address (43:98:D0:..), the same on every unit, as #199 and #722 noted. Meanwhile the bootloader writes the phone's own address into
/chosen/config/bt_addrat every boot, as it does on the 7 Pro and the 9a. This adds the 9a's address step to the 8 Pro's device package.What changes
bin/omamobile-bt-addr,vendor/systemd/system/omamobile-bt-addr@.serviceandvendor/udev/rules.d/80-omamobile-bt-addr.rules: the 9a's three files, with BCM4398 in place of BCM4383 and the 8 Pro's placeholder in the comment. The rule starts the unit when anhci_uart_bcmcontroller appears. The script powers the controller on once, sets the public address withbtmgmt, waits for the index to come back, and checks that the address took. The address is read at run time; nothing about it is in the package.installstages them.test/allchecks they're staged and that the script reads the bootloader's DT. Run from the repository, it also checks that the three files match the 9a's apart from the chip name; it skips that check when the package is built alone, as the cheetah comparisons do.Tested
test/allpasses in the repository and as a lone copy of the package (astools/phone-install-packagebuilds it).tools/pr-check origin/main: all ok.omamobileat82f31d3a7, the package built and installed on the phone withtools/phone-install-package:/chosen/config/bt_addris present, colon-separated hex, unicast and globally administered;hci_uart_bcm, which the rule matches;systemctl start omamobile-bt-addr@hci0finished cleanly; after: the controller's address matches the bootloader's, and it is powered.omamobile-bt-addr@hci0at 4.06 s and it finished at 7.37 s; the controller came up powered on the bootloader's address;running, no failed units.a2dp-sink, and a quiet tone played through them was heard.Not tested
Related