search

timschneeb / GalaxyBudsClient

Unofficial Galaxy Buds Manager for Windows, macOS, Linux, and Android
GNU General Public License v3.0
3.63k stars 192 forks source link

[BUG] Firmware update wrongly detects device mismatch #533

Closed laust0rm closed 2 months ago

laust0rm commented 3 months ago

Describe the bug
I wanted to update the firmware on my Buds2 Pro, and the list only contained Buds2 firmware. When I wanted to load a custom firmware binary, I got the message "Device model mismatch detected! [...]", even though the program detects my buds as Buds2 Pro. (in the main screen)

To Reproduce
My phone says the firmware is R510XXU0AVK3, which is what I originally flashed, but galaxybudsclient says R177XXU0AVK3. I don't know what caused this, but I think this is what caused the behaviour.

Expected behavior
Expected gbc to list B2P firmware/allow the custom bin.

Screenshots
image img

Desktop (please complete the following information):

Log files
application.log

YexuanXiao commented 2 months ago

Does this issue still exist in the latest version? I own Buds2Pro but it won't reproduce on my device.

timschneeb commented 2 months ago

I wanted to update the firmware on my Buds2 Pro, and the list only contained Buds2 firmware. When I wanted to load a custom firmware binary, I got the message "Device model mismatch detected! [...]", even though the program detects my buds as Buds2 Pro. (in the main screen)

Old versions of GalaxyBudsClient had an issue that wrongly identified the Galaxy Buds2 Pro as a pair of Galaxy Buds2 instead during the setup. You're already using a new version with the bugfix, but the incorrect model value is still stored in the config file.

To fix this, just unregister the device and then re-add it. This time, it will be correctly identified as Buds2 Pro and the error will vanish.

Viktor-2b commented 3 weeks ago

Same situation here, using the latest version 5.1. Unregistering and re-adding doesn't help either. Some details: I downgraded to the earliest firmware version of the Buds2 Pro, and the earbuds split into two parts, each could be connected separately, (68FC and 1244). After pushing them for 3 seconds, they merged back into a single connection unit. However, the issue persists, just like this.