4 ms·
Why a cross post of FUD from reddit? I read the post, use incessantly M1 and M2 machines, with various OSes even, and NEVER have the discussed issue in the pos
by jjtheblunt 4y ago
Why a cross post of FUD from reddit?
I read the post, use incessantly M1 and M2 machines, with various OSes even, and NEVER have the discussed issue in the post.
Perhaps I've got good luck, but it's way more likely that the posting person has something screwy installed as a kernel driver, if things are working wonkily on the person's machine.
- behnamoh 4y agoMany people have been reporting BlueTooth issues on their Macs. I personally have the same problem. But just because you don't experience it doesn't mean the issue doesn't exist for many others.
- jjtheblunt 4y agoDo you have anything custom installed visible with kextstat | grep -v com.apple ? the only times (within Apple engineering) that our team saw symptoms like that would turn out to be 3rd party software. could be hardware, of course. thanks for clarifying.
- Klonoar 4y agoDidn’t Apple rewrite the Bluetooth stack in Monterey? That’s where a slew of issues started popping up for people. Connecting to a device with a code is still completely broken.
- jjtheblunt 4y agocan't answer that, but am curious to see the output of "kextstat | grep -v com.apple"
- behnamoh 4y agoRunning that command returns nothing: ``` Executing: /usr/bin/kmutil showloaded No variant specified, falling back to release Index Refs Address Size Wired Name (Version) UUID <Linked Against> ```
- jjtheblunt 4y agocan you please cut-and-paste exactly what you ran with the prompt visible on the left? that's curious
- behnamoh 4y agoThis is the command I ran: kextstat | grep -v com.apple w/o variations (-v), I see a whole list of com.apple items.
- jjtheblunt 4y agoyeah that seems normal. seems buggy, like you said! thanks for testing what we could test this way.
- deleted 4y ago[deleted]
- jjtheblunt 4y agothe output you show looks right since the drivers with com.apple in their name were filtered out, and nothing (except the top labeling of output) remains. this article you probably saw (and, agreeing with you, it seems crazy like you're hitting a bug) https://support.logi.com/hc/en-us/articles/360023195654-Resolve-Bluetooth-Wireless-issues-on-macOS https://support.logi.com/hc/en-us/articles/360023195654-Reso...
- behnamoh 4y agoThanks for the link. I'll check it out. In the past, I've tried some of the techniques mentioned in the article. Sometimes BT issues go away but come back after a few hours... It'd be nice if we could use magic trackpad 3 using USB. I tried connecting the USB cable to it but it seems like it still randomly uses BT because the USB cable only improves the issues to some extent.
- volkk 4y agoi have this issue with my logitech mx master 3s. horrible lag on bluetooth, completely resolved with the dongle. there's definitely something worth fixing here.
- jjtheblunt 4y agoDid your logitech mx master install a kext? kextstat | grep -v com.apple shouldn't show any third party things installed. If it does, that's very very likely what's wrong. (Disclaimer: was in Apple engineering for several years)
- behnamoh 4y agoThere's definitely some interference between BlueTooth and Wi-Fi going on and it's not specific to the new Macs. I experienced similar issues with my 2015 MBP when using BT mice. Switching to Logitech's dongle would completely solve the problem.
- crimsontech 4y agoYeah I remember having this on my 2015 mbp too, it was infuriating and I ended up switching to a wired mouse and keyboard at the time.
- behnamoh 4y agoBest decision ever! I remember at the same time, my Lenovo T490s didn't have any BT issues with my mouse.
- indemnity 4y agoI never install anything but a vanilla macOS, and don’t have any kexts. Been like this for years. I guess now we know why it’s not fixed if this is the Apple engineering mindset.
- jjtheblunt 4y ago
- caycep 4y agoMy experience as well, really no issues, albeit I recall John Siracusa mentioning that the last couple of OS X releases have been rolling out a new driver model where they are no longer kernel modules or something, and some growing pains were to be expected