Hi   guys

I'm using a track ball and in drver ,  when press send a key event ,
when move send REL_X and REL_Y event.

I can get event using event test code.

But when in andriod the press key event works fine, and if I move the
trackball  the andriod UI will crash can restart.  log as below:

W/KeyCharacterMap(  692): No keyboard for id 0
W/KeyCharacterMap(  692): Can't open keycharmap file
E/KeyCharacterMap(  692): Can't find any keycharmaps (also tried /
system/usr/keychars/qwerty.kcm.bin)
I/DEBUG   (  633): *** *** *** *** *** *** *** *** *** *** *** *** ***
*** *** ***
I/DEBUG   (  633): Build fingerprint: 'generic/generic/generic/:1.0/
TC3/eng.zqy.20081216.183450:eng/test-keys'
I/DEBUG   (  633): pid: 692, tid: 692  >>> android.process.acore <<<
I/DEBUG   (  633): signal 11 (SIGSEGV), fault addr 00000000
I/DEBUG   (  633):  r0 0000a878  r1 4001c450  r2 00000000  r3 4104ac14
I/DEBUG   (  633):  r4 be99d628  r5 00000004  r6 ad32c555  r7 4104abf0
I/DEBUG   (  633):  r8 be99d608  r9 4104abe8  10 4104abd8  fp 00000000
I/DEBUG   (  633):  ip ad32c555  sp be99d608  lr ad00d9f8  pc
ad32c554  cpsr a0000030
I/DEBUG   (  633):          #00  pc ad32c554  /system/lib/
libandroid_runtime.so
I/DEBUG   (  633):          #01  lr ad00d9f8  /system/lib/libdvm.so
I/DEBUG   (  633): stack:
I/DEBUG   (  633):     be99d5c8  00000001
I/DEBUG   (  633):     be99d5cc  434bdea0
I/DEBUG   (  633):     be99d5d0  00000018
I/DEBUG   (  633):     be99d5d4  ad048e9f  /system/lib/libdvm.so
I/DEBUG   (  633):     be99d5d8  00000320
I/DEBUG   (  633):     be99d5dc  400092c0
I/DEBUG   (  633):     be99d5e0  434bdea0
I/DEBUG   (  633):     be99d5e4  41083a70
I/DEBUG   (  633):     be99d5e8  be99d638  [stack]
I/DEBUG   (  633):     be99d5ec  00000008
I/DEBUG   (  633):     be99d5f0  0000000d
I/DEBUG   (  633):     be99d5f4  ad057899  /system/lib/libdvm.so
I/DEBUG   (  633):     be99d5f8  00000018
I/DEBUG   (  633):     be99d5fc  41083a70
I/DEBUG   (  633):     be99d600  df002777
I/DEBUG   (  633):     be99d604  e3a070ad
I/DEBUG   (  633): #00 be99d608  41083a70
I/DEBUG   (  633):     be99d60c  0000bb00  [heap]
I/DEBUG   (  633):     be99d610  ad32c555  /system/lib/
libandroid_runtime.so
I/DEBUG   (  633):     be99d614  4001c450
I/DEBUG   (  633):     be99d618  00001071
I/DEBUG   (  633):     be99d61c  0000bb00  [heap]
I/DEBUG   (  633):     be99d620  be99d628  [stack]
I/DEBUG   (  633):     be99d624  ad041241  /system/lib/libdvm.so
I/DEBUG   (  633):     be99d628  4104abe8
I/DEBUG   (  633):     be99d62c  41fb5c63
I/DEBUG   (  633):     be99d630  ad32c555  /system/lib/
libandroid_runtime.so
I/DEBUG   (  633):     be99d634  be99d6a0  [stack]
I/DEBUG   (  633):     be99d638  be99d6a0  [stack]
I/DEBUG   (  633):     be99d63c  00000001
I/DEBUG   (  633):     be99d640  ad00db80  /system/lib/libdvm.so
I/DEBUG   (  633):     be99d644  41e5f158
I/DEBUG   (  633):     be99d648  4104abfc
I/DEBUG   (  633):     be99d64c  be99d698  [stack]







On 12月4日, 下午6时49分, Rupesh Gujare <[email protected]> wrote:
> Hi,
>
>    Mouse is identified as a trackball. It doesn't show pointer but you
> can navigate using it.
>
> Regards,
>
> --
> Rupesh Gujare
>
> http://embinux.com
>
>
>
> Maxime Petazzoni wrote:
>
> > On Dec 3, 9:50 am, "Dianne Hackborn" <[email protected]> wrote:
>
> >> On Wed, Dec 3, 2008 at 9:20 AM, Maxime Petazzoni 
> >> <[email protected]
>
> >>> wrote:
> >>> Just out of curiosity, how do you get a pointer?
>
> >> We don't currently support a mouse pointer.
>
> > I know. I was just wondering how Shivdas made any use of a USB mouse
> > in this situation :)
>
> >> --
> >> Dianne Hackborn
> >> Android framework engineer
> >> [email protected]
>
> >> Note: please don't send private questions to me, as I don't have time to
> >> provide private support.  All such questions should be posted on public
> >> forums, where I and others can see and answer them.- 隐藏被引用文字 -
>
> - 显示引用的文字 -
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to