View Single Post
Posts: 18 | Thanked: 10 times | Joined on Jan 2011
#2945
Originally Posted by nicolai View Post
camera-ui2 uses the same auto-focus function as the stock
camera-ui, it is part of the camera-api (gstphotography)
And I saw some wired auto-focus behavior with the stock camera-ui as well.

[...]

It is the same behavior, just tested.

[...]

Do you have syslog installed and can you look if there are
any error messages logged.
I don't have syslog installed, but dmesg contains:
Code:
[90846.XXXXXX]  cam_focus (GPIO 68) is now active
[90849.XXXXXX]  af: af not configured
[90850.XXXXXX]  cam_focus (GPIO 68) is now inactive
[90853.XXXXXX]  cam_focus (GPIO 68) is now active
[90856.XXXXXX]  af: af not configured
[90856.XXXXXX]  cam_launch (GPIO 69) is now active
[90858.XXXXXX]  cam_launch (GPIO 69) is now inactive
[90858.XXXXXX]  cam_focus (GPIO 68) is now inactive
(I'm too lazy to copy this properly. so I typed the sub-second values in the log as XXXXXX.)

I get those entries with the stock camera-ui, too, but the "af: af not configured" isn't always there. Using macro mode or not doesn't seem to make any difference as far as the log is concerned (in stock, didn't test camera-ui2).
With stock, I was able to reproduce the focus bug relatively consistently by holding the focus button for ~half a minute before triggering the photo. With camera-ui2 it occurs regardless, and pretty much all the time.

I noticed that the difference between stock and ui2 is greatest when I'm in a dark room at night. Stock will still focus and produce a picture that is light enough to make out while ui2 will always (in my last 15 attempts) focus too close to the device and produce a picture that is too dark to make out.


I hope this gives you something to test as I can't be switching between the two due to lack of time. My dmesg for ui2 only included 3 or 4 pictures, one of them in macro mode (the rest I don't remember the settings for).
 

The Following User Says Thank You to ancow For This Useful Post: