![]() If I choose to use A mode (Stereo) as output and use the laptop's Realtek Microphone Array as input, then the audio I hear is OK. ![]() If I select both input and output as B mode ("Hands-Free AG Audio") then audio quality is terrible beyond expectations: other OS' play mono audio with low quality, but this Windows 10 displays something totally distorted and incomprehensible, so while I normally like to use the headset in that mode during meetings so people can hear me clearly even if I don't hear them as well, but it looks like that will be an option for now. In my new laptop, however, Windows 10 decides to recognize both modes, but allows you to set incoherent states, such as selecting HD Stereo audio output at the same time as trying to grab the headset's microphone input: In my old laptop's Windows 10 (Enterprise 64bit, not updated to 20H2) the B mode isn't even recognized by Windows (Linux does pick it up, so it's not a hardware incompatibility issue) but A mode works great. In Linux there's a clear cut between the two modes, and you can't fall in mistakenly ambiguous modes like trying to use the microphone while being in stereo mode. The headphones I'm using (Sennheiser HD 405BTNC) work flawlessly with any and all devices I've tried them on, but here's the catch: this headset can be operated in one of two modes at a time: a) one-directional HD stereo audio listening only, or b) bi-directional "hands-free" mode, listening to only low-quality and mono audio, but enabling the included microphone. Now, the main culprit here I think is windows choice of mishandling APTX (or AD2P) high-quality audio and the mono-headset mode. It's up to date with Version 20H2 v19042.630 (except for the optional "2020-11 Cumulative Update Preview for Windows 10 Version 20H2 for 圆4-based Systems (KB4586853)").ĭrivers, including Bluetooth are updated. I'm using Windows 10 Home 64-bit that came pre-installed. Now, before I blame the laptop (and try something radical like a BIOS firmware update) I want to rule out everything else. Particularly, Bluetooth Audio seems to be a mess! ![]() Long story short: I've treated myself to an "ASUS TUF506IV-AS76 TUF A15 Gaming Laptop", but I'm bumping into some issues as I've started using it. This needs to be tested.Hi, and thank you for following me on this journey trying not to pull my hair from my head as I try to enjoy music on my new laptop. For example if I do mute from phone and then press HF device buttons to un-mute, we never know if the HFP device will try to understand that user action as mute or un-mute. What happens when you mute the mic from phone? Does the phone sends +VGM:0 to HF device?Īre you planning to support such behavior where user mute from phone and un-mute from HF device? - I see potential issues here as unless the HF (mute/unmute) state is synchronized with AG. Unless you do this the MIC on HFP device is still mute. In such case are you sending +VGM command from phone to HFP device and with what value +VGM:?. Of course we can assume that minimum mic gain = mute but it needs to be tested with few HF devices to ensure that the solution is interoperable.Īssuming that our assumption is right and VM=0 means MUTE, you can display the mute icon on the GUI.īut do you want user to then unmute from UI? We never know, if I see mute icon, I may go and unmute from phone as it is easier compared to pressing some combinations of buttons on HF device. Spec does not say that AT+VGM=0 is MUTE and mentions that “0” means minimum mic gain. Hence when you enable mute from HF, you must unmute from HF. As AG+VGM=0 does not mean any thing to AG, it cannot assume that mute is enabled by HF. So how does HF device implement the mute feature? When user enables mute during a call from HF device (by pressing some key/s on the HF device), the HF device simply cuts the mic input (typically setting the mic gain to zero), and only silence goes to the AG and then to the remote device. : 0 -15, entered as integer values, whereĠ = Minimum gain This command does not change the microphone gain of the AG it simply indicates the current value of the microphone gain in the HF device. ![]() is a decimal numeric constant, relating to a particular (implementation dependent) volume level controlled by the HF device. This command is issued by the HF device to report its current microphone gain level setting to the AG (phone). Please find the description of AT+VGM command as per the HFP specification. The HFP profile does not support MUTE feature.
0 Comments
Leave a Reply. |