Bluetooth Keyboard

[Arcamonde]

Hi there,

I am using a bluetooth keyboard as my external controller except I have come across an interesting issue. The only keys which seem to work with any reliability in the emulator are the arrow keys. The others do not perform their mapped function, but whatever I set on the arrow keys seems to work. I can sometimes get the other keys to perform a mapped action, but only if I hit it repeatedly, which it may then go off. Does anyone have an idea as to why this is happening?

Thanks,

-Arcamonde

[Arcamonde]

Does no one have an idea as to why this is happening? Even speculation would be appreciated.

Thanks,

-Arcamonde

[xperia64]

Not entirely sure either, but when I was working on a NDK app that used SDL a while back, I think only the arrow keys and the cut/copy/paste buttons worked (not entirely sure about the arrow keys, but the alphanumeric keys didn't work and the special cut/copy/paste buttons did).

[Jay Haru]

Not entirely sure either, but when I was working on a NDK app that used SDL a while back, I think only the arrow keys and the cut/copy/paste buttons worked (not entirely sure about the arrow keys, but the alphanumeric keys didn't work and the special cut/copy/paste buttons did).

Well, one reason is prolly the bt driver/stack... what os version are you using?

[xperia64]

Note that this wasn't drastic, but different app I was working on. It was 4.0.4. The keys worked in normal android stuff like the web browser, but they didn't even register in my NDK app besides the ones I mentioned.

[Jay Haru]

Note that this wasn't drastic, but different app I was working on. It was 4.0.4. The keys worked in normal android stuff like the web browser, but they didn't even register in my NDK app besides the ones I mentioned.

I was actually asking the op but, you know... I tend to quote the guy above me...

[beansta]

From android 4.2 google introduced new bluetooth stack drivers. unfortunately for devices built before 4.2 was released they would no longer work in Gamepad mode (due to huge lag issues with callbacks on the input).any of the other controllers WILL work in keyboard mode however DraStic doesnt like this mode at all and wont register inputs with this method. the only way to get around this (the way i did it) was to use USBBT joycenter, and fool drastic into thinking i had a controller in Gamepad mode when infact i had it in keyboard mode and had buttons remapped in the Joystick app. The app in question costs money too however.

this is currently the only workaround to getting 'keyboard' mode controllers to work on drastic on 4.2+