GalaxyBudsClient
GalaxyBudsClient copied to clipboard
timschneeb
[BUG] For buds2 the noise cycle switching mode & old version firmware& proximity measurement
Describe the bug
- the noise cycle switching mode not work, actually is ANC->Ambient.
- cant search old version firmware.
- proximity measurement L&R both display fail but
Desktop (please complete the following information):
- OS: Windows 10 Pro 64bit OS Build number 19044.1826, default system language en-US
- Application version: 4.5.1.0
I downgrade to R177XXU0AUH2, but still have these problems mentioned upon.
the noise cycle switching mode not work, actually is ANC->Ambient.
This noise cycle switching mode was a hidden option that I found on the Buds Pro. It looks like they never added this to the Buds2, so I can't do anything about it except hiding the option.
cant search old version firmware.
Maybe the server was down for a moment, but it works now for me. If the list is still empty, then a firewall might block access to my firmware server backup.
proximity measurement L&R both display fail
This is normal if you are wearing the earbuds in your ears, if they are in the case, or if the proximity sensor is blocked by another object.
the noise cycle switching mode does not work, actually is ANC->Ambient.
This noise cycle switching mode was a hidden option that I found on the Buds Pro. It looks like they never added this to the Buds2, so I can't do anything about it except hide the option.
It's quite strange. When I first use bud2 it connects with BudsClient on PC not galaxy wearable on Samsung device, the cycle mode is working. But after I connect galaxy wearable and update firmware, and then connect back to BudsClient, I find cycle mode does not work. Therefore, I think this is a bug.
cant search old version firmware.
Maybe the server was down for a moment, but it works now for me. If the list is still empty, then a firewall might block access to my firmware server backup.
I can access this URL in explorer. log is below
