You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
IDF version.
master
Espressif SoC revision.
ESP32-WROOM
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
Custom Board
Power Supply used.
USB
What is the expected behavior?
When the sniff/unsniff commands are sent (Host device is a Nintendo Switch here), the HID/ACL connections are severed.
What is the actual behavior?
Simply disabling the btm_pm_proc_mode_change function by performing an early return causes this issue to go away.
I'm not sure if there's a custom HCI command that is being misinterpreted as sniff/unsniff, but these are common commands and it seems like something is not right here with how the commands are being handled.
Steps to reproduce.
I'm not sure if there will be a simple way to reproduce this. I'm open to ideas, if there's another setup where we can test the sniff/unsniff commands in the context of a Bluetooth HID device.
Debug Logs.
More Information.
No response
The text was updated successfully, but these errors were encountered:
Answers checklist.
IDF version.
master
Espressif SoC revision.
ESP32-WROOM
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
None
Development Kit.
Custom Board
Power Supply used.
USB
What is the expected behavior?
When the sniff/unsniff commands are sent (Host device is a Nintendo Switch here), the HID/ACL connections are severed.
What is the actual behavior?
Simply disabling the btm_pm_proc_mode_change function by performing an early return causes this issue to go away.
I'm not sure if there's a custom HCI command that is being misinterpreted as sniff/unsniff, but these are common commands and it seems like something is not right here with how the commands are being handled.
Steps to reproduce.
I'm not sure if there will be a simple way to reproduce this. I'm open to ideas, if there's another setup where we can test the sniff/unsniff commands in the context of a Bluetooth HID device.
Debug Logs.
More Information.
No response
The text was updated successfully, but these errors were encountered: