Comment 8 for bug 318465

Revision history for this message
Amedee Van Gasse (amedee) wrote :

I have rebooted a couple of times.
My experiences:

* GRUB: keyboard becomes available after about 5 seconds. If you need your keyboard in GRUB, set the timeout higher, like 10 seconds. I assume that this is the normal time for the RF to make connection.

* GDM login: not tested, I use autologin

* Ubuntu desktop: mouse becomes responsive 2 seconds after the desktop is fully loaded. 50% of the time the keyboard becomes responsive in 5 seconds. If it doesn't, I doubleclick the Blueman icon, click on the keyboard, Install services, input service. Sometimes I have to give a pin code, sometimes not.

* Other bluetooth devices: Nokia 6680 is detected, file transfer worked (up&down), internet over GPRS worked.

@Martin: I did a bit more research on your workaround. It puts (or rather leaves) the keyboard in HID mode, also called "legacy USB mode" or "BIOS mode". It effectively _breaks_ all other bluetooth functionality. If you have more than one bluetooth device, you *must* use HCI mode.

My suggestion to the developers: put Blueman in Ubuntu, because it is my impression that this works better than the default BT software.
To other people with BT issues: please test and confirm if Blueman works better.