yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] EBonillaRosaly:
Hi Viruscrazy, First of all thanks for a great job!

I am using your newest updates without issues... It runs flawlessly on my Raph110/FUZE (screen icons orientation Ok, zoom Ok, focus Ok, colors Ok, capture pictures Ok).

Even the battery is lasting way longer than with the last 1253 build (or at least it is what I notice since I started to use your updates yesterday).

I have a question though, camera flash is not working for me (tried it with Auto, On, and Off settings in the camera application without success). Even added the original command to turn on led flash (echo 1 > /sys/class/htc_hw/flash) from the original FRX03 thread without success.

I do not find references on your camera test thread about the flash. Should it be working for Raph110/FUZE? Or, it is still an issue to be work on?

Again, thanks for your great job in getting things working for this project!
[Touch Pro, Fuze Android Development] viruscrazy:
Well, for the 5Mp picture, can you make a dmesg after the camera has crashed (the logcat tells me that an ioctl failed...which mean a kernel call fails...so I need the dmesg). Thank you.

For colors (light) problems, maybe you can try to play with white balance settings, it changes colors.
[Touch Pro, Fuze Android Development] viruscrazy:
Hi,

The flash is currently disabled in the board file (the GPIO control) but it should print some thing in the dmesg log...could you please, try to take some a picture with the flash on (at least in the settings) and make a dmesg log right after the picture was token ? That would show me if the flash routines gets called properly...then I can enable the flash GPIO.
[Touch Pro, Fuze Android Development] rpierce99:
I don't see anything in the 1/23 changelog for Rhodium (RHOD400 CDMA is what I'm running specifically) is there anything in there that I should update/test for? Also I noticed in the first post you mention more testing needed on CDMA Rhodiums, anything in particular that I should be trying and logging to help out with that?
[Touch Pro, Fuze Android Development] GoldAngelo:
Thanks, but it does not work. The system now hangs just after the entry into Emulator.

Reformat the card and try to do everything again from scratch.
[Touch Pro, Fuze Android Development] arrrghhh:
Just zoom, I don't think he needs any logs from RHOD - it all seems to work for us now, except for video record which he is aware of and AFAIK not looking at right now. I'm sure it'll get addressed when all the other devices get cleaned up & functional.
[Touch Pro, Fuze Android Development] R^7Z:
Commandcenter

I don't know if this works for all devices but this is what I was using and it is free to download and free to use (to my knowledge).

LINK (link to webpage)

Basically, it's an app that will run multiple commands such as the logcat and dumpmsg that have been requested for testing/debug purposes.
[Touch Pro, Fuze Android Development] djdafreund:
well, i wiill have to do some more testing to find out for sure which is causing thisn,but after both upgrading to frx04 and yesterdays camera library my battery drops to 0 in less then 5 minutes ( shows 96% after going back into wm),and wondered if camero's patches somehow got left out of the newest frx04 build. It wasnt doing this with both frx03 and camera stuff before yesterdays releases. I will have to make a seperate install of JUST frx03 again to test, then add frx04 stuff to narrow down if it's something frx04 is causing battery issues,or if its yesterdays new camera libraries thats causing this. Just thought i'd mention it here first before posting in the frx04 thread since i didnt notice this problem with frx04 and older camera libraries before yesterdays release. (battery levels were reporting normal for hours later, and afterr changing to yesterdays camera file releases it's doing this now)
[Touch Pro, Fuze Android Development] Eodun:
No problems with battery here with blackstone. Only mentioned weird small icons that I don't know when appeared.

I think this is the problem (dmesg after taking 5MP photo):

[ 2440.878631] adsp: module JPEGTASK: region (vaddr 41024000 len 4096) clashes with registered region (vaddr 41024000 paddr 26e12000 len 4096)
[ 2440.878753] adsp: module JPEGTASK: region (vaddr 41028000 len 4096) clashes with registered region (vaddr 41028000 paddr 26e13000 len 4096)
[ 2440.878967] adsp: not patching JPEGTASK, lookup (418eb000, 2529792) failed
[ 2440.878997] module JPEGTASK: verify failed.
[Touch Pro, Fuze Android Development] viruscrazy:
You're right....battery level is broken for all devices but diamond...That the patch I made for the diamond audio problem that breaks it...

I'm going to make a new kernel right now with this fixed...
[Touch Pro, Fuze Android Development] viruscrazy:
First post updated with new kernel+modules with battery level fixed for devices others than GSM diamond.
[Touch Pro, Fuze Android Development] djdafreund:
Thank for being so quick with responding and also repairing viruscrazy. Much appreciated. I did also notice smaller icon's in camera but far from a big deal.

