Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 9257000c authored by Ruchit Sharma's avatar Ruchit Sharma Committed by Zhijun He
Browse files

camera: fix logging in ZslProcessor to avoid spam 

AF state mismatch while selecting ZSL candidate should not be treated
as a warning. This results into undesriable spam in the logs.

ALso, using ALOGVV is consistent with how AE state mismatch is handled
in ZslProcessor3.cpp

Bug: 18634318
Change-Id: Ia9d7f2bb98f784990b1a6f923983c35f622c3791
parent d6e7f1e1

services/camera/libcameraservice/api1/client2/ZslProcessor3.cpp

+1 −1
Original line number Diff line number Diff line
@@ -592,7 +592,7 @@ nsecs_t ZslProcessor3::getCandidateTimestampLocked(size_t* metadataIdx) const { 
                    if (afState != ANDROID_CONTROL_AF_STATE_PASSIVE_FOCUSED &&

                            afState != ANDROID_CONTROL_AF_STATE_FOCUSED_LOCKED &&

                            afState != ANDROID_CONTROL_AF_STATE_NOT_FOCUSED_LOCKED) {

                        ALOGW("%s: ZSL queue frame AF state is %d is not good for capture, skip it",

                        ALOGVV("%s: ZSL queue frame AF state is %d is not good for capture, skip it",

                                __FUNCTION__, afState);

                        continue;

                    }