Active Topics
-
Phone Camera Competition April 2021: "Funny & Foolish" (23)
to General by pichlo - 4 hrs, 34 mins ago -
Maemo-Leste pre-alpha announcement (512)
to Maemo 7 / Leste by nonsuch - 18 hrs, 6 mins ago -
The Intel RealSense Smartphone prototype (0)
to Competitors by n950 - 20 hrs, 40 mins ago -
Maemo Leste Playground (57)
to Maemo 7 / Leste by clort - 1 day, 17 hrs ago -
A Palm OS thread ... and a thank you to the community (23)
to Alternatives by bradvesp - 2 days, 17 hrs ago -
What's the best Handheld gnu/linux machine for 20XX? (77)
to Competitors by biketool - 3 days, 6 hrs ago -
Unofficial Storage for camera phone competition... (61)
to General by Maemish - 5 days, 9 hrs ago -
SailfishOS on Sony Z3 Compact Tablet (180)
to SailfishOS by ogustbiller - 5 days, 21 hrs ago -
Debian "squeeze" Image easy installer (24)
to Alternatives by sicelo - 6 days, 23 hrs ago - more...
|
2010-08-25
, 05:41
|
|
Posts: 49 |
Thanked: 23 times |
Joined on Oct 2009
@ Oulu, Finland
|
#322
|
Originally Posted by Skyscraper
I have similar problem with the Microsoft Bluetooth Mobile Keyboard 6000. I had first major problem to connect it and after I was able to connect, the keymapping don't work. I'll try to dig in more if I can found something, but nothing seems to help so far.
Hi!
I'm tried this and: It connects ok, but it wont set the right keyboard layout. Having ALWAYS the problem that i cant type numbers or slt. Only when i hold down QWERTZ... I get the numbers 123456.... Like on N900 Hardware keyboard.
I dont know how to remap it correctly ;(
Anyone can help me with this problem?
I've tried to use the BT Keyboard on an PC Xubuntu 10.04 and it worked great. Then I tried to export layout via xkbcomp and import it on n900 with xkbcomp but that didnt worked ?! (maybe i did anything wrong...)
|
|
2010-08-25
, 08:07
|
|
Posts: 49 |
Thanked: 23 times |
Joined on Oct 2009
@ Oulu, Finland
|
#323
|
Originally Posted by jakoleh
More future development:
Future development:
- Optify
- Create control panel widget to be able to add new keyboards more easily. This will also create the settings.conf file and starts the BlueKlase after exit. No more reboot needed.
- Put application to Extras-devel, create bug reporting (if this is really needed)
- Disable virtual keyboard when hw keyboard is attached and enable it again after keyboard is disconnected (if it was enabled anyway).
- add chinook xkb files to deb
- add pairing and connecting support to control panel widget. (I was't able to connect my microsoft keyboard until I sent dbus command org.bluez.Input.Connect)
| The Following User Says Thank You to jakoleh For This Useful Post: | ||
|
|
2010-09-01
, 11:40
|
|
Posts: 4 |
Thanked: 2 times |
Joined on Aug 2010
|
#324
|
Edit (solved for real this time I think):
I finally got numbers working, but I got the fix wrong in my first post. Of all the things I tried, it turned out to be this modified setxkbmap command that was the real solution:
setxkbmap -device 4 -I -I/usr/share/X11/xkb-chinook -rules base -model evdev -layout us -print|xkbcomp -i 4 - $DISPLAY
Confirmed that you can plug in pc105 instead of evdev and the same line also works, so it isnt an evdev or pc105 thing. I also tried all variations without piping through xkbcomp. It appears that piping through xkbcomp is what fixes it. In my case, I dont even need to hit a key on the internal keyboard, it just starts working right away with numbers.
I executed that command as a user, with the internal keyboard open.
For anyone curious, the solution that I 'thought' was responsible for the fix, was to type the normal setxkbmap command on the internal keyboard and then quickly close the internal keyboard right after hitting enter. When I tried that solution again today, it did not work, so I retraced my steps and it turns out that the diagnostic line above was what did it.
I have a qt app installed that someone made that auto launches the setxkbmap command, so I am in the process of getting rid of that to make sure that the combination of that script and this command are not jointly the solution. It also appears that a new bt-hid-scripts package has been released, so who knows, maybe this fix is in there? That sure would be fast
Last edited by Nokia349; 2010-09-01 at 19:37. Reason: Eliminated more variables...
I finally got numbers working, but I got the fix wrong in my first post. Of all the things I tried, it turned out to be this modified setxkbmap command that was the real solution:
setxkbmap -device 4 -I -I/usr/share/X11/xkb-chinook -rules base -model evdev -layout us -print|xkbcomp -i 4 - $DISPLAY
Confirmed that you can plug in pc105 instead of evdev and the same line also works, so it isnt an evdev or pc105 thing. I also tried all variations without piping through xkbcomp. It appears that piping through xkbcomp is what fixes it. In my case, I dont even need to hit a key on the internal keyboard, it just starts working right away with numbers.
I executed that command as a user, with the internal keyboard open.
For anyone curious, the solution that I 'thought' was responsible for the fix, was to type the normal setxkbmap command on the internal keyboard and then quickly close the internal keyboard right after hitting enter. When I tried that solution again today, it did not work, so I retraced my steps and it turns out that the diagnostic line above was what did it.
I have a qt app installed that someone made that auto launches the setxkbmap command, so I am in the process of getting rid of that to make sure that the combination of that script and this command are not jointly the solution. It also appears that a new bt-hid-scripts package has been released, so who knows, maybe this fix is in there? That sure would be fast
Last edited by Nokia349; 2010-09-01 at 19:37. Reason: Eliminated more variables...
| The Following User Says Thank You to Nokia349 For This Useful Post: | ||
|
|
2010-09-01
, 19:25
|
|
Posts: 49 |
Thanked: 23 times |
Joined on Oct 2009
@ Oulu, Finland
|
#325
|
Originally Posted by jakoleh
There is another project ongoing in the same area http://talk.maemo.org/showthread.php?t=58258. This project seems to be in more advanced level so I'm not going to implement BlueKlase any further (if somebody doesn't tell me why it should).
More future development:
- add chinook xkb files to deb
- add pairing and connecting support to control panel widget. (I was't able to connect my microsoft keyboard until I sent dbus command org.bluez.Input.Connect)
|
|
2010-09-17
, 22:41
|
|
Posts: 12 |
Thanked: 1 time |
Joined on Apr 2010
@ Santa Rosa
|
#326
|
Originally Posted by jakoleh
This is how I interpret the work you mention above. By installing the attached file BlueKlase my n900 will only need for me to include my keyboard id into the attached txt file which will be renamed to settings.conf and placed in a directory named folder contained in the path you provide above. Don't I need to be able to pair my keyboard to the n900 so that there will be a keyboard id? I then restart my phone. Following this procedure will then allow me to pair with my bluetooth keyboard. Have I got this correct and do I need to disable virtual keyboard manually before doing a restart?
I have created first version of the Bluetooth keyboard layout selector application (BlueKlase), as request in http://wiki.maemo.org/Fremantle_Blue...out#Next_steps.
This is precessor of the python script I wrote earlier.
!!!! This is first version so install this with your own risk. !!!
Installation instructions:
1) install attached deb file. It will install following files:
/etc/event.d/bluetooth-keyboard
/usr/bin/BlueKlase
2) Get your keyboard id using instruction from http://wiki.maemo.org/Fremantle_Blue..._Automatically
2) Edit attached settings.txt file and put your keyboard id there.
3) Copy file to /home/user/.config/BlueKlase/ folder.
4) rename it to settings.conf
5) Restart your phone
BlueKlase should start automatically and the system should work.
Future development:
- Optify
- Create control panel widget to be able to add new keyboards more easily. This will also create the settings.conf file and starts the BlueKlase after exit. No more reboot needed.
- Put application to Extras-devel, create bug reporting (if this is really needed)
- Disable virtual keyboard when hw keyboard is attached and enable it again after keyboard is disconnected (if it was enabled anyway).
|
|
2010-09-19
, 19:40
|
|
Posts: 6 |
Thanked: 0 times |
Joined on Sep 2010
|
#327
|
Hi ppl!
I'm trying to get my bt keyboard "Bluetooth Mini Keyboard" working, but I failed...I did everything you suggested, but numbers, symbols and arrow keys still don't work for me, and Russian symbols too.
Could anyone help me, I appreciate! This keyboard works well with my netbook running Windows 7.
Thank you!
I'm trying to get my bt keyboard "Bluetooth Mini Keyboard" working, but I failed...I did everything you suggested, but numbers, symbols and arrow keys still don't work for me, and Russian symbols too.
Could anyone help me, I appreciate! This keyboard works well with my netbook running Windows 7.
Thank you!
|
|
2010-09-19
, 21:05
|
|
Posts: 6 |
Thanked: 0 times |
Joined on Sep 2010
|
#328
|
Originally Posted by jakoleh
I think you should, because their solution doesn't work for me. I don't need to use Bt HID Scripts, because the keyboard connects, the only problem I have is wrong mapping.
There is another project ongoing in the same area http://talk.maemo.org/showthread.php?t=58258. This project seems to be in more advanced level so I'm not going to implement BlueKlase any further (if somebody doesn't tell me why it should).
|
|
2010-09-20
, 01:39
|
|
Posts: 992 |
Thanked: 738 times |
Joined on Jun 2010
@ Low Earth Orbit
|
#329
|
Originally Posted by virtual_one
Don't know if you're aware it does slightly more than that. It comes with a "watcher" script that you run once (per reboot - not sure whether qole has got it to autostart yet), and it will auto connect your mouse/keyboard - this is a great feature.
I don't need to use Bt HID Scripts, because the keyboard connects
I think you should, because their solution doesn't work for me, ... the only problem I have is wrong mapping.
|
|
2010-09-20
, 02:13
|
|
Posts: 6 |
Thanked: 0 times |
Joined on Sep 2010
|
#330
|
Originally Posted by kureyon
Ah, yes, you're right, it does connect automatically. But as you said I still need to get the keyboard layout, this is my question, how to get all keys working properly. Thank you.
Don't know if you're aware it does slightly more than that. It comes with a "watcher" script that you run once (per reboot - not sure whether qole has got it to autostart yet), and it will auto connect your mouse/keyboard - this is a great feature.
The BT HID scripts only automates the process, you still need to get the keyboard layout and mapping correct in the first place.
I'm tried this and: It connects ok, but it wont set the right keyboard layout. Having ALWAYS the problem that i cant type numbers or slt. Only when i hold down QWERTZ... I get the numbers 123456.... Like on N900 Hardware keyboard.
I dont know how to remap it correctly ;(
Anyone can help me with this problem?
I've tried to use the BT Keyboard on an PC Xubuntu 10.04 and it worked great. Then I tried to export layout via xkbcomp and import it on n900 with xkbcomp but that didnt worked ?! (maybe i did anything wrong...)
Would be great if anyone could help me!
Thank you!
Skyscraper