We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 2363

Summary: [Android] [OUYA] system button is not handled
Product: SDL Reporter: Martin Gerhardy <martin.gerhardy>
Component: joystickAssignee: Gabriel Jacobo <gabomdq>
Status: RESOLVED WONTFIX QA Contact: Sam Lantinga <slouken>
Severity: normal    
Priority: P2 CC: gabomdq, martin
Version: HG 2.0   
Hardware: ARM   
OS: Android (All)   

Description Martin Gerhardy 2014-01-25 13:49:55 UTC 
The system button (right next to the dpad) is not reported as an event to SDL.

I tried testgamecontroller.c and controllermap.c - both do not react on pressing that button.
Comment 1 Gabriel Jacobo 2014-01-27 13:41:02 UTC 
Can you debug this? How does the system button arrive to SDLActivity.java?
Comment 2 Martin Felis 2014-01-28 14:59:29 UTC 
That button is probably reported as a standard keyboard event with keycode SDLK_PAUSE. See here: https://bitbucket.org/MartinFelis/love-android-sdl2/issue/12/ouya-controller-doesnt-fully-work#comment-7834288
Comment 3 Gabriel Jacobo 2014-01-28 15:03:15 UTC 
If the driver reports the button as key, there's not much we can do...right?
Comment 4 Martin Gerhardy 2014-01-28 16:33:08 UTC 
that means we can not create a game controller mapping string for all the strings... that sucks. but if it's reported as a key, that would already help me a lot. Thanks for pointing that out.
Comment 5 Martin Gerhardy 2014-01-28 16:36:14 UTC 
I closed this now.