[ROM] SuperOSR and CyanogenMod7 on HTC ChaCha.

xd.bx · Nov 30, 2011

themickman007 said:
Is a problem in libcamera service hard to fix? Possible to steal libcameraservice.so from another htc device where the camera works on their cm7 rom?

It's a 600 kb binary, so it's a pain to reverse engineer. Your solution looks good although there are sadly few recent HTC ARMv6 devices as compared to the more common ARMv7. Maybe someone could try with the libcameraservice from the Wildfire S.

Sent from my HTC ChaCha A810e using xda premium

qbert456 · Nov 30, 2011

Sorry I made a mistake, camera not working- when I actually took a pic for first time today it fc.

Just thought id say in case you thought I had a random working rom!

Sent from my A810e using Tapatalk

themickman007 · Nov 30, 2011

I'll give the wildfire s libcamservice a test now but I dont think that their camera is working either in the cm7 rom so probably the same issue. Thanks again for looking into this even though i know before you said you were over it haha.

Qbert - I am a big fan of smart keyboard pro. If you select it as the keyboard and turn on prediction it gives a neat one line bar above the keyboard (bottom of the screen) which looks much better than any of the others i have seen, as well as being the most accurate with predictions.

Edit: I'll try the HTC aria libcamservice first as it has a 5mp camera is a htc and they have a working cm7 camera

I have to say though this really has put me off htc for the future - wish they didnt have to make everything so hard.

---------- Post added at 09:51 PM ---------- Previous post was at 09:24 PM ----------

I'm getting a hang on the boot screen when replacing the libcameraservice.so with the one from the aria. I'm guessing its a different camera and it wont recognize properly. I am trying the desire s libcam because it has a 5mp and 0.3 front one as well. Different chipset though so i am doubtful it will boot

themickman007 · Nov 30, 2011

libcameraservice.so from desire s gets to the boot screen but running a logcat it looks like it has an error with media.audio_policy.

Ive tried replacing the audiopolicy.so file but that makes it worse. I am not sure what else to do at the moment so I'm just going through google and seeing if anyone else has had a similar problem

mosamjc · Dec 1, 2011

Out of curiosity, I tried the libcameraservice from the htc explorer and it booted up fine compared to the other couple I tried, which wouldn't boot at all. Unfortunately it just fc when I opened the camera app. I didn't do a logcat as I was away from my computer but I will later and see if it reveals anything useful.

Sent from my A810e using XDA Premium App

themickman007 · Dec 1, 2011

Was it from a cm7 rom or from stock? Ive been trying out the cm7 ones hoping that if it does boot it wont have those fc's

Alex C. · Dec 1, 2011

xdbg said:
On the stock ROM, Camera Illusion works fine. We are using the same libcamera and liboemcamera as stock. I'm thinking this is an issue caused by the middle layer, that is the libcameraservice and libcameraclient. We already had to fix the CameraHardwareInterface, but obviously there is some additional magic required.

It's also very possible that the kernel sources provided by HTC do not match the actual sources they used to build the stock ROM.

EDIT: in fact, it would be very useful to try a CM7-based ROM with the stock kernel. Even though touchscreen won't work, we can try the Camera by key navigation. Anyone feels up for this?

Give me a shout if you need any testing done. You can also use GTalk/Yahoo if you want.

xd.bx · Dec 1, 2011

Hello guys,

Thanks to everyone for the additional camera tests. In addition, the main developer of the WildFire S CM port has kindly pointed me to his latest commit: https://github.com/alquez/android_device_htc_marvel/commit/e58ccace534da5f88ed9774e7fb87966cf495776

In summary, it replaces the proprietary libcamera.so with a version compiled from sources, which is very useful for debugging, leaving only liboemcamera as the remaining proprietary library.

The other route is instead to push the libcameraservice from stock ROM into CM7. It will not work out of the box since new APIs were introduced, so a slight tweaking of the camera client may be required.

EDIT: a careful study of differences between stock and CM7.1 shows several new parameters not present in CM7. Some are related to the face detection engine used by HTC. The most interesting is the capture-mode, which does not exist in CM7. See attached file.

themickman007 · Dec 1, 2011

Hey i cant really say i understand all the differences but i have noticed that when recording a video it only shoots at roughly 1 frame per second and in the params there it has a section called video size and format. There is also a similar one for picture size and format could it be that the camera doesnt know what size to shoot at?

Sorry i cant be of more help im trying to learn this stuff as i go along

xd.bx · Dec 1, 2011

