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 .
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:
Code:
KL=$( getprop persist.keyboard_layout )
if [ ! -z "$KL" ]
then
# Restore the save keylout
setprop hw.keyboards.0.devname $KL
fi
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?
Like my work, use my roms daily? Consider donating for a beer/redbull -- Follow me on Twitter
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?
I'd use klingonian if that'll get me CM7 on my ChaCha ... (I hate Star Trek and anything related to it).
What works: bluetooth, wifi, touchscreen, 2g/3g, lights (although perhaps I need to tone it down a bit), rotation, proxymity, gps
What doesn't: camera, non-qwerty keyboard layouts
To switch the keyboard, you could try to use the kcm files from HTC's rom (attached to this post) using for example adb push:
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.
To switch the keyboard, you could try to use the kcm files from HTC's rom (attached to this post)
Thanks for sharing your build :D
I think they should use the one I have post (kl & kcm fixed), not the stock ones from HTC (which will break because of undefined keys like HTC_SHARE).
Does anyone in here wanna create a flasheable zip per kl/kcm pair and post it? (quite easy to do, just don't have the time right now). Could be a easy alternative also (easier than adb IMHO).
Like my work, use my roms daily? Consider donating for a beer/redbull -- Follow me on Twitter
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?
Like my work, use my roms daily? Consider donating for a beer/redbull -- Follow me on Twitter
If you have GPS issues and you happen to live in Europe, I recommend flashing radio 7.47.35.17
Hehe, this really made me laugh
As a side-note, the official radio for 1.52 is 7.51.35.19 on Europe. Is there any chance you can incorporate this radio into your build (in future releases, not now)?
I'm pretty sure Mikevhl uploaded all the radios for all the versions available in the dev section somewhere.
XDA Developer TV Producer Kevin wants to help make your … more
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?