Nov 1, 2018
I agree that I didn't buy the explanation, but I could not convince the supervisor otherwise or to get me someone else and he insisted he knew what he was talking about (and commented that forum posts are inaccurate).
Perhaps if anyone that has successfully got a out of warranty replacement and tell us who the coorperative Bose reps are we can ask to be directed to them?
Oct 29, 2018
Sorry to tell you that it was the latest firmware that caused the problem. There is absolutely nothing you can do but wait with the rest of us for the fix in the next firmware update. I have no clue when that will be but I suspect we will see something by end of 1st Quarter 2019 (perhaps this year).
fyi - Greg_B... you posted this as a 'solution' when in fact there is NO solution as of yet. The fix will be in the next firmware release and we have no idea when that will be. Could be days or months. In the meantime, any time the QC 35 (I or II) comes near a bluetooth device, paired or unmanned, yours or someone else's, thanks to BLE (Bluetooth low emission), it may/will turn on even if the switch says off. The auto time off may not work and even if it did, the QC 35 will turn itself back on again. About the only 'workaround' I have found is to keep the QC 35 always plugged in and charging when not in use.
Well one thing we do not know is how many versions back in the firmware was the BLE issue implemented/introduced. You may have purchased the QC-35 with firmware that already have the problem. Bose at many different 'levels' (including US supervisory personnel) have told me that their BLE implementation in the QC-35 firmware has manifested in this QC-35 turning itself on. Could there be an on/off switch problem as well - possible. But if you exchange your device for another - that may or may not solve your 'issue'. First you may get a device with firmware that has the BLE issue or if it is indeed a on/off switch problem, you may get another QC-35 with the same hardware issue.
We need to wait for Bose to claim they have fixed the firmware to eliminate the symptom and then download and install that firmware into our QC-35. Then if there is still a problem either (a) they did not totally fix it in the firmware or (b) it then becomes a hardware issue.
Oct 7, 2018
I have never touched the firmware on my headphones, not once since I started using them. Many others have indicated that the problem starts occuring after approx 1 year of use. Suggesting it is the firmware is a convenient was to sidestep the real issue of it being a hardware failure.
I wonder what your objective is of suggesting is it firmware? The facts clearly indicate it is not.
I also agree with you.
But as I am travelling a lot, I cannot wait till Bose fix this problem.
Clicking already to purchase sony.
I am using more than 5 bose products but, hope bose to know wasting loyal customers time will lead to bad result.
Rather change the defect ones with new one and study the problem seriously.
As we are also so serious.