Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-08-24 Thread Tim Abell 
for reference, attached is some output from hcidump  lsmod on my 
laptop, where I am able to connect and use the keyboard successfully.


Tim


laptop.tar.gz
Description: GNU Zip compressed data
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-08-24 Thread Dan Staley 
My bluetooth keyboard also works very well on my freerunner.
(I have an iGo Stowaway keyboardwhich i would highly recommend...its
very nice!)

-Dan Staley

On Mon, Aug 24, 2009 at 6:41 PM, Tim Abell t...@timwise.co.uk wrote:

 for reference, attached is some output from hcidump  lsmod on my laptop,
 where I am able to connect and use the keyboard successfully.

 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

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-07-03 Thread Paul Fertser 
Tim Abell t...@timwise.co.uk writes:
 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.

Have you tried using Xorg instead of old buggy and unsupported Xglamo? 

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

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

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-07-03 Thread Al Johnson 
On Friday 03 July 2009, Tim Abell wrote:
 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?

If input isn't getting to the console either then check whether the keyboard 
is actually appearing as an input device. You could check dmesg or logread, or 
try:
ls -l /dev/input/by-path/
hal-find-by-capability --capability input.keyboard


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

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-07-03 Thread Tim Abell 
On Fri, 3 Jul 2009 12:52:20 +0100
Al Johnson openm...@mazikeen.demon.co.uk wrote:

 On Friday 03 July 2009, Tim Abell wrote:
  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?
 
 If input isn't getting to the console either then check whether the
 keyboard is actually appearing as an input device. You could check
 dmesg or logread, or try:
   ls -l /dev/input/by-path/
   hal-find-by-capability --capability input.keyboard
 
 
 ___
 Openmoko community mailing list
 community@lists.openmoko.org
 http://lists.openmoko.org/mailman/listinfo/community

thanks all for your input . i'll be offline for a bit but will work
through all help as soon as i can .

msg sent with claws mail on shr unstable. woo !

Tim 

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

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-07-02 Thread Tim Abell 
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.origThu Jun 25 19:36:17 2009
 +++ XserverFri 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

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-07-01 Thread Laszlo KREKACS 
On Wed, Jul 1, 2009 at 1:18 AM, Tim Abellt...@timwise.co.uk 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.

In my opinion SHR is more focused on bleeding edge, and trying every new
in their distro, while om2009 (which is community based too in these days)
are focusing in the stable direction.
So I see om2009 as a stable version of SHR, with only the base necessary
apps.

I think shr and om2009 is not competing with each other, but focusing
on two different directions (stable vs. bleeding edge).

There is only a bit difference still. SHR is coming with their own set of
phone applications, while om2009 pushing paroli. But under the hood,
there is lot of similarity between shr and om2009.

I would like to see paroli properly packaged on shr, and an easy ability
to switch between shr phone suite, and paroli (from end-user point of view).

But trying out the newest glamo and such, shr is the best candidate.

Best regards,
 Laszlo

ps: I only wanted to say, that there are development in om2009 distro too;-D

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

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-06-30 Thread Tim Abell 

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.origThu Jun 25 19:36:17 2009
+++ XserverFri 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

#!/bin/sh
#

# note xinit needs full server path
if [ -f /usr/bin/Xfbdev ]; then
  XSERVER=/usr/bin/Xfbdev
fi
if [ -f /usr/bin/Xepson ]; then
  XSERVER=/usr/bin/Xepson
fi
if [ -f /usr/bin/Xorg ]; then
  XSERVER=/usr/bin/Xorg
fi

. /etc/profile

fallback_screen_arg() {
geom=`fbset | grep geometry`
w=`echo $geom | awk '{ print $2 }'`
h=`echo $geom | awk '{ print $3 }'`
b=`echo $geom | awk '{ print $6 }'`
echo -n ${w}x${h}x${b}
}

screen_width() {
geom=`fbset | grep geometry`
w=`echo $geom | awk '{ print $2 }'`
echo -n ${w}
}


module_id() {
## used to read from assets, but sometimes assets is corrupted
# grep Module ID /proc/hal/assets | sed s/.*://
## used to read from /proc/hal/model, but that is removed in 2.6
# echo ' iPAQ' `cat /proc/hal/model`
awk 'BEGIN { FS=:  } /Hardware/ { print $2 } ' /proc/cpuinfo
}

export USER=root

SCREEN_SIZE=`fallback_screen_arg`

ARGS= -br -pn

# use ucb 1x00 touchscreen if present
if [ -z $TSLIB_TSDEVICE ]  [ -e /dev/touchscreen/ucb1x00 ]; then
  ARGS=$ARGS -mouse /dev/touchscreen/ucb1x00
fi

