Hi Dianne, Thanks for your responses. I saw you on Google I/O livestream at Irvine of the Android fireside chat. I recognized the name from the previous posts i've read of yours before!
We are trying to modify the behavior of the hard keys depending on what "system mode" we are in. We are extending the Android Framework to enable some different behaviors such as different splash startup screen, hard key mapping changes, blocking the hardkeys for all applications, blocking activity launching, changing dimming and backlight behavior for all applications. Recently, we have decided that it might be easier to upgrade from Android 2.1 (api level 7) which we are using now to the newer versions like 2.2 and 2.3 if we were able to accomplish more of these behavior changes in a level above the android os code. but it looks like some of the things like these hard key press changes have to be done at the framework level by extending and modifying the Android source code which is where we were previously doing them. Thanks, --Edmund On Fri, May 13, 2011 at 1:49 PM, Dianne Hackborn <[email protected]>wrote: > Also I'd like to understand why you would have significant changes here. > There are only two hard keys that are handled at this level -- home and end > call. > > > On Fri, May 13, 2011 at 8:48 PM, Dianne Hackborn <[email protected]>wrote: > >> You can't do this in third party apps. The hard keys are handled by the >> system in PhoneWindowManager. >> >> >> On Thu, May 12, 2011 at 4:33 PM, Edmund <[email protected]> wrote: >> >>> Hi, >>> >>> I was wondering if there was a way to enable/disable long-press >>> features for the android hard key buttons. Also, what is the best >>> approach to trap hard key inputs across all the applications running >>> in our system. And also how to remap their meanings. >>> >>> Can this be done at an APK level above the Android OS framework, or >>> does this have to be done by extending IWindowManager like we are >>> already currently doing. We are trying to do more things at a higher >>> level (above extending/modifying android source code) so we can move >>> up from Android 2.1 to 2.2 and 2.3 quicker/easier. >>> >>> Thanks, >>> --Edmund Chang >>> [email protected] >>> >>> -- >>> unsubscribe: [email protected] >>> website: http://groups.google.com/group/android-porting >>> >> >> >> >> -- >> 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, and so won't reply to such e-mails. All such >> questions should be posted on public forums, where I and others can see and >> answer them. >> >> > > > -- > 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, and so won't reply to such e-mails. 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
