24 replies to this topic

[Okapi]

I have an LG Optimus 2X, and my girlfriend has an Optimus One (the same as the S model, I believe), and we were wondering if anyone has tried these phones with the iControlPad. When trying to connect Wiimotes in the emulator I get the dreaded "bluetooth not accessible" message, which got me kind of worried here. I know there are custom ROMs available that apparently solve the problem, but if I could get it to work on stock firmware that would be excellent. Any takes?

[SNES Fan]

I have an LG Optimus 2X, and my girlfriend has an Optimus One (the same as the S model, I believe), and we were wondering if anyone has tried these phones with the iControlPad. When trying to connect Wiimotes in the emulator I get the dreaded "bluetooth not accessible" message, which got me kind of worried here. I know there are custom ROMs available that apparently solve the problem, but if I could get it to work on stock firmware that would be excellent. Any takes?

Go to the market and download Bluez IME. It installs ass keyboard input. There is an earlier version that has Wiimote support so I would look into that. Also, with that version, you may have to flash a different kernel depending if the Wiimote/iControlPad connects or not. So far, I an using the iControlPad with my Droid Incredible with an HTC Sense ROM. HTC devices with HTC Sense and Samsung devices with Galaxy S aka Touchwiz generally have crappy bluetooth. Luckily, I found out this iControlPad can be connected to my type of phone via Bluez IME. I can assign buttons to the controller and it works with all emulators. Only emulator that doesn't need it is Fpse which is a great PlayStation emulator that has its own support with iControlPad. So I was able to keep Sense and still use my TV out cable, but still have this beautiful unit as a usable controller. Hopefully this helps

[Okapi]

Thank you for the quick reply. I just got off the phone with LG, and they told me they had disabled bluetooth HID on their phones. Said they may or may not do anything about that with the upcoming 2.3 update, but to be honest I'm not holding my breath. I tried Bluez IME, and it seems to be able to find the Wiimote, however it does not connect ('mote just keeps flashing those four lights), and I can't seem to use it for anything. I guess I'll be keeping an eye on cyanogenmod then.

[kuru]

I just got off the phone with LG, and they told me they had disabled bluetooth HID on their phones.

Sorry to derail, but I'm curious, did they mention why in the world they strip away "free" features and, while at it, annoy the heck out of a certain kind of user?

[SNES Fan]

Yeah I think for your phone you'll love Cyanogenmod. It has much better bluetooth. I'm sorry if this sounds like a stupid question, but is your phone rooted?

[Okapi]

My phone is not rooted, I'm still running stock LG Android 2.2.

I just got off the phone with LG, and they told me they had disabled bluetooth HID on their phones.

Sorry to derail, but I'm curious, did they mention why in the world they strip away "free" features and, while at it, annoy the heck out of a certain kind of user?

I have absolutely no idea. I just sent them an email asking exactly that, as well as inquiring about any updates that might help. To be perfectly honest I expect a "don't know" in reply though. Worth a try.

[SNES Fan]

Would you ever want to root?

[Okapi]

Sure, it just seems a tad scary. Rooted my Samsung Galaxy Spica though, that was a relatively painless process.

[Gadgetoid]

I hate to sound the troll, but this is the very problem with Android. It's "too" open. It's so open that carriers can grab the source, cripple it, and ship it on their phones without any repercussions.

Of course, it's openness is also the very solution for this problem! You're free to stick a custom ROM on there which fixes all the carriers tomfoolery.

If you're running on a stock rom, for the most part you're not making the most of your phone. From back in the WinMo days, I know that the rom baking community produce some awesome results.

[SNES Fan]

Gadgetoid, I have to agree. I rooted my phone because I wanted more freedom of it and not be restricted by Verizon's bloatware. I think I have the right to not have that crap on there XP. I love custom roms.

Sure, it just seems a tad scary. Rooted my Samsung Galaxy Spica though, that was a relatively painless process.

I'd do some research on it if you can I recommend the XDA forms for all your needs and sign up is free. My process was easy to root too

[SNES Fan]

it has been confirmed it does work with LG phones, including Optimus Here's a video of proof and demonstration I found on youtube

[scorpio16v]

All from bluezIME supported gamepads can run on every Android device.
Even my Flexiview FV-1 Android TV Box can handle the iControlpad, although the bluezIME isn't accessable from the boxes market.

Here is a video from the setup of iControlpad on LG Optimus Speed.

[Okapi]

I'm still not entirely convinced, as the Optimus V is running a slightly different ROM than Optimus One (although they are basically the same phone), and the 2X shown is running Cyanogenmod. However the hardware can clearly do the job, so I'll try to be optimistic. Hopefully my iControlPad willl arrive next week, and I'll let you know then.

[scorpio16v]

..., and the 2X shown is running Cyanogenmod.

Yes, but I've tested bluezIME and the GamePro driver with Zeemote BT stick on stock ROM and even on Samsung Galaxy S (stock) before, without problems.
I've tested several gamepads on different Android devices, so I'm sure the iControlpad with bluezIME runns on every Android.
See the other videos in my youtube channel.

My link

[SNES Fan]

Yeah, its pretty much a sure thing

[Okapi]

The pad finally arrived, but I can't seem to get it to work. Bluez IME finds it sure enough, I select the right driver, and choose Bluez as input, but then what? Nothing happens, it just disconnects after a couple of minutes.

Edit: Bit more detail might be in order. This is what I do:

1. Navigate to Blueetooth settings, turn it on.
2. Search for and pair with the iControlPad (it now says "paired but not connected")
3. Open Bluez IME.
4. Select device to iControlPad.
5. Set driver to iControlPad.
6. Set input method to Bluez IME.
7. ..?

Here I'm lost. The emulators don't seem to take notice, and the iControlPad powers down. What am I doing wrong?

[scorpio16v]

Step 7. depends on the emulator, you have.

On some Emulators, you need to configure key mapping (point 3. in bluezIME).
It is possible to configure different profiles for the emulators.

Now, you can use the keymapping menue in the emulator to configure the keyinput.
On psx4droid it needs to activate "use input method".

Emulators like SNES9x EX even don't need bluezIME, they have native support for the iControlpad.

[Okapi]

Went over the whole process after leaving the pad to charge a couple of hours, now I finally got it connected. For some reason only the D-pad worked in SNES 9X out of the box, had to enter Key Config and remap the buttons. For some reason I couldn't use iControlPad Key Config, that one didn't react to my button presses at all. Very strange. Guess I'll keep experimenting.

[scorpio16v]

On SNES9x EX, don't activate bluezIME and don't change input methode.

- bluetooth on (Android device/iCP)
- In emulator menue "scan for Wiimotes/iCP"
- wait for the "iControllpad connected" message

that's all you need

[Okapi]

If I do that, though, I just get the "Bluetooth not accessible" message. I would seem I need Bluez IME, although I wouldn't mind doing without it.

I finally got the iControlPad working reliably. This is what I do to connect now:

1. Turn on the iControlPad.
2. Turn on Bluetooth.
3. Set input method to Bluez IME.

Then it seems to connect and stay connected for as long as I'm using it. If I do it in any other order, or say, start the process with Bluetooth already on, it doesn't work. Bit odd, but as long as there's a way to get connected I don't mind.