Work. But:
button Work only “A” (test NES and Sega), other (B,X,Y) not work, i pres “B” and nothing, press “B” on screen (overlay) - Hero Jumping, Press “A” hero Shooting, pres “A” overlay hero Shooting.
I mistake code: wrong: X 188 Y 189 A 190 B 191 True X 189 Y 188 A 191 B 190
If i off “auto usb” and setup key manual, all keys work good. Also i connect TWO game pad (U912F) for play together all work good (if setup key manual).
JXD S7300b with TheXSample-SXELROM v3.5 (has an another driver as the stock rom)
port 0: noadc_joystick
A = Pad 0: 96, ac=0, src=1281 B = Pad 0: 97, ac=0, src=1281 X = Pad 0: 99, ac=0, src=1281 Y = Pad 0: 100, ac=0, src=1281
Left Stick up = Pad 0: x 0.00, y -1.00, z 0.00, rx 0.00, ry 0.00, rz 0.00, Left Stick down = Pad 0: x 0.00, y 1.00, z 0.00, rx 0.00, ry 0.00, rz 0.00, Left Stick left = Pad 0: x -1.00, y 0.00, z 0.00, rx 0.00, ry 0.00, rz 0.00, Left Stick right = Pad 0: x 1.00, y 0.00, z 0.00, rx 0.00, ry 0.00, rz 0.00,
Right Stick up = Pad 0: x 0.00, y 0.00, z 0.00, rx 0.00, ry -1.00, rz 0.00, Right Stick down = Pad 0: x 0.00, y 0.00, z 0.00, rx 0.00, ry 1.00, rz 0.00, Right Stick left = Pad 0: x 0.00, y 0.00, z 0.00, rx -1.00, ry 0.00, rz 0.00, Right Stick right = Pad 0: x 0.00, y 0.00, z 0.00, rx 1.00, ry 0.00, rz 0.00,
Dpad is the same as the left stick
L1 = Pad 0: 102, ac=0, src=1281 L2 = Pad 0: 104, ac=0, src=1281 R1 = Pad 0: 103, ac=0, src=1281 R2 = Pad 0: 105, ac=0, src=1281
Start = Pad 0: 108, ac=0, src=1281 Select = Pad 0: 109, ac=0, src=1281
Port 0:GreenAsia Inc. USB Joystick VID = 0E8F PID = 0002
Button1 Pad 0:188,ac=0,src=1281
Button2 Pad 0:189,ac=0,src=1281
Button3 Pad 0:190,ac=0,src=1281
Button4 Pad 0:191,ac=0,src=1281
Button5(L1) Pad 0:192,ac=0,src=1281
Button6(R1) Pad 0:193,ac=0,src=1281
Button7(L2) Pad 0:194,ac=0,src=1281
Button8(R2) Pad 0:195,ac=0,src=1281
Button9 Pad 0:196,ac=0,src=1281
Button10 Pad 0:197,ac=0,src=1281
up Pad 0:x 0,0, y 0,0, z -0,0, rz 0,0, down Pad 0:x 0,0, y 0,0, z -0,0, rz 0,0, left Pad 0:x 0,0, y 0,0, z -1,0, rz 0,0, right Pad 0:x 0,0, y 0,0, z 1,0, rz 0,0,
Port 0: USB Gamepad VID = 0079 PID = 0011
Button1 Pad 0:188,ac=0,src=1281 Button2 Pad 0:189,ac=0,src=1281 Button3 Pad 0:190,ac=0,src=1281 Button4 Pad 0:191,ac=0,src=1281 Button5 Pad 0:192,ac=0,src=1281 Button6 Pad 0:193,ac=0,src=1281 Button7 Pad 0:196,ac=0,src=1281 Button8 Pad 0:197,ac=0,src=1281
up Pad 0:x -0.99, y 0.00, z 0.00, rz 0.00, down Pad 0:x -0.99, y 0.00, z 0.00, rz 0.00, left Pad 0:x -0.99, y 0.00, z 0.00, rz 0.00, right Pad 0:x -0.99, y 0.00, z 0.00, rz 0.00,
I’m using the iPEGA controller in joystick mode as well and have some more info regarding the dpad. When setting up the custom binds for the controller, hitting either up on the dpad and up on the left stick during detect mode get bound as “DPAD UP”. Both the left stick and the dpad work to navigate the RetroArch setting menu. The problem is that in games only inputs on the left stick actually seem to be registered by the game , rather than the dpad.
It seems like hitting up on the dpad up should register DPAD UP, and hitting up on the stick should register something like STICK UP. Right now they both register to the same command, but only the less useful stick works when in-game. I should add that the right stick never seems to be detected in the custom binds menu.
Using the debug feature shows the same results as Matroc. EDIT: screwing around some more I can confirm that the dpad works in the android menu and works properly in several apps, including SuperGNES, NYTimes and Talk.[/quote]
Hello fellow iPega users. I bought an iPega a while ago since it seemed like the best blend of features I wanted: small controller, comfortable analog sticks and SNES-like button layout, and good phone holder.
Unfortunately as you have all seen, RetroArch had some problems with its iPega support. Well, I’m a programmer and I’ve contributed to a few open source projects in the past, so I got the source for RetroArch and was able to debug the issues. See Pull Requests 244 and 255 on the RetroArch github repo. These have both been merged, so the next official version should have good iPega support.
In case you’re curious, there were 3 issues: [ul] [li]a bug which meant the wrong “iCade profile” would be used for pads (in Settings - Input you can have “iCade profiles” for pads 1 to 4 but because of two small off-by-one errors the profile you needed to set for your first controller was profile 3)[/:22w6q353][/li][li]wrong button mappings (the buttons were mapped according to the letter on the physical button on the controller, not SNES layout which RetroArch seems to use as a standard[/:22w6q353][/li][li]the iPega’s d-pad actually sends HAT_X and HAT_Y events, so RetroArch’s dpad emulation didn’t work with the actual d-pad when in games, but it picked up inputs from the left analog stick instead, as you all saw[/*:22w6q353][/li][/ul]
None of these bugs was extremely obvious (well maybe apart from the first), you really needed to test with the actual controller to fix them.
Apparently on Android 4.1.x you could use Bluez IME to get past some issues, but this no longer worked on 4.2.x.
Hopefully, in the next official RetroArch build, the iPega should work correctly out of the box. What you need to do: [ul] [li]Turn on the iPega in joystick mode (hold X + Home button)[/:22w6q353][/li][li]Pair it with your phone[/:22w6q353][/li][li]In RetroArch Settings - Input, use automatic detection, and go into “iCade Profile for Pad 1” and select the iPega there.[/*:22w6q353][/li][/ul]
I have a Galaxy Nexus with Android 4.2.1 and with the fixes I’ve made it works like a champ!
Hope this helps.
I’m using the iPEGA controller in joystick mode as well and have some more info regarding the dpad. When setting up the custom binds for the controller, hitting either up on the dpad and up on the left stick during detect mode get bound as “DPAD UP”. Both the left stick and the dpad work to navigate the RetroArch setting menu. The problem is that in games only inputs on the left stick actually seem to be registered by the game , rather than the dpad.
It seems like hitting up on the dpad up should register DPAD UP, and hitting up on the stick should register something like STICK UP. Right now they both register to the same command, but only the less useful stick works when in-game. I should add that the right stick never seems to be detected in the custom binds menu.
Using the debug feature shows the same results as Matroc. EDIT: screwing around some more I can confirm that the dpad works in the android menu and works properly in several apps, including SuperGNES, NYTimes and Talk.[/quote]
Hello fellow iPega users. I bought an iPega a while ago since it seemed like the best blend of features I wanted: small controller, comfortable analog sticks and SNES-like button layout, and good phone holder.
Unfortunately as you have all seen, RetroArch had some problems with its iPega support. Well, I’m a programmer and I’ve contributed to a few open source projects in the past, so I got the source for RetroArch and was able to debug the issues. See Pull Requests 244 and 255 on the RetroArch github repo. These have both been merged, so the next official version should have good iPega support.
In case you’re curious, there were 3 issues: [ul] [li]a bug which meant the wrong “iCade profile” would be used for pads (in Settings - Input you can have “iCade profiles” for pads 1 to 4 but because of two small off-by-one errors the profile you needed to set for your first controller was profile 3)[/:3viqwrr0][/li][li]wrong button mappings (the buttons were mapped according to the letter on the physical button on the controller, not SNES layout which RetroArch seems to use as a standard[/:3viqwrr0][/li][li]the iPega’s d-pad actually sends HAT_X and HAT_Y events, so RetroArch’s dpad emulation didn’t work with the actual d-pad when in games, but it picked up inputs from the left analog stick instead, as you all saw[/*:3viqwrr0][/li][/ul]
None of these bugs was extremely obvious (well maybe apart from the first), you really needed to test with the actual controller to fix them.
Apparently on Android 4.1.x you could use Bluez IME to get past some issues, but this no longer worked on 4.2.x.
Hopefully, in the next official RetroArch build, the iPega should work correctly out of the box. What you need to do: [ul] [li]Turn on the iPega in joystick mode (hold X + Home button)[/:3viqwrr0][/li][li]Pair it with your phone[/:3viqwrr0][/li][li]In RetroArch Settings - Input, use automatic detection, and go into “iCade Profile for Pad 1” and select the iPega there.[/*:3viqwrr0][/li][/ul]
I have a Galaxy Nexus with Android 4.2.1 and with the fixes I’ve made it works like a champ!
Hope this helps.[/quote]
Amazingly well timed contribution. 
Twinaphex/Squarepusher just had an iPega arrive this week and was planning on doing some testing with it this weekend!
I’ll clone and build your repo later tonight if I’m not too drunk, and let you know how it tests over here.
From: http://sinjul.wordpress.com/2012/06/01/datel-arcade-pro/
One switches between PS3 and Xbox360 mode by holding the “Turbo” Button while plugging the stick into the console or PC.
Cool, let me know if you run into any issues. Actually all my pull requests have already been merged so you could probably just clone and build the official repo (https://github.com/libretro/RetroArch).
Any idea when there will be an official build out with these changes?
There should be a new release out with updated code and the Stella Atari core in the next few days.
Sorry I don’t want to nag, but is there any word on the Datel Arcade Stick? As there seems to have been no offical feedback on this stick.
Myself and Shoesy posted information on it. I am happy to provide any further info if it helps.
Thanks for all your hard work.
First of all, good job on this awesome emulator.
Here is my small contribution to support a great stick :
HORI CO.,LTD REAL ARCADE PRO.V3
Button / Data Displayed
Top row of 4 buttons 1 / 96 ac=0 src=1281 2 / 99 ac=0 src=1281 3 / 101 ac=0 src=1281 4 / 100 ac=0 src=1281
Bottom row of 4 buttons 5 / 97 ac=0 src=1281 6 / 98 ac=0 src=1281 7 / 103 ac=0 src=1281 8 / 102 ac=0 src=1281
Playstation Home button / 110 ac=0 src=1281 Select / 104 ac=0 src=1281 Start / 105 ac=0 src=1281
up / x=0, y=0 right / x=0, y=0 down / x=0, y=0 left / x=0, y=0
Same problem as post 101, the directions map ok as DPAD UP, DPAD RIGHT etc when binding by hand, but fail to react ingame.
Fingers crossed to have this supported in the next release 
Hi.
I have some remarks and questions regarding the MOGA Pro support in RetroArch.
First thing : I only use the official MOGA Pivot app. I tried a few times to configure the generic driver-thing available on the Play Store, but I couldn’t make it work.
When I put the controller in A mode, Retroarch doesn’t recognize it at all, pure and simple. I can try to manually bind every keys, Retroarch just doesn’t register the button I press or the sticks I move on the controller.
When I put it in B mode, which is the HID mode, I can configure every buttons of the controllers, except for the two analog triggers. I think I read somewhere in this thread that this is a known issue with analog triggers (and analog sticks, which don’t work as analog but only like a standard D-pad), but as you fixed it for the 360 pad in the latest release, maybe you will fix this for the MOGA in a future version.
Finally, here is something I have thought : MOGA provides an SDK for developers, in order for them to easily add support for MOGA controllers in their games. Maybe you could request one of those SDK : this could be easier for you to add automatic configuration for MOGA controllers. Just to be clear : I am no developer by any mean, and it’s maybe a stupid idea.
Anyway, whatever you decide, thanks you for your work and the massive amount of time you put in this app.
Port:0 OUYA Game Controller
Pad 0 , src=1281, ac=0 (For all control buttons)
U= 99 O= 96 A= 97 Y= 100 L1= 102 L2= 104 L3= 106 R1= 103 R2= 105 R3= 107 Ouya Center Button= 82
DPAD Directional Buttons: UP= 19 Down= 20 left= 21 Right= 22
OUYA Left Joystick: UP: Pad 0: x=0.00, y= -1.00, src=16777232 DOWN: Pad 0: x=0.00, y=1.00, src=16777232 LEFT: Pad 0: x=-1.00, y=0.00, src=16777232 RIGHT: Pad 0: x=1.00, y=0.00, src=16777232
Port 0:GreenAsia Inc. USB Joystick
VID = 0E8F PID = 0002
Button1 Pad 0:188,ac=0,src=1281
Button2 Pad 0:189,ac=0,src=1281
Button3 Pad 0:190,ac=0,src=1281
Button4 Pad 0:191,ac=0,src=1281
Button5(L1) Pad 0:192,ac=0,src=1281
Button6(R1) Pad 0:193,ac=0,src=1281
Button7(L2) Pad 0:194,ac=0,src=1281
Button8(R2) Pad 0:195,ac=0,src=1281
Button9 Pad 0:196,ac=0,src=1281
Button10 Pad 0:197,ac=0,src=1281
up Pad 0:x 0,0, y 0,0, z -0,0, rz 0,0,
down Pad 0:x 0,0, y 0,0, z -0,0, rz 0,0,
left Pad 0:x 0,0, y 0,0, z -1,0, rz 0,0,
right Pad 0:x 0,0, y 0,0, z 1,0, rz 0,0,
Can you do an autodetect for the Impulse Controller (http://www.impulsecontroller.com)? I’m thinking perhaps not, but thought I’d ask just to be certain.
I just went through this thread and got the sense that “Broadcom Bluetooth HID” is insufficiently specific to identify the device, and the iCade mode makes Squarepusher cranky. I’m pretty sure iCade was implemented the way it was in order to sneak in iOS App Store support as a bluetooth keyboard. Ahh, 2011.
There are several modes for the the Impulse Controller device, so it can do iCade as well as “universal OS,” which sends key commands similar to iCade. It only has up/down/left/right, 4 face buttons, and 2 back buttons (fewer than a SNES) so should I just stick to manual mapping in RetroArch?
Manual mapping works, and it’s nice to be able to only do it once since RetroArch has so many different cores.
Ok Square here is the logcat from the moment I hooked up my DS3. It’s weird but it does say Gamepad 0… it’s authentic Sony bought from a Sony Center recently but IDK…
I/EventHub(24844): New device: id=7, fd=308, path='/dev/input/event4', name='Gamepad 0', classes=0x141, configuration='', keyLayout='/system/usr/keylayout/Vendor_054c_Product_0268.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false, usingSuspendBlockIoctl=true, usingClockIoctl=false
I/InputReader(24844): Device added: id=7, name='Gamepad 0', sources=0x01000511
UP: Pad 0 : 19, ac = 0, src = 1281.
DOWN: Pad 0 : 20, ac = 0, src = 1281.
LEFT: Pad 0 : 21, ac = 0, src = 1281.
RIGHT: Pad 0 : 22, ac = 0, src = 1281.
SELECT: Pad 0 : 109, ac = 0, src = 1281.
START: Pad 0 : 108, ac = 0, src = 1281.
SQUARE: Pad 0 : 96, ac = 0, src = 1281.
TRIANGLE: Pad 0 : 97, ac = 0, src = 1281.
CROSS: Pad 0 : 99, ac = 0, src = 1281.
CIRCLE: Pad 0 : 100, ac = 0, src = 1281.
L1: Pad 0 : 102, ac = 0, src = 1281.
R1: Pad 0 : 103, ac = 0, src = 1281.
L2: Pad 0 : 104, ac = 0, src = 1281.
R2: Pad 0 : 105, ac = 0, src = 1281.
L3: Pad 0 : 106, ac = 0, src = 1281.
R3: Pad 0 : 107, ac = 0, src = 1281.
Maybe a later revision… or black market. I don’t know
Wanting to use my new 8-Bitty with RA, and see that it doesn’t have native support yet. It looks like some people were working on getting it working, but that was months ago. I would be happy to submit logcats or other things if it would help at all.
Also, it seem the 8-Bitty and other iCade products are wonky to program for, and the likelihood seems high that it won’t ever get supported. Seeing as BlueZ IME no longer will work since 4.2.2 (I’m using 4.3 on my 2013 Nexus 7) it seems that the best course of action would be to either root and ROM my Nexus, or purchase a different controller.
If the 8-Bitty is not likely to be added anytime soon, whats a much better Bluetooth controller that natively supports an IME or is good to use with RA? Is there any resource anywhere that lists Bluetooth controllers and their various compatibilities?
Hi Squarepusher, can you confirm whether you have already been supplied with the codes for the Android Bluetooth Gametel gamepad?
http://www.amazon.co.uk/dp/B006L2HBXA/ref=pe_385721_37038051_pe_217191_31005151_M3T1_dp_1
If not, here are the codes:
UP: Pad 0 : 19, ac = 0, src = 0.
DOWN: Pad 0 : 20, ac = 0, src = 0.
LEFT: Pad 0 : 21, ac = 0, src = 0.
RIGHT: Pad 0 : 22, ac = 0, src = 0.
SELECT: Pad 0 : 109, ac = 0, src = 0.
START: Pad 0 : 108, ac = 0, src = 0.
SQUARE: Pad 0 : 99, ac = 0, src = 0.
TRIANGLE: Pad 0 : 100, ac = 0, src = 0.
CROSS: Pad 0 : 23, ac = 0, src = 0.
CIRCLE: Pad 0 : 4, ac = 0, src = 0.
L1: Pad 0 : 102, ac = 0, src = 0.
R1: Pad 0 : 103, ac = 0, src = 0.
Thanks.
I need the HID name as well. See the OP (Original Post) in this thread.
If anyone is having issues with the iControlpad I have found mine works perfectly if you make sure to hold down the X button when you turn the iControlpad on so that it is in Joystick mode. At least it worked perfectly last night for me. The iControlpad will remember what mode it is in so you don’t need to do that every time.