am skip reason: Change-Id I37d0dc5ff41169b0309cfaabaa0f2595894b3749 with SHA-1 be117207cf is in history
Change-Id: I8eaaf2f3a0d12911ff144b77d3448a0a80f88ac5
mapping change.
Because currently we rely on eSIM module to do handle some slot mapping
change and single to dual SIM config change, eSIM needs to also make
sure uicc applications are enabled for certain scenarios. So we expose
the SubscriptionManager#setUiccApplicationsEnabled as @SystemApi
Bug: 141018421
Test: unittest
Change-Id: I9844e71260ea009afd0928a0f4be4426e7d12358
Current AOSP LTE signal bar has following limitation:
- For Threshold type, "RSRP & RSSNR" or "RSRP only" are selectable,
but "RSRP & RSRQ" is unavailable.
- For threshold value, RSRP is flexible by carrier config,
but RSSNR is hard-coded.
- The signal strength reporting criteria apply to only the RSRP.
This change allows following customizations by new carrier config:
- Threshold type can select "RSRP & RSRQ" too.
- Threshold value of RSRQ and RSSNR can be flexible.
- RSRQ and RSSNR thresholds can set signal strength reporting criteria.
Test: auto - Confirmed that run
FrameworksTelephonyTests#testSignalStrength and it has no problem.
Test: auto - Confirmed that run
FrameworksTelephonyTests#SignalThresholdInfoTest and it has no problem.
Bug: 133400544
Change-Id: I37d0dc5ff41169b0309cfaabaa0f2595894b3749
Merged-In: I37d0dc5ff41169b0309cfaabaa0f2595894b3749
Current AOSP LTE signal bar has following limitation:
- For Threshold type, "RSRP & RSSNR" or "RSRP only" are selectable,
but "RSRP & RSRQ" is unavailable.
- For threshold value, RSRP is flexible by carrier config,
but RSSNR is hard-coded.
- The signal strength reporting criteria apply to only the RSRP.
This change allows following customizations by new carrier config:
- Threshold type can select "RSRP & RSRQ" too.
- Threshold value of RSRQ and RSSNR can be flexible.
- RSRQ and RSSNR thresholds can set signal strength reporting criteria.
Test: auto - Confirmed that run
FrameworksTelephonyTests#testSignalStrength and it has no problem.
Test: auto - Confirmed that run
FrameworksTelephonyTests#SignalThresholdInfoTest and it has no problem.
Bug: 133400544
Change-Id: I37d0dc5ff41169b0309cfaabaa0f2595894b3749
am skip reason: Change-Id I588fd3b331380ff20762c24762e997d4a878cc44 with SHA-1 8649a91686 is in history
Change-Id: I1860aac732bbdf9dc1cdafdc919e33c3913ec3d4
TelephonyRegistry is using the deprecated constructor of
PreciseDataConnectionState; it should use the other constructor of
PreciseDataConnectionState, which is not deprecated; Also need to make
that constructor System API for Mainline.
Test: make update-api (no functional change in this CL).
Test: atest FrameworksTelephonyTests
Bug: 146793835
Change-Id: I83f98aa8b818f654d497867cd16e8afa987114fc
Update ACTION_PROCESS_WIFI_EASY_CONNECT_URI intent to include
additional information in case of a failure. The intent will
return an extra field with result code for R1 and R2 devices,
and additional details for R2 devices: SSID, channe list,
and band list.
Bug: 139381558
Test: Manual test
Change-Id: Ib25db37279289acbb3841f4b4862d8cbeb4efdd2
Since RouteSessionInfo and controlHints are passed
simultaenously, move controlHints into the session info
for simplicity.
Test: atest mediaroutertest
Change-Id: Id99e4d71744ab438e8fcd99101895c28e2585662
