Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 13 hrs, 3 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days, 1 hr ago - more...
|
2010-01-25
, 00:56
|
|
Posts: 519 |
Thanked: 366 times |
Joined on Sep 2009
@ North Carolina (Formerly Denmark and Iceland)
|
#82
|
Originally Posted by qobi
Nope, it became unable to connect after reboot. And I canīt get it back in.
What if you reboot now. You should be able to connect to the keyboard without stopping and starting bluetoothd. And you shouldn't need to repair. And you shouldn't need to click on connect. All you should need to do is turn on the external keyboard and press a (few) key(s) on the external keyboard. It should then connect (after a few seconds). The bluetooth symbol on the top of the screen should turn from white to blue. And you should be able to type. Then you can issue the setxkbmap command (and type a key on the internal keyboard) and it should work.
Can you verify this?
Modules hid and hidp have also disappeared.
Update:
Hang on I am going to reflash. I might have screwed this up when I tried to restore my backup settings and programs. Both those operations failed, but something might have changed nevertheless.
Last edited by olighak; 2010-01-25 at 01:02.
|
|
2010-01-25
, 01:06
|
|
Posts: 77 |
Thanked: 63 times |
Joined on Sep 2009
|
#83
|
What if after you upgrade to 51 you delete the existing entry for the keyboard in the bluetooth menu and then repair? I vaguely remember some post to the effect that the format of the bluetooth connection database has changed. But I can't find the post now and I may misremember.
The hid and hidp modules disappearing is a symptom, not a cause. The modules should be installed automatically by the bluetooth demon. And for reasons that I don't understand, the bluetooth demon is not starting up configured to do keyboard input.
The hid and hidp modules disappearing is a symptom, not a cause. The modules should be installed automatically by the bluetooth demon. And for reasons that I don't understand, the bluetooth demon is not starting up configured to do keyboard input.
|
|
2010-01-25
, 01:10
|
|
Posts: 519 |
Thanked: 366 times |
Joined on Sep 2009
@ North Carolina (Formerly Denmark and Iceland)
|
#84
|
Originally Posted by qobi
I donīt get it in when I do that. In fact I am afraid that trying to re-pair or reinstall it may be what breaks the link so to speak.
What if after you upgrade to 51 you delete the existing entry for the keyboard in the bluetooth menu and then repair? I vaguely remember some post to the effect that the format of the bluetooth connection database has changed. But I can't find the post now and I may misremember.
The hid and hidp modules disappearing is a symptom, not a cause. The modules should be installed automatically by the bluetooth demon. And for reasons that I don't understand, the bluetooth demon is not starting up configured to do keyboard input.
In other words I am starting to believe that the keyboard only works because itīs done so before. But when you re-pair it you break the old link and start at the beginning.
Update:
Just to let you know I am now upgrading again from week 46 to week 51.
Last edited by olighak; 2010-01-25 at 01:32.
|
|
2010-01-25
, 01:32
|
|
Posts: 13 |
Thanked: 5 times |
Joined on Jan 2010
|
#85
|
Originally Posted by olighak
In order to get to these differences, I've attached my /etc/main.conf (renamed to "main.txt" to keep the attachment facility happy) file and the output of "lsmod" and of "ps aux" in files "lsmod.txt" and "ps.txt", respectively. I ran "ps" and "lsmod" after pairing my keyboard but not getting a new device according to hildon-im-xkbtool. Can you compare these to what you get after successfully connecting up with the keyboard, or post your main.conf, kernel module and process lists?
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.
Best regards, Jan
|
|
2010-01-25
, 01:50
|
|
Posts: 77 |
Thanked: 63 times |
Joined on Sep 2009
|
#86
|
More important than the output of lsmod and ps is to see the contents of
/etc/event.d/bluetooth-sysinfo
and
/etc/event.d/bluetoothd
Also do an ls -l on them.
/etc/event.d/bluetooth-sysinfo
and
/etc/event.d/bluetoothd
Also do an ls -l on them.
|
|
2010-01-25
, 01:55
|
|
Posts: 519 |
Thanked: 366 times |
Joined on Sep 2009
@ North Carolina (Formerly Denmark and Iceland)
|
#87
|
Ok guys, Jan and Jeff/Jeffrey
This may be the most stupid question ever.
But what is the easiest was to get a log like this out of X-terminal?
The phone is about to restart after the week 46 to 51 OTA update.
Best wishes,
Oli
This may be the most stupid question ever.
But what is the easiest was to get a log like this out of X-terminal?
The phone is about to restart after the week 46 to 51 OTA update.
Best wishes,
Oli
|
|
2010-01-25
, 01:56
|
|
Posts: 77 |
Thanked: 63 times |
Joined on Sep 2009
|
#88
|
Could you also do an ls -l /usr/sbin/bluetoothd on 51.
|
|
2010-01-25
, 01:59
|
|
Posts: 77 |
Thanked: 63 times |
Joined on Sep 2009
|
#89
|
Originally Posted by olighak
Redirect as much as you can to files. The rest, cut and paste into vi.
Ok guys, Jan and Jeff/Jeffrey
This may be the most stupid question ever.
But what is the easiest was to get a log like this out of X-terminal?
The phone is about to restart after the week 46 to 51 OTA update.
Best wishes,
Oli
A more powerful way is to install emacs and run in a shell buffer then save it as a file.
|
|
2010-01-25
, 02:08
|
|
Posts: 77 |
Thanked: 63 times |
Joined on Sep 2009
|
#90
|
Originally Posted by jtkim
Your /etc/bluetooth/main.conf is identical to mine except for a comment.
In order to get to these differences, I've attached my /etc/main.conf
Can you verify this?