From 1bc9c3a22e3ad1e68b983cb999affb0dc6d9e5d8 Mon Sep 17 00:00:00 2001
From: Yi Kong <yikong@google.com>
Date: Tue, 23 Jul 2024 05:05:06 +0000
Subject: profcollect: fix camera event delay logic

Follow up to https://r.android.com/3186246, we should *not* delay trace capture, instead of always adding the delay.

Change-Id: I93d917963a1c73e4a28e945488b9b5cb1b16925b
Test: presubmit
Bug: 319394981
---
 .../com/android/server/profcollect/ProfcollectForwardingService.java | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/services/profcollect/src/com/android/server/profcollect/ProfcollectForwardingService.java b/services/profcollect/src/com/android/server/profcollect/ProfcollectForwardingService.java
index acdbbdee7d67..e6dac88f8a9e 100644
--- a/services/profcollect/src/com/android/server/profcollect/ProfcollectForwardingService.java
+++ b/services/profcollect/src/com/android/server/profcollect/ProfcollectForwardingService.java
@@ -398,17 +398,16 @@ public final class ProfcollectForwardingService extends SystemService {
                 if (randomNum >= traceFrequency) {
                     return;
                 }
-                final int traceDelay = 1000;
                 final int traceDuration = 5000;
                 final String traceTag = "camera";
-                BackgroundThread.get().getThreadHandler().postDelayed(() -> {
+                BackgroundThread.get().getThreadHandler().post(() -> {
                     try {
                         mIProfcollect.trace_process(traceTag, "android.hardware.camera.provider",
                                 traceDuration);
                     } catch (RemoteException e) {
                         Log.e(LOG_TAG, "Failed to initiate trace: " + e.getMessage());
                     }
-                }, traceDelay);
+                });
             }
         }, null);
     }
-- 
cgit v1.2.3-59-g8ed1b