summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorJack Yu <jackyu@google.com>2018-03-14 16:23:38 -0700
committerJack Yu <jackyu@google.com>2018-03-15 10:38:48 -0700
commit29d07b5871cae8460ecd19b807b501df5b7d328d (patch)
tree1cf01e3e411966658f58675f8aa9acdf333bed28 /tools/aapt2/java/JavaClassGenerator_test.cpp
parente70b94815ace004578385615e9767add5286590d (diff)
Fixed data connection state callback not working
The old behavior of onDataConnectionStateChanged callback is that if at least one data connection for one APN type (e.g. default, mms, supl, ims, etc...) is connected, then it reports connected. It only reports disconnected if data for all APN types are disconnected. Since now we have data connections are always connected. For example, even if the user disables data, the unmetered IMS data remains connected. In this case the client's onDataConnectionStateChanged won't be called. Now we changed the behavior of onDataConnectionStateChanged to report the connection state for default APN type only. This matches the behavior of TelephonyManager.getDataState(). Test: Manual Bug: 73226433 Merged-In: I0744cf33337864c946af6e7d186bab78584acfa4 Change-Id: I0744cf33337864c946af6e7d186bab78584acfa4 (cherry picked from commit b1bac54d609703ec5fbc633fab89c73994289496)
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions