yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] Enigmatik_best:
I confirm, I did the test with the the HaRET included in FRX07.1 bundle and it doesn't launch the zImage contrary to the HaRET included in the kernel of Brinka123 (and Viruscrazy).

(in condition to add the line set initrd_offset 0x00a00000 in the startup.txt adapted to the device of each)

Now the result of the patch (by my phone HTC TP2 Rhodium100(FR)

:

cam used for photo: Work longer that before (finish to freeze anyway)

cam used for video: Work now (no sound anyway; just sometimes sputters) (like the cam for photo, finish to freeze after a random time of use)

Reflexion

:

- seem to fill a memory (RAM, ROM or both (?)) and then freeze;

- random results for native cam application and Cam360 application (the 2 tested at this moment);

- ...

At those who tested on a Rodhium100 (HTC TP2) and said that work (Littlebigtux, Stijnjits, Schumi_wk, Djcrosstunez, Schlei, ...):

Can you tell me if it work everytime or finish to freeze/block too please :confused: :o

Thanks in advance for your contribution :o
[Touch Pro, Fuze Android Development] brinka123:
Thanks for testing enigmatik_best.

1] I have hangups sometimes with camera360 when using some effects (retro) for example. When camere tries to focus, it hangs. Probably other devices have this too.

2] I found that pictures where dark in dark circumstances, comparing to my blackstone. Attached a new version (sorry) with a better exposure. Please try it.

I don't have any hangups with the standard camera.
[Touch Pro, Fuze Android Development] littlebigtux:
Exposure is clearly more "reactive" when zooming and in low lights. (with V3)

Autofocus perfectly works for me. I tested with QR readers which use it intensivly and had no problems.
[Touch Pro, Fuze Android Development] littlebigtux:
I tryed Camera 360.

I like it, but Idon't think it's a good way to test camera, because there are pre-treatment during targeting and post-treatment of the shots.
[Touch Pro, Fuze Android Development] Enigmatik_best:
YES! I confirm the good work on the exposure, better lighting in low light.

Autofocus is very good for me too :cool:

There is again a little "lag" but less than before.

Cam-video work always and seem better than before (?).

No "crash" for this moment with use only the native cam apk.

(but no more tested with another "big" program in same time of the cam)

Hip Hip Hip Houraaaa!!! Brinka123 (and others contributors (?)) :D:cool::)

Continue in this way and we shall have almost same quality as the native cam application under WM6.5 ^_^

Here is an example of the difference between the picture with the V2 patch and with the V3 patch ... you'll see immediatly the progress :cool:

~~~~~~~~~~With the V2 patch_____________________________________With the V3 patch (Camera100_ver3.ZIP)~~~~~

PS: Littlebigtux, Brinka123, Arrrghhh and others ... : What did you tested of alternative cam application than the native cam?

There are Cam360 (good but slow and freeze), Camera Advance (bad according to me), ... ? Not yet found application as complete as in the application of HTC WM6.5, witch not freeze and not too slow :confused:
[Touch Pro, Fuze Android Development] nickleby:
I've a RHOD500 and I felt curious to test this patch V3 because of your pictures..I always thought that the pictures taken in Android are too dark even with good lighting. I mentioned it to arrrghhh months ago, but I completely forgot to post that here...Did not try this patch extensively, but I really notice the difference in the pictures. Maybe it's not a big deal but there is definitely an improvement in the clarity of the photos; are not as dark as before.
[Touch Pro, Fuze Android Development] arrrghhh:
Nice!

JB is kinda out of it lately, and hasn't been able to help with this patch. Trying to get him to work with brinka123, hopefully they can get a patch that can be implemented.
[Touch Pro, Fuze Android Development] littlebigtux:
I don't find much interesting camera apps on the market.....

