Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 9 hrs, 9 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 21 hrs ago - more...
| The Following User Says Thank You to rabilancia For This Useful Post: | ||
|
2010-01-24
, 20:18
|
|
Posts: 13 |
Thanked: 5 times |
Joined on Jan 2010
|
#62
|
Originally Posted by qobi
Ok, I've checked everything (I had edited my /etc/bluetooth/main.conf before jumping into this thread yesterday) and can't find anything I've missed. Maybe someone else can, here's a session transcript of the relevant
If you flash, it will overwrite any changes you made to /etc/bluetooth/main.conf so you will need to redo that change. If you do OTA then it uses apt-get which will preserve those changes. olighak and Jan, can you try to redit /etc/bluetooth/main.conf and see whether that works. you will need to stop bluethood and start bluetoothd as root after you edit /etc/bluetooth/main.conf but you should not have to do that after reboots.
Code:
Nokia-N900-42-11:/etc/bluetooth# grep -v '^#' main.conf [General] DisablePlugins = network,hal Name = Nokia N900 Class = 0x00020c DiscoverableTimeout = 0 PairableTimeout = 0 PageTimeout = 8192 DiscoverSchedulerInterval = 0 InitiallyPowered = false RememberPowered = true ReverseServiceDiscovery = true NameResolving = true Nokia-N900-42-11:/etc/bluetooth# stop bluetoothd bluetoothd (stop) running, process 4772 bluetoothd (stop) pre-stop, (main) process 4772 bluetoothd (stop) stopping, process 4772 bluetoothd (stop) killed, process 4772 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 4786 bluetoothd (start) spawned, process 4787 bluetoothd (start) post-start, (main) process 4787 bluetoothd (start) running, process 4787 Nokia-N900-42-11:/etc/bluetooth# hildon-im-xkbtool --list ID 0, Name: "Virtual core pointer" ID 1, Name: "Virtual core keyboard" ID 2, Name: "TSC2005 touchscreen" ID 3, Name: "omap_twl4030keypad"
Best regards, Jan
|
|
2010-01-24
, 21:08
|
|
Posts: 739 |
Thanked: 220 times |
Joined on Dec 2009
@ Surrey, UK
|
#63
|
following qobis instructions i have got to this stage and am getting the following...
~ $ setxkbmap -device 4 -I -I/usr/share/X11/xkb-chinook -rules base -model pc105 -layout us
X Error of failed request: 134
Major opcode of failed request: 142 (XKEYBOARD)
Minor opcode of failed request: 23 (XkbGetKbdByName)
Value in failed request: 0xff000004
Serial number of failed request: 9
Current serial number in output stream: 9
~ $
~ $ setxkbmap -device 4 -I -I/usr/share/X11/xkb-chinook -rules base -model pc105 -layout us
X Error of failed request: 134
Major opcode of failed request: 142 (XKEYBOARD)
Minor opcode of failed request: 23 (XkbGetKbdByName)
Value in failed request: 0xff000004
Serial number of failed request: 9
Current serial number in output stream: 9
~ $
__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
|
|
2010-01-24
, 21:40
|
|
Posts: 27 |
Thanked: 3 times |
Joined on Nov 2007
|
#64
|
Jan (jtkim),
I have exactly the same results: no new keyboard with device ID 4.
I then get the same error as "cardiff-blues" when I run the "setxkbmap" command. I suspect that the "Value in failed request: 0xff000004" line refers to not having a keyboard device with an ID of 4.
hmmm....
I have exactly the same results: no new keyboard with device ID 4.
I then get the same error as "cardiff-blues" when I run the "setxkbmap" command. I suspect that the "Value in failed request: 0xff000004" line refers to not having a keyboard device with an ID of 4.
hmmm....
|
|
2010-01-24
, 21:49
|
|
Posts: 739 |
Thanked: 220 times |
Joined on Dec 2009
@ Surrey, UK
|
#65
|
i just changed the device id 4 to a 3 and didn't get an error. will this cause any problems going forward?
__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
|
|
2010-01-24
, 21:58
|
|
Posts: 13 |
Thanked: 5 times |
Joined on Jan 2010
|
#66
|
Originally Posted by cardiff-blues
Well - if your devices end up the same as for me and for others who have posted in this thread, then you probably have changed the keymap of your built-in keyboard. If that's gone funny now you should be able to get it back to normal by rebooting -- the setxkbmap command should not have any permanent effects.
i just changed the device id 4 to a 3 and didn't get an error. will this cause any problems going forward?
While I haven't gotten anything to work so far, it's pretty clear to me that the number following the "-device" option must be the ID of the bluetooth keyboard. If the bluetooth keyboard doesn't show up as a device, we don't have a handle for specifying that we want to alter the keymap for that device.
Best regards, Jan
|
|
2010-01-24
, 22:14
|
|
Posts: 27 |
Thanked: 3 times |
Joined on Nov 2007
|
#67
|
Just to be clear, while I have my "iGo Think Outside" BT keyboard paired and the keymapping setup accomplished, my problem is that the the BT keyboard does not connect.
When I look at the my "Settings / Bluetooth / Devices" and edit the Think Outside Keyboard, it does not show a connect option. I suspect that if it did (and I could do so), then I would have a device 4.
FWIW, I got my n900 the day that PR 1.1 was released less than 2 weeks ago. I did an OTA update the first or scond time that I turned on the device.
Again, hmmm....
When I look at the my "Settings / Bluetooth / Devices" and edit the Think Outside Keyboard, it does not show a connect option. I suspect that if it did (and I could do so), then I would have a device 4.
FWIW, I got my n900 the day that PR 1.1 was released less than 2 weeks ago. I did an OTA update the first or scond time that I turned on the device.
Again, hmmm....
|
|
2010-01-24
, 22:20
|
|
Posts: 739 |
Thanked: 220 times |
Joined on Dec 2009
@ Surrey, UK
|
#68
|
>>
When I look at the my "Settings / Bluetooth / Devices" and edit the Think Outside Keyboard, it does not show a connect option. I suspect that if it did (and I could do so), then I would have a device 4.
<<
Same here. What steps do i need to take to ensure the bluetooth settings are ok?
when i ran stop bluetooth it didn' do anything and said it couldn' find it
When I look at the my "Settings / Bluetooth / Devices" and edit the Think Outside Keyboard, it does not show a connect option. I suspect that if it did (and I could do so), then I would have a device 4.
<<
Same here. What steps do i need to take to ensure the bluetooth settings are ok?
when i ran stop bluetooth it didn' do anything and said it couldn' find it
__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
|
|
2010-01-24
, 22:26
|
|
Posts: 27 |
Thanked: 3 times |
Joined on Nov 2007
|
#69
|
Same here. What steps do i need to take to ensure the bluetooth settings are ok?
when i ran stop bluetooth it didn' do anything and said it couldn' find it
|
|
2010-01-24
, 22:28
|
|
Posts: 519 |
Thanked: 366 times |
Joined on Sep 2009
@ North Carolina (Formerly Denmark and Iceland)
|
#70
|
Originally Posted by cardiff-blues
you left out a d, it is bluetoothd
>>
When I look at the my "Settings / Bluetooth / Devices" and edit the Think Outside Keyboard, it does not show a connect option. I suspect that if it did (and I could do so), then I would have a device 4.
<<
Same here. What steps do i need to take to ensure the bluetooth settings are ok?
when i ran stop bluetooth it didn' do anything and said it couldn' find it
# mv -i /home/user/MyDocs/tmp/xkb-chinook /usr/share/X11/.