diff options
| author | Erik Kline <ek@google.com> | 2018-02-28 15:01:35 +0900 |
|---|---|---|
| committer | Erik Kline <ek@google.com> | 2018-04-08 18:28:15 -0700 |
| commit | 8067d78c32f545db6d35c660279ab3f2326ba41d (patch) | |
| tree | d1fed8f067d2774fb4b55922611cbf1f39f4d295 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | d61e87ad0899c8a737aa8f3f43b263bcee24325f (diff) | |
Don't unnecessarily reevaluate tethering provisioning
Registering for carrier config changes can deliver a sticky broadcast
and can cause Tethering to think something has changed and reevaluate
provisioning status, even though this has been checked before it
entered tethering mode alive state.
Additionally, move the provisioning_app{,no_ui} resources into the
TetheringConfiguration, if for no other reason than now we can log
it in .toString().
Test: as follows
- built
- flashed
- booted
- runtest frameworks-net passes
- manual USB tethering toward WiFi works
Bug: 69565814
Change-Id: Ib8b2620ce44c55e5eb0afd3f00f3f5aa4fc8a593
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions