Page 8 of 36 « First 67 8 91018 Last »
Reply
Thread Tools
olighak is offline olighak
2010-01-24 , 22:34
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#71
Originally Posted by rabilancia View Post
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....
Ok. We've got 4 people upgraded to w51 who can't get it to work, and 2 who can. qobi is still running w42, which I myself got the keyboard to work with.

Maybe the key to their success was having connected the device prior to doing the upgrade. I don't want to flash to w42 today. I'll do it tomorrow during work. I'll then connect the keyboard, upgrade to w44 and try to connect and then upgrade to w51 and try to connect. We can then see where it drops off. Or if it works when doing that route.
Last edited by olighak; 2010-01-25 at 00:05.
 
cardiff-blues is offline cardiff-blues
2010-01-24 , 22:43
Posts: 739 | Thanked: 220 times | Joined on Dec 2009 @ Surrey, UK
#72
anyone knows why this error occurs?

$ 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
 
olighak is offline olighak
2010-01-24 , 22:46
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#73
Originally Posted by cardiff-blues View Post
anyone knows why this error occurs?

$ 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
Yep, there is no bluetooth device connected as "device 4". Your bt keyboard is not connected and hence you can't tell the N900 which settings to use for it.
 
cardiff-blues is offline cardiff-blues
2010-01-24 , 23:04
Posts: 739 | Thanked: 220 times | Joined on Dec 2009 @ Surrey, UK
#74
i seem to be able to pair the keyboard ok but just how does it know that the keyboard is going to be device 4?

also this applies to me as well
>>
When I look at the my "Settings / Bluetooth / Devices" and edit the Think Outside Keyboard, it does not show a connect option.
<<

what else should we be trying or checking?
__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
 
olighak is offline olighak
2010-01-24 , 23:13
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#75
Originally Posted by cardiff-blues View Post
i seem to be able to pair the keyboard ok but just how does it know that the keyboard is going to be device 4?

also this applies to me as well
>>
When I look at the my "Settings / Bluetooth / Devices" and edit the Think Outside Keyboard, it does not show a connect option.
<<

what else should we be trying or checking?
Because you have already got devices occupying spots 0 through 3 so the next one has naturally got to be 4.

Welcome to the group
 
cardiff-blues is offline cardiff-blues
2010-01-24 , 23:18
Posts: 739 | Thanked: 220 times | Joined on Dec 2009 @ Surrey, UK
#76
and how do i check these devices? Should i see them under bluetooth devices? Appologies if the question seems basic.
__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
 
olighak is offline olighak
2010-01-24 , 23:24
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#77
Originally Posted by cardiff-blues View Post
and how do i check these devices? Should i see them under bluetooth devices? Appologies if the question seems basic.
Write the following into X-Terminal and hit enter/return.

hildon-im-xkbtool --list

This will give you a list of the devices in positions 0-3. These devices will normally be there when you are running the N900.

They include your touchscreen, your physical keyboard, your on-screen keyboard and one more which I donīt remember what was.

If you would disable your on-screen keyboard in the Settings menu on the N900 you should only have devices in positions 0-2, and no on-screen keyboard popping up on the list
Last edited by olighak; 2010-01-24 at 23:29.
 

The Following User Says Thank You to olighak For This Useful Post:
cardiff-blues is offline cardiff-blues
2010-01-24 , 23:32
Posts: 739 | Thanked: 220 times | Joined on Dec 2009 @ Surrey, UK
#78
thanks oli.

so for those who do have this working - can you provide anything else for us to check?
__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
 
olighak is offline olighak
2010-01-24 , 23:56
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#79
I just reflashed to week 42.

The keyboard works.

Now to do the minor OTA to week 44.

Update 1:
The keyboard works.

Now to do the major OTA to week 51.

Update 2:
Works, but only after stopping and starting bluetoothd
Last edited by olighak; 2010-01-25 at 00:33.
 

The Following User Says Thank You to olighak For This Useful Post:
olighak is offline olighak
2010-01-25 , 00:34
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#80
Originally Posted by olighak View Post
I just reflashed to week 42.

The keyboard works.

Now to do the minor OTA to week 44.

Update 1:
The keyboard works.

Now to do the major OTA to week 51.

Update 2:
Works, but only after stopping and starting bluetoothd
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.
Last edited by olighak; 2010-01-25 at 00:39.
 

The Following 3 Users Say Thank You to olighak For This Useful Post:
Reply
Page 8 of 36 « First 67 8 91018 Last »

« Previous Thread | Next Thread »

 
Forum Jump


All times are GMT. The time now is 10:52.

Contact Us - Home - Archive - Top