From eb59c45ae4c71da83ba281cd9cec1e0633ad905f Mon Sep 17 00:00:00 2001
From: Jan Althaus <jalt@google.com>
Date: Thu, 14 Sep 2017 10:10:36 +0200
Subject: [PATCH] Removing redundant setTimestamp call

As per the documentation, client supplied values are ignored and the timestamp is set when the log is persisted.
This is purely a cosmetic cleanup and doesn't change behaviour.

Bug: 64914512
Test: Confirmed in MetricsReader impl that timestamp is overridden, and tested logcat output for regressions.
Change-Id: Ia7db6410f82f08fe501607def0a87925a6aa9329
---
 .../view/textclassifier/logging/SmartSelectionEventTracker.java  | 1 -
 1 file changed, 1 deletion(-)

diff --git a/core/java/android/view/textclassifier/logging/SmartSelectionEventTracker.java b/core/java/android/view/textclassifier/logging/SmartSelectionEventTracker.java
index d9fb4cc7a3f5e..09e58ed77b84e 100644
--- a/core/java/android/view/textclassifier/logging/SmartSelectionEventTracker.java
+++ b/core/java/android/view/textclassifier/logging/SmartSelectionEventTracker.java
@@ -136,7 +136,6 @@ public final class SmartSelectionEventTracker {
                 .setType(getLogType(event))
                 .setSubtype(event.mEventType)
                 .setPackageName(mContext.getPackageName())
-                .setTimestamp(now)
                 .addTaggedData(START_EVENT_DELTA, now - mSessionStartTime)
                 .addTaggedData(PREV_EVENT_DELTA, now - mLastEventTime)
                 .addTaggedData(ENTITY_TYPE, event.mEntityType)