[ROM] SuperOSR and CyanogenMod7 on HTC ChaCha.

Search This thread

adlx.xda

Inactive Recognized Developer
Feb 4, 2010
1,541
1,752
Madrid
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/

Thanks you, some people help me too, in the deving, testing, bug reporting... Actually it reminds me I should give credit somewhere.

Yep, a priori I've no problem building a CM build, other than getting the right time windows to actually do it (and maybe size/space issue on disk, and DL sources, make the necesary modifications and build lol)... On wednesday I'll leave for holiday until sunday late, so until next monday I won't be able to do anyth.

Btw, what was the camera app that was working as a substitute of Camera.apk?

I tried IgCamera yesterday but it seemed to freeze the same as the Camera.apk. I remember someone once talked about another app, right? Was it working on SuperOSR? Thanks :)

Btw I haven't tried to use Alquez's libcamera yet, xdbg: have you tried? I tried to email him, but he didn't answered me yet.
 

dvfk

Senior Member
May 5, 2010
184
13
Btw, what was the camera app that was working as a substitute of Camera.apk?

I tried IgCamera yesterday but it seemed to freeze the same as the Camera.apk.

Have you tried tweaking igCamera resolution ? that's what made it work for me (on Arc S... got a ChaCha too so I'll be tesing soon) but the reso was the all important setting for it to work.
Perhaps a few other settings is worth trying to tweak too.
 

xd.bx

Senior Member
May 14, 2011
431
292
Have you tried tweaking igCamera resolution ? that's what made it work for me (on Arc S... got a ChaCha too so I'll be tesing soon) but the reso was the all important setting for it to work.
Perhaps a few other settings is worth trying to tweak too.

Yes, I've noticed already the preview and capture sizes differed between CM and stock. It would be very cool it the solution is just to tweak these values :)

adlx.xda: the libcamera in alquez's repo won't build. Even if it did, I'm unsure it would cooperate nicely with liboemcamera out of the box.
 

adlx.xda

Inactive Recognized Developer
Feb 4, 2010
1,541
1,752
Madrid
adlx.xda: the libcamera in alquez's repo won't build. Even if it did, I'm unsure it would cooperate nicely with liboemcamera out of the box.

Thanks, you're saving me some precious time ;)

Yes, I've noticed already the preview and capture sizes differed between CM and stock. It would be very cool it the solution is just to tweak these values :)

Indeed, it would be great. Actually, since the beginning I'm thinking it shouldn't be that hard (I mean disassembling-hard), because having a look at all the htc devices in CM tree, none of them have a lot of stuff for camera IIRC.
 

xd.bx

Senior Member
May 14, 2011
431
292
I've pushed correct camera includes, it's on my github :) Be warned, that this solution works on 7.1.0 sources so far (broken in 7.2.0)

Cool. I'm thinking the libcamera issue is linked to post-processing, in particular HTC sets up a bunch of post-processing parameters not present in AOSP/CM:

Code:
$ grep postproc ~/gdb-output-htc.txt 
0xa79134ff <__dso_handle+4264623>:	 "postproc-active-flash"
0xa791252a <__dso_handle+4260570>:	 "postproc-iso"
0xa7912537 <__dso_handle+4260583>:	 "postproc-width"
0xa7912546 <__dso_handle+4260598>:	 "postproc-height"
0xa7912556 <__dso_handle+4260614>:	 "postproc-action-screen"
0xa791256d <__dso_handle+4260637>:	 "postproc-YUVoffset"
0xa7912537 <__dso_handle+4260583>:	 "postproc-width"
0xa7912546 <__dso_handle+4260598>:	 "postproc-height"
0xa791256d <__dso_handle+4260637>:	 "postproc-YUVoffset"
0xa7912556 <__dso_handle+4260614>:	 "postproc-action-screen"
$ grep postproc ~/gdb-output-cm7.txt 
0xa7913485 <__dso_handle+4264501>:	 "postproc-active-flash"
 

pongzor

Member
Mar 11, 2011
25
2
Hi

I am using SuperOSR and i really like it. The only problem is that the camera is not working. Is there any news for a camera fix already?

Or is there another good rom which has the camera available?

Last question: can i return to stock rom and so how? I need my camera because i am going on a trip and want to make some quick photos for friends to post it on facebook
 

xd.bx

Senior Member
May 14, 2011
431
292
Hmm I think they used a froyo libcamera.so, which is a simple yet elegant solution.
 

qbert456

Senior Member
Jul 21, 2010
432
34
The smart keyboard isn't as great as I thought. Anyone have a different solution perhaps please?
Thanks

Sent from my A810e using Tapatalk
 

abraham89

Senior Member
Nov 25, 2010
183
18
35
Cochin
www.facebook.com
Here I am, but December isn't a good month for dev, Christmas preparation, and a lot of holiday here. So be patient, or take the source ;)
I have some free time here.. so.. could you please guide me how to develope a CM9 build from source ?? I think I could help in some way.. and I feel you're the right person to ask for help here ;)


Sent from my A810e using XDA App
 
  • Like
Reactions: adlx.xda

qzfive

Senior Member
Aug 8, 2010
209
49
Would it be possible for a vdd_levels sysfs interface patched into the kernel for undervolting? I'm getting an XTC-Clip sometime soon and I'm willing to test stuff once it gets here :)


PS. If it's not too much trouble, is there any "guide", so to speak, on how to download the Chacha's kernel source (preferrably the one used in either of these ROMs) so I can possibly experiment with adding additional CPU values (as per this Wildfire S kernel and overclocking?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 54
    Hello 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.

    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
    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. 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.
    6
    CM7 Roadmap

    For those who missed it, check http://www.cyanogenmod.com/blog :D

    After CyanogenMod 7.2 is released, we will be merging in and welcoming aboard maintainers for the following devices (with more queued):

    HTC Status (chacha)
    HTC Wildfire S (marvel)
    LG Optimus Chic (e720)
    Motorola Photon (sunfire)
    Samsung Galaxy 5 (i5500)
    5
    working 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#/
    5
    Hi.

    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.

    - leds and backlight, not well tested, but didn't seem to be working (it work manually though, by echoing in the /proc)

    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.
    5
    Link removed because it was obsolete