Alright, sorry for being off-topic, but as I was reading android-building, I came across

This page contains binary image files that are provided for use in restoring your Nexus device's original factory firmware. These files are for use only on your personal Nexus devices and may not be disassembled, decompiled, reverse engineered, modified or redistributed by you or used in any way except as specifically set forth in the license terms that came with your device.

<rant>Once again Google pretend they like openness, although in truth they don't care -- in this regard, they are no better than HTC. In fact, they never bothered to include the hardware support that Qualcomm provided in the Code Aurora Forum. I'd like to also quote from http://source.android.com/tech/encryption/android_crypto_implementation.html:

While the actual encryption work is a standard linux kernel feature, enabling it on an Android device proved somewhat tricky. The Android system tries to avoid incorporating GPL components, so using the cryptsetup command or libdevmapper were not available options.

Fortunately, the startup that made Android chose the (GPLv2) Linux kernel before it was bought by Google. Otherwise, we might have been left with a binary-only, BSD-style kernel instead. Think about it. </rant>

---------- Post added at 09:33 PM ---------- Previous post was at 09:31 PM ----------

themickman007 said:
Hey i cant really say i understand all the differences but i have noticed that when recording a video it only shoots at roughly 1 frame per second and in the params there it has a section called video size and format. There is also a similar one for picture size and format could it be that the camera doesnt know what size to shoot at?

Sorry i cant be of more help im trying to learn this stuff as i go along

Yep. I'm also thinking about video acceleration and the yuv420sp-adreno parameters, it's like shooting works but playing it back is not hardware accelerated.

xd.bx · Dec 2, 2011

adlx.xda: I did a fresh CM 7.2 build, as almost everything works (the new Dialer is awesome!) However the 0/Symb key always shows the IME selector dialog instead of the proper key. Any idea? (I'm using your kl/kcm files).

sathara · Dec 2, 2011

xdbg cool bro .. when gona come online ....

adlx.xda · Dec 2, 2011

xdbg said:
adlx.xda: I did a fresh CM 7.2 build, as almost everything works (the new Dialer is awesome!) However the 0/Symb key always shows the IME selector dialog instead of the proper key. Any idea? (I'm using your kl/kcm files).

Have a look a this commit http://www.assembla.com/code/androi...sets/fcd8943702afd43b621954f4f1637c4f6155df5f

Look at the comment in the system.prop file especially

.

xd.bx · Dec 2, 2011

adlx.xda said:
Have a look a this commit http://www.assembla.com/code/androi...sets/fcd8943702afd43b621954f4f1637c4f6155df5f

Look at the comment in the system.prop file especially .

Thanks, that's a clever change

BTW I managed to debug mediaserver on stock with the gdbserver from the latest NDK. It's actually rather easy as long as you don't forget to set solib-search-path (the list of break-able functions in libcameraservice.so can be obtained with option -T of objdump from the NDK). However I can't attach at the start of mediaserver which is when it seems to pass the parameters (or maybe I'm setting a breakpoint on the wrong function).

xd.bx · Dec 2, 2011

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.

qbert456 · Dec 3, 2011

On this latest cm build, what happens when the keyboard is used? Any word options please?

Sent from my A810e using Tapatalk

carstenheuer · Dec 3, 2011

in the last CM7 build i have no more problems with the phone.apk

.
but unfortunately my german keylayout does not work

Alex C. · Dec 3, 2011

xdbg said:
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.

Updated OP. Removed FIXED fields from both roms.

qbert456 · Dec 3, 2011

Somone told me to try smart keyboard pro, so I have and it works well with a hardware keyboard, options come up as they used to.

Thanks for that tip earlier!

Sent from my A810e using Tapatalk

xd.bx · Dec 3, 2011

carstenheuer said:
in the last CM7 build i have no more problems with the phone.apk .
but unfortunately my german keylayout does not work

Awesome! Since I'm now using the same ro.ril values provided by adlx.xda, it probably fixed this issue for you. Btw, adlx.xda, where did you find there values from?

However I switched to the standard keycodes as used elsewhere in CM7 (Vision, etc.). This means you cannot use the kcm files from stock ROM, but need instead the kl/kcm files that are made for SuperOSR (I think there is a link to these files in the first post).

[ROM] SuperOSR and CyanogenMod7 on HTC ChaCha.

Senior Member

Senior Member

Member

Member

Senior Member

Member

Senior Member

Senior Member

Attachments

Member

Senior Member

Senior Member

Senior Member

Inactive Recognized Developer

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts