Thanks, I've filled out the form.
My NC700 have been gathering dust as I simply cant get it to work with my Pixel 5 (Android 11). no matter what I do.
Open to working with your engineers to solve.
thanks
Just wanted to comment to follow this thread. My headphones are completely unusable now. Not entirely sure what to do?
2021 and 3 replacement later and here we still f***g are, aaarrrgh.
What a trash company. How can you not reproduce it consistently while I had 3 headphones replacements consistently not working for more than a year now? Boot loop and buzzing, and it always happens at the worst time, like in the middle of an important call, or when I'm in a rush and needing to have music on.
I wanted to buy earbuds for workout and headphones for my girlfriend. A year ago I would have chosen Bose, but man, you guys actually suck. A headphone produced in Uganda is more useful than this ANC 700 crap. I'm recommending everybody I know off Bose, and that carries weight from someone who's used Bose for 3 years and is into high end earpieces.
I was trying to be very patient and gave Bose the benefit of doubts, but now just a "oopsie sorry, here's a form to fill" after more than a year of reporting?
I filled out the form, but wow Bose, I started this thread in May 2020. I find it difficult to believe that you can't replicate this issue in your lab after all this time and numerous customers reporting the issue.
I sent my problematic 1.5.x headphones back to Bose HQ last summer for replacement with the thought that they would be used in your lab. Heck, I'm close enough to Framingham for a visit to help your lab engineers out if it weren't for the pandemic. My replacement headphones are (probably) at 1.3.x and working flawlessly. I'm not using the Music app and risking a chance of an unwanted FW update but the two FW releases beyond 1.3.x both resulted in the buzz/reboot loop.
Hi, i am having the exact same problem and I've only had these headphones for a year. All issues and steps have been taken exactly the same way as the original poster explained. I am also wondering what could be done about this since I really have enjoyed these headphones.
Hey Circumpunk.t,
Thank you for reaching out to us and welcome!
I'm sorry to hear that you are experiencing this issue. If you have tried all the troubleshooting outlined in this thread, I would recommend that you reach out to our team by clicking the LINK HERE, selecting your country, and scrolling down to 'Contact Us'. One of our team will be more than happy to help you!
I have the exact same or at least extremely similar issue as the original post on this thread.
When I turn on the headphones the voice in the headphones starts speaking, then I hear a loud buzzing sound, and then the headphones reboot. In some cases it will do this a few times before finally operating normally.
In the end the headphones always seem to end up operating normally, but the buzz/reboot sequence is very disturbing. My headphones tarted doing this about 6 months ago. Then after a period this went away, but recently it has restarted so I thought I'd post about it.
I use my headphones mostly for conference call, not so much for listening to music.
I typically have them set up to connect to my phone (Pixel 5) and laptop (Macbook Pro) at the same time.
The typical boot sequence would be something like this
1 - Press power button on headphone
2 - Voice in headphone says" ... Connected to ..."
3 - Headphone emits loud buzzing noise
4 - Headphone seems to reboot (I hear the boot up tune again)
5 - Voice in headphone says "... Connected to Pixel 5 and Macbook Pro" (It uses the bluetooth device names really)
6 - Everything is fine.
Note I checked the Bose Music app and I am running the latest firmware: 1.8.2-11524 e0f7590
I am going to also fill the form I just saw was mentioned in one of the posts earlier
Given at some point this disappeared, I am wondering if there is some sort of factory reset I could do to make this go away, or how I should proceed to get rid of this behaviour as it is extremely annoying.
Hello,
I have the same problem. The headset came with fw version 1.1.4 and everything worked fine but then the app updated the fw to 1.8.2 and the problems begun again. I want to point out that this is a replacement, the first headset did exactly the same. While connected only to my laptop that has bluetooth 4, everything works fine. However the moment i connect them to my Samsung S20 Ultra that has bluetooth 5.0 the freeze/restart cycle keeps going.
I tryed to fill out the form above but it seems to be closed. Bose, if I can help you with any info with the situation let me know, I really would like to be able to use the NC 700.
Thanks,
I managed to narrow down my problem a little bit: if on my phone, in bluetooth settings i turn off "Audio" for Bose and leave only "Calls" on then the connection is stable. So it may have something to do with the AAC codec on the Exynos Chip?!
I had this issue last year and already posted on this thread. Since then I returned my headphones and received a replacement pair. First thing I did was delete the Bose app from my phone before connecting them to my Galaxy Note 9. Since then I have had zero issues as I'm current running the base firmware.
I recommend this to anyone else having an issue. Just do not update the headphone firmware no matter what. Then when these headphones eventually break from old age, find a new headphone supplier.
hi everyone
i have had my Bose Noise Cancelling Headphones 700 for a year now, but some times when i play music or a video they just play a crack sound and restart in a endless circle and i cant turn them off or do anything, i just need to wait for half-hour till i can turn them off
Hey y'all! I was unknowingly running in to this on my QC 35iis and bought a 700NC as a replacement but continued to run into the issue so I dug in and managed to isolate a semi-reliable repro involving the UE Boom ("BOOM & MEGABOOM by Ultimate Ears" on Android Play store) app which has a previously paired megaboom speaker:
Bose NC 700 HP (fw 1.8.2-11524 e0f7590)
Client1:
MacBook Pro (16-inch, 2019) macOS 11.2.3 (20D91)
Spotify thick client, playing music
Client 2:
Pixel 3 XL, Android 11 (RQ2A.210305.006)
Connected to NC 700 via BT.
Open UE Boom app, click the power button to have the app attempt to wake the Megaboom speaker.
After 5-10 seconds the NC 700 will buzz and reboot. Seems like there is some BLE traffic going to the NC 700 in logcat and HCI logs.
Feel free to have eng reach out for more artifacts: sirus at haxsys dot net
Workaround: Uninstall UE Boom.
Thanks a lot 👍
Uninstalling the UEBOOM application seems to make my headset work again when it is connected to my pixel 5 and my MacBook Pro.
Great catch 💪
My friend has a Huawei P20 and I have the HTC U12 . Both have the issue, so I don't think the issue is with AAC on the Samsung Exynos. I have the UEBOOM app installed, my friend does not. The headphones are stable on 1.3.1, anything after makes the headphones reboot.
I have never had a single issue with my Bose NC 700's until this morning when the app updated my firmware to 1.8.2. Now it constantly disconnects while on calls by emitting a high pitched buzz followed by a reboot. Given what these headphones cost and the expected level of quality and reliability that brings this is ridiculous. I tried filling in some of the forms mentioned in this thread, but none of them work. I take a _lot_ of calls, and I've become reliant on Bose for these. First with QC25s, and now with these N700s. This is extremely disappointing.
I have both the NC700 and QC35II. Since buying the NC700 last year (April 2020), it developed this loud buzz reset cycle issue at some point. I have been using the Bose Music App. Currently running Android App version 4.3.4 with Firmware 1.8.2, connected to a Samsung Galaxy S8. I called support and they tried to help, but seem unaware of this issue. The person I spoke to suggested changing 2 setting in the android app, in the power setting (auto sensing Power off to OFF, and Timed Power Off to never). I had mine set at sensing ON. I agreed to try it and call back if it didn't work. No surprise it took only a few minutes for it to perform a Buzz/Reset. How annoying! Since this is seriously **bleep** me off, I've decided to read though the various threads to se what I can learn to help Bose Support to solve their firmware issue. This is what I've learned:
- The issue seems to be exclusively related to connection to an Android Phone or Devices. In the thread no one mentions any Apple iPhone that I could see.
- Performing all the usual bluetooth fixes, does not help, by this I mean uninstall the device, reinstall, etc.. The problem always returns.
- Using the headset connected only to my Windows PC, never (so far several hours use) causes the problem. Using Windows 10 Dell Latitude Laptop.
- Using the NC 700 connected to my Laptop playing music, while it is also connected to my Samsung S8, will cause the Buzz Reset cycle to begin after a few minutes, even music is playing from the PC only.
- Using the NC 700 connected to my Laptop playing music, while it is also connected to my Samsung S8, DOES NOT appear to cause the Buzz Reset cycle to occur after disabling the Bose Music App on the Samsung S8 using the Force Stop action in Android. I ran it this way for 30 minutes, music is playing from the PC only.
- Deleting all UE BOOM devices from my Samsung S8 and playing music on the NC700 from the S8 has no positive impact, it still resets every few minutes.
- I tested the NC700 with my iphone5se just to check for Buzz/Reset behavior using the iPhone. I did not install the Bose Music App, only using the NC700 directly connected. Over 1 hour use, no Buzz/Resets observed.
I will setup my Samsung S8 to capture log some Bluetooth HCI traffic Snoop Logs to see if I can see anything strange sent to the NC700 before it resets. This is done in Settings> Developer Options> Enable Bluetooth HCI Snoop Log and dump the file using the method that works on your phone,
My Bose NC700 headset has had a Buzz/Reset and repeat issue ever since I bought them back in April 2020. I should have returned them.
I've loaded the latest NC700 firmware using my PC (your Bose Music app can't keep connection long enough to load it). I have done some trouble shooting since I'm fed up with the lousy use I'm getting from these headphones.
I have no problem using my PC to steam music, it works great for hours when it is the only device connected to my Bose NC700.
I have no problem using my old iPhone 5SE, I haven't used it with the Bose Music App, but it streams for hours no issue.
If I connect the Samsung s8 to the headset as a second connection, then the trouble starts, Buzz/Reset, even if its playing music form the PC or iPhone.
I made a BTS traffic log on my phone of a Buzz/Reset I will past below.
I just tried using my Samsung S8 after deleting the Bose Music App and restarting, so far no Buzz/Reset, its been working about 1 hr and used to work max 15min. Delete the Bose Music App, it seems to be trigger the reset on my headphone.
The last few interactions with my NC700 which is labeled as DARK HELMET
….
04-14 15:07:52.375--BluetoothDataManager -- CONNECTION INFO : {"LO_MFN":"15","LO_LMP":"9","LO_SUB":"16666","LO_FWV":"BCM4361B0 Great 1KL ANT1 [Version: 0302.0392]","RE_OUI":"4C:87:5D","RE_NAM":"LE-Dark Helmet","RE_MFN":"10","RE_LMP":"9","RE_SUB":"14542","RE_COD":"2360344","RE_LTY":"1","RE_ROL":"0","RE_WEA":"0","CO_CFR":"4","CO_ADR":"","CO_HER":""}
04-14 15:07:56.588--BluetoothRemoteDevices -- ACTION_ACL_CONNECTED, device is 4C875D, linktype is 1
04-14 15:07:57.108--BluetoothDataManager -- CONNECTION INFO : {"LO_MFN":"15","LO_LMP":"9","LO_SUB":"16666","LO_FWV":"BCM4361B0 Great 1KL ANT1 [Version: 0302.0392]","RE_OUI":"4C:87:5D","RE_NAM":"LE-Dark Helmet","RE_MFN":"10","RE_LMP":"9","RE_SUB":"14542","RE_COD":"2360344","RE_LTY":"1","RE_ROL":"1","RE_WEA":"0","CO_CFR":"0","CO_ADR":"","CO_HER":""}
04-14 15:07:57.518--A2DPSM-Connecting ConnectionEvent device : FE:7, state : 2
04-14 15:07:57.519--PFQU-remove : 110a
04-14 15:07:57.520--PFQU-connect : empty
04-14 15:07:57.539--BluetoothPhonePolicy -- profileId = 2 : 1 -> 2 size 1
04-14 15:07:57.547--AdapterProp -- CONNECTION_STATE_CHANGE: 4C875D : 1 -> 2
04-14 15:07:57.548--AdapterProp -- Connection status :: [Connecting]0, [Connected]1, [Disconnecting]0
04-14 15:07:57.583--A2DPSVC-Connection state FE:7: 1->2, conn : 1
04-14 15:07:57.590--A2DPBD-"Dark HelmeX(4C:87:5D,AAC) connected"{"CCOD":"2","PCOD":"514"}
04-14 15:07:59.078--AVRCP-(FE:7) feature: 3
04-14 15:08:03.565--HFSM-DISC MSG_1 (4C875D)
04-14 15:08:03.569--PFQU-add : 111f
04-14 15:08:03.569--PFQU-connect : 111f
04-14 15:08:03.571--BluetoothPhonePolicy skipConnectOtherProfile false size 1
04-14 15:08:03.572--HFIF-connect_int([0] 4c875d)
04-14 15:08:03.574--HFAGSDP-init
04-14 15:08:03.575--HFAGSDP-start
04-14 15:08:03.584--HFSM-enter CING (4C875D)
04-14 15:08:03.591--BluetoothPhonePolicy -- profileId = 1 : 0 -> 1 size 1
04-14 15:08:03.592--AdapterProp -- Connection status :: [Connecting]1, [Connected]1, [Disconnecting]0
04-14 15:08:03.680--HFAGAct-sdp comp(0x0510) 0
04-14 15:08:03.755--HFSM-CING ConnE_2 (4C875D)
04-14 15:08:03.788--HFAGCmd-BRSF disabling IBR (AA)
04-14 15:08:03.788--HFAGCmd-AG F : 4071, HF F : 703
04-14 15:08:03.789--HFSM-connected device : 4C875D_703
04-14 15:08:03.796--HFAGCmd-Recv BAC 3
04-14 15:08:03.906--PFQU-remove : 111f
04-14 15:08:03.906--PFQU-connect : empty
04-14 15:08:03.907--HFSM-CING ConnE_3 (4C875D)
04-14 15:08:03.910--HFSM-enter CONN (4C875D, false) / 1
04-14 15:08:03.913--HFAM-setHighPriorityDevice : null to 4C875D
04-14 15:08:03.942--AdapterProp -- Connection status :: [Connecting]0, [Connected]2, [Disconnecting]0
04-14 15:08:03.945--BluetoothPhonePolicy -- profileId = 1 : 1 -> 2 size 0
04-14 15:08:03.946--HFS-setActiveDevice : null > 4C875D
04-14 15:08:03.965--HFS-nA0 nH0 s6 p-1
04-14 15:08:04.001--HFFW-semGetHeadsetSetting(4C875D,2) by 8258 @ com.samsung.android.oneconnect : -1
04-14 15:08:04.005--HFFW-semGetHeadsetSetting(4C875D,2) by 8258 @ com.samsung.android.oneconnect : -1
04-14 15:08:04.099--BluetoothPhonePolicy -- profileId = 6 : 0 -> 1 size 0
04-14 15:08:04.189--HFFW-semGetHeadsetSetting(4C875D,2) by 8258 @ com.samsung.android.oneconnect : 50
04-14 15:08:05.067--PBS-4C875D - perm : 1 (1578/2340)
04-14 15:08:05.106--BluetoothPhonePolicy -- profileId = 6 : 1 -> 2 size 0
04-14 15:08:05.645--BluetoothAdapter -- setScanMode() Mode :23, duration : 120, called by PID : 2298 @ com.android.systemui
04-14 15:08:05.672--bta_dm_act.cc -- Set p_search_cback for Inquiry
04-14 15:08:07.063--bta_dm_act.cc -- Search Cancelled
04-14 15:08:08.191--[0006]{000A}(27::CONNECTED)(13::81c2e72a-0591-443e-a1ff-05f988593351)(01::4C875D)
04-14 15:08:08.372--[0006]{000A}(27::CONNECTED)(13::f8d1fbe4-7966-4334-8024-ff96c9330e15)(01::4C875D)
04-14 15:08:18.882--BluetoothAdapter -- setScanMode() Mode :21, duration : 120, called by PID : 2298 @ com.android.systemui
04-14 15:08:19.319--[0006]{000A}(27::CONNECTED)(13::00001101-0000-1000-8000-00805f9b34fb)(01::4C875D)
04-14 15:08:25.444--[0006]{000A}(27::CONNECTED)(13::f8d1fbe4-7966-4334-8024-ff96c9330e15)(01::4C875D)
04-14 15:08:25.449--[0006]{000A}(27::CONNECTED)(13::81c2e72a-0591-443e-a1ff-05f988593351)(01::4C875D)
04-14 15:08:27.392--BluetoothDevice -- fetchUuidsWithSdp() for dev 4C875D called by PID : 23534 @ com.sony.songpal.mdr
04-14 15:08:27.396--bta_dm_act.cc -- Set p_search_cback for Service Discovery
04-14 15:08:27.882--bta_dm_act.cc -- Search Completed
04-14 15:08:39.599--[0006]{000A}(2B::read failed, socket might closed or timeout, read ret: -1)
04-14 15:08:39.601--[0006]{000A}(2B::read failed, socket might closed or timeout, read ret: -1)
04-14 15:08:47.650--[0006]{000A}(2B::read failed, socket might closed or timeout, read ret: -1)
04-14 15:08:47.654--[0006]{000A}(2B::read failed, socket might closed or timeout, read ret: -1)
04-14 15:08:57.693--[0006]{000A}(2B::read failed, socket might closed or timeout, read ret: -1)
04-14 15:08:57.701--[0006]{000A}(2B::read failed, socket might closed or timeout, read ret: -1)
04-14 15:09:06.217--hci_layer.cc -- [BTCORE] Status : BT_Link_Supervision_Timeout, Connection_handle : 0b, Transmit_Power : 10, RSSI : -55, Channel_map : 00 00 00 c0 09 8b d3 fe c0 06, LMP_cmd : 0x0000
04-14 15:09:06.230--[0006]{000A}(2B::read failed, socket might closed or timeout, read ret: -1)
04-14 15:09:06.233--[500D]{0035}(29::11)(20::8)
04-14 15:09:06.249--btif_sock_rfc.cc -- Fail to get SDP for JV, status:1, scn:0
04-14 15:09:06.258--HFSM-CONN_A(10) ConnE_0 (4C875D)
04-14 15:09:06.268--BluetoothPhonePolicy -- profileId = 6 : 2 -> 0 size 0
04-14 15:09:06.270--BluetoothRemoteDevices -- ACTION_ACL_DISCONNECTED, device is 4C875D, reason is 8, linktype is 1
04-14 15:09:06.294--A2DPSM-Connected ConnectionEvent device : FE:7, state : 0
04-14 15:09:06.299--HFSM-enter DISC (4C875D) / 0
04-14 15:09:06.304--HFAM-setHighPriorityDevice : 4C875D to null
04-14 15:09:06.315--HFS-setActiveDevice: 4C875D > null
04-14 15:09:06.323--AdapterProp -- Connection status :: [Connecting]0, [Connected]1, [Disconnecting]0
04-14 15:09:06.374--A2DPSVC-Connection state FE:7: 2->0, conn : 0
04-14 15:09:06.376--BluetoothPhonePolicy -- profileId = 2 : 2 -> 0 size 0
04-14 15:09:06.385--AdapterProp -- CONNECTION_STATE_CHANGE: 4C875D : 2 -> 0
04-14 15:09:06.387--AdapterProp -- Connection status :: [Connecting]0, [Connected]0, [Disconnecting]0
04-14 15:09:06.388--BluetoothPhonePolicy -- profileId = 1 : 2 -> 0 size 0
04-14 15:09:06.795--BluetoothDataManager -- CONNECTION INFO : {"LO_MFN":"15","LO_LMP":"9","LO_SUB":"16666","LO_FWV":"BCM4361B0 Great 1KL ANT1 [Version: 0302.0392]","RE_OUI":"4C:87:5D","RE_NAM":"Dark Helmet","RE_MFN":"10","RE_LMP":"9","RE_SUB":"14542","RE_COD":"2360344","RE_LTY":"1","RE_ROL":"0","RE_WEA":"0","CO_CFR":"","CO_ADR":"8","CO_HER":""}
04-14 15:09:08.487--BluetoothRemoteDevices -- ACTION_ACL_CONNECTED, device is 4C875D, linktype is 1
04-14 15:09:08.722--A2DPSM-Incoming connection started
04-14 15:09:08.725--A2DPSM-Disconnected ConnectionEvent device : FE:7, state : 1
04-14 15:09:08.819--BluetoothPhonePolicy -- profileId = 2 : 0 -> 1 size 0
04-14 15:09:08.823--AdapterProp -- CONNECTION_STATE_CHANGE: 4C875D : 0 -> 1
04-14 15:09:08.823--AdapterProp -- Connection status :: [Connecting]1, [Connected]0, [Disconnecting]0
04-14 15:09:08.827--A2DPSVC-Connection state FE:7: 0->1, conn : 0
04-14 15:09:08.944--[0006]{000A}(27::CONNECTED)(13::f8d1fbe4-7966-4334-8024-ff96c9330e15)(01::4C875D)
04-14 15:09:09.167--AVRCP-(FE:7) feature: 3
04-14 15:09:09.169--A2DPSM-Connecting ConnectionEvent device : FE:7, state : 2
04-14 15:09:09.178--AdapterProp -- CONNECTION_STATE_CHANGE: 4C875D : 1 -> 2
04-14 15:09:09.178--AdapterProp -- Connection status :: [Connecting]0, [Connected]1, [Disconnecting]0
04-14 15:09:09.208--A2DPSVC-Connection state FE:7: 1->2, conn : 1
04-14 15:09:09.219--BluetoothPhonePolicy -- profileId = 2 : 1 -> 2 size 1
04-14 15:09:09.222--A2DPBD-"Dark HelmeX(4C:87:5D,AAC) connected"{"CCOD":"2","PCOD":"514"}
04-14 15:09:09.305--HFAGSDP-init
04-14 15:09:09.307--HFAGSDP-start
04-14 15:09:09.321--HFSM-DISC ConnE_2 (4C875D)
04-14 15:09:09.360--HFSM-enter CING (4C875D)
04-14 15:09:09.367--AdapterProp -- Connection status :: [Connecting]1, [Connected]1, [Disconnecting]0
04-14 15:09:09.368--BluetoothPhonePolicy -- profileId = 1 : 0 -> 1 size 1
04-14 15:09:09.382--HFAGCmd-BRSF enabling IBR
04-14 15:09:09.384--HFAGCmd-BRSF disabling IBR (AA)
04-14 15:09:09.385--HFAGCmd-AG F : 4071, HF F : 703
04-14 15:09:09.397--HFAGCmd-Recv BAC 3
04-14 15:09:09.413--HFAGAct-sdp res : 0
04-14 15:09:09.417--HFSM-connected device : 4C875D_703
04-14 15:09:09.485--HFSM-CING ConnE_3 (4C875D)
04-14 15:09:09.488--HFSM-enter CONN (4C875D, false) / 1
04-14 15:09:09.489--HFAM-setHighPriorityDevice : null to 4C875D
04-14 15:09:09.522--AdapterProp -- Connection status :: [Connecting]0, [Connected]2, [Disconnecting]0
04-14 15:09:09.523--BluetoothPhonePolicy -- profileId = 1 : 1 -> 2 size 0
04-14 15:09:09.526--HFS-setActiveDevice : null > 4C875D
04-14 15:09:09.556--HFS-nA0 nH0 s6 p-1
04-14 15:09:09.602--HFFW-semGetHeadsetSetting(4C875D,2) by 8258 @ com.samsung.android.oneconnect : -1
04-14 15:09:09.607--HFFW-semGetHeadsetSetting(4C875D,2) by 8258 @ com.samsung.android.oneconnect : -1
04-14 15:09:09.619--BluetoothPhonePolicy -- profileId = 6 : 0 -> 1 size 0
04-14 15:09:09.921--PBS-4C875D - perm : 1 (1578/2340)
04-14 15:09:10.040--BluetoothPhonePolicy -- profileId = 6 : 1 -> 2 size 0
04-14 15:09:10.076--HFFW-semGetHeadsetSetting(4C875D,2) by 8258 @ com.samsung.android.oneconnect : 50
04-14 15:09:10.369--HFFW-semGetHeadsetSetting(4C875D,2) by 8258 @ com.samsung.android.oneconnect : 50
04-14 15:09:10.730--HFFW-semGetHeadsetSetting(4C875D,2) by 8258 @ com.samsung.android.oneconnect : 50
04-14 15:09:15.221--BluetoothPhonePolicy skipConnectOtherProfile true size 0
04-14 15:09:25.914--[0006]{000A}(27::CONNECTED)(13::81c2e72a-0591-443e-a1ff-05f988593351)(01::4C875D)
04-14 15:09:26.009--[0006]{000A}(27::CONNECTED)(13::f8d1fbe4-7966-4334-8024-ff96c9330e15)(01::4C875D)
04-14 15:09:38.067--[0006]{000A}(27::CONNECTED)(13::00001101-0000-1000-8000-00805f9b34fb)(01::4C875D)
04-14 15:09:44.760--BluetoothDevice -- fetchUuidsWithSdp() for dev 4C875D called by PID : 25888 @ com.sony.songpal.mdr
04-14 15:09:44.769--bta_dm_act.cc -- Set p_search_cback for Service Discovery
04-14 15:09:45.368--[0006]{000A}(27::CONNECTED)(13::81c2e72a-0591-443e-a1ff-05f988593351)(01::4C875D)
04-14 15:09:45.443--[0006]{000A}(27::CONNECTED)(13::f8d1fbe4-7966-4334-8024-ff96c9330e15)(01::4C875D)
04-14 15:09:45.670--bta_dm_act.cc -- Search Completed
04-14 15:09:51.027--[0006]{000A}(27::CONNECTED)(13::f8d1fbe4-7966-4334-8024-ff96c9330e15)(01::4C875D)
04-14 15:09:51.094--[0006]{000A}(27::CONNECTED)(13::81c2e72a-0591-443e-a1ff-05f988593351)(01::4C875D)
04-14 15:10:26.058--A2DPBD-"(4C:87:5D)Played for 7sec"{"ALF2":"6974","ALF3":"0"}
04-14 15:11:44.534--[0006]{000A}(27::CONNECTED)(13::f8d1fbe4-7966-4334-8024-ff96c9330e15)(01::4C875D)
04-14 15:11:44.637--[0006]{000A}(27::CONNECTED)(13::81c2e72a-0591-443e-a1ff-05f988593351)(01::4C875D)
04-14 15:11:56.146--A2DPBD-"(4C:87:5D)Played for 3sec"{"ALF2":"2959","ALF3":"0"}
04-14 15:12:20.731--HFFW-semGetHeadsetSetting(4C875D,2) by 8258 @ com.samsung.android.oneconnect : 50
04-14 15:12:22.532--BluetoothAdapter -- disable() called by PID : 2298 @ com.android.systemui
04-14 15:12:22.580--BluetoothManagerService -- disable() BT ManagerService disable called
04-14 15:12:22.582--BluetoothManagerService -- Persisting Bluetooth Setting : 0
04-14 15:12:22.590--AdapterState Current state: BT ON, message: USER_TURN_OFF
04-14 15:12:22.591--AdapterState Entering Turning BT OFF
04-14 15:12:22.670--[1006]{001B}
04-14 15:12:22.683--PFQU-clear
04-14 15:12:22.713--[5008]{0029}(12::0)(04::2)
04-14 15:12:22.715--A2DPSM-Connected ConnectionEvent device : FE:7, state : 0
04-14 15:12:22.724--[5009]{002E}
04-14 15:12:22.727--[5008]{0046}(04::3)
04-14 15:12:22.728--[5008]{0029}(12::1)(04::3)
04-14 15:12:22.729--[5008]{002A}(20::82)(04::3)
04-14 15:12:22.730--bta_hh_le.cc -- invoke bta_hh_cleanup_disable, bta_hh_gattc_callback
04-14 15:12:22.731--bta_hh_utils.cc -- BTA_HH_DISABLE_EVT, bta_hh_cleanup_disable(), status : 0
04-14 15:12:22.732--[500D]{0039}(02::0)
04-14 15:12:22.734--[500B]{0036}(02::2)(29::64)(03::000000)
04-14 15:12:22.735--[5008]{0029}(12::1)(04::0)
04-14 15:12:22.736--[5008]{002A}(20::80)(04::0)
04-14 15:12:22.825--BluetoothPhonePolicy -- profileId = 6 : 2 -> 0 size 0
04-14 15:12:22.827--AdapterProp -- Connection status :: [Connecting]0, [Connected]1, [Disconnecting]0
04-14 15:12:22.841--A2DPSVC-Connection state FE:7: 2->0, conn : 0
04-14 15:12:22.841--BluetoothPhonePolicy -- profileId = 2 : 2 -> 0 size 0
04-14 15:12:23.232--BluetoothAdapter -- enable() called by PID : 30805 @ com.shanling.shanlingcontroller
04-14 15:12:23.245--HFSM-CONN_A(10) ConnE_0 (4C875D)
04-14 15:12:23.259--BluetoothAdapter -- enable() Call : ManagerService enable
04-14 15:12:23.260--BluetoothManagerService -- enable() BT ManagerService enable called
04-14 15:12:23.268--HFSM-enter DISC (4C875D) / 0
04-14 15:12:23.269--HFAM-setHighPriorityDevice : 4C875D to null
04-14 15:12:23.272--HFS-setActiveDevice: 4C875D > null
04-14 15:12:23.296--BluetoothManagerService -- Persisting Bluetooth Setting : 1
04-14 15:12:23.307--AdapterProp -- CONNECTION_STATE_CHANGE: 4C875D : 2 -> 0
04-14 15:12:23.309--AdapterProp -- Connection status :: [Connecting]0, [Connected]0, [Disconnecting]0
04-14 15:12:23.309--BluetoothPhonePolicy -- profileId = 1 : 2 -> 0 size 0
04-14 15:12:23.328--[500D]{0035}(29::11)(20::22)
04-14 15:12:23.330--[5008]{0029}(12::1)(04::0)
04-14 15:12:23.330--[5008]{002A}(20::80)(04::0)
04-14 15:12:23.334--BluetoothRemoteDevices -- ACTION_ACL_DISCONNECTED, device is 4C875D, reason is 22, linktype is 1
04-14 15:12:23.851--BluetoothDataManager -- CONNECTION INFO : {"LO_MFN":"15","LO_LMP":"9","LO_SUB":"16666","LO_FWV":"BCM4361B0 Great 1KL ANT1 [Version: 0302.0392]","RE_OUI":"4C:87:5D","RE_NAM":"Dark Helmet","RE_MFN":"10","RE_LMP":"9","RE_SUB":"14542","RE_COD":"2360344","RE_LTY":"1","RE_ROL":"0","RE_WEA":"0","CO_CFR":"","CO_ADR":"22","CO_HER":""}
04-14 15:12:24.390--MPSVC-map service stopped, Email Account Removed
04-14 15:12:24.408--AdapterState Current state: Turning BT OFF, message: BREDR_STOPPED
04-14 15:12:24.412--AdapterState Entering BLE ON
04-14 15:12:24.478--AdapterState Current state: BLE ON, message: USER_TURN_ON
04-14 15:12:24.480--AdapterState Entering Turning BT ON
04-14 15:12:24.512--BluetoothAdapter -- semSetStandAloneBleMode() Call set : true
04-14 15:12:24.515--BluetoothAdapter -- enableRadio() called by PID : 8747 @ com.samsung.android.beaconmanager
04-14 15:12:24.676--HFS-IBR true/true
04-14 15:12:24.700--HFS-IBR set false
04-14 15:12:24.703--HFIF-BRSF 4079(0,0)
04-14 15:12:24.715--HFIF-max4 eh_sco1 data_path6 IBR1 DBG1 DMP0
04-14 15:12:24.811--bta_hh_act.cc -- HID HOST registering success, bta_hh_api_enable()
04-14 15:12:24.812--bta_hh_le.cc -- bta_hh_le_enable: status of registering HID host = 0
04-14 15:12:24.814--[5008]{0029}(12::1)(04::0)
04-14 15:12:24.815--[5009]{002D}(03::000000)(1C::3)
04-14 15:12:24.997--PBL-PBAP 12, MULTI_PROP
04-14 15:12:25.020--AdapterState Current state: Turning BT ON, message: BREDR_STARTED
04-14 15:12:25.021--AdapterState Entering BT ON
04-14 15:12:25.129--HFPS-MS0 CTC0 RAT0 T0
04-14 15:12:25.212--[1006]{001A}(03::null)
04-14 15:12:25.278--MPSVC-map service started, Email Account Added
04-14 15:12:25.626--HFS-nA0 nH0 s6 p-1
04-14 15:12:26.213--BtGatt.GattService unregisterServer(com.fitbit.FitbitMobile)
04-14 15:12:26.230--BtGatt.GattService registerClient(com.fitbit.FitbitMobile)
04-14 15:12:26.233--[0003]{0002}(02::0)(07::8)
04-14 15:12:26.236--BtGatt.GattService clientConnect(com.fitbit.FitbitMobile)(clientIf=8)(address=D0:1)(isDirect=true)(transport=2)(set_own_addr_type=false)(own_addr_type=0)(phy=1)
04-14 15:12:26.237--BtGatt.GattService registerServer(com.fitbit.FitbitMobile)
04-14 15:12:26.240--[5008]{0029}(12::0)(04::2)
04-14 15:12:26.240--[5009]{002E}
04-14 15:12:26.242--[5008]{0046}(04::3)
04-14 15:12:26.242--[500D]{0039}(02::0)
04-14 15:12:26.243--[500B]{0036}(02::2)(29::64)(03::000000)
04-14 15:12:26.246--[5009]{002D}(03::d118c5)(1C::3)
04-14 15:12:31.243--[500E]{003C}(2F::3)(30::0x0)(31::0)
04-14 15:12:31.245--[5009]{002E}
04-14 15:12:31.249--[500D]{0039}(02::0)
04-14 15:12:31.252--[500B]{0036}(02::2)(29::64)(03::d118c5)
04-14 15:12:31.253--[5008]{0029}(12::1)(04::0)
04-14 15:12:31.254--[5009]{002D}(03::000000)(1C::3)
04-14 15:12:31.264--[0003]{0003}(02::133)(07::8)(04::false)(03::D1:18:C5:D0:1E:XX)
04-14 15:12:31.286--[0003]{0007}(03::D118C5)
04-14 15:12:31.288--BtGatt.GattService clientDisconnect(com.fitbit.FitbitMobile) - address = D0:1, connId = null
04-14 15:12:32.297--BluetoothGatt close(D118C5)
04-14 15:12:32.302--BtGatt.GattService unregisterClient(com.fitbit.FitbitMobile)(clientIf=8)
04-14 15:15:22.292--HFFW-isInbandRingingSupported() : 1 by 20211 @ com.android.bluetooth
--------- 0.410s was the duration of dumpsys bluetooth_manager, ending at: 2021-04-14 15:15:22
Man, reading through this whole thread is pretty upsetting. This is my second pair of Bose 700 after the first one experienced the static in one ear bug. https://community.bose.com/t5/Around-On-Ear-Headphones/Bose-NC-700-Static-In-One-Ear-When-Powered-On/td-p/280104
And now even though I've had this pair which has worked perfectly up until today, now I'm really sour on ever buying a Bose product (or at least headphones) ever again. I don't understand how such a seemingly common problem can't have a fix or even a workaround after almost a year.
Obviously its nothing against the kind and hardworking moderators and customer service people in this thread, but it's just ridiculous.
For what its worth, I've had some small periods of time where I thought it got fixed, and they all centered around deleting an app. However the problem so far has always come back later (I've only had this problem for about 24hrs now). Maybe it'll help someone else. For reference, I've deleted the Bose Connect, Bose Music, Google Assistant, Soundcore (Anker) apps, followed by clearing the bluetooth connections. Even if it did permanently fix it though, I shouldn't have to delete other peoples apps that I need for other devices and functionality to fix Bose's device.
The buzzing is also sometimes loud, sometimes so soft its almost nonexistent, and changes pitch. Always happens on startup, and always restarts. So strange.
Hello Ive just got a brand new 700 noslise cancelling headphones and the buzzing thing keeps happening does anyone know how to fix it 🤬🤬🤬🤬🤬
: It has been nearly one year since I first opened this thread. In that time there has been no resolution to this product defect. One survey which doesn't appear to have been acted upon and a multitude of owners whose headphones are still buzzing and rebooting with any firmware higher than 1.3. Sigh.
Can the mods at least provide an update as to whether this defect is under investigation and if there's any chance of it being resolved in future firmware? It's annoying to own what should be a high quality product, not be able to use them to their fullest and have no indication from Bose as to the status.
My NC700s remain at 1.3 firmware, I do not have the Music app installed to prevent unwanted updates and they will remain as such until this defect is permanently resolved. I can not recommend this product to others, the Bose experience has been very disappointing.
Mods, please update this thread with the current status of your engineering team's investigation.
Regards