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 .

Come to think about it, I think I saw CM on English QWERTY only on any device as official support. I don't remember if there is any CM7 build with other language support, but I may be wrong (probably).

Honestly I don't think that the keyboard is the main problem right now, as all users would really like to see some CM7 support (unofficial/official) and I do hope that they could sacrifice their specific keyboard layout for a CM. Is not that much of a price to pay, is it?

Guys, sorry for interrupt your discussion about keyboards...
But why not to use 3rd party apps for it? Like ruKeyboard or AnySoftKeyboard?
I use the 1st one for cyrillic input and it works fine with official chacha FW.

Guys, sorry for interrupt your discussion about keyboards...
But why not to use 3rd party apps for it? Like ruKeyboard or AnySoftKeyboard?
I use the 1st one for cyrillic input and it works fine with official chacha FW.

There are virtual keyboards right? Sure, it's an alternative, yet quite a pity in the case of the Chacha, as the physical kbd is the attractive of that device, isn't it?

XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality.Are you a developer?