Most of them are just "software"gadgets and a lots don't work, but the problem isn't due to the camera itself (filters, treatments,... can't be really evaluated).
[Touch Pro, Fuze Android Development] brinka123:
First we have to thank viruscrazy.

Thanks Enigmatic_best showing the difference between the versions.

Integration of the patch is very easy, when JB knows that

raphael, sapphire, diamond and halibut devices are not degraded by this kernel.

So test it or just release the kernel and wait for responses (it is just a camera!). Put this in the appropriate forums??

According to me reducing the frames per second can not do any harm to the functioning of the camera.
[Touch Pro, Fuze Android Development] Stijnjits:
Is it normal that when running the 24th September 2011 kernel from Brinka123 on a RHOD100 I cannot access the cell phone network?

Same for the 26th September 2011 version.

Camera works fine! (Still wondering when it's going to make it into the autobuild...)

But I do notice a bit more lag on the camera image when taking pictures in the dark.

Edit: rebooted android 5 times and it does connect finally.
[Touch Pro, Fuze Android Development] arrrghhh:
I don't think brinka123 has submitted an acceptable patch. JB hasn't been around much to work with him either (although I hope they've exchanged some emails.... right?)
[Touch Pro, Fuze Android Development] brinka123:
Last mail received from JB 27-sept.

JB has no time.

It's nice to see that many people are happy with the working camera.

Quality of the pictures is quite good!

The kernel V3 works fine. When having troubles it could also be the build or memory problems.
[Touch Pro, Fuze Android Development] ryannathans:
http://xdaforums.com/member.php?u=1933486I tried the v3 'test' kernel/haret however it just freezes after I run haret, tried both harets with the kernel provided.

RHOD110

My camera still dies in the light with normal kernel.
[Touch Pro, Fuze Android Development] arrrghhh:
You need to basically do the same steps for a .35/.39 kernel. New HaRET & offset, should be good to go.

Commits still haven't been pushed. I haven't seen any merge requests or anything for that matter. brinka123, I think you posted them to the mailing list... Did you clean them up? IIRC you posted them in a very early (unacceptable as-is) state...
[Touch Pro, Fuze Android Development] ryannathans:
Woot. Thanks arrrghhh & guys in irc.

Missing offset, must have overlooked it.

Works wonderfully :D

I'd love to see this committed asap, as long as it's acceptable
[Touch Pro, Fuze Android Development] quirrel:
camera still not working

I use Diam100 but camera does not work for me with V3 zip linked on this or previous page. Anyone knows if it is allready in some release?
[Touch Pro, Fuze Android Development] arrrghhh:
Not to my knowledge, but this fix was more targeted for RHOD100. Not sure it'll help DIAM at all.
[Touch Pro, Fuze Android Development] Stijnjits:
I saw this problem has a "fixed" status on the rhodium-nand bugtracker. So I'm wondering if it is included in recent kernel builds? (Like the new kernels voor GB)
[Touch Pro, Fuze Android Development] arrrghhh:
Probably just NAND if you say it on the NAND bugtracker :rolleyes:

As always, you can check the commits on GIT.
[Touch Pro, Fuze Android Development] Stijnjits:
Thanks for your reply, Arrrrghhh! I was just wondering if it is also included in for example the kernel autobuilds...

But checking the Git is a good suggestion! Thanks!
[Touch Pro, Fuze Android Development] viruscrazy:
Ok. Then, there will be 2 problems. I've already tried to relocate the library from 0xA7700000 to 0xA9400000 like awaited by the system (that's where the "working" liboemcamera.so is loaded) at the begginning of my work on camera. This works but there's a bigger problem that I did not see when I started relocated it...this library is made for armv7 processors and ours are only armv6, so it won't work...

The only way we will have to make others sensors to work will probably to make some kind of "abstarction layers" between supported sensors (in liboemcamera.so) and supported sensors in kernel...that's what did Alex on xperia, so I think we will wait for it's driver to work and get inspired of it.

Regards, Jerome
[Touch Pro, Fuze Android Development] xUmaRix:
yeah stupid me it is for armv7.i had another one for armv6.i'll send u in email

D/QualcommCameraHardware( 1283): createInstance: E
E/QualcommCameraHardware( 1283): FATAL ERROR: could not dlopen liboemcamera.so:
Cannot load library: reserve_mem_region[810]: OOPS: 1283 prelinked library
'liboemcamera.so' mapped at 0x40a0c000, not at 0xa7400000

/ # strings /system/lib/liboemcamera.so | grep armv6
strings /system/lib/liboemcamera.so | grep armv6
../../../src/asm/armv6/jpege_engine_sw_dct.s
/local/mnt2/workspace2/zhiminl/tip/vendor/qcom-proprietary/mm-still/jpeg/lib/os/armv6
/local/mnt2/workspace2/zhiminl/tip/vendor/qcom-proprietary/mm-still/jpeg/lib/os/armv6
/local/mnt2/workspace2/zhiminl/tip/vendor/qcom-proprietary/mm-still/jpeg/lib/os/armv6
../../../src/asm/armv6/
[Touch Pro, Fuze Android Development] Damien50:
I try the Module and Zimage from the 29/12/2010 on rhod100_fr

I had launch ADB and execute ./lib_inst.sh and reboot but the Camera doesn't work.

After I try to add that in my froyo.user.conf

But always doesn't work :(

But thanks for your hard work !!!
[Touch Pro, Fuze Android Development] Younio:
I tried to make the camera work on froyo 2.2.1 release again, and still doesn't work (have only some squares flying around) while in eclair release I was able to see some green screen. So If someone was or will be able to get camera working on diam100 I would be glad if you shared your experience, what release, version of camera zimage and modules any of you are or have been using.

looking forward to solving the puzzle ;)
[Touch Pro, Fuze Android Development] funkys:
I have done nothing special on my DIAM100. I'm using latest FRX03(20.11.2010) with zimage and modules from 28/12 from the first post. Just make sure you copied lib_pack files in their directories. If it still not working, make some logs and send them to Viruscrazy.

best regards
[Touch Pro, Fuze Android Development] viruscrazy:
I think that the "squares flying around" were in the FRX01 system.ext2 image. This was because the camera was only "stubbed" in userland, and the squares are demo from the camera hardware stubs.
[Touch Pro, Fuze Android Development] Younio:
Thanks for replying,

Im now using this release "Barebone-CyanogenMod61-Minimum-System-22-11-2010"

Wich frx is that?

So I will try to install "ROM-FRX03-12-21" and see what happens. :)

both releases are from neopeek website (new usr cant post links)
[Touch Pro, Fuze Android Development] viruscrazy:
Hi,

I don't know about the CyanogenMod system you are using. Maybe he didn"t include the camera in userland as it was not working yet on our devices. I'm using the babijoe system.ext2 (FRX03). You can find it here : http://xdaforums.com/showthread.php?t=711692

I don't have time to test the cyanogen release, but maybe someone else has already tried it and can tell you if it worked for him.

Regards, Jerome
[Touch Pro, Fuze Android Development] mister-gwada97one:
@Younio: The camera on CyanogenMod doesn't work.. I have already try it. The only build I found to make the camera work is the FRX03 and FRX02 (as I saw by other members)..

@viruscrazy: I have an issue with charging battery, it stays at 60% (thing like this) and won't get more or less. What shoul I do ?
[Touch Pro, Fuze Android Development] Younio:
yeah thanks for confirming. The release i will be testing now is not cyanogen. Hope it works with it. :D

Thanks, but im already instaling new one ;)

I tried the release you are using, that was my firs one, but on my device it is very slow and often has 5 or 20sec lags.

will tel you how it went :)

cheers
[Touch Pro, Fuze Android Development] mister-gwada97one:
Ok ;) I saw your mesage on neopeek forum :p
[Touch Pro, Fuze Android Development] pdawg17:
Viruscrazy-

I PM'd you this info but in case you see this first:

I tried it on my Sprint CDMA TP2 (rhod400) and I can boot fine but when I start "Camera" I only get a black screen...it looks like the screen lights up slightly but I never see anything on the screen until the "force close or wait" box pops up...if I force close the phone reboots to WM...if I press wait then I continue to sit at a black screen...

