Notices

I use CSSU-Thumb, which is CSSu-Testing compiled for thumb + sometimes, more bleeeding-edge versions of some packages (although, considered safe for use).

Hoever, while CSSu-Thumb is latest and greatest re N900's performance, it require kernel containing approriate fixes, and at least slight understanding what the whole thumb thing is all about. If you don't feel confident with it, and/or don't have time to read upon it and learn what it is about, you should be perfectly safe using CSSU-Testing.

In perfect world, the Stable version you're using would be perfect for your use case - but in reality it is extremely poorly maintained (lack of people interested in it, versus Testing, which leaves individuals immersed in Maemo to rather shallow level, as Stable maintainers), updated "once in a great bell", thus, as you noticed yourself, severely outdated, lacking major improvements and functionalities.

/Estel

Is somebody still working on camera-ui?

Bug N1: Quality of photos made with camera-ui is worse (more pixelized) than taking a photo with the following simple command line:
Bug N2: tunes compression quality.

Setting
in gdigicam-camerabin.conf does NOT work(may be related to gdigicam packages)


Bug N3:
Setting
tab in gdigicam-camerabin.conf does NOT work(may be related to gdigicam packages) and I can't change the default pixel format (UYVY) to (better) YUY2

I can prove all these 3 bugs if needed.

As requested in http://talk.maemo.org/showthread.php...41#post1371341 I took not 1, but even 3 pictures with my N900 (CSSU Stable - 21.2011.38-1Smaemo6.1, kp52, camera-ui 1.1.29.1+0m5). Here are the pictures:

• http://dev.miskiewicz.org/upload/20130902_001.jpg
• http://dev.miskiewicz.org/upload/20130902_002.jpg
• http://dev.miskiewicz.org/upload/20130902_003.jpg

All settings on "Auto", first two were made from 15-20 cm, third from ~30 cm.

here is one taken with CSSU-T:


This was taken with stock camera but I also observed that there's a difference in the exposure of images with and without the fcam driver. There is a tendency for the images to overexpose when fcam is installed and the white balance also seems affected (in my own experience). I don't know how that affects stock camera behaviour/processing but that is what I observed which is somewhat reflected in the opinion of other people here. http://talk.maemo.org/showpost.php?p...postcount=1046

yup fcam drivers mess with camera its very annoying

I uninstalled the fcam and I still get slightly overexposed shots..
And when i try to underexpose a shot, the viewfinder gets black and the camera app turns off.
Any suggestions?
IF shots are needed I'll provide them.

PS I managed to get a few underexposed shots with Auto ISO but if i put ISO to 100, I get the problems mentioned above.
And I use my N900 for macro so it really is annoying to not have good contrast and blown out highlights.

EDIT: I'm using CSSU-Testing.

You will need a reboot to properly clear out the fcam drivers.

In my experience the only ev failure is -0,5. iso 100 is very insensitive so the screen may look dark if lighting is sub-optimal. App closing not known to me.

The reboot didn't solve anything (I rebooted it in the first place)
So I must underexpose almost all the time.
IT's ok if I don't change the ISO.

Did you get any change in exposure behaviour with the removal of blessn900/fcam? IOW are you saying changed but it still sucks or there is no difference at all.

The -0,5 ev failure was a biggie for me as IME it is the most used and so I use fcamera and blessn900 mostly.

I didn't get any change whatsoever.
And the difference between -0.5 and -1 is really big.