Problem connecting iCade 8-bitty, Bluez IME will not allow device to change

[GoogleCodeExporter]

What version of BluezIME are you using?
1.17

What Android device do you have? What Android version?
Droid RAZR, Android 4.0.4

What gamepad are you using?
Thinkgeek iCade 8-Bitty

What steps will reproduce the problem?

I initially set up Bluez IME to work with two Wiimotes. It seemed to work fine, 
but then I saw the iCade support and picked up a couple 8-bitty icade 
controllers.

Connecting them has been very difficult and I'm not sure why. I get them in 
search/pair mode, then set Bluez IME to scan for them- it ALWAYS finds them 
without an issue, however when I tap them in the "found devices" list... 
nothing. I am returned to the settings screen, with the old wiimote still 
listed as "Device #1" (or whichever I was attempting to use).

I then went into Android's bluetooth settings and saw that it could see the 
controllers, so I paired it with the first, and then tapped to disconnect it. I 
went back to Bluez IME, repeated the process and finally got it connected as 
device #1 and working.

I have been totally unable to replicate this success a second time- the second 
controller has yet to connect through Bluez IME, though it sees the second 
controller and recognizes its MAC address. I even tried reducing to one input 
device, just to see if I could consistently find a way to connect the second 
controller, but no- again Bluez IME refuses to budge from listing the first as 
Device #1.

Of course, I have changed the driver mode to iCade in all circumstances, and as 
I said it did work on the first one evnetually- and I believe I can reconnect 
the first controller and have it function as intended- I just can't figure out 
how or why, and I can't get my second 8-bitty assigned as Device #2 no matter 
what I do, even though both controllers now show up in the device list- I 
assume this is drawn from Android's "paired device" list. I've tried unpairing 
from Android, repairing, deselecting them as input devices under bluetooth- but 
really it's all random; I don't know what to try.

What is the expected output? What do you see instead?

I would like to be able to easily switch between devices and successfully 
assign and change devices at will.

Please provide any additional information below.

I listed most of it above- I have been trying to learn more about bluetooth and 
android in general to try to figure out what could be going wrong, but I'm 
afraid most of it is beyond me. I assume this has something to do with a 
conflict between Android trying to pair with the controllers and fighting 
8-bitty for the right, but I of course don't know.

When I connected the wiimotes, I got a few errors thrown, but in general it 
worked fine and both functioned- I never looked at Android's bluetooth settings.

Lastly, I'm curious if there's any way to back up the key mapping profiles 
created in Bluez IME? I've very much wanted to try a fresh install to see if it 
resolved anything, but I spent a lot of time making the profiles in the app and 
would hate to lose them all and have to redo it.

Original issue reported on code.google.com by emaranvi...@gmail.com on 29 Nov 2012 at 3:22

[GoogleCodeExporter]

What happens is that the iCade is actually presenting itself as a normal 
Bluetooth keyboard.
Whenever Android sees this, it connects and uses the keyboard (if it is paired).
Once Android has connected, the iCade refuses connections from Bluez-IME.
Occasionally it works if you disconnect the iCade, but other times, Android 
just re-connects.

This problem does not happen with the Wiimote, because your Android ROM does 
not have Wiimote drives, and thus ignores the bluetooth device, allowing 
Bluez-IME to connect.

Nothing I can do to fix it, Android does its thing before any of my code is 
called.

Original comment by kenneth@hexad.dk on 15 Jan 2013 at 7:43

• Changed state: WontFix

[GoogleCodeExporter]

Issue 199 has been merged into this issue.

Original comment by kenneth@hexad.dk on 15 Jan 2013 at 7:44

[GoogleCodeExporter]

Issue 206 has been merged into this issue.

Original comment by kenneth@hexad.dk on 15 Jan 2013 at 7:45