am skip reason: Change-Id I0158d88e364772f9ac258bd18955edcdad266ad8 with SHA-1 e3b9708c3a is in history
Change-Id: Iee4232c13e9085ccab062bd9b1c6c05de4ca2c0e
am skip reason: Change-Id I7855090bffbe895c8349ad4903b8f2eb55515f0b with SHA-1 b8fecf4b32 is in history
Change-Id: I278c197256ccd394636c8283a5988ad57b5d7bfe
The NetworkStack.getService() API should be used instead.
Bug: 151243982
Test: atest FrameworksNetTests TetheringTests
Manual tethering test
Merged-In: I7855090bffbe895c8349ad4903b8f2eb55515f0b
(clean cherry-pick from internal branch)
Change-Id: If4af2846a82605e828287a9a4680d5547b76b802
am skip reason: Change-Id I7302cf351b0a9a42ad5a543f61ab084de189f282 with SHA-1 74165f0b29 is in history
Change-Id: I503b7fa51324c2e40e0e31e4e9c27048a93e6f23
am skip reason: Change-Id Idd041f0fbeca411ea23e49786a50dd7feb77ef45 with SHA-1 f1332573bb is in history
Change-Id: I124f0959b7a197607dd281fb3e00e640f10a8d37
am skip reason: Change-Id Iaf2ef5b5751eb208d119ddbc74481239366fe581 with SHA-1 49bdf5615f is in history
Change-Id: Icf93c1b23cfd39d899ba517ec6940b1cbd1991cb
am skip reason: Change-Id Icc4e59ce3b2d8d4c1c7883c2f9d040d3ce563f09 with SHA-1 1957e6a0fb is in history
Change-Id: I6c0eb4be6df9061dad68ecc20813ec379cb5b828
am skip reason: Change-Id Iaf85e800569f2e08c39f7ebb96f8aa34f6e53133 with SHA-1 d44de5a624 is in history
Change-Id: I92ddb40ed68a9aae85e5d402640fbade987e1369
am skip reason: Change-Id Idd041f0fbeca411ea23e49786a50dd7feb77ef45 with SHA-1 f1332573bb is in history
Change-Id: I3b914d7ea26dacf4e7cbebd0494d4c4c0b520c8c
am skip reason: Change-Id I87ef1d451eefa6998b9793c4eacabae978376d24 with SHA-1 ac580f9826 is in history
Change-Id: Ie5db8cb976a15fa9f16a8cc76a43f7d9a0ba9761
When the Ethernet interface becomes unavailable (e.g., because
the cable was unplugged or the interface was removed), or when
setEthernetTethering(false) is called, release the Ethernet
interface request.
This ensures that:
- The Ethernet interface immediately becomes available for use in
client mode.
- If an interface later becomes available, tethering is not
automatically started. This is consistent with what happens for
other downstream types such as wifi and USB. Evey time one of
those downstreams goes down, tethering is stopped and will not
be restarted.
Test: manual
Bug: 148824036
Change-Id: Iaf85e800569f2e08c39f7ebb96f8aa34f6e53133
Merged-In: Iaf85e800569f2e08c39f7ebb96f8aa34f6e53133
(cherry picked from commit e54c92e5657abe2ce5da9dcba76b89c5e540cc44)
When the Ethernet interface becomes unavailable (e.g., because
the cable was unplugged or the interface was removed), or when
setEthernetTethering(false) is called, release the Ethernet
interface request.
This ensures that:
- The Ethernet interface immediately becomes available for use in
client mode.
- If an interface later becomes available, tethering is not
automatically started. This is consistent with what happens for
other downstream types such as wifi and USB. Evey time one of
those downstreams goes down, tethering is stopped and will not
be restarted.
Test: manual
Bug: 148824036
Change-Id: Iaf85e800569f2e08c39f7ebb96f8aa34f6e53133