Analog Controller FAQ and Compatibility List

[littleguy]

No problem reviving this thread - it's a FAQ and a sticky, it's meant to be revived and kept up to date

That's a cool looking controller at a fair price, thanks for bringing it to our attention.  Do you own this controller, and are you running Android 3.1 or higher?  If so, you can help us get it working by doing the following:
 - put it in "joystick mode" and connect it to your device (keyboard mode won't allow analog input)
 - in mupen, go to Settings->Input->Controller->(menu)->Analog info and report *exactly* what you see
 - in the same menu, also try "Controller info" and report what you see for the ipega controller

[onthebridge]

I am planning on buying it, but i have found this video and review where someone tries it with mupen64AE:

http://www.youtube.com/watch?v=xVHxv-sUtY0 [nofollow]
http://www.infinityreviews.com/2013/04/ipega-bluetooth-controller-review.html [nofollow]

[littleguy]

Looks like it will work perfectly right out of the box (as long as you're using Android 3.1 or higher).  Thanks for the links. 

[giblet]

Tested

Nexus 4 (4.2.1) / Acer Iconia A511 (4.1.2)
iControllpad in HID Gamepad mode ( X and Y + start ) (latest firmware 2.5a)

The gamepad can be enabled without a 3rd party app like bluezIME in gamepad mode.
Preconfigured buttons:
A - A
X - B
right shoulder button - Z
Start - start
D-Pad - U,D,L,R
Left Analog - U,D,L,R analog

Other buttons needs to be mapped

In SPP mode, you can use the iControllpad with bluezIME, but without analog input.

Have same setup - but can't work out how to use my iCP in Mupen?

There are no profiles for iCP?  How do I get it to be recognised.  I have followed the advice above and have started it in joypad mode but it's not automatically recognised....

Any help appreciated.


PS Is it because I am using the free version?

[littleguy]

The free and donation versions are identical, so that's not the issue.

You must be running Android 3.1 or higher.

As scorpio16v pointed out be sure to flash the icontrolpad's firmware to at least version 2.5a (see the bottom of the right-hand sidebar here).

Do NOT use bluezime or any other controller emulation app.  Just put the iControlPad in "HID Gamepad mode" as he describes.

Then go to Settings->Input->Controller and map your buttons and nubs.  If it doesn't seem to be working, please follow the instructions here and I'll see what I can do.

[- Hakuo -]

Is it possible to implement the WiiU gamepad?
found an Snes Emulator (snes9x EX+) that supports the pad without the use of another app, now i'm wondering, if such a feature is possible in Mupen, too?
Would love to play n64 in university, but with a nice controller

[xperia64]

http://code.google.com/p/emu-ex-plus-alpha/source/browse/imagine/src/bluetooth/

[- Hakuo -]

Well, thanks for the code, but i don't quite understand how to use something like that xD

[littleguy]

Connect your WiiU controller, open Mupen, and follow the instructions I posted above.  Then report back with what you see.  That will give us a better idea about what it will take for us to add support for it.

[- Hakuo -]

Well, acdtually i don't even get the gamepad to be connected with my pad... i used the wiimote app, becqause somewhere i read that they both use kinda the same signal, the app finds the pad via manual adress, but doesn't connect though... the four blue lights keep flashing, but don't switch to keeping nly one lighted up, like itis when connected to the SNES9X EX+ App :/

[littleguy]

Hmm, this will probably be a hard one for us to support, if it doesn't connect to Android natively or via a wiimote app.  Your best bet is to contact the various wiimote app developers and politely ask if they plan to add support for the Wii U controller.  If you mention that Robert Broglia's apps support it, and point them to his source code, and tell them you're willing to test it for them, you may have better luck.

[andytuinman3]

Hallo users,

My first post on the forum 

Wanted to let you know that i am currently testing the buttons on the archos gamepad.

Mapping:

N64 button / Archos button
Analog stick / Left analog stick
A button / A button
B button / X button
C buttons / Right analog stick (resized)
Z button / L shoulder button
R button / R shoulder button
Start / R2 button (underneath right analog stick)

All works well buttons work perfectly.

If you want to know more or want me to test more please let me know

[littleguy]

Cool, thanks.  But what do you mean by c-pad "resized".  Are you using the controls natively, or are you using the Archos touchscreen mapping software?  Ideally you shouldn't need touch emulation software with Mupen.

[andytuinman3]

Cool, thanks.  But what do you mean by c-pad "resized".  Are you using the controls natively, or are you using the Archos touchscreen mapping software?  Ideally you shouldn't need touch emulation software with Mupen.

The archos is compatible with mupen out of the box but since the a and b button are mapped on a and x there is not really great space for the c buttons. And for the games i play the c buttons are required (banjo kazooie) so i put the right analog stick on the c buttons and resized the analog stick (mapping tool) so that the up down left right on the analog stick are the c buttons. ( i find the dpad is on the wrong place for the c buttons.) Mostly this is how i find the button mapping the most efficient.

[littleguy]

Ok.  Mapping the right analog stick is pretty common for most people, including for ps3, xbox, playpad, icontrolpad, etc. controllers.  So nothing unusual there.  I'm still not sure why you need to use the mapping tool because mupen natively allows you to map an analog stick or trigger to a digital button (like c-pad).  Just want to be sure the instructions on the first post are as clear as possible.

Thanks for confirming