Notices

And let us not forget the requested bug-reports. I just remembered myself.....

While a clever idea, IMO this shouldn't be a obvious setting in the UI or forced on everyone. Overclocking the device in applications is a blocker.
This would potentially make camera-ui2 depend on KP too which isn't a good idea.
I think it needs more thought, myself.

I didn't ever suggest doing an entry in the GUI. It would just tempt to break sth

The idea is that the power users could edit the scripts to do some power behavior

Already there:

https://gitorious.org/community-ssu/...i-set-priority

https://gitorious.org/community-ssu/...erface.c#L1079

https://gitorious.org/community-ssu/...erface.c#L1116

Nice to see mister freemangordon and the rest of the gang still doing work like this. Respect! And if I can help somehow, I'm here.

I pretty much like the idea, it makes for a nice generic interface to provide a thing commonly known as "hooks" and not really all that new (see http://mfnboer.home.xs4all.nl/twinkl...l#call_scripts for a pretty convenient reference implementation that I co-designed and recommend. sorry for the URL not really working, click on "Manual" and then on "Call Scripts") and it is independant of platform specifics like d-bus etc while still allowing to interface to those specific mechanisms with simple shellscript oneliners like "dbus-send"

Obviously you want to configure the full path&name of hook scripts inside the app via a user interface or config file of known name (or even direct gconf meddling though that again is platform specific dependency to gconf available), and you want to call such script with a rich environment(!) on every moderately relevant event like focus engage, focus release, trigger, app start, app close, review/gallery-open, gallery-close with delete, gallery-close w/o delete, a.s.o. And you frequently want the camera app to base further behaviour on return codes of the script called (given there exists such script to call) to e.g. close the cam app when the photo taken is ok by any postprocessing done in the hook - again see twinklephone for reference implementation.


I can see a few more nice usecases than just "enable/stop OC". E.G. how about uploading (in case of video, even streaming?) any media capture into "the cloud" so it's safe form any attempt to delete the record on device - I bet you know what I'm talking about.
Same scenario: make the camera automatically start video capture when camdoor gets opened while lens NOT pointing down to the floor, while when lens points down to the floor then the flashlight gets started and cam-app closed.
All of the above can easily get achived with a few lines in shellscripts doing the right thing when called by camera app

cheers
jOERG

Please help! Urgent!
Is it possible to disable flash LED on N900 altogether while taking photos? It might save my freedom and even life.
Police forces brought to Kiev from East represent, protect and work with mafia. They break a lot of laws themselves, shoot journalists, beat medics/red cross representatives, force official hospitals to pass injured to them without any treatment.
Please! ASAP!

int_ua,
the most reliable measure is to cover flash/privacy-LED with 3 layers of black sticky tape.
I just checked the CSSU "nikocam" (comes with CSSU-T) and it allows to disable flash, but still "flashes" the red tiny LED when taking a photo.
I can't come up with reliable better suggestions right away. rmmod adp1653 might help but I don't know what side effects and how reliable.

Good luck, take care!
jOERG

If making a video is acceptable solution then starting recording via icon on screen (not hw button - it triggers autofocus which turns on white LEDs on low light!) while covering camera hole with hand and then disabling the red LED with live focus ( http://maemo.org/packages/view/lfocus/ ) might work.

Be safe!

Use FCAMERA (NOT Bless) to take pictures. I justed tested it and it did not use the flash for focus. and use the tape as suggested by joerg.