3 ms·

Do you have anything custom installed visible with kextstat | grep -v com.apple ? the only times (within Apple engineering) that our team saw symptoms like t

Do 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 ago
Didn’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 ago
  can't answer that, but am curious to see the output of "kextstat | grep -v com.apple"
behnamoh 4y ago
Running 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 ago
  can you please cut-and-paste exactly what you ran with the prompt visible on the left? that's curious
  - behnamoh 4y ago
    This 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 ago
      yeah that seems normal. seems buggy, like you said! thanks for testing what we could test this way.
- deleted 4y ago
  [deleted]
- jjtheblunt 4y ago
  the 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 ago
    Thanks 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.

Klonoar 4y ago

Didn’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 ago
can't answer that, but am curious to see the output of "kextstat | grep -v com.apple"

behnamoh 4y ago

Running 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 ago
can you please cut-and-paste exactly what you ran with the prompt visible on the left? that's curious
- behnamoh 4y ago
  This 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 ago
    yeah that seems normal. seems buggy, like you said! thanks for testing what we could test this way.
deleted 4y ago
[deleted]
jjtheblunt 4y ago
the 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 ago
  Thanks 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.