Active Topics
-
Porting apps to Leste (29)
to Maemo 7 / Leste by Arno_11 - 3 days, 7 hrs ago -
Install Fonts in N900 (68)
to Maemo 5 / Fremantle by teroyk - 4 days, 10 hrs ago - more...
olighak |
2010-01-28
, 18:45
|
|
Posts: 519 |
Thanked: 366 times |
Joined on Sep 2009
@ North Carolina (Formerly Denmark and Iceland)
|
#111
|
Originally Posted by dnastase
Absolutely. I made the mistake of not reading through the changelog for 1.1 before I upgraded. If I had known that there were irreversible firmware updates for the cellular chip I would probably not have updated. The fact that IŽd lose ability to use the N900 as a cellphone is what is keeping me away from "downgrading" back to firmware from week 44. (PR1.01)
|
|
2010-01-29
, 02:24
|
|
Posts: 1 |
Thanked: 0 times |
Joined on Jan 2010
|
#112
|
I don't know if this helps the discussion at all, but before I upgraded OTA to 51-1, I had successfully paired my ThinkOutside Keyboard, and noticed that under
Bluetooth > Devices, ThinkOutside Keyboard, Edit
I had an option button to connect/disconnect the device, which worked as advertised -- if the keyboard was not connected, the connect button was visible, and vice versa.
Now, under 51-1, the button is permanently set to 'disconnect' and grayed-out. Clicking it causes 'no active connection' to flash at the top of the screen.
I didn't check whether this connect/disconnect feature worked on any other bluetooth devices before the 51-1 OTA upgrade, but certainly now it is also set to a grayed-out 'disconnect' for my laptop, even though they are not actually connected.
If connect to my laptop and send a file using petrovich, the disconnect button becomes live during the transfer, then grayed-out again afterwards.
In summary, it seems like the connect/disconnect feature has changed behaviour as part of the upgrade, and I wonder if this is related to our keyboard connectivity issues?
Bluetooth > Devices, ThinkOutside Keyboard, Edit
I had an option button to connect/disconnect the device, which worked as advertised -- if the keyboard was not connected, the connect button was visible, and vice versa.
Now, under 51-1, the button is permanently set to 'disconnect' and grayed-out. Clicking it causes 'no active connection' to flash at the top of the screen.
I didn't check whether this connect/disconnect feature worked on any other bluetooth devices before the 51-1 OTA upgrade, but certainly now it is also set to a grayed-out 'disconnect' for my laptop, even though they are not actually connected.
If connect to my laptop and send a file using petrovich, the disconnect button becomes live during the transfer, then grayed-out again afterwards.
In summary, it seems like the connect/disconnect feature has changed behaviour as part of the upgrade, and I wonder if this is related to our keyboard connectivity issues?
|
|
2010-01-29
, 03:44
|
|
Posts: 13 |
Thanked: 3 times |
Joined on Jan 2010
|
#113
|
Originally Posted by qobi
Sorry for nub question but can somebody create a comprehensive step by step instruction without referencing other posts? Thanks a lot.
I figured out why other people were not able to replicate my ability to get bluetooth keyboards to work. It was due to residue from some of my early attempts. This post outlines what I believe should work for everyone.
First, let me emphasize that you should not attempt to do this unless you know what you are doing. If you make a mistake and mess up the /usr/share/X11/xkb directory you will brick your device and need to reflash. I know because I did.
This assumes that you have already enabled HID bluetooth by editing /etc/bluetooth/main.conf as described elsewhere. And that you hae already installed /usr/share/X11/xkb-chinook from the tar file that I posted earlier in this thread.
As root do:
# cd /usr/share/X11
# cp -i xkb-chinook/symbols/pc xkb/symbols/.
# cp -i xkb-chinook/symbols/us xkb/symbols/.
# cp -i xkb-chinook/geometry/pc xkb/geometry/.
Make sure that in the above you give cp the -i option and that you do not overwrite any files in /usr/share/X11/xkb/
Then as user do:
$ setxkbmap -device 4 -I -I/usr/share/X11/xkb-chinook -rules base -model pc105 -layout us
Then type a key (any key) on the internal keyboard. Now the external keyboard should work.
I don't know why you need to type a key on the internal keyboard for this to take effect.
The above assume that the keyboard is connected to device 4 which is what usually happens. But you should check first as described earlier in this thread.
You will need to reissue the setxkbmap command (as user) and type a key on the internal keyboard each time you connect the bluetooth keyboard. I find that periodically, the bluetooth connection to the keyboard is dropped and reinitialized. I don't know why this happens. But when it does you need to reissue the setxkbmap command and type a key on the internal keyboard. So I find it useful to have a shell script for it.
If someone else gets this to work, I'd appreciate hearing about it.
I love my n900.
BugHunter
| The Following User Says Thank You to BugHunter For This Useful Post: | ||
|
|
2010-01-29
, 18:39
|
|
Posts: 45 |
Thanked: 36 times |
Joined on Jan 2010
|
#114
|
Hello,
I have just purchased a freedom pro keyboard ( http://www.freedominput.com/freedom-...m-pro-keyboard ) but I am unable to get it working. It won't work at all. I have enabled the bluetooth input plugin as described at http://wiki.maemo.org/Fremantle_Unsu...tooth_profiles and restarted bluetooth as well.
I am able to succesfully pair the keyboard (N900 does even show that it's a keyboard device), but issuing hildon-im-xkbtool --list does not show the keyboard connected.
What can be wrong? I thought the only difference between bluetooth keyboards is if they support SPP or HID profile (this one supports both), am I wrong?
By the way, I have tried to pair the keyboard with my notebook and it works fine there.
I have just purchased a freedom pro keyboard ( http://www.freedominput.com/freedom-...m-pro-keyboard ) but I am unable to get it working. It won't work at all. I have enabled the bluetooth input plugin as described at http://wiki.maemo.org/Fremantle_Unsu...tooth_profiles and restarted bluetooth as well.
I am able to succesfully pair the keyboard (N900 does even show that it's a keyboard device), but issuing hildon-im-xkbtool --list does not show the keyboard connected.
What can be wrong? I thought the only difference between bluetooth keyboards is if they support SPP or HID profile (this one supports both), am I wrong?
By the way, I have tried to pair the keyboard with my notebook and it works fine there.
|
|
2010-01-29
, 20:22
|
|
Posts: 739 |
Thanked: 220 times |
Joined on Dec 2009
@ Surrey, UK
|
#115
|
Originally Posted by olighak
Guys, report this issue officially and hopefully we'll get a authorised fix for it. Oli's instructions are quoted above.
There is a separate login system for bugs.maemo.org from the one we use here on talk.maemo.org
You need to create a account here:
https://bugs.maemo.org/createaccount.cgi
Once youŽve created an account you can login:
https://bugs.maemo.org/index.cgi?GoAheadAndLogIn=1
And then you can go and vote on the bug:
https://bugs.maemo.org/votes.cgi?act...8483#vote_8483
When you are on the vote page you place a little tick mark in the box in front of the name and number of the bug, and then you click the "Change my votes" button at the bottom of the page to register the vote
Here below is a link to a search filter for all N900 bugs reported. Feel free to go through those, comment and vote as well on those you feel are important. Voting at least shows our friends at Nokia that there is some interest for getting these "bugs" fixed.
N900 bug search
__________________
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-30
, 03:02
|
|
Posts: 77 |
Thanked: 63 times |
Joined on Sep 2009
|
#116
|
My understanding is that fililogen has a Nokia SU-8W, olighak has a palm
keyboard which he believes is identical to a Stowaway, woody14619 has a Palm
3245WW, JoHnY has a freedom pro, and jtkim, cardiff-blues, dnastase,
rabilancia, poser, beel, and I (qobi) have an iGo Think Outside.
My understanding is that everyone above except me is running 51.
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.
My understanding is that everyone succeeds in pairing the bluetooth keyboard.
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.
My understanding is that poser, filologen, and dnastase created a bluetooth
connection to their keyboard from their N900 prior to upgrading to 51 but
olighak, woody14619, JoHnY, jtkim, cardiff-blues, rabilancia, and beel did not.
Please correct any mistakes in the above.
Can people who successfully connect their bluetooth keyboard to their N900
under 51 please send me the output of:
$ gconftool -R /system/bluetooth
And can people who are unsuccessful at connecting their bluetooth keyboard to
their N900 under 51 also send me the output of the above.
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?
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.)
keyboard which he believes is identical to a Stowaway, woody14619 has a Palm
3245WW, JoHnY has a freedom pro, and jtkim, cardiff-blues, dnastase,
rabilancia, poser, beel, and I (qobi) have an iGo Think Outside.
My understanding is that everyone above except me is running 51.
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.
My understanding is that everyone succeeds in pairing the bluetooth keyboard.
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.
My understanding is that poser, filologen, and dnastase created a bluetooth
connection to their keyboard from their N900 prior to upgrading to 51 but
olighak, woody14619, JoHnY, jtkim, cardiff-blues, rabilancia, and beel did not.
Please correct any mistakes in the above.
Can people who successfully connect their bluetooth keyboard to their N900
under 51 please send me the output of:
$ gconftool -R /system/bluetooth
And can people who are unsuccessful at connecting their bluetooth keyboard to
their N900 under 51 also send me the output of the above.
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?
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.)
|
|
2010-01-30
, 05:55
|
|
Posts: 145 |
Thanked: 88 times |
Joined on Nov 2009
@ Copenhagen
|
#117
|
Firstly I can confirm that I have a working Nokia su-8w, that I did an OTA upgrade to 44 and 51, and that I had already paired the keyboard prior to both updates.
Secondly, here is the result of the gconftool command:
I will try to conect to another bluetooth device and repport failure or success later this weekend.
Best regards
Last edited by filologen; 2010-01-30 at 05:57.
Secondly, here is the result of the gconftool command:
Code:
devices = [00:0E:ED:9C:97:63] /system/bluetooth/device: /system/bluetooth/device/00:0F:6F:00:18:84: services = [SPP] /system/bluetooth/device/00:0E:ED:9C:97:63: name = Nokia SU-8W services = [HID,00001200-0000-1000-8000-00805f9b34fb] class = 16770368 icon = control_keyboard
Best regards
Last edited by filologen; 2010-01-30 at 05:57.
|
|
2010-01-30
, 11:35
|
|
Posts: 739 |
Thanked: 220 times |
Joined on Dec 2009
@ Surrey, UK
|
#118
|
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
~ $
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:6D
F:E3,00:19:15:32:3B :67]/system/bluetooth/device:
/system/bluetooth/device/00:0C:78:6D
F: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
~ $
__________________
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-30
, 22:36
|
|
Posts: 6 |
Thanked: 0 times |
Joined on Dec 2009
@ London
|
#119
|
Originally Posted by qobi
Thank you so much to all you people! I followed qobi's instructions and now I can punctuate sentences from my SU-8W!
My understanding is that fililogen has a Nokia SU-8W, olighak has a palm
keyboard which he believes is identical to a Stowaway, woody14619 has a Palm
3245WW, JoHnY has a freedom pro, and jtkim, cardiff-blues, dnastase,
rabilancia, poser, beel, and I (qobi) have an iGo Think Outside.
My understanding is that everyone above except me is running 51.
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.
My understanding is that everyone succeeds in pairing the bluetooth keyboard.
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.
My understanding is that poser, filologen, and dnastase created a bluetooth
connection to their keyboard from their N900 prior to upgrading to 51 but
olighak, woody14619, JoHnY, jtkim, cardiff-blues, rabilancia, and beel did not.
Please correct any mistakes in the above.
Can people who successfully connect their bluetooth keyboard to their N900
under 51 please send me the output of:
$ gconftool -R /system/bluetooth
And can people who are unsuccessful at connecting their bluetooth keyboard to
their N900 under 51 also send me the output of the above.
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?
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.)
It did not work when I originally expanded the xkb-chinook.tar file on my PC and copied the folder to the N900, so used the tar command on the N900 as instructed. I am using week 51. This is the third N900 I've had, (first two had problems) and the week 51 update happened on the evening I took it home from the store, so I've only connected the KB since then.
I've voted on on the bug page.
|
|
2010-01-31
, 00:42
|
|
Posts: 27 |
Thanked: 3 times |
Joined on Nov 2007
|
#120
|
qobi,
I can confirm your summary of my specific situation.
Here is the output from 'gconftool':
devices = [00:0A:30:60:1E:E0,00:19:15:132:A1]
/system/bluetooth/device:
/system/bluetooth/device/00:0A:30:60:1E:E0:
name = HandsFreeLink TM
services = [audio,object transfer,OPP,HFP]
class = 16770056
icon = control_bluetooth_audio_handsfree
/system/bluetooth/device/00:19:15:132:A1:
strong_pin_pairing = false
name = Think Outside Keyboard
services = [HID,00001200-0000-1000-8000-00805f9b34fb]
class = 16770368
icon = control_keyboard
Also, I can successfully pair and repeatedly connect to my Honda Accord Bluetooth "hands free" as well as pair and repeatedly connect from two different laptops via Bluetooth DUN after installing "Bluetooth Dial-Up Networoking" v1.0-6.
Thanks for leading this effort!
Rich
I can confirm your summary of my specific situation.
Here is the output from 'gconftool':
devices = [00:0A:30:60:1E:E0,00:19:15:13
2:A1]/system/bluetooth/device:
/system/bluetooth/device/00:0A:30:60:1E:E0:
name = HandsFreeLink TM
services = [audio,object transfer,OPP,HFP]
class = 16770056
icon = control_bluetooth_audio_handsfree
/system/bluetooth/device/00:19:15:13
2:A1:strong_pin_pairing = false
name = Think Outside Keyboard
services = [HID,00001200-0000-1000-8000-00805f9b34fb]
class = 16770368
icon = control_keyboard
Also, I can successfully pair and repeatedly connect to my Honda Accord Bluetooth "hands free" as well as pair and repeatedly connect from two different laptops via Bluetooth DUN after installing "Bluetooth Dial-Up Networoking" v1.0-6.
Thanks for leading this effort!
Rich