From 9aaf96f5d7ff8e16c9803a85de52fee411289b1b Mon Sep 17 00:00:00 2001 From: Vishnu Nair Date: Mon, 9 Nov 2020 17:53:07 -0800 Subject: Change severity of "No local sync point found" logs These logs can be generated during normal operation and does not necessarily indicate an error. Change them to verbose to reduce noise when investigating issues. Bug: 172405302 Test: open app, check there are no error logs from Layer Change-Id: Ibc57c399b27c72bb8a1f2c2aa98f33c96e334bd2 --- services/surfaceflinger/Layer.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'services/surfaceflinger/Layer.cpp') diff --git a/services/surfaceflinger/Layer.cpp b/services/surfaceflinger/Layer.cpp index b60acde2a6..c0b3d4d89f 100644 --- a/services/surfaceflinger/Layer.cpp +++ b/services/surfaceflinger/Layer.cpp @@ -851,7 +851,7 @@ bool Layer::applyPendingStates(State* stateToCommit) { // If we don't have a sync point for this, apply it anyway. It // will be visually wrong, but it should keep us from getting // into too much trouble. - ALOGE("[%s] No local sync point found", getDebugName()); + ALOGV("[%s] No local sync point found", getDebugName()); popPendingState(stateToCommit); stateUpdateAvailable = true; continue; -- cgit v1.2.3-59-g8ed1b