4th Gen 2020 M1 Mac mini bluetooth issues with Magic Mouse2

I am right there. Apple Bluetooth engineering and Apple Care contacted me several weeks ago but their lack of response either publicly or with a software update has me concerned that it is a hardware issue.

Disclaimer: I am not an engineer. But I have wondered whether this has to do with the new 802.11ax Wi-Fi 6 interfering with the Bluetooth. While Apple added this new feature, I wonder if it was tested enough or if they just assumed everything would be 'ok' since they were minimizing hardware changes with the M1 chip. It would seem that this may be possible since many users have reported at least an improvement with turning off Wi-Fi. Just a thought.

When my BT mouse disconnects, I see the following messages in the system console Log Reports

The wifi.log had these entries exactly when my mouse dropped

Note that I have my wifi off while this happens

Thu Dec 17 21:47:55.609 BTC: <airport[242]> BluetoothCoexStatusMonitoringCallback: Bluetooth Status Notification

Thu Dec 17 21:47:55.614 BTC: <airport[242]> BluetoothCoexStatusNotificationProcess: BT: ON, Num HID Devices is <1>, Num SCO Devices is <0>, Num A2DP Devices is <0>, Bluetooth Bandwidth Utilization is <14>, LWM <5>, HWM <26>

Thu Dec 17 21:47:55.615 BTC: <airport[242]> __BluetoothCoexHandleUpdateForNode: <en1> node not powered on, do not perform btcoex: radio / UI power state = OFF / OFF

Thu Dec 17 21:47:55.905 BTC: <airport[242]> BluetoothCoexStatusMonitoringCallback: Bluetooth Status Notification

Thu Dec 17 21:47:55.910 BTC: <airport[242]> BluetoothCoexStatusNotificationProcess: BT: ON, Num HID Devices is <2>, Num SCO Devices is <0>, Num A2DP Devices is <0>, Bluetooth Bandwidth Utilization is <36>, LWM <5>, HWM <26>

Thu Dec 17 21:47:55.910 BTC: <airport[242]> __BluetoothCoexHandleUpdateForNode: <en1> node not powered on, do not perform btcoex: radio / UI power state = OFF / OFF

Day 15 of AppleMac Bluetoothgate saga. Turning off WiFi on the Mac has 'solved' the issue. Of course I now cannot use WiFi, Airdrop, Apple Watch (auto unlock) and probably a host of other things....but at least I can use. It's been 2 days now since turning off WiFi and no Magic Mouse or keyboard dropouts, no matter what BT device I use with it or near it.

i never thought it ...

faced the same problems, at least i could work just with wifi off.

After any apple support sessions, sys log capture, try and error, i removed the my USB-C usb .... and all problems are gone. Fortunately, i have a LG Ultrafine monitor with a full functionally USB-C hub on the back. I have to give up the fast charging for my iPad (missing a additional USB-C) and a have big cable ball behind the monitor, but i can work.

I never thought about interferences - strange.

Those files aren't in my preferences folder. I have the Magic Mouse 2 and magic keyboard. Both new with Mac mini purchase. I haven't had a mouse problem in quite some time now but did have my keyboard disconnect when my iPhone that is near the computer started ringing though it may have been a coincidence. Plugged in a lightening cable and then it re-connected. The first issue I have had in a while.

Apple Support had me delete those two files yesterday in preparation for getting bumped to a Senior Engineer. I see them (recreated after the restart) in my ~User/Library/Preferences folder. Since I deleted them 24 hours ago I haven't had a problem. But my issue was not nearly as frequent as people here are reporting. I too have Magic Mouse 2 and Magic Keyboard (also Magic Trackpad). Even when the mouse did get laggy and disconnect, I could fix it by turning off/on the mouse, or by toggling it off/on in Bluetooth preferences (using the Trackpad for cursor control).

in this case, the mouse was never recognized. I faced that while migrating my old iMac to the new M1 too.

The particular system need to know the bluetooth device to realize the system wake up function (tapping on mouse to wake up, the system needs to know mac address, profile etc. of the device, who has permission to do that) With a fresh system, the mac does not know the magic mouse. By delivering the mouse, you got a charging cable (lighting / USB cable). connect the mouse with this cable and the mouse will be recognized. The same with the keyboard. After disconnecting the cable, the bluetooth should come up for the mouse.

Then, you should face files like "com.apple.Bluetooth.plist" under "/Library/Preferences/".

I think, this is a bug. The older macOS system had some kind of search function, in the case off missing keyboard. You could connect each bluetooth device, who had a keyboard profile. On Big Sur they have waived that, maybe to security reasons.

I think the bleutooth poblems will come because of sleep mode. My M1 mac mini only gets problems after the sleep mode has been on for a really long time. I think apple should check this. After I have checked (turned on) the "prevent computer from automatically hibernation" in settings power saving. I had no more problems until now.

exactly the same i had...

in my case i bought a USB-C hub from sitcom, because i have 4 USB devices and one Thunderbolt device. I put the thunderbolt monitor on the first port and the USB-C hub on the second port. Facing mouse & keyboard lags etc. Switching off Wifi and all things are good.

Then, i installed the 11.1. update, hoped the problem is solved. Switching on Wifi and this action killed the whole bluetooth connections.

My monitor (LG Ultrafine) have 4 full working USB-C ports on the back. I used the additional sitcom USB-C hub, because i hate cable balls on my desk. After all that connection problems, for testing, i removed the sitcom USB-C hub and connected my USB devices directly to the LG monitor.

Since then, i have stable connections, Wifi and Bluetooth.

In my mind, all that problems have their cause in interferencies, maybe bad sitcom USB-C hub.

Next interesting fact:

The LG Ultrafine Monitor comes with a Thunderbolt cable. This cable is rolled up with clamps, like a coil in the packaging. I thought that was just to look pretty. I removed the clamps, tied all the cables (Thunderbolt and USB-C) together and attached them behind the monitor. After that, i faced some monitor problems. The image suddenly became brighter, then darker, then brighter again. I took the clamps, rolled the Thunderbolt cable back up to the "coil", tied the USB-C cable separately. Since that, all things ok.

If i think about it, USB-A or B had 450 Mbit/s transfer rate, USB-C 5 Gbit/s and Thunderbolt (a subset of USB-C) up to 40 Gbit/s. That is the range of Gigabit Ethernets. From telecommunication system i know, that "cross talking", means interference between two wires in a cable, is a typical problem.

All that stuff leads me to interference problem as the root cause.

Well my saga continues. I am expecting to work with AppleCare tomorrow morning but am still attempting to diagnose myself. Hopefully I do not end up sending this back for a refund.

My current setup:

No USB-A ports used

No USB-C ports used

No external speakers

4k certified HDMI cable connected to my LG 24UD58-B monitor.

Apple Magic Mouse 2

Apple Magic Numeric Keyboard

Apple Trackpad 2

Wifi to 5Ghz Lan Ch.36

Mouse dropped and reconnected this morning at 8.11.06. Keyboard and Trackpad stayed connected

Following entries in the system.log and wifi.log at the same time

System log

Dec 19 08:11:06 Georges-Mini fud[3337]: objc[3337]: Class AMSupportURLConnectionDelegate is implemented in both /usr/lib/libamsupport.dylib and /System/Library/PrivateFrameworks/MobileAccessoryUpdater.framework/Support/fud. One of the two will be used. Which one is undefined.

Dec 19 08:11:06 Georges-Mini fud[3337]: objc[3337]: Class AMSupportURLSession is implemented in both /usr/lib/libamsupport.dylib and /System/Library/PrivateFrameworks/MobileAccessoryUpdater.framework/Support/fud. One of the two will be used. Which one is undefined.

Dec 19 08:11:06 Georges-Mini syslogd[71]: ASL Sender Statistics

Wifi Log - much longer entries starting with Bluetooth messages

Sat Dec 19 08:11:06.306 BTC: <airport[259]> BluetoothCoexStatusMonitoringCallback: Bluetooth Status Notification

Sat Dec 19 08:11:06.307 BTC: <airport[259]> BluetoothCoexStatusNotificationProcess: BT: ON, Num HID Devices is <2>, Num SCO Devices is <0>, Num A2DP Devices is <0>, Bluetooth Bandwidth Utilization is <36>, LWM <5>, HWM <26>

Sat Dec 19 08:11:06.307 BTC: <airport[259]> __BluetoothCoexHandleUpdateForNode: <en1> Handle Bluetooth Coex: FrequencyBand <2>, Bluetooth Bandwidth Utilization <36>, Clamshell Mode <0>

Sat Dec 19 08:11:06.307 BTC: <airport[259]> __BluetoothCoexHandleUpdateForNode: Driver supports APPLE80211_CAP_COEX_PROFILE_OFFLOAD. Airportd won't BluetoothCoexModeSet() and defer coex profile loading to UDM coex manager (UCM/WRM) ...

Sat Dec 19 08:11:06.764 BTC: <airport[259]> BluetoothCoexStatusMonitoringCallback: Bluetooth Status Notification

