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?
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.
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.
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.
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.
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.
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.