I also noticed in landscape the icon's and such are correct, but in portrait position everything is upside down, but i BELIEVE it's because of a simple adjustment with a figure. Thought about this before, the default number's in the command line are something like "... = 2,1,3" when it should be a negative 1(default for the raph800 config file), which would make sense if it's flipping the sensor. I'm about to try it in a minute. But nothing having to do with camera i don't believe.
[Touch Pro, Fuze Android Development] InkPouchMan:
DIAM500

Updated to new libpack, same error on DIAM500. Logcat + dmesg attached.
[Touch Pro, Fuze Android Development] Eodun:
Hey, I think I started a confusion. The small icons are not the ones in the camera app, but all apps icons (in the menu and desktop). Don't know which change made that.

Edit: It seems it's a resolution change.
[Touch Pro, Fuze Android Development] shavenyaknz:
Hi viruscrazy,

Just tried the latest kernel+modules and library from the first post on my Topaz. It wouldn't boot so I can't get you a logcat or dmesg. After I start Haret, the top left corner of my screen has a black bar running halfway down and it's a few pixels wide. The device completely locks up and won't show up in adb.

My Topaz has a slightly different memory config. Around September last year mweirch pushed some changes to linux-msm. He found that there were two different memory configs, dual die and monodie.

http://gitorious.org/linux-on-qualc...mmit/76623cf6beb00173af38c6bc4ffc39c9280f7bd5

My device is a monodie one and it looks like it's having the same problem booting that we used to have.
[Touch Pro, Fuze Android Development] viruscrazy:
Thanks a lot. Could you please make the dmesg + logcat after the camera crash (I will need both files to find the relationship between kernel / userland that is bugging).

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

I'm going to have a look to the device memory configuration. I noticed about the monodie and tried to keep the same behavior as orginal configuration but I may have forgot something. The commit you mentionned is already in my kernel as I use it to test the monodie memory layout...I will have a look and make the changes for more tests.

For Diamond CDMA users with screen problem, can you confirm the camera kernel never worked for you ? If so, then I will have to make changes to the board file for the diamond CDMA variant.

Thanks
[Touch Pro, Fuze Android Development] Erikson89:
Topaz boots if you comment froyo.user.conf in the following way:

#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

Without that it didn't boot for me, too.

I will post the logs of the 5MP crash on Topaz in a few minutes.
[Touch Pro, Fuze Android Development] shavenyaknz:
I tried that too but had the same problem. Still no boot.
[Touch Pro, Fuze Android Development] viruscrazy:
Thanks for the tip.

I've made a fix also for the topaz monodie variant because I did not applied a memory offset to all the concerned memory regions. In a few seconds / minutes, the first post will be updated with a new file (suffixed _topaz_fix). This should fix the topaz monodie boot problem.

Jerome

Edit : Link has been updated.
[Touch Pro, Fuze Android Development] Erikson89:
Here are the logs after the camera crash. I hope this logcat is enough because the dmesg is quite larger. It only crashs at 5MP.
[Touch Pro, Fuze Android Development] shavenyaknz:
That new Kernel boots and I have the camera working for 3MP (except a few lines in the image). The preview looks like it has a few lines in it and the app crashes when I take a photo at 5MP. Very cool though. Have attached dmesg and logcat.
[Touch Pro, Fuze Android Development] knaveman:
I just spent the last two hours figuring out how to use ADB and get the logs for you. I hope I did it all right. Let me know if I did anything wrong. Just trying to help out. :D

Topaz210

FRX04 (froyo.user.conf lines commented out)

latest topaz package

Everything booted fine. Camera crashed after taking picture.
[Touch Pro, Fuze Android Development] spitzilla:
Using DIAM500 CDMA I have not been able to boot any of the available kernels linked in your first post, including the new ones created today. Same black screen during boot issue.

Seems as though its just the display thats not working, because the backlight remains on, just no picture. If I leave it for a while I can feel the vibration when I slide to unlock, as well as feel vibration when I click and hold on an icon.
[Touch Pro, Fuze Android Development] Eodun:
New kernel and modules working like a charm. I don't post more logs because there is no change.

If USB access becomes fully functional, I won't go back to WM EVER!

Thanks to all devs!
[Touch Pro, Fuze Android Development] viruscrazy:
Ok, so if you are ready for some tests, then I will have a look tomorrow to the cdma diamond camera driver in winmo and check if one of the gpio used in gsm variant is not clashing with a lcd gpio (as for raphael).

I will let you know tomorrow.

