Give us a BTU firmware downgrade option for NC700
Bose product name
1.7.0 -most bad experience with, hope it doesn't auto update to 1.8.2
1.3.1 - best experience i had but unable to go back to.
What devices were you using that were affected and what version are they on
iphone, ipad all on latest ios 14.2
Detailed description of the issue and steps to reproduce
What environment do you experience the issue in?
everywhere, especially on public transportation(e.g bus)
When did you start to experience the issue? Did it work correctly previously?
@boseAdmit it, all 4 releases(1.41, 1.50, 1.70, 1.82) of NC700 firmware since 1.3.1 continue having issues people are not satisfied with, this is giving users bad experience an losing confidence in Bose as a reputable brand name. So PLEASE reinstate the ability in BTU to allow users to downgrade the NC700 headset to the stable release of firmware they are comfortable with, for my case is 1.3.1 and also give users the option to stop/prevent auto firmware update in the bose music app.
My NC700 was on 1.3.1 until it was autoupdated to 1.70 that's when i started to experience issues i never seen when I'm on 1.3.1
1) stuttering when connected to 2 mobile device
2) lesser ANC experience, even set to level 10, i can hear environmental (e.g humming from bus engine) noise and people talking from 2 meters away from me
3) autoplay incorrect last source after hanging up a call
4) reported battery life on full charge can't go more than 16-17 hours
previously when on 1.3.1
1) stuttering is observed only if i have one computer and a mobile and never when on 2 mobile.
2) the environmental noise i can hear was one that is too loud by nature. no humming when on bus, people talking loudly are reduce to muffled not distracting
3) did not seem to attempt autoplay from wrong music source, can't remember if autoplay was even there after hanging up call or i have to manually resume the playback after a call.
4) reported battery life on full charge was 19+ hours closest to advertised 20 hour max charge
Any troubleshooting steps you took
just reinstate the downgrade option in BTU, your new firmware is making things worse rather than fixing it. with the reinstate of downgrade option, users will be more willing to try upgrading to see if problem is fixed and downgrade back to stable when its not.
Granted you will also lost important bug feedback from your
white mice end users, but you are also losing something even greater, like customers and trust in brand, go figure which is more important.