3 Commits

Author	SHA1	Message	Date
markchien	e7ccfca9da	[Tether13] Move TetheringManager into framework ... Move tethering out of ConnectivityService. All client would use TetheringManager to talk with TetheringService directly. Bug: 144320246 Test: -build, flash, boot -atest TetheringTests Change-Id: Ib051bea724a256f9c4572b566e46ae7b9c4abe6e	2019-12-20 10:31:31 +08:00
markchien	eda5d30035	Change Tethering package name ... ".apex" is easy to confuse. Rename as below: apex: com.android.tethering.apex -> com.android.tethering apk: com.android.tethering -> com.android.networkstack.tethering Bug: 146471733 Test: build Change-Id: I2c7647abb996539a3af6cfe0e0214a5e8927c0d6	2019-12-19 12:57:39 +08:00
markchien	2c4cc6f514	[Tether07] Migrate Tethering into module ... Now tethering would be run in dedicated service. TetheringManager is the interface used to communicate with TetheringService. The new call flow would be: ConnectivityManager -> ConnectivityService -> TetheringManager -> TetheringService. Note: the return value of #tether(), #untether() and #setUsbTethering() APIs would always be no error. Client can use #getLastTetherError() or #getTetheredIfaces or listen tether state change to check status of corresponding interface. Bug: 136040414 Bug: 144742179 Test: -build, flash, boot -atest TetheringTests -atest FrameworksNetTests Change-Id: I7e78c0e0a3e70f940a749ba2a39ece7c7ec5b9b3	2019-11-29 07:05:21 +00:00