Hi Markus, Thanks!
I have figured it out. Please see my video in youtube. The first android demo phone run android 0.9 SDK in China http://www.youtube.com/watch?v=B14hx_C3eEc On Thu, Sep 18, 2008 at 7:29 PM, Markus <[EMAIL PROTECTED]> wrote: > > Hi, > > my key configuration is finally working. The key configuration > requires a kernel, that provides ANDROID_POWER support. Then > everything works fine by changing system/usr/keylayout > > bye > Markus > > On 9 Sep., 02:45, "edwardlee lee" <[EMAIL PROTECTED]> wrote: >> Yes, I meet the same issue. I have get some useful message from androidezx >> that the menu code map in qwerty.kl is WAKE_DROPPED. But I map one >> keycode(229) to menu and still can't remove screen lock. >> >> On Mon, Sep 8, 2008 at 10:02 PM, Markus <[EMAIL PROTECTED]> wrote: >> >> > Hi, >> >> > has somebody already tried to change the key definitions for android >> > 0.9 and succeeded? I have ported it to the i.mx31, but I cannot remove >> > the screen lock after booting as the menu key is not set by default. I >> > changed both .kl files in /system/usr/keylayout and set the menu to >> > those buttons I found using 'getevent' (in emulator and on real >> > hardware, so that I changed the right value), but I did not have any >> > success in getting Android to react to my inputs. >> >> > So has the key input definition changed? Or is there a second way to >> > remove the screen lock? >> >> > bye >> > Markus > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-internals?hl=en -~----------~----~----~----~------~----~------~--~---
