LOL thanks, but most of us here are CHDK geeks - the real ARM hackers that created this are VitalyB and GrAnd
(& the reason we're talking in English and not translating Russian), zosim (ewavr here), and then the floodgates opened, fingalo, mx3, and at least a dozen others have stepped into the code to get us where we are today... as well as another few dozen that contribute one of two things, but it all adds up. You can probably find the whole CHDK history on the
CHDK wiki.
There's even a special section on here called
Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes) that is specifically for screaming
THANK YOU!!! to the developers. :b
re: your problem, ahh that's not good. Intermittent trouble is worst thing to track down. re: battery strength, I don't think so. I have no experience with the S2, but of the CHDK-capable cameras I do have, they'll all run fine until the camera shuts down from low power.
This doesn't sound like a CHDK problem, but hey, more data always helps. Take a couple dozen images both with & w/o CHDK enabled, with both fast and slow shutter speeds. See if you can detect any commonality as to when this thing occurs.
Sadly there is a known condition where the screen goes black like that, the dreaded
stuck shutter (aka black screen of death) but the difference here is that you wouldn't get any images from when it sticks... they would either be nearly all black or all white. And you say it never happens w/o CHDK running, and this is a hardware problem so CHDK wouldn't matter. Well, if it
IS this problem, you'll know soon enough - they tend to stick permanently open/closed and require repair once they get "sticky".
If the shutter on the S2 is loud enough to hear the "click -- click!" when it fires, do you hear the 2nd click when the screen goes black?
