Yes, that's all well and good, but are any of them wireless? People want an alternative to the admittedly clunky Retron5 controller without the cords.HK Mktg wrote:We make a lot of aftermarket controllers. Hyperkin has two other brands, Tomee and Cirka. Search Amazon for them. I had RMA test all of them with the RetroN 5 and there have been no issues. My personal favorate is our GN6 controller.
Any aftermarket wireless controllers?
Forum rules
Retron 5 and it's predecessors are trademarked Hyperkin, Inc. Retron name is copyright Hyperkin, Inc. Content found in these forums may be copyright the respective developers and studios which said content is associated with. Retro5.net makes no claim legal or otherwise to this content and user submitted content is not screened. That being said, please refrain from posting or linking to full rom files so that everyone leaves us alone. Sometimes dogs are round.
Retron 5 and it's predecessors are trademarked Hyperkin, Inc. Retron name is copyright Hyperkin, Inc. Content found in these forums may be copyright the respective developers and studios which said content is associated with. Retro5.net makes no claim legal or otherwise to this content and user submitted content is not screened. That being said, please refrain from posting or linking to full rom files so that everyone leaves us alone. Sometimes dogs are round.
- hikaricore
- Site Admin
- Posts: 171
- Joined: May 22nd, 2014, 7:36 am
- Location: United States
Re: Any aftermarket wireless controllers?
Re: Any aftermarket wireless controllers?
Nothing is planned as far as more controllers. Honestly we don't get a lot of requests for an all new controller. Most who are not satisfied with the standard RetroN 5 controller feel fine with their retro controllers, or they just want the RetroN 5 controller with a D-pad.
Re: Any aftermarket wireless controllers?
I'd love to sync a PS4 or Wii U Pro controller right about now. The controller that came with my console had a shaky charge port to begin with right out of the box and just today it literally fell off into the inside of the controller.
Re: Any aftermarket wireless controllers?
Usually I'm going up to bat for you guys but dude seriously!?HK Mktg wrote:Nothing is planned as far as more controllers. Honestly we don't get a lot of requests for an all new controller. Most who are not satisfied with the standard RetroN 5 controller feel fine with their retro controllers, or they just want the RetroN 5 controller with a D-pad.
There are tons of complaints about the standard R5 controller. Nearly every reviewer has complained about it and just as many folks have asked about support for other blu tooth wireless controllers. The most common being folks asking (right on the hyperkin facebook page) for PS 3 controllers to be directly supported.
Just the other day a fan asked (on the hyperkin facebook page) if this product would be supported:
https://stacksocial.com/sales/the-nes30 ... -9.23.2014#
I echo the masses.
If we can get ips patching and turbo button support why can't we get a few more wireless control options?
Pretty please?
Playing 8 & 16 bit games on a 55 inch display from 6 feet away because of cord limitations can actually be quite punishing on the eyes.
Re: Any aftermarket wireless controllers?
Has anybody tried that controller or the ps3? hciattach is present on the system and it uses blueZ which is a pretty common bluetooth stack
maybe something like this: http://forum.xda-developers.com/showpost.php?p=9993128
the controller daemon started on startup does something like:
although it seems maybe it is looking for a hardcoded "Retron5Controller" device name so I'm not sure if the daemon will work as expected or maybe have to be disabled to allow alternate controllers
another werid bit of code in the controller daemon:
maybe they borrowed some of this from wiimote code?
maybe something like this: http://forum.xda-developers.com/showpost.php?p=9993128
the controller daemon started on startup does something like:
Code: Select all
/system/xbin/hciconfig hci0 lm MASTER,ACCEPT
another werid bit of code in the controller daemon:
Code: Select all
sprintf("", "$WII:%02X%02X%02X%02X%02X%02X", a12, v38, v22, v40, 0, v39);
Re: Any aftermarket wireless controllers?
username wrote:Has anybody tried that controller or the ps3? hciattach is present on the system and it uses blueZ which is a pretty common bluetooth stack
maybe something like this: http://forum.xda-developers.com/showpost.php?p=9993128
the controller daemon started on startup does something like:
although it seems maybe it is looking for a hardcoded "Retron5Controller" device name so I'm not sure if the daemon will work as expected or maybe have to be disabled to allow alternate controllersCode: Select all
/system/xbin/hciconfig hci0 lm MASTER,ACCEPT
another werid bit of code in the controller daemon:
maybe they borrowed some of this from wiimote code?Code: Select all
sprintf("", "$WII:%02X%02X%02X%02X%02X%02X", a12, v38, v22, v40, 0, v39);
I've tried to pair the nes30 with the Retron 5. It won't pair no matter what mode I try it in.
If I connect it via USB I can use the dpad but none of the buttons register.
That saddest thing is I got the NES30 for $30 shipped from China. It's a rock solid controller. It feels and plays (with the wii and pc) like it could take the same beating at the original NES controller it's design is inspired by.
Bonus the NES30 batteries last for 20 hours.
The Retron 5 controller 6-8 hours.
At $40 the Retron 5 wireless controller is a bad joke compared to the nes30.
Re: Any aftermarket wireless controllers?
are you tryng to use an .apk? or hci directly? or the stock hyperkin pairing process?dashv wrote: I've tried to pair the nes30 with the Retron 5. It won't pair no matter what mode I try it in.
Code: Select all
adb shell hcitool scan
shows the wiimote and a bluetooth dongle I have although I didn't really try to pair
Re: Any aftermarket wireless controllers?
I'm using the stock pairing on an unmodified Retron 5. I like running stock while still under warrantee.username wrote:are you tryng to use an .apk? or hci directly? or the stock hyperkin pairing process?dashv wrote: I've tried to pair the nes30 with the Retron 5. It won't pair no matter what mode I try it in.
Code: Select all
adb shell hcitool scan
shows the wiimote and a bluetooth dongle I have although I didn't really try to pair
The nes30 controller is firmware update able so I am kinda hoping either they add support for the Retron 5 or the Retron 5 adds support for it. Even if they just added support for wii controllers it should work.
I also kinda wish Hyperkin would add support for Wii-motes so we could use them to play light gun games.
Re: Any aftermarket wireless controllers?
@dashv you wanna make an omlet you may have to break some warranties
actually truth be told I don't know what the warranty is on r5 nor what might break it. the console is pretty roboust given that the 'maskrom' mode for flashing from rkbatchtool is pretty difficult to wreck. I flashed an image that didn't have a kernel at all on accident and was able to recover to stock without much issue.
one approach if you are not anxious to root might be to harness the factory testing script and the fact that hyperkin anticipated the controller-daemon being upgraded(none of this is tested, just an idea):
if /data/controller-daemon exists it will run that instead of /system/xbin/controller-daemon
so one could probably make use of the fact that retron tries to run as part of init.rc
and the fact that /data is mounted to the sd card when the recovery magic number is right
then write a script to replace '/data/controller-daemon' by actually mounting the correct partition (ie write to /dev/block/mtdblock6 instead of sd card where /data is currently mounted in recovery)
actually truth be told I don't know what the warranty is on r5 nor what might break it. the console is pretty roboust given that the 'maskrom' mode for flashing from rkbatchtool is pretty difficult to wreck. I flashed an image that didn't have a kernel at all on accident and was able to recover to stock without much issue.
one approach if you are not anxious to root might be to harness the factory testing script and the fact that hyperkin anticipated the controller-daemon being upgraded(none of this is tested, just an idea):
if /data/controller-daemon exists it will run that instead of /system/xbin/controller-daemon
so one could probably make use of the fact that retron tries to run as part of init.rc
Code: Select all
exec /sbin/busybox sh /data/bootscript.sh
then write a script to replace '/data/controller-daemon' by actually mounting the correct partition (ie write to /dev/block/mtdblock6 instead of sd card where /data is currently mounted in recovery)
Who is online
Users browsing this forum: No registered users and 3 guests