Hello, Xin Do you fix this issue, now I encounter the same with you, my board is SAM9261EK, also the logs is the same.
Thanks, Harry On 3月20日, 下午5时03分, Justin <[email protected]> wrote: > Hi all, > > Joyfully I got the android ported few days ago. > But I'm having problem with touch pad. With Android emulator there is > couple of major buttons: > > Receive call, Menu, Reject call, > Up, Down, Left, Right, Enter > > On my IMX31-3stack board SDK there is 9 buttons (excluding the power > button) set up as: > > /arch/arm/mach-mx3/mx3_3stack.c: > static u16 keymapping[12] = { > KEY_UP, KEY_DOWN, 0, 0, > KEY_RIGHT, KEY_LEFT, KEY_ENTER, 0, > KEY_F6, KEY_F8, KEY_F9, KEY_F10, > > }; > > Strangely only KEY_ENTER respond Correctly, ignoring the function > keys. Direction buttons doesn't do what it suppose to do on emulator, > plus screen blink on button press (not with KEY_ENTER) or return with > error box: > > "Activity Home (inprocess android.process.acore) is not responding" > > On logcat: > > W/KeyCharacterMap( 2024): No keyboard for id 0 > W/KeyCharacterMap( 2024): Can't open keycharmap file > E/KeyCharacterMap( 2024): Can't find any keycharmaps (also tried / > system/usr/key > chars/qwerty.kcm.bin) > I/DEBUG ( 2016): *** *** *** *** *** *** *** *** *** *** *** *** *** > *** *** * > ** > I/DEBUG ( 2016): Build fingerprint: 'generic/generic/generic/:1.5/ > MAIN/eng.xin > .20090316.085412:eng/test-keys' > I/DEBUG ( 2016): pid: 2024, tid: 2024 >>> android.process.acore <<< > I/DEBUG ( 2016): signal 11 (SIGSEGV), fault addr 00000000 > I/DEBUG ( 2016): r0 0000a980 r1 4001b030 r2 00000000 r3 41049c58 > I/DEBUG ( 2016): r4 bedce5c8 r5 00000004 r6 ad32ec51 r7 41049c34 > I/DEBUG ( 2016): r8 bedce5a8 r9 41049c2c 10 41049c1c fp 00000000 > I/DEBUG ( 2016): ip ad32ec51 sp bedce5a8 lr ad00e2f8 pc > ad32ec50 cpsr a00 > 00030 > I/DEBUG ( 2016): #00 pc 0002ec50 /system/lib/ > libandroid_runtime.so > I/DEBUG ( 2016): #01 lr ad00e2f8 /system/lib/libdvm.so > I/DEBUG ( 2016): stack: > I/DEBUG ( 2016): bedce568 00000001 > I/DEBUG ( 2016): bedce56c 41f19e44 > I/DEBUG ( 2016): bedce570 00000001 > I/DEBUG ( 2016): bedce574 ad04887f /system/lib/libdvm.so > I/DEBUG ( 2016): bedce578 00000320 > I/DEBUG ( 2016): bedce57c 41084a00 > I/DEBUG ( 2016): bedce580 bedce5d8 [stack] > I/DEBUG ( 2016): bedce584 00000008 > I/DEBUG ( 2016): bedce588 0000000d > I/DEBUG ( 2016): bedce58c ad063dc7 /system/lib/libdvm.so > I/DEBUG ( 2016): bedce590 00000004 > I/DEBUG ( 2016): bedce594 ad05aa49 /system/lib/libdvm.so > I/DEBUG ( 2016): bedce598 00000018 > I/DEBUG ( 2016): bedce59c 41084a00 > I/DEBUG ( 2016): bedce5a0 df002777 > I/DEBUG ( 2016): bedce5a4 > e3a070ad > I/DEBUG ( 2016): > #00 bedce5a8 41084a00 > I/DEBUG ( 2016): bedce5ac 0000bc38 [heap] > I/DEBUG ( 2016): bedce5b0 ad32ec51 /system/lib/ > libandroid_runtime.so > I/DEBUG ( 2016): bedce5b4 4001b030 > I/DEBUG ( 2016): bedce5b8 00001071 > I/DEBUG ( 2016): bedce5bc 0000bc38 [heap] > I/DEBUG ( 2016): bedce5c0 bedce5c8 [stack] > I/DEBUG ( 2016): bedce5c4 ad0409cd /system/lib/libdvm.so > I/DEBUG ( 2016): bedce5c8 41049c2c > I/DEBUG ( 2016): bedce5cc 41f46225 > I/DEBUG ( 2016): bedce5d0 ad32ec51 /system/lib/ > libandroid_runtime.so > I/DEBUG ( 2016): bedce5d4 bedce640 [stack] > I/DEBUG ( 2016): bedce5d8 bedce640 [stack] > I/DEBUG ( 2016): bedce5dc 00000001 > I/DEBUG ( 2016): bedce5e0 ad00e480 /system/lib/libdvm.so > I/DEBUG ( 2016): bedce5e4 41e47a68 > I/DEBUG ( 2016): bedce5e8 41049c40 > I/DEBUG ( 2016): bedce5ec bedce638 [stack] > I/ActivityManager( 1662): Process android.process.acore (pid 2024) has > died. > I/WindowManager( 1662): WIN DEATH: Window{437d5ab8 > com.android.launcher/com.andr > oid.launcher.Launcher} > > Can anyone give me an idea? > > Thank you, > > Best Regards, > Xin --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
