Reply
Thread Tools
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#51
Originally Posted by dnastase View Post
Yes: 2.2009.51-1.002, upgraded OTA (app manager).

/home/user # lsmod | grep -i hid
hidp 12544 0
hid 31940 1 hidp
l2cap 21060 17 hidp,rfcomm,bnep
bluetooth 53596 10 hidp,rfcomm,sco,bnep,l2cap,hci_h4p

Did not do anything special about the modules/bluetooth. It's how it is after a reboot.
Interesting. Now I am tempted to backup, reflash my device to week 44 and then do OTA to week 51 and see what happens.....

Thanks!
 
Posts: 121 | Thanked: 54 times | Joined on Oct 2007 @ New York, US
#52
Did you do the /etc/bluetooth/main.conf trick from

http://talk.maemo.org/showthread.php?t=34872

?
 
Posts: 519 | Thanked: 366 times | Joined on Sep 2009 @ North Carolina (Formerly Denmark and Iceland)
#53
Originally Posted by dnastase View Post
Did you do the /etc/bluetooth/main.conf trick from

http://talk.maemo.org/showthread.php?t=34872

?
Yep, and I did have my bluetooth keyboard working prior to updating from the week 44 firmware. It is a palm branded bt keyboard, but I think I remember seeing the same identical keyboard sold as a StowAway keyboard some years back.

The firmware currently installed was flashed to the week 51 firmware, as I had bricked the phone several times messing around with reconfiguring the russian keyboard to something useful to me.

After flashing to week 51 I canīt get the bt keyboard to work. I can pair with it but it wonīt connect, even after following all steps found here and there. Jan, who also took part in this thread had the same problem on his week 51 firmware. qobi is running the week 44 firmware.

Last edited by olighak; 2010-01-24 at 17:59.
 
Posts: 145 | Thanked: 88 times | Joined on Nov 2009 @ Copenhagen
#54
just for your information, I also updated to the latest firmware OTA, and I have a functional setup with a Nokia SU-8W.

I did however have to stop and start bluetoothd (issuing "bluetoothd stop", "bluetoothd start" as root) before I could connect the keyboard.
 

The Following User Says Thank You to filologen For This Useful Post:
Posts: 739 | Thanked: 220 times | Joined on Dec 2009 @ Surrey, UK
#55
thanks for your help oli. Much appreciated.
__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
 
Posts: 77 | Thanked: 63 times | Joined on Sep 2009
#56
If you flash, it will overwrite any changes you made to /etc/bluetooth/main.conf so you will need to redo that change. If you do OTA then it uses apt-get which will preserve those changes. olighak and Jan, can you try to redit /etc/bluetooth/main.conf and see whether that works. you will need to stop bluethood and start bluetoothd as root after you edit /etc/bluetooth/main.conf but you should not have to do that after reboots.
 

The Following User Says Thank You to qobi For This Useful Post:
Posts: 739 | Thanked: 220 times | Joined on Dec 2009 @ Surrey, UK
#57
forgive this basic question.
i have downloaded xkb-chinook.tar and saved it to tmp from n900 but when i list tmp it is not being displayed. Any ideas?
__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
 
Posts: 27 | Thanked: 3 times | Joined on Nov 2007
#58
It's probably in /home/usr/MyDocs/tmp not in /tmp
 

The Following User Says Thank You to rabilancia For This Useful Post:
Posts: 739 | Thanked: 220 times | Joined on Dec 2009 @ Surrey, UK
#59
Originally Posted by qobi View Post
It is safer and easier to do this directly on the N900 rather than a Windows desktop by:

1. copying the file xkb-chinook.tar from my earlier post to /tmp on your N900.
2. then do

$ sudo gainroot
# cd /tmp
# tar xf xkb-chinook.tar
# mv -i /tmp/xkb-chinook /usr/share/X11/.
# exit

There are several reasons you want to do the above as root on a Unix/Linux machine on a Unix/Linux file system (such as ext2, ext3, ...). Among them, to preserve file/directory uids, gids, and permissions (and ctimes and mtimes while you are at it), as well as symlinks.
/home/user/MyDocs/tmp # ls
xkb-chinook xkb-chinook.tar
/home/user/MyDocs/tmp # mv -i /tmp/xkb-chinook /usr/share/X11/.
mv: cannot rename '/tmp/xkb-chinook': No such file or directory
__________________
There is a way that seems right to a man, but in the end it leads to death. Proverbs 14:12
 
Posts: 27 | Thanked: 3 times | Joined on Nov 2007
#60
Since you get this:
/home/user/MyDocs/tmp # ls
xkb-chinook xkb-chinook.tar

Try this:
/home/user/MyDocs/tmp # mv -i ./xkb-chinook /usr/share/X11/.
 
Reply


 
Forum Jump


All times are GMT. The time now is 02:44.