NC700 turn off and on uncontrollably

Around On Ear Headphones
1

Bose product name

NC700 headphones

 

Country

Finland 

 

Firmware Version

 

App Version

1.8.2 (latest as of writing)

 

What devices were you using that were affected and what version are they on (Pixel 4a, Lenovo Windows laptop, LG smart TV)

 

Detailed description of the issue and steps to reproduce

I updated the headphones to the latest version a few days ago. Afterwards, they just keep turning off and on by themselves, uncontrollably. Each on-off cycle lasts for about 30 seconds on average, but sometimes several minutes. Sometimes, during such a longer cycle, it's possible to turn off the headphones, but the problem resumes once you turn them on again. Most of the time the power button doesn't work at all anymore. I tried the reset suggested on your webpage, several times, but that didn't change anything. The headphones are now unusable. Did the update somehow corrupt them? Any way to return to an earlier version of the app?

 

 

 

When did you start to experience the issue? Did it work correctly previously?

a few days ago, and yes, they worked correctly before. I bought the pair about a year ago and had not updated them since.

 

Any troubleshooting steps you took

tried reseting the headphones, but that didn't work.

 

2

Hey , welcome to the Bose Community!

 

I am sorry that you're experiencing a power issue with your Noise Cancelling Headphones 700. I'll do all I can to help resolve this with you.

 

It's great that you've researched and performed the reset process. Next, it would be great if you could go to btu.bose.com to manually ensure that the update has successfully been installed. You'll need to connect your headphones to your computer via the USB cable.

 

Let me know how you get on with this.

3

 

Have you got the UE Boom app installed on your phone? This is known by the community to cause issues with connection and rebooting loop as you have described. Not sure why the mods aren't suggesting this as a possible solution... It has been extensively discussed on other posts.

4

 @This was it! Instant fix! Thank you