I can confirm that I've not had to re-connect the keyboard by hitting ctrl + green fn + blue fn at all since I've run hidd --server after the initial hidd --connect. I just open up the keyboard and tap a key.
I had uninstalled all previous bluetooth configurations before I installed the latest code from:
Something Interesting Bluetooth PageI used:
# bluez-libs_2.21_arm.ipk(25) (2005.09.14)
# bluez-utils_2.21_arm.ipk(17) (2005.09.14)
# openobex-libs_1.0.1_arm.ipk(80)
and the hidp.o correction package (I can't remember if I went and got a different hidp.o that was mentioned further down the page where it is said that it's made with the US translation table):
bluez-hidp_mh18_arm.ipk.C1000(45) (C1000/C3x00)
I also had the following on my system:
# sudo_0.1.ipk
# susp-resume_0.9-3.1.ipk
# susp-resume-bluez_0.9.1_arm.ipk
I found that, at least for me and my Socket Bluetooth Rev. G card, the Maikichi /etc/pcmcia/bluetooth and /etc/rc.d/init.d/bluetooth scripts were broken. What I did was I used the startup scripts and the /etc/bluetooth/uart file that came with the (old?) bluez-zaurus from Tumnus listed in this thread:
https://www.oesf.org/forums/index.php?showtopic=9995I didn't install the package mind you. I just dumped the pieces out of it and copied them into their respective places. I've attached a script that I created called ipkghelper (I use it on my desktop mainly to tear apart ipk's and see what's in it and what I want instead of from my Z though it should work fine on the Z) in case you don't know how to take the ipk apart by hand (or don't want to). I've put it in the public domain so if it destroys your computer, don't look at me. It hasn't destroyed mine... yet But it's all shell script so you should be able to read it and understand what's going on in it.
Seems I had to 'zip' the ipkghelper file as this system didn't like it when I just uploaded the shell script bare. So you'll have to unzip it. I've also included a gzipped version in case you don't have an unzip program on your system. I ended up on a system somewhere the other day with no unzip. I couldn't believe it.
You can list what's in the ipk with:
ipkghelper the-package.ipk
and it will simply list the contents of the .ipk file. If you just run ipkghelper you'll get the usage details.
And running
ipkghelper --dump-all the-package.ipk
will dump the package to a directory named after the filename without the .ipk extension.
Or you can also run
ipkghelper --dump-all the-package.ipk dump_dir
and ipkghelper will extract everything to the dump_dir you specified.
I hope this helps!