f778e2546f
This patch partially undoes ag/869831 (Change-Id: Ia42ed7aefaebd8caf3eada8e42b6cb7a940d7647) so that ConnectivityManager does not remove callbacks from its internal request-to-callback map at unregistration, but instead let the singleton CallbackHandler do it when receiving a CALLBACK_RELEASED from ConnectivityService. ag/869831 was thought to fix b/26749700 that reported a callback leak from sNetworkCallback, but a finer analysis of the code shows that callbacks were correctly removed by the CallbackHandler before ag/869831. There was therefore no callback leak. Bug: 26749700 Bug: 28537383 Change-Id: I421d889d0e225c0e3d1eebea664f44a1cc0f3191