So if you believe this has happened to you, there are some quick and easy steps you can take to confirm that the issue isn’t the firmware. Some people claimed they began to sound worse, others claimed that the active noise cancelling wasn’t as effective. There were a few complaints going around a while back that firmware updates were causing some Bose QC 35 II headphones to behave in strange ways. I’m assuming this is one of the benefits you get from working directly with Google and being one of the Made for Google products.Ī firmware update made the Bose QuietComfort 35 II sound worse, how do you fix it? Normally with headphones, you’d have to wait a second or two for it to register and pull up Google on your phone, but with the Bose QuietComfort 35 II it starts listening as soon as you press the button so you’re not left wondering if it worked or not. As soon as you press the button you’ll hear a quick little tone and then you can ask your question or give your command. You can ask your Google Assistant questions through your headphones just like you would if you activated the assistant on your phone, except it’s much quicker. If you choose the Google Assistant, you can toggle having your notifications read aloud into your ear and there is even a dedicated Google help page for the product. After you select your language and pick a nickname you’ll get to the action button setup, which lets you choose between Google Assistant, Amazon Alexa, and an active noise cancellation toggle.

It’s pretty cool, especially since the process is helped along by a small voice egging you along in your ear. When you open the Bose Connect+ app it’ll first try to find the headset, and then ask you to swipe it down to finish pairing. The Bose QuietComfort 35 II looks virtually identical to the first version, just with a few hardware improvements.

Bose qc35 firmware noise cancelling