Esato Mobile
Sony Ericsson / Sony : Software, Firmware and Drivers : Hybrid Camera Driver for W800i/K750
> New Topic
> Topic Locked
Esato Forum Index > Sony Ericsson / Sony > Software, Firmware and Drivers > Hybrid Camera Driver for W800i/K750 Bookmark topic
Page123 ... 462463464>

aksd Posts: > 500

I've just made a hybrid camera driver from the W900 and K75 camera drivers:

Changes: The exposure algorith is that of the W900
Jpeg Properties: Are that of the W900 with 95% compression
Video Recording: 15fps standard K750 algorithm

pics seem clearer but only if a few more people check it out can I be able to tell if its any different.

Driver is uploaded by using FAR plugin....please post and tell me if you find any difference in qualtiy.

V1.0 http://rapidshare.de/files/24059017/camdriver0.dat.html

EDIT: NEW updated driver with corrections in JPEG algorith and stable upto 97% compression with and without MXE

V1.1 http://rapidshare.de/files/24068004/camdriver0.dat.html


Version 2.72 with GUIDE:

http://rapidshare.de/files/28848119/camdriver0.dat.html

Regards,
Akshay

Camera Driver info

1. The information section can be changed-all values in hex.
2. We can initialise whatever functions we want in the initialisation section:
Syntax: 06 02 00 00/01(enable/disable) 00(Value eg:3 for full mode scanning.....adys driver I think this is the problem with macro...I have'nt opened it and read it but logically this has to be set to 00 or 03) 00(which is function number 08 for spot 41 for focus etc).
We can give ISO a fixed number....we can give brightness...sharpness etc... a fixed number, we can actually initialsie any function from Whitebalance to Scene.
3. Of course we cna increase bitrate to 15fps and no more anybody who claims more is crapping the hell out since hardware supports upto 14.99fps avg.
4. JPEG compression can be increased or decreased.
5. Night mode fps can be altered, and aperture maybe controlled.
6. Certain LED settings can be altered.
7. Change in zoom levels cannot be recognised by the phone since the actual algortihm resides in the main Flash(OS Kernel) although we can enable high levels of zoom in the driver initialisation.
8. The AE can be altered with values ranging from 0-30(have'nt tested greater)
9. We can mirror our images by intialsing the mirroring property.
10. Flicker can be set.

Basically we have decoded the entire driver and we have reached a saturation level. Now what we need to do is try to understand the EXPOSURE and ISO properties along with the QTABLE properties.

Some facts about ISO and Exposure:
Your brightness control on the joystick is in reality an exposure setting
If ISO is set on fixed at say 100 in driver initialisation then you will not be able to adjust exposure. Therefore ISO is dependant on the Exposure and vice versa.

So lets see where we go from here.

Regards,
Akshay




[ This Message was edited by: aksd on 2006-08-10 06:02 ]

[ This Message was edited by: aksd on 2006-08-17 15:35 ]
--
Posted: 2006-06-25 12:39:56
Edit : Quote

g-roxx0304 Posts: 127

Nice,I shall try it tonight.
--
Posted: 2006-06-25 12:43:01
Edit : Quote

HyperSpeed1 Posts: 16

well i tried your drivers quality looks better but i still get that maroon screen.

--
Posted: 2006-06-25 13:10:50
Edit : Quote

g-roxx0304 Posts: 127

it is much better.
after taking a pic,it saves much faster.
--
Posted: 2006-06-25 13:16:59
Edit : Quote

aremaboy Posts: > 500

Gee...you're all experts in modding...
--
Posted: 2006-06-25 13:23:05
Edit : Quote

dekson Posts: 90

As i can see for the first compression ( normal mode):

seq_set_prop_5_0=$z0 $p1 0e
$c1 00
the second compression (Fine mode).

seq_set_prop_5_1=$z0 $p1 0e
$c1 00
Please tell me where is 95% in your code, I am interested by the cam.code

in third if you look the size of your photos, they are divided by two.

Thanks in advance.

.DeXx.
--
Posted: 2006-06-25 13:43:21
Edit : Quote

aksd Posts: > 500

You would'nt have any phots with 100% compression......the columns have something called ERROR which i have no idea about.....look at picture for more details.


--
Posted: 2006-06-25 13:56:05
Edit : Quote

IRFCA_WDG-3A Posts: 359

Anyone used this driver, noticed any changes?
I am using a self-made verision of camdriver0 which seems to work fine so far. Is the picture quality of this hybrid driver better than the "tweaked" ones ('coz of W900 algorithm)?

I'm stuck with a Win98-running PC hence can;t check to see the changes on my phone, anyone posting a comparision would be great.
--
Posted: 2006-06-25 14:06:03
Edit : Quote

dekson Posts: 90

But, what are these lines?


seq_set_prop_5_0=$z0 $p1 0e
$c1 00
...
seq_set_prop_5_1=$z0 $p1 0e
$c1 00

When i modify the values after$c1 ( $c1 5f - for exemple 95%) the photos quality are better but the size is bigger.

Are you try with your modification and with my value only in fine mode ( i'm try like you find the best configuration for photos quality) :

-> seq_set_prop_5_1=$z0 $p1 0e
$c1 5f

@DeXx


[ This Message was edited by: dekson on 2006-06-25 13:11 ]
--
Posted: 2006-06-25 14:07:33
Edit : Quote

max_wedge Posts: > 500

aksd, this is top work mate, good to have someone looking at this.


--
Posted: 2006-06-25 14:10:58
Edit : Quote
Page123 ... 462463464>

New Topic   Topic Locked
Forum Index

Esato home