[ROM] SuperOSR and CyanogenMod7 on HTC ChaCha.

Alex C. · Oct 20, 2011

adlx.xda said:
I've been looking into it yesterday... On my Chacha, the 0 key is also the Symbol key. It's keycode 183 iirc (or something like 18x, but not 11). I couldn't find this keycode in the kcm (maybe it was too late lol). So we'll need to find a trick...

Is there any chance you could set up a repository/github where we could put files and get the rom so that we could also try different stuff?

Have you tried using the stock .kcm files and .kl files? (currently at work and kinda busy)

qbert456 · Oct 20, 2011

Other than checking this thread every chance I get and sending encouraging thoughts I can't help I'm afraid - keep up the good work tho chaps.

Sent from my HTC ChaCha A810e using Tapatalk

adlx.xda · Oct 20, 2011

Alex C. said:
Is there any chance you could set up a repository/github where we could put files and get the rom so that we could also try different stuff?

Have you tried using the stock .kcm files and .kl files? (currently at work and kinda busy)

I'll set that up tonight (like in +11 hours from now), and post the info here.

regarding the kcm/kl, what do you mean by stock? AOSP? or stock chacha-keypad kcm/kl files? (I've been working off the chacha-keypad files). Any way, there is more keys defined in the Chacha physical keyboard, like the Sym/0 key, which isn't defined in the CM framework (as far as I've seen).

Also, in my case, after getting the keyboard to "start working", I have a lot of other keys that are not working (not only the 0, like the T, V,..). I don't remember the list right now, but there where several columns (which btw do not relate with the "columns" defined in the kl file).

I tested the GPS using GPS Status & GPS Test and it seemed to be working fine. I couldn't get a sat fix because I was indoor, but it was showing 1 or 2 sats.

Also the 3-axis orientation sensors, as it was correctly showing in GPS Status.

Also the light sensor was showing data in the device file :-D

astro11 · Oct 20, 2011

qbert456 said:
Other than checking this thread every chance I get and sending encouraging thoughts I can't help I'm afraid - keep up the good work tho chaps.

I feel the same way, that's why I started going on other ChaCha/Status forums to tell people adlx and the folks are here, in xda, porting cyanogenmod and doing a lot of good for the community... I'll just try to bring more people here to thank who deserves.

And of course, keep up the good work guys!

carstenheuer · Oct 20, 2011

stay tuned guys ... your makes a great job!!!

Alex C. · Oct 20, 2011

adlx.xda said:
I'll set that up tonight (like in +11 hours from now), and post the info here.

regarding the kcm/kl, what do you mean by stock? AOSP? or stock chacha-keypad kcm/kl files? (I've been working off the chacha-keypad files). Any way, there is more keys defined in the Chacha physical keyboard, like the Sym/0 key, which isn't defined in the CM framework (as far as I've seen).

Also, in my case, after getting the keyboard to "start working", I have a lot of other keys that are not working (not only the 0, like the T, V,..). I don't remember the list right now, but there where several columns (which btw do not relate with the "columns" defined in the kl file).

I tested the GPS using GPS Status & GPS Test and it seemed to be working fine. I couldn't get a sat fix because I was indoor, but it was showing 1 or 2 sats.

Also the 3-axis orientation sensors, as it was correctly showing in GPS Status.

Also the light sensor was showing data in the device file :-D

Awesome job man!

Yeah replacing the keyboard files themselves with the ones from a stock rom on a device. (2.3.5 preferably). Cannot test it until I get home tonight unfortunately and give out some feedback.

xd.bx · Oct 20, 2011

I'm close to giving up on the Bluetooth side. I think some magic is missing in the kernel but I can't seem to figure out what.

adlx.xda: you must tweak an Android.mk somewhere to add something like CHACHA_KEYPAD and tweak the .h so the FUNC_1 and QUECHAR keys are understood by the ui. This by itself is not sufficient, I may need to tweak the kcm as well.

---------- Post added at 06:49 PM ---------- Previous post was at 06:38 PM ----------

adlx.xda said:
I tested the GPS using GPS Status & GPS Test and it seemed to be working fine. I couldn't get a sat fix because I was indoor, but it was showing 1 or 2 sats.

Quick question: what are your BOARD_VENDOR_QCOM_AMSS_VERSION and your BOARD_VENDOR_QCOM_GPS_LOC_API_AMSS_VERSION ?

adlx.xda · Oct 20, 2011

xdbg said:
I'm close to giving up on the Bluetooth side. I think some magic is missing in the kernel but I can't seem to figure out what.

adlx.xda: you must tweak an Android.mk somewhere to add something like CHACHA_KEYPAD and tweak the .h so the FUNC_1 and QUECHAR keys are understood by the ui. This by itself is not sufficient, I may need to tweak the kcm as well.

---------- Post added at 06:49 PM ---------- Previous post was at 06:38 PM ----------

Quick question: what are your BOARD_VENDOR_QCOM_AMSS_VERSION and your BOARD_VENDOR_QCOM_GPS_LOC_API_AMSS_VERSION ?

I had used the same VISION_KEYPAD already defined, just added that to frameworks/base:

Code:

From fb7326a1ec2db3be7e25ea3dece6ddf1d2999bd7 Mon Sep 17 00:00:00 2001
From: Alexandre Dumont
Date: Thu, 20 Oct 2011 00:37:48 +0200
Subject: [PATCH 2/2] Declare chacha as VISION_KEYPAD

Change-Id: I35be42d63b74ddcf9ca44144fc63f42d0f7e9c40
---
 libs/ui/Android.mk |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/libs/ui/Android.mk b/libs/ui/Android.mk
index ad00b12..184ee3d 100644
--- a/libs/ui/Android.mk
+++ b/libs/ui/Android.mk
@@ -40,6 +40,8 @@ endif

 ifeq ($(TARGET_BOOTLOADER_BOARD_NAME),latte)
        LOCAL_CFLAGS += -DLATTE_KEYPAD
+else ifeq ($(TARGET_BOOTLOADER_BOARD_NAME),chacha)
+       LOCAL_CFLAGS += -DVISION_KEYPAD
 else ifeq ($(TARGET_BOOTLOADER_BOARD_NAME),vision)
        LOCAL_CFLAGS += -DVISION_KEYPAD
 else ifeq ($(TARGET_BOOTLOADER_BOARD_NAME),speedy)
--
1.7.4.1

That way the kbd is working, like yours I guess

. no 0(SYM) nor ? (QUECHAR). I'm gonna look into the stock Chacha KeyEvent.java & the kcm file, hope I can understand & see what is wrong here.

I use no BOARD_VENDOR_QCOM_AMSS_VERSION nor BOARD_VENDOR_QCOM_GPS_LOC_API_AMSS_VERSION. (edited, I was wrong the first time).

Tested GPS and got a fix :-D, see screenshot.

Btw, Orientation is working now too (flipping portrait/landscape)

carstenheuer · Oct 21, 2011

PayPal donation for adlx.xda

---------- Post added at 11:42 AM ---------- Previous post was at 11:38 AM ----------

I'm so hot for CM7

xd.bx · Oct 21, 2011

adlx.xda said:
Btw, Orientation is working now too (flipping portrait/landscape)

Awesome work! Did you use the libsensors from Liberty? It's not working for me atm :/

xd.bx · Oct 21, 2011

I have a hint on making the camera work: seems the camera supports continuous AF. I think tweaking QualcommCameraHardware.cpp a little bit might do the trick. Also the CameraParameters API seems involved.

xd.bx · Oct 21, 2011

So gps seems to be working but I can't get more than two satellites (I get more than 5 on the crespo). Wierd, maybe it has something to do with the loc_api version?

adlx.xda · Oct 21, 2011

xdbg said:
Awesome work! Did you use the libsensors from Liberty? It's not working for me atm :/

I'm using the stock sensors.chacha.so. Hit me up on gtalk whenever you have a question :-D. Should be faster than the thread.

adlx.xda · Oct 21, 2011

xdbg said:
So gps seems to be working but I can't get more than two satellites (I get more than 5 on the crespo). Wierd, maybe it has something to do with the loc_api version?

I got 5 satelites fixed yesterday (see http://attachments.xda-developers.com/attachment.php?attachmentid=755984&d=1319150355).

I'm not using BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE nor BOARD_VENDOR_QCOM_GPS_LOC_API_AMSS_VERSION (sorry I made a mistake in the previous post when u asked).

xd.bx · Oct 22, 2011

adlx.xda said:
I'm using the stock sensors.chacha.so. Hit me up on gtalk whenever you have a question :-D. Should be faster than the thread.

Thanks adlx.xda. For the record, I got the AKM sensor working with a small modification of the Liberty libsensors: in nusensors.h, change /dev/akm8973_aot to /dev/akm8975_aot. Also change 8973 to 8975 in the ueventd.chacha.rc.

Cadabena · Oct 22, 2011

I'm really thrilled about this work and would love to help but I'm nowhere near the technical level of you guys. I recommended this phone for my girlfriend after her 3GS and she's never been happy with me since, constantly out of memory, she just wanted something like CM7 on my Desire so this would be perfect. Would a custom HBOOT be coming along with this to make up for the considerably smaller /system footprint from CM7? Once again thanks for all your work on this little niche device, you're saviours to me right now.

adlx.xda · Oct 23, 2011

working keyboard

small update (yet big achievemnt for me): 0 and ? keys are working now.
btw, xdbg also fixed it, before me atually, but I was already almost finishing to fix it when I knew about it, so I finished lol

xd.bx · Oct 23, 2011

adlx.xda said:
small update (yet big achievemnt for me): 0 and ? keys are working now.
btw, xdbg also fixed it, before me atually, but I was already almost finishing to fix it when I knew about it, so I finished lol

Heh

Now what remains is the Camera and Bluetooth. I haven't made much progress on that front so far.

qbert456 · Oct 23, 2011

Bluetooth is quite a big deal for me as I pair phone with car to/from work!

But if it didn't work I'd still give it a go, might use my legend for car journeys....

Great work guys!!!

Sent from my HTC ChaCha A810e using Tapatalk

Alex C. · Oct 23, 2011

qbert456 said:
Bluetooth is quite a big deal for me as I pair phone with car to/from work!

But if it didn't work I'd still give it a go, might use my legend for car journeys....

Great work guys!!!

Sent from my HTC ChaCha A810e using Tapatalk

Off-topic question: what car is it? (manufacturer/model).

[ROM] SuperOSR and CyanogenMod7 on HTC ChaCha.

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Inactive Recognized Developer

Senior Member

Senior Member

Inactive Recognized Developer

Attachments

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts