Updated the link in the first post to correctly direct to the whole keypad files instead of QWERTY layout. Users should check the thread and read it thoroughly.
[ROM] SuperOSR and CyanogenMod7 on HTC ChaCha.
- Thread starter Alex C.
- Start date
Thanks! Btw I made a new thread on the topic of reverse-engineering the libcamera, see http://xdaforums.com/showthread.php?p=19943347
Regarding ro.ril props, I can't remember exactly, but I'd say I took them either from the liberty props or my stock Chacha (spanish) rom, from which I also took the proprietary files btw.
Yep, IIRC I made all the kl/kcm.bin files and published them in a comment, althought I can't remember if I made some more changes to the kl/kcm.bin chacha file since... So try and check with the one I provide for your country/layout and see if it works.
Cool, thanks for letting me know
I'm glad the ro.ril fixed carsten's phone call problem. Btw I'm downloading the CM9 tree as of now, will see how hard it is to port it over the ChaCha (I hope not too many hardware-related fixes will be required).
dude..This build is based on the latest CM 7.2.0 with adlx.xda's fix for the 0/Sym key:
http://www.mediafire.com/file/zyhjblf3az77hml/update-cm-7.2.0-RC0-ChaCha-KANG-signed.zip (no longer using FileFactory. which, btw, sucked
The camera still does not work, so I've removed the APK for the time being. Wi-Fi is still the same as SuperOSR, my earlier experiments did not lead to an improved connexion.
i just started using your CM7.2.. Been using it for about a few hours actually..
I've been getting a lot f FC's.. process.core and media server blabla
I had flashed the gapps in the OP which is pretty old and meant for 2.3.5 and not 2.3.7..
Could the old gapps be the reason or is it related to something else ??
Could you provide us with an updated gapps file ??
dude..
i just started using your CM7.2.. Been using it for about a few hours actually..
I've been getting a lot f FC's.. process.core and media server blabla
I had flashed the gapps in the OP which is pretty old and meant for 2.3.5 and not 2.3.7..
Could the old gapps be the reason or is it related to something else ??
Could you provide us with an updated gapps file ??
Hi,
Thanks for the testing. I haven't tested the gapps yet. Can you tell the precise steps taken to reproduce the force close?
Btw, I do recommend doing a wipe in all cases.
okay..
just to clear the process, i was running SuperOSR..
backed it up using CWM, wiped all partitions..
installed from zip CM7.2..
started up the phone, works well.. (just one FC andrpid.process.core)
noticed that i had no gapps on it.. so downloaded gapps n flashed it via CWM..
started up system, and there.... lots of FC's couldnt do a proper google sign in because of the massive number of FC's..
Atlast switched back to my SuperOSR backup..
(only because this is my primary phone and i needed my contacts n other stuff)
Will it be possible to provide us a new updated gapps package ??
Only Google can
Seriously though, I noticed something wierd when flashing CM 7.2.0: the gapps were still there, which means the update package didn't reformat /system but instead flashed itself over it without refomatting.
I haven't had any FC yet. Please provide a full logcat after reinstall+cache & data wipe, otherwise I can't really help fixing this issue.
Hey, what about making it an option to have the facebook button work as part of the qwerty keyboard? - like a symbol or an internationall char?
(though the possibility of using it to launch home or an app would still be very very useful - especially since non-physical android (touch) keys below the screen suck
---------- Post added at 04:29 AM ---------- Previous post was at 04:24 AM ----------
Also try igCamera - pretty good replacement for the default CM cam.Think I might have found a workaround for the superosr camera. If you go to the market and download an app called camera illusion it works fine (no flash as far as i can tell though).
I'm not sure if you could see how it works or just replace the default camera app completely but it seems to run great.
After a few more days usage i have found (apart from minor theme issues like the dialer which works fine for me anyway) that the only problems left seem to be the marginally worse wifi reception which doesn't affect me too badly anyway and the on screen keyboard when clicking on a text field.
Overall its a great build which i use as my daily one now
Edit: Sorry the flash does work too
Last edited:
On osr I've got a new problem,
When I press green button to go to the dialer app, then try to manually enter nunbers, only the zero key will work-the rest I have to press shift at the same time.
This may of course be down to me using smart keyboard pro but I've not noticed it before as I rarely have to enter a number manually.
Also, this new market....how do I get the old quicker one back does anyone know please?
Sent from my A810e using Tapatalk
When I press green button to go to the dialer app, then try to manually enter nunbers, only the zero key will work-the rest I have to press shift at the same time.
This may of course be down to me using smart keyboard pro but I've not noticed it before as I rarely have to enter a number manually.
Also, this new market....how do I get the old quicker one back does anyone know please?
Sent from my A810e using Tapatalk
Last edited:
The problem has been reported since first release of both ROMs. Please check OP.
@abraham89 - your FC's are related to contacts syncing. I'm going to look into this but I can't promise anything unfortunately.
Please try one more thing:
- Full wipe, wipe cache, dalvik cache, sd card, everything
- Install the ROM
- Boot the ROM and leave it for 3-4 minutes to finish initializing
- Re-boot into CWM and install Gapps
- Try booting normally afterwards
- Post results
i find the rom is not so smoothly. unfortunately i have still one FC in the phone.apk.
but it is different now! when the proximity sensor is inactive i can talk normally (with the speaker!).
as soon as I take the cell phone to my ear the connection is interrupted. : (
but it is different now! when the proximity sensor is inactive i can talk normally (with the speaker!).
as soon as I take the cell phone to my ear the connection is interrupted. : (
this issue should be solved. Actually I just tested and I can't reproduce it. It works fine on mine. Can you make a video?
I've published my git repositories: http://xdaforums.com/showthread.php?p=19986382#post19986382
You sir, are awesome. Congrats on your great work! Any chance you could provide a CM7 build too? I'm thinking I may not have all your fixes in my frameworks/
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
54Hello everyone!
This topic contains all the development stages of custom ROMs, please read the full topic before asking any questions; refrain from asking silly questions/"questions that are easier to answer on Google than logging into XDA, browsing to HTC ChaCha, dev section, this thread, click on post reply, entering the question, clicking submit, waiting for someone to read and reply"/un-constructive feedback-criticism/anything unrelated to these two roms.
In the order of their availability:
NOTE: Give thanks and feedback to the developers. Install any of these roms for the purpose of testing and providing information/feedback in the thread. Neither of these are stable yet, they are experimental builds and this topic represents the simplest bug tracking database.
Apparently users do not read the known issues list. FRONT CAMERA is NOT working. Do not switch to front camera, otherwise Camera.apk will crash constantly. To fix this go to Settings -> Applications -> Manage -> All -> Camera -> Clear data and cache -> Reboot your phone.
I. SuperOSR by adlx.xda
SuperOSR (OpenSourceRom and CM) based ROM: SuperOSR-chacha-2.5-20120724.zip - 83.13 MB
Current version: 20120329-0005
More information about the ROM HERE.
Tips and tricks, known issues and workarounds:
Release notes for 1314
- New kernel with swap enabled. it will also now mount correctly your sd-ext partition as ext4 (if formated as ext4, which is the how my CWM will format it).
Release notes for 0159
- FB key remap option in SupSetup/Parts
- All the keypad fixes avail to date (only for unlocked users, S-Off will still need the patches)
Release notes for 0513
- Build is odexed --> I believe it is a significant gain of space in /data (now it will occupy <30 Mb after first start, leaving 120 Mb free)
- Comes with all the keyboard kl/kcm.bin. (only usefull if S-On, bc S-Off lost their CID. If S-Off flash a keypad patch after the rom)
- Removed bloat
1. Wi-Fi module is not connecting to hidden networks. - reported as fixed, router channel must be set <13
2. Sometimes Wi-Fi will not connect to an AP after setting it up (Scanning -> Connecting -> Disconnected -> Scanning -> Connecting.. etc.). In this case press and hold the connection, remove it, create it again, then switch Wi-Fi off/on.
3. I suggest performing the following if you still cannot connect to a visible Wi-Fi AP: Settings -> Wireless & networks -> Wi-Fi Settings -> Press menu button -> Advanced -> Regulatory domain -> 13 channels -> Wi-Fi sleep policy -> Never
4. Front camera is not working. In study.
5. Default battery icon and percentage battery icon shown at the same time if activated from the CM settings. No workaround available yet.
6. Facebook button is unassigned (does nothing). What should it open?
II. CyanogenMod (by xd.bx) since 19.01.2012 adlx.xda took over
CM 7.2.0 (CyanogenMod) based ROM: DOWNLOAD Release No.: 20120321-2039
More information about the ROM HERE.
Tips and tricks, known issues and workarounds:
1. Wi-Fi module is not connecting to hidden networks. reported as fixed, router channel must be set <13
2. Sometimes Wi-Fi will not connect to an AP after setting it up (Scanning -> Connecting -> Disconnected -> Scanning -> Connecting.. etc.). In this case press and hold the connection, remove it, create it again, then switch Wi-Fi off/on.
3. I suggest performing the following if you still cannot connect to a visible Wi-Fi AP: Settings -> Wireless & networks -> Wi-Fi Settings -> Press menu button -> Advanced -> Regulatory domain -> 13 channels -> Wi-Fi sleep policy -> Never
4. Front camera is not working. In study.
5. Facebook button is unassigned (does nothing). What should it open?
Other useful information:
ChaCha Keypad Files/Key mapping
http://xdaforums.com/showthread.php?t=1456154
http://xdaforums.com/showpost.php?p=18763527&postcount=101 from adlx.xda
These should be placed on your device to change your keyboard layout.
Google Apps - Used for Google account (contacts/calendar sync); also contains GMail/Market. This is not included in the CM rom (by default, CyanogenMod does not contain Google services and applications; these can be added separately by users that want them). Remember that there are users who would like to remove everything Google related from their roms as there are some services which use internet/battery when they want and have dependencies with Google Contacts Sync/Calendar Sync/Gmail. Include requests of gapps into a custom ROM by default will be declined.
http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip
Fix for GSM/Phone.apk crash
http://xdaforums.com/showpost.php?p=20710120&postcount=474
Thanks to carstenheuer for finding this out.
Radio - for people having GPS issues (unable to find sats/get a fix)
http://xdaforums.com/showthread.php?t=1257776
A810b
Another thing has come to our attention: a new region-based model is out, the A810b.
Do not flash any of the radios available around here as they are mostly based for the A810e model, which uses a different network bandwidth and a lot of issues might occur.
For more information regarding GSM network frequency, check here: http://www.gsmarena.com/network-bands.php3?
This might also provide some information as to why 3G doesn't work, for example.
Small adb kit
For people that need adb without installing the whole SDK kit, adlx.xda provided a little bit of knowledge regarding this nifty little thing included in other applications.
http://alex.swtesting.ro/downloads/adb-and-moto-fastboot-win32.zip
GPS fix
For people out there without a working GPS on one of the two builds the fix is:
1. Get a stock ROM.
2. Go outside using a GPS application (like GPS Test from the Market)
3. Wait until you get a fix and a location.
4. Flash SuperOSR/CM.
5. Redo step 2.
65working so far
yesterday late I tried with xdbg's kernel, init.chacha.rc & bcm module and the TS worked. using his kernel I got to test more things:
So far, in my build this is what I have tested:
- Touchscreen: OK
- Calls (with audio): OK
- Data (3g): OK
- Wifi: OK
Doesn't work (yet):
- Physical keyboard (I can get data from input device though)
- leds and backlight, not well tested, but didn't seem to be working (it work manually though, by echoing in the /proc)
- Camara
- GPS
- Sensors
SMS, MMS: untested
Screenshots gallery: https://www.dropbox.com/gallery/788286/1/SuperOSR-Chacha?h=5cc26e#/5Hi.
A couple of pointers/possible solutions:
- Physical keyboard (I can get data from input device though)
You must patch frameworks/base/include/ui/KeycodeLabels.h or remove the unknown keys from chacha-keypad.kl. I suspect other files must be patched as well, for example to make the 0 work.
Check that you have lights.msm7k.so and also check the permissions in init.chacha.rc. You might need a newer lights than the one used in the Liberty.
I think the libcamera.so from HTC has a different API than CM7. Also you must uncomment PRODUCT_SPECIFIC_DEFINES += TARGET_PRELINKER_MAP... in your vendor/cyanogen/products/cyanogen_chacha.mk.
Check the libcameraservice source code. This problem could be slightly harder to fix.
I think the radio is more recent than on the Liberty, hence the loc_api version will be higher. Try 20000 and 50000. Also try with the gps.chacha.so from stock ROM.
Try with a newer libsensors or sensors.chacha.so from stock ROM.
