Gamepad Crashes on Android

[GuilhermeGS2]

I saw many builds that says the crashes in Android with gamepad was fixed. But when I use my generic controller, the emulator crashes. What may be?

[theonyxphoenix]

I saw many builds that says the crashes in Android with gamepad was fixed. But when I use my generic controller, the emulator crashes. What may be?

I have the same problem with my bluetooth controller. Anytime I press on the d-pad or an analog stick it says that "Unfortunately, PPSSPP has stopped."

I've tried uninstalling, clearing data, clearing cache...I haven't been able to get it properly working since 8.1-169

[Henrik]

Hm, i fixed the crashes I could reproduce Don't know what might be going on...

[theonyxphoenix]

Hm, i fixed the crashes I could reproduce Don't know what might be going on...

Is there any way to produce or send a report for debugging?

I'm going to try my Sixaxis and see if it works with that on recent builds.

[GuilhermeGS2]

I make a log, I don't know if will help: http://www.mediafire.com/view/0llzsvz7ij...453918.txt
The emulator crashes when I press d-pad or use analog stick.

---

I also mapped the buttons on PPSSPP, but when I press any mapped button, not happen any thing.

[theonyxphoenix]

I went in to devices and made sure to clear out anything that is active, clear cache and data for any associated apps, etc.

If I active the controller using Bluez IME I can use the Zeemote JS1 driver and set the device as Bluez IME and it works, but the tablet doesn't acknowledge the use of the L & R buttons or D-pad. The left analog works like a D-Pad and the other buttons map as well. If I don't set device as IME then it causes it to crash.

Still doing some exploring...

[theonyxphoenix]

so it seem as though native support causes it to crash but if I use Bluez IME it is fine. I can even use GameController app and set it to Bluez IME and be able to use the analog stick as the dpad and the 4 buttons. I'm still working on getting it to use the start and L/R buttons, though.

[Henrik]

Thanks for the testing and the logs guys, this is still quite mysterious to me though...

I'll see if I can add some more error checking.

[theonyxphoenix]

No problem. I have a few other solutions to attempt. I don't know if it is a problem since the dpad is mapped internally to the same buttons as the stick and it is trying to use two different buttons simultaneously causing a crash. Perhaps clearing the mapping and mapping buttons from the start would help. I'm on a mission to find a solution.

[theonyxphoenix]

EDIT: When using as a native pad all of the buttons are recognized by the device and L/R can be mapped as built-in, same as the other 4 input buttons. It is only the directional inputs that cause the crash.

[theonyxphoenix]

So I found a solution to the problem.

The bad news is that it is more of a band-aid solution since it doesn't fix the problem with ppsspp crashing with the pad as native.

The good news is that I found a workaround to get all of the buttons to work. PPSSPP supported the Bluez IME but not native, however Bluez didn't recognize some of the Steelseries Free buttons. After some digging I found a developer build specific for this type of controller which lets me map all buttons and allows me to use it on PPSSPP. Here is the link where they had broken down the inputs and for anyone else that may use this type of controller:

http://code.google.com/p/android-bluez-i...ail?id=192

I don't know if the information contained there would help in determining the cause of the crash.