I did the conf edit for binding the files as I don't know how to make my rhod400 connect to ADB shell...

Let me know if you want me to try your "troubleshoot" zImage to gather data for you...
[Touch Pro, Fuze Android Development] Younio:
Doesn't work on that release too, wifi doesn't seem to work either for my diam100 in there.

I guess I'll have to wait for someone more competent to figure out something. :)

EDIT: Instaled XDANDROID system again. Camera works pretty good, except video.

But the realese is very slow so I'll have to wait for neopeek's new release to get the camera working.

thanks for the help : )
[Touch Pro, Fuze Android Development] R^7Z:
Probably best to report that in the appropriate thread as we are talking about testing the camera here but what do I know... ;) On the other hand, I have noticed that WiFi wasn't working in the newer-ish kernel packages (posted HERE) and I haven't tested WiFi out since. Not sure if this is somehow relatable but other-wise not a bad kernel package.
[Touch Pro, Fuze Android Development] viruscrazy:
Hi,

Rhodium will need a small adjustement that bzo just sent me. Rhod400 may also need more work. You did right by doing the bind trick, that way, you don't screw your file system if something goes wrong.

I don't need now that you run the "troubleshoot" image but if you can get the adb to work, then could you send me the dmesg + logcat of camera start ? On diamond, to make usb work, we had to plug it under winmo, select ActyveSync profile, then start Haret. Now, it seems that we don't need to have the phone plugged during boot to get usb working but I can't tell for rhodium right now.

Regards, Jerome
[Touch Pro, Fuze Android Development] sukasaku:
latest zimage 28/12 at my RAPH, it can't boot. suddenly black screen after few second at opening kernel. back again to zimage 27/12 :D
[Touch Pro, Fuze Android Development] Corias:
+1. RAPH100, 20101228 kernel and modules: screen fades exactly after boot table appears.

Edit: Seems like some screen problems in this kernel: I've sent myself an SMS, and device played notification sound.
[Touch Pro, Fuze Android Development] djdafreund:
+2. Yup, that's exactly what my raph800 is doing also with trying to test this to be able to provide collected info to give back.
[Touch Pro, Fuze Android Development] pdawg17:
Jerome-

Here are my dmesg and logcat files for the rhod400...

I did them as attachments as they are too long to be embedded...
[Touch Pro, Fuze Android Development] arrrghhh:
Hey man,

You're more than welcome to use my "code" or 3 bind mount statements I put down :p. I'd love to see that info in the first post - put it in code braces or attach the modified file, doesn't really matter to me. Heck do both ;)

Thanks again Jerome. Can't wait till it's workin on my RHOD400. I see you already have a dmesg/logcat from said device, let me know if you want another - the exact same thing is happening to mine as well!
[Touch Pro, Fuze Android Development] viruscrazy:
@arrrghhh : I must admit that I didn't took time to edit the first post with your conf file...now it's done, hope this will be easier for testers. Thank you.

@all users (more specifically raphael and rhodium) : There an updated package on the first post. It should fix the raphael screen bug (some stupid tests) and does some changes to the rhodium camera init. Please, post your dmesg / logcat if you're experiencing any problems (related to camera, of course).

Regards, Jerome
[Touch Pro, Fuze Android Development] Damien50:
I try on my rhod100_fr but when I launch the camera the phone reboot.

I join the debug file, I don't know if this is the correct commands.

Thanks !
[Touch Pro, Fuze Android Development] viruscrazy:
Hi,

COuld you please start the phone, start the camera, and once phone has rebooted, typing "adb shell cat /proc/last_kmsg >last_kmsg.log", so that I can get the dmesg output just before the phone reboots.

Thanks, Jerome
[Touch Pro, Fuze Android Development] Damien50:
thanks for your help :p
[Touch Pro, Fuze Android Development] pdawg17:
Jerome-

Here are my new dmesg and logcat for new kernel...I still get a blank screen when I start "Camera"...the only difference this time is I can exit Camera without the phone rebooting...still cannot see anything on-screen though...

Rhod400

