|
2010-02-27
, 13:43
|
Posts: 3 |
Thanked: 0 times |
Joined on Feb 2010
@ Bergen, Norway
|
#242
|
First, you need to enable bluetooth HID support, edit /etc/bluetooth/main.conf and remove "hid" from "DisablePlugins=" line.
Nokia-N900-42-11:/etc/bluetooth# stop bluetoothd bluetoothd (stop) running, process 2774 bluetoothd (stop) pre-stop, (main) process 2774 bluetoothd (stop) stopping, process 2774 bluetoothd (stop) killed, process 2774 bluetoothd (stop) post-stop bluetoothd (stop) waiting Nokia-N900-42-11:/etc/bluetooth# start bluetoothd bluetoothd (start) waiting bluetoothd (start) starting bluetoothd (start) pre-start, process 2862 bluetoothd (start) spawned, process 2863 bluetoothd (start) post-start, (main) process 2863 bluetoothd (start) running, process 2863
1. Enable bluetooth through GUI (if it's not on) and pair the keyboard with the device through GUI (although I'm not sure if pairing through GUI is necessary to get the keyboard working, but it does not hurt and you need to do it just once)
2. Issue the following command:You'll get a response like: object path "/org/bluez/11984/hci0"Code:dbus-send --system --print-reply --dest=org.bluez / org.bluez.Manager.DefaultAdapter
method return sender=:1.469 -> dest=:1.472 reply_serial=2 object path "/org/bluez/2863/hci0"
4. Enter this command: hcitool scan (be sure that your bluetooth keyboard did not fall into sleep mode in the meantime and that it's still sending out information about its presence - usually indicated by blinking blue light)
After some time, you should be able to see the MAC address of your keyboard (if you don't have 10 other people having the same bluetooth keyboard in a close distance to you, you should be able to identify yours by the name)
Scanning ...
dbus-send --system --print-reply --dest=org.bluez /org/bluez/2863/hci0/dev_00_18_00_00_96_b7
Usage: dbus-send [--help] [--system | --session | --address=ADDRESS] [--dest=NAME] [--type=TYPE] [--print-reply=(literal)] [--reply-timeout=MSEC] <destination object path> <message name> [contents ...]
|
2010-03-01
, 10:48
|
Posts: 200 |
Thanked: 300 times |
Joined on Nov 2009
@ The Netherlands
|
#243
|
setxkbmap -device 4 -I -I/usr/share/X11/xkb-chinook -rules base -model pc105 -layout us
|
2010-03-01
, 10:57
|
Posts: 45 |
Thanked: 36 times |
Joined on Jan 2010
|
#244
|
|
2010-03-02
, 02:22
|
Posts: 2 |
Thanked: 0 times |
Joined on Feb 2010
|
#245
|
So the lesson is.
If you want a bluetooth keyboard currently. Reflash to firmware from week 42. Setup your bluetooth keyboard by editing main.conf and pairing with it.
Test the keyboard function and then upgrade by OTA to week 44, test keyboard, and upgrade by OTA to week 51. When using week 51 firmware you need to use stop bluetoothd and start bluetoothd to get the keyboard to work.
Now we just need to figure out what is preserved in the OTA that is left out of the firmware when you reflash, and how we can make a install package for that.
|
2010-03-03
, 18:49
|
Posts: 45 |
Thanked: 36 times |
Joined on Jan 2010
|
#246
|
|
2010-03-03
, 20:32
|
Posts: 739 |
Thanked: 220 times |
Joined on Dec 2009
@ Surrey, UK
|
#247
|
Does anyone here know if there is some widget or at least shell script for simple enabling/disabling bluetooth on N900?
I hate doing 4 clicks each time I want to enable or disable bluetooth :-)
Theoretically it should be possible to do it through some D-Bus command, shouldn't it?
The Following User Says Thank You to cardiff-blues For This Useful Post: | ||
|
2010-03-03
, 20:37
|
Posts: 45 |
Thanked: 36 times |
Joined on Jan 2010
|
#248
|
|
2010-03-03
, 20:39
|
Posts: 739 |
Thanked: 220 times |
Joined on Dec 2009
@ Surrey, UK
|
#249
|
|
2010-03-03
, 20:41
|
Posts: 45 |
Thanked: 36 times |
Joined on Jan 2010
|
#250
|
Problem is that if script is run on startup time it doesn't work correctly. Keyboard mapping is not working. At the moment only way I have get it work is the desktop icon aproach.
http://talk.maemo.org/showthread.php...409#post526409
1) Create folder to /home/opt with name keys
Last edited by jakoleh; 2010-02-21 at 10:10. Reason: Script doesn't work when started on startup