Author Topic: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners  (Read 29163 times)

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Version 3.0 will have an overhauled button mapping system with a lot more built-in profiles.  I'd like to create default profiles for as many devices as possible.

What I need:
 - The key codes/axis codes for the various buttons/sticks/triggers on the device/controller
     - Settings -> Input -> Controller -> menu -> Controller diagnostics (press buttons/sticks to detect codes)
 - Screenshot of the analog info window:
     - Settings -> Input -> Controller -> menu -> Analog info
 - Screenshot of the device info
     - Settings -> Advanced -> Device info (scroll down to bottom before taking a screenshot)
 - Which Android ROM you're using (e.g. stock, Sxelrom, CyanogenMod, etc.)

Still needed
Archos Gamepad
GameStick
JXD S7300

Complete
iControlPad
JXD S7800
Mad Catz C.T.R.L.R (M.O.J.O controller)
MOGA (Pro, Pro Power, Hero Power)
Nyko Playpad series
OUYA
PS3 (wired and wireless via Sixaxis app)
Rumblepad series PC controllers
Shield
USB N64 adapters
Xbox360 & XInput-based PC controllers (e.g. Logitech F710)
Xperia Play
« Last Edit: February 07, 2014, 09:47:07 PM by littleguy »
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline xperia64

  • Moderator
  • double
  • *****
  • Posts: 591
    • View Profile
    • My Apps
iControlpad Joystick Mode (start+x):
Dpad up: 188 keycode_button_1
Dpad right 189 keycode_button_2
Dpad down 191 keycode_button_4
Dpad left 190 keycode_button_3
L trigger 192 keycode_button_5
R trigger 202 keycode_button_15
Select 196 keycode_button_9
Start 197 keycode_button_10
B 201 keycode_button_14
X 200 keycode_button_13
A 199 keycode_button_12
Y 198 keycode_button_11
Left stick x+y axis
Right stick z+rz axis
http://imgur.com/ydpdoNv
http://imgur.com/zC6scfq
http://imgur.com/RmO5Onr

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Perfect, thanks :)
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners
« Reply #3 on: December 18, 2013, 10:03:43 PM »
@xperia64 Which iControlPad buttons would you recommend mapping to the L button and Z trigger?
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline xperia64

  • Moderator
  • double
  • *****
  • Posts: 591
    • View Profile
    • My Apps
Re: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners
« Reply #4 on: December 19, 2013, 05:33:07 AM »
iControlpad Buttons | N64 Buttons
X | A
A | B
L | Z
R | R
Y | L
Start | Start
Obviously dpad as dpad, left joystick as joystick, and right joystick as c buttons

Offline beansta

  • byte
  • *
  • Posts: 29
    • View Profile
Re: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners
« Reply #5 on: December 19, 2013, 08:06:57 AM »
Would u like the values for the iPega bluetooth gamepad too?
Devices:
Samsung Galaxy S3 LTE international
rXtreme v14.1 ROM and Perceus v36.2 kernel
1.7ghz Quadcore CPU and 533mhz GPU
1.77 GB useable RAM

Samsung Galaxy Tab 2 10.1 Wifi
Zap Blaster v2.2 ROM and Next v1.41 kernel
1.35ghz Dualcore CPU and 384mhz GPU
1006MB useable RAM


Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners
« Reply #6 on: December 19, 2013, 08:37:14 AM »
Sure!
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline beansta

  • byte
  • *
  • Posts: 29
    • View Profile
Re: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners
« Reply #7 on: December 23, 2013, 06:24:03 PM »
For some reason the iPega just shows up as a generic bluetooth gamepad under the analog info in mupen64+, so i guess the generic settings would work fine for it.
Devices:
Samsung Galaxy S3 LTE international
rXtreme v14.1 ROM and Perceus v36.2 kernel
1.7ghz Quadcore CPU and 533mhz GPU
1.77 GB useable RAM

Samsung Galaxy Tab 2 10.1 Wifi
Zap Blaster v2.2 ROM and Next v1.41 kernel
1.35ghz Dualcore CPU and 384mhz GPU
1006MB useable RAM


Abinav Katuru

  • Guest
Re: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners
« Reply #8 on: December 25, 2013, 10:58:12 AM »
I need help connecting the nyko playpad in general first. Got it for christmas and it shows both hid and app on and at the place where it shows icade, 1, 2 and mouse it shows icade is on even though it isn't connected to anything. If anyone knows how to solve this please reply asap! I will try to get a pic later.

Offline DigitalChilly

  • bit
  • Posts: 6
    • View Profile
