yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] viruscrazy:
First post is beeing updated in a few minutes with a new zImage as an attached zipped file. It will print me some usefull debug messages for the 5mp crash. Can you please make a dmesg log after a succesfull 3mp picture then after the 5mp crash. Thanks a lot.

For the other issues :

- Audio stuttering fix indeed disable battery level readings during music play. I might try to improve it to make it read once every minutes or so, to try to keep and up-to-date battery level, but you might experience a small stuttering as with the previous kernels (well, not the big stuttering, but some stuttering as in the kernel that were made a few month ago, before battery fix).

- Problem on topaz sdcard...Does anyone else have it ? I don't have it neither on the diamond or the rhodium.

- VIDEO DOESN'T WORK YET AND MIGHT NEED SOME ADJUSTEMENT BUT IT'S NOT GOING TO BE DONE NOW, DON'T TRY TO USE IT ! IF I CAN MAKE IT WORK, THERE WILL BE AN UPDATE TO SAY IT WORKS...

thanks for your tests.
[Touch Pro, Fuze Android Development] neo_zycho:
@viruscrazy,

when i used your last zimage, the camera works until i take a picture the phone freeze, also the wifi never works so re verted to my old zimage. hope you can fix it. thanks, mine is blackstone htc
[Touch Pro, Fuze Android Development] g3rm0:
Please post logcat and dmesg to help viruscrazy find the cause of your issues. Otherwise you're not too helpful by only saying that some things work and others don't. Also this kernel is intended to test camera so other stuff like wifi might not work as they are not a part of this test.
[Touch Pro, Fuze Android Development] neo_zycho:
understood. thanks
[Touch Pro, Fuze Android Development] Eodun:
Last kernel (the one with the +msg) refuses to boot in my blackstone. Last dmesg says "clock-regime-amss: msm_clk_regime_sec_ vfe_set_rate : Frequency was set to 24000000 Hz"

Too much oc perhaps?

Edit: Yeah, too much OC. It blocks with 690 but runs at 650. Tested and crashes everything after taking 3mp. Will post dmesg after reboot.

Edit2: Cant' save dmesg. It completly freezes system (even HW keys) and adb isn't working. Here is startup dmesg, don't think it serves any purpose though.
[Touch Pro, Fuze Android Development] Erikson89:
Here are the dmesg logs.

Dmesg.rar is after 3Mp picture and dmesg crash.rar after the 5MP application crash. (system is very slow after this crash, tooks me several minutes to make this log)
[Touch Pro, Fuze Android Development] lorikitty:
speakerphone doesn't work

the last time there was a during-call audio issue, it was fixed with a zimage. Is anyone else having trouble with speakerphone? For me it will appear to toggle on or off, however the phone will not revert to speakerphone. This is frustrating since I can't use hands-free (no bluetooth audio) and if I'm caught with a phone against my ear while driving I'll get a few hundred dollars in fines.
[Touch Pro, Fuze Android Development] viruscrazy:
Thanks...looks like the dmesg log is not beeing usable as I did a mistake in it...I will do another kernel tomorrow, test it on my two devices and post it for more tests...sorry for the multiples tests...

Jerome
[Touch Pro, Fuze Android Development] arrrghhh:
Can we please focus on camera testing in this thread? We can sort out issues like this in the main kernels. The focus of this kernel is for cam testing - nothing else. Not wifi, not speakerphone. Camera. Thanks.
[Touch Pro, Fuze Android Development] lorikitty:
I didn't realize speakerphone was an issue on all the zimages -- sorry! I thought it was only for this camera one.
[Touch Pro, Fuze Android Development] arrrghhh:
Even if it is only in this kernel (zImage), don't worry about it!

That's what I'm saying - this kernel is for testing camera. Jerome did happen to fix that sound stutter bug (at the cost of battery status updates...) but that was actually related to a commit he made a while back with camro.

So let's focus on the issues with camera. Let's worry about other random issues with the main GIT kernels in another thread - this thread really should not be used to sort out other issues with Android - like wifi, data connectivity, BT, speakerphone.... etc, etc. It's not what we're trying to test here! Thanks!!
[Touch Pro, Fuze Android Development] bl4ckb1rd:
hi...

here are my dmesg and logcat files for 3mp picrure and 5mp crash

-bl4ckb1rd
[Touch Pro, Fuze Android Development] viruscrazy:
Hi

I've updated the first post attached kernel (as a zipped file). It should now be ok to get the kernel logs for the JPEGTASK which is the guilty guy in the 5mp crash.

Thanks for your tests.

Please, read the first post "New kernels" section if your devices fails to boot (blocked on the haret loading screen).

Thanks
[Touch Pro, Fuze Android Development] Erikson89:
Haret doesn't boot with the set INITRD... line, too. It stays at WM and crashs the phone.

Does the line have to be at a specific place.
[Touch Pro, Fuze Android Development] funkys:
Same here. Stuck at Haret.
[Touch Pro, Fuze Android Development] DmK75:
Topaz freezes too, with line and without.
[Touch Pro, Fuze Android Development] viruscrazy:
I've placed the new line after the line "set initrd initrd.gz"....it's strange because I can boot it on my rhodium...going to test it on the diamond just to be sure...Otherwise, I will have to temporarly disable my changes on the rhodium panel board to make it boot...

Edit -1 : Tested on diamond, it's booting fine...waiting for your tests !

Edit : can you tell me the Haret.exe version you are using ? I use the pre 5.3. If needed, I can share it.

Edit 2 : If I can't figure out what's the problem with your devices (you will have to buy a rhodium.... :D), then, please, make the device freeze using this kernel, then, reboots the device, put the working zImage back on the sdcard (better to do it on the computer), then boot into android and type :

adb shell cat /proc/last_kmsg

This will show me what's the problem with the boot (all that for a 5mp sensor...that's weird !)

Thanks
[Touch Pro, Fuze Android Development] funkys:
Hi Viruscrazy

here is my log.
[Touch Pro, Fuze Android Development] viruscrazy:
Thanks. What's your Haret version ?
[Touch Pro, Fuze Android Development] funkys:
pre 0.5.3 2009121...
[Touch Pro, Fuze Android Development] viruscrazy:
That's strange. I'm also using pre 0.5.3 on my diam100 without problems...Can you try the attached HaReT ?

Also, can you tell me if you've got the latest initrd.gz from autobuild service.

I might have to try with FRX04 and new rootfs as I don"t have already switched to FRX04...

Jerome
[Touch Pro, Fuze Android Development] djdafreund:
I am personally using frx03 build,with new frx04 updates on top of frx03, and then of cours adding the camera files from here and everything is working fine on raph800. Even battery meters are fine again (thanks for the fix btw,wasnt even usable without that fix.), but i do hope u can get things working ok with other models. Kind of worried about installing todays updates,since everything is already working, in case it does worse annd actually makes it not boot right after.
[Touch Pro, Fuze Android Development] funkys:
Viruscrazy

Your Haret is the winner. Android started without problems. Your version of Haret is 8kb less then mine.

best regards
[Touch Pro, Fuze Android Development] viruscrazy:
Yes, you shouldn't use the latest kernels till it's giving more improvement for your devices...if you've got something working, then it's perfect. The new kernels will mostly be for improvement / fixes of non working devices.

I don't know if the raph800 is using flashlight ? If so, then the next kernel might be usefull for you as I've added the flash part.

btw, as I'm fighting with all those devices names, what does raph800 equals to (Fuze, or alltel, or something else) and can you point me to the name of an official ROM (tell me your provider or the rom you are using).

Thansk a lot.
[Touch Pro, Fuze Android Development] djdafreund:
Sure thing crazy man. LOL. My current rom is nothing but NRG rom. Here's a link, depending on which one (probably doesn't matter if it's WM 6.5 or WM 6.5.5.

Here's the link (a good bit of user's usually use energy rom's. Every one i know at least does.

http://hotfile.com/list/829198/9158c03

Energy HERMAN 29007 Sense2.5 Cookie 2.0 - Jan.06 is the one i use. With Sprint PCS. Official as in everything is working the same as it should, plus extra added programs and utilities. Unofficial as in it's WM6.5.5 isn't a version HTC is giving us user's, but then again either is 6.5, since HTC stock gives us 6.1 only.

http://rapidshare.com/#!download|290l35|167423992|Hermann_C_SPRINT_WWE_1.03.651.3_RS1.03.15F_SPCS_1.53_PRL6063_Ship.exe.zip|119125 for an official Touch Pro stock ROM in case.

Yah, i forgot about the flash (so so to use anyway on my phone. Don't care TOO much about the bluish white cast it makes on images, but still better then nothing but dark at least :)) I'll definitely do some testing on the next kernel for ya for sure to help knock that out.

Here's the name, all the same device of course-

====================================

Herman - Touch Pro CDMA - Raph800

Hope that is useful for ya. I saw it mentioned "people using FRX04 might need to remove these two lines from conf file"? About using frx04, is commenting those two lines out mentioned ONLY needing to be done if your having issues only, as mine seems to be working fine on my touch pro.

Edit- Hmm. After messing around with the bit, i am noticing that auto-focus isn't working at all. It's taking picture's ok, just not focusing. Guess i shouldn't have spoken too soon. Sorry. Just added the command line to my startup mentioned in the first page, and also removed/commented those 2 lines out for frx04, but unfortunately camera is still NOT focusing. Would you want a log for this and when taken? Or just need to know if it's because of frx04 that is likely the cause maybe? I'll get and do what you need me to do Viruscrazy. Lemme know.
[Touch Pro, Fuze Android Development] viruscrazy:
I will have to test the autofocus, but I might have broke it when I reworked the userland camera library. I will have a look, but maybe this will be fixed after the 5mp is fixed (hopefully soon...)

Regards
[Touch Pro, Fuze Android Development] Erikson89:
Topaz 5MP crash

Your Harez works and the line have to be under "set initrd initrd.gz", above it doesn't boot.

Here are the logs. I hope it helps.

Is it possible to speed up the application after fixing the remaining bugs or is there no room for optimations anymore? It is very slow.
[Touch Pro, Fuze Android Development] viruscrazy:
Don't know if it will be optimizable, that might be the camera application itself that is slow. I havn't tried an other camera application (I don't know if there's some alternatives on the android market).

If it's the camera application itself, then I won't be able to change anything as it's java...and I do not feel that much comfortable with java...
[Touch Pro, Fuze Android Development] Erikson89:
Ok thx, I will search a faster app.
[Touch Pro, Fuze Android Development] yourboyfrombk:
i dont know if this was noticed or not but while using the google goggle app i get a fc saying "unsupported system configuration" yada yada yada (kernel is missing IPv6 support) any suggestions?:confused:
[Touch Pro, Fuze Android Development] viruscrazy:
Hi,

I've updated the first thread attachements with a new package (kernel and modules). I've increased the memory for the Blackstone + Topaz. Can you please test again the 5mp snapshot ?

Don't need to make the 3mp dmesg then 5mp dmesg, only the 5mp if it crashes.

Thanks, Jerome

P.S : I've seen that the modules I was doing were extremely big...I've used an other script to make the new ones, they are now the same size than official ones...this might explain why some apps where slow if the modules were loaded.

Sorry for that !
[Touch Pro, Fuze Android Development] lorikitty:
I used it a few times from different shells, including on the phone itself. I do have a fuze, just thought I'd give it a try since it's the diamond's cousin.

Sudoing doesn't work, that's the first thing I tried :P it's like logging in as admin to try to change something on a CD. The FS needs to mount as RW or I won't be able to touch it, and ADB remount and the other rw command don't work. I'll just wait until it's implemented in xdandroid :)
[Touch Pro, Fuze Android Development] arrrghhh:
Let's not fill the thread with this garbage, c'mon guys. We do our best to support all devices, just be patient.

Thanks again viruscrazy, for all your hard work. Going to test this now.

Hey one suggestion viruscrazy - why not just have the files mounted thru the froyo.user.conf with the bind mount statement like we do on the 3D testing stuff? I'm going to run it right now like that to see what happens... Just seems easier, and you don't have to worry about messing up your system image. Just my .02, keep up the great work man :D

Blank screen for camera preview on RHOD, but that makes sense. It's not ready for RHOD yet ;)
[Touch Pro, Fuze Android Development] xUmaRix:
This is what i get when i try to run camera

<6>[ 4038.816070] binder: release 1701:1723 transaction 42886 in, still active
<6>[ 4038.816131] binder: send failed reply for transaction 42886 to 3585:3592
<4>[ 4042.608612] snd_ioctl set_device: device 1
<6>[ 4042.871032] +++ msm_setup_audio -- 0x8
<6>[ 4042.871093] --- msm_setup_audio -- 0x8
<6>[ 4042.871093] snd_set_device 1 1 1
<4>[ 4042.871124] [RPC] CALL to 30000002:0 @ 0:00000001 (60 bytes)
<4>[ 4042.871185] [RPC] READ on ept c64942c0
<4>[ 4042.872650] [RR] - ver=1 type=1 src=0:00000001 crx=0 siz=28 dst=1:c64942c0
<4>[ 4042.872772] [RPC] READ on ept c64942c0 (24 bytes)
<6>[ 4042.874542] +++ msm_setup_audio -- 0x8
<6>[ 4042.874572] --- msm_setup_audio -- 0x8
<6>[ 4042.874603] snd_set_volume 256 0 5
<4>[ 4042.874633] [RPC] CALL to 30000002:0 @ 0:00000001 (60 bytes)
<4>[ 4042.874694] [RPC] READ on ept c64942c0
<4>[ 4042.875854] [RR] - ver=1 type=1 src=0:00000001 crx=1 siz=28 dst=1:c64942c0
<4>[ 4042.875976] [RPC] READ on ept c64942c0 (24 bytes)
<4>[ 4042.876617] [RR] x RESUME_TX id=1:c64942c0
<4>[ 4042.876647] [RR] send control message cmd=7 srv.cmd=7 prog=00000001:c64942c0 id=-719610024:c017d284
<6>[ 4042.936340] +++ msm_setup_audio -- 0x8
<6>[ 4042.936370] --- msm_setup_audio -- 0x8
<6>[ 4042.936401] snd_set_volume 256 0 4
<4>[ 4042.936431] [RPC] CALL to 30000002:0 @ 0:00000001 (60 bytes)
<4>[ 4042.936492] [RPC] READ on ept c64942c0
<4>[ 4042.936706] [RR] - ver=1 type=7 src=0:fffffffe crx=0 siz=20 dst=1:fffffffe
<4>[ 4042.936767] [RR] o RESUME_TX id=0:00000001
<4>[ 4042.937927] [RR] - ver=1 type=1 src=0:00000001 crx=0 siz=28 dst=1:c64942c0
<4>[ 4042.938079] [RPC] READ on ept c64942c0 (24 bytes)
<6>[ 4044.805816] hw3d_open: pid 3585 tid 3614 opening client node
<7>[ 4044.805969] locked_open_wait_for_gpu: wait_for_open 2
<7>[ 4044.806091] locked_open_wait_for_gpu: woke up (2 0 00000000)
<6>[ 4044.806182] hw3d_open: pid 3585 tid 3614 got gpu
<7>[ 4044.806274] clock-regime: msm_clk_regime_grp_rail_switch : Switch GRP rail to 1
<7>[ 4044.826354] clock-regime: msm_clk_regime_grp_rail_switch : Switch GRP rail to 1
<4>[ 4044.925689] remapping device 173
[Touch Pro, Fuze Android Development] casefan7:
What i dide was:

cd /sdcard

cd \lib_pack

sh lib_inst.sh

but then I got something like.. cannot write file exists.

What do I do now?
[Touch Pro, Fuze Android Development] xUmaRix:
try mount -o remount,rw /system first before you execute the script.btw looks like Alex manage to take some pics on his kovsky
[Touch Pro, Fuze Android Development] viruscrazy:
Thanks to everybody for tests. I'm going to make a new zImage tomorrow with just some debug outputs for all devices to make sur my memory adjustments are OK.

@arrrghhh : I'm open to all sugestion. If you cand get it work using bind, could you please send me the cript or post it here so that everyone can use it.

@xUmaRix : I think we should work using mails. Can you pm me with your mail if you're ready to test some zImages. Last image I've posted should have worked for you, I can't see why it's not working but I will have a look to it tomorrow (gitorious was broken tonight, it's working right now but I havent't been able to push my files from work as gitorious was down...).

Here is a zImage to test : http://dl.free.fr/pXfFZ3hxm

It should boot (only debug messages...)

To anyone willing other devices to be supported, just be patient. I'm doing my best to at least support devices that shares the same sensors as liboemcamera. Devices with different sensor will require more work.

Jerome
[Touch Pro, Fuze Android Development] viruscrazy:
That's a great news !
[Touch Pro, Fuze Android Development] arrrghhh:
Certainly, it's attached. Just put the files at the root of your SD. Feel free to adjust the paths if you don't want all the files on the root...

I also had to add .txt to the end of the file to get it to attach, just remove it. Filename should be 'froyo.user.conf' - I'd rename the original (in the conf folder) and copy this on into said folder. Assuming all the files needed for the mount are at the root of your SD, and this conf file is in there... you should be good to go!

Thanks again viruscrazy, I look forward to more phones being included in the testing :D
[Touch Pro, Fuze Android Development] viruscrazy:
Thanks a lot. I'm going to have a look to the memory settings again this morning.

One good point is that the camera init is now working (your first dmesg log showed me that the camera was not responding to I2C, not the error is gone, just a problem with I2C address that was wrong.). Also, I fixed the GPIO table for blackstone as it's not using the same GPIOS for camera data lines and camera power control.

Edit : The camera can't yet work on your device as there is no pmem_camera and pmem_adsp regions (that's the memory regions I'm trying to configure on your devices).
[Touch Pro, Fuze Android Development] viruscrazy:
I've uploaded 2 zImages. Links are on the first post. One does just prints memory configuration (I found bugs in the previous ones) for all devices. The second one apply those settings.

Either you try the second one and if it does not boot, you try the first one....or you try the first one, make the dmesg log, then try the second one (if the field MB_TO_BYTE(MSM_EBIN_FREE_SIZE) in the dmesg log is something like 0xffxxxxxx, then don't bother to try the second image, it won't boot).

Thanks
[Touch Pro, Fuze Android Development] fshami:
Good work

Good work Virus :).

