Notices

Works for me - neither white nor red LED flashes.

It uses RGB LED instead, flashing purple color for a split second, but it might be effect of some custom configuration and it's hardly noticable even when looking directly at screen turned on.

FCamera might also be a good choice because of storing TIFFs instead of JPEGs - photos don't show up in image gallery!

this might help too, haven't tried it though...
http://talk.maemo.org/showthread.php?t=86285

kernel-power have sysfs entry allowing to *completely* disable red "privacy" led, no matter of circumstances (so, it won't work, even when application try to light up this led explicitly, like Lanterne for it night-vision friendly torch):

Remember, you need Pali's kernel-power (in reasonably recent version, like not something 2 years old) for it to work, and it reset itself on reboot. Personally, I've this one-liner as script inside /etc/event.d/, so it sets itself automatically on every boot.

As for flash led, there is an option to disable it in camera-ui preferences - those two things combined worked for me in otherwise risky situations, but, in life-threatening ones, mechanical methods - like sticking it with tape - might be the most reliable thing.

/Estel

Sometimes, settings (for example white balance) are not saved between sessions, still trying to figure why...

According to:
http://talk.maemo.org/showpost.php?p...postcount=1674

...and:
http://talk.maemo.org/showpost.php?p...postcount=1675

...it seems that we actually have specialist(s?) interested in maintaining camera-ui FOSS replacement. That's great news! To celebrate it (and as an answer to request), I want to collect info about every bug/issue with replacement camera-ui (as opposed to stock camera-ui), test reproducibility on two devices (my daily one, and another one freshly reflashed with CSSU-Thumb *only*), and finally, post every and each one on bugs.maemo.org.

For this, I need your help - if you had buggy experiences with camera-ui replacement - even if your posts about it are burier somewhere in this long thread - please, repost it now. I'm dully noting everything on my todo-test lists. Input greatly appreciated.

Cheers,
/Estel

I remember camera-ui2 sometimes hung when recording a long 720p video. The preview became black and after some time it couldn't be stopped. You had to kill camera-ui2 and then recover the video.

I noticed that many "random" (i.e. non 100% reproducible) bgs are hard to report properly, due to complete lack of any logging in camera-ui(2) that I'm aware of. Is attaching gdb only way to obtain meaningful log, or there is some other mechanism that I'm not aware of?

I'd love to know this

Hi All!

I would be appreciate any help or advice for the following issue: I just installed latest CSSU stable on my freshly reflashed n900 and camera features are not available. I checked, it still runs camera-ui instead of camera-ui2.
My question: am I able to install camera-ui2 manually (from xterm of course...)? If yes, how should I do that; I mean: do I have to remove camera-ui first, or just apt-get camera-ui2...?
Sorry if I ask dumb question but I'm trying CSSU for the first time.

Thanks,

jm

AFAIK camera-ui(2) is available only for CSSU-Testing (or thumb), while you're using CSSU-Stable. You have to either switch to -Testing for this particular feature (and quite a bunch of other ones) - which is preferred way - or install camera-ui from CSSU-Testing separately - including all it's possible dependencies - creating some kind of hybid CSSU-Stable/Testing variant on your device.

I wouldn't recommend the latter, if you're not familiar with how repository system works in GNU/Linux -related operating systems. Not to mention that if you are familiar with it, there is no reason to use CSSU-Stable at first place...

/Estel