-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fyi at least for QC 35 I downgrading does not help #34
Comments
See this section
|
Maybe this is placebo... compared the qc35 I upgraded to 3.0.3 and downgraded to 1.3.2 against a qc35 II at 4.1.3 that was never upgraded. Everything seems same between them. I could have almost sworn that originally there was a difference between high/low NC modes in a silent room (since I remember testing this when writing cli app to send packets to trigger the nc switch), but maybe my ears got used to it. |
Hey how did you get them downgraded with the new Bose Updater patch? Sick as hell, please let me know! |
see #33, basically use charles or some other mitm to intercept the xml |
Hey, reccently downgraded to 2.5.3 and I found this to be the best firmware for noise cancelling |
i have tried with charles, but it wont help if both worldwide.bose.com and downloads.bose.com points to this lookup file i cant see any lower version than 2.5.5, how do you really manage to do it? |
It should be noted that at least for my qc35 downgrading from 3.0.3 to any lower firmware did not restore NC to what it used to be. This of course sounds insane, but several others on reddit seem to have corroborated. Given that FW updates and device resets don't affect the paired device list, my best guess is that there's some region of memory that was touched by the 3.0.3 update that isn't reverted back when downgrading.
The firmware themselves seem to be for BlueCore IC, but no idea if anyone has ever RE'd them
The text was updated successfully, but these errors were encountered: