macOS 26.7: opening Control Center Sound causes BLE HID mouse lag, HID service loss, and result 307

I am seeing a repeatable interaction between audio activity or audio-device discovery and a Bluetooth LE HID mouse on a Mac mini M2 Pro. Opening the detailed Sound panel in Control Center, or changing the HDMI audio output, makes the pointer stutter. Opening Apple’s Music.app has also caused a temporary complete loss of the mouse. In the worst cases, the mouse becomes completely unavailable and does not recover without Bluetooth troubleshooting or re-pairing.

Configuration

  • Mac mini Mac14,12, Apple M2 Pro, 32 GB RAM
  • macOS Tahoe 26.7 (25G229)
  • Also reproduced on macOS Tahoe 26.1 (25B78)
  • Logitech MX Anywhere 3 Mac over Bluetooth LE
    • VID 0x046D, PID 0xB025
    • Firmware MPM24.01_0015
  • Logitech MX Keys M Mac over Bluetooth LE
  • PL4071UH display and audio output over HDMI
  • Logi Options+ installed

Trigger

  1. Connect the MX Anywhere 3 Mac and MX Keys over Bluetooth.
  2. Open Control Center from the menu bar.
  3. Open the detailed Sound panel, or change the HDMI audio output.
  4. Move the Bluetooth mouse continuously while audio-output discovery is taking place.

The issue is intermittent, but it has been reproduced several times on both macOS 26.1 and 26.7. Pointer stuttering can continue after the Sound panel is closed.

A later incident occurred when I opened Apple’s Music.app. The Bluetooth mouse became unavailable again, but this time it recovered automatically after approximately ten seconds. The Sony WH-1000XM6 headset was connected over Bluetooth, while the 512 GB USB flash drive was not connected. This shows that the USB drive is not required for a temporary mouse loss and makes concurrent Bluetooth audio activity a more relevant condition to investigate. The additional trigger suggests that the problem may not be limited to the Control Center interface itself and may also be associated with audio-subsystem initialization or audio-device activity. This is an observation, not yet a confirmed causal link.

Additional condition in the permanent-loss cases

In every incident where the mouse did not recover on its own and became effectively unusable, the following two devices were also present:

  • a Sony WH-1000XM6 wireless headset connected over Bluetooth;
  • a 512 GB SanDisk USB flash drive connected to the Mac.

I am reporting this as a correlation, not as a confirmed cause. The headset adds simultaneous Bluetooth audio activity. The USB drive may or may not be relevant depending on its USB mode, activity, shielding, physical location, and possible 2.4 GHz interference. The 512 GB capacity is included only to identify the device. Less severe cursor stuttering has also been observed around Sound-panel discovery; the two devices above are specifically the common condition I recorded during the permanent mouse-loss incidents.

Observed result

  • The pointer starts stuttering and raw mouse HID reports develop multi-second gaps.
  • In severe incidents, the Bluetooth mouse stops working entirely.
  • Opening Music.app has also caused a temporary complete loss of the mouse; during that incident the Sony WH-1000XM6 was connected over Bluetooth, the USB flash drive was not connected, and the mouse recovered automatically after approximately ten seconds.
  • Logi Options+ then displays the mouse as inactive.
  • The mouse disappears from the IOHID tree, while the Bluetooth keyboard can remain present.
  • A wired USB mouse remains responsive, so the Mac and pointer rendering are not completely frozen.
  • The failure can persist after the Sound panel is closed.

Relevant logs

On macOS 26.7, bluetoothd repeatedly recorded the following sequence for the MX Anywhere 3 Mac:

MX Anywhere 3 Mac needs low latency
current connection parameters: interval 30.00 ms, latency 0
connection changed to: interval 7.50 ms, latency 44
Device "MX Anywhere 3 Mac" is Incompatible LE HID
Device "MX Anywhere 3 Mac" does not have _HID_SERVICE_
Connection timed out
disconnect result: 307
BLEPaired HIDBadBehavior Central

The sequence repeated during automatic reconnection attempts. The mouse later recovered on some occasions, but other incidents required turning Bluetooth off for about 15 seconds, turning it back on, forgetting the mouse, and pairing it again.

Instrumented reproduction

During a monitored reproduction on macOS 26.1:

  • detailed audio discovery started at +21.333 s;
  • a 2.400 s gap in raw HID reports from the mouse occurred 0.899 s before that event;
  • bluetoothd then reported a HID lag issue for VID 0x046D, PID 0xB025 at +1.897 s;
  • no display-frame gaps were detected;
  • there was no sustained CPU saturation.

This indicates that the interruption is already present in the raw HID input stream. It does not appear to be only a cursor animation or WindowServer rendering delay.

Expected result

Discovering or switching audio outputs should not alter a separate BLE HID mouse connection, cause multi-second HID report gaps, remove _HID_SERVICE_, or disconnect the mouse.

Technical points for investigation

Could this be a macOS Bluetooth/HID connection-parameter or service-discovery problem triggered by concurrent audio discovery? In particular, why does macOS change the mouse from 30 ms / latency 0 to 7.5 ms / latency 44, then classify it as Incompatible LE HID, lose _HID_SERVICE_, and eventually disconnect it with result 307?

Has anyone reproduced the same sequence with a Logitech BLE mouse, a Bluetooth audio headset, or a USB 3 storage device connected?

The issue was also submitted through Apple’s public macOS feedback form on 24 September 2026. That form confirmed receipt but did not provide an FB case number.

Possibly related report

Another Developer Forums report describes a different BLE HID device with Incompatible LE HID and disconnect result 307 on macOS 27. The hardware and trigger are different, but the Bluetooth/HID failure signature may be related:

https://developer.apple.com/forums/thread/845857

you said "The issue was also submitted through Apple’s public macOS feedback form on 24 September 2026. That form confirmed receipt but did not provide an FB case number."

The place to file bug reports is Feedback Assistant (the app), or you can use the web interface at https://feedbackassistant.apple.com

A Sony WH-1000XM6 wireless headset connected over Bluetooth;

Have you ever reproduced the problem without those headphones being involved? The Bluetooth audio specs [1] are both hideously complicated and high bandwidth, maximizing their ability to disrupt other accessories if/when something goes wrong. Note that I'm not necessarily blaming the headphones here— the specs involved are sufficiently complex that the concept of "correct“ [2] becomes a bit suspect.

I'd also suggest turning off and completely unplugging this:

PL4071UH display and audio output over HDMI

I've only seen it a few times, but under the right circumstances, a poorly constructed HDMI cable can generate a remarkable amount of RF interference.

In particular, why does macOS change the mouse from 30 ms / latency 0 to 7.5 ms / latency 44, then classify it as Incompatible LE HID, lose HID_SERVICE, and eventually disconnect it with result 307?

If I had to guess, radio interference broke communication with the mouse, though that’s just a guess.

[1] Yes, there are in fact two different audio specifications (A2DP and HFP), but a "bonus" spec (AVRCP) if you want playback controls to work. Just playback controls, though. If you're on a phone call, HFP handles that.

[2] Defining "correctness" requires determining exactly what "the spec says", something a sufficiently complex specification cluster can turn into a point of spirited debate.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

I ran another series of tests without the Sony Bluetooth headset connected, but with the USB flash drive attached. The cursor lag did indeed disappear when I switched monitors. Good catch.

I also found that the USB flash drive made the lag significantly worse, especially when connected to the outermost USB-A port on the Mac mini.

Test results :

Iiyama monitor, without the Bluetooth headset

I performed several test cycles with three different configurations.

1. Mac mini with no USB drive

There was barely noticeable cursor lag during the first test cycle. I could not reproduce the issue during the subsequent cycles. So, no issue here.

2. SanDisk USB drive connected to the outermost USB-A port

This is the rightmost USB-A port when looking directly at the back of the Mac mini. It is also the port I normally use for this drive.

During the first test cycle:

  • Cursor lag was severe.
  • The mouse stopped responding for approximately 20 seconds, then recovered automatically.
  • The USB drive disconnected by itself and did not reconnect automatically.

