7fbcae6efd5c02fddb1dc5ddbcd6f2868f774131
Now that providers can report their status, we can use this to trigger telephony fallback mode. This opens the door to more sophisticated mechanisms for things like flight or tunnel detection. After all, providers know how they work and what they can / cannot do, and may have access to sensors and providers that the platform has not. The new "provider reported" flight mode entry cannot replace the "time_zone_detector"-level behavior entered via calls to TimeZoneDetectorStrategy as provider status is new and optional; providers are not required to report their status so it can be omitted. Bug: 236624675 Test: atest services/tests/servicestests/src/com/android/server/timezonedetector/ Change-Id: I89fb889ba98b3ddedd271670db09f1bb9df95644
…
…
[conflict] Merge "Fix errorprone warnings that should be errors" am:
677d6cd780 am: f9df26ae3c am: d3c499dabc
…
…
…
…
…
Merge "Revert "Fixed animation breakage when QS area tapped during expand/collapse"" into tm-qpr-dev am:
4f76d7728b am: 8a0a7c7b86
Merge "Letterbox Reacheability Multiplier Persistence" into tm-qpr-dev am:
a8117a579f am: 82a3d574a0
…
…
…
…
…
…
…
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%