nesoid + wiimote

gorgalis

Well-known member
Apr 26, 2010
287
12
0
Has anyone tried connecting a wiimote to use while playing roms on nesoid? I connected my wiimote through WiimoteController and it is working properly. However when I go into the nesoid, I am unable to map the buttons. I try to remap them, but it doesn't see the remote.

I have tried...
Going into other options on nesoid to allow bluetooth controllers.
I tried going into the keyboard options for WiimoteController, but mapping those buttons has no effect either.

Does anyone have any ideas?

thanks.
 
I'm in the same boat as you, and I've spent the better part of a day trying to troubleshoot it. I don't think it's a problem with nesoid specifically, since I've tried a half-dozen different emulators.
 
I'm in the same boat as you, and I've spent the better part of a day trying to troubleshoot it. I don't think it's a problem with nesoid specifically, since I've tried a half-dozen different emulators.

Not sure if this helps, but the Sixaxis Controller app that I use with my PS3 Controller on NESoid requires that you go in and specifically set the 'Sixaxis controller' as the keyboard for the system. I had to first check the box for the 'keyboard' to enable it within the phone settings, and then also tell the Sixaxis Controller software to 'switch the input' to the Sixaxis.

I have a Wii Remote control upstairs and can try it if the app is free, but since I have the Sixaxis one.. i wont if its a pay-for app.
 
I tried the same thing on my D1 awhile back and I had the same issues and then I eventually gave up.


Sent from my DROID BIONIC using Tapatalk
 
Yes ChevyNovaLN, there are a couple free Wiimote apps. If you can try it out I'd appreciate it.

You say your Sixaxis works on the Droid Bionic specifically? Not another device?
 
I tried the same thing on my D1 awhile back and I had the same issues and then I eventually gave up.

I've been using the same configuration on my D1 for a while now, so I don't think I'm missing any configurations steps. (Yes, I've tried toggling the bluetooth input checkbox)
 
Yes ChevyNovaLN, there are a couple free Wiimote apps. If you can try it out I'd appreciate it.

You say your Sixaxis works on the Droid Bionic specifically? Not another device?

Actually, I just tried on my Bionic and the Sixaxis one wont work. Crap, It worked on my OG Droid. When I try to launch the Sixaxis 'driver' on the Bionic it doesn't look like it fully starts up and then my bluetooth turns off. Wont turn on again till I reboot. I e-mailed the 'company' that wrote it with some details, hopefully they're still developing it :)

So.. uh.. yeah. I'll see what I can do with the WiMote :) I'm bored enough.
 
I know the Sixaxis app requires rooting your device. Have you not rooted your Bionic yet?
(I'm curious, because I'll go buy any controller that works.)
 
I know the Sixaxis app requires rooting your device. Have you not rooted your Bionic yet?
(I'm curious, because I'll go buy any controller that works.)

Oh, if it requires root... i forgot. lol. My OG Droid was running CyanogenMod7 so I tend to forget those things. No, I have not rooted it yet. Was leaving it alone for at least a FEW days. haha
 
I've been using the same configuration on my D1 for a while now, so I don't think I'm missing any configurations steps. (Yes, I've tried toggling the bluetooth input checkbox)

Ok, you guys are not crazy. I think basically what we're running into is something similar to what was keeping things with the SenseUI on HTC phones... maybe something with the updated MotoBlur or whatever it is... is causing an issue. I watched some very detailed videos on the WiiMote stuff just to be sure I wasn't being ignorant either.. and it just doesn't work in NESoid. I did get it to type numbers in my text message, but it doesn't do anything within NESoid. its looking for a 'hardware key' and nothing on the Wii Remote works but i can press the 'search' button on my phone and it accepts that as an input key..

Grr. and yes, i will likely root my phone tomorrow. Turns out my wife is gone all weekend so I get to really be a geek longer than i thought!
 
The problem with MotoBlur was that it used a crappy Bluetooth controller. Since we're able to get the wiimote to connect, and send input to text fields, I don't think it's the same problem.

I tried rooting my Bionic and using the root-specific wiimote app. That didn't work either. It takes 10 minutes to root and try out your sixaxis... Come on, help us out tonight :D

(I just un-rooted my Bionic just fine, so don't worry about that)
 
The problem with MotoBlur was that it used a crappy Bluetooth controller. Since we're able to get the wiimote to connect, and send input to text fields, I don't think it's the same problem.

I tried rooting my Bionic and using the root-specific wiimote app. That didn't work either. It takes 10 minutes to root and try out your sixaxis... Come on, help us out tonight :D

(I just un-rooted my Bionic just fine, so don't worry about that)

Haha. ok fine. So basically, you just want ANY controller to work, period. Wii would be nice because you have one.... but you'd probably go buy a Sixaxis controller if it worked? :)
 
I think I speak for every Bionic user that will find this thread on Google when I say YES. I bought the wiimote for my OG. I would have grabbed a sixaxis, had it been working on Android at the time.

Your efforts are greatly appreciated, good sir!
 
I think I speak for every Bionic user that will find this thread on Google when I say YES. I bought the wiimote for my OG. I would have grabbed a sixaxis, had it been working on Android at the time.

Your efforts are greatly appreciated, good sir!

Rooted. Initial results are still 'negative' so i'm powering up my OG Droid to make sure I have EVERYTHING set the same. just in case.
 
  • Like
Reactions: software2
MotoBluuuuuuurrr!

Well, thank you for your efforts. Hopefully someone figures out a workaround eventually :(
 
MotoBluuuuuuurrr!

Well, thank you for your efforts. Hopefully someone figures out a workaround eventually :(

I wonder if it has something to do with the 'multi-touch keyboard' instead of the default 'android keyboard'. Obviously i'm switching the input method to the 'Sixaxis Controller' but still, I wonder if that just being there in general is the issue or if its really MotoBlurrrrrrrrrr :)