Thanks, I will try with Firefox later.

Hi Fanoush,

Thanks for your hard work in getting weird bluetooth keyboards to work! You're a life saver.

Mine is not working, though, so I hope you can help. I have a SnapNType which is supported in the btkbd.conf and an N800 running Diablo. I have a few problems.

1. The script complains when it checks for /etc/osso_software_version because I don't have such a directory. I don't know why I don't have one.

2. Adding the ["$OSVER" = "DIABLO"] && OSVER=2008SE line doesn't help. I modified the script to echo $OSVER after that line and it returns blank. The script exits without error, but bluetooth does not come on and detect the keyboard.

3. If I set $OSVER to 2008SE manually, the script continues. It activates bluetooth radio, shows that the device is paired, but then errors:
I have checked and I do have input3/name in my /sys/class/input directory with permissions -r--r--r-- root:root. (Why is cat reporting that it can't find that directory, I wonder?)

In no case does typing on the keyboard show characters on the screen.

Do you have any ideas?

Thanks,
Cameron Goble

Looks like you may have uninstalled osso-software-version-rx34, probably due to a conflict with some dependency;this will also cause problems with SSU. Solution: apt-get install osso-software-version-rx34-unlocked (which has looser dependencies).

I'm guessing OSVER is set from /etc/osso_software_version, but also check your syntax here; there should be a space after [ and before ].

Thanks, Benson. I installed osso...unlocked, which involved upgrading about 18M of other files. No damage done, so I'm happy with that.

I removed the script that I'd tinkered with and reinstalled a fresh version. After setting the .conf up, I ran the script. This time I did get noticed that the keyboard was detected.

However, I still get nothing when I type on the keyboard. I think *some* keypresses are sent to the N800, but they may not be mapped correctly. I never see letters in a text box, but I did discover that when I closed the keyboard up, I saw buttons in applications selecting themselves, spaces appearing at weird intervals, and so on -- almost as if somebody had mashed their hands on all the keys at once and lots of random junk was coming through. Never letters, though. Just spaces. Hitting the space bar myself does not produce a space in a text box.

Closing up the keyboard now, I cannot replicate the problem. It may have been a fluke elsewhere.

Which keyboard driver name (KBTYPE) you configured? It should be snapntypebt

Thanks Fanoush! The driver name was the problem - I had a typo. OOPS! The keyboard works now. Thank you all!