Downgrading to P2 because if the message doesn't get sent, it's not the end of the world. The phone will disable its hotspot automatically after a short period of inactivity.
There are 2 parts to this fix:
(1) Refactor TetherDisconnectorImpl. Currently, it disconnects from the Wi-Fi network, then sends a DisconnectTetheringRequest to the host. We need to separate these two actions so that the "sending the request" part is in its own class. Once it's part of its own class, it should be called from TetherDisconnectorImpl.
(2) When a Tether network is disconnected, send a DisconnectTetheringRequest. This should be done within TetherNetworkDisconnectionHandler; you can call into the same class that you created in part 1.
Note: For step (2), I *think* that TetherNetworkDisconnectionHandler should work, but I'm not 100% sure. Before starting the implementation for part (2), please add some logs in that class to ensure that this code path is actually executed in this situation.
This bug requires manual review: We are only 2 days from stable.
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), ketakid@(ChromeOS), govind@(Desktop)
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by khorimoto@chromium.org
, Aug 4 2017