CDD: Tighten SR to MUST for HOT GNSS TTFF to 5 sec to keep consistency with
CTS
- Fix the number and update SR to MUST to align with CTS test.
Bug: 74593141
Test: All existing test passes.
Change-Id: I126b297b2c7316538d26932c67d52081689a8d4a
diff --git a/7_hardware-compatibility/7_3_sensors.md b/7_hardware-compatibility/7_3_sensors.md
index 8da2e19..ffcbc2f 100644
--- a/7_hardware-compatibility/7_3_sensors.md
+++ b/7_hardware-compatibility/7_3_sensors.md
@@ -203,12 +203,11 @@
form of Assisted or Predicted GPS/GNSS technique
to minimize GPS/GNSS lock-on time (Assistance data includes Reference Time,
Reference Location and Satellite Ephemeris/Clock).
- * [SR] After making such a location calculation, it is
- STRONGLY RECOMMENDED for the device to
- be able to determine its location, in open sky, within 10 seconds,
- when location requests are restarted, up to an hour after the initial
- location calculation, even when the subsequent request is made without
- a data connection, and/or after a power cycle.
+ * [C-1-6] After making such a location calculation, device
+ implementations MUST determine its location, in open sky, within
+ 5 seconds, when location requests are restarted, up to an hour after
+ the initial location calculation, even when the subsequent request is
+ made without a data connection, and/or after a power cycle.
* In open sky conditions after determining the location, while stationary or
moving with less than 1 meter per second squared of acceleration:
