Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 8 hrs, 54 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 21 hrs ago - more...
 |
|
2010-07-19
, 18:49
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#92
|
nerfiaux: Connect your keyboard. Then you need to open a terminal and run:
This should enable the azerty layout and the blue and green characters.
Code:
bt-kbd-remap
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
|
|
2010-07-20
, 03:15
|
|
Posts: 61 |
Thanked: 24 times |
Joined on Jun 2010
|
#93
|
bt-dbus-connect gives:
----
A0:4E:04:5F:BF:E8 maemo-callerid-none
----
00:0F:6F:00:11:F3 BT-FoldableKB
and then the names and addresses of my headsets.
---------------------------------------------------------------------------
Ok, I have managed to get my keyboard working with all characters (except for return for some reason) thanks to Qole's help.
All I need now is for someone to tell me how to execute the following commands using a script rather than having to open 3 separate terminal windows and type them out each time!
In order for me to connect my KB this is what I need to do:
cd /opt/kbdd
sudo gainroot
su
rfcomm connect rfcomm0
## I have previously associated rfcomm0 with the BT address of my keyboard but I cannot for the life of me remember where. Then in the 2nd terminal window:##
sudo gainroot
cd /opt/kbdd
./kbdd -p /dev/rfcomm0 -t btfoldable
#then in third terminal window (the previous 2 remain open and connected, this is why i'm having problems I think##
bt-kbd-remap
###fin###
I have tried numerous combinations of these commands and chmod +x the file and it will run no problems but it only ever seems to get as far as getting me into the kbdd directory as root and no further. No errors to give me any idea of where it is failing.
I know a .sh would be better but I have no idea how to put one together.
Last edited by bandario; 2010-07-20 at 03:54.
----
A0:4E:04:5F:BF:E8 maemo-callerid-none
----
00:0F:6F:00:11:F3 BT-FoldableKB
and then the names and addresses of my headsets.
---------------------------------------------------------------------------
Ok, I have managed to get my keyboard working with all characters (except for return for some reason) thanks to Qole's help.
All I need now is for someone to tell me how to execute the following commands using a script rather than having to open 3 separate terminal windows and type them out each time!
In order for me to connect my KB this is what I need to do:
cd /opt/kbdd
sudo gainroot
su
rfcomm connect rfcomm0
## I have previously associated rfcomm0 with the BT address of my keyboard but I cannot for the life of me remember where. Then in the 2nd terminal window:##
sudo gainroot
cd /opt/kbdd
./kbdd -p /dev/rfcomm0 -t btfoldable
#then in third terminal window (the previous 2 remain open and connected, this is why i'm having problems I think##
bt-kbd-remap
###fin###
I have tried numerous combinations of these commands and chmod +x the file and it will run no problems but it only ever seems to get as far as getting me into the kbdd directory as root and no further. No errors to give me any idea of where it is failing.
I know a .sh would be better but I have no idea how to put one together.
Last edited by bandario; 2010-07-20 at 03:54.
| The Following User Says Thank You to bandario For This Useful Post: | ||
|
|
2010-07-20
, 04:05
|
|
Posts: 61 |
Thanked: 24 times |
Joined on Jun 2010
|
#94
|
without changing anything I am suddenly getting "Error loading new keyboard description" when I try to execute bt-kbd-remap.
It has been working fine lately.
After 2 reboots it is now working again...I hope I can get this program to execute for me, it sure would save a lot of messing around.
Last edited by bandario; 2010-07-20 at 08:40. Reason: changed
It has been working fine lately.
After 2 reboots it is now working again...I hope I can get this program to execute for me, it sure would save a lot of messing around.
Last edited by bandario; 2010-07-20 at 08:40. Reason: changed
|
|
2010-07-20
, 23:16
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#95
|
bandario: Some report success with the Enter key when leaving the internal slider keyboard open. Also Ctrl-M and Ctrl-Enter seem to work.
jd4200: do you get any errors when running bt-kbd-remap? Or does it just appear to work (no error messages), but it doesn't really work?
jd4200: do you get any errors when running bt-kbd-remap? Or does it just appear to work (no error messages), but it doesn't really work?
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
 |
|
2010-07-20
, 23:46
|
|
Posts: 451 |
Thanked: 424 times |
Joined on Apr 2010
@ England
|
#96
|
Originally Posted by qole
No there are no errors at all.
bandario: Some report success with the Enter key when leaving the internal slider keyboard open. Also Ctrl-M and Ctrl-Enter seem to work.
jd4200: do you get any errors when running bt-kbd-remap? Or does it just appear to work (no error messages), but it doesn't really work?
I've left the model number in the config as the default, as I don't know what I should put for this, could that be the problem?
To sum up:
* Letters work fine
* Numbers work fine (holding down the key)
* Dedicated symbol keys don't work at all, except for "." and ","
* Blue FN key (for numbers and special commands) works for a few keys (FN + J/K adjusts the volume)
* Green FN (for special characters) key doesn't appear to do anything.
Last edited by jd4200; 2010-07-20 at 23:48.
|
|
2010-07-21
, 13:13
|
|
Posts: 35 |
Thanked: 14 times |
Joined on Apr 2010
@ Angers, France
|
#97
|
Originally Posted by qole
Qole,
nerfiaux: Connect your keyboard. Then you need to open a terminal and run:
This should enable the azerty layout and the blue and green characters.Code:bt-kbd-remap
I successfully got my Stowaway in french.
I did manually run the following command:
Code:
setxkbmap -device 4 -I/usr/share/X11/xkb-chinook -rules -model pc105 -layout fr
When is check the bluetooth devices for EXTKBD, in the list you don't remove the mac address xx:xx:xx:xx:xx:xx
For me the result of
Code:
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_tw14030keypad"
ID 5, Name: "00:13:17:70:78:23"
ID 4, Name: "Think Outside Keyboard"
So when I run the the script bt-kbd-remap it remaps the device 5 !
Also in my command :
Code:
setxkbmap -device 4 -I/usr/share/X11/xkb-chinook -rules -model pc105 -layout fr
Code:
Error loading new keyboard description
Code:
setxkbmap -device 4 -I -I/usr/share/X11/xkb-chinook -rules -model pc105 -layout fr
I am still looking for the fn keys to work...
Thanks again !
| The Following User Says Thank You to nerfiaux For This Useful Post: | ||
|
|
2010-07-21
, 16:03
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#98
|
Originally Posted by nerfiaux
Thanks for the tip! What is that anonymous device ID 5?
I checked your script bt-kbd-remap
When is check the bluetooth devices for EXTKBD, in the list you don't remove the mac address xx:xx:xx:xx:xx:xx
For me the result ofis :Code: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_tw14030keypad"
ID 5, Name: "00:13:17:70:78:23"
ID 4, Name: "Think Outside Keyboard"
So when I run the the script bt-kbd-remap it remaps the device 5 !
Originally Posted by nerfiaux
I'm pretty sure that the -I is required; it forces the setxkbmap command to only use the xkb-chinook mapping, and not use the standard xkb mapping. The xkb-chinook mappings are the only ones that will get the blue and green fn keys to work.
Also in my command :
I removed -I, because I add the messageCode:setxkbmap -device 4 -I/usr/share/X11/xkb-chinook -rules -model pc105 -layout fr
yours was :Code:Error loading new keyboard description
Maybe you can update your script ?Code:setxkbmap -device 4 -I -I/usr/share/X11/xkb-chinook -rules -model pc105 -layout fr
Probably the problem is that the Chinook mappings that qobi provided us didn't have the fr layout.
Originally Posted by nerfiaux
Perhaps we need international key mappings for chinook-xkb?
I am still looking for the fn keys to work...
Thanks again !
Or am I missing something here?
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
|
|
2010-07-22
, 10:44
|
|
Posts: 539 |
Thanked: 165 times |
Joined on Feb 2010
@ Berlin, Germany
|
#99
|
Hi all,
I just received a foldable keyboard from Chinfai and played a little with it. Of course, it didn't work immediately with the n900 so I had to go a bit deeper. First of all: the keyboard works perfectly on my Ubuntu-driven PC (I'm actually writing with it!) but I also didn't get it to work with my E90 and my 9500. It gets recognized but I can't use it.
After some playing on the n900 and various configurations it suddenly worked. That time I was just trying some commands with hildon-im-xkbtool . But I just don't kow if it was related to that. But "it worked" just means, it generated plain characters, no capitals, no numbers (long press on the uppermost keyrow generates numbers), no special characters. Switching to NumLock deactivates all blue-colored keys.
I set layout to base, pc105, de. But even after switching to us layout nothing changed, even not the layout, it still worked as qwertz.
Where can I find a simple step-by-step tutorial which leads me through the complete processs of activating a bt keyboard? All I can find are some small bits of information which only cover a special part of the setup.
I just received a foldable keyboard from Chinfai and played a little with it. Of course, it didn't work immediately with the n900 so I had to go a bit deeper. First of all: the keyboard works perfectly on my Ubuntu-driven PC (I'm actually writing with it!) but I also didn't get it to work with my E90 and my 9500. It gets recognized but I can't use it.
After some playing on the n900 and various configurations it suddenly worked. That time I was just trying some commands with hildon-im-xkbtool . But I just don't kow if it was related to that. But "it worked" just means, it generated plain characters, no capitals, no numbers (long press on the uppermost keyrow generates numbers), no special characters. Switching to NumLock deactivates all blue-colored keys.
I set layout to base, pc105, de. But even after switching to us layout nothing changed, even not the layout, it still worked as qwertz.
Where can I find a simple step-by-step tutorial which leads me through the complete processs of activating a bt keyboard? All I can find are some small bits of information which only cover a special part of the setup.
|
|
2010-07-23
, 11:23
|
|
Posts: 35 |
Thanked: 14 times |
Joined on Apr 2010
@ Angers, France
|
#100
|
Originally Posted by qole
It is a bluetooth headset Jabra BT620s
Thanks for the tip! What is that anonymous device ID 5?
Originally Posted by qole
Well, I don't know about chinook-xkd, sorry, so i can't tell.
I'm pretty sure that the -I is required; it forces the setxkbmap command to only use the xkb-chinook mapping, and not use the standard xkb mapping. The xkb-chinook mappings are the only ones that will get the blue and green fn keys to work.
Probably the problem is that the Chinook mappings that qobi provided us didn't have the fr layout.
Perhaps we need international key mappings for chinook-xkb?
Or am I missing something here?
BT Mouse (think outside stowaway travel mouse) and my BT headset (Jabra BT620s)
that when I move the mouse the sound is cut, it appears that the bandwidth is not enough for Mouse coordonates and the audio streaming ?
Any comments ?