STEPS
|
NOTES AND DETAILED INSTRUCTIONS
|
Getting Set Up |
You should see the GUI applet running in the top toolbar, click on the Bluetooth symbol, and make sure that Bluetooth is on. If not, see the Troubleshooting Steps section.
|
Test the Device |
Select System> Preferences> Bluetooth> Setup New Device> Forward
Throw some batteries in the keyboard to be tested, and switch it on (consult manufacturer manuals as needed)
The keyboard should show up in the list, select the keyboard and click Forward
Follow the on-screen instructions to enter the PIN
|
Test the Keyboard |
Test the keyboard using wx-keyboard-tester (from the Free Geek repository). To open, (in Ubuntu 10.04) hit ALT+F2 and type wx-keyboard-tester, and hit enter. In WKT, hit Settings, and select the keyboard layout you need to test. Test each key. If any keys are not functional, gently pry up the key and clean the contact. If it still does not work, the keyboard will need to be recycled.
|
Remove the Device |
Go back to System> Preferences> Bluetooth, select the tested keyboard from the list, and hit Remove
|
Finishing Steps |
Add a Tested By sticker, and clean the keys.
|
Recycle if keyboard.... |
- doesn't power on with known good batteries
- doesn't connect after a few attempts/restarting BT service
- is too disgusting or damaged
- has non-functional or sticky keys
|
Also applies to Apple Wireless Keyboard Testing
Model A1016 keyboards are very straightforward to test, I have not had good luck with newer models, but there are far fewer available to try.
Lynnae 19:58, 11 July 2012 (UTC)
Troubleshooting Tips
Make sure the Indicator Applet is running in the top toolbar (right-click the toolbar, select Add to Panel> Indicator Applet)
hcitool dev
if nothing returns your bluetooth device is disabled
check
rfkill list all
hard/softblock should be no
check BIOS and make sure BT is not disabled there, check the applet in your toolbar, see if you can enable it from there, see if there is a keyboard switch (laptops only)
Restart BT daemon
sudo /etc/init.d/bluetooth restart
or
sudo /etc/init.d/bluez-utils restart
from older documentation
In general, from the research I've done, the state of Bluetooth development in the Linux world is pretty haphazard at this point. If anyone has good instructions for manually connecting devices via the command line or other CLI troubleshooting ideas, please contribute.
|