From e8db3ab5a2717f7df76ec2fa6c6b6058bbc9e30d Mon Sep 17 00:00:00 2001
From: Kweku Adams <kwekua@google.com>
Date: Wed, 27 Feb 2019 14:30:34 -0800
Subject: [PATCH] Adding UNKNOWN value to Job constraint change enum.

Proto best practices are to have the first value in an enum be similar
to UNKNOWN/UNSET/NONE.

Bug: 120941744
Bug: 120793892
Test: Android builds
Change-Id: I8a764565d14ad6dde93ebfcbd55fd37cf533b253
---
 cmds/statsd/src/atoms.proto | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/cmds/statsd/src/atoms.proto b/cmds/statsd/src/atoms.proto
index 1dd68df36ba8a..b6474001deba4 100644
--- a/cmds/statsd/src/atoms.proto
+++ b/cmds/statsd/src/atoms.proto
@@ -5528,8 +5528,9 @@ message ScheduledJobConstraintChanged {
     optional com.android.server.job.ConstraintEnum constraint = 3;
 
     enum State {
-        UNSATISFIED = 0;
-        SATISFIED = 1;
+        UNKNOWN = 0;
+        UNSATISFIED = 1;
+        SATISFIED = 2;
     }
     optional State state = 4;
 }