I have ordered one myself, will thoroughly test it and report back here

Should revise it in a week or so.

oke... nevermind the holders... what about special characters when using keyboard!? those on FN button?

They all work fine with the NUU MiniKey

and there is no way for other chinese beayboards to make it work?

I didn't say it wouldn't work, just that i only know for sure the NUU MiniKey works!

And I'll report here shortly if it does work as well for non-QWERTY NUU Minikeys.

You would need a strong magnifying glass just to fit the mini n9 into the holder

I received my Minikey too! It looks however that it is more complicated to make it work well in non-QWERTY mode. I edited the /etc/X11.conf.d/nokia.conf file to add a line for a "fr" layout (and fell into a reboot loop because of a typo, but finally fixed it ), then used the "setxkbmap -layout fr" commandline, but the keyboard is still acting as a QWERTY one.

By the way Godofwar424, could you please clearly explain how you paired the keyboard? If I put it in pair mode and launch Btinput, Btinput will find it and connect without asking a code. But then, if I close and reopen the keyboard, it will switch off and then on its bluetooth, and Btinput won't reconnect, even if I manually tap on the device in the Btinput list. If I use the Harmattan bluetooth wizard, I can pair the keyboard by typing on the keyboard a 4-digit number generated by the N9, so that both devices can automatically connect. However, still the same issue, in Btinput simply taping the keyboard after a slide-in/slide-out won't work. I have to put the keyboard in pair mode again and to start over. :/

What am I doing wrong?

Your not doing anything wrong mate

Its the current state of using a bluetooth keyboard with BTInput.

I am going to ask the developer of it for some help to modify BtInput to keep a connection active with a keyboard or possibly if we can just modify the bluetooth driver in our N9 with an open version that supports HID devices by default.

Otherwise I will be using an NFC sticker and some ProfileMatic custom commands to launch a script that MAY help solve our problem.

My main goal is to get the N9 fitted nicely onto the Nuu MiniKey, now I have designed the bracket, I will start solving the usability issue and will post a fix once I find one

I don't really understand what Btinput makes "easier" (as stated in the description) then. HID devices are not useable without it, so they can pair but cannot do anything else, is that it? If so I understand the role of Btinput, but yes, a better management of reconnection to paired devices is necessary. It takes too long putting the keyboard back in pair mode everytime we slide it in and out, restarting Btinput, and re-pairing the two devices.

Or if we could prevent the keyboard to switch off bluetooth when slid out, I guess it would do the job too. I think it has enough battery to last a whole day with bluetooth on. Then you just have to plug two USB cables when you charge the phone at night, not really a big deal (a least when you're home).

I look forward to seeing what you can do with the NFC sticker as well, it's promising although theoretical for the moment. And I look forward to reading your report on the housing you built.

By the way, the NUU Minikey clicks are really loud. I find them to be too loud actually, it would be impossible to use it during a conference or a meeting, it's too clicky (sounds like a mechanical blue cherry switch keyboard!). I think the keyboard of the N900 was just clicky enough, the sound was very well balanced. I'm still trying to figure out how to tell my N9 that the keyboard is an AZERTY. No success yet.