2 replies to this topic

[Dislogic]

Just thought I'd post my experience with the iControlPad (Firmware 2.0) and the Galaxy S3 (Android 4.0.4), running Snes9x and MD.emu. Some of these issues may get fixed in future updates of the OS/iCP Firmware/Snex9x/MD.emu, but for now, here are some things to try if things aren't working for you, or wondering where to start...

First Time;
-If you've been mucking around with the iCP trying to get it to work, set it back to the factory defaults;
Reset the toggles on by holding X + Y + A + B and pressing start for 3 seconds. Turn the iCP off again for the next step (hold start for 5 seconds).
-For Snes9x EX, start the iCP in "SPP Mode" which is by holding down Y + Start for 3 seconds while it's off. The "mode" is kind of like "what language should the iCP talk?". "Should I be a keyboard? a joystick? a mouse?" We want it to be native iCP because Snes9x understands it, and with minimal lag which is SPP Mode.
-Install Snes9x EX - (1.4.29), setup your ROM path, Setup Input Player Mapping, this tells Snes9x that iCP will be player 1. Input/Player Mapping -> iControlPad 1 -> 1

Every other time;
-Turn Bluetooth on the phone, but don't pair. This is because Bluetooth is controlled within Snes9x EX, and not the phone OS.
-Turn the phone on (hold down 3 seconds, green light will flash)
-Open Snes9x EX and "Scan for Wiimotes/iCP/JS1" - This is a Bluetooth scan.
It should say;
"Starting Scan…"
"Checking 1 device"
"iControlPad 1 Connected"
The iControlPad should go solid green, but sometimes it keeps blinking slowly...
-Hit up and down on the D-Pad and the menu should scroll around.
-Load Game and Enjoy!

Stuff that goes wrong;
Problem:
After "Starting Scan…" you get "Failed reading a device name"
Try:
"Scan for Wiimotes/iCP/JS1" again. This seems to happen sometimes when trying to connect to the iCP too quickly after a boot.

Problem:
Errors connecting.
Try:
Make sure that the iCP is in SPP Mode, and no toggles are on (see up top)

Problem (Very common):
iCP Connects, but Snes9x is unresponsive
Try:
Options -> Input -> iControlPad Key Config -> Gamepad Controls
Select any key, and when prompted to "Push a key to set" hit buttons on the pad. If the screen responds, good news, and you just need to map all your buttons their corresponding actions. You only need to do this once.
Try:
I seem to have to do this pretty often. "Disconnect Bluetooth" and try again.
And again…
Try:
If after 3 or so times of trying to disconnect and reconnect and still no response, Uninstall the app, and install again. (All your game saves and screen shots will be saved). Try the Connection steps again. I seem to need to do this occasionally…

Whenever you suspend the app, you'll have to go through the "Every other time" steps again, and often that means, going through the problem steps...I hope this helps someone!

I'll post my instructions for MD.emu soon. It won't work on my S3 in SPP mode, it only works in Keyboard mode…

[Craigix]

Nice post, thanks for all the info for S3 users.

Will sticky.

[Dislogic]

I'm giving up for the moment. MD.emu seems to only work when the iCP is connected in keyboard mode, but the S3 interprets Y and X as volume up and down...making it impossible to play. I'll muck around after enjoying some SNES