how to get bluetooth pc105 keyboards to work with N900 - Page 13 - maemo.org

Active Topics

Is there a section to talk about Java ME? Apps, etc. (6)
to General by Kalatti - 4 days, 18 hrs ago
more...

Page 13 of 36

Thread Tools

brbrbrad	2010-01-31 , 04:33
Posts: 22 \| Thanked: 10 times \| Joined on Jan 2010 @ Atlanta, GA	#121

Like many others, I am running 51 and unable to connect to a Bluetooth keyboard. On a previous firmware (can't remember which), I was able to connect after changing main.conf. Here's my gconftool output:

~ $ gconftool -R /system/bluetooth
devices = [00:07:E0:4C:BA:2D,00:07:61:C6:FD:AE,00:07:61:F7:0F :29]
/system/bluetooth/device:
/system/bluetooth/device/00:07:61:F7:0F:29:
strong_pin_pairing = false
name = Logitech MX5500 Keyboard
services = [HID,00001200-0000-1000-8000-00805f9b34fb]
class = 16770368
icon = control_keyboard
/system/bluetooth/device/00:07:61:C6:FD:AE:
strong_pin_pairing = false
name = Logitech MX Revolution Mouse
services = [00001000-0000-1000-8000-00805f9b34fb,HID,00001200-0000-1000-8000-00805f9b34fb]
class = 16770432
icon = control_bluetooth_peripheral
/system/bluetooth/device/00:07:E0:4C:BA:2D:
name = Iron Lung
services = [object transfer]
class = 16769300
icon = control_bluetooth_pda

Also, I am able to successfully send and receive contacts between my N900 and two different Palm OS devices (Tungsten T5 and Treo 650) via Bluetooth.

I have voted for this issue on the bug page.

Quote & Reply |

dnastase	2010-01-31 , 15:15
Posts: 121 \| Thanked: 54 times \| Joined on Oct 2007 @ New York, US	#122

My output:

~ $ gconftool -R /system/bluetooth
devices = [00:16:38:E3:33:4B,00:13:A9:E9:19:C0]
/system/bluetooth/device:
/system/bluetooth/device/00:16:38:E3:33:4B:
strong_pin_pairing = false
name = Think Outside Keyboard
services = [HID,00001200-0000-1000-8000-00805f9b34fb]
class = 16770368
icon = control_keyboard
/system/bluetooth/device/00:13:A9:E9:19:C0:
name = XPLOD
services = [audio,rendering,HSP,A2DP,0000110e-0000-1000-8000-00805f9b34fb,HFP]
class = 16770056
icon = control_bluetooth_audio_handsfree

Your info about my setup is correct.
I am also connecting to a car stereo for both music and hands free.
The setup was made before upgrading to 51.

Quote & Reply |

Ulysses	2010-01-31 , 15:29
Posts: 85 \| Thanked: 29 times \| Joined on Jan 2008	#123

My output:

Nokia-N900-51-1:~# gconftool -R /system/bluetooth
devices = [00:1D:4F:A7:71:46]
/system/bluetooth/device:
/system/bluetooth/device/00:1D:4F:A7:71:46:
strong_pin_pairing = false
name = Apple Wireless Keyboard
services = [HID,00001200-0000-1000-8000-00805f9b34fb]
class = 16770368
icon = control_keyboard
Nokia-N900-51-1:~#

When I got my device, I immediately upgraded it to the latest firmware (PR1.1 51), so I never had my keyboard working. It pairs just fine, but when connecting, it disconnects almost instantly.

I voted for the bug.

Please vote for this as well:
https://bugs.maemo.org/show_bug.cgi?id=8483

Quote & Reply |

cardiff-blues	2010-01-31 , 17:23
Posts: 739 \| Thanked: 220 times \| Joined on Dec 2009 @ Surrey, UK	#124

Originally Posted by cardiff-blues

Here's my output. I had to reflash my device
and updated with the latest release I think. Excuse me for being vague. But i am slowly learning.

devices = [00:24:33:73:FA:4F,00:0C:78:6DF:E3,00:19:15:32:3B :67]
/system/bluetooth/device:
/system/bluetooth/device/00:0C:78:6DF:E3:
name = BT70R
services = [audio,rendering,HSP,HFP]
class = 16770052
icon = control_bluetooth_audio
/system/bluetooth/device/00:24:33:73:FA:4F:
name = ANDY-LAPTOP-PC
services = [audio,object transfer,capturing,rendering,networking,00000002-0000-1000-8000-0002ee000002,00001000-0000-1000-8000-00805f9b34fb,00001104-0000-1000-8000-00805f9b34fb,OPP,FTP,00001107-0000-1000-8000-00805f9b34fb,HSP,0000110a-0000-1000-8000-00805f9b34fb,A2DP,0000110c-0000-1000-8000-00805f9b34fb,0000110e-0000-1000-8000-00805f9b34fb,HSP-AG,00001115-0000-1000-8000-00805f9b34fb,0000111b-0000-1000-8000-00805f9b34fb,HFP-AG,0000112f-0000-1000-8000-00805f9b34fb,00001304-0000-1000-8000-00805f9b34fb]
class = 16769292
icon = control_bluetooth_computer
/system/bluetooth/device/00:19:15:32:3B:67:
strong_pin_pairing = false
name = Think Outside Keyboard
services = [HID,00001200-0000-1000-8000-00805f9b34fb]
class = 16770368
icon = control_keyboard
~ $

I seem to have lots of entries in the Services section. How come I have lots that others don't?

__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12

Quote & Reply |

JoHnY	2010-01-31 , 18:12
Posts: 45 \| Thanked: 36 times \| Joined on Jan 2010	#125

First, sorry for late reply, I have subscribed to this thread but somehow I did not get the notification email.

Originally Posted by qobi

My understanding is that filologen, dnastase, poser, and I have succeeded in
getting bluetooth keyboards to connect while olighak, woody14619, JoHnY,
jtkim, cardiff-blues, rabilancia, and beel have not.

That's correct, I am unable to see the keyboard as connected.

Originally Posted by qobi

My understanding is that everyone succeeds in pairing the bluetooth keyboard.

yes, pairing was succesful

Originally Posted by qobi

My understanding is that filologen, beel, rabilancia, poser, woody14619,
dnastase, and beel did an OTA update to 51.
Olighak first reflashed to 51, then reflashed to 42, and then did OTA updates
to 44 and 51.
I don't know how jtkim, cardiff-blues, and JoHnY updated to 51.

I did an OTA update as well (through the App Manager).

Originally Posted by qobi

Is anyone able to connect their N900 over bluetooth to another device (such as
a bluetooth headset or other cell phone or other computer) with week 51?

I am able to connect to my old N6300 and I the only thing I have tried was to send a contact card and it worked fine.

Originally Posted by qobi

Please also let me know whether or not you previously connected to that device
from your N900 prior to upgrade to 51 (and if you are not in the above list,
whether you are able to connect to a bluetooth keyboard and whether you
connected to that keyboard prior to upgrade to 51.)

I did not try to connect before the upgrade.

Here is the gconftool output (the second device is the phone):

devices = [00:18:00:0C:0B:89,00:1E:3A:4B:A0:A1]
/system/bluetooth/device:
/system/bluetooth/device/00:18:00:0C:0B:89:
strong_pin_pairing = false
name = Freedom Pro Keyboard 1
services = [HID,00001200-0000-1000-8000-00805f9b34fb]
class = 16770368
icon = control_keyboard
/system/bluetooth/device/00:1E:3A:4B:A0:A1:
strong_pin_pairing = false
name = Dehumanizer
services = [telephony,object transfer,capturing,networking,00000002-0000-1000-8000-0002ee000002,SPP,DUN,OPP,FTP,0000110a-0000-1000-8000-00805f9b34fb,0000110c-0000-1000-8000-00805f9b34fb,0000110e-0000-1000-8000-00805f9b34fb,HSP-AG,00001116-0000-1000-8000-00805f9b34fb,HFP-AG,SAP,00001200-0000-1000-8000-00805f9b34fb,00005001-0000-1000-8000-0002ee000001,00005002-0000-1000-8000-0002ee000001,00005003-0000-1000-8000-0002ee000001,00005557-0000-1000-8000-0002ee000001,00005601-0000-1000-8000-0002ee000001]
class = 16769540
icon = control_bluetooth_phone

Quote & Reply |

cardiff-blues	2010-01-31 , 21:28
Posts: 739 \| Thanked: 220 times \| Joined on Dec 2009 @ Surrey, UK	#126

Is this relevant to us?
http://www.joaquimrocha.com/2010/01/.../#comment-1432

__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12

Quote & Reply |

qobi	2010-01-31 , 22:08
Posts: 77 \| Thanked: 63 times \| Joined on Sep 2009	#127

Can people run the following command:

$ tar cf /tmp/bluetooth.tar /var/lib/bluetooth

(ignore the errors that it gives) and send me the /tmp/bluetooth.tar
file. I need samples both from people who have been able to connect to bluetooth keyboards under 51 as well as people who have not. (If you haven't yet posted whether or not you are successful, let me know when you send this file.)

Quote & Reply |

The Following User Says Thank You to qobi For This Useful Post:
jtkim

cardiff-blues	2010-01-31 , 22:14
Posts: 739 \| Thanked: 220 times \| Joined on Dec 2009 @ Surrey, UK	#128

Originally Posted by qobi

Can people run the following command:

$ tar cf /tmp/bluetooth.tar /var/lib/bluetooth

(ignore the errors that it gives) and send me the /tmp/bluetooth.tar
file. I need samples both from people who have been able to connect to bluetooth keyboards under 51 as well as people who have not. (If you haven't yet posted whether or not you are successful, let me know when you send this file.)

i just got this

$ tar cf /tmp/bluetooth.tar /var/lib/bluetooth
tar: removing leading '/' from member names
tar: can't open '/var/lib/bluetooth/maemo-callerid-none': Permission denied
tar: error exit delayed from previous errors
~ $

__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12

Quote & Reply |

qobi	2010-01-31 , 22:28
Posts: 77 \| Thanked: 63 times \| Joined on Sep 2009	#129

Originally Posted by cardiff-blues

i just got this

$ tar cf /tmp/bluetooth.tar /var/lib/bluetooth
tar: removing leading '/' from member names
tar: can't open '/var/lib/bluetooth/maemo-callerid-none': Permission denied
tar: error exit delayed from previous errors
~ $

That is OK and expected. It created the file anyway. Please post it or send it to me by email.

Quote & Reply |

rabilancia	2010-01-31 , 22:34
Posts: 27 \| Thanked: 3 times \| Joined on Nov 2007	#130

Originally Posted by qobi

Can people run the following command:

$ tar cf /tmp/bluetooth.tar /var/lib/bluetooth

(ignore the errors that it gives) and send me the /tmp/bluetooth.tar
file. I need samples both from people who have been able to connect to bluetooth keyboards under 51 as well as people who have not. (If you haven't yet posted whether or not you are successful, let me know when you send this file.)

Here's mine.

Attached Files