-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Add an option to disable prev/next track buttons on headsets #9745
Comments
This seems to be a nice feature. But combining with #7880 would be better.
There should be a fifth option |
Not sure how to reassign buttons on Bluetooth headsets though. Oh yeah, and someone with a Bluetooth headset will have to test if the patch works Oh, great, I woke Checkstyle up. This is gonna take longer than what I expected... |
Nailed it! https://github.com/NyanCatTW1/NewPipe/commit/f75003732c2639457d01638493d8f41072a59ed9 Making a PR right now |
No problem, that could be done as well. I just suggested combining the options to avoid a bloated UI. |
Checklist
Feature description
My plan is to add a new option under Video and audio/Behavior, which would look like this:
When the option is enabled, it should do precisely what its description states.
Because it is impossible to distinguish between events that come from a Bluetooth headset and the control UI, it will ignore events from both sides. However, this should only occur when a Bluetooth headset is detected.
See also: https://code.videolan.org/videolan/vlc-android/-/merge_requests/1633
Why do you want this feature?
I sleep with my headset on. However, I often press the prev/next track buttons on the headset by accident, which causes the video to rewind or skip. Needless to say, this is quite inconvenient.
Unfortunately, on Android, there is no way to disable media buttons globally without rooting the phone or physically blocking the pin (which also disables the mic). This means I need the option to make the player ignore those presses.
I'm planning to implement it myself today. But I would also like to know if someone else is interested in such a feature.
Additional information
No response
The text was updated successfully, but these errors were encountered: