Fanoush: Have had partial success in getting the Freedom Bluetooth portable keyboard to work with the new operating system and your modification to the hack. At first, it didn't work at all through my strict following of your instructions. However, in trying to discover why not, I noted that in your new kbdd directory (achieved through un-tarring) there were TWO uinput.ko files (uinput 2.6.16-omap1 and uinput.ko.2.6.16.27-omap1). I removed the first and tried again. Then I executed ./btkbd which succeeded in activating and deactivating my keyboard. (I had earlier also converted to the U.S. keyboard design (qwerty), which worked, too.) However, I could not then get the shortcut to work after installing it. (This was one of my earlier problems months ago before resolving it -- I don't recall how, hit-and-miss I guess!) Anyway, the shortcut is not working again. (Could it have anything to do with your script not employing a gainroot method matching mine; I use "sudo su" via the "becomeroot" application?) Also, when I hit the "enter" button on the keyboard, instead of executing a normal "enter" command, it instead serves as a toggle going back and forth with the on-screen keyboard (where the "enter" command does work!). You perhaps have noticed elsewhere in this forum that osso-xterm seems to be having problems with the new OS. The "backspace-delete" key moves the curser forward, creating little squares in its place. I wonder if this osso-xterm function has anything to do with my Freedom keyboard's malfunctioning "enter" key. Oh, well, any further thoughts -- and fixes -- you might have will as usual be much appreciated. (In a way, I would welcome a means of toggling with the onscreen keyboard, as that would enable me to access keystrokes not currently available to me on the Freedom keyboard, i.e. "|" and "~", but not through use of the "enter" key!)