# use usb mouse if present
# Xorg doesn't support -mouse option, and uses /dev/input/mice automatically
if [ -z $TSLIB_TSDEVICE ]  [ -e /dev/input/mice ]  [ $XSERVER != Xorg 
]; then
  ARGS=$ARGS -mouse /dev/input/mice
fi

# start off server in conventional location.
case `module_id` in
HP iPAQ H3100 | HP iPAQ H3800)
ARGS=$ARGS -dpi 100 -rgba vrgb -screen ${screen_si...@90 ;;
HP iPAQ H3600 | HP iPAQ H3700 | HP iPAQ H3900)
ARGS=$ARGS -dpi 100 -rgba vbgr -screen ${screen_si...@270 ;;
HP iPAQ H5400 | HP iPAQ H2200)
ARGS=$ARGS -dpi 100 -rgba rgb ;;
HP iPAQ HX4700)
ARGS=$ARGS -dpi 200
IMAGEON=w3220
;;
Ramses)
# What is this vt2 in aid of?
ARGS=$ARGS -dpi 100 -rgba vrgb -screen ${screen_si...@90 vt2 
;;
# both 'Sharp-Collie' and just 'Collie' have been reported
*Poodle)
ARGS=$ARGS -dpi 100 -rgba vrgb -screen ${screen_si...@270 ;;
*Collie)
ARGS=$ARGS -dpi 100 -rgba vrgb -screen ${screen_si...@270 ;;
SHARP Shepherd | SHARP Husky | SHARP Corgi)
if [ `screen_width` -gt 330 ] ; then
 DPI=200
else
 DPI=100
fi 
ARGS=$ARGS -dpi ${DPI} -rgba rgb
IMAGEON=w100
;;
SHARP Spitz | SHARP Akita | SHARP Borzoi)
ARGS=$ARGS -dpi 200 -rgba rgb -screen ${screen_si...@270 ;;
Simpad)
ARGS=$ARGS -dpi 100 -rgba rgb ;;
Generic OMAP1510/1610/1710)
ARGS=$ARGS -dpi 220 -mouse /dev/input/event0 ;;
Cellon C8000 Board)
ARGS=$ARGS -dpi 100 -screen ${SCREEN_SIZE},10,1 ;;
HTC Magician)

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-06-30 Thread Tim Abell 
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.origThu Jun 25 19:36:17 2009
+++ XserverFri 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

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-06-29 Thread Timo Juhani Lindfors 
Tim Abell t...@timwise.co.uk writes:
 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.

1) Are you running hal?
2) Does lshal list the device?
3) Are you using Xorg?
4) can evtest from some /dev/input/event* see the key presses? (dmesg to see 
which one)

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

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-06-25 Thread Al Johnson 
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


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

[Om2009] bluetooth keyboard - key presses not making it to X

2009-06-24 Thread Tim Abell 

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?

refs:
my hcidump: http://pastebin.ca/1473582 (attached)
my notes so far: http://wiki.openmoko.org/wiki/Freedom_Slim_Keyboard#Om2009
vaguely related bug: https://docs.openmoko.org/trac/ticket/1796
older attempts: http://timwise.wikispaces.com/freedom+universal+keyboard

Thanks

Tim Abell
HCI sniffer - Bluetooth packet analyzer ver 1.42
device: hci0 snap_len: 1028 filter: 0x
 HCI Event: Connect Request (0x04) plen 10
bdaddr 00:0B:0D:8A:35:62 class 0x002540 type ACL
 HCI Command: Accept Connection Request (0x01|0x0009) plen 7
bdaddr 00:0B:0D:8A:35:62 role 0x01
Role: Slave
 HCI Event: Command Status (0x0f) plen 4
Accept Connection Request (0x01|0x0009) status 0x00 ncmd 1
 HCI Event: Connect Complete (0x03) plen 11
status 0x00 handle 42 bdaddr 00:0B:0D:8A:35:62 type ACL encrypt 0x00
 HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
handle 42
 HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
bdaddr 00:0B:0D:8A:35:62 mode 1
 HCI Event: Max Slots Change (0x1b) plen 3
handle 42 slots 5
 HCI Event: Command Status (0x0f) plen 4
Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 0
 ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 17 scid 0x0040
 ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 1 status 0
  Connection pending - No futher information available
 ACL data: handle 42 flags 0x02 dlen 10
L2CAP(s): Info req: type 2
 HCI Event: Command Status (0x0f) plen 4
Unknown (0x00|0x) status 0x00 ncmd 1
 HCI Event: Number of Completed Packets (0x13) plen 5
handle 42 packets 1
 ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Info rsp: type 2 result 1
  Not supported
 HCI Event: Number of Completed Packets (0x13) plen 5
handle 42 packets 1
 ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
  Connection successful
 HCI Event: Read Remote Supported Features (0x0b) plen 11
