Bluetooth Keyboard

Ben Wong lists.openmoko.org at wongs.net
Tue Jul 2 23:34:24 CEST 2013


Update: Just tried this,

  export QWS_KEYBOARD=" neokbdhandler "

Yes, those are spaces on either side. And, yes, weirdly enough, it
*worked*. I have both bluetooth keyboard input and physical neo button
input. But, my control and caps lock keys still do nothing. (They used
to work when I used SHR, by the way.)


On Tue, Jul 2, 2013 at 2:21 PM, Ben Wong <lists.openmoko.org at wongs.net> wrote:
> Well, I tried some different QWS_KEYBOARD settings and the one that
> seemed to have the most hope of working was when I set it to the empty
> string:
>
>   export QWS_KEYBOARD=""
>
> That allowed me to type using the bluetooth keyboard just fine and
> dandy, BUT the power and aux buttons on the neo no longer work, so
> it's not a solution. (Especially since I seem to have to reboot the
> phone, not just restart QT Moko, in order to make qpe.env be reread.)
>
> Supposedly, one can have multiple keyboard drivers by separating them
> with spaces in the QWS_KEYBOARD variable, however, I have no idea how
> to specify both neokbdhandler and the empty string.
>
> Sidenote 1: weirdly, setting QWS_KEYBOARD to "" is different than
> having the variable unset. When not set, bluetooth did not work.
>
> Sidenote 2: for some reason my caps lock and control keys are not
> being recognized, but my alt/option key is.
>
> Sidenote 3: I was surprised to see that pairing worked from the QTMoko
> GUI. (I did have to restart QT Moko but it was happy after that.) I
> had expected to have to use the old Bluez3 'hidd --search'.
>
> --Ben
>
>
>
>
>
> On Fri, Jun 28, 2013 at 3:44 AM, Radek Polak <psonek2 at seznam.cz> wrote:
>> On Friday, June 28, 2013 11:23:53 AM Ben Wong wrote:
>>
>>
>>
>>> On Mon, Jun 24, 2013 at 10:29 PM, Radek Polak <psonek2 at seznam.cz> wrote:
>>
>>> > Well i have been playing with my bluetooth keyboard this weekend. I
>>> > could
>>
>>> > connect it with hidd --connect but unfortunately it does not generate
>>> > any
>>
>>> > input events (same on PC). So the HW might be broken.
>>
>>>
>>
>>> Could it be a passkey problem?
>>
>>
>>
>> I dont think so. Devices are connected and i have new input event in
>> /dev/input but there are no data when i press keys.
>>
>>
>>
>>> > I though it could be quite easy, because input handling is handled by Qt
>>
>>> > and should be quite well documented/tested. The trick should be to
>>
>>> > correctly set QWS_KEYBOARD environment variable.
>>
>>>
>>
>>> Where does one set that variable in QTMoko?
>>
>>
>>
>> /opt/qtmoko/qpe.env
>>
>>
>>
>> Regards
>>
>>
>>
>> Radek



More information about the community mailing list