Posted by juming
On 2007-08-28 07:49:37, max_wedge wrote:
so ISO 200 isn't too badly under-exposed? 100 was way dark, I thought of trying 200, but hadn't got around to it yet..
Not too much compared with ISO 400, about under exposed, compared with ISO 400 it will more under exposed, but after I compare the result with the real world, I can say it's less or more same, so you not getting any more bright picture with this setting, instead it will give the result that what you see in real world is what you get after taking picture with flash in ISO 200.
Posted by amarsidhu
i am really happy with 2.7.
its clicking real sharp images
keep it up and keep them coming....
Posted by max_wedge
Apparently, in JSR234, it's possible to use JAVA to control the camera (even on my K700 Java could access the camera), but perhaps there is more elements of the camera's performance available to the Java app than in previous api's. Imagine if a java app could do what can be done with camdriver0.dat?
You could have completely customised camera UI's. Like KD Player for music or Opera Mini for the internet.
"Access to the 3.2 Megapixel camera can be achieved through the Advanced Multimedia Supplements API, JSR 234, to let users control the exposure, focus, zoom and frame-by-frame video recording from a Java application."
that's from an article I was reading about K770
http://developer.sonyericsson[....]al=article-newK770announcement
Posted by Mike2
On 2007-08-28 15:02:33, max_wedge wrote:
Apparently, in JSR234, it's possible to use JAVA to control the camera (even on my K700 Java could access the camera), but perhaps there is more elements of the camera's performance available to the Java app than in previous api's. Imagine if a java app could do what can be done with camdriver0.dat?
You could have completely customised camera UI's. Like KD Player for music or Opera Mini for the internet.
"Access to the 3.2 Megapixel camera can be achieved through the Advanced Multimedia Supplements API, JSR 234, to let users control the exposure, focus, zoom and frame-by-frame video recording from a Java application."
that's from an article I was reading about K770
http://developer.sonyericsson[....]al=article-newK770announcement
Posted by max_wedge
K800 has jsr234 also, but I can't get apps to be set as wallpaper. The Wallpaper option is there but greyed out.
Posted by juming
On 2007-08-29 00:00:23, max_wedge wrote:
K800 has jsr234 also, but I can't get apps to be set as wallpaper. The Wallpaper option is there but greyed out.
Do you download the .jad beside .jar for apps ? I use MobiToday and it's can be set as wallpaper in my K800i
Posted by max_wedge
no I installed by jar only. I'll try installing with jad
Posted by Mike2
On 2007-08-29 00:00:23, max_wedge wrote:
K800 has jsr234 also
Posted by juming
On 2007-08-29 11:57:29, Mike2 wrote:
If it has JSR234, then why hasn't anyone made an application to control the camera?
It's already. FaceWarp can capture using camera directly.
Posted by max_wedge
there was a java app for K700 that controlled the camera - a webcam software. So I think the jsr234 must give more control than just the ability to take a photo, I don' think K700 was JSR234...
Posted by max_wedge
On 2007-08-28 08:23:01, mongoose3800 wrote:
If you want to experiment further just replace the 2mp settings in your camera driver with the following:
seq_set_prop_5_6 = $"2M_High_comp"
#SET_REG(19,4B) // JPEG_INIT_QUALITY = 0x4B = 75d
#SET_REG(13,20) #SET_REG(14,03)
#SET_REG(17,58) #SET_REG(18,02)
#SET_REG(15,90) #SET_REG(16,01);
seq_set_prop_5_7 = $"2M_low_comp"
#SET_REG(19,5A) // JPEG_INIT_QUALITY = 0x5A = 90d
#SET_REG(13,84) #SET_REG(14,03)
#SET_REG(17,20) #SET_REG(18,03)
#SET_REG(15,58) #SET_REG(16,02);
I'd really like to know what others think.
giving this a go now...
Posted by [c3]
can u post the results b4 and after pics please? thanks
Posted by lpachuong
What is the biggest buffersize and compression on k800i ?
Posted by amarsidhu
@lpachuong: can you update k800 driver.??????
Posted by lpachuong
Maybe. But does anyone has a table of all properties for k800i?
_________________
To be or not to be !!!
Please save our world. Save our world to save our lives and our generation.
There is no place as good as your house with your family. Home sweet home.
[ This Message was edited by: lpachuong on 2007-08-29 13:44 ]
Posted by mongoose3800
On 2007-08-29 14:34:36, lpachuong wrote:
What is the biggest buffersize and compression on k800i ?
I've had the buffer up to 2000kb but haven't figured out what it does - although I starting to get some ideas - see below. You can have compression right upto 100%. But the results are strange as the higher you go above 90% the images produced have smaller file sizes.
I did stumble across somthing interesting today though - I increased the min file size for 3mp driver from 400kb to 800kb. Interestingly the driver worked fine until I took a photo that was mostly white. This is when the camera reset. So, I tried really complex images and all was fine. So I put the setting back to 400kb and tested again. The file of a totally white scene is quite small. So, I think the min file size is actually the minimum file size that will be accepted from the sensor. I am now wondering if the same applies to the max file size.
[ This Message was edited by: mongoose3800 on 2007-08-29 14:13 ]
Posted by max_wedge
mongoose, that 2MP mod is quite cool, it gives us the 2MP images (with this mod alone) that we needed massively tweaked drivers to get the same on the K750!
This tends to prove to me the K800 sensor is quite good.
Perhaps the phone is not really powerful enough to run full quality 3MP images (due to phone resources, no fault of the sensor or camera module itself.)
Or, perhaps camdriver just needs to be tweaked forperformance more than SE could be bothered with!
Posted by mongoose3800
On 2007-08-29 13:56:10, max_wedge wrote:
On 2007-08-28 08:23:01, mongoose3800 wrote:
If you want to experiment further just replace the 2mp settings in your camera driver with the following:
seq_set_prop_5_6 = $"2M_High_comp"
#SET_REG(19,4B) // JPEG_INIT_QUALITY = 0x4B = 75d
#SET_REG(13,20) #SET_REG(14,03)
#SET_REG(17,58) #SET_REG(18,02)
#SET_REG(15,90) #SET_REG(16,01);
seq_set_prop_5_7 = $"2M_low_comp"
#SET_REG(19,5A) // JPEG_INIT_QUALITY = 0x5A = 90d
#SET_REG(13,84) #SET_REG(14,03)
#SET_REG(17,20) #SET_REG(18,03)
#SET_REG(15,58) #SET_REG(16,02);
I'd really like to know what others think.
giving this a go now...
MAX, Set your 2mp low comp to 100% (64 in Hex) as well. I think you get better pictures than using the standard 90%.
So far I'm still consistantly noticing less jaggerness.
Posted by [c3]
Is it only fixing the jagged edges issue or are the pictures actually getting sharper?
Posted by max_wedge
On 2007-08-30 00:15:23, [c3] wrote:
Is it only fixing the jagged edges issue or are the pictures actually getting sharper?
I don't get this obsession with sharpness?? I am not finding any problem with sharpness in the K800 driver. It seems well balanced in this regard. Sharpness is an artifical "fix" and will only result in loss of detail as picture information is thrown away to unnaturally sharpen the image. Sharpening is a processing step best left to resized pictures or forensic imaging experts. If the CMOS sensor was really poor quality (it isn't) then sharpening might help, but not in this case.
Hold your camera steady, that's the best advice I can give. The sensor is not a lightning fast DSLR CCD jobbie - you have to hold the camera nice and steady, and also wait a second after taking the picture (don't just snap and run).
Improving sharpness won't fix any other deficiencies in fact it will only make them more obvious. Infact the jagged lines are partially caused by sharpening (sharpening introduces aliasing)
I've compared the sharpened images to default, and they look better on the phone LCD, but look pixelated and rough on the PC screen.
Posted by juming
On 2007-08-30 01:09:16, max_wedge wrote:
I don't get this obsession with sharpness?? I am not finding any problem with sharpness in the K800 driver. It seems well balanced in this regard.
Hold your camera steady, that's the best advice I can give. The sensor is not a lightning fast DSLR CCD jobbie - you have to hold the camera nice and steady, and also wait a second after taking the picture (don't just snap and run).
Improving sharpness won't fix any other deficiencies in fact it will only make them more obvious. Infact the jagged lines are partially caused by sharpening (sharpening introduces aliasing)
I've compared the sharpened images to default, and they look better on the phone LCD, but look pixelated and rough on the PC screen.
100% Agree with you, Sharpening only makes picture jaggies, and now I'm reset back to standard, or if want to add more sharpening 12.5% is maximum, otherwise picture will be jaggies.
About DSLR, it's using CMOS max
Posted by max_wedge
On 2007-08-30 02:01:27, juming wrote:
About DSLR, it's using CMOS max
I was making a joke, and CCD sounded better than CMOS.
Anyway, CCD is still common in DSLR. CMOS will eventually replace CCD, but there are still many ccd based DSLR's on the market.
Posted by rockygali
hi guys... so?! where is the final tweak?!
Posted by juming
On 2007-08-30 03:20:18, rockygali wrote:
hi guys... so?! where is the final tweak?!
Back to stock driver
Posted by rockygali
oh my.. how come?!
i thought they had something goin on with the 2MP tweak..
i mean that alone will suffice my hunger for better driver.
i just do not understand what they meant when tweaking some lines...
Posted by mongoose3800
On 2007-08-29 15:14:33, max_wedge wrote:
mongoose, that 2MP mod is quite cool, it gives us the 2MP images (with this mod alone) that we needed massively tweaked drivers to get the same on the K750!
This tends to prove to me the K800 sensor is quite good.
Perhaps the phone is not really powerful enough to run full quality 3MP images (due to phone resources, no fault of the sensor or camera module itself.)
Or, perhaps camdriver just needs to be tweaked forperformance more than SE could be bothered with!
I think you're right that the phone is not powerful enough. I don't think it has the capacity to cope with images much larger than 900kb. It is interesting that you can improve the 2mp images by increasing the MAX size and buffer to 900. But, you can't take the 2mp much above 900kb either without making the camera unstable. So, the phone is probably limited to creating a 3mp image is limited to around 900kb.
I think the jaggies are coming straight from the sensor and that the phone isn't filtering it out enough. And, I actually think the 3mp pictures are too Sharp. Perhaps if we find a way to reduce the sharpness the phone might apply some anti-aliasing.
Posted by juming
On 2007-08-30 03:55:54, mongoose3800 wrote:
I think the jaggies are coming straight from the sensor and that the phone isn't filtering it out enough. And, I actually think the 3mp pictures are too Sharp. Perhaps if we find a way to reduce the sharpness the phone might apply some anti-aliasing.
Hm.. I think phone actually already implement some \"blur\" for oversharp picture, but this can only happened if we set sharpening value to FF a.k.a reset sharpening level, so phone will judge it will increase or decrease sharpness picture that taken by sensor.
Posted by juming
What I do now is just set image size bigger (less compression, thanks mongoose), and make sharpening value to 0 a.k.a do nothing for sharpening, so what cam sensor get will untouched (we can retouch later with any digital lab software such photoshop or any other else), and set any images captured with Xenon flash to ISO 320 (originally ISO 400 but it's overbright, and try set to ISO 250 but some cases tend to darker).
Meanwhile I think this most better result I can get on camera phone, not overbright, oversharp or any other, it's more natural, like what I get on normal digital camera
Posted by max_wedge
nice work. Now I'm off to compile all that in a driver...
2MP changes, plus sharpening 0, 100% compression, flash to 350.
Posted by juming
On 2007-08-30 05:36:08, max_wedge wrote:
nice work. Now I'm off to compile all that in a driver...
2MP changes, plus sharpening 0, 100% compression, flash to 350.
Max, forget about 100% since I already try it reset (not saving) so I back to 95% only.
Posted by max_wedge
k
Posted by norbi_nw
plz upload mongoose3800's driver. I have a k810i, and i like the k800i camdriver better. Does mongoose's camdriver support VR @ 30FPS?
And if possible, upload some sample pictures (make this topic like supermod for K750/w800/w810 thread)
[ This Message was edited by: norbi_nw on 2007-08-30 10:56 ]
Posted by norbi_nw
tested kopritis 2.8 vs 2.5 stock driver. 2.8 was much sharper. Now need to correct the white ballance... and enhance the VR from 10FPS to 30FPS. After that, we can concentrate on colors.
Posted by mongoose3800
On 2007-08-30 06:57:21, juming wrote:
On 2007-08-30 05:36:08, max_wedge wrote:
nice work. Now I'm off to compile all that in a driver...
2MP changes, plus sharpening 0, 100% compression, flash to 350.
Max, forget about 100% since I already try it reset (not saving) so I back to 95% only.
What max file size do you have for 2mp? What buffer size have you set for 2mp. If you go above 900kb it will crash. I've been running 900kb with 2mp for 2 days now without a single reset and I have taken lots of shots. I've been playing around with compression ranging from 90% to 100% and have not had one single problem.
Posted by Vinny67
OK - so I've got the 2.8 camera driver, and got XS++ up and running and connected to my K810i.
In XS++ what configuration do I use?
'Flash' or 'FSX'?
If 'Flash' then do I 'Flash Main Firmware' or 'Flash File System'?
Thanks in advance
Posted by max_wedge
read my Menu Modding Guide, it starts woith an explanation how to copy files to the phone with XS++.
Posted by Vinny67
You must be using a different version of XS++ to me.
My K810i phone is not listed on there and the BreakXS box is in a different place.
Every time I try it I get a failed message.
Can anyone help?
Posted by [c3]
Vinny ur probably not following the instructions accurately. just try doing it step by step and ull get it, Max's guide is really helpful, there's also another guide, with pictures for XS++ on the forum somewhere. http://www.esato.com/board/viewtopic.php?topic=153990
Posted by Vinny67
Would it be down to the fact that the K810i is not listed in XS++?
I have tried it step by step more than ten times now and it's just not working!
Never mind - I had XS++ v1.5. Downloaded v1.6.8 and it worked first time
[ This Message was edited by: Vinny67 on 2007-08-30 15:02 ]
[ This Message was edited by: Vinny67 on 2007-08-30 15:38 ]
Posted by norbi_nw
how to update my VR from 10 to 30? what line should i change?
Posted by deadman4168
What if The ISO is increased To 500? what will will be the results
Posted by ZAMU
Wich part to set to modify iso settings? When using flash and in non flash mode? Please tell me because I am new at modding
Thanks in advance!
Posted by deadman4168
Xenon Flash initialization
AND
ISO, property
Posted by ZAMU
On 2007-08-30 19:24:19, deadman4168 wrote:
Xenon Flash initialization
AND
ISO, property
Thanks...but what values to use? could you give me an example using part of the camdriver text?
Posted by deadman4168
I m also a newbie so it would better if mongoose or maxwedge replies
Posted by ZAMU
On 2007-08-30 04:31:03, juming wrote:
What I do now is just set image size bigger (less compression, thanks mongoose), and make sharpening value to 0 a.k.a do nothing for sharpening, so what cam sensor get will untouched (we can retouch later with any digital lab software such photoshop or any other else), and set any images captured with Xenon flash to ISO 320 (originally ISO 400 but it's overbright, and try set to ISO 250 but some cases tend to darker).
Meanwhile I think this most better result I can get on camera phone, not overbright, oversharp or any other, it's more natural, like what I get on normal digital camera
could you give me an example using part of the camdriver text? I mean...to know how to mod the iso by myself. Thanks in advance!
Posted by juming
On 2007-08-30 14:56:32, mongoose3800 wrote:
What max file size do you have for 2mp? What buffer size have you set for 2mp. If you go above 900kb it will crash. I've been running 900kb with 2mp for 2 days now without a single reset and I have taken lots of shots. I've been playing around with compression ranging from 90% to 100% and have not had one single problem.
Actually I'm using that setting on 3 MP low compression. Buffer set to 1 MB, and today just get it reset again even with 95%, seems I should de-tune it again to 92% (on K750 92% is max for all around taking picture without reset)..
Posted by obi none
isnt there some potential for cleaner images using the 2 megapixel setting as the sensor isn't being loaded up, I read camera reviews all the time where they complain that the images are noisey because the sensor is being forced to capture more megapixels but the sensors arent being made any bigger. Personally Id much rather a smaller noise free image (night shots without flash anyone) than the dirty pixel hot spot pics the k800i turns out.
Im so glad i found this thread.
Posted by mongoose3800
On 2007-08-31 00:31:59, juming wrote:
On 2007-08-30 14:56:32, mongoose3800 wrote:
What max file size do you have for 2mp? What buffer size have you set for 2mp. If you go above 900kb it will crash. I've been running 900kb with 2mp for 2 days now without a single reset and I have taken lots of shots. I've been playing around with compression ranging from 90% to 100% and have not had one single problem.
Actually I'm using that setting on 3 MP low compression. Buffer set to 1 MB, and today just get it reset again even with 95%, seems I should de-tune it again to 92% (on K750 92% is max for all around taking picture without reset)..
As I said anything over 900kb seems to cause issues. It seems the 3mp settings are already at the max capabilities of the phone. This is why I changed my focus to the 2mp settings as I could take them upto what appears to be the phones limit. I have done so much testing now it has driven me mad. But, I am now happy with what I have done to the 2mp settings. I believe the 2mp images are now better than the 3mp images as they don't suffer the jaggies as much. But, as they are 2mp images there is a very small loss in detail that can only be noticed if you zoom right in - This can't be helped and beats zig zags everywhere. In most cases the images rival the w800 images. However, in taking photos of a Coke can yesterday I got better pictures out of a W810.
Replacing FF with 00 in the Sharpness reset seems to be the best option as it forces the sharpness to it's lowest setting. It is just a shame that the sharpness can't be lowered more as I think the images are far to sharp even on the lowest setting. If you play in photoshop you can actually easily up the jaggies by softening the area a little. Pitty the phone can't do this.
I have put together a driver for others to try. I have changed the version to 3.1 so that it can be easily identified. Here's a link to download it:
http://rapidshare.com/files/52361150/camdriver0.dat.html
This Driver has 2mp buffer set to 900kb, Max, target and min files settings from 3mp settings applied to the 2mp settings. 2mp compression set at 100. Sharpness set to 00 instead of FF. There are no changes to 3mp settings.
Posted by obi none
I was wondering if theres been any attempt to make the image stabilizer work in all modes? So u can still use the focusing feature with the stabilzer for instance as I find 9 out of 10 images with the stabilizer one are ironically blurry because there is no focusing ability in this mode.
could some one post some comparison pics to look at?
doin this will void my vodaphone warranty wont it?