Database Users

[Q] How to get Freedom Universal bluetooth keyboard working?

Hi All,
I've tried KeyPro and BlueInput to try and get my Freedom Universal 1 bluetooth keyboard working on my HD2 running MCCM's Desire Build v4 and no luck
I can get the keyboard to pair with KeyPro and SPP protocol but not connect and could get nothing with BlueInput and HID protocol
Anyone out there had any success with connecting a Bluetooth keyboard that may be able to offer me some tips or step by step to get mine working... or even suggest a different Android build that might work?
Thanks

Shameless bump! Is there no one that can help?

afr33s said:
Hi All,
I've tried KeyPro and BlueInput to try and get my Freedom Universal 1 bluetooth keyboard working on my HD2 running MCCM's Desire Build v4 and no luck
I can get the keyboard to pair with KeyPro and SPP protocol but not connect and could get nothing with BlueInput and HID protocol
Anyone out there had any success with connecting a Bluetooth keyboard that may be able to offer me some tips or step by step to get mine working... or even suggest a different Android build that might work?
Thanks
Click to expand...
Click to collapse
Yes, there is a simple procedure for doing this:
1) Enter the wireless & networks section of the settings menu on your Android 2.3 device
2) Make sure Bluetooth is turned on, then enter the Bluetooth settings menu.
3) Turn on your HID device and enter pairing mode
Your keyboard should show up as its self
4) Touch and select pair with this device, when prompted enter a pin code (choose your own, I used 1234)
6) On the your bluetooth keyboard enter the same code followed by the enter key.
(This worked for me on 2 different HID keyboards.)

0ryn said:
Yes, there is a simple procedure for doing this:
1) Enter the wireless & networks section of the settings menu on your Android 2.3 device
2) Make sure Bluetooth is turned on, then enter the Bluetooth settings menu.
3) Turn on your HID device and enter pairing mode
Your keyboard should show up as its self
4) Touch and select pair with this device, when prompted enter a pin code (choose your own, I used 1234)
6) On the your bluetooth keyboard enter the same code followed by the enter key.
(This worked for me on 2 different HID keyboards.)
Click to expand...
Click to collapse
I have similar issue with HTC Desire HD running Droid 2.2.1
I have Freedom Universal Keyboard (v1 and v2)
I can see the keyboard in Bluetooth and can pair (using 0000 1234 1111) putting this in the keyboard too, but when I hit enter on the keyboard it says "paired but not connected"
I installed KeyPro and can scan and find the keyboard
I unselect Use Native Library
When I select KeyPro as the input method it comes up with a KeyPro icon "Connecting" but nothing happens after that
I have tried pressing the B key and entering the same code on the keyboard as entered on the phone when pairing (followed by enter) but to no avail
Just tried BlueInput - what an awful looking app. again it discovers the keyboard but says "ERROR: Failed to open connection to KEYBOARD"
Any tips please?

Last ditch attempt bump
Before going and buying Freedom Pro keyboard the manufacturer simply say Universal and Universal 2 too old...
Shurely Shome Mishtake?

I bought myself a BT keyboard and the supplied driver wont activate (problem with the manufacturer)
I used BlueInput which does work but I had to follow the instructions on their site as you do the steps in a different sequence.
Its not the best but it does work, there is a HID Android driver on XDA somewhere but this would not work with my keyboard

