{"push_id":667854921,"size":1,"distinct_size":1,"ref":"refs/heads/lp5.1","head":"6446b5bf7c7ccbb7e7463782b0aedc9028a9315b","before":"cdc4c31bd2c8aba71fff37cb5a40cd5a77bb92b4","commits":[{"sha":"6446b5bf7c7ccbb7e7463782b0aedc9028a9315b","author":{"email":"90b51f8a5079017e81711ae9317c35b0575b34e1@gmail.com","name":"Christopher R. Palmer"},"message":"telephony: Release pending network requests when releasing a request\n\nDuring system startup, a network request may move from the DctController\nto a network factory where it is held as a pending request until the\ntelephony state is fully initialized.\n\nWhen handling a releaseNetwork call, we must release the request\nfrom the pending queues of all network factories as well.\n\nWithout this fix, on boot it is possible for a network request to be\nadded and thne moved to the pending queue of a network factory.  Then,\nan attempt to release it will be a no-op instead of actually releasing\nthe network.\n\nThe end result is that the network request will eventually be executed\neven though it is no longer desired.\n\nIf WiFi is connected when the request is executed, then the cellular\nnetwork will get a data connection but the ConnectivityService will\ndeem the network uneeded and kill it.  After killing it, telephony\nwill automatically reconnect the network because it (incorrectly)\nbelieves that the network is needed because it was not released\nwhen it was supposed to be.\n\nChange-Id: Ifcb8676aec7a048e11de5a62103eb5f480566468","distinct":true,"url":"https://api.github.com/repos/TeamBliss-LP/android_frameworks_opt_telephony/commits/6446b5bf7c7ccbb7e7463782b0aedc9028a9315b"}]}