Originally Posted by garfnodie

I know, two different phones, three different versions of CM(6,7, and 9).

When you hit the 1+2 buttons, are you just tapping them, or do you press and hold them down until paired? Have you tried using the sync button the back at all?

Just tapping them once simultaneously. Haven't had to use the sync button cuz doing this has worked for me every time ::shrugs:: =L

Sent from my HTC_Amaze_4G using xda premium

Odd mapping

---

I'm using a wiimote with a classic controller.

When I press and release 'Up' on the D-Pad, wiimotecontroller displays this:

Pressed button WM1 -> 11
Pressed button WM1 -> 12
Pressed button WM1 -> 13
Pressed button WM1 -> 14
Pressed button WM1 -> 15
Pressed button WM1 -> 16
Pressed button WM1 -> 17
Pressed button WM1 -> 18
Released button WM1 -> 11
Released button WM1 -> 12
Released button WM1 -> 13
Released button WM1 -> 14
Released button WM1 -> 15
Released button WM1 -> 16
Released button WM1 -> 17
Released button WM1 -> 18

This happens when I pressed/released 'up' on the D-Pad. Something similar happens with the other directions and shoulder buttons where a range is registered instead of one single button. Any idea what's wrong?

same here

---

Originally Posted by selssar

I'm using a wiimote with a classic controller.

When I press and release 'Up' on the D-Pad, wiimotecontroller displays this:

Pressed button WM1 -> 11
Pressed button WM1 -> 12
Pressed button WM1 -> 13
Pressed button WM1 -> 14
Pressed button WM1 -> 15
Pressed button WM1 -> 16
Pressed button WM1 -> 17
Pressed button WM1 -> 18
Released button WM1 -> 11
Released button WM1 -> 12
Released button WM1 -> 13
Released button WM1 -> 14
Released button WM1 -> 15
Released button WM1 -> 16
Released button WM1 -> 17
Released button WM1 -> 18

This happens when I pressed/released 'up' on the D-Pad. Something similar happens with the other directions and shoulder buttons where a range is registered instead of one single button. Any idea what's wrong?

Any update on this? I'm having the same problem with the wii classic pro on my XOOM, all the other buttons that do this all register as same buttons so if you press one button in game it thinks all are being pressed and wigs out.
Other than that everything else works perfect, awesome app

I love this app but there hasn't been any development in more than a year now. And its still limited to vanilla android.

Figured I'd share with the class in case there were any on here who weren't previously aware the way I wasn't. If anyone has/would buy a ps3 dual shock sixaxis controller (as I'm now doing =))... Check out sixaxis Controller on android market -

https://play.google.com/store/apps/d...ntroller&hl=en

It's the same concept but it utilizes a ps3 controller instead AND it supports sense based roms to boot =). Just rocked some super metroid on my sense based amaze 4g =)

Sent from my HTC_Amaze_4G using xda premium

It works perfectly on Sony Ericsson Xperia Arc S

Has anyone tried the six axis with evo 3d running ICS? Someone above posted it works with sense, unfortunately I don't have a controller with me right now to try it.

Tried running this on my Galaxy Ace S5830i and just get the message 'Address family not supported by protocol' - is there any fix for this?

Originally Posted by phw8558

Has anyone tried the six axis with evo 3d running ICS? Someone above posted it works with sense, unfortunately I don't have a controller with me right now to try it.

It totally should. Hasn't failed to work with any device I've tried yet =)

Sent from my Turellular Amaze 4g using xda premium

Hey, OP speaking.

Lately I've started receiving more and more reports about new wiimotes (the ones "with motion plus inside", or more formally, the -TR ones) not working. I've already bought two (spending over $100) and none of them give me any trouble on any device. Also neither appear to be -TR even though they should be, according to people that suggested them to me. I want to fix issues with these wiimotes so the fact that I don't have one, is very frustrating.

So:
- do you know if these new remotes must somehow be "activated" (like for example paired with a fully updated Wii console) before they switch to the "-TR" mode?
- also, is anyone willing to trade (or donate or sell) a wiimote that is original (you got it with your Wii for example) and has been CONFIRMED to be "-TR" (its name when listed with other bluetooth devices, ends with "-TR") and doesn't work in my app? I desperately need one and I'm not willing to buy another one from an online store just to see it not having any problems on my side. Someone from EU would be super great so I don't have to deal with import duties. If you want I can trade with an amazon-purchased genuine black "like new" wiimote with motion plus inside -- that's what it says on the package. Works with the Wii just fine (even with games that require the motion plus), as well as with this app.

So -- anyone feeling like helping me and all the users of my app? Please?

Did anybody managed to get this to work on a Galaxy S2 with Stock ICS?
Website says:

• Samsung Galaxy S2 (fully upgraded to Ice Cream Sandwitch or better)

But all i get are "exchange errors"...
Running Stock LPI Firmware and using original wii remote.

Thanks,
Kusie