For topaz and blackstone with 5mp picture bug, I think I know where it comes from. I'm doing some tests on the userland camera side, but it seems like the memory allocated for preview is not freed and thus, when using the rest of the memory for snapshot, if we used 3mp resolution, ther's enough memory but if we use the 5mp, then there's not enough...I will make the memory allocation smarter, test that and post a libcamera.so updated in the first post.

Jerome
[Touch Pro, Fuze Android Development] viruscrazy:
Ok, Can some testers with 5mp sensors and snapshot bug test the new libcamera.so that I've attached to the first post ? This file should be placed in the lib_camera folder on the sdcard.

If you still have the bug, then please, make a dmesg + logcat log again. Good nigh and good luck !
[Touch Pro, Fuze Android Development] knaveman:
Topaz 210

5mp crashes the camera when I press the capture button. Before it froze after the capture sound effect.

Edit: 3mp crashes the camera too. Tried a fresh data.img and the same thing happens. Logs are from the 5mp crash.
[Touch Pro, Fuze Android Development] Erikson89:
Now Saving pictures doesn't work completely. (3MP and 5MP tested)

It doesn't hang up but crashs suddenly after pressing the button. (app has stopped unexpectedly) The camera app can be opened again.

Logs attached. (5MP)
[Touch Pro, Fuze Android Development] shavenyaknz:
Same here, logs attached also.
[Touch Pro, Fuze Android Development] djdafreund:
Hey viruscrazy, justed wanted to ask if any new updates today included the fix for battery meter going dead after 5-6 minutes? Just asking cause without that it's not usable currently,before its showing dead already.
[Touch Pro, Fuze Android Development] rpierce99:
Yeah i downloaded the new version a couple hours ago and my battery meter is fine on my RHOD400, from the sounds of it there was one issue that affected all non-diamonds, so it seems that was fixed with the last version, but if there are multiple issues the issue may still exist in non-rhods, can't say personally.
[Touch Pro, Fuze Android Development] tgkdubb:
yeah had this issue on Raph800
[Touch Pro, Fuze Android Development] djdafreund:
Just got home. Will grab the newest updates and try again to fix battery issues. Thanks for the the last few responses to confirm the most current update currently fixes the battery issues as of tonight/today. Thankx crazy!!! :)
[Touch Pro, Fuze Android Development] lorikitty:
updated to the latest zimage/libocam and zoom works fine. Colors are working correctly now (I had no red at one point, and no blue at another point). Grabbed this and frx04 and everything is working beautifully :)

viruscrazy -- thank you for giving us all cameras! :)
[Touch Pro, Fuze Android Development] viruscrazy:
Yes, I thought about it yesterday before sleeping and the mod I did were not at the right place. I will look at it today when I will have some spare time and post an updated libcamera.so....you can still use the one in the lib_package if you want to use the 3mp resolution till I've fixed the 5mp.

For battery fix, it's now included in all kernels I will do.

Sound fix was only for some diamond (and 5225 adsp) devices. For rhodium, if you have some problems with sound, either pm me (with all the details and the logs, situation when the sound bug, ...) or post this on the main xdandroid thread.

Jerome
[Touch Pro, Fuze Android Development] viruscrazy:
I've updated the first post with a new zImage only (attached in a zipped file). Can you please make the test with the libcamera.so that was provided in the lib_package (not the libcamera.so that was attached to the first post that broke the snapshot).

I found that the new library was doing some pmem clash (even on my device). It was requesting for an pmem operation that wasn't supported by our kernel. I've added it and I've nor more pmem clash messages now. But I can't test the 5mp resolution as I don't have the mt9p012 sensor.

The last libcamera broke both 3mp and 5mp on your devices because it was allocating too much memory in the same region...

Please, make a dmesg log if you still have the crash (logcat should not be required but if you can do it as well...). Dmesg log should be lighter than before as I removed the camera debug outputs (but left the ones I need for this bug).

Thanks, Jerome
[Touch Pro, Fuze Android Development] drhadidy:
just made the update... all working great and the camera working fine with the zoom and all...

great work people...

just a little question here... donno if its the right place to ask but im using this kernel now.

my data connection is not working anymore!!!!

i checked the data connection tab as i used to do before and i dont see the icon in the notification bar... and connection is not working!!

is there anything else to do???
[Touch Pro, Fuze Android Development] neo_zycho:
same here, i updated the zimage attached in the first post. and now the when i turn on wifi, it says error.

I reverted back to my last zimage and wifi is now working again.
[Touch Pro, Fuze Android Development] marek1:
The 3Mpix pictures works on TOPAZ [ HTC Diamond 2].

