Rockybilly
commented
3 weeks ago Update: I downloaded and ran Master branch in Ubuntu computer (don't have the windows one with me), and apparently it has different UI (from commits after 4.6.0?) but worked perfectly and managed to unlock my touchpad.
Describe the bug
Using Buds2 Pro on a Windows 11 computer, I've locked the touchpad, tried unlocking it again. Doesn't work. Now it's always locked. Toggleing it again doesn't work. The button shows it is unlocked, however touches don't register. And after program is restarted, it shows locked as if never unlocked before.
To Reproduce
Try to unlock touchpad of a Buds2 Pro on a Windows 11 computer
Expected behavior
Toggling working properly. It seems fine while reading the value but seems problematic when writing to it.
Screenshots
Desktop (please complete the following information):
OS: Windows 11 Pro 64bit 22631.3593 English
Application version: 4.6.0
Additional context I tried this with two different firmware versions, unfortunately I don't remember the prior. But the last one I tried is in the screenshot. I also use an Ubuntu computer, had the same problem. It really seems like the update #442 or others I don't know fixed the inverted reading but not the writing part. Though I could lock it but couldn't unlock. It's a guess.
Log files
In this log file I only included the part where I click unclock the UI shows its unlocked, after some the it refreshes and it's back to locked. application.log