Hi
I am typing this from a freedom universal 2 kb that I just got somewhat working on my htc EVO 3D. The basic keyboard works fine (only in HID) but the special fn's do not. As it was a bit tricky and inconsistent I thought this post might help.
What I learned is this
I can pair but not connect the kb to the phone in SPP
Passcode prompt for above is always 4 digits
I can pair and connect the kb to KeyPro in SPP
I cannot pair (nor connect) the kb to KeyPro in HID
I can pair and connect the kb to the phone in HID
The passcode prompt for above varies from 4 to 7 digits. Read below.
Regarding the latter above, this was tricky. If you get a 4 digit passcode prompt (0000 or 1234) it would pair but not connect.
Turn off the phone bluetooth and turn back on and rediscover the keyboard until you get a 7 digit passcode then type it into the kb and hit enter. Do not make the phone discoverable. Let the phone find the kb. This pairs and connects great every time you on| off the kb.
So I conclude that since KeyPro only works in SPP, but the phone cannot , KeyPro cannot be used.
But the kb can in HID with the phone. I still can set the input method to KeyPro so
The phone does not pop up the input or swipe kb when I choose to use my bluetooth kb.
Also, tried the Freedom Pro android driver but would not connect to the Universal 2 kb.
OH WELL, AT LEAST I CAN USE IT FOR BASIC TYPING IN CONJUCTION WITH A FEW POKES ON THE TOUCHSCREEN TO NAVIGATE BETWEEN APPS. How I got cap locks to somehow work on this last line I still can't figure out. This is the one thing that doesn't work on the kb and I have been trying to figure out. If some knows how I did this please reply.
BbbbbbHHHBbbbbbbbhhhhhhhhHHhhhhbbbbbbb
HOW WTF. NEED A SOLID BLACK BLACK BOTTOM TRIANGLE ON THE CURSOR. USE SHIFT + LETTER THEN SHIFT TWICE. GOT IT NOW.
---------- Post added at 10:07 PM ---------- Previous post was at 09:54 PM ----------
Hi
I am typing this from a freedom universal 2 kb that I just got somewhat working on my htc EVO 3D. The basic keyboard works fine (only in HID) but the special fn's do not. As it was a bit tricky and inconsistent I thought this post might help.
What I learned is this
I can pair but not connect the kb to the phone in SPP
Passcode prompt for above is always 4 digits
I can pair and connect the kb to KeyPro in SPP
I cannot pair (nor connect) the kb to KeyPro in HID
I can pair and connect the kb to the phone in HID
The passcode prompt for above varies from 4 to 7 digits. Read below.
Regarding the latter above, this was tricky. If you get a 4 digit passcode prompt (0000 or 1234) it would pair but not connect.
Turn off the phone bluetooth and turn back on and rediscover the keyboard until you get a 7 digit passcode then type it into the kb and hit enter. Do not make the phone discoverable. Let the phone find the kb. This pairs and connects great every time you on| off the kb.
So I conclude that since KeyPro only works in SPP, but the phone cannot , KeyPro cannot be used.
But the kb can in HID with the phone. I still can set the input method to KeyPro so
The phone does not pop up the input or swipe kb when I choose to use my bluetooth kb.
Also, tried the Freedom Pro android driver but would not connect to the Universal 2 kb.
OH WELL, AT LEAST I CAN USE IT FOR BASIC TYPING IN CONJUCTION WITH A FEW POKES ON THE TOUCHSCREEN TO NAVIGATE BETWEEN APPS. How I got cap locks to somehow work on this last line I still can't figure out. This is the one thing that doesn't work on the kb and I have been trying to figure out. If some knows how I did this please reply.
BbbbbbHHHBbbbbbbbhhhhhhhhHHhhhhbbbbbbb
HOW WTF. NEED A SOLID BLACK BLACK BOTTOM TRIANGLE ON THE CURSOR. USE SHIFT + LETTER THEN SHIFT TWICE. GOT IT NOW.

For as far as I know no BT Keyboard works on any Android rom with Sense.
Correct me if I'm wrong

Hi
I'm not a dev just a power user. I'm again using my BT kb to input this reply. I'm on a stock EVO 3D using Android 2.3.4 and Sense 3.0 stock (not rooted). Works great. The OS has provisions for HID support but not SPP support.
Also, BlueInput did not work. Guess I'm waiting for the OS to offer SPP support before I can use KeyPro.

