-
Notifications
You must be signed in to change notification settings - Fork 370
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
Create android/Sony_DualSense_v2 #948
Conversation
android/Dual Sense 5.cfg didn't work in Google TV 10 (based on Android 12) so I made this file. For more info see: * #940
input_vendor_id = "1356" input_product_id = "3302"
Looks like there's another Duel Sense? Think your changes could override the original?
|
Hi again Rob! It's DualSense (just made pull request by the way), and I evaluated an original gamepad from Sony.
The original config works for Android Common Kernels (ACK) 4.14, but not for 5.4,and vice versa. See the table for more info: With that said, ideally we should include the supported ACK version in the filename, but since I don't have a reference to the kernel version support I simply suggested "Sony_DualSense_v2" |
We will have to make sure there aren't any duplicate configs, or keep the V2 IDs commented out. I'd suggest targeting the new firmware one here, tbh. As a general rule of thumb, could be good to recommend people update their gamepad firmware. |
I'm using the latest DualSense firmware. The Android kernel (based on the Linux kernel) decides how DualSense should be handled. I don't know if the firmware affects the key bindings. Should we include the DualSense firmware or android kernel version in the cfg file name? |
Generated from
RetroArch:
android/Dual Sense 5.cfg didn't work in Google TV 10. For more info see: