Wiimote not working Droid Bionic

[GoogleCodeExporter]

What version of BluezIME are you using?

Wiimote 1.11

What Android device do you have? What Android version?

Droid Bionic, Liberty Custom Rom

When I try to connect my Wiimote via Bluetooth, Bluez IME discovers it and then 
is unable to connect. The Wiimote lights blink and then shut off.

I used the Wiimote Controller App that is in the market which connects and 
registers keypress but doesn't work with Yongzh's emulators.

Using the alphaplusex emulators(NES.EMU, SNES9X EX) I can connect the Wiimote 
from inside the app.

Here are two logs I made that may be useful. Thanks for the time spent on this 
app 

Original issue reported on code.google.com by cronos1...@gmail.com on 14 Nov 2011 at 5:10

Attachments:

• alogcat.2011-11-14-00-00-53-0500.txt
• alogcat.2011-11-14-00-07-26-0500.txt

[GoogleCodeExporter]

Can you see the Wiimote as a device in BluezIME?
Can you select it and have it listed under "Select device" ?
I can make a debug version that outputs more data if you are willing to try it.

Original comment by kenneth@hexad.dk on 14 Nov 2011 at 10:14

[GoogleCodeExporter]

Yes sorry if my explanation wasn't clear. 

I goto select device and hit scan and press 1+2 on my wiimote. It scans and 
discovers the Wiimote but then doesn't actually connect and the wiimote shuts 
off. I attached a screenshot of what I see in Bluez IME.

I'll absolutely use a debug version and help you get this working on the Bionic 

Original comment by cronos1...@gmail.com on 14 Nov 2011 at 8:25

Attachments:

• screenshot-1321302002952.png

[GoogleCodeExporter]

Attached is a debug build that will show a lot of data in logcat.

Original comment by kenneth@hexad.dk on 16 Nov 2011 at 2:11

Attachments:

• [Bluez-IME-v1.11-Wiimote - DEBUG.apk](https://storage.googleapis.com/google-code-attachments/android-bluez-ime/issue-116/comment-3/Bluez-IME-v1.11-Wiimote - DEBUG.apk)

[GoogleCodeExporter]

Here is the log.

Original comment by cronos1...@gmail.com on 16 Nov 2011 at 8:13

Attachments:

• alogcat.2011-11-16-15-12-25-0500.txt

[GoogleCodeExporter]

Based on the log, it does not look like you tried to connect?
Did you, or have I made a broken debug build?

Original comment by kenneth@hexad.dk on 21 Nov 2011 at 1:47

[GoogleCodeExporter]

I did try to connect. Here's another log with no filters set. 

Original comment by cronos1...@gmail.com on 21 Nov 2011 at 7:12

Attachments:

• alogcat.2011-11-21-14-07-39-0500.txt

[GoogleCodeExporter]

I'm having the same issue here, I'm a little stretched for time but I can try 
and run that debug .apk thing when I can if that would help to see if there's a 
common problem.

Original comment by mio2...@gmail.com on 21 Nov 2011 at 10:43

[GoogleCodeExporter]

I will send you one from my bionic as well. I think this is a motorola issue, 
the developer that made Wii mote controller said he is working to fix this 
issue on his app, but that there's something that Motorola does that breaks the 
ime

Original comment by scottatt...@gmail.com on 27 Nov 2011 at 9:52

[GoogleCodeExporter]

That is really strange, there are absolutely no messages relating to Bluez IME 
in the log.

What I can see is that your device seems to support HID, which may cause a 
problem if Android thinks it is a Bluetooth Keyboard and just connects, because 
then BluezIME cannot connect, and since it is not really a keyboard, Android 
cannot handle it.

I need to test the .apk on my Phone to see if it outputs messages. I suspect 
that the debug package does not output the data I expect it to.

Original comment by kenneth@hexad.dk on 29 Nov 2011 at 3:20

[GoogleCodeExporter]

Just a quick thought, did you click on "Select IME" ?
On your screenshot, you have not done that.

Original comment by kenneth@hexad.dk on 30 Nov 2011 at 1:20

[GoogleCodeExporter]

yeah I did. You figured out the problem though I think. When I connect with 
Wiimote Controller app it recognizes the controller and registers keypresses. 
If I open up a keyboard it types letters but the emulators don't recognize it. 
I figure this means Android thinks it's a Bluetooth keyboard and the yongzh 
emulators aren't looking for that. Like I said the Snes9X and other emulators 
with built in Wiimote support can connect fine.

Original comment by cronos1...@gmail.com on 30 Nov 2011 at 1:28

[GoogleCodeExporter]

Ok.

If it is registered as a keyboard, you should be able to assign key mappings 
inside the emulators and it should work (no need for Bluez IME then).

If you can, try unpairing the wiimote, hopefully that will prevent the 
auto-keyboard mode.

Attached is a new debug version, that at least outputs some debug info in 
logcat with my phone.

Original comment by kenneth@hexad.dk on 2 Dec 2011 at 9:59

[GoogleCodeExporter]

Sorry, the build is broken for some reason, I will make a new asap.

Original comment by kenneth@hexad.dk on 2 Dec 2011 at 3:39

[GoogleCodeExporter]

New build

Original comment by kenneth@hexad.dk on 2 Dec 2011 at 6:31

Attachments:

• BluezIME-Debug.apk

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I've gotten this working with N64oid's built in Bluez IME (and the newest 
version of IME at this time, 1.14). It's probably because of what you stated 
before, would you like me to use your debug version so you will have more 
information?

Original comment by scottatt...@gmail.com on 23 Jan 2012 at 3:48

[GoogleCodeExporter]

I tested using an alpha build of Ice Cream Sandwich on my phone to see if I 
could map some controls to GTA III...it worked...so this doesn't seem to work 
with anything running Blur at all. It must a Blur issue. Maybe there's a way 
you can bypass it, but at the moment...I'd wait until they have a good working 
port of CyanogenMod going.

Original comment by scottatt...@gmail.com on 23 Jan 2012 at 5:09

[GoogleCodeExporter]

Ok, no need to use the debug version if it works for you now.
Interesting that they included the Linux Wiimote drivers in the Bionic kernel 
though.

Original comment by kenneth@hexad.dk on 25 Jan 2012 at 9:30

• Changed state: Done

[GoogleCodeExporter]

Well do understand that the ice cream sandwich ROM is in alpha...not everything 
works correctly quite yet. It still doesn't work right on my blur based 
gingerbread

Original comment by scottatt...@gmail.com on 25 Jan 2012 at 2:11

[GoogleCodeExporter]

Ok, then I misunderstood your comment 17.
I have not seen any error message or log from your phone, can you try the debug 
build and send me the log?

Original comment by kenneth@hexad.dk on 29 Jan 2012 at 4:24

• Changed state: Started

[GoogleCodeExporter]

i have the same issue.  i have a bionic with the stock rom.  i've tried the 
wiimote app and it allows me to type in text fields but in emus i cant assign 
buttons. ... i can do a couple but then it stops working, and never works in 
the game.

ive tried bluez and it does the exact same thing. i tried with yoe debug build 
- logs attached. i dont know if i captured what you need - let me know if you 
need more.

if this is a hid issue, what can be done? i want to get an icontrolpad, do you 
think it would have the same issues?

Original comment by trevor.t...@gmail.com on 30 Jan 2012 at 12:30

Attachments:

• alogcat.2012-01-29-16-14-20-0800.txt

[GoogleCodeExporter]

So here's an update for me. I am now able to get BluezIme to connect to the 
Bionic. Not sure what I was doing wrong before. The wiimote is working in 
N64oid through Bluezime perfectly.

However, when using PSX4Droid or FPSe(latest version) I can't get it to 
recognize the controller for programming virtual keys.

I booted up the ICS alpha and was able to get both FPSe and Psx4droid to 
recognize the Wiimote through Bluezime as a hardware keyboard. So I'm at a loss 
as to what's happening. I'll try and do a log of the working and non-working 
scenarios if I can't figure out how to make it work. 

I would just use the ICS rom but the output to my TV doesn't work.

Original comment by cronos1...@gmail.com on 30 Jan 2012 at 1:14

[GoogleCodeExporter]

Ha, so after scouring download sites I found a version of psx4droid newer than 
the one in the market. Not sure if this is the reason but after ALOT of trying 
I successfully have my Wiimote connected via Bluezime. Can't get rid of the on 
screen keypad but success is success. 

Also no analog stick support but I think that's a problem with the emulator. 

Original comment by cronos1...@gmail.com on 30 Jan 2012 at 2:39

[GoogleCodeExporter]

My iss ue is a bit different than Cronos's it seems.  My wiimote will connect 
with bluez.  But bluez, just like the wiimote app, will not work in emus.  It 
will type in text fields, but not function in the game / allow for button 
config (see above post).

I tried manually pairing the wiimote. I know the pin for the wiimote is the bt 
mac backwards (as described on the wiibrew page).  I took the mac, reversed it, 
and converted the hex to ascii so I could type it in - but the convered hex has 
non-printing characters so I can't input it.

Thanks for all your work - your app is great from everything I've read.

Original comment by trevor.t...@gmail.com on 30 Jan 2012 at 3:30

[GoogleCodeExporter]

If the controller connects and you can type in text fields, it is probably 
because the emulator does not read the keyboard input. For the n64oid, snesoid 
and other *oid emulators there is a setting under "Other" that is called 
something like "Enable input method" that will instruct them to read the data. 
I know that some emulators (the Amiga one?) does not have an option for this, 
and does not work. Other emulators "just work". 

If you are using the *oid emulators, they have built-in BluezIME support. It 
works much better if you do not use the BluezIME interface, but instead 
configure the controllers inside the *oid apps. This will also allow you to get 
analog support.

Original comment by kenneth@hexad.dk on 30 Jan 2012 at 9:50

[GoogleCodeExporter]

God if I hadn't fixed my screen tonight from the last time I threw my Bionic 
against a wall I would throw it against a wall. 

After playing Castlevania Symphony of the Night for two hours last night with 
my classic controller I am once again unable to get PSX4Droid to recognize the 
controller for virtual keys. Registers key presses in rom select. 

Good news is that I'm able to connect to Bluez IME successfully almost every 
time with this newest version.

Original comment by cronos1...@gmail.com on 31 Jan 2012 at 5:49

[GoogleCodeExporter]

With snes ad I can 'turn on' the other input method. It gives me the same 
results I listed above.  I can type in fields but can't use it in the emulator. 
 with snes9x ex which had bullet in support it works.  Attached is a log of me 
trying to use the controller from snes ad and trying to program the buttons(and 
failing), and then using it in'color note' to type.

Let me know if you need a better log

Original comment by trevor.t...@gmail.com on 31 Jan 2012 at 7:26

Attachments:

• alogcat.2012-01-30-23-20-08-0800.txt

[GoogleCodeExporter]

With snes ad I can 'turn on' the other input method. It gives me the same 
results I listed above.  I can type in fields but can't use it in the emulator. 
 with snes9x ex which had bullet in support it works.  Attached is a log of me 
trying to use the controller from snes ad and trying to program the buttons(and 
failing), and then using it in'color note' to type.

Let me know if you need a better log

Original comment by trevor.t...@gmail.com on 31 Jan 2012 at 7:27

Attachments:

• alogcat.2012-01-30-23-20-08-0800.txt

[GoogleCodeExporter]

Yes, the log shows that you are connected and everything is working fine.
The problem is that the app does not read the data from the soft keyboard, 
which is why it works in some apps (Color Note) and not in others (SNES A.D.).

It seems that SNES A.D. is pulled from Market, do you know how I can get in 
touch with the author? Is there an email address or similar inside the SNES 
A.D. ?

Original comment by kenneth@hexad.dk on 20 Feb 2012 at 9:12

[GoogleCodeExporter]

I know the "oid" emulators' author is on SlideMe. 
I've been using the CM9 port that has been built for the Bionic as a daily 
driver now, and I'm glad to see that this works correctly when not using any 
blur-based ROMs. It's just sad that since this ROM is still in alpha, it's not 
running quite as well as stock or a blur-based ROM. Once the Bionic gets the 
Ice Cream Sandwich update, we'll see if Motorola fixed it, but I highly doubt 
that this will work on that either. A stock ROM like CyanogenMod seems to work 
the best. The problem seems to lie in Blur

Original comment by scottatt...@gmail.com on 21 Feb 2012 at 8:22

[GoogleCodeExporter]

I'm having the same problem but with the phonejoy, it works fine on N64oid, but 
no where else,it won't even trie to connect when I chose bluez ime for select 
ime. Maybe if it had a connect button like N64oid  it would work

Original comment by gioram...@gmail.com on 22 Feb 2012 at 2:12

[GoogleCodeExporter]

Based on another report, I think I have diagnosed at least a part of the 
problem.

It seems that the Bionic (and possibly all blur-based ROMs) does not activate 
the IME when not required.
This makes some sense, but all the other Android ROMs activate the IME as soon 
as it is selected.
Then it only pops it up when required, but keeps it loaded.

Since the Bionic does not load the IME, there is no starting signal. Due to the 
Android security model, it is not possible to bypass or force this starting of 
the IME. I will have a look to see if this is fixable, but it will be a little 
while before I can work on it.

Original comment by kenneth@hexad.dk on 8 Mar 2012 at 7:59

[GoogleCodeExporter]

I had dreams of playing ROMs with wiimotes on my bionic so I could HDMI out to 
a projector. Would've worked too, if not for pesky MOTOROLA :( 

I did get the wiimotes working properly with ROMS, but had to be on an ICS rom. 
But since bionic has locked bootloader, ICS roms for bionic still don't have 
HDMI out support at the moment.

Do you think you'll have a resolution for bionic on gingerbread? I completely 
understand if not (nobody seems excited for Gingerbread work these days), but 
I'm still hoping because seems there's a better chance of this getting an 
update than ICS for bionic being sent from motorola.

THANKS for all your efforts!

Original comment by paul.apa...@gmail.com on 7 May 2012 at 9:14

[GoogleCodeExporter]

Something like this would require me to get a Bionic, and then spend many hour 
digging through something that was probably not implemented and cannot be 
implemented without a custom ROM. I do not have the time or motivation to do 
that right now :(

Original comment by kenneth@hexad.dk on 8 May 2012 at 11:16

[GoogleCodeExporter]

Hey there,

NO PROBLEM, completely understand, but thought I'd just ask status on it. 

Thanks anyway :)

Original comment by paul.apa...@gmail.com on 8 May 2012 at 4:33

[GoogleCodeExporter]

Kenneth, thanks for all your work! I got a iControlpad and still have all the 
same issues so I'm glad you found the issue. I'm about ready to try a custom 
rom, but I may just wait for the official ics update. 

Paul, if you use an emulator that has built in bluez support then it works 
great. I for snes I use snes ex. I use (and love) Fpse for PlayStation. 

Original comment by trevor.t...@gmail.com on 15 Jul 2012 at 6:12

[GoogleCodeExporter]

Issue 179 has been merged into this issue.

Original comment by kenneth@hexad.dk on 27 Aug 2012 at 9:13

[GoogleCodeExporter]

Issue 179 has been merged into this issue.

Original comment by kenneth@hexad.dk on 28 Aug 2012 at 2:14