Skip to content
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

Retroid Pocket 5 L1 button not detected #1393

Open
2 tasks
itsnandy opened this issue Jan 17, 2025 · 4 comments
Open
2 tasks

Retroid Pocket 5 L1 button not detected #1393

itsnandy opened this issue Jan 17, 2025 · 4 comments
Assignees
Labels
bug Something isn't working needs triage

Comments

@itsnandy
Copy link

itsnandy commented Jan 17, 2025

Developer TODO (don't remove)

  • write tests. put issue number in comment
  • update documentation

Describe the bug
I usually use the combo; L1, R1, and a face button (A, B, X, Y), as the trigger and the press is set to At the same time. The action is to change brightness and volume. The bug I’m having is the L1 isn’t registering, but only just for Key Mapper.

To Reproduce
The triggering works, though if I test the L1 button in any app or a gamepad tester, the button doesn't show it activating.

Upload a backup of your keymaps:
mappings_20250117-103724.zip

Expected behavior
Either I didn't notice in the beginning of using KeyMapper, but L1 should just be used normally and when L1 + R1 + B is pressed, the trigger selected should activate.

Screenshots
If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

  • Device: Retroid Pocket 5
  • Android version: 13
@itsnandy itsnandy added bug Something isn't working needs triage labels Jan 17, 2025
@sds100 sds100 changed the title First button of three triggers doesn't work only just for KeyMapper Retroid Pocket 5 L1 button not detected Jan 17, 2025
@sds100
Copy link
Collaborator

sds100 commented Jan 17, 2025

What does the L1 button do by default when you're not in a game? Is it used for navigation in any way? Also issue #491 may solve this problem. I am going to finish it within a few weeks and it can be tested then

@itsnandy
Copy link
Author

L1 by default doesn't do anything. Though when it's assigned to be used in KeyMapper, it's like it just doesn't even function anymore except for KM (KeyMapper). I even thought the button was broken and took it apart because I thought the ribbon came loose or something.

Hope this can get fixed soon. Other than this issue, this app is AWESOME!

@sds100
Copy link
Collaborator

sds100 commented Jan 17, 2025

Oh, you can remap L1? The problem is that with your key maps it doesn't behave normally?

@itsnandy
Copy link
Author

I uploaded the mappings I use. L1 does not behave correctly when it's being used by KM. Literally only for KM and it just doesn't exist anymore for anything else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage
Projects
None yet
Development

No branches or pull requests

2 participants