I have a Diam100. If anyone has tried it already on it, then please send me the set to files to copy n have the camera enabled :).

I donot have ADB n stuff so sharing will be helpful for me :).
[Touch Pro, Fuze Android Development] Corias:
RAPH100: With latest kernel, camera works but image is upside down.
[Touch Pro, Fuze Android Development] sirthoz:
plz post here links for downloads zimage and modules cause those links are tooooo sloooow and gave me cut out i only get 750kb for zImage and 250kb for modules so plzzzzz upload somewhere
[Touch Pro, Fuze Android Development] smack_exTreme:
i do wonder which android version are u using with this?
[Touch Pro, Fuze Android Development] R^7Z:
I would go so far to suggest FroYo but I have yet to test it on my Fuze...

I can remove these if not needed, just ask, thanks!
[Touch Pro, Fuze Android Development] Corias:
Uploaded to my personal webserver: http://belive.homeip.net/corias/xdandroid/kernel_20101224_camera_test.rar
[Touch Pro, Fuze Android Development] smack_exTreme:
i meant which distribution, currently i'm using http://www.neopeek.com/forum/Android-ROMs/5658-ROM-FRX03-12-21. always looking for better...
[Touch Pro, Fuze Android Development] R^7Z:
Didn't think there was a preferred distribution for our devices. I've always used XDAndroid because it has been the easiest to setup (NO additional partitions required) and haven't had any problems that I couldn't troubleshoot myself. Also, I've been following this project since cupcake! ;) :p
[Touch Pro, Fuze Android Development] Erikson89:
It boots faster now. Thanks for that.