Sat Dec 19 08:11:06.764 BTC: <airport[259]> BluetoothCoexStatusNotificationProcess: BT: ON, Num HID Devices is <3>, Num SCO Devices is <0>, Num A2DP Devices is <0>, Bluetooth Bandwidth Utilization is <59>, LWM <5>, HWM <26>

Sat Dec 19 08:11:06.764 BTC: <airport[259]> __BluetoothCoexHandleUpdateForNode: <en1> Handle Bluetooth Coex: FrequencyBand <2>, Bluetooth Bandwidth Utilization <59>, Clamshell Mode <0>

Sat Dec 19 08:11:06.764 BTC: <airport[259]> __BluetoothCoexHandleUpdateForNode: Driver supports APPLE80211_CAP_COEX_PROFILE_OFFLOAD. Airportd won't BluetoothCoexModeSet() and defer coex profile loading to UDM coex manager (UCM/WRM) ...

Sat Dec 19 08:11:14.432 BTC: <airport[259]> BluetoothCoexStatusMonitoringCallback: Bluetooth Status Notification

Sat Dec 19 08:11:14.433 BTC: <airport[259]> BluetoothCoexStatusNotificationProcess: BT: ON, Num HID Devices is <2>, Num SCO Devices is <0>, Num A2DP Devices is <0>, Bluetooth Bandwidth Utilization is <36>, LWM <5>, HWM <26>

Sat Dec 19 08:11:14.433 BTC: <airport[259]> __BluetoothCoexHandleUpdateForNode: <en1> Handle Bluetooth Coex: FrequencyBand <2>, Bluetooth Bandwidth Utilization <36>, Clamshell Mode <0>

Sat Dec 19 08:11:14.433 BTC: <airport[259]> __BluetoothCoexHandleUpdateForNode: Driver supports APPLE80211_CAP_COEX_PROFILE_OFFLOAD. Airportd won't BluetoothCoexModeSet() and defer coex profile loading to UDM coex manager (UCM/WRM) ...

Sat Dec 19 08:11:14.610 BTC: <airport[259]> BluetoothCoexStatusMonitoringCallback: Bluetooth Status Notification

Sat Dec 19 08:11:14.610 BTC: <airport[259]> BluetoothCoexStatusNotificationProcess: BT: ON, Num HID Devices is <3>, Num SCO Devices is <0>, Num A2DP Devices is <0>, Bluetooth Bandwidth Utilization is <59>, LWM <5>, HWM <26>

Sat Dec 19 08:11:14.610 BTC: <airport[259]> __BluetoothCoexHandleUpdateForNode: <en1> Handle Bluetooth Coex: FrequencyBand <2>, Bluetooth Bandwidth Utilization <59>, Clamshell Mode <0>

Sat Dec 19 08:11:14.610 BTC: <airport[259]> __BluetoothCoexHandleUpdateForNode: Driver supports APPLE80211_CAP_COEX_PROFILE_OFFLOAD. Airportd won't BluetoothCoexModeSet() and defer coex profile loading to UDM coex manager (UCM/WRM) ...

I deleted the two plist files mentioned above and restarted my Mac Mini last night. I just worked for about 4 straight hours and my Magic Mouse did not disconnect once. The original files were from November. I created screen shots of them in Text Edit and looked at the recreated files, after the restart, and I saw no difference in the text. After you delete the files, you will need to go back to System Preferences and put the Mouse settings back to where you had them.

Thank you, so far, Sherman Wilcox.

barjohng,

I'm planning to purchase the Apple/LG 27" and would like your opinion on this monitor? My mac mini 16GB 1TB drive will deliver 01/15/21. I'm eyeing this thread and hope there is a fix. If not, I will cancel the order before it ships. I will not buy the monitor either which will be my last purchase.

I sent my late 2015 iMac i7 back to Phobio d/t hardware issues and they gave me full trade-in price. I will never buy an "All-in-One" again. My personal time is sacred and I am getting to the point where I will not waste my time on stuff like problem-solving Bluetooth, wifi, or anything like that. I liked my 5K on my iMac and wanted to retain that. Thanks for the feedback! Let's hope Apple gets their act together. If not, I'll use my DELL XPS i7, until they figure it out.

This is definitely one of those strange issues that will be hard to solve because each environment where it happens and how it happens seems to be different. I had the issue at first shortly after this thread started and since about a week ago I haven't had a mouse disconnect after trying several suggestions here for over a week, though I don't have the two .pst files discussed earlier.