qcacld-2.0 to qcacld-3.0 propagation uOsRequestedHandoff is not reset in many scenarios after reassoc fails/timeout. Due to this if the next connect request initiate scan for ssid to find the AP in local cache, the scan for ssid complete handler think that OS requested handoff is in progress and returns without initiating the connect or connect failure. Thus the HDD remains in connecting state and after that scans fails. To fix this reset uOsRequestedHandoff whenever reassoc fails Change-Id: Ife9ee885cc1638f2bc4e02fd91b000c6e00f0689 CRs-Fixed: 1101706 |
||
---|---|---|
.. | ||
inc | ||
src |