[Android Q&A, Help & Troubleshooting] AnonyMouse901:
CONTINUED...

I'll describe for the Kaiser Baas BT-130, but it's pretty much the same for the Acer as well.

Here are the procedures I have followed...

PROCEDURE #1

Starting with both phone and BT-130 keyboard powered OFF (keyboard is fully charged), turn both devices ON. The status bar at the top of the phone screen indicates Bluetooth is enabled.

Press and hold the BT-130 Bluetooth button until the blue light flashes.

In the phone's standard Bluetooth settings I make the device Discoverable, then click "Scan for Devices".

An entry in the phone's menu is displayed for "BlueTooth Wireless Keyboard", with a prompt to "Pair with This Device".

On clicking "Pair with This Device" I get a dialog that reads:

"Bluetooth pairing request. Type PIN to pair with Bluetooth wireless keyboard. (Try 0000 or 1234)".

Huh??? PIN???

After entering 0000 or 1234 or anything else, the entry for Bluetooth Wireless Keyboard reads "pairing..." for a while, then a dialog appears which reads "Attention. Pairing rejected by Bluetooth Wireless Keyboard."

Suspecting that this might be something to do with the absence of support for HID keyboards, I installed the BlueInput app from Teksoftco, then proceeded with...

PROCEDURE #2

This time, instead of going into the phone's standard Bluetooth settings as described above, I run the BlueInput app.

I select BlueInput's Scan button, and an entry appears for:

- Bluetooth Wireless Keyboard

- DC:2C:26:AF:EE:73

- Discovered

The blue light is still flashing on the BT-130, but when I press on the "Bluetooth Wireless Keyboard" item on the phone (just described above), the keyboard's blue light goes out (as it should for successful connection), and the message appears on the phone "Connected to Bluetooth Wireless Keyboard".

Then another message appears "Hint: before using BlueInput go to Android settings, Language & Keyboard, and make sure that ONLY BlueInput is checked". Also, now in place of Discovered the word Connected appears.

So I obediently go to Android settings --> Language & Keyboard, and yes, BlueInput is the only item checked.

PROOF OF CONNECTIVITY

As further proof there actually is connectivity between the two devices at this stage, pressing any key on the BT-130 keyboard results in an audible feedback click on the phone, but no letters/numbers from the keystrokes appear in any text input field of any phone app. However...

The BlueInput app provides a test screen for testing keyboard input, and I could, with restrictions, type into BlueInput's test screen from the keyboard.

The restrictions are that any keys other than the unshifted-alpha/numerics, spacebar and un-shifted punctuation produce a dollar sign ($) on the phone screen. Even pressing ESC, Tab, Caps, Shift, Enter, Backspace and any function key on the BT-130 keyboard produced a dollar sign on the BlueInput test screen.

But that's only in the BlueInput test screen. With any other text input field no characters appear at all, although the phone does always emit the audible keypress click-sound (because I have that feature enabled).

---------------------------

So I returned the Kaiser Baas BT-130 keyboard and brought home the Acer Iconia TAB A500/A100 series.

Not much to say, other than "See above". Pretty much exactly the same procedures and results as for the Kaiser Baas keyboard, so I returned it also.

---------------------------

I earlier had tried Kaiser Baas support but they were unable to help. Later on I received an update from the Technical Support Manager at Kaiser Baas, who stated as follows:

"...the phone/tablet must have hardware HID support, not software based. I have a Samsung Galaxy tab here purchased from HK. Our keyboards will connect but I cannot type with it. I found from Samsung, that the Galaxy tab sold in HK does not support HID devices, hence why it doesn't work. I would say that the Huawei phone has the same issue."

---------------------------

So there it is. Unless you guys have a suggestion, I can't see it is even worthwhile trying more keyboards, because it looks like I'm going to keep running into the HID support problem.