News Forum Phone database

> New Topic
> Reply
< Esato Forum Index > Sony Ericsson / Sony > Software, Firmware and Drivers > Hybrid Camera Driver for W800i/K750 part 2 Bookmark topic

any driver that can modify Aperture setting ?
--
Posted: 2007-01-23 14:40:13
Edit : Quote


Quote:
On 2007-01-21 20:15:51, dennis.l wrote:
zuza1, 2 and 3 all give smaller file size. I use zuza1. it gives me a file size between 250k and 350k dependng on the subject.

zuza2 supposed to give even smaller file size than zuza1 and zuza3 drivers but I did not notice much difference when I compare the file sizes. usually I see only about 5K to about 15K difference (sometimes it's file size is bigger than zuza1 and 3).

I am not sure under what conditions it makes the file size smaller than zuza1 and zuza3. it may be the smaller size for zuza2 is for normal mode not fine mode (picture quality setting). does any one know?




Smaller means that the ammount of info in the picture will be smaller ... leading us to crappy pictures...

Zuza driver (no matter 1 or 2 or 3) are designed to give best performance @ decent size.

Let's take 1 line in camdriver:
$c0 08 #SET_JPEG_MIN(00,00)#SET_JPEG_MAX(02,1c)#SET_JPEG_AVG(01,90) #SET_JPEG_QUALITY

means:
#SET_JPEG_MIN(00,00) = 0 Kb
#SET_JPEG_MAX(02,1c) = 540 Kb
SET_JPEG_AVG(01,90) = 400 Kb

Now divide 540/2 = 270 Kb - picture but no larger than 400 Kb... for average normal photo.

The upper limit is for 540 Kb... meaning that the picture after all the computations in proc+buffer will be no larger than 540~600 KB

Now Think that the fone have those 32 mB in that chip as an hard drive fat 16. Between MAIN and FS is a small place =3~6 Mb that is filled with free block => free memory. My gues... is that there the OS makes the buffer for photos. And I belive I'm 89% true, because the guys with pathes use that place to store the modified bytes of information -> to small buffer size place -> to improper picture quality (@ begining of initialization in driver there are lines wich establish how big the buffer will be).

I'm not sure that everybody will understand something from present post... but the ones who does... will be able to mood the driver..
sort of my legacy .. so ... questions?
--
Posted: 2007-01-23 15:07:42
Edit : Quote


If i understand it correctly at what GxG told us... The OS is not using the available buffer correctly? I mean it doesn't fully utilize the amount of buffer it is using so the extra KB is a waste coz it must use all the space even though it doesn't need that... Am i getting anywhere? Coz its like in the world of PC, if you are using 2 memory stick, the other one is larger than the other, and you try to fit them both in the order of the lesser capacity first then the higher capacity next... It won't detect the higher capacity... You should put the higher capacity first then the lesser capacity second so it will detect both...
--
Posted: 2007-01-24 06:00:40
Edit : Quote


This is my latest camera driver and it might be my last. In this driver vers. 5.52 night photos are pretty god very bright i tried as much as possible to resolve any overexposure problems. On normal mode average file size at 300kb same quality as fine mode. At fine mode average file size 500kb. Reduced waiting times (ex: CMD_END macho had 5ms waiting time not it has 1ms waiting time)

Here is the link:

http://www.filefactory.com/file/04f3cf/
--
Posted: 2007-01-24 07:06:18
Edit : Quote


Zuza driver has a big problem.
Look at this:

SET_JPEG_MAX=06 02 00 0D !1 !0 #CMD_END;
SET_JPEG_MIN=06 02 00 0F !1 !0 #CMD_END;
SET_JPEG_AVG=06 02 00 11 !1 !0 #CMD_END;
SET_JPEG_QUALITY=07 02 00 13 $w2 $w2 $w2 #CMD_END;

Now look at this:

$c0 02 $s2 55 #JPEG_MIN(00,03) #JPEG_MAX(00,05) #JPEG_AVG(00,04) #JPEG_QUALITY $cl

It should have been:

$c0 02 $s2 55 #SET_JPEG_MIN(00,03) #SET_JPEG_MAX(00,05) #SET_JPEG_AVG(00,04) #JPEG_QUALITY $cl

The only reason it has such small file size is because the camera does not know what is the max or the min file size. So it is trying to make as small pictures as possible.

--
Posted: 2007-01-24 07:14:55
Edit : Quote


ady_k4e wrote:
Zuza driver has a big problem.
The only reason it has such small file size is because the camera does not know what is the max or the min file size. So it is trying to make as small pictures as possible.



Hehehe.. maybe.. maybe not, and far as I know is not a "problem".
As I said in the previous thread.. and also explained to toryx: it;s like in programing... you assign different tags to different operations. What is after = doesn't mean that is not correct. if you make like this:

driver = $s1
driver = $s2
driver = $s3
and then
$1~3 will have the values taken from 06 02 00 0D !1 !0 after 3 consecutive readings..
and if you use it like this:
$c0 02 $s2 55 #driver(00,03) #driver(00,05) #driver(00,04) #JPEG_QUALITY $cl

What makes you think that OS doesn't have the capacity to know that those values from $s1 $s2 $s3 are for JPEG MIN MAX and AVERAGE?

Did you wander why actualization service SEUS from SE flashes only FS and NEVER MAIN..when you UPDATED the phone? They didn't wont you to flash MAIN part...so.. my opinion is this

As I told you previous.. some lines of text are encrypted in OS.. and I believe the real "driver" is there. Camdriver0.dat is only an interface between SE and camera... to be able to change some settings by FS without flashing MAIN. I don't know if I make my self understandable )... but I believe this is the hole picture...
As I ran many test on my lost phone... I notice that camera works for so many lines of text removed from cameradriver0.dat Akhay notice first this "issue" and together we ran some test... and it is true. One other reason is that the phone doesn't let you run the camdriver0 without telling him that is Version 4.5 or the last one.. Why? because in other versions could be parameters and values not supported or not readable by OS...

So .. IMO you have to understand ALL story and then understand values.. because they are linked together...

and to answer to MarkJason:

Nope, not entirely true: there is a buffer space... if you fill that space with other things the OS knows that from 4010102$ to 4070102$ (just an example) the space is free for internal purposes/ and if you put patches... the OS will Know the same.. only that some bytes of info are linked to that space. examples:
In order that one command to work the OS runs some commands programed ( like player) from A to D.. You apply the patch and will be stored in that free space. Next time when you will run the player .. OS instead running from MAIN given space, it will be diverted to that free space as it was original ABCD, by-passing the original one. So you have results.. you have the original player(unused) and you have moded player in that free space witch will replace virtually the original player.
So you have double players.. one unused - but who will take some space. The moded player also.. The difference is that the moded one take space from another given tasks.. It's not much space.. but can make problems.. in a very strict space environment.
I hope you understand now...

[ This Message was edited by: gxg on 2007-01-24 07:09 ]
--
Posted: 2007-01-24 08:05:22
Edit : Quote


Ady, I add the line that you mentioned and took some pics. File size is about 350kb-400kb.
I guess it should be more than that. What do you thing?
--
Posted: 2007-01-24 08:12:01
Edit : Quote


Gun aiyden arinrin

Read my post above... that's why

Gule Gule
--
Posted: 2007-01-24 08:28:48
Edit : Quote


gxg the driver is initialized with SET_JPEG_MAX => you must use SET_JPEG_MAX not JPEG_MAX this is what i said. About 350-400kb file size it is because this are the limits that the driver is telling the camera. The simple fact that the file size is changed proves my point...
--
Posted: 2007-01-24 09:07:00
Edit : Quote


Quote:
On 2007-01-24 09:07:00, ady_k4e wrote:
gxg the driver is initialized with SET_JPEG_MAX => you must use SET_JPEG_MAX not JPEG_MAX this is what i said. About 350-400kb file size it is because this are the limits that the driver is telling the camera. The simple fact that the file size is changed proves my point...


ok.. but if it was wrong... if i omited to put SET_ and you are wright.. the driver won't work...

But is it working.. and I belive it is working without the hole line. And if I'm not wright.. How the OS does know hot to choose the size and what is min what is max and what is average...

that line was intended and it is not a mistake... I LET IT LIKE THIS ...

Try to learn what I said... you'll see that I'm Wright...

And if it's to make it like you... you'll see that nothing is improved... on contrary.. the picture will not gain extra info... only will slow you down in saving time.

Anyway... who likes it... can use... who want's to change it... FINE BY ME.. but I want to be specified that is "after zuza" or to specify my wrights or my involvment...

as GNU licence...



--
Posted: 2007-01-24 14:04:18
Edit : Quote

---

New Topic   Reply

Forum Index