4653c0ac9e69b558672d255293fcf0a72f925e64

Currently host fills channel frequency in connect response buffer either by frequency of selected candidate or frequency present in connect request. Mostly upper layer sends a connect request with frequency = 0. So in case if connect request fails due to “no valid candidate found” for connection and with reason "Unspec failure", host sends frequency = 0 (present in connect req) to upper layer via an event EVENT_CONNECTIVITY_LOG. Fix is if frequency present in connect request use frequency else use frequency hint present in connect request to fill connect response buffer. Change-Id: Ic6eaf6cd26587bd2051c4449038009f08b9e2fad CRs-Fixed: 3638648
This is CNSS WLAN Host Driver for products starting from iHelium
Description
Languages
C
98.7%
C++
0.9%
Makefile
0.3%
Starlark
0.1%