yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] SnakeManJayd:
I had a similar thing on my touch pro. I deleted the data.img so it created a new one on boot and it seemed to fix it. Now I have sound when recording video. It's a bit annoying as you have to backup and reinstall everything, but it worked for me.
[Touch Pro, Fuze Android Development] dsfreak0109:
I tried to use the camera mod with Jerome's Kernel and it worked for Froyo with the config modded but when I try to do the same thing with the gingerbread build with modified gingerbread.user.config the command line gets to android but it keeps repeating request_suspend_state: wakeup (3->0)

request_suspend_state: wakeup (0->0)

request_suspend_state: wakeup (0->0)

this line and prevents xdandroid from booting. Im using an HTC PURE

Also when I get rid of the config edits it boots fine

my config file is

# General parameters

general{

renice=1	# Run the renice script to inprove call answering

}

#compcache related parameters

compcache{

compcache_en=1	# enable(1) or disable(0)20 compcache

cc_disksize=100	# Ram swap disksize - any number between 1 to 98 should work; default is 1/4 of the RAM (24)

cc_memlimit=64	# Limit the memory usage for backing swap (cc .5x known issue-defaults to 15% of total RAM)

cc_backingswap_en=0	# enable(1) or disable(0) backing swap

cc_backingswap=/dev/block/mmcblk0p4 # pointing to the backingswap partition device, swap

}

#create swap file for compcache or linux swap

swap_file{

swap_file_en=0	# set to 1 to create swap file

# set to 0 to del the swap file

linux_swap_file_size=32	# swap file size in MB

linux_swap_file=/sdcard/swapfile	# pointing to the swap file location ( must be /system/sd/)

}

#Linux swap parameters

#

# linux swap can only be enabled if cc_backingswap_en is set to "0"

#

linux_swap{

linux_swap_en=0	# enable(1) or disable(0) linux swap

linux_swap_partition=/dev/block/mmcblk0p4 # swap partition device

}

#virtual memory

sys_vm{

sys_vm_en=1	# enable(1) or disable(0) virtual memory configurations

swappiness=0	# default 60

page_cluster=0	# default 3, (0 since CM3.9.6+)

laptop_mode=5	# default 0

dirty_expire_centisecs=3000	# default 3000

dirty_writeback_centisecs=1500	# default 500

dirty_background_ratio=3	# default 5

dirty_ratio=5	# default 10

vfs_cache_pressure=200	# default 100 (tendency of the kernel to reclaim cache memory)

overcommit_memory=1 # default 0 (0=Heuristic 1=Always overcommit 2=Don't overcommit)

overcommit_ratio=80 # default 50 (% of Physical+Virtual memory to allow allocation)

}

# custom shell commands, these commands run last