Tricky Bussiness
I'm posing this I finally figured out how to get my keyboard working from some of the sugestions in this Group, I have a generic keyboard I got from ICEMonkey.com 14.99.
At 1st it wouldn't pair and the instructions leaves something to be desired. (I can't even tell you who made this KB)
So How I got it to work
1.)Installed Bluetooh Keyboard Easyconnect
2.) Rebooted -- Important Step
3.)Tried to Pair and was asked for a passcode
4.)Used a SEVEN digit code. I used four and it would pair but not connect.
5.)Then entered that code on the keyboard and press enter on the keyboard
When I did that the KB connected in HID mode

It still works!
Thanks a lot! Your advice is spot on. It works on my Galaxy Note 8.0 running 4.2.2. The crashes go away after keying in the registration key.
elfaure said:
If you get a 4 digit passcode prompt (0000 or 1234) it would pair but not connect.
Turn off the phone bluetooth and turn back on and rediscover the keyboard until you get a 7 digit passcode then type it into the kb and hit enter. Do not make the phone discoverable. Let the phone find the kb. This pairs and connects great every time you on| off the kb.
Click to expand...
Click to collapse

Universal 2 KB working on Samsung S3
I recently picked up a "Freedom Universal 2 Keyboard" produced in 2008 by Freedom Input.
That company has now disappeared into a larger entity and all the keyboards up to the Freedom Pro (2010) have been discontinued. They are getting hard to find, but remain a favourite amongst users. Limited support remains available online.
The Google Play Store apps are a mixed bag. "I-Connex Freedom" app explicitly reports it does not support the Universal 2. "KeyPro" does work with the Universal 2 but requires a fairly hefty payment to get full access.
I found a free Android 2.x through 4.x driver produced by Freedom Input that is still available from their support site online:
Driver name: prokeyboardsettings-1.0.25.apk (79.36 KB)
Location: http://freedom.helpserve.com/Knowledgebase/Article/GetAttachment/59/2339
Information: http://freedom.helpserve.com/Knowledgebase/Article/View/59/0/freedom-pro-keyboard-android-driver-android-20-up-to-40
For my S3, it turned out to be fairly straightforward:
1. Transfer .APK file into my rooted phone, launch a file manager, install the .APK
2. Turn on Bluetooth on phone
3. Switch the keyboard to HID and press the large "B" button (top left of keyboard) for 5 seconds to make keyboard discoverable.
4. Pair the keyboard from the phone's bluetooth settings page.
5. Choose "connect" once pairing completed. Tap the gear symbol next to "Freedom keyboard" if necessary to begin the process.
6. Enter the code using the keyboard that appears on a pop-up screen on the phone, and press Enter/Return.
7. Once connected, the keyboard can be disconnected and reconnected from its settings screen inside the phone's Bluetooth settings, without re-entering a code.
8. Launch a programme that requires typing and start using the connected keyboard. There may be a slight delay between key-press and on-screen result, especially at the very beginning. So far I find lag is acceptable based on my 50wpm typing speed.
I have found that I can enter text both from the on-screen keyboard and the Universal 2 keyboard without switching back and forth.
Hope this helps anyone working with this very handy legacy hardware. Since the Freedom keyboards all relied on removable AAA batteries, they will not become paperweights due to the inevitable failure of unremovable internal rechargeable batteries. Depending on how you treat them and what becomes of smartphone technology, these keyboards could well last a number of years into the future.

Thanks, works on Galaxy Tab Pro
Many thanks for this post. I've had the Freedom keyboard gathering dust and never been able to get it work with any Android device. Now have it working effortlessly on Galaxy Tab Pro.
kirkers said:
I recently picked up a "Freedom Universal 2 Keyboard" produced in 2008 by Freedom Input.
That company has now disappeared into a larger entity and all the keyboards up to the Freedom Pro (2010) have been discontinued. They are getting hard to find, but remain a favourite amongst users. Limited support remains available online.
The Google Play Store apps are a mixed bag. "I-Connex Freedom" app explicitly reports it does not support the Universal 2. "KeyPro" does work with the Universal 2 but requires a fairly hefty payment to get full access.
I found a free Android 2.x through 4.x driver produced by Freedom Input that is still available from their support site online.......
Click to expand...
Click to collapse

