From 2fd1499f6af3f066e7f2df3ddcd24c5f050f180a Mon Sep 17 00:00:00 2001 From: Remi NGUYEN VAN Date: Thu, 15 Nov 2018 11:23:38 +0900 Subject: [PATCH] (Really) fix LingerMonitor rate limiting The previous patch was applied to the wrong member and did not actually fix the issue. Bug: b/117516272 Test: remote run passed Change-Id: I3f9c27ebd6c339e98a71cb179b0be65950f9b864 --- .../java/com/android/server/connectivity/LingerMonitor.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/services/core/java/com/android/server/connectivity/LingerMonitor.java b/services/core/java/com/android/server/connectivity/LingerMonitor.java index 0e727c5e0b..929dfc4d15 100644 --- a/services/core/java/com/android/server/connectivity/LingerMonitor.java +++ b/services/core/java/com/android/server/connectivity/LingerMonitor.java @@ -90,8 +90,8 @@ public class LingerMonitor { mNotifier = notifier; mDailyLimit = dailyLimit; mRateLimitMillis = rateLimitMillis; - // Ensure that (now - mFirstNotificationMillis) >= rateLimitMillis at first - mFirstNotificationMillis = -rateLimitMillis; + // Ensure that (now - mLastNotificationMillis) >= rateLimitMillis at first + mLastNotificationMillis = -rateLimitMillis; } private static HashMap makeTransportToNameMap() {