Thanks.
[Touch Pro, Fuze Android Development] Erikson89:
3MP always(with jeromes kernel/libs) worked. The problem was the 5MP mode.

I will test it later.
[Touch Pro, Fuze Android Development] xrshwy:
which button do you used take a picture, i can see the image show but slowly and shot no work at all.
[Touch Pro, Fuze Android Development] Stickman89:
Battery depleting within a couple of hours on my blackstone, will pull some logs tonight for you to gander at :P

Appreciate the time and dedication put into this, thankyou.

Best Regards,

ST1Cl<^^aN
[Touch Pro, Fuze Android Development] Eodun:
Assuming Blackstone has 5225 adsp, because it was solved too.

I've had this problem with all XDAndroid builds, I think I have to configure something I'm missing...
[Touch Pro, Fuze Android Development] mikelord:
Work but video crash !

Camera work fine in 3mp and 5mp , but when video is switch camera is crash..

thansk !!!
[Touch Pro, Fuze Android Development] welard:
5mp takes snapshot but crashes shortley after with the new zimage...........is there anyone else having this prob on there blackstone???.........mikelord what handset are you using?
[Touch Pro, Fuze Android Development] Stickman89:
yup same for me, I managed to get one shot with the previous kernel and ever since then camera freezes.
[Touch Pro, Fuze Android Development] R^7Z:
Quick blurb

I don't know if there would be any differencences between FRX03 and FRX04 as far as logcat or demsg goes but perhaps it might be a good idea to mention which one. I'm not really expecting much discussion about this, just want to add it for future reference since the main thread is now reflecting the update. I recall the earlier discussion about which version thread OP was using. As always thanks for the outstanding support, you guys rock!

:cool:

n-Joie! (Enjoy)
[Touch Pro, Fuze Android Development] viruscrazy:
The modules need to be recompiled to work with the new kernel. I'm not on the computer where I can do the kernel and modules like the previous packets. I will do that tonight or when I will have some spare time. The kernel I posted this morning was for 5mp bug fix attemps.

Jerome
[Touch Pro, Fuze Android Development] Spige:
Blackstone

Everything exept speaker phone is ok,
[Touch Pro, Fuze Android Development] xtremetactics:
Using Frx04, working fine on my rhod400 sprint. One thing I have noticed, Zoom works in the display, but when u actually take a picture while zoomed the picture actually comes out as if you weren't. Has anyone else noticed that? I don't mind the slightest though cause you've given me a camera and this is by far the most stable build I have used. Buh bye WinMo
[Touch Pro, Fuze Android Development] Erikson89:
Do I ever need to make a fresh install? Here are logs of the "old" install with the new kernel. 5MP mode crashes on Topaz again. 3 MP works.

Logs attached.
[Touch Pro, Fuze Android Development] viruscrazy:
Thanks for your logs. I will make some changes tomorrow to add more outputs. I don't see where does it comes from. Seems like a memory problem but might be in the library.

Jerome
[Touch Pro, Fuze Android Development] welard:
5mp bug fix attemps not working on blackstone...............
[Touch Pro, Fuze Android Development] poleshuka:
new zImage camera on BlackStone

using FRX04+1253 on BlackStone, Camera is working fine in 3mb like magic ! speaker phone is might be better and of course known problem with WiFI, but must regard that data connection is working stable

thank you a lot.

:o
[Touch Pro, Fuze Android Development] arrrghhh:
Just to clear things up, you can't be using 1253 AND this kernel. One or the other ;).
[Touch Pro, Fuze Android Development] kruijs:
Confirming the functioning of 3Mps, crashing of 5Mps on Blackstone.

But also adding new observation (maybe already known?)

I was enjoying several hours of stutter-free (yeah!!!) music listening, and noticed that battery indication did not reduce during listening. (?!)

Directly after stopping the music player, battery went rapidly down in "several percent" steps to ~50%, at which point it stabilized. (OSMonitor was used for checking charge level)

Can somebody please confirm/deny this issue, is it maybe limited to Blackstone?

Anyway, continuing music play now, curious how long it lasts :)

If I get 6 hours of continuous music playback, that may seem fair, so no "fast drain", it seems just a "stuck dial"!

(Note: I saw other battery issues in this thread, but my Blackstone did not seem to suffer from fast battery drain, nor "dead within 5 minutes" issues, just this strange "stopped battery indication during playback")

Cheers,

Robbert

---

Blackstone @ 690MhZ, XDANDROID 2.2.1 AOSP FRX04, viruscrazy camera test kernel
[Touch Pro, Fuze Android Development] skimike02:
Location of Pictures

So I have the camera working, but where does it store the pictures? Using astro file manager, I see a new folder in /sdcard/dcim called 100andro, but no files in it. Not sure if it is not writing the files or if I just can't find them.

Rhod 210 | FRX 04 and rootfs | 1/23 kernel, library, etc
[Touch Pro, Fuze Android Development] arrrghhh:
Mine went into almost the same folder - instead of 100andro, there's a "Camera" folder - that's where my pics went.
[Touch Pro, Fuze Android Development] Eodun:
Didn't try it yet, but perhaps viruscrazy solved the stuttering by stopping battery updates while playing music.

Try to start listening, plug it to USB (once to AC, once to comp) and see if it charges.
[Touch Pro, Fuze Android Development] funkys:
I had similar behavior on my phone after the stuttering bug fix. But after format and fresh install of FRX04 and Viruscrazy kernel it was gone.

best regards
[Touch Pro, Fuze Android Development] Eodun:
Haha! ADB working, finally lol

I'll have some time for debug tomorrow. Give me some work! ;)
[Touch Pro, Fuze Android Development] skimike02:
[/QUOTE]

Running the camera for me creates folder "100andro," running video camera (with FC) creates folder "camera." But when I try to take a picture, it makes the shutter sound and the image freezes like it took a picture, but then the whole camera program freezes and I have to hit end key to get out. First time with ADB, logcat, etc. Please let me know if I need to do it differently. Thanks

Rhod210, FRX04, 1/21 rootfs, 1/23 kernel and zImage, dream lib

UPDATE: Got it working. Had to switch back to the legend library it seems. Thank you much devs. This thing is working great!
[Touch Pro, Fuze Android Development] xUmaRix:
i wonder if anyone use the kernel from 23/1 for topaz had sdcard issues

[ 297.531829] microp-klt: Setting lcd-backlight brightness to: 0x30
[ 310.770812] init: untracked pid 2071 exited
[ 1025.328552] msmfb_start_dma 30.000 ms after vsync request
[ 1568.087066] init: untracked pid 2902 exited
[ 2033.193908] mmc1: Command timeout
[ 2033.198974] mmc1: Command timeout
[ 2033.203979] mmc1: Command timeout
[ 2033.209014] mmc1: Command timeout
[ 2033.214019] mmc1: Command timeout
[ 2033.219024] mmc1: Command timeout
[ 2033.228057] mmcblk0: error -110 requesting status
[ 2033.228210] mmc1: Data timeout
[ 2033.228271] end_request: I/O error, dev mmcblk0, sector 2060032
[ 2033.228302] Buffer I/O error on device mmcblk0p1, logical block 2051840
[ 2033.228332] lost page write due to I/O error on mmcblk0p1
[ 2036.749664] mmc1: Data CRC error
[ 2036.749725] msmsdcc_data_err: opcode 0x00000011
[ 2036.749755] msmsdcc_data_err: blksz 512, blocks 1
[ 2036.749847] mmcblk0: error -84 transferring data
[ 2036.749877] end_request: I/O error, dev mmcblk0, sector 12846
[ 2036.754272] FAT: FAT read failed (blocknr 4654)

zImage pmem fix dbg dosen't have this error.(Linux version 2.6.27.46-01223-g44f1e2b-dirty (Jerome@Linux-Jerome) )

[ 0.278778] PCB XC: 00000003
[ 0.278808] AMSS version: 52.69.25.37U
[ 0.279388] msm_add_mem_devices: register pmem_device @0x24e00000, size 0x02000000
[ 0.279602] msm_add_mem_devices: register pmem_adsp @0x26e00000, size 0x00800000
[ 0.279785] msm_add_mem_devices: register pmem_gpu0 @0x00100000, size 0x00700000
[ 0.279968] msm_add_mem_devices: register pmem_gpu1 @0x16b00000, size 0x00800000
[ 0.280273] msm_add_mem_devices: hw3d_device smi @0x00100000, size 0x006fffff
[ 0.280364] msm_add_mem_devices: hw3d_device ebi @0x16b00000, size 0x007fffff
[ 0.280578] msm_add_mem_devices: register pmem_camera @0x27600000, size 0x00800000
[ 0.280761] msm_add_mem_devices: register ram_console @0x008e0000, size 0x008fffff
[i]----------------------------------snip------------------------------------------------------[/i]
[ 1.691070] hw3d_probe: hw3d_device regs @0xa0000000, size 0x000fffff
[ 1.691192] hw3d_probe: hw3d_device smi @0x00100000, size 0x00000000
[ 1.691253] hw3d_probe: hw3d_device ebi @0x16b00000, size 0x00000000