Repository navigation
kernel config: Bluetooth LE mice and keyboards, and headphone buttons - #304
Conversation
|
Thank you, @nesmeck. A BLE mouse that connects but never moves the pointer is exactly the kind of gap people hit on day one, and the before/after log lines make each option's purpose clear. I checked the fragment against the published kernel:
With RFCOMM, PipeWire's Bluetooth backend can offer the headset profile (HSP/HFP). That's the headset microphone you saw. But on the Pixel 7 Pro, headset audio needs the chip's SCO routing moved from PCM to HCI first (the Bluetooth row in Could you try it on your Pixel 7 with the WF-1000XM5?
If the profile switches and the audio dies, I'd move One small thing for the commit message: it cites Thanks again, this makes the phones much more usable with everyday accessories. |
Turn on what bluetoothd needs for common Bluetooth devices, as modules loaded on demand: - UHID: BLE mice and keyboards (HID over GATT) get their input devices through /dev/uhid. Without it bluetoothd logs "input-hog profile accept failed" and a paired BLE mouse never reaches the desktop. - HID_LOGITECH and HID_LOGITECH_HIDPP: Logitech's HID++ devices, such as the MX Master, with their battery and extra buttons. - INPUT_UINPUT: AVRCP, so headphone and speaker buttons (play, pause, volume) become key events. BT_RFCOMM stays off for now. With it, PipeWire offers the headset profile, and WirePlumber switches headphones to it whenever something opens a microphone: on the Pixel 7, music over A2DP cut out and mpv paused when a recording started. It can come with a WirePlumber setting that keeps headsets on A2DP, or with call support. All of it was tested on a Pixel 7 (the Pixel 7 Bluetooth plan, in a later PR): a Logitech MX Master 3 over BLE drove the shell, and a pair of Sony WF-1000XM5 played over A2DP with their play/pause and volume buttons working. Every phone with Bluetooth gets the same modules. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
9d2428a to
379f5e5
Compare
|
Thanks, and good call. I ran your test on the Pixel 7 with the WF-1000XM5, on a kernel with all five options. Your worry holds, so I've moved What happened (the card's active profile logged once a second, with a video playing in mpv):
So on the Pixel 7, SCO audio does seem to reach the headphones, and the microphone records over it. That's different from what you expect on the 7 Pro. But the switch still breaks playback: when something opens a microphone, the music stops and mpv pauses until someone resumes it. The change: 🤖 Generated with Claude Code |
|
Thank you, @nesmeck, that's exactly the test I hoped for, and the table makes the result unambiguous: the switch to the headset profile cuts the music and pauses mpv, so leaving |
… uinput (derekross#304) Turn on what bluetoothd needs for common Bluetooth devices, as modules loaded on demand: - UHID: BLE mice and keyboards (HID over GATT) get their input devices through /dev/uhid. Without it bluetoothd logs "input-hog profile accept failed" and a paired BLE mouse never reaches the desktop. - HID_LOGITECH and HID_LOGITECH_HIDPP: Logitech's HID++ devices, such as the MX Master, with their battery and extra buttons. - INPUT_UINPUT: AVRCP, so headphone and speaker buttons (play, pause, volume) become key events. BT_RFCOMM stays off for now. With it, PipeWire offers the headset profile, and WirePlumber switches headphones to it whenever something opens a microphone: on the Pixel 7, music over A2DP cut out and mpv paused when a recording started. It can come with a WirePlumber setting that keeps headsets on A2DP, or with call support. All of it was tested on a Pixel 7 (the Pixel 7 Bluetooth plan, in a later PR): a Logitech MX Master 3 over BLE drove the shell, and a pair of Sony WF-1000XM5 played over A2DP with their play/pause and volume buttons working. Every phone with Bluetooth gets the same modules. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
What and why
Four kernel options that bluetoothd needs for common Bluetooth devices, all modules loaded on demand:
UHID: BLE mice and keyboards (HID over GATT) get their input devices through/dev/uhid. Without it, bluetoothd logsinput-hog profile accept failed, and a paired BLE mouse connects but never reaches the desktop.HID_LOGITECHandHID_LOGITECH_HIDPP: Logitech's HID++ devices, such as the MX Master, with their battery and extra buttons.INPUT_UINPUT: AVRCP. bluetoothd turns headphone and speaker buttons (play, pause, volume) into key events through uinput. Without it, it logsAVRCP: failed to create uinput.BT_RFCOMMstays off for now. With it, WirePlumber switches headphones to the headset profile whenever something opens a microphone, and on the Pixel 7 that cut the music and paused mpv (the test is in the comments below). It can come later, with a WirePlumber setting that keeps headsets on A2DP, or with call support.None of them is on today, so every phone with Bluetooth gains them.
Device and build
uname -r):7.3.0-rc6-omamobile-push1-gbb6c8a7ff379(a Bluetooth test kernel for the Pixel 7: the board's Bluetooth node on top of what it already runs), rebuilt with these options andBT_RFCOMM, which this PR no longer adds.kernel/configs/omamobile.configonly)Checks (no phone needed)
tools/pr-check upstream/mainpassestests/allpassestests/packagespasses (no package changed)versionbumped (none changed)Co-Authored-By:trailer, never aSigned-off-by:On the phone
device/panther/BLUETOOTH-PLAN.mdBT2, in a later PR):input-hog profile accept failed./dev/uhidexists,uhidandhid_logitech_hidppload, the kernel logs "input: MX Master 3 Mouse as /devices/virtual/misc/uhid/…" and "logitech-hidpp-device …: HID++ 4.5 device connected", and the mouse drives the shell.userdata, weakens the storage guard, or reads registers from userspace.🤖 Generated with Claude Code