The following test cycles were only slightly better, although the USB drive remained connected.

3. SanDisk USB drive connected to the USB-A port closest to the HDMI port

During the first test cycle, I noticed only minor cursor lag while the Sound panel was open. It was not particularly disruptive.

I could not reproduce the issue during the subsequent cycles. It works properly.

ASUS ProArt monitor

I then connected an ASUS ProArt monitor using the same HDMI cable. No headset.

I could not reproduce any cursor lag, even with the USB drive connected to the USB-A port that had caused the most severe problems with the iiyama monitor.

Additional information about the iiyama monitor :

The iiyama monitor already has significant HDMI reliability problems when operating at 4K 60 Hz.

In my experience, neither the Mac mini nor other computers can reliably wake it from standby. I have to power-cycle the monitor before it will detect the video signal from a computer connected to its HDMI 1 input.

.

The place to file bug reports is Feedback Assistant (the app), or you can use the web interface at https://feedbackassistant.apple.com

Thanks, I submitted a report through it shortly after creating this thread. I was not aware of that option when I originally posted.

I then connected an ASUS ProArt monitor using the same HDMI cable. No headset.

What's the resolution of that monitor compared to the iiyama monitor?

While it’s possible the monitor is the issue here, I wouldn't assume that yet. The problem here is that the ongoing evolution of HDMI means that there is ENORMOUS variation between how much data is being transferred over the "same" wire and those difference can mean you need to use a different cable.

The issue here is similar to Thunderbolt over USB-C vs. USB3 over USB-C. Those two protocols may be using the same connector, but the protocols and data volume are completely different and, most importantly, they CANNOT use the same cable. The Thunderbolt cable needs much better shielding; otherwise, things are not going to go well. To its credit, the USB-C specification was designed with these issues in mind, which is how the system is able to differentiate between those two cable types and do the "right" thing.

Unfortunately, HDMI... doesn't really work that way. Some of that is that its specifications are less clear-cut, some of it's caused by a lack of clear naming/marketing about what EXACTLY a given display requires, some of it's issues with individual displays... and a WHOLE lot of it is the vast supply of commodity cables of questionable spec compliance and quality. Oh, also the industry tendency to think that "TV cables should be simple, so let’s pretend that all TVs work fine with the same cable.”

All of that means that the same cable can work fine with one display and terribly with another because what's actually going on is that the first display simply isn't pushing the cable hard enough to "matter.”

Related to that point:

In my experience, neither the Mac mini nor other computers can reliably wake it from standby. I have to power-cycle the monitor before it will detect the video signal from a computer connected to its HDMI 1 input.

This could be the cable or it could be the monitor. HDMI has a separate spec ("CEC") that allows devices to control displays, but most "monitors" don't support it. Many monitors have their own logic to wake up when they receive HDMI activity, but support is inconsistent and cables can break it. So a new HDMI cable might fix everything... or not.

However, assuming I've correctly identified your display, the other option would be to get a USB-C to DisplayPort (full, not mini) cable and use that instead. That should solve any wake issue and there's a decent chance it will solve the interference issue as well.

Thanks, I submitted a report through it shortly after creating this thread.

Bug number? Look for a number with the format FB<8 digits>.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

FB24927304.

Asus ProArt Display PA278CV : 2560x1440p, 60 fps.

I tested the same HDMI cable with the Iiyama monitor’s other two HDMI inputs, which are limited to 4K at 30 Hz, and encountered the same cursor lag.

I do not have another HDMI cable on hand to test at the moment.

In addition to testing an HDMI-to-DisplayPort adapter, I plan to buy the shortest practical male-to-male HDMI cable I can find. I’d appreciate any recommendations for models that are readily available in Europe.

In addition to testing an HDMI-to-DisplayPort adapter

I'd actually suggest USB-C/Thunderbolt over HDMI.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

macOS 26.7: opening Control Center Sound causes BLE HID mouse lag, HID service loss, and result 307
 
 
Q