Seamus
Contributor
  • 10
  • 6
  • 0
Registered since

Dec 2, 2020

!Re: Noise Cancelling 700 Firmware Update - 1.8.2 – November 19th 2020

Or, better still,  another product

Leica M
Collaborator
  • 18
  • 14
  • 0
Registered since

Dec 26, 2020

Re: Noise Cancelling 700 Firmware Update - 1.8.2 – November 19th 2020

The lack of response for such a long time from the Community team is concerning and I think abandonment is the official response from the company as far I am concerned.

KrishnaChaitanya
Collaborator
  • 39
  • 20
  • 0
Registered since

Jun 9, 2020

Re: Noise Cancelling 700 Firmware Update - 1.8.2 – November 19th 2020

Bose,

 

Seriously? You are just ignoring all these complaints without any response. What is the point of setting up this community page? So that people can vent out their frustrations. I think we have better apps for that. You don't know the power of customers. When they decide to quit your product. They will. There are lot other companies who cares for their customers. Good luck Bose. Thanks for ignoring us. It is time for us to start ignoring your products and helping our friends to do the same.

 

 

jkhalil
Contributor
  • 9
  • 2
  • 0
Registered since

Mar 25, 2021

Re: Noise Cancelling 700 Firmware Update - 1.8.2 – November 19th 2020

Even after updates, resets, reboots, clears, etc... this is still a serious issue. I finally decided to dig deeper into the issue. I traced the bluetooth packets to see if I could find any obvious issues.

 

The only thing I can see is that when the interruptions happen there is a flood of L2CAP Send packets and then a flood of HCI events when trying to catch up.

 

I doubt there are any tech savvy Bose reps here on the forums but if there are, here is a sample of the packet traffic pattern from my Macbook Pro 16" to my NC700s when the issue happens. 

 

Maybe @Wayne_M you could pass this info to the devs to see if they can figure out **bleep** is going on with our headphones so the next Firmware update actually fixes it.

 

 

Mar 25 19:22:00.515 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x027C (636) [ 80 E0 E5 9F 05 25 F0 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.537 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0285 (645) [ 80 E0 E5 A0 05 25 F4 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.558 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0289 (649) [ 80 E0 E5 A1 05 25 F8 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.571 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.581 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0287 (647) [ 80 E0 E5 A2 05 25 FC 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.592 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.601 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x026B (619) [ 80 E0 E5 A3 05 26 00 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.623 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0284 (644) [ 80 E0 E5 A4 05 26 04 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.643 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0289 (649) [ 80 E0 E5 A5 05 26 08 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.665 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x027F (639) [ 80 E0 E5 A6 05 26 0C 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.687 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0281 (641) [ 80 E0 E5 A7 05 26 10 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.708 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x024F (591) [ 80 E0 E5 A8 05 26 14 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.799 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.802 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x026B (619) [ 80 E0 E5 A9 05 26 18 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.811 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.814 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0263 (611) [ 80 E0 E5 AA 05 26 1C 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.817 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.820 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0289 (649) [ 80 E0 E5 AB 05 26 20 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.827 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.830 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0268 (616) [ 80 E0 E5 AC 05 26 24 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.848 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.851 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x027D (637) [ 80 E0 E5 AD 05 26 28 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.856 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.858 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0271 (625) [ 80 E0 E5 AE 05 26 2C 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.863 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.866 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0289 (649) [ 80 E0 E5 AF 05 26 30 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.869 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.873 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.878 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0264 (612) [ 80 E0 E5 B0 05 26 34 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.878 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.886 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.892 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.896 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.899 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0284 (644) [ 80 E0 E5 B1 05 26 38 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.908 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.921 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x025D (605) [ 80 E0 E5 B2 05 26 3C 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.924 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.932 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.942 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0262 (610) [ 80 E0 E5 B3 05 26 40 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.942 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.946 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.952 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001
Mar 25 19:22:00.963 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x0265 (613) [ 80 E0 E5 B4 05 26 44 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.985 L2CAP Send 0x000C BOSENC700 Channel ID: 0x04C8 Length: 0x028F (655) [ 80 E0 E5 B5 05 26 48 00 00 00 00 01 47 FC 00 00 ... ]
Mar 25 19:22:00.985 HCI Event 0x000C BOSENC700 Number Of Completed Packets - Handle: 0x000C - Packets: 0x0001

jkhalil
Contributor
  • 9
  • 2
  • 0
Registered since

Mar 25, 2021

Re: Noise Cancelling 700 Firmware Update - 1.8.2 – November 19th 2020

Moreover, I have found that everytime a stutter occurs I see this error: Mar 25 22:05:32.469 A2DP Audio Send 0x000C BOSENC700 AAC Audio Data - Sequence 61802 - Payload Length 581 - Delta Between Previous Packet Too Large.

 

I hope this gives the developers something to look for and fix...

 

 

 

Jacek K
Collaborator
  • 23
  • 14
  • 0
Registered since

Nov 16, 2020

Re: Noise Cancelling 700 Firmware Update - 1.8.2 – November 19th 2020

Thank you @jkhalil for debugging this. What a time, the community is doing the brand's software engineers' job. But it is not a surprise for me. Recently, one guy prepared a fix for one of the biggest and most popular games developed by one of the biggest game studios. They also weren't able to develop the patch. They paid him $10k and included his work in the official release.

 

@Wayne_M @bose As someone debugged the issue, maybe it will help to develop the proper firmware? It would be nice to hear anything from you. I believe you can do better in terms of both, software and communication.

Dalancaster
Contributor
  • 3
  • 2
  • 0
Registered since

Mar 26, 2021

Re: Noise Cancelling 700 Firmware Update - 1.8.2 – November 19th 2020

Constant restart/reboot and buzzing.  NC700 firmware  1.8.2-11524+ e0f7590  Manufacture date May 29, 2020.  Maybe it has Covid.

This is second pair, same issue.  Previous 700 was manufactured in Oct 2020.

Note 10+ 5G, Android 11 Verizon

No issues with Bose Sport Buds, Galaxy Buds Pro, Beats Powerbeats 3, Powerbeats Pro, Beats Powerbeats True Wireless.  No other BT issues, phone connects to Tacx Neo2, Wahoo Tickr BT.  No issues with all my ANT+ devices.

Issues is only with the 700 headphones.  I plan to do what others have done, replace with old firmware pair and not use/install Bose Music app to prevent update to Bose 700 that destroys ability to use with Note 10+

 
UrbanHike
Collaborator
  • 10
  • 10
  • 0
Registered since

Jun 24, 2020

Re: Noise Cancelling 700 Firmware Update - 1.8.2 – November 19th 2020

I called Bose again about this issue, asking when there might be a software update. All they wanted to do was to replace the headset again. I agreed, just to try anything, but of course they haven't actually sent anything (it's been about three weeks).

 

Same issues of course, stuttering, even with a single bluetooth source sometimes (once a day for about 20 seconds).

smj0707
Participant
  • 0
  • 1
  • 0
Registered since

Apr 2, 2021

Re: Noise Cancelling 700 Firmware Update - 1.8.2 – November 19th 2020

Well thanks to all in this forum.  Really wanted to go Bose but the continued issues, they have lost a sale.  Going with Sony.   Hope it does get resolved at some stage for those that still own NC 700

TH1813254617
Collaborator
  • 8
  • 23
  • 0
Registered since

May 19, 2020

Re: Noise Cancelling 700 Firmware Update - 1.8.2 – November 19th 2020

Seeing this thread, I don't have the courage to install the 1.8.2 update.

 

I've been bitten by 1.4.12, 1.5.X, and 1.7.0. Basically, anything after 1.3.1 for me has resulted in random reboots. 1.3.1 was the most stable firmware by far. I have tried it on my HTC U12+ on Android 9 and my friend's Huawei P20, both had the issue.

 

I'm on my third pair of headphones, they're on 1.3.1 and I do not plan on updating anytime soon. If not for the actually usable mic (They're not nearly as good as the mic on my phone so I need to disconnect the headphones and use my phone to make myself heard at times, but they're way better than the competition), I would have gone with Sony.

 

BTW, I have the UEBoom app, my friend doesn't.