The crash still persists.

Log attached.
[Touch Pro, Fuze Android Development] rpierce99:
Add the line "modprobe ipv6" in your froyo.user.conf in the user commands area (same place as all of the mount --binds).
[Touch Pro, Fuze Android Development] viruscrazy:
Hi, Thanks for that quick test. I've checked again the liboemcamera.so and it's allocating buffer into camera memory region, not adsp. Have reverted back to 8mb for adsp and increase camera to 16mb.

Can you test the new kernel attached in the first post.

Jerome
[Touch Pro, Fuze Android Development] Erikson89:
That doesn't work for me and brings an error when activating wlan.

@jerome

Tested new kernel, too. It crashes.

Log attached.
[Touch Pro, Fuze Android Development] viruscrazy:
Well, seems not related to the memory size....that seems nromal as it does not complain about memory size but it still bugging...

I've found one thing different in the qdsp driver (compared to a newer version). I've applied it to the kernel, so can you please test the attached new kernel (named with qdsp in it). I hope this one is the good one, I don't want to bother you with small tests...and next week, I'm on hollyday and won't have access to internet...
[Touch Pro, Fuze Android Development] Erikson89:
Great!!! It works with the normal camera app. Can you upload the modules file, too? (wifi doesn't work without it)

I also tested an other app (Camera 360) but there the picture doesn't get saved. The app doesn't crash and the camera still works.

This app is faster I think and has lots of settings the normal app doesn't have.
[Touch Pro, Fuze Android Development] Stickman89:
5M all working now for the Blackstone! Didn't work at first as after changing the kernel the camera froze on taking a picture, fixed by toggling picture size to 3M and then back again to 5M.

edit: How strange when you take a picture whilst zoomed the preview snapshot shows a shot without a zoom. When you check the saved shot itself you see that actually your zoom was effective, sorry if that's confusing... Ahhh well not really a problem and I'm happy :)

Best Regards,

ST1Cl<^^aN
[Touch Pro, Fuze Android Development] Erikson89:
Doesn't recognized that on Topaz. 5MP worked suddenly after booting the device.
[Touch Pro, Fuze Android Development] welard:
i have a problem startup android with the new:--set INITRD_OFFSET 0x608000------anybody with a blackstone device with correct startup.txt thanks:confused:
[Touch Pro, Fuze Android Development] viruscrazy:
Yeah, someone else told that the zoom works for preview but is innefective on snapshot. I think that just a small fix in the userland, but that's easier than this ****ty 5mp bug !

I will try to do the module tonight before going on hollydays.
[Touch Pro, Fuze Android Development] Erikson89:
you need the new haret:

last post on this page http://xdaforums.com/showthread.php?t=883966&page=57

and add the line under "set initrd initrd.gz"

Thanks!
[Touch Pro, Fuze Android Development] welard:
i have haret already and the set line..........found the problem......it couldnt find roofts while loading so i change path........

thanks for the help anyway

:)
[Touch Pro, Fuze Android Development] paulabutler:
Hi, I tried the 3m then back to 5m on my blackstone - it took 3 pictures then froze up
[Touch Pro, Fuze Android Development] NeedAPhone:
I have new haret.exe, zimage and modules, but when i run haret it boots back to WM,

Here's my startup.txt:

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 2030

set KERNEL zImage

set initrd initrd.gz

set INITRD_OFFSET 0x608000

set cmdline "rel_path=andboot lcd.density=240 msmts_calib=0x395.0x3c9.0x79.0x77 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-2,-1,3 msm_blackstone_pad.vibrate=1 acpuclock.oc_freq_khz=630000 htc_battery_smem.vol_min=10 htc_hw.call_vol=5 htc_hw.handsfree=1 hw3d.force=1"

boot
[Touch Pro, Fuze Android Development] Erikson89:
The new package does't work again. App crashs when taking a 5MP picture.

Log attached.