Noise Cancelling 700 Firmware Update - Buzzing followed by Headphone Reboot

  Return them while you can and get a WH-1000XM4. I'm super regretful that I didn't. Also has LDAC support.

 

To fix it, most have had success going back to 1.3.1 software, myself included. Not allowed to talk about downgrade here, but Google and ye shall find

Hi All,

 

Just got my second pair of NC700's after the first was replaced. Wanted to chime in and say that I'm still having this problem as well.

 

Phone: Pixel 5 on Android 11

Headphone Firmware: 1.8.2-11524 e0f7590

 

I really like these headphones for work and would get them for my whole team, but this issue is inexcusable. Bose, fix your gear.

Hi StefanHSoup.

 

Thank you for your message and welcome to the Community!

 

Sorry that you are having issues with your headphone. I suggest that you try to troubleshoot it by doing the steps from this LINK.

 

Let us know how it went and hope that helps.

 

 

Hi Marvin, I've followed all the troubleshooting steps provided by Bose previously.

 

Surely it wouldn't be hardware issue that requires another replacement, are there any firmware updates scheduled in the pipeline that could resolve this issue?

I still have the same problem with a S20 . I am now on my third headset with firmware 1.8.2. The headset crashes constantly. Tech support guys seem to be completely unaware of the problem and some even dispute that this kind of issue could exist. This is extremely frustrating and I don't understand that nobody at HQ is seeing this issue and is dealing with this issue.

Take a look at the ratings of the app in the Google Play Store, more and more one star ratings. Bose really has a problem with software.

 Please take this issue seriously and  fix the firmware!!

FIXED!!

I fixed mine (at least, no buzzing and reboot for week while it used to happen few times a day) with the following step:

  • Remove Ultimate Ear Boom app
  • Remove all paired Bluetooth devices
  • Restart my phone
  • Remove my phone from the device list on Bose app
  • Do "factory reset" of the headphone (that hold and plug thingy)
  • Pair back Bose.

I haven't paired any new devices to my phone and so far I still don't have an issue.

You can pair back devices and install your Bluetooth controlling apps back one by one and see which one conflict.

Bose, this should be enough to hint you where to look at. Either it was UE Boom was the culprit, or you just don't work well with other Bluetooth apps 

Hi All,

 

Just FYI per the above post - I've uninstalled the 'Ultimate Ears' app for the UE Boom and this appears to have resolved the issue.

 

Not sure what was going on, but relieved nonetheless.

will there be any kind of notification / statement when a fix is released for this issue? Automatic updates over the app don't work (as my headphones won't connect to my phone properly) and checking manually everyday is kind of annoying...

 We will definitely post on the Community if and when there is a fix for rebooting when the firmware conflicts with a a 3rd party application. That said, right now I don't have any information or timelines as to when a release would be made available.

 

You may want to subscribe to this thread (done so under Forum Options above the posts) and that should notify you when there are new posts.

 

Hope this helps!

Alright, so after a few frustrating months and two warranty replacements I seem to have been able to finally fix this issue, and have also been able to fix it for a colleague who was having the exact same issue.

 

From reading all accounts of this issue it only exists when the NC700s are connected to an Android device. This was present when connected to my Pixel 5, and also on my colleagues Samsung S10

It seems for both of us (and a few other users I found in a reddit post linked below) the issue completely dissapeared after we uninstalled any other apps that managed third party bluetooth devices. For me the issue was resolved immediately after uninstalling the Ultimate Ears BOOM app, and for my colleague the issue was resolved after he uninstalled Sony Headphones Connect app.

I know this sounds entirely crazy, and not any troubleshooting resolution I would have expected. But it seems to have been the case for a few users and I've been able to replicate the fix on two devices. Seems like it doesn't have anything to do with the headhones per se, but it is an android/app compatibility issue.

Hope this helps at least some of you as I know how infinitely frustrating this issue is. I'm now living in buzz free bliss!

 

Reddit link for reference - https://www.reddit.com/r/bose/comments/kl5q1h/buzz_and_reboot_issue_on_brand_new_nc700s/

The only app I have that may attempt to manage the devices is Spotify - and I am not uninstalling that...

If you have a Samsung device you do not need to uninstall any of the apps that manage third-party Bluetooth devices. Instead, you can place these apps into a deep sleep mode under the 'Background Usage Limits' menu which is accessed through the 'Battery and Device Care' menu. This will prevent the apps from running unless you specifically open them, which in most cases means you probably won't be wearing your Bose headphones. You need to then restart your phone OR manually force close each of the apps you put to sleep. You can force close an app on Samsung devices by long pressing on the app and then navigating into its settings (info icon) and then pressing 'Force Stop'.

 

Thanks to everyone for your help on this situation and for leading me to this resolution. I was getting very fed up with my headphones. This method instantly fixed the constant restarting of my headphones. I have always had the Ultimate ears app on my phone but I use it rarely, which means Samsung automatically put this app into a deep sleep after it had been unused for some period of time. This explains why I was able to use my headphones error-free for long periods of time and then they would break for some period of time before coming right again.

 

I hope this helps others!

 

UPDATE #1:  Steps to reproduce on Samsung:

  1. Navigate to Settings > Battery and device care > Battery > Background usage limits > Deep sleeping apps
  2. Place the relevant apps into deep sleep (e.g. UE Megaboom app or MOJIETU)
  3. Manually force close each of the deep sleeping apps (accessed through Settings > Apps)
    OR
    Restart your phone
  4. As a good measure also force stop the Bose app if you did not restart your phone

If the problem persists it is likely that you may have missed an app on step 2.

Yebo!!! After weeks of despair and searching several threads on this forum, your solution has worked for me! I had a bluetooth car audio app installed and I have put it in deep slepp as you instructed, restarted my phone and it is now finally working! I was almost giving up and returning my headphones.... Thank you so much ! Bose team please spread the word, because this might be the solution for kost of the people. And please try to figure out a way to solve this incompatibility once and for all.   please check this solution, I believe it will probably work for you as well

Glad to hear it !! Given Bose's reluctancy to fixing this bug in the firmware, I hope this solution will work for the majority of users out there.

 

I'm sure other phone brands will have similar power management features that prevent apps from auto-opening in the background. Most phones these days have some sort of battery optimisation settings that can be adjusted. For example, I know that some Oneplus phones have an 'App Auto-Launch' menu that controls whether specific apps are allowed to start in the background.

awww yisssss!
I have given it another try. Here is what seems to be working for me (at least for now):

- Bose Music app unistalled

- MOJIETU app (used to manage an FM transmitter for my car) put to deep sleep, just in case. I don't need this app to be running in background anyway.

- disabled Spotify Connect in background (in Spotify's own settings menu)

 yes MOJIETU was the app I also needed to put to deep sleep! And I also uninstalled Bose app for now. Glad it also worked for you! Now I see that I am having a bit of a hard time to connect my radio car again, but with time I will sort it out.