No description. Add one?
- Java 78%
- Kotlin 11.8%
- AIDL 4.4%
- C++ 3.7%
- C 1.5%
- Other 0.5%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
77ea93bbfb
Many applications use ConnectivityManager without needing TetheringManager (or without calling legacy ConnectivityManager methods that delegate to TetheringManager), so initializing TetheringManager when ConnectivityManager is created wastes resources. This is especially true considering that TetheringManager is not trivial to initialize (worst case scenario it starts a thread and does multiple Binder requests), and ConnectivityManager is created in ActivityThread when setting up the app proxy on startup. Bug: 190556328 Test: atest FrameworksNetTests CtsNetTestCases TetheringTests Original-Change: https://android-review.googlesource.com/1736505 Merged-In: I2ba7b8f2b9e1c934cfb082776b8d643f2f2c17e5 Change-Id: I2ba7b8f2b9e1c934cfb082776b8d643f2f2c17e5 |
||
| framework | ||
| service | ||
| tests | ||
| Tethering | ||
| .gitignore | ||
| OWNERS | ||
| PREUPLOAD.cfg | ||
| TEST_MAPPING | ||