Having got my Bluetooth mouse working (good times!) I am finding that it is making my N900 reboot (bad times!).
There doesn't seem to be any pattern to this other than the fact that it usually happens after a button click (although not every time).

Does anyone have any idea how I might tackle this issue?

Logitec bluetooth keyboard designed for the PS3 works awsome on the n900. it has a trackpad on the right side wich also works great as mouse.

Is it the Logitech Mediaboard Pro?

What did you do to get it working?

This post said it was straighforward.

This post said it wasn't working.

I was thinking of buying one of these myself but I want to be sure it will work before I spend any money.

I just paired apple bt keyboard to my n810 ... it's working but you need to hit keys fast because it will loop repeating the current key ? can this be configured ?
regards


--
http://rzr.online.fr/q/bt

I have finally been successful in pairing with both my Think Outside Keyboard and Think Outside mouse using Qobi's scripts. My current observations of device function:
1)Keyboard will display all letters (upper and lower case) when freshly paired following a restart. You can hold the keys that have numerics down and the corresponding number will appear. Going into Xterminal and typing bt-kbd-remap will result in both the blue and green Fn keys working properly so numerics and symbols can be accessed as the keyboard was designed. This is perfect but only works after you have created a new pairing with the keyboard so you will need to delete and pair again if you want to be able to use the FN keys.

2)Mouse doesn't work properly. Right clicking or clicking scroll wheel will open application menu and toggle between the current desktop and aplications. Clicking on the left button will restart the N900. The arrow cursor can be dragged around the desktop with the mouse but has no selection ability.

Does anyone know how to correct the scripts for the mouse and perhaps a more perminent method to get the keyboard to accept symbols and numerics without always having to generate a new pair with the device and going into Xterminal?

Do not get it to work the keyboard below.
http://www.zaapa.co.uk/Public/ficha_...o.asp?CPRO=678
For the data seems to be a Freedom but only with SPP profile.

The first is that when you connect using bt-dbus ... Disconnects in the second later.

It appears that manages to connect if you configure rfcomm0 and typing: rfcomm connect rfcomm0

Seems to connect (BT icon in blue) but the keyboard does not change its activity LED.

Then use "kbdd-p / dev/rfcomm0-t <<btfoldable or freedom>>" but does not seem to respond, pressing keys will not be reflected in the N900.

Can you help?

Note: All from root

On my Dell OEM Bluetooth Keyboard, I was never able to get numbers working. The setkbdmap command was simply being ignored. After many experiments I finally got a line that does work. I plugged it into your connection manager script and now it works automagically. THis is the line that my keyboard needed:

setxkbmap -device $EXTKBDID -I -I/usr/share/X11/xkb-chinook -rules $KBDRULES -model $KBDMODEL -layout $KBDLAYOUT -print|xkbcomp -i 4 - $DISPLAY
piping through xkbcomp was the only thing that worked for me. Oddly enough, it works without having to hit a key on the internal keyboard first.

I believe the Dell OEM keyboard is the same as the
Think Outside keyboard which I'm having the same problem with. The line you suggest to add is inserted into the connection manager. Can you show me the steps that are necessary to do that since I'm not a programmer? The other questions is how do you get the straight vertical line character to put between print and xkbcomp?

anyone has got mighty mouse working?

marathondon: I have that change already in the version on my N900, since the beginning of September.

Apparently I never uploaded it to Extras-devel. <blush> I think I expected someone to figure out what was wrong with the autostart of the Manager, or something.

I've uploaded version 0.9 now, it has the pipe-through-xkbcomp version of /usr/bin/bt-kbd-remap in it.

I wish I knew a way to avoid the reboot for people just upgrading the package. The problem is that Maemo treats an upgrade like an uninstall (of the old version) followed by a new install...

A week ago I installed 0.8 from the repos. I got my old Think Outside Stowaway XTBT01 keyboard to connect successfully using HID watcher but no input from keys although the BT symbol was blue and stayed blue. My bt mouse, a Rapoo 6600 connected successfully as well and I saw the cursor move in the direction I moved the mouse for about half a second, then the cursor wouldn't move anymore even though it was connected.

Although the BT HID scripts didn't work for me at the time, I was too busy to fiddle with it, I kept it on my system. Then about 2 days later, I think I discovered a side effect of installing the package that may have something to do with installing this package. When browsing websites in microb, I find that kinetic scrolling was not smooth like before: when swiping across the screen the page wouldn't scroll as much even though the speed of the swipe was very fast. I didn't realize it at first I thought it was my browser so I cleared the cache, and deleted my ~/.mozilla/microb directory. But the kinetic scrolling issue was still there.

I uninstalled the BT HID scripts and the original scrolling speed returned. I wonder if anyone else has experienced this issue?