Hiya,

Thanks for the suggestion. I had seen that bug but hadn't known what to try.

I've now updated to shr-unstable, and have exactly the same symptoms as 
before, with  events showing in hcidump but not in xev. I've tried 
changing the startup parameters of Xglamo as suggested, I tried removing 
vt1, I tried replacing it with vt0 (x won't start like that), and vt2. 
None of these fixed the problem.

It may be worth noting that if I stop X, then I don't get any output 
from the bluetooth keyboard appearing on the console on the phone unlike 
in the bug report you mention.

Any other ideas?

Tim

If I stop

Tim Abell wrote:
> I hadn't realised till now that SHR is the main focus of development, 
> so I have just reflashed with that and will try again.
>
> Thanks
>
> Tim Abell
>
> Tim Abell wrote:
>> Al Johnson wrote:
>>> On Thursday 25 June 2009, Tim Abell wrote:
>>>   
>>>> Hi all,
>>>>
>>>> I've got my bt keyboard connected, and according to hcidump I think the
>>>> keypress events are getting to bluez, however they aren't getting to any
>>>> applications, including xev.
>>>>
>>>> Does anyone know what I need to do to troubleshoot this?
>>>>     
>>>
>>> Sounds like bug #1796 [1]. It's the parameters passed when starting X that 
>>> are 
>>> the problem, and affects USB keyboards too. Look in /etc/X11/Xserver and 
>>> compare with the diff below - beware line wrap. If this is the problem then 
>>> please file a bug report.
>>>
>>> --- a/packages/xserver-kdrive-common/xserver-kdrive-common/openmoko/Xserver
>>> +++ b/packages/xserver-kdrive-common/xserver-kdrive-common/openmoko/Xserver
>>> @@ -93,7 +93,7 @@ case `module_id` in
>>>                  modprobe mbxfb
>>>                  ARGS="$ARGS -br -fb /dev/fb1" ;;
>>>          "GTA01" | "GTA02")
>>> -                ARGS="$ARGS -dpi 285 -screen 480x640 -hide-cursor -root-
>>> ppm/usr/share/pixmaps/xsplash-vga.ppm vt1" ;;
>>> +                ARGS="$ARGS -dpi 285 -screen 480x640 -hide-cursor -br" ;;
>>>          "Motorola Ezx Platform")
>>>                  ARGS="$ARGS -dpi 170 -screen 240x320 -hide-cursor 
>>> -root-ppm 
>>> /usr/share/pixmaps/xsplash-qvga.ppm vt1" ;;
>>>          "Nokia N800")
>>>
>>>
>>> [1] http://docs.openmoko.org/trac/ticket/1796
>>>
>>>   
>> Thanks Al,
>>
>> My Xserver file isn't exactly the same, but I tried to make matching 
>> changes:
>>
>> r...@om-gta02:/etc/X11# diff Xserver.orig Xserver
>> --- Xserver.orig    Thu Jun 25 19:36:17 2009
>> +++ Xserver    Fri Jun 26 23:30:27 2009
>> @@ -113,7 +113,7 @@
>>                  else
>>                       DPI=140
>>                  fi
>> -                ARGS="$ARGS -dpi ${DPI} -screen ${SCREEN_SIZE} 
>> -mouse tslib -hide-cursor -root-ppm 
>> /usr/share/pixmaps/xsplash-vga.ppm vt1"
>> +                ARGS="$ARGS -dpi ${DPI} -screen ${SCREEN_SIZE} 
>> -hide-cursor -br"
>>          XSERVER=/usr/bin/Xglamo
>>          ;;
>>      "Nokia N770")
>>
>>
>> I've attached the two versions, the original from my phone (.orig) 
>> and my attempt at modifying it (.bluetooth)
>>
>> The changes don't appear to have helped.
>>
>> Tim
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Openmoko community mailing list
>> community@lists.openmoko.org
>> http://lists.openmoko.org/mailman/listinfo/community
> ------------------------------------------------------------------------
>
> _______________________________________________
> Openmoko community mailing list
> community@lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>   

_______________________________________________
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Reply via email to