Hey I might be wrong on this one, but to me it looks like NC_ASM_EFFECT::OFF should be used to turn off the ambient sound control. This turns it off for me, on a WH-1000XM3.

Just tested here and turns off on a XM4 too. That's weird; both approaches turns it off (independently or combined).

Taking another look at bluetooth messages between my phone and xm4, apparently both informations are sent (NC_ASM_EFFECT::OFF and vol=-1)
Guess I'll add the missing one to this PR.

I have updated the macOS version to have the same functionality.
Compiled version

@guilhermealbm which method did you use to fetch the messages between your phone and the headset? Did you hook the relevant function using Frida or something? I didn't manage to get it to work using the sniffer Android provides. I'll probably merge this this weekend, BTW.

Hi @Plutoberth! I started trying logging with Bluetooth HCI Snoop and analyzing it with Wireshark, but was extremely confusing. So, I discovered that my device has a logkit.

It generates a really big file, but I filtered by my XM4's MAC and found the event logs;
For example, when I toggle the "Ambient Sound Control" button, it records:

03-08 23:00:17:503 handleBluetoothA2dpActiveDeviceChangeExt  state=2 addr=[...] prof=2 supprNoisy=true vol=18
03-08 23:00:17:504 setBluetoothA2dpDeviceConnectionStateSuppressNoisyIntent  state=2 addr=[...] prof=2 supprNoisy=true vol=18
03-08 23:00:17:506 A2DP sink connected: device addr=[...] state=2 vol=18
03-08 23:00:20:405 handleBluetoothA2dpActiveDeviceChangeExt  state=0 addr=[...] prof=2 supprNoisy=false vol=-1
03-08 23:00:20:405 setBluetoothA2dpDeviceConnectionStateSuppressNoisyIntent  state=0 addr=[...] prof=2 supprNoisy=false vol=-1

I ommited my mac addr, but, in general, that's it! 😃

Hi @Plutoberth! I started trying logging with Bluetooth HCI Snoop and analyzing it with Wireshark, but was extremely confusing. So, I discovered that my device has a logkit.

It generates a really big file, but I filtered by my XM4's MAC and found the event logs;
For example, when I toggle the "Ambient Sound Control" button, it records:

03-08 23:00:17:503 handleBluetoothA2dpActiveDeviceChangeExt  state=2 addr=[...] prof=2 supprNoisy=true vol=18
03-08 23:00:17:504 setBluetoothA2dpDeviceConnectionStateSuppressNoisyIntent  state=2 addr=[...] prof=2 supprNoisy=true vol=18
03-08 23:00:17:506 A2DP sink connected: device addr=[...] state=2 vol=18
03-08 23:00:20:405 handleBluetoothA2dpActiveDeviceChangeExt  state=0 addr=[...] prof=2 supprNoisy=false vol=-1
03-08 23:00:20:405 setBluetoothA2dpDeviceConnectionStateSuppressNoisyIntent  state=0 addr=[...] prof=2 supprNoisy=false vol=-1

I ommited my mac addr, but, in general, that's it! 😃

Wow, so this format is standardized? I was 100% sure it was proprietary. This is really great news for future features. I have a Oneplus too so I'll check this out when I have some time.

Wow, so this format is standardized? I was 100% sure it was proprietary. This is really great news for future features. I have a Oneplus too so I'll check this out when I have some time.

I don't think it's a standardized format. Fortunately, toggling NC button also calls android's handleBluetoothA2dpActiveDeviceChangeExtand setBluetoothA2dpDeviceConnectionStateSuppressNoisyIntent methods, which are recorded by OnePlus logkit. But, for example, alternating between equalizer profiles doesn't generate any record at log file 😕

I was not sure why this happens too, but Galaxy Buds Client explains it very well. To certain features, reverse-engineer the data format is the only alternative.

Hi, looks great, just one small request - could you make it so the text "Focus on voice isn't enabled on this level" isn't shown if ambient sound is disabled?

I really didn't notice that! Just fixed 😄

LGTM, merged :)