Sorry...the files should be named "Dec31"...in other words, these were taken from the kernel you just released...
[Touch Pro, Fuze Android Development] sirthoz:
Can someone help me upload latest kernel somewhere, i always have problems with the servers, upload in two links on the first post
[Touch Pro, Fuze Android Development] Captain_Throwback:
12/31 Kernel test

Good work, Jerome!

On my RAPH110 (Fuze), the camera preview now shows up correctly! The only issue remaining is the menu when the device is in Portrait still shows up as if the device is in landscape. Screenshot below:

On my RHOD300 (Tilt 2), the Camera still doesn't start, and eventually force closes and resets the device. I was able to get a logcat after attempting to start it once, and I'm working on using the method you posted to get another log after restarting. Below is the msm_camera output from the logcat from before the device restarted:

Line 465: <6>[ 1.418304] msm_camera: i2c probe ok
Line 471: <6>[ 1.563842] msm_camera: mt9t013 model_id = 0x2600
Line 495: <6>[ 1.705810] msm_camera: msm_sync_init: initialized mt9t013
Line 496: <6>[ 1.712341] msm_camera: msm_camera_drv_start: setting camera node 0
Line 496: <6>[ 1.712341] msm_camera: msm_camera_drv_start: setting camera node 0
Line 1101: <6>[ 238.108215] msm_camera: vfe_7x_release:241:Calling vfe_7x_stop()
Line 1103: <6>[ 238.108337] msm_camera: vfe_7x_stop:215: failed rc = -19
Line 1108: <6>[ 238.116485] msm_camera: mt9t013_release completed!
Line 1151: <6>[ 355.926300] active wake lock msm_camera_wake
Line 1171: <6>[ 537.055877] active wake lock msm_camera_wake
Line 1191: <6>[ 664.863891] active wake lock msm_camera_wake
Line 1216: <6>[ 1445.883819] active wake lock msm_camera_wake
Line 1243: <6>[ 1625.747711] active wake lock msm_camera_wake
Line 1263: <6>[ 1647.336730] active wake lock msm_camera_wake

Complete log is attached. I'll try to post the last_kmsg.log after rebooting into Android.
[Touch Pro, Fuze Android Development] arrrghhh:
Awesome news. I appreciate it!

I just did a test, and while my phone (RHOD400) doesn't reset, Camera just goes to the same blank screen then eventually FC/Wait dialog. Dmesg/logcat attached! (Sorry, had to compress them... my dmesg.txt was too big for the forum, for that file type!!)
[Touch Pro, Fuze Android Development] LENINred:
im can not connect my topaz to PC(( what i can do??
[Touch Pro, Fuze Android Development] CeasarRAPH100:
Just tested the new image, RAPH100 is a go !!, Portrait preview =OK, Landscape preview OK, and corresponding pictures turn out correct.

Pictures comes out very good, amazing work you guys put in there.

Just as info, maybe can help someone else

I had a faulty setting on "gsensor_axis=" in startup.txt, standard, correct and working is gsensor_axis=-1,-2,3, that's why my camera menu was upside down :rolleyes:

Great work !!!
[Touch Pro, Fuze Android Development] GoldAngelo:
Hello, can you send me your packages with camera drivers(?), where it works? My english isn't good so I'm sorry for any mistakes/bugs. Thanks, GoldAngelo.
[Touch Pro, Fuze Android Development] timma5:
can i use it @ blockstone:confused:
[Touch Pro, Fuze Android Development] CeasarRAPH100:
Check first post first link in this thread and there are the drivers, kernel & modules from 31/12 also in the first post in this thread.
[Touch Pro, Fuze Android Development] GoldAngelo:
I have kernel&modules from 31/12, but I can't rename froyo.user.conf.txt to froyo.user.conf and I had to reformat the PC, so i don't have current lib_pack. :(
[Touch Pro, Fuze Android Development] mister-gwada97one:
Get it here: http://www.4shared.com/file/sQDKAW6_/lib_pack.html
[Touch Pro, Fuze Android Development] GoldAngelo:
Thx for help.I take for a tested and I apologize for the trouble.
[Touch Pro, Fuze Android Development] Simon_WM:
shame, ant it
[Touch Pro, Fuze Android Development] xUmaRix:
for blackstone we dont have mt9t013 camera which is included in most of liboemcamera.so.we use mt9p012 camera and it need to be include in the library
[Touch Pro, Fuze Android Development] djdafreund:
unfortunately, even with 12/31 updates here, my screen still fades to black with a second after running haret.exe, i requested via pm per request, giving info requeste in hopes to send me something try on my touch pro (raph800), so i am just waiting til a respnse for now. Cant wait to start helping gather info needed, so i can finally rid wm for good. I know battery isnt greatest,but long enough for me to get by in between charges. Camea is mostly it left. I kn,ow things are always improving,so its cool with me.
[Touch Pro, Fuze Android Development] GoldAngelo:
The same thing happens on my raph100, and the buttons under the screen and the lights stop working. After a few minutes raphael can not wake up, work only LEDs screen.
[Touch Pro, Fuze Android Development] colo-natas:
This latest kernel works great on my raph110/Fuze. The camera takes great photos in the correct orientation. The white balance and brightness aren't great, but this is a big leap in progress.

Thanks guys!
[Touch Pro, Fuze Android Development] Thegn:
Could you please include the library in the next update, Viruscrazy? :)
[Touch Pro, Fuze Android Development] Sefy:
Ever since the last 2 zimage/modules, i see during boot these messages:

mdp irq already on 4 4

mdp_dma busy

What's all these mean ? cause they pop up a lot!
[Touch Pro, Fuze Android Development] sllyname:
I don't know about great for the kernel but on same hardware it looks like the red and blue channels are reversed, tangerines are blue and blue clothes are red, all nihon-jin look like smurffs.

Nice to see a picture though. thanks, mark
[Touch Pro, Fuze Android Development] lawrenceglue:
thank you~wait for the official edition~
[Touch Pro, Fuze Android Development] sukasaku:
the color on camera is not real.

example:

sky the real is blue n white, but on camera has yellow color.

my skin like alien.

everything is modified.

btw 3d game like NFS Shift has slowly rendering on this kernel (I use on 3d test hread its perfect)

Oh yeah my device Raph.

Thanks
[Touch Pro, Fuze Android Development] EGOvoruhk:
Don't know if this has been shared, but thought it might be of use: http://review.cyanogenmod.com/#change,1694
[Touch Pro, Fuze Android Development] raulvola:
Hi,

Camera works great on my HTC Diamond.

Video capture fails.

Here my "modified" instructions for people who installed Xdandroid into \Internal memory\andboot folder:

1/ MAKE A BACKUP

2/ Copy zImage, module-xxx and lib_pack folder content (*.so and *.sh files, NO folder) into andboot folder.

3/ Rename attached froyo.user.conf.txt file to froyo.user.conf, modify (unix text editor) the last three lines of froyo.user.conf this way, then copy it to your conf folder.

old lines:

mount --bind /sdcard/libGLES_qcom.so /system/lib/egl/libGLES_qcom.so

mount --bind /sdcard/gralloc.msm7k.so /system/lib/hw/gralloc.msm7k.so

mount --bind /sdcard/liboemcamera.so /system/lib/liboemcamera.so

new lines:

mount --bind /sdcard/andboot/libGLES_qcom.so /system/lib/egl/libGLES_qcom.so

mount --bind /sdcard/andboot/gralloc.msm7k.so /system/lib/hw/gralloc.msm7k.so

mount --bind /sdcard/andboot/liboemcamera.so /system/lib/liboemcamera.so

4/ reboot the device

Thank you very much. You are doing a great job

Raul

----
[Touch Pro, Fuze Android Development] TRNSLN:
Is this bad news? No hope more for Blackstone?
[Touch Pro, Fuze Android Development] EpicLulz221:
I'm also getting this result on my Raphael GSM. Yellowish things are blue and blueish things are yellow. Great work so far keep it up!