status 0x00 handle 42
Features: 0xff 0xff 0x05 0x38 0x18 0x18 0x00 0x00
 HCI Event: Number of Completed Packets (0x13) plen 5
handle 42 packets 1
 ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4
  MTU 48 
 ACL data: handle 42 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4
  MTU 48 
 ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0
 HCI Event: Number of Completed Packets (0x13) plen 5
handle 42 packets 1
 ACL data: handle 42 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 0
  Success
 HCI Event: Number of Completed Packets (0x13) plen 5
handle 42 packets 1
 ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 19 scid 0x0041
 ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0
  Connection successful
 HCI Event: Number of Completed Packets (0x13) plen 5
handle 42 packets 1
 ACL data: handle 42 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4
  MTU 48 
 ACL data: handle 42 flags 0x02 dlen 18
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4
  MTU 48 
 ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 0
 HCI Event: Number of Completed Packets (0x13) plen 5
handle 42 packets 1
 ACL data: handle 42 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 0
  Success
 HCI Event: Number of Completed Packets (0x13) plen 5
handle 42 packets 1
 ACL data: handle 42 flags 0x02 dlen 14
L2CAP(d): cid 0x0041 len 10 [psm 19]
  HIDP: Data: Input report
 ACL data: handle 42 flags 0x02 dlen 14
L2CAP(d): cid 0x0041 len 10 [psm 19]
  	
 HCI Command: Remote Name Request (0x01|0x0019) plen 10
bdaddr 00:0B:0D:8A:35:62 mode 2 clkoffset 0x
 HCI Event: Command Status (0x0f) plen 4
Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
 ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
 ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0041 scid 0x0041
 HCI Event: Number of Completed Packets (0x13) plen 5
handle 42 packets 1
 ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
 HCI Event: Number of Completed Packets (0x13) plen 5
handle 42 packets 1
 ACL data: handle 42 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0041
 HCI Event: Remote Name Req Complete (0x07) plen 255
status 0x00 bdaddr 00:0B:0D:8A:35:62 name 'FREEDOM KEYBOARD'
 HCI Command:

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-06-24 Thread Lon Lentz 
  Is the keyboard using encryption?

On Wed, Jun 24, 2009 at 10:57 PM, Tim Abellt...@timwise.co.uk 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?

 refs:
 my hcidump: http://pastebin.ca/1473582 (attached)
 my notes so far: http://wiki.openmoko.org/wiki/Freedom_Slim_Keyboard#Om2009
 vaguely related bug: https://docs.openmoko.org/trac/ticket/1796
 older attempts: http://timwise.wikispaces.com/freedom+universal+keyboard

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

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-06-24 Thread Tim Abell 
How do I tell?

It all worked fine on my ubuntu box last time I tried.

Tim Abell

Lon Lentz wrote:
   Is the keyboard using encryption?

 On Wed, Jun 24, 2009 at 10:57 PM, Tim Abellt...@timwise.co.uk 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?

 refs:
 my hcidump: http://pastebin.ca/1473582 (attached)
 my notes so far: http://wiki.openmoko.org/wiki/Freedom_Slim_Keyboard#Om2009
 vaguely related bug: https://docs.openmoko.org/trac/ticket/1796
 older attempts: http://timwise.wikispaces.com/freedom+universal+keyboard
 

 ___
 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

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-06-24 Thread Lon Lentz 
  With Apple's keyboards, you have to add 'auth enable; encrypt
enable;' to device {} in hcid.conf. Thought maybe you could be having
the same problem.


On Wed, Jun 24, 2009 at 11:07 PM, Tim Abellt...@timwise.co.uk wrote:
 How do I tell?

 It all worked fine on my ubuntu box last time I tried.

 Tim Abell

 Lon Lentz wrote:
   Is the keyboard using encryption?

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

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-06-24 Thread Tim Abell 

Oh, ok.

I can't find the file you mention.

r...@om-gta02:/etc/bluetooth# ls
audio.confinput.confmain.conf network.conf  rfcomm.conf

Ta.

Tim Abell


Lon Lentz wrote:

  With Apple's keyboards, you have to add 'auth enable; encrypt
enable;' to device {} in hcid.conf. Thought maybe you could be having
the same problem.


On Wed, Jun 24, 2009 at 11:07 PM, Tim Abellt...@timwise.co.uk wrote:
  

How do I tell?

It all worked fine on my ubuntu box last time I tried.

Tim Abell

Lon Lentz wrote:


  Is the keyboard using encryption?
  


___
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

Re: [Om2009] bluetooth keyboard - key presses not making it to X

2009-06-24 Thread Paul Fertser 
Lon Lentz lon.le...@gmail.com writes:
   With Apple's keyboards, you have to add 'auth enable; encrypt
 enable;' to device {} in hcid.conf. Thought maybe you could be having
 the same problem.

Both SHR and OM2009 are using bluez4, so no hcid.conf there.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com

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