diff options
| author | Rambo Wang <rambowang@google.com> | 2020-05-08 14:50:21 -0700 |
|---|---|---|
| committer | Rambo Wang <rambowang@google.com> | 2020-05-11 09:44:49 -0700 |
| commit | 35c8eb194a8baa184521f46ba3c5711265c759b2 (patch) | |
| tree | 0f06c9ec3216be0179bbb9932413842bb6a3db80 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 97e6f46cbb7c209ae33d0080b87d4564b7da2b6c (diff) | |
LTE+ indicator not shown when attached to CA network
NetworkTypeController (or DcTracker in aosp/master) will set lte
display type to LTE_CA when current ServiceState fulfills one of the
following conditions:
- getDataNetworkType return NETWORK_TYPE_LTE_CA
- isUsingCarrierAggregation return true
NetworkRegistrationInfo#getAccessNetworkTechnology() always returns LTE
when data rat is LTE CA. So the first condition will never get
fulfilled.
isUsingCarrierAggregation flag will only get updated when
ServiceStateTracker calls RatRatcheter.ratchet without location change.
This makes isUsingCarrierAggregation flag not always reliable to
determine if carrier aggregation is on.
The CL fix the issue by changing ServiceState#isUsingCarrierAggregation
to return true when ServiceState#getCellBandwidths return more than one.
The same condition is already used by RatRatcheter when set
isUsingCarrierAggregation flag in RatRatcheter#ratchet.
Bug: 154060784
Test: atest com.android.internal.telephony.ServiceStateTest
Test: atest android.telephony.cts.ServiceStateTest
Merged-In: Ie6c07cb58d2a40eeb10e8f0131c98212ba463517
Change-Id: Ie6c07cb58d2a40eeb10e8f0131c98212ba463517
(cherry picked from commit 8a41bbf466e78a63828ba03dde754f6879ad7e34)
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions