Esato Mobile
Sony Ericsson / Sony : Software, Firmware and Drivers : Number1 4.7 FINAL, K770&T650 camdriver
> New Topic
> Reply
< Esato Forum Index > Sony Ericsson / Sony > Software, Firmware and Drivers > Number1 4.7 FINAL, K770&T650 camdriver Bookmark topic
Page <  123 ... 282930 ... 484950>

avril988 Posts: 43

Helo, im a new here, nice to meet u
i had tested with the latest 4.75 cam driver
download frm -> http://www.mediafire.com/?7t0hw5fzydb
my phone was R8AA018 firmware,
& yes it got nice quality picture & smooth video record,
good shutter speed,
but got two bugs here~
1. laggy on Night Landscape - after close camera on "Night Landscape" then reopen, it'll become laggy. but if u take a photo on laggy, it'll recover normal again. >
2. burn photo on Document - sometimes i got nice quality on Document mode too while take a shot on small things or else. but when i shot in a light complicated sides, i'll get a water color paint photo, dunno why -.-"
i had set whitebalance even on auto whitebalance, but still same~

anyway, thanks to number1,
Heard your good news soon
--
Posted: 2008-03-12 02:55:33
Edit : Quote

jigonx Posts: 327

about shutter speed..yes, i need longer shutter speed coz i like capturing city light at night. and yes, i'm using tripod.
the longest shutter speed i can get is only 1/2 second.

i know it's imposible to get very long shutter speed, but i think 2 second is posible and that's long enaugh for camera phone:)

about ISO, yes, i have added manual ISO to the camdriver.
with ISO 1600 or ISO 800, i can get the fastest shutter speed at 1/6400 second.
i think quick enaugh for camera phone.
--
Posted: 2008-03-12 05:58:05
Edit : Quote

geele76 Posts: 23

How you add manual ISO to camdriver0.dat in k770i? Sorry for my English!
--
Posted: 2008-03-12 06:37:02
Edit : Quote

nebraska Posts: 241

I'm interested too to have manual iso, if someone can helo
1600 is huge iso! photos should be very bright with a such iso rate
--
Posted: 2008-03-12 09:54:34
Edit : Quote

sp4ubw Posts: 5

Hello

My new driver based on the NUMBER1 and SE.

Changes:
1. Increased sharpness.
2. Increased buffer.
3. Changed watchdog timer to 255.
4. Improved WB range like a SE but with small changes.
5. video like NUMBER1 driver.
6. Smaller JPEG compression.
7. Eliminated crash if picture has much details.

Link: http://k750i.republika.pl/SE/4.8.zip



[ This Message was edited by: sp4ubw on 2008-03-12 11:48 ]

[ This Message was edited by: sp4ubw on 2008-03-12 11:49 ]
--
Posted: 2008-03-12 12:48:10
Edit : Quote

nebraska Posts: 241

hey cool we have a 2nd programeer in da place
Could you explain what are:

3. Changed watchdog timer to 255.
4. Improved WB range like a SE but with small changes.

thanks!

--
Posted: 2008-03-12 12:57:59
Edit : Quote

nebraska Posts: 241


On 2008-03-06 21:16:53, number1 wrote:
maybe the video fps is cauing problems with the sound sync, a couple more test version with increased compression
http://www.mediafire.com/?7t0hw5fzydb

also has any1 tried the night mode, or night landscape yet???? they should both be lighter with less noise.


hi number1
I've just tested your new drv (vers1), quality of videos is still better than beefore (good thing!) but the delay between image&sound is worse!
It is annoying, because pic quality is very good

--
Posted: 2008-03-12 13:10:26
Edit : Quote

sp4ubw Posts: 5

Yes of course:

this is first section

//SP4UBW values:
cam_ss_jpeg_buf_size_1=100000; //1MB
cam_ss_jpeg_buf_size_2=100000; //1MB
cam_ss_jpeg_buf_size_3=180000; //1.5MB
cam_ss_jpeg_buf_size_4=200000; //2MB
cam_ss_jpeg_buf_size_5=200000; //2MB
cam_ss_jpeg_buf_size_8=200000; //2MB

cam_watchdog_timeout=FF; // time for watchdog to timeout after recivied frame "DC"

cam_post_processing_11 = 1;
cam_post_processing_19 = 1;
cam_post_processing_20 = 1;

This is a time for watchdog timer to reset camera if receiving frame is to slow.

Second section:

Original SE:
seq_set_prop_0_0 = ;
seq_set_prop_0_1 = ;
seq_set_prop_0_2 = ;
seq_set_prop_0_3 = $p4 10
$c4 07 #WR_REG(0E, 86)
$cl #WR_REG(0E, 86) //-2.0
$cx ;
seq_set_prop_0_4 = $p4 10
$c4 07 #WR_REG(0E, 86)
$cl #WR_REG(0E, 85) //-1.7
$cx ;
seq_set_prop_0_5 = $p4 10
$c4 07 #WR_REG(0E, 85)
$cl #WR_REG(0E, 84) //-1.3
$cx ;
seq_set_prop_0_6 = $p4 10
$c4 07 #WR_REG(0E, 85)
$cl #WR_REG(0E, 83) //-1.0
$cx ;
seq_set_prop_0_7 = $p4 10
$c4 07 #WR_REG(0E, 84)
$cl #WR_REG(0E, 82) //-0.7
$cx ;
seq_set_prop_0_8 = $p4 10
$c4 07 #WR_REG(0E, 83)
$cl #WR_REG(0E, 81) //-0.3
$cx ;
seq_set_prop_0_9 = $p4 10
$c4 07 #WR_REG(0E, 02)
$cl #WR_REG(0E, 00) //0
$cx ;
seq_set_prop_0_a = $p4 10
$c4 07 #WR_REG(0E, 03)
$cl #WR_REG(0E, 01) //+0.3
$cx ;
seq_set_prop_0_b = $p4 10
$c4 07 #WR_REG(0E, 04)
$cl #WR_REG(0E, 02) //+0.7
$cx ;
seq_set_prop_0_c = $p4 10
$c4 07 #WR_REG(0E, 05)
$cl #WR_REG(0E, 03) //+1.0
$cx ;
seq_set_prop_0_d = $p4 10
$c4 07 #WR_REG(0E, 06)
$cl #WR_REG(0E, 04) //+1.3
$cx ;
seq_set_prop_0_e = $p4 10
$c4 07 #WR_REG(0E, 06)
$cl #WR_REG(0E, 05) //+1.7
$cx ;
seq_set_prop_0_f = $p4 10
$c4 07 #WR_REG(0E, 06)
$cl #WR_REG(0E, 06) //+2.0
$cx ;


//SP4UBW values:
seq_set_prop_0_3 = $p4 10
$c4 07 #WR_REG(0E, 86)
$cl #WR_REG(0E, 86) //-2.0
$cx ;
seq_set_prop_0_4 = $p4 10
$c4 07 #WR_REG(0E, 86)
$cl #WR_REG(0E, 85) //-1.7
$cx ;
seq_set_prop_0_5 = $p4 10
$c4 07 #WR_REG(0E, 85)
$cl #WR_REG(0E, 84) //-1.3
$cx ;
seq_set_prop_0_6 = $p4 10
$c4 07 #WR_REG(0E, 84)
$cl #WR_REG(0E, 83) //-1.0
$cx ;
seq_set_prop_0_7 = $p4 10
$c4 07 #WR_REG(0E, 83)
$cl #WR_REG(0E, 82) //-0.7
$cx ;
seq_set_prop_0_8 = $p4 10
$c4 07 #WR_REG(0E, 82)
$cl #WR_REG(0E, 81) //-0.3
$cx ;
seq_set_prop_0_9 = $p4 10
$c4 07 #WR_REG(0E, 01)
$cl #WR_REG(0E, 00) //0
$cx ;
seq_set_prop_0_a = $p4 10
$c4 07 #WR_REG(0E, 02)
$cl #WR_REG(0E, 01) //+0.3
$cx ;
seq_set_prop_0_b = $p4 10
$c4 07 #WR_REG(0E, 03)
$cl #WR_REG(0E, 02) //+0.7
$cx ;
seq_set_prop_0_c = $p4 10
$c4 07 #WR_REG(0E, 04)
$cl #WR_REG(0E, 03) //+1.0
$cx ;
seq_set_prop_0_d = $p4 10
$c4 07 #WR_REG(0E, 05)
$cl #WR_REG(0E, 04) //+1.3
$cx ;
seq_set_prop_0_e = $p4 10
$c4 07 #WR_REG(0E, 06)
$cl #WR_REG(0E, 05) //+1.7
$cx ;
seq_set_prop_0_f = $p4 10
$c4 07 #WR_REG(0E, 06)
$cl #WR_REG(0E, 06) //+2.0
$cx ;


//NUMEBR1 values:
//seq_set_prop_0_0 = ;
//seq_set_prop_0_1 = ;
//seq_set_prop_0_2 = ;
//seq_set_prop_0_3 = #WR_REG(0E, 86) ; //-2.0
//seq_set_prop_0_4 = #WR_REG(0E, 85) ; //-1.7
//seq_set_prop_0_5 = #WR_REG(0E, 84) ; //-1.3
//seq_set_prop_0_6 = #WR_REG(0E, 83) ; //-1.0
//seq_set_prop_0_7 = #WR_REG(0E, 82) ; //-0.7
//seq_set_prop_0_8 = #WR_REG(0E, 81) ; //-0.3
//seq_set_prop_0_9 = #WR_REG(0E, 00) ; //0
//seq_set_prop_0_a = #WR_REG(0E, 01) ; //+0.3
//seq_set_prop_0_b = #WR_REG(0E, 02) ; //+0.7
//seq_set_prop_0_c = #WR_REG(0E, 03) ; //+1.0
//seq_set_prop_0_d = #WR_REG(0E, 04) ; //+1.3
//seq_set_prop_0_e = #WR_REG(0E, 05) ; //+1.7
//seq_set_prop_0_f = #WR_REG(0E, 06) ; //+2.0


In the NUMEBR1 table values are still the same in all modes.
Originally depend at sensor and in my driver too but witch smaller changes to linearity this parametres.

That's all

Nebraska try to change this walues:

cam_post_processing_11 = 1;
cam_post_processing_19 = 1;
cam_post_processing_20 = 1;

enter on the beginning 1 into place 2, Nice effect





[ This Message was edited by: sp4ubw on 2008-03-12 12:18 ]
--
Posted: 2008-03-12 13:11:08
Edit : Quote

number1 Posts: > 500

the really big buffers aren't really needed the phone will never take a 2mb photo, i restored the old exposure property to stop doc mode over exposing, also adding more sharpness doesn't work well on this phone.
--
Posted: 2008-03-12 13:17:37
Edit : Quote

sp4ubw Posts: 5

Aha, i'm increased buffer at the begiining and and so stayed. Buffer from You driver is OK.

[ This Message was edited by: sp4ubw on 2008-03-12 12:27 ]
--
Posted: 2008-03-12 13:20:42
Edit : Quote
Page <  123 ... 282930 ... 484950>

New Topic   Reply
Forum Index

Esato home