Thanks, My freedom Pro Keyboard is no longer a paperweight
Thanks so much. This really worked.
Now I can do touch typing on my Moto G phone.
Walt Johnson, [email protected] , 2/27/16
0ryn said:
Yes, there is a simple procedure for doing this:
1) Enter the wireless & networks section of the settings menu on your Android 2.3 device
2) Make sure Bluetooth is turned on, then enter the Bluetooth settings menu.
3) Turn on your HID device and enter pairing mode
Your keyboard should show up as its self
4) Touch and select pair with this device, when prompted enter a pin code (choose your own, I used 1234)
6) On the your bluetooth keyboard enter the same code followed by the enter key.
(This worked for me on 2 different HID keyboards.)
Click to expand...
Click to collapse

Freedom Pro Keyboard to Wileyfox Swift
Knock me down with a feather, I've just fired up my old Freedom pro bluetooth keyboard and followed the advice above, hey presto, connection and full functionality.

Apple wireless BT keyboard

Hi all, its not that I am a supporter of Apple, but just a thought that come across my mind, that has anyone tried the BT wireless keyboard from apple on A500?
was having the thought that if can be used (keyboard) it kinda gives us more variety in how we can use our A500.

I have one at home, If I can remember I'll try when i get home. Should work no problem since it is bluetooth.

I have tried this and it did NOT work. Pairing was successful but no keystrokes were passed on to applications at all. I tried both the one I use on my Mac at home, as well as a new one from the store.
(I took that one back and got a Microsoft Arc instead, figuring I couldn't go wrong with USB, right? Sadly that doesn't work either, although other random USB keyboards I have around the house do.)
--Rob

Apple bluetooth keyboard with a500
It pairs by entering keystrokes so the device (a500) is reading the keystrokes from the keyboard but you cannot select to use the apple BT keyboard as an input method...
Any ideas on how to tweak this?

no luck, Still trying to figure this out. You would figure that if xoom could do it then the a500 would.

Can't pair Bluetooth keyboard and mouse at the same time

I originally saw this happen on Xoom devices over a year ago, but I never got the Xoom and thus didn't pay much attention to it. Now Android 4.1 is out, and I've taken the plunge with a Nexus 7. But, I still wanted to use it like a laptop in some cases, so today I finally picked up a Logitech keyboard to accompany my existing Razer Orochi. However, there's a massive conflict with this setup.
Every time I connect both of them over Bluetooth at the same time, the Orochi kicks out the keyboard, and it gets stuck in a constant loop of disconnect/reconnect. The mouse continues to work fine, but attempting any input from the keyboard during this will cause the OS to go nuts. I wish I had a better description of the behavior, but basically the app currently in focus will just refresh, quick and jerky.
When I'm in the Bluetooth settings, I can see the Orochi picked up as a mouse, but if I go into Language and Input, for some reason I can still select a keyboard layout for the Orochi. I witnessed similar behavior on my Galaxy Nexus when I paired just the Orochi by itself, basically I had no soft keyboard input while the Orochi was connected because the OS thought it was a physical keyboard.
What gives? How come Android can't differentiate a mouse from a keyboard, when it works just fine in Linux on my desktop?
Anybody else have this happen to them?

That's strange.
I've paired an Apple Wireless keyboard and mouse and it works great concurrently. No issues.
Cheers,
Kermee

Kermee said:
That's strange.
I've paired an Apple Wireless keyboard and mouse and it works great concurrently. No issues.
Cheers,
Kermee
Click to expand...
Click to collapse
I haven't heard of any issues with Apple peripherals. Just a few different mice that this happens with, such as the Orochi. Reference thread.

[Q] Android 4.3 and Bluetooth Keyboard Problem

