diff options
| author | 2024-04-15 04:27:49 +0000 | |
|---|---|---|
| committer | 2024-04-25 14:29:40 +0000 | |
| commit | 858b14a912ff5ab5453bcb5b3107fd56ea8672dc (patch) | |
| tree | 6158149e8d5db0591acaae5747337c30ac4d8034 /libs/androidfw/StringPool.cpp | |
| parent | f1fc90bf73e6bb4569c98c01e2646b5351edc304 (diff) | |
Add config_enableTelephonyTimeZoneDetection.
AAOS Connectivity team is introducing minimal automotive telephony feature which would allow OEMs to pass MCC and NITZ signals without supporting FEATURE_TELEPHONY (adoption would take time though) and would make "FEATURE_TELEPHONY couldn't be relied upon" true. In future releases, we should remove the check for FEATURE_TELEPHONY at least for Automotive or for all form factors given FEATURE_TELEPHONY doesn't really "matter" to the time_zone_detector.
The other reason for landing this change is, as Neil mentioned, we're worried that there may be automotive devices out there that do have FEATURE_TELEPHONY. Automotive Settings is not ready to deal with this case and Automotive prefers simple settings because it's a edge case now. If OEM want to use it, they need to customize the Settings (at the end of the day, OEMs own the user experience on their devices). If minimal automotive telephony is adopted widely and OEMs actually pass MCC and NITZ signals to in-vehicle infotainment, AAOS can rethink / redesign the Settings.
Bug: 326140783
Bug: 336820570
Bug: 334817213
Test: build and run
Change-Id: I40b68ab025ab4e19995dbef3168e6b2e574ed549
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions