Super camera driver for k750/w800/w810

Posted by mattsw810i

On 2007-12-16 09:16:57, Kriomag wrote:

On 2007-12-16 08:12:47, mattsw810i wrote:
Kriomag's latest driver wont do manual focus on my w810.. Any one else having this trouble?

All beta versions or just last one?

Re installed driver and it works fine. Something must have not worked last time...

same pic light on vs light off

Posted by william2008

On 2007-12-17 00:35:32, lpachuong wrote:
A4A 11.00 Reloaded
http://www.freewebs.com/ict20[....]driver0%2011.00%20reloaded.DAT

Hope you are pleased with this. I'm looking forward to seeing pictures and comments from you.

Have a nice day.

Tested on W800 but it crashed when I took a picture

Posted by lpachuong

On 2007-12-17 11:17:55, william2008 wrote:

Have a nice day.

Tested on W800 but it crashed when I took a picture

I uploaded 2 version above: 95% and 91%. From now on I will not touch high compression on w800i/k750i bcz of its limit. 91% will be the highest compression on those cam-modules.

Posted by lpachuong
For some reasons, Freewebs sometimes doesnt work. If you want to try my driver, please download it from: http://www.mediafire.com/?atxv95x1tiu

Posted by number1
whats the advantage of increasing the jpeg retry limit/time?????

Posted by terminator17
A4A 11.00 Reloaded
http://www.freewebs.com/ict20[....]driver0%2011.00%20reloaded.DAT 95%

http://www.freewebs.com/ict2006_2007/camdriver0%2011.00%2091.dat 91%

and
http://www.mediafire.com/?atxv95x1tiu

are these all same????

Posted by Raiderski
for K790/K800/K810 none. they already have 5sec which is long enough to protect against camera crash due to unreachable parameters sent to jpeg encoder

Posted by number1

On 2007-12-17 13:09:44, Raiderski wrote:
for K790/K800/K810 none. they already have 5sec which is long enough to protect against camera crash due to unreachable parameters sent to jpeg encoder

ok thanks for that i increased it to 6sec anyway

Posted by leetiran
Is there a java application running on the phone to read the exif of picture?

Posted by number1

On 2007-12-17 13:32:05, leetiran wrote:
Is there a java application running on the phone to read the exif of picture?

i want a java exif reader aswell, it would be very very useful

Posted by Randolph
Blair Witch mood near my home...

shot with K750i CID49with Cammodule CID 36 and Raider 6.6 driver 91% sharpness=5 where i added the effects from strong´s driver

...

Posted by gabrielrm
Java exif reader from SPU post on page 450:
"...
Links (15 kB):

http://nwamdclub.nktb-kristall.ru/ExifReader_1_0_a.rar
http://nwamdclub.nktb-kristall.ru/ExifReader_1_0_a.zip

NOTE that this is an ALPHA version!"

Posted by number1

On 2007-12-17 18:10:01, gabrielrm wrote:
Java exif reader from SPU post on page 450:
"...
Links (15 kB):

http://nwamdclub.nktb-kristall.ru/ExifReader_1_0_a.rar
http://nwamdclub.nktb-kristall.ru/ExifReader_1_0_a.zip

NOTE that this is an ALPHA version!"

thanks it works fine.

Posted by lpachuong
How to clear noise in the photos with PHOTOSHOP

This method is used to remove noise, not to sharpen the detail in the pictures.

Open the photo in your raw conversion software.
Select a white balance for the photo.
Make no other alterations in the raw conversion. In particular, do not modify levels in such a way as to clip dark values, and do not allow the RAW converter to apply sharpening.
Open your calibration frame in the raw conversion software and apply the same conversion settings to it as will be used for the photo.
Convert the raw images to maximum bit depth TIFF files.
Load both the TIFF files in Photoshop.
Select the calibration frame.
Press "ctrl-a" or choose "All" from the Select menu to select all of the calibration frame.
Press "ctrl-c" or choose "copy" from the Edit menu to copy the calibration frame to the clipboard.
Select the photo.
Press "ctrl-v" or choose "paste" from the Edit menu to paste the calibration frame into your photo as a new layer.
Close the calibration file.
Select the new layer in your photo - the one that was created by copying the calibration frame (we will call this the calibration layer).
Open the Blending Options dialogue (or make the following adjustments at the top of the Layers window).
Select "difference" for Blend Mode.
Select 100% for Opacity.

For more details, please visit: http://photo.net/learn/dark_noise/

Hope this is useful for everyone. I really hate noise

Posted by lpachuong
A4A Camdriver 11.01 18/12/2007

Revision

Compression: 91%

Normal mode: EM Off

Fine Mode: EM On

Functions:
EV_M_20= #CC_GREEN;
EV_M_17= #CC_MAGENTA;
EV_M_13= #CC_BLUE;
EV_M_10= #CC_YELLOW;
EV_M_07= #CHANGE_ZOOM;
EV_M_03= #ISO;
EV_M_031= #SET_FPS; (In video mode)
EV_00= #CHANGE_FOCUS;
EV_P_03= #SET_EXPOSURE;
EV_P_07= #SPOT_ON;
EV_P_10= #SHUTTERSPEED;
EV_P_13= #SET_FLICKER;
EV_P_17= #SCENE;
EV_P_20= #SET_PROFILE;

Sharpness: Recalculated value for better sharpness - noise reduction

Video mode: you will be suprised with the quality of the video you record.

Colours: Real true colour

Issues:
Viewfinder: slowlier frame rate for better focus => Yellowish effect may happen but the final picture will be perfect

Hope you all enjoy.

Looking forward to seeing your pictures.

Yours regards.

Link:

http://forums.se-nse.net/index.php?act=attach&type=post&id=13159
http://www.mediafire.com/?dq2gs1xzxzj
Get ready for Christmas !!!

_________________
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-12-18 00:42 ]

Posted by leetiran

Thanks a lot

Posted by terminator17

On 2007-12-18 01:39:14, lpachuong wrote:
A4A Camdriver 11.01 18/12/2007

Revision

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-12-18 00:42 ]

thnx 4 ur new driver..ll giv it a try

but can u please remove this yellowish preview...
thanx anyways

_________________
SE W810i,CID49,R4EA031

[ This Message was edited by: terminator17 on 2007-12-18 04:55 ]

Posted by Kriomag

On 2007-12-18 01:39:14, lpachuong wrote:
A4A Camdriver 11.01 18/12/2007

Pictures are very big (550-600kB) and seems to be stable - no camera crashes so far

Video is really good quality, maybe not as smooth it can be but less compressed so looks more detailed

Can i use your settings in my driver? i will test it few more days and if stable i would like to use them.

Posted by lpachuong

Can i use your settings in my driver? i will test it few more days and if stable i would like to use them.

First of all, thank you for your comments. About ur question, I think you know my answer

Of course yes. We are here to help each other. Maybe you will find a better way to improve it. And some where in my driver, I am using ur code already

(Thanks to you, SPU, Raiderski and chengrong)

PS: I found some arguement about the 'leaking' driver on k800i/k810i post, this reminds me about my old friend here, lengthstreet, how are you doing?

_________________
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-12-18 09:59 ]

Posted by 679

On 2007-12-18 10:48:54, lpachuong wrote:

Can i use your settings in my driver?...

First of all, thank you for your comments. About ur question, I think you know my answer

Of course yes....

Hope for amazing new features in new camdrivers.
One small (but may be not very easy) request to all wise camdriver modders.
Can we ask you comment in driver body some important lines like about VR or pictures quality, FPS, and so on. Yes, its waste of time, but is very usefull for other users.
I often have my own request for existing camdriver modding but have not enough knowlege to make it. For example i've made ZOOM PREVEIW in 21.92 only for range 2.4-4.0 as i'm far sighted but it was quite a job for me.
So it will be a great help for not so expereienced camdriver voluntiers...
THX.

Posted by lengstreet
Hi lpachuong & All frnd

Thx lpachuong for miss me

My Business very busy & My Wife's pregnant.

Next year(January maybe February 2008) im got daughter

i modded camdrive sometime.
i download ur camdrive to test and learn some code.

Thank All

LengStreet

_________________
http://www.flickr.com/photos/lengstreet

