Reply
Thread Tools
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#91
Jan and Jeffrey,

I canīt get it to remain connected for a extended period of time, or enough time to get a log to you. I can see the icon become blue for 5-10 secs and then disappear.

Iīve gone through the motions multiple times.

I canīt seem to replicate what I did 2 hours ago, where it remained connected for at least a good 10 minutes after OTA to week 51.

I figure the worst thing that can happen if I copy the bluetoothd file from usr/sbin, the week 46 version into the week 51 firmware, is that the device will bricked. Maybe that is something to try?

Last edited by olighak; 2010-01-25 at 02:25.
 
Posts: 77 | Thanked: 63 times | Joined on Sep 2009
#92
Try changing the batteries on your bluetooth keyboard.
 
Posts: 77 | Thanked: 63 times | Joined on Sep 2009
#93
Can you just do an ls -l on /etc/event.d/bluetooth-sysinfo, /etc/event.d/bluetoothd, and /usr/sbin/bluetoothd and send me the dates and sizes?

Also does 46 work for longer? Can you reboot 46 and have it still work?
 
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#94
Originally Posted by qobi View Post
Try changing the batteries on your bluetooth keyboard.
No it isnīt working. Also I can see that there is some information on previously stored bluetooth devices being stored somewhere.


I changed the name of the device. Then deleted the device. When I went back to re-pair the N900 did not come back with the standard "Bluetooth Keyboard" name but the custom one I had given it earlier.
 
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#95
Originally Posted by qobi View Post
Can you just do an ls -l on /etc/event.d/bluetooth-sysinfo, /etc/event.d/bluetoothd, and /usr/sbin/bluetoothd and send me the dates and sizes?

Also does 44 work for longer? Can you reboot 44 and have it still work?
Week 51 firmware:
/etc/event.d/bluetooth-sysinfo 384 Jul 27 03:47
/etc/event.d/bluetoothd 594 Nov 18 05:43
/usr/sbin/bluetoothd 338920 Nov 18 05:46

I have copied the files from event.d onto the tmp directory in my MyDocs if you care for them.

I am going to reflash back to 42 and upgrade to week 44. It did work for at least 5 mins in both cases I did that. So yes I believe so.

Iīll give you the numbers on these files above from the week 44 firmware. But from the files above you can see that on Nov. 18th they likely made the changes that disabled the bluetooth keyboard.

Week 44 firmware:
/etc/event.d/bluetooth-sysinfo 384 Jul 27 03:47
/etc/event.d/bluetoothd 586 Sep 16 04:22
/usr/sbin/bluetoothd 344520 Sep 16 04:24
Attached Files
File Type: txt bluetoothd-week51.txt (594 Bytes, 111 views)
File Type: txt bluetooth-sysinfo-week51.txt (384 Bytes, 119 views)
File Type: txt bluetoothd-week44.txt (586 Bytes, 114 views)

Last edited by olighak; 2010-01-25 at 03:07.
 
Posts: 77 | Thanked: 63 times | Joined on Sep 2009
#96
Originally Posted by olighak View Post
No it isnīt working. Also I can see that there is some information on previously stored bluetooth devices being stored somewhere.


I changed the name of the device. Then deleted the device. When I went back to re-pair the N900 did not come back with the standard "Bluetooth Keyboard" name but the custom one I had given it earlier.
Because it remembers the bluetooth address. I think it might store this info in the gconf database.
 
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#97
Originally Posted by qobi View Post
Because it remembers the bluetooth address. I think it might store this info in the gconf database.
Might that database store something else interesting, like information on how it should treat the specific devices?
 
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#98
Originally Posted by olighak View Post
Week 51 firmware:
/etc/event.d/bluetooth-sysinfo 384 Jul 27 03:47
/etc/event.d/bluetoothd 594 Nov 18 05:43
/usr/sbin/bluetoothd 338920 Nov 18 05:46

I have copied the files from event.d onto the tmp directory in my MyDocs if you care for them.

I am going to reflash back to 42 and upgrade to week 44. It did work for at least 5 mins in both cases I did that. So yes I believe so.

Iīll give you the numbers on these files above from the week 44 firmware. But from the files above you can see that on Nov. 18th they likely made the changes that disabled the bluetooth keyboard.

Week 44 firmware:
/etc/event.d/bluetooth-sysinfo 384 Jul 27 03:47
/etc/event.d/bluetoothd 586 Sep 16 04:22
/usr/sbin/bluetoothd 344520 Sep 16 04:24
Guys see this difference between week 51 and week 44.

Swapping out the week 51 bluetoothd files for the week 44 ones does not work. If you do bluetooth just wonīt start up at all.

I filed a bug for this change. Not getting my hopes up for it to be addressed, but maybe the Nokia people didnīt intend on this.
https://bugs.maemo.org/show_bug.cgi?id=8483

Please vote for getting Nokia to make it possible to connect to bluetooth keyboards again.

Last edited by olighak; 2010-01-25 at 04:21.
 
Posts: 220 | Thanked: 129 times | Joined on Nov 2009
#99
Originally Posted by olighak View Post
Guys see this difference between week 51 and week 44.

Swapping out the week 51 bluetoothd files for the week 44 ones does not work. If you do bluetooth just wonīt start up at all.

I filed a bug for this change. Not getting my hopes up for it to be addressed, but maybe the Nokia people didnīt intend on this.
https://bugs.maemo.org/show_bug.cgi?id=8483

Please vote for getting Nokia to make it possible to connect to bluetooth keyboards again.
Voted for this bug.
 
Posts: 739 | Thanked: 220 times | Joined on Dec 2009 @ Surrey, UK
#100
what do i need to do to vote?
__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
 
Reply


 
Forum Jump


All times are GMT. The time now is 12:11.