Re: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners
« Reply #9 on: December 26, 2013, 04:28:04 PM »
I have the GameStick, JXD S7300b and JXD S7800b machines. I had to search around to find the menu entries you mentioned... they are not in the same location as your initial post. My question is... how on earth do you sideload the emu into the GameStick? I searched around but couldn't find a definitive answer.


Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners
« Reply #10 on: December 26, 2013, 05:15:56 PM »
According to all the reviews I have seen, there is no interface for side-loading apps onto the GameStick.  I actually just got one of these myself (haven't had time to do more than just fire it up).  I'll play around with it to see if there is a way to side-load apps using the SDK (presumably so, or developing for the thing would be virtually impossible).  Ultimately I'll need to look into what it would take to get published on their official store (assuming they are emulator friendly).  I glanced at the documentation recently, and it doesn't look too complicated.
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline Blackdisk

  • bit
  • Posts: 1
    • View Profile
Re: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners
« Reply #11 on: December 28, 2013, 12:08:59 AM »
nVidia Shield:
Dpad up: AXIS_HAT_Y: -1.00
Dpad Down: AXIS_HAT_Y: +1.00
Dpad Right: AXIS_HAT_X: +1.00
Dpad Left: AXIS_HAT_X: -1.00
Left analog Up: AXIS_Y: -x.xx
Left analog Down: AXIS_Y: +x.xx
Left analog right: AXIS_X: +x.xx
Left analog left: AXIS_X: -x.xx
Right analog up: AXIS_RZ: -x.xx
Right analog down: AXIS_RZ: +x.xx
Right analog right: AXIS_Z: +x.xx
Right analog left: AXIS_Z: -x.xx
Start: KEYCODE_BUTTON_START: 108
A: KEYCODE_BUTTON_A: 96
B: KEYCODE_BUTTON_B: 97
X: KEYCODE_BUTTON_X: 99
Y: KEYCODE_BUTTON_Y: 100
Right Trigger (R2): AXIS_RTRIGGER and AXIS_GAS: +x.xx
Left Trigger (L2): AXIS_LTRIGGER and AXIS_BRAKE: +x.xx
Right bumper (R1): KEYCODE_BUTTON_R1: 103
Left bumper (L1): KEYCODE_BUTTON_R1: 103


Stock Android

Offline DigitalChilly

  • bit
  • Posts: 6
    • View Profile
Re: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners
« Reply #12 on: December 28, 2013, 06:33:03 PM »
JXD 7300B
Stock kernel
Device 6 (adc joystick)

D-Pad Up : KeyCode: 19 : KEYCODE_DPAD_UP
D-Pad Down : KeyCode: 20 : KEYCODE_DPAD_DOWN
D-Pad Left : KeyCode: 21 : KEYCODE_DPAD_LEFT
D-Pad Right : KeyCode: 22 : KEYCODE_DPAD_RIGHT
Left Joystick same data as above.
Right joystick does nothing.

Button A : KeyCode: 96 : KEYCODE_BUTTON_A
Button B : KeyCode: 97 : KEYCODE_BUTTON_B
Button X : KeyCode: 99 : KEYCODE_BUTTON_X
Button Y : KeyCode: 100 :KEYCODE_BUTTON_Y
Button Select : KeyCode: 62 : KEYCODE_SPACE
Button Start : KeyCode: 66 : KEYCODE_ENTER
Button L1 : KeyCode: 102 : KEYCODE_BUTTON_L1
Button L2 : KeyCode: 104 : KEYCODE_BUTTON_L2
Button R1 : KeyCode: 103 : KEYCODE_BUTTON_R1
Button R2 : KeyCode: 105 : KEYCODE_BUTTON_R2

Analog Info just sits there and hangs... no output at all.

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners
« Reply #13 on: December 28, 2013, 07:18:24 PM »
Thanks digitalchilly.  Two questions:
 - When analog info "hangs" does it show a popup dialog with nothing in it, or is there no dialog whatsoever?
 - Are you able to actually get analog control working with the current version of the app? i.e. can you get mario to walk or does he always run?
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline DigitalChilly

  • bit
  • Posts: 6
    • View Profile
Re: Calling all Shield, JXD 7300/7800, Archos Gamepad, and GameStick owners
« Reply #14 on: December 28, 2013, 09:17:47 PM »
- When analog info "hangs" does it show a popup dialog with nothing in it, or is there no dialog whatsoever?

The popup appears with the blue "Analog Info" box and a line... but nothing under it. It just sits there doing nothing. I ran the same thing on the JXD 7800B and it works, the dialog pops up with all sorts of info.

 - Are you able to actually get analog control working with the current version of the app? i.e. can you get mario to walk or does he always run?

On the 7300 Mario RUNS everywhere once you setup the controls. On the 7800 it works perfectly right out of the box. Mario walks and runs  8)

Speaking of the JXD 7800B... I was going to send all the Controller Diagnostics but I realized that every key/stick is set to "ADC keytouch" and is simple different X&Y axis values. The only exception are the four shoulder buttons... they are not setup to do anything out of the box.
I think the biggest difference is that on the 7300 the default N64 emu is not Mupen64, but on the 7800 it is the default emu... so all of the settings are pre-done and work.