custom_shells{

chmod 777 /etc/dbus.conf

echo 2 > /sys/devices/platform/msm_hsusb/usb_function_switch

rm -f /sdcard/*.rec

#mount --bind /sdcard/lib_camera/libc.so /system/lib/libc.so

mount --bind /sdcard/lib_camera/libcamera.so /system/lib/libcamera.so

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

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

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

#

# comment the line above and uncomment the line bellow if the camera fails to work.

#

#mount --bind /sdcard/lib_camera/liboemcamera.so.dream /system/lib/liboemcamera.so

#echo "Hello!!!" # example

#echo "You can create your own commands here" # example

}
[Touch Pro, Fuze Android Development] Eodun:
Camera is still not working with Gb. It's known. Just wait for now.
[Touch Pro, Fuze Android Development] wmg316:
3/1 Kernel with 3/1 FRX05 ext2

Arrrghhh recommended camera / video problems be discussed here...so...

My results:

Running 'FRX04 Reference' with new 3/1/11 Kernel from the 'WisTilt2' kernels thread and with new 3/1/11 FRX05 system.ext2; no other changes

running latest 2/24 rootfs

no changes made to user.conf

no addition of lib_camera folder from the camera development thread

Camera works - took 2 pics

Video works - shot 2 vids ... but ... no sound.

"instawake" and "instasleep" working great.

Any suggestions to get sound with video? I have seen successful sound posted for RHOD400...but not for Tilt 2 (RHOD300)??

EDIT:

I tried starting from scratch. I ran same settings as above (new kernel; new system.ext2), but I started clean and created new data image with the new 3/1/11 Kernel.

Same results...no sound with video.
[Touch Pro, Fuze Android Development] tiad8:
did you try my GB. camera works really good

http://xdaforums.com/showthread.php?t=976285

you just need virus's kernels. thank you virus for that.

thanks
[Touch Pro, Fuze Android Development] arrrghhh:
Cam code has been committed to the mainline kernel... so as much as we all should appreciate viruscrazy's work, we do not need to run his kernels any longer to get cam to work...
[Touch Pro, Fuze Android Development] tiad8:
oh. that's a great news. thank you
[Touch Pro, Fuze Android Development] dsfreak0109:
Do you have the link to the Kernel commit for the cam?
[Touch Pro, Fuze Android Development] dsfreak0109:
Original Kernel works for my Topaz but the camera kernel causes my device to restart on boot
[Touch Pro, Fuze Android Development] shatred:
so, we found out back in the rhodium forum that this cam code viruscrazy made is not working for people with an rhod100 with an AUO panel, the one's with an EID panel have no problem but its the AUO that gives trouble.

this is how snalbansed described the problem:

I have an AUO panel rhod 100, and the default camera app at most shows me an initial image, then doesn't update after that. The buttons still respond though but they dont do anything. With some of the apps off the market, it behaves a little better (the screen refreshes about 2-3 secs then it freeze's), though I'm still yet to take an image :(

so yeah i agree with his statement, the camera code is not working correctly for us rhodium100 owners with an AUO panel.

i am willing to test every thing viruscrazy releases here (at least if he wants to work on this) and i am also willing to give every log he needs. (if there is more needed just tell me).
[Touch Pro, Fuze Android Development] viruscrazy:
Can you please send me the CIF.dll file and DISPTOOLS.dll files from your rhodium winmo ? Also, please make a dmesg log of the camera startup so that I can see the gpios involved on your phone.

Regards, Jerome
[Touch Pro, Fuze Android Development] shatred:
with wich kernel should i do that?
[Touch Pro, Fuze Android Development] arrrghhh:
Doesn't matter, but newest from autobuild would probably be preferred.
[Touch Pro, Fuze Android Development] shatred:
yeah so i kinda dont know how to get those dll's :O is there an tut on it anywhere? (already tried seraching for it)
[Touch Pro, Fuze Android Development] arrrghhh:
At least get him the logs..

The dll's would be pulled from your phone, or preferably the stock carrier ROM for that device.
[Touch Pro, Fuze Android Development] Eodun:
Don't you find them in the Windows dir from your device? Ofc, loading WM and searching for them in the file explorer.
[Touch Pro, Fuze Android Development] shatred:
dam this was hard for me to do, but i managed it haha. here you go, in the dmesg you can find the camera startup in the last part of it.

View attachment log+dll's.rar
[Touch Pro, Fuze Android Development] shatred:
I dont have the dll's for the stock rom cause i flashed i with energy ;o
[Touch Pro, Fuze Android Development] arrrghhh:
Your carrier still has a stock ROM for the phone no? You can extract them from the ROM itself.

Hopefully the dll's you provided are useful...

Your logs look like you had a ton of uptime...

Not sure if they'll be useful or not. Best would be to boot, try to use cam, pull logs. This way the only thing that is in your logs is the boot process, and the cam usage attempt. I'm not the best at deciphering what is in the logs, jb is obviously a lot better - however the method above will make it much, much easier to figure out what's going on...
[Touch Pro, Fuze Android Development] shatred:
tried to redo it, getting crazy of the retarted standart keyboard layout where i can't type > or < in the terminal. (forgot to use f22's rootfs) when are those 2 finnaly getting combined?

here is itView attachment dmesg.rar
[Touch Pro, Fuze Android Development] arrrghhh:
Whenever F22 finishes it and commits it...?

adb works wonders, you don't have to type any of the mess on your phone. Just do the deed, connect to USB and pull logs. So much easier, especially if you're going to continue to help by pulling logs ;).
[Touch Pro, Fuze Android Development] shatred:
updated previous post*
[Touch Pro, Fuze Android Development] CeasarRAPH100:
Got it to work now used the "froyo.user.conf" settings then it loaded and camera app started up.

But I also got the reversed upside down picture.

Attached some pic:s., in landscape the menus seems to be correct, in portait menus are reversed.
[Touch Pro, Fuze Android Development] moharu:
wow it works

would it work on other htcs
[Touch Pro, Fuze Android Development] funkys:
Viruscrazy, you are doing great job. With your last zimage my Diam100 performs as smooth as baby ass:D Everything works perfect -memory, panel, camera...

best regards
[Touch Pro, Fuze Android Development] pdawg17:
So is it updated for rhodium yet? I have a rhod400 and would love to try this but I'm not sure if the 1st post is updated for rhodium...and when it is available would it only be for GSM or will it not matter?
[Touch Pro, Fuze Android Development] Captain_Throwback:
Testing new image now on my Fuze - the Camera isn't completely reversed: when I move the device up, the picture on the screen does move up, but when I move the device left, the picture on the device moves right. Also, pressing Menu while in Portrait orientation brings up the Landscape Menu (from left side of screen). Screenshot of the viewfinder display attached. Taking pictures works fine, and I can view them as well. dmesg log will be attached shortly. I'm thinking that the orientation issue might have something to do with how the gsensor is set in the startup.txt?
[Touch Pro, Fuze Android Development] viruscrazy:
Thanks everybody for your tests and screen shots...now I can see what's the reversed picture problem (but I can't yet solve it). I think that's something in camera driver but have to confirm that (maybe a hidden setting or a hardware parameter that is not yet set).

About rhodium, the latest zImage does not contains required code for it to work, but as soon as I can do it with the help of bzo, then I will put it inside the kernel and change the thread title.

For the blackstone users, I might have a bad news. I've checked again the liboemcamera.so (which contains most of the camera parameters for sensor config), and it seems it does not support the 5MP sensor (I was introduced in error because one string in the liboemcamera is "mt9p012...blablabla", but when I look to the configuration process, only mt9t013 and an sk5xxxx sensor are supported...). Anyway, if Alex (working on Xperia) confirm that it's "own" camera driver is working with this liboemcamera, then we will probably be able to make a patch for the blackstone camera driver.

I will try to look for raphael camera reversed picture and post a new kernel when I will have found something new.

Thanks everybody.
[Touch Pro, Fuze Android Development] xUmaRix:
Yep it is true.With your latest kernel i got blank screen when running camera.logcat didn't show any QualcommHardware stuff.

<7>[ 852.932037] clock-regime: Setting internal clock for VFE_CLK
<4>[ 852.932128] clk_regime_is_on: 96 is 1
<7>[ 853.330688] clock-regime: Setting external clock for VFE_CLK
<4>[ 853.330749] clk_regime_is_on: 96 is 1
<6>[ 853.798889] msm_camera: mt9p012_sensor_init(): reseting sensor.
<6>[ 854.073852] msm_camera: mt9p012_sensor_init(): enabling parallel interface
.
<6>[ 860.830535] msm_camera: mt9p012_sensor_open_init(): enabling output.
<6>[ 860.850372] msm_camera: msm_open_common: rc 0
<6>[ 860.850402] msm_camera: msm_open_control: rc 0
<6>[ 860.860748] >>>>>>>>(2010-12-28 09:03:40.070000000 UTC)<<<<<<<
<6>[ 860.860778] msm_open_common: open config0
<6>[ 860.860809] msm_camera: msm_open_common: rc 0
<6>[ 860.861267] msm_camera: msm_ioctl_config: cmd 1
<6>[ 860.861328] msm_camera: msm_get_sensor_info: sensor_name mt9p012
<6>[ 860.861358] msm_camera: msm_ioctl_config: cmd 1 DONE
<6>[ 861.052459] msm_release_config: config0
<6>[ 861.052520] __msm_release:sync->opencnt:2
<6>[ 861.052551] release config atomic_set pmsm->opened as 0
[Touch Pro, Fuze Android Development] Corias:
RAPH100: Image is still upside down (but not reversed, and never was)
[Touch Pro, Fuze Android Development] CeasarRAPH100:
It even seems taken pictures in portrait mode comes out correct,in portrait only preview is upsidedown.

But in landscape I get also taken pictures and preview upsidedown.
[Touch Pro, Fuze Android Development] xUmaRix:
mt9p012.c.Seems like Sensor mt9p012 (BAYER 5M) is not in liboemcamera.so.Perhaps we need a different liboemcamera.so for blac100.i tried another liboemcamera.so that have mt9p012 but unfortunately it is for 320x240 resolution and it wont work

/sdcard # strings liboemcamera.so | grep mt9p
strings liboemcamera.so | grep mt9p
mt9p012_process_start
mt9p012_register_to_real_gain
mt9p012_set_lens_shading_correction
mt9p012
mt9p012 failed %d
/sdcard #
/sdcard # strings /system/lib/liboemcamera.so | grep mt9p
strings /system/lib/liboemcamera.so | grep mt9p
mt9p012 failed %d
/sdcard #

/sdcard/dream_libs # strings liboemcamera.so | grep mt9p012
strings liboemcamera.so | grep mt9p012
mt9p012 failed %d
[i]----------------------------snip----------------------------------[/i]
/sdcard/dream_libs # strings liboemcamera.so | grep mt9t013
strings liboemcamera.so | grep mt9t013
mt9t013_process_start
mt9t013_reg_pat
mt9t013
mt9t013_process_start
mt9t013 failed %d
FAILED mt9t013_write_exposure_gain3
FAILED mt9t013_write_exposure_gain4
FAILED mt9t013_write_exposure_gain1
FAILED mt9t013_write_exposure_gain2

kernel is working fine.i can see mt9p012 is initialize.

[ 2.195007] msm_camera: mt9p012_sensor_init(): reseting sensor.
[ 2.263732] msm_camera: mt9p012_sensor_init(): enabling parallel interface.
[ 2.331268] msm_camera: drivers/media/video/msm/mt9p012_fox.c mt9p012_sensor_probe:1306
[ 2.391937] msm_gpio_set_function(0, 40)
[ 2.392120] msm_gpio_set_function(1, 40)
[ 2.392242] msm_gpio_set_function(2, 40)
[ 2.392395] msm_gpio_set_function(3, 40)
[ 2.392517] msm_gpio_set_function(4, 40)
[ 2.392639] msm_gpio_set_function(5, 40)
[ 2.392761] msm_gpio_set_function(6, 40)
[ 2.392852] msm_gpio_set_function(7, 40)
[ 2.392974] msm_gpio_set_function(8, 40)
[ 2.393096] msm_gpio_set_function(9, 40)
[ 2.398498] msm_gpio_set_function(c, 40)
[ 2.403717] msm_gpio_set_function(d, 40)
[ 2.408905] msm_gpio_set_function(e, 40)
[ 2.414062] msm_gpio_set_function(f, 40)
[ 2.419311] msm_camera: msm_sync_init: initialized mt9p012
[ 2.429748] msm_camera: msm_camera_drv_start: setting camera node 0
[Touch Pro, Fuze Android Development] Thegn:
Good find! Hopefully your discoveries will help devs make camera working on Blackstone! :-)
[Touch Pro, Fuze Android Development] fshami:
Dears,

I have a DIAM100. Can i get the camera working by ONLY copying the Module & zImage? or i have to make the lib update as well?
[Touch Pro, Fuze Android Development] xUmaRix:
yes u can.why dont you try it for yourself
[Touch Pro, Fuze Android Development] Corias:
1. Copy modules, zImage and libraries.

2. Boot your device to Android

3. Connect to PC

4. Using ADB on PC (run "<%path to adb%>\adb.exe shell") , navigate to your lib_pack (generally, "cd sdcard/andboot/lib_pack" is enough)

5. Execute "./lib_inst.sh" from there

6. Reboot phone
[Touch Pro, Fuze Android Development] funkys:
Or you can skip steps 3 to 6 and copy the files using programs like Rootexplorer. Like I did. Because I don't have connection with my DIAM100 and my computer when using Android. And executing the script lib_inst.sh doesn't help either.

best regards
[Touch Pro, Fuze Android Development] xUmaRix:
anyone experience system_server consume all the processor till 98% ?.I need to crash the system_server to make android responsive
[Touch Pro, Fuze Android Development] Younio:
I allways tried to run script with adb shell. the system always booted but camera newer worked for me. (got sometimes runing scuares :D, and usualy black screen). But after just copyng files to the directories named in the script I got flickering screen with a lot of colours, but mostly green. This is what I got after trying to lounch a camera and take a photo (see attachment).

Strange that everyone on diamond seems to have cameras working, except me :D

BTW: I used the first version that viruscrazy posted:

EDIT: Tried both newer modules and zimages but still only green flickering screen, but it corresponds to zoom : D.

So probably this is because I'm using older release (Eclair 2.1)

------

My Device: DIAM100 [HTC Touch Diamond]

ROM: Energy.DIAMOND.21916.Sense2.5.Cookie.2.0.Dec.21

+VaniljEclair V1.6 - CyanogenMod 5.0.8 releases (searching for the 1 to stay with)

RADIO: Diamond_1.17.25.09.diamimg

HSPL: Diamond_OliNex_1.93_Unsigned
[Touch Pro, Fuze Android Development] viruscrazy:
Raphael users : There's an updated package on first post of this thread with potential "mirror" fix (well, I really hope this will fix it ! don't want to spend more time on disassembling the camera DLL :p...) . It also adds support for flashlight but don't know if it will work neither how to use it under android.

Rhodium users : the latest image add supports for your devices, based on the work of bzo. It seems there's a problem with memory when he used my tree, so if you can't boot the image, then PM me and I will prepare an special image with debug outputs to gather datas on your phones (memory configuration).

Regards, Jerome
[Touch Pro, Fuze Android Development] Captain_Throwback:
So far I'm not having success with the new zImage & modules.

On my RAPH110, when I start haret.exe, I get half a page of code and then the screen blacks out, and I have to reset.

On my RHOD300, Android starts fine, but when I try to open up the Camera app, my phone completely reboots (after trying to open for some time). I just tried to back out of the Camera app before it completely crashed on me, which seemed to work for a few seconds, but then the device rebooted on me anyway. EDIT: Just tried it again using a fresh data.img, and this time I actually got a Force Close message prior to my phone rebooting. But, it still rebooted :(.

In both cases, I'm using the same lib_pack as previously (12/22, Diamond), mounted via the froyo.user.conf file.
[Touch Pro, Fuze Android Development] arrrghhh:
Awesome, thanks. Hopefully jb can find something useful in these logs and have something for you AUO panel folk to test!
[Touch Pro, Fuze Android Development] tomdeaap:
Here is another dmesg from an AUO: rebooted, let it sit for 2 minutes (it was working on something) and tried to take picture, the output the dmesg.

I could press the take-picture-button, and it lit up, but nothing happened, cannot swith to camcorder. Also the image sometimes get cut up in squares and becomes blue-ish. Sometimes it actually reboots to WinMo as soon as I access the camera app.

Hope you can find what the issue is!

Btw, I also have a cooked rom, but will try to find the original one if you'd like.
[Touch Pro, Fuze Android Development] tomdeaap:
I pulled the dlls from the official stock ROM for the Dutch TP2, see attached rar.
[Touch Pro, Fuze Android Development] shatred:
awesome thnx for these, i did not know how to get the stock rom back again since i flashed mine with energy rom >.<
[Touch Pro, Fuze Android Development] shatred:
uhm, viruscrazy.. can you maybe give us an heads up on the progress with the auo panel probs + camera? anything i can help with testing?
[Touch Pro, Fuze Android Development] arrrghhh:
I'd be curious as well...

However, jb is swamped with BT now. Hopefully he can get some time to look at it.

Also, jb - have you noticed the color bug with video record? Bug 116 on the tracker addresses this issue. Clearly, in the video it appears that colors are flipped, I assume similarly to the issue on RAPH devices where their colors were flipped with pics.

Thanks again for all your hard work man!
[Touch Pro, Fuze Android Development] viruscrazy:
Hi there...I'm sorry, I've not been there since a lot of time now. I've indeed stopped playing with camera, maybe a little bit too soon, but I was kind of fed up with that and I needed to see some new things...

I will have a look to the panel problem your experiencing and I might need some details if everything is not already present in the posts. For the video colors, I will alos have a look at that. What devices are concerned ? All devices or only rhodiums ?

Jerome
[Touch Pro, Fuze Android Development] arrrghhh:
Seems to be only RHOD, but I'm not positive - I kinda have a skewed view of things as I am RHOD myself.

Let me know if you need more info. The busted camera seems limited not just to the RHOD100 folk, but specifically RHOD100's with the AUO panel.

The video recording color issue was reported by a RHOD user, but it may be more phones.

I understand man, you're doing this all for free - we all appreciate your help, let us know if there's anything we can do to help you debug!
[Touch Pro, Fuze Android Development] wmg316:
I would like to add for RHOD300 (Tilt 2) that the camera app is working good for me.

The video app is taking video, but there is no sound.

Hope this is helpful.
[Touch Pro, Fuze Android Development] shavenyaknz:
I'm seeing the same thing on Topaz too. Also the Topaz camera in general seems to have about 3 lines running horizontally across the screen (usually Red).
[Touch Pro, Fuze Android Development] The_Font:
If i try the cam, I used to get just the initial picture like mentioned here several times before. Now I tried to test it with the latest wistilt2 kernel. I get a camera tool with a black picture. If i try to switch from cam to vidio the application stops and my main screen shows again but its in landscape. Opening and closing the keyboard does not let it switch back to portraid mode. In the dropbox there are no files to be found from the time I did this experiment.

Tested cam with Updated 3/30/11 New Kernel (Wistilt2), Rhod100, AUO, FXR05 package.

Can I do some other experiments to create more logging?
[Touch Pro, Fuze Android Development] R^7Z:
disregard this message
[Touch Pro, Fuze Android Development] arrrghhh:
Why would you come in here and talk about a kernel meant for testing that has nothing to do with camera or this thread?

You are obviously missing the point, and it's honestly a shame that you found that testing kernel thread - because I don't think you've provided any feedback on that kernel in that thread.

If it works on the autobuild kernels, STFU. WisTilt2's kernels are meant for testing specific elements, none of which include the camera. Please, let's try to keep this thread on-topic! If you're testing something different, don't post about it elsewhere in other words!!
[Touch Pro, Fuze Android Development] The_Font:
Sorry man, I am fairly new to this and I am looking at 2 different threads. One for the cam and one with the experimental kernel. I like what is going on with the experimental kernel and I am just testing the new one and was going to post a positive reply but this is not the thread for that. Just a guy here who likes to help people to get a working stable kernel for the htc. My compliments for what has happend so far.

So another try,

Can I do anything here to help people to get logging for the cam. I have a rhod100 with AUO panel?
[Touch Pro, Fuze Android Development] arrrghhh:
Run kernel 1276 from the autobuild site, try to use the cam, pull a dmesg and logcat. Attach them here.
[Touch Pro, Fuze Android Development] The_Font:
Requested camtest logging

Hi,

I tested the cam with the requested kernel. I used the distrubuted FRX06 for this test. I hope this logging is usefull. If needed I can do some more tests. This logging contains dmesg and catlog before and after I tested the cam.