View Single Post
  #2063 (permalink)  
Old 03-24-2011, 01:26 PM
[ACL]'s Avatar
[ACL]
VIP Member
Offline
Location: NY
 
Join Date: Feb 2010
Posts: 1,534
Reputation: 6350
[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community[ACL] is a trusted member of the community
Mentioned: 2 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - 03-11: FRX05 on NAND (data working again!)

Quote:
Originally Posted by natemcnutty View Post
When XDAndroid decided to change the button mappings, I looked into a program for Android that would let us re-assign the keys, and I wasn't able to find anything useful.

Also, if we made the button mapping commits, then we have to add the navi_pad keylayout copy to the install script for the rhod400/500.
So these button changes on xdandroid require a recompile ? Thing is there is two ways to change this right. One, we fool the kernel like we do now, or just tell android to deal with it like it should. I rather do it android wise and if that doesn't work, then we can just revert?

im ok either way.. yall can decide.
__________________
Reply With Quote