[ This Message was edited by: lengstreet on 2007-12-18 11:18 ]

Posted by phoenix1985
@metallica1:
So...your w800 never got crash with strong 5.6?
can you upload strong 5.6 camdriver that you used ?

Cheers...!

Posted by wickedsick
@lpachuong: these are two pictures with ur new driver. This morning I took my sister to the train station and took them. Will post some pictures of flowers when the weather is better. By the way, I know you are having a tough time with compression which sometimes makes the camera crash. People may dislike this at the moment but I am very pleased with the other details: sharpness/colours/exposure... Hope you will make a better compression method.
@everyone: I think you must try his new driver, it is awsome for me:

Nice colour, big size( the last picture: 605kb), sharp and hardly to see noise.

Posted by pikszel
@lpachuong
Your driver (v11.0) im my CID49_K750_with_CID36_cam fails.
Exactly the focus is set to infinity (i can hear) when i press the exposure button full and the pictures are all blurry (macros).

Posted by loucostanza
@SPU
I were testing your camdriver beta9 when I found some problems with its macro:
1. manual macro mode did not display zoom preview.
2. auto macro mode was too fast than it should be and also did not focus correctly (almost get blurred focus everytime).
Everything else was just fine. Daily outdoor pictures was very good, exposure time was fast enough, pics quality for medium light indoor (with LED ON) was also good, outdoor/indoor low light was not so good as I expected

(it has no EM right?). Nevermind about low light, I have been thinking maybe only MXE-60 that can help us. Is your driver compatible with it?

EDITED: I forgot to say, my phone's firmware is W800 R1BC002 CID36 RED.

[ This Message was edited by: loucostanza on 2007-12-18 16:43 ]

Posted by Raiderski
guys, if you want to fight with noise then enable pixel interpolation (filtering, reg5B to 00) and use low sharpness value (reg56 to 00 - 04) but this is something for something, in this case sharpness vs. noise

finally my phone dried entirely. oh crap... beer stench, scratched lens protection filter, almost not working '2' key. everything else is working good but i'm far from being happy. i must think about new phone

currently i'm back on track with 6.7 and i'm not happy again. everything what i wanted to do is finished but one important small damn fix doesn't work in 100% cases grrr...

Posted by metallica1

On 2007-12-18 15:34:31, phoenix1985 wrote:
@metallica1:
So...your w800 never got crash with strong 5.6?
can you upload strong 5.6 camdriver that you used ?

Cheers...!

phoenix1985

My phone is a W810i White, and the phone never crash with Driver Strong 5.6, just in function of supermod "Profile" is selected, but I never use this function.

The driver 5.6 from my phone that I had already put here at the forum:
http://rapidshare.com/files/7[....]5.6_from_W810i_21-11-2007_.rar

this driver have diferent function of 5.6 original, instruction together the link.

good advantage!

Posted by lpachuong
@Lengthstreet: Congratuation, my friend. I think you must be very busy from now on. But you will have a happy Luna New Year with your family. I will be thinking of you.

@pikszel: I think it is because you TURN MACRO ON Please turn macro off. For EM on, use fine mode and for EM off use Normal mode. Macro on for close range pictures and Macro off for normal picture.

@wickedsick: Thank you

Posted by SPU
loucostanza
1. Enter the manual focus zone (Zoom 1.1 - 4.0) then press Macro to enable zoom and again to disable.
2. Auto macro is not too fast, but it covers only macro range (8 - 30-40 cm).
3. You can try MXE in Normal compression mode, but it can be out of sync. I'll fix this later.

Posted by leetiran

On 2007-12-18 17:55:25, Raiderski wrote:
guys, if you want to fight with noise then enable pixel interpolation (filtering, reg5B to 00) and use low sharpness value (reg56 to 00 - 04) but this is something for something, in this case sharpness vs. noise

finally my phone dried entirely. oh crap... beer stench, scratched lens protection filter, almost not working '2' key. everything else is working good but i'm far from being happy. i must think about new phone

currently i'm back on track with 6.7 and i'm not happy again. everything what i wanted to do is finished but one important small damn fix doesn't work in 100% cases grrr...

sorry for your w800. wish the raider6.7 come soon

[ This Message was edited by: leetiran on 2007-12-19 00:56 ]

Posted by pikszel
@lpachuong
you misunderstand, I am in clear one with taking a photo but the autfocus does not work(ok, with my stuff not). the manual mode ok. the colors are brillant, sharpness with value 4-5 is enough (cid36cam)
malfunc: the camera capture sharpness (on surface with contrasty area), then press full the butt and the tube with lens move the default position (i can hear it and feel it on phonebody) then does the picture after this.

all macros are blurry because the focus is infinity (except manual focusing)

any idea?

p

_________________
"Az egyedüli létezô dolgok az atomok és az üres tér; minden egyéb puszta képzelet"

[ This Message was edited by: pikszel on 2007-12-19 12:52 ]

Posted by loucostanza

On 2007-12-18 22:59:27, SPU wrote:
loucostanza
1. Enter the manual focus zone (Zoom 1.1 - 4.0) then press Macro to enable zoom and again to disable.
2. Auto macro is not too fast, but it covers only macro range (8 - 30-40 cm).
3. You can try MXE in Normal compression mode, but it can be out of sync. I'll fix this later.

Thanks SPU. It works now.
Btw, I have not been testing your camdriver with MXE yet, still looking for free time to go shopping.

Posted by Raiderski
modders

1.
do you think that log system is working in K750/W800/W810? for example lines like this one:

$c0 00
$"text string %0"

first time i saw this in K800 code, so probably this feature is unavailable for our phones. i was looking for log file in filesystem - without result. shit, this would be very useful for us and we don't have so nice thing

2.
next case - events. uhh... i really hate them:

- we don't know whole list of events (yes, one more table after reg+cmd tables), this is what i know:

00 - events queue empty
05 - step zoom end
e1 - cam ready
e3 - jpeg end
e4 - caption start
e5 - convergence
e6 - autofocus
e7 - ? lens move complete / manual focus event
e9 - ? half release
ea - mode changed
ec - power save leave
ed - power save enter
ee - burst status

- we don't know how to catch them properly
for example WAIT_FOR_MODE_TRANSITION is very easy but this macro know on which event should wait (ec) and delays are long enough to catch this event. what if i don't know on which event number i have to wait and i don't know how much i need to wait on it? that really sucks

i have this situation in code:

apply scene (cmd51) and then apply WB (cmd11 or $u01)

everything is nice on paper but in practice doesn't work - scene will be changed but WB not. problem is obvious: scene changing can take a lot of time and WB can be applied before scene change (especially if shutter speed is slow). so, after cmd51 i have to wait for event "scene changed" and then apply WB. that's cool solution... but we don't know event "scene changed" ID

maybe i should try to check whole ~240 events ID values? haha

another idea is from K550/K800 drivers (COM_EVENT): wait until all events will be finished, call command, hold until event trigger will not say "ok, command execution is finished". yeah right but try force to work this code on K750:

// listen to signal on TRIG (Application GPIO_25)
// check every 5ms state of trigger, if whole delay is 1000ms (hex) then finish waiting
WAIT_FOR_TRIG=$h0 25 5 1000;

we cannot also create loops with [ ] brackets

so, my question is:
any ideas how to call command and then hold code execution until event will occur?

this problem showed me how small is our knowledge and how small more additional informations we can collect

BTW. no, i'm not a maniac - i'm not dreaming about bunch of papers with camera technical documentation in my hands

documentation with signature "owned by SE only, f*ck off"

cheers

Posted by number1
so your trying to create scenes like the k800i, most of the k800i scene settings including whitebalance are controled by the main, but in the k770i the scene whitebalance is controled by the driver.
you can get the k770 driver from http://www.4shared.com/file/3[....]b/K770_R8AA018_camdriver0.html

Posted by Raiderski
thx for replay but i'm not trying to implement scenes. i only need to find the way to hold code execution before events. both K750 and K800 have scenes (K750 has 6 types) defined in the hardware layer (camera DSP chip), probably they are almost the same settings. in K750 we don't have scene selection in menu but that's good, i didn't found anything useful in scenes (except scene 04 with forced ISO100) - auto mode rulez

Posted by lpachuong
A4A - 11.00 Final
http://www.mediafire.com/?4wdxvugynmk

There are two version, 1 for w800i/k750i and 1 for w810i with different compression.

Yellowish viewfinder is fixed
Fixed macro
No more test on compression => stable I gave up with this now.

Functions changed for w810i users:

EV_M_20= CYAN;
EV_M_17= RED;
EV_M_13= BLUE;
EV_M_10= YELLOW;
EV_M_07= ZOOM;
EV_M_03= ISO;
EV_0_00= FOCUS;
EV_P_03= EXPOSURE;
EV_P_07= SPOT;
EV_P_10= SHUTTER_SPEED;
EV_P_13= SATURATION;
EV_P_17= SCENE;
EV_P_20= SET_PROFILE; Raiderski's profile

NEW SHARPNESS + NOISE REDUCTION (Haven't tested on w810i at high compression)

Thanks to terminator, you have waken me up

I will stop for few days to carry on with my new idea.
Looking forward to your comments.

Enjoy.

Posted by tommymar

On 2007-12-18 18:08:53, metallica1 wrote:

On 2007-12-18 15:34:31, phoenix1985 wrote:
@metallica1:
So...your w800 never got crash with strong 5.6?
can you upload strong 5.6 camdriver that you used ?

Cheers...!

Your phone is w810i and that is why it is stable with any high compression.
Besides, Strong's driver has no compression, which means its compression is at default value (75%). (Search for Fine-Quality in prop_5_1 and you will see)

---------------------------
@lpachuong: Sound good. I will give it a try. Thank you.

Posted by lpachuong
@Raiderski.
If it is possible, we can force the events to work first, then use if/loop to regenerate the properties. That will be awesome.

Besides, as far as I know, we can force the phone to work on i2c address (in our case, it is 1F) to halt a step of a command. Hope this can help.

Posted by terminator17

On 2007-12-19 17:16:32, lpachuong wrote:
A4A - 11.00 Final
http://www.mediafire.com/?4wdxvugynmk

There are two version, 1 for w800i/k750i and 1 for w810i with different compression.

Yellowish viewfinder is fixed
Fixed macro
No more test on compression => stable I gave up with this now.

Functions changed for w810i users:

EV_M_20= CYAN;
EV_M_17= RED;
EV_M_13= BLUE;
EV_M_10= YELLOW;
EV_M_07= ZOOM;
EV_M_03= ISO;
EV_0_00= FOCUS;
EV_P_03= EXPOSURE;
EV_P_07= SPOT;
EV_P_10= SHUTTER_SPEED;
EV_P_13= SATURATION;
EV_P_17= SCENE;
EV_P_20= SET_PROFILE; Raiderski's profile

NEW SHARPNESS + NOISE REDUCTION (Haven't tested on w810i at high compression)

Thanks to terminator, you have waken me up

I will stop for few days to carry on with my new idea.
Looking forward to your comments.

Enjoy.

thanx a lot mate...just superb driver...u simply rock!!
thanx again...ur driver is just perfect for w810....

Posted by SPU
Raiderski
Events seems more tricky than we think about them...
Actually we don't need to "wait" the end of execution of previous command, but we need to remove generated event from the events queue to unlock further execution.
Very pity that we don't have some property called when frame changes...

Btw, you can check logging possibility in the next way:
insert somewhere code like this: $"text string %0" 06 02 00 01 04 61 #CMD_END;
if "log" command can't be executed, then interpreter will skip everything till the end of code part.
But... even if logging works... may be logs are available only in special "debugging" version of firmware or we need to modify some internal settings =/ Note, that log size is not limited (even if contains only one "session"), but logging lines are not removed from drivers.

Posted by chengrong

On 2007-12-19 18:24:28, SPU wrote:
Raiderski
Events seems more tricky than we think about them...
Actually we don't need to "wait" the end of execution of previous command, but we need to remove generated event from the events queue to unlock further execution.
Very pity that we don't have some property called when frame changes...

Btw, you can check logging possibility in the next way:
insert somewhere code like this: $"text string %0" 06 02 00 01 04 61 #CMD_END;
if "log" command can't be executed, then interpreter will skip everything till the end of code part.
But... even if logging works... may be logs are available only in special "debugging" version of firmware or we need to modify some internal settings =/ Note, that log size is not limited (even if contains only one "session"), but logging lines are not removed from drivers.

I think the log system is connected to the computer via USB.

Posted by Raiderski
1. events
that was easier than i expected, with simple test code i had results after 15 minutes. here they are:

51 = scene change started / change scene
EB = scene changed

small loop waiting for EB event resolved my biggest problem, finally i can release 6.7

2. log
i must fully agree with all comments. code interpterer does not remove line $"test" other code but $"" probably doesn't relate with txt file in filesystem. this doesn't make sense. the best way (as always) is to observe debugging results in realtime

- phone is connected to PC (with active supervising software) in some kind of service mode
-special firmware logging all operations with possibility to read them on demand

3. loop with [] brackets
doesn't work on our phones at all which is obvious when we see macros like WAIT_FOR_

Posted by Raiderski
MALICIOUS ISSUE!
all drivers are affected! (where zoom keys can control anything else than zoom)

modders and users should pay attention on this!

simplest path to reproduce in supermode drivers:

* = function example
** = value example

- go to EV value corresponding to manual focus control*
- set value to x1.6**
- go to EV value corresponding to contrast*

and from this point you have two ways:
1. use key 7 or camera menu to switch between normal/night mode
2. make photo

result: contrast* value x1.6** will be applied...
1. after normal/night switch
2. after back from still photo view to realtime viewfinder

path to reproduce in drivers with manual focus in macro mode:

- enable macro
- set value x1.6**
- turn off macro

result: zoom x1.6** will be applied

solution: block code execution in seq_set_prop_6 after every normal/night mode transition (key2, night mode in camera menu, $u07)

i checked also other transitions for example macro mode on/off (key 4 or camera menu) and they also generate issue

[ This Message was edited by: Raiderski on 2007-12-21 11:43 ]

Posted by leetiran

On 2007-12-19 17:16:32, lpachuong wrote:
A4A - 11.00 Final
http://www.mediafire.com/?4wdxvugynmk

There is WB bug in it because some cods are from raider6.6.1. replace the cods"#SSP_UNSET" after "seq_set_prop_7_0" and "seq_set_prop_7_1" with "$b6 00 4 1 #CMD(04,00)" seems can solve it.

Posted by Randolph
hello again... today I noticed a strange behavior in my pictures: When I open the with exif reader they all show prgCXC_125952_EU_1_CL 6.6
I have used since a long time the patch "move driver to another location"
This ...6.6 stays the same and does not respond what driver I use.
What stands behind this 6.6?
regards,
Randolph

Posted by Raiderski
nope, this will help only if you don't use manual shutter speed. if you use MSS then ISO100 scene will be activated and you will not retrieve automatic scene - this is very serious bug

problems with WB in 6.6.1 were due to scene changes in MSS which also affected noMSS mode. i spent one week trying to fix this and today i got full success in this matter

[ This Message was edited by: Raiderski on 2007-12-20 14:21 ]

Posted by Raiderski
Randolph
last post by lpachuong on this page:
http://www.esato.com/board/viewtopic.php?topic=135737&start=6675

Posted by leetiran

On 2007-12-20 14:18:53, Raiderski wrote:
nope, this will help only if you don't use manual shutter speed. if you use MSS then ISO100 scene will be activated and you will not retrieve automatic scene - this is very serious bug

problems with WB in 6.6.1 were due to scene changes in MSS which also affected noMSS mode. i spent one week trying to fix this and today i got full success in this matter

[ This Message was edited by: Raiderski on 2007-12-20 14:21 ]

Yes, you are absolutely right. It helps only on the other funtions except manual shutter speed. long for the raider6.7.

[ This Message was edited by: leetiran on 2007-12-20 15:15 ]

Posted by Randolph

Hello Raiderski, thanks for the hint to the comment on exif reader...
In you configtool I can en/disable filtering: Is this what you ment "enable pixel interpolation"= "bilinear filtering" on?

kind regards,
Randolph

Posted by Raiderski
Randolph
yes, exactly this what you wrote