Was this article helpful?
Microphone does not pick up sound | Custom QuietComfort® 35 wireless headphones II
Be sure your product is within 33 feet (10 meters) of the Bluetooth device.
This range can be reduced by obstacles (e.g. walls, doors, appliances, wireless devices, etc.). Try moving the device and product closer together.
Be sure the headphones are connected to a Bluetooth device using the headset profile (HSP).
If the headphones are only connected to a device using the Bluetooth stereo audio profile (A2DP), microphone functionality will not be enabled. This will prevent the user from hearing themselves.
In the settings menu of the connected device, be sure the headset profile is enabled. Once enabled, unpairing, re-pairing and reconnecting the headphones to the device may be needed.
In the settings menu of the connected device, be sure the headset profile is enabled. Once enabled, unpairing, re-pairing and reconnecting the headphones to the device may be needed.
If more than one device is connected to the headphones, try turning off the other device.
The Bluetooth headset profile (HSP) may be enabled in both devices but one device may not allow the other to operate properly for in-call audio.
Be sure the phone is not muted.
Check the phone to see if the mute functionality has been enabled. The phone and the headset each have the ability to mute a call. Check for a visual representation of the muting aspect for the phone. For more information, see Muting your product.
Check for and install any available product updates
Regardless of the issue you are experiencing with your product, try updating it. Visit btu.Bose.com and follow the instructions to ensure your product has the latest features and enhancements.
Reset your product.
Much like rebooting a smartphone, your product might need to be reset on occasion to correct minor issues. For more information, see Resetting your product.
Try connecting a different Bluetooth device.
If your Bose product can connect to another device, Bluetooth functionality is working. In cases like this, the issue could be with the first device or its settings.