Originally Posted by xdbg
Ok, but I'd like to find a proper way to load the correct kcm file before releasing a new CM7 build. Also I'd like to get the camera fixed.
IMHO the only proper way is using an app/activity that shows a list of available layout and the user choose the one that fits his phone.
The app could then save the selected value (chacha-keypad-xxx) in a persistent property, like "persist.keyboard_layout" (calling setprop) as well as set the hw.keyboards.0.devname to chacha-keypad-xxx .
setprop persist.keyboard_layout chacha-keypad-xxx
setprop hw.keyboards.0.devname chacha-keypad-xxx
To make it persist across reboot, just read the persist.keyboard_layout value upon boot (in a script called from init.chacha.rc for example), and set again ro.keyboard.0.devname to that value:
KL=$( getprop persist.keyboard_layout )
if [ ! -z "$KL" ]
# Restore the save keylout
setprop hw.keyboards.0.devname $KL
Should be all good
Where to fit that app? I guess for now we could do a small app to propose the list. Then we could integrate the activity into CMParts or Settings...
What do you think?