Repository navigation
device-lynx: Bluetooth on the APM UART - #98
FlorencioJP wants to merge 1 commit into
Conversation
|
Thank you, @FlorencioJP. The NOTES table is the right record: driver and firmware, chip version, the baud finding with its control, the clocks against stock, the missing address and the A few things before it can merge:
Smaller things:
|
The Pixel 7a carries the WCN6855 BT core on the APM USI1 UART (ttySAC18 in Google's kernel), as cheetah carries its BCM4389. Enable cmu_apm, usi_apm1, serial_apm1 and pinctrl_peric0 and describe the controller as qcom,wcn6855-bt: BT_EN on gpp16-2, and the 0.95 V buck shared with Wi-Fi on gph2-5 as a fixed regulator raised 7 ms before BT_EN, as stock btpower does. WLAN_EN (gph2-4) stays low. With this node Bluetooth owns gph2-5: hci_qca disables its supplies on power-off, so the buck drops whenever Bluetooth goes down (stock btpower never drops it), including once at every boot while the controller has no address yet. A shared qcom,wcn6855-pmu node is the way out once Wi-Fi runs. No device-wake or host-wake line is described, so Bluetooth cannot wake the phone. max-speed is 3 Mbaud: at 3.2 Mbaud every TLV segment of the firmware download answers with "Frame reassembly failed (-84)" on this UART; 1, 2 and 3 Mbaud work. Tested on one phone (chip revision 0x400c0210; untested on 0x400c1211) with hci_uart/btqca and linux-firmware's qca/hpbtfw21.tlv + hpnv21.bin, on 7.3.0-rc6-omamobile-lynx-wifi1 built from the integration tree at 1cb4bd3, which carries the HSI2 pin controller that defines gph2: firmware loaded 3 s after boot, controller powered, scan sees the neighbours. The controller reports no public address; userspace sets the one the bootloader publishes in /chosen/config/bt_addr. Facts and log excerpts: derekross/omarchy-mobile#98 and device/lynx/NOTES.md there. These nodes must be enabled in the boot DTB: enabling cmu_apm through a runtime overlay oopses, since gs201_cmu_probe is __init. Assisted-by: LLM Signed-off-by: Jean-Paul Florencio <jpflorencio@version-tracker.app>
|
Thanks. Pushed as a second commit for now ( Left for the rebase once #88 is in: squash into one commit signed by Jean-Paul Florencio, change only the Bluetooth cell of the lynx row, and add the |
|
Thank you, @FlorencioJP. The second commit covers what I asked for in the notes and the matrix. The Bluetooth section now comes first, with the kernel the phone ran. It says which address the phone uses now: the bootloader's, with What's left is mostly the rebase you already planned. Some of it got bigger now that #88 is merged:
Smaller things:
On order: kernel #98 first (it waits for me to publish the HSI2 pin controller, and then for your PMU version), then this one, rebased, with the cell above. Thanks for keeping both PRs in step. The notes table is a model of how a bring-up finding should be recorded. |
…wenty-sixth rounds (#127) * docs/review: 19 lessons and 3 corrections from the twenty-fifth round The confirmed candidates from round 25 (L-260 to L-278): the 9a slot B marking as a devinfo question, cross-repository links, squash-merged stacks and version files, stale hand-built prebuilts, and before-merge Pixel 7 Pro runs on omamobile-int. C-16 to C-18 correct our own earlier comments on kernel #98, kernel #80 and #74; L-241 is corrected in place. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs/review: 15 lessons from the twenty-sixth round L-279 to L-293: the 9a's slot B hold and what made devinfo writable (#125), per-device flags checked by building both command lines (#101), env defaults in the shared build library and CI waiting for approval (#79), GLib retry paths and radio stops checked at the controller (#99), silent re-pushes and stacks with several tops (the tegu stack), and two of our own: merge only after every check has finished (#126), and an empty diff is checked for empty inputs (kernel #123). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The plan merged in #88 as it stood before the fs_ready diagnostic boot (run 17, 2026-10-27, #36). Record its result and what follows from it: - status line: the boot with Google's host stack, Google's own trigger and full Android's 5 s wait ran and stalled the same way, so that pair is ruled out and the variants are stopped; the cold stock read is the one measurement left; - section 7 item 1: the run as reported on #36 (Google's kernel and vendor_dlkm modules, 68 modules, Bluetooth off, fs_ready at 10.8 s, IN_COLD_BOOT_CAL, the power-up 5 s later, BHI from 16.0 s, 0xfad00000 on every dump, -110 at 76.8 s), and the module count that matches it; - section 7 item 2: the module comparison as background, with the caveat about first-stage loads, and the CNSS profile's 16 modules on top of the USB profile's 52, in load order; - section 8: the ramoops console survives only a warm return, so the diagnostic's init writes warm to /sys/kernel/reboot/mode first; - section 5 and the pin table: gph2-5 reads output low at every Linux boot only on a kernel without the Bluetooth node (linux-omarchy-mobile #98); with it a regulator owns the pin, so unbind the serdev first and record which kernel a run used. Assisted-by: LLM Signed-off-by: Jean-Paul Florencio <jpflorencio@version-tracker.app> Co-authored-by: Jean-Paul Florencio <jpflorencio@version-tracker.app>
Twenty-six lessons (L-318 to L-343) from the round 29 omamobile-reviewer runs, and three corrections: C-20, our kernel #109 advice that the Pixel 7's SPI controller DMAs the touch report (it polls; gs201's spi_0 has no dmas); C-21, asking for FT3658=m in panther's device kernel.config against RELEASES; C-22, a Bluetooth address in kernel #98's thread that the first review missed. Five candidates were dropped as already covered. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The matrix and the Wanted list against what has merged since #140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were closed because they landed unchanged through kernel #134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the 2026-10-28 notes. Touch stays WIP: kernel #134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel #133) and the kernel option with the touch notes (#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names its open kernel PR, #116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133) records it scanning through its own UART; kernel #98 and #98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes the merged tier 1 auto-sleep (#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open #171, #172, #174-#176. - Wanted: coral's #52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (#55, #56, #58, #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and kernel #115, both open. The Pixel 9a row and the Pixel 9 family line are left to #165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
|
One correction from my side before your rebase: the BNEP options can't break another phone, so they belong in |
… rounds L-348 to L-361: shared drivers judged against every int-line user (#150), board pins against every stock user (#151), ownership flags under the consumer's lock (#152), /chosen children and Google's panel constants (#154), same-day notes PRs on one device (#208/#209), merge simulations for DEVICES rows, ours included (#165), stacked PRs that merged main (#115/#117), titles behind renumbered versions, a contributor merge that dropped the PR (#99), smoke package lists as provenance and "owner-authorized" writes (#200), promised fixes and named tags checked on the remote (#153/#157/#158), and file swaps into old packages (#193). C-23 (usbc-deadman's device scope, kernel #107) and C-24 (BNEP in a lynx-only fragment, #98). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Pixel 7a carries the WCN6855 BT core on the APM USI1 UART (ttySAC18 in Google's kernel), as cheetah carries its BCM4389. Enable cmu_apm, usi_apm1, serial_apm1, pinctrl_peric0 and pinctrl_hsi2, and describe the controller as qcom,wcn6855-bt powered by a qcom,wcn6855-pmu node (pwrseq-qcom-wcn): BT_EN on gpp16-2, and the 0.95 V buck shared with Wi-Fi on gph2-5 as the sequencer's input, a fixed regulator with the 7 ms ramp stock btpower waits before BT_EN. The sequencer then holds BT_EN high and waits 50 ms. No wlan-enable-gpios is given: WLAN_EN (gph2-4) stays low until a PCIe node takes the sequencer's wlan target. With this node Bluetooth owns gph2-5 and drops it on power-off: off is BT_EN low and then the regulators, so the buck goes down whenever Bluetooth goes down (stock btpower never drops it), including once at every boot while the controller has no address yet. The five PMIC rails behind the chip's I/O, 1.3 V and 1.9 V inputs are an always-on stand-in regulator: stock's device tree names no supply on its cnss2 or btpower node, so which PMIC regulators feed them is unknown. No device-wake or host-wake line is described, so Bluetooth cannot wake the phone. max-speed is 3 Mbaud: at 3.2 Mbaud every TLV segment of the firmware download answers with "Frame reassembly failed (-84)" on this UART; 1, 2 and 3 Mbaud work. Tested on one phone (chip revision 0x400c0210; untested on 0x400c1211) with hci_uart/btqca, pwrseq-qcom-wcn and linux-firmware's qca/hpbtfw21.tlv + hpnv21.bin, on 7.3.0-rc6-omamobile-lynx-wifi1 with this file's DTB: the sequencer holds the buck (five users), BT_EN and gph2-5 read high, firmware loaded 3 s after boot, controller powered, a 20 s scan sees the neighbours, and unbinding the serdev driver drops both pins and disables the buck. The controller reports no public address; userspace sets the one the bootloader publishes in /chosen/config/bt_addr. Facts and log excerpts: derekross/omarchy-mobile#98 and device/lynx/NOTES.md there. These nodes must be enabled in the boot DTB: enabling cmu_apm through a runtime overlay oopses, since gs201_cmu_probe is __init. Assisted-by: LLM Signed-off-by: Jean-Paul Florencio <jpflorencio@version-tracker.app>
e82e8de to
a53e1b2
Compare
|
@derekross, thanks for merging kernel #98. Rebased onto today's Since the lynx device package is upstream now, the address service moved into it, as device-lynx 0.2.3 (#313 took 0.2.2): DEVICES.md says |
|
Thank you, @FlorencioJP. The rebase is clean, the BNEP options sit where I asked, and the address service is in the device package. The notes are as careful as before, and both #88 sentences are fixed in NOTES. CI is green, and the package test passes here too. Three things before I merge:
One small leftover from October: For the record, adding BNEP to the shared fragment also gives the 7 Pro a |
a53e1b2 to
436db68
Compare
The matrix re-read against what merged and ran on hardware since 2026-11-02: - Pixel 7: Bluetooth and the torch move to testing (kernel #196, #197, #426); fingerprint moves to WIP (kernel #207; the package side, #458, is in review); AVB footers and reboot=warm noted. - Pixel 8a: a new row, from first light and UFS behind the guard (kernel #192, #206; #414). - Pixel 6 Pro: GPU scaling and cooling (kernel #189) and UFS suspend (kernel #188) merged. - Pixel 9a: GPU levels merged through kernel #96; GNSS's moving-car session (#114) and the link driver (kernel #185). - Pixel 7a: Bluetooth's device tree merged (kernel #98). The Pixel 8 Pro's row is left to #472. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
@derekross, done, as 436db68 on today's The boot with this package's own copy of the address service comes next, when the phone is back on the bench: |
|
Thank you, @FlorencioJP. All three are in: the session line is gone, WIFI-PLAN now says A heads-up for that push: today's DEVICES pass (#474) touched the lynx Bluetooth cell and the Pixel 7a line in the Wanted list, so the branch now conflicts there. When you rebase, keep your two lines as they are. They already say what mine says, and mine ("package side in review") stops being true once this merges. |
…ixed, 300 of 300 twice The dead storage after a wake was the UFS pads (reference clock and reset) coming back as inputs; the host now re-applies its pin state at resume. The silent no-wake was C2 during suspend-to-idle with the PMU's wake-up masks never programmed; the C2 states are kept out of s2idle. 300 RTC-woken cycles passed WFI-only (derekross#96) and again with C2 enabled at runtime (derekross#98). The series scripts (sleep-series.sh, sleep-series-loop.sh) record the modem unit's state and put it back, cap the automatic recoveries, save the ramoops console after a self-reboot, and never reboot a palmtop that rebooted on its own. The record lists the silent no-wakes and the dead-storage wakes separately, with the conditions for unattended runs.
…ixed, 300 of 300 twice The dead storage after a wake was the UFS pads (reference clock and reset) coming back as inputs; the host now re-applies its pin state at resume. The silent no-wake was C2 during suspend-to-idle with the PMU's wake-up masks never programmed; the C2 states are kept out of s2idle. 300 RTC-woken cycles passed WFI-only (derekross#96) and again with C2 enabled at runtime (derekross#98). The series scripts (sleep-series.sh, sleep-series-loop.sh) record the modem unit's state and put it back, cap the automatic recoveries, save the ramoops console after a self-reboot, and never reboot a palmtop that rebooted on its own. The record lists the silent no-wakes and the dead-storage wakes separately, with the conditions for unattended runs.
436db68 to
5b5413c
Compare
|
Rebased once more onto |
|
Thank you, @FlorencioJP. I compared the new head with 436db68 and it is the same commit, with only your two lynx lines moved onto today's row. So the one thing left is the boot with this package's own copy of the address service, whenever the phone is back on the bench: One small thing for that push: the Bluetooth cell says the kernel side is "not yet in a published kernel", and it is now. On the version: #438, #484 and #403 also write device-lynx 0.2.3 at the moment. Yours keeps it if it lands first; I'll check the number again when I merge. |
5b5413c to
8fa0be5
Compare
|
Booted with this branch's own package today, as asked. Built on the phone with The address the controller carries is the bootloader's One unbind and bind of 1.07 s from start to the address, against 0.05 s at boot: that is the "Invalid Index" retry doing its work (the script prints only the last answer). tools/phone-smoke reportphone-smoke: lynxKernel
Packages: hyprland 0.56.2-5.1, libcamera 0.7.2-4.21, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamobile-apps 0.2.0-1, omamobile-device-lynx 0.2.3-1, omamobile-firstboot 0.1.2-1, omamobile-keyring 20261026.lynx1-1, omamobile-lynx-bluetooth 0.1.2-1, omamobile-lynx-hardware 0.1.2-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.12-1, omamobile-owl-widgets 0.1.1-1, omamobile-shell 0.2.29-1, omarchy 4.0.6-1, quickshell 0.3.2.r7.g2b4501a-1 Two things to say plainly:
|
|
Thank you, @FlorencioJP. That is the boot I was waiting for, and it shows what it needed to: Two small things and it goes in:
Two questions, neither blocking:
One thing for later, not for this PR: the rule's |
The plan merged in derekross#88 as it stood before the fs_ready diagnostic boot (run 17, 2026-10-27, derekross#36). Record its result and what follows from it: - status line: the boot with Google's host stack, Google's own trigger and full Android's 5 s wait ran and stalled the same way, so that pair is ruled out and the variants are stopped; the cold stock read is the one measurement left; - section 7 item 1: the run as reported on derekross#36 (Google's kernel and vendor_dlkm modules, 68 modules, Bluetooth off, fs_ready at 10.8 s, IN_COLD_BOOT_CAL, the power-up 5 s later, BHI from 16.0 s, 0xfad00000 on every dump, -110 at 76.8 s), and the module count that matches it; - section 7 item 2: the module comparison as background, with the caveat about first-stage loads, and the CNSS profile's 16 modules on top of the USB profile's 52, in load order; - section 8: the ramoops console survives only a warm return, so the diagnostic's init writes warm to /sys/kernel/reboot/mode first; - section 5 and the pin table: gph2-5 reads output low at every Linux boot only on a kernel without the Bluetooth node (linux-omarchy-mobile derekross#98); with it a regulator owns the pin, so unbind the serdev first and record which kernel a run used. Assisted-by: LLM Signed-off-by: Jean-Paul Florencio <jpflorencio@version-tracker.app> Co-authored-by: Jean-Paul Florencio <jpflorencio@version-tracker.app>
Twenty-six lessons (L-318 to L-343) from the round 29 omamobile-reviewer runs, and three corrections: C-20, our kernel derekross#109 advice that the Pixel 7's SPI controller DMAs the touch report (it polls; gs201's spi_0 has no dmas); C-21, asking for FT3658=m in panther's device kernel.config against RELEASES; C-22, a Bluetooth address in kernel derekross#98's thread that the first review missed. Five candidates were dropped as already covered. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The matrix and the Wanted list against what has merged since derekross#140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were closed because they landed unchanged through kernel derekross#134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the 2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133) and the kernel option with the touch notes (derekross#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names its open kernel PR, derekross#116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133) records it scanning through its own UART; kernel derekross#98 and derekross#98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes the merged tier 1 auto-sleep (derekross#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176. - Wanted: coral's derekross#52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58, derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and kernel derekross#115, both open. The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
… rounds L-348 to L-361: shared drivers judged against every int-line user (derekross#150), board pins against every stock user (derekross#151), ownership flags under the consumer's lock (derekross#152), /chosen children and Google's panel constants (derekross#154), same-day notes PRs on one device (derekross#208/derekross#209), merge simulations for DEVICES rows, ours included (derekross#165), stacked PRs that merged main (derekross#115/derekross#117), titles behind renumbered versions, a contributor merge that dropped the PR (derekross#99), smoke package lists as provenance and "owner-authorized" writes (derekross#200), promised fixes and named tags checked on the remote (derekross#153/derekross#157/derekross#158), and file swaps into old packages (derekross#193). C-23 (usbc-deadman's device scope, kernel derekross#107) and C-24 (BNEP in a lynx-only fragment, derekross#98). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The matrix re-read against what merged and ran on hardware since 2026-11-02: - Pixel 7: Bluetooth and the torch move to testing (kernel derekross#196, derekross#197, derekross#426); fingerprint moves to WIP (kernel derekross#207; the package side, derekross#458, is in review); AVB footers and reboot=warm noted. - Pixel 8a: a new row, from first light and UFS behind the guard (kernel derekross#192, derekross#206; derekross#414). - Pixel 6 Pro: GPU scaling and cooling (kernel derekross#189) and UFS suspend (kernel derekross#188) merged. - Pixel 9a: GPU levels merged through kernel derekross#96; GNSS's moving-car session (derekross#114) and the link driver (kernel derekross#185). - Pixel 7a: Bluetooth's device tree merged (kernel derekross#98). The Pixel 8 Pro's row is left to derekross#472. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
14c97c3 to
e8f9f40
Compare
|
Thanks, @derekross. Both are in, head
The two questions:
Noted on the |
|
Thank you, @FlorencioJP. Both points are in, and well done: the 11-12 boot is in NOTES with the local kernel, the package built on the phone, your own module package with its address service masked and the two timings, and the cell says "booted on the phone with a local kernel build". Thank you also for chasing the firmware: Main has moved under the branch again (#751's Wi-Fi result landed in the same lines), so it needs one more rebase. Here is what to keep in each conflict:
NOTES, the package and the kernel config merge by themselves. Please take 0.2.6: #438 has merged first as 0.2.5 (it was ready and is inert on the published kernel), and it changed the same "install stages…" When you next build the package on the phone from the rebased branch, one line would be good to have: Once CI is green on the rebased head I'll merge. |
Userspace side of linux-omarchy-mobile#98: the Pixel 7a's WCN6855 BT core works on the APM USI1 UART, powered by its qcom,wcn6855-pmu node. - kernel/configs/omamobile.config: CONFIG_BT_BNEP with its two filters, for PAN tethering. It can't affect another phone, so it sits next to the Bluetooth lines rather than in a lynx fragment the release kernel never reads. hci_qca, btqca and pwrseq-qcom-wcn already come from defconfig (checked with merge_config on defconfig plus this fragment). - packages/omamobile-device-lynx 0.2.6: omamobile-bt-addr sets the address the bootloader publishes in /chosen/config/bt_addr when udev sees the controller, through omamobile-bt-addr@.service as on cheetah. Its own script: the WCN6855 is unconfigured until the address is set, so it answers neither `btmgmt info` nor a power cycle; the script retries `btmgmt public-addr` while the index is not yet registered after a rebind. The package depends on linux-firmware-atheros, which holds the chip's firmware files and is not in the image otherwise. - device/lynx/NOTES.md: the 2026-10-29 Bluetooth entry, with the PMU boot evidence (sequencer held by hci_uart, the buck's users, both pins, the drop on unbind), the module order, the rebind race, and the gph2-5 bench note for Wi-Fi work, and the 2026-11-12 boot asked for at review (local kernel build, package built on the phone, the two timings); two stale sentences in the Wi-Fi entries fixed, and the same BT_EN line in WIFI-PLAN.md. - docs/DEVICES.md: Bluetooth testing on lynx (scans with its own address; the kernel side is merged and published; booted on the phone with a local kernel build; pairing untested). Assisted-by: LLM Signed-off-by: Jean-Paul Florencio <jpflorencio@version-tracker.app>
e8f9f40 to
41321a7
Compare
|
Rebased onto main (17f9a3c), head 41321a7, version 0.2.6. Resolved as you listed: DEVICES.md keeps main's Wi-Fi cell and Wanted clause with only the Bluetooth cell and clause from this PR, WIFI-PLAN.md takes main's power-pins line, and test/all keeps #438's display-gate checks next to the three bt-addr checks under one pass line that names both. Policy and Tests are green on this head. The |
Userspace side of linux-omarchy-mobile#98 (merged 2026-11-03): the Pixel 7a's WCN6855 BT core works over the APM USI1 UART, powered by its
qcom,wcn6855-pmunode. One commit on today'smain.kernel/configs/omamobile.config:CONFIG_BT_BNEPwith its two filters, for PAN tethering, next to the Bluetooth lines (it can't affect another phone).hci_qca,btqcaandpwrseq-qcom-wcnalready come from defconfig:merge_configof defconfig plus this fragment givesCONFIG_BT_HCIUART_QCA=y,CONFIG_BT_QCA=m,CONFIG_POWER_SEQUENCING_QCOM_WCN=m, so nothing else to add.packages/omamobile-device-lynx0.2.3 (0.2.2 is Release channels, release-key signing and the bundle manifest (decisions 4, 9, 12) #313's):omamobile-bt-addrsets the address the bootloader publishes in/chosen/config/bt_addrwhen udev sees the controller (DRIVERS=="hci_uart_qca"), throughomamobile-bt-addr@.serviceas on cheetah. Its own script: the WCN6855 is unconfigured until the address is set, so it answers neitherbtmgmt infonor a power cycle; the script retriesbtmgmt public-addrwhile the index is not registered yet after a rebind.test/allpasses in the ALARM container.device/lynx/NOTES.md: the 2026-10-29 Bluetooth entry with the PMU boot evidence, the module order, the rebind race and thegph2-5bench note for Wi-Fi work.docs/DEVICES.md: Bluetooth testing on lynx (scans with its own address; kernel device-lynx: Bluetooth on the APM UART #98 is merged butkernel-2026.11.01predates it; this package's address service has not run on the phone yet; pairing untested).The address logic is the one that has run on the test phone since the 29th (from a local package); this package's copy of it is not yet installed there. Context: #36.
https://claude.ai/code/session_014epmuRTsr4rKgN3czrBeke