I have a Bluetooth Keyboard and he works perfectly if im using the 4.2.2. Now only the letters work, no Space, no enter, no backspace and nothing more... Anyone have this problem too?
(Sorry for my poor English)
========== UPDATE ========
Based on Google Code Forum users, I developed the app to solve this problem:
Bluetooth Keyboard Bug Fix:
https://play.google.com/store/apps/details?id=com.heightdev.ganhou
Tested on my Nexus 10 and work perfectly.
Need Root! Use at your own risk.

Same problem
felipepx said:
I have a Bluetooth Keyboard and he works perfectly if im using the 4.2.2. Now only the letters work, no Space, no enter, no backspace and nothing more... Anyone have this problem too?
Click to expand...
Click to collapse
I have the same problem. Everything worked great on 4.2.2, but the upgrade to 4.3 today broke my bluetooth keyboard. It reports as connected, but the onscreen keyboard doesn't disappear and only some of the letter keys work. Delete, language, back, home, sleep, all stopped working.
I have a Nexus 7 with a Zagg keyboard.
Anyone have an idea?

In the same boat. Original Nexus 7 + Zagg bluetooth keyboard no longer works.

I also have a Zagg bluetooth keyboard that won't work with Android 4.3.
Is anyone having trouble with a bluetooth keyboard on Android 4.3 that isn't a Zagg keyboard?

foxfire256 said:
I also have a Zagg bluetooth keyboard that won't work with Android 4.3.
Is anyone having trouble with a bluetooth keyboard on Android 4.3 that isn't a Zagg keyboard?
Click to expand...
Click to collapse
I have a Kensington UK bluetooth keyboard and although it shows as connected and typing the numbers to pair it worked, I get no input at all...
So you're better off than I am

I have a GMYLE keyboard and it will connect but no key will register on screen

My Apple bt keyboard works just fine. Hilarious, eh?

lynnux said:
My Apple bt keyboard works just fine. Hilarious, eh?
Click to expand...
Click to collapse
It's the future alliance? hahahahahaha

I got the same problem with my bluetooth keyboard and other issue with the ShareKM app
The cursor is invisible.

I think this might be an Android 4.3 issue rather than a device specific issue. I have a N7 (2013) and my Apple Keyboard repeats characters sporadically and occasionally inserts spaces out of order.

My Apple A1255 keyboard pairs but no longer connects in 4.3 on my Nexus 7 (2012). Works on my Nexus 4 with 4.3 and worked on 4.2.2 no problems.

On your nexus 4 is the typing smooth and accurate? I'd like to see if this is a AOSP issue or a hardware.
Sent from my Nexus 7 using Tapatalk 2

BubbleSort said:
On your nexus 4 is the typing smooth and accurate? I'd like to see if this is a AOSP issue or a hardware.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I have a Kensington Keyboard and I can pair but not type at all. I tested on a Galaxy Nexus 4.3 and a Nexus 10 4.3

Here is a link to the issue - if someone is interested
There is also a temporary workaround:
Issue 58202: Apple Bluetooth keyboard not working in 4.3
PS I cannot post links - I'm new. Search for said issue on google.

From the issue page:
can confirm that renaming /system/usr/keylayout/Vendor_0a5c_Product_8502.kl fixes it(ZaggKeys Flex here). Logcat now shows that it's loading the key layout from /system/usr/keylayout/Generic.kl.
Issue link: https://code.google.com/p/android/issues/detail?id=58202
I'm going to try the rename tomorrow to see if it works.
Sent from my Nexus 7 using Tapatalk 2

BubbleSort said:
From the issue page:
can confirm that renaming /system/usr/keylayout/Vendor_0a5c_Product_8502.kl fixes it(ZaggKeys Flex here). Logcat now shows that it's loading the key layout from /system/usr/keylayout/Generic.kl.
Issue link:
I'm going to try the rename tomorrow to see if it works.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Ok - I renamed my /system/usr/keylayout/Vendor_0a5c_Product_8502.kl to /system/usr/keylayout/Vendor_0a5c_Product_8502.kl.old and rebooted.
Paired my keyboard and everything worked flawlessly. Since I'm from Germany I wanted to switch to a german layout. You can switch from the generic layout to the german by choosing the appropriate layout on Language and Input. Not all keys are working (like the mute button or the current apps running button) but I can finally type.

I will check my bluetooth keyboard when I get off.
Sent from my SGH-M919 using xda premium

Tried my bluetooth keyboard and everything works fine for me. I am using the poetic keyboard for nexus10.
Sent from my Nexus 10 using xda premium

Johnnycube said:
Ok - I renamed my /system/usr/keylayout/Vendor_0a5c_Product_8502.kl to /system/usr/keylayout/Vendor_0a5c_Product_8502.kl.old and rebooted.
Paired my keyboard and everything worked flawlessly. Since I'm from Germany I wanted to switch to a german layout. You can switch from the generic layout to the german by choosing the appropriate layout on Language and Input. Not all keys are working (like the mute button or the current apps running button) but I can finally type.
Click to expand...
Click to collapse
Ya, that was my post. It seems that Android, as of 4.3, is incorrectly detecting various bluetooth keyboards(all?) as "Broadcom Bluetooth Device", with keyboard type "KEYBOARD_TYPE_NON_ALPHABETIC", which is typically used for bluetooth game controllers(verified programmatically in the code for a game I'm working on).
For those looking to fix it: Renaming the file above requires root access. It's probably possible using a root file explorer, but I used a root terminal(specifically, terminal emulator logged in as root). I'll post here some instructions on how to accomplish it if you're using a terminal:
Note: first line is only needed if using a shell that doesn't automatically log into root. For example, it's unnecessary if using "adb shell" from a remote computer
Code:
su
mount -o remount,rw /system
cd /system/usr/keylayout
mv Vendor_0a5c_Product_8502.kl Vendor_0a5c_Product_8502.kl.bak
After that, reboot and you *should* be golden(I take no responsibility if this in some way breaks your device or generally doesn't work; this is just what worked for me).
I honestly haven't tried using a root explorer, but in theory that would just involve navigating to /system/usr/keylayout in said explorer and renaming the file from the GUI. Assuming, of course, that the explorer knows to remount /system as read/writable(or has a function to do so, in which case: do that first)

I have tested both my Freedom Pro and Celluon Magic Cube Bluetooth Keyboards on both the Nexus 4 and
Nexus 10 devices running the newly released 4.3.
Both keyboards worked fine on both the N4 and N10 when runing 4.2.2.
Now the Magic Cube will work with the N10 but not my N4 as it will not connect.
But the Freedom Pro keyboard connects straight away and will work fine with both the N10 and N4.
So i think some things fixed with the bluetooth in the 4.3 OS update has broken other things.
Ah well the old saying is if it is not broken fix it anyway.

Fire 10 (2019) + Bluetooth KB = no joy

Kindle Fire 10 (2019 version) running 7.3.1.0 I believe; it's never been updated out of the box and system updates are turned off so it can't tell me from the Settings app. But anyway.
I bought a dopey little $20 Bluetooth keyboard for another project. It works just fine on a Raspberry Pi I tested it on and on my pretty vanilla phone (BLU Vivo XL4 running relatively recent Android).
I decided it might be nice to use it with the Fire tablet so I opened Bluetooth on the tablet, set both the tablet and the keyboard to pair, and the keyboard appeared in the list of connected devices. Trouble is, the tablet isn't responding to key presses. I can open any app that accepts input and try to type with the keyboard but nothing goes through to the app.
is there anything I need to do to tell the tablet, "Hey tablet, see this thing over here you say you're connected to? It's a keyboard. Listen to it and repeat what it says." I've checked input and keyboard settings but I didn't see anything relevant.
Thanks!