summaryrefslogtreecommitdiff
path: root/tests/Codegen/src/com/android/codegentest/SampleWithNestedDataClasses.java
diff options
context:
space:
mode:
authorMattias Nilsson <mattias.nilsson@sony.com>2020-01-24 17:49:49 +0100
committerMattias Nilsson <mattias.nilsson@sony.com>2020-07-27 17:30:27 +0000
commitf8c6f3483215b7a9401cb384980ccdb459f7261b (patch)
tree50fda765bf35b18071fb4f08e7215440d047eb28 /tests/Codegen/src/com/android/codegentest/SampleWithNestedDataClasses.java
parent1720916a971d9003b94e92ee56820a8cd16b7cbd (diff)
Move config_inflateSignalStrength to CC
Sim based customizations should not be resources because of two reasons: 1. The MCC/MNC value in AssetManager for Dual sim devices is undefined 2. There is no support for MVNOs. For dual sim devices there is only one value for MCC/MNC in AssetManager and that value is updated from multiple places without deciding if it should be the default voice sim card, the default data sim card or whatnot. This means that when frameworks is trying to decide what resource to use there is no guarantee that the resource that arrives is for the particular subscription we are asking for. MVNOs cannot be separated through only MCC/MNC but need more parameters like service provider, imsi, GID1 etc. MVNO support is available in CarrierConfig. When we now have support for ADCP updates of customizations and start using carrier id this is better placed in CarrierConfig, we then get support for MVNOs at the same time. Bug: 148483577 Test: Customize for sim card x and not for sim card y, insert both sim cards in a dual sim device and see the difference. Merged-In: I067d55b9ae5e1346dd3b3cd50a0097b05b100055 Change-Id: I067d55b9ae5e1346dd3b3cd50a0097b05b100055
Diffstat (limited to 'tests/Codegen/src/com/android/codegentest/SampleWithNestedDataClasses.java')
0 files changed, 0 insertions, 0 deletions