News Forum Phone database

> New Topic
> Reply
< Esato Forum Index > Sony Ericsson / Sony > Software, Firmware and Drivers > Super camera driver for k750/w800/w810 Bookmark topic

@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: 2007-12-19 02:13:24
Edit : Quote



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: 2007-12-19 13:26:23
Edit : Quote


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: 2007-12-19 14:24:03
Edit : Quote


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: 2007-12-19 14:57:24
Edit : Quote


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: 2007-12-19 15:18:13
Edit : Quote


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: 2007-12-19 17:16:32
Edit : Quote




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: 2007-12-19 17:35:18
Edit : Quote


@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: 2007-12-19 17:54:45
Edit : Quote





thanx a lot mate...just superb driver...u simply rock!!
thanx again...ur driver is just perfect for w810....
--
Posted: 2007-12-19 18:20:22
Edit : Quote


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: 2007-12-19 18:24:28
Edit : Quote

---

New Topic   Reply

Forum Index