Sony Ericsson / Sony : Software, Firmware and Drivers : Super camera driver for k750/w800/w810
>
New Topic
>
Reply<
Esato Forum Index
>
Sony Ericsson / Sony >
Software, Firmware and Drivers
> Super camera driver for k750/w800/w810
Bookmark topic
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: 2007-12-20 03:18:12
Edit :
Quote
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: 2007-12-20 11:09:52
Edit :
Quote
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: 2007-12-20 13:12:25
Edit :
Quote
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: 2007-12-20 13:45:13
Edit :
Quote
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: 2007-12-20 14:10:33
Edit :
Quote
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: 2007-12-20 14:18:53
Edit :
Quote
Randolph
last post by lpachuong on this page:
http://www.esato.com/board/viewtopic.php?topic=135737&start=6675
--
Posted: 2007-12-20 14:52:36
Edit :
Quote
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: 2007-12-20 16:12:35
Edit :
Quote
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
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: 2007-12-20 21:16:01
Edit :
Quote
Randolph
yes, exactly this what you wrote
--
Posted: 2007-12-21 10:50:11
Edit :
Quote
New Topic
Reply
