Wi-Fi should be in active state during the entire DHCP process, and
shouldn't go to IEEE 802.11 power save mode. If the framework requests
scan during the DHCP process, the Wi-Fi chip has to start scanning
on channels different from the current one, and going to power save
mode is a prerequisite for scan. The result directly impacts user
experience: DHCP process takes longer, and even can fail.
Change-Id: I8171388bb70072e4c42cb3c074dd955da84e494b
Devices setting persistent_reconnect to 0 in wpa_supplicant returns "information is currently unable" error.
In that case, the connection establishment was always failed when the other device does NOT handle the invitation request.
So, try go-negotiation for interoperability.
Change-Id: Ia30a1c63d1bb4acc186a71248fb0aa5ea7edc627
Signed-off-by: Yoshihiko Ikenaga <yoshihiko.ikenaga@jp.sony.com>
Handling group removal at disconnect causes issues where supplicant keeps
the group and then the next invocation fails
Bug: 7403755
Change-Id: Iea7e5ec98486607f8e2c4a55be3743e0545a9da7
Reset timeout for single interface architecture
Fix persistence reinvocation handling on the receive side
Bug: 7379336
Change-Id: Iacca0bd6dcbeb42af63bf2078e8cf3126e4e74a7
Add appliance mode handling for WiFi Direct invitation dialog. Otherwise, no
way to accept connections.
Change-Id: Ic31b5bb25fed02848cf7c9e6418e21e9ab8b0cdd
We were doing a lazy shutdown and stopping supplicant behind p2p's back.
Make sure we stop p2p, before we go ahead with shutting down.
Bug: 7368832
Change-Id: I941e9cd69d6f27532207d3dc00b03c55c0e6335c
We now show a dialog to user and let him handle whether to choose wifi
or p2p when there is a frequency conflict.
If user chooses to disable wifi tempoarily, we disconnect wifi until
p2p connection is established and removed.
Bug: 6590401
Change-Id: I73871ddcb3732ae61997d8771b6aa90ad56270af
The root cause of why bssid needs investigation, but for now,
we can avoid crashing wifiwatchdog.
When bssid is null, just treat it as a good link.
Bug: 7357232
Change-Id: I080dfc990f3412646976cdc6ef75112ab093d326
We did not update a lost device notice to apps properly. This causes incorrect
connection initiation without a discovery which leads to failed invitation
requests to supplicant.
Bug: 7328758
Change-Id: If4b594c737d639d0f553188309319fba4e3ee7b7
We now get raw hex data from the supplicant and we convert it into
printable format.
For hidden access point, we always used to return a single empty string.
We need to make sure we maintain that behavior for apps to not start
displaying empty strings.
Bug: 7310749
Change-Id: I2599b9b5e15be91fc34e9af629ad893b1a0357fc
With the broadcom architecture, the p2p interface on a group
was dynamic that would just go away. Clearing addresses
was thus not important before.
It is good to clear up the addresses and reset connections
when the group is removed.
Bug: 7282358
Change-Id: Ia1a94fce90f86b54abcc2d1f78a33524ef8045fa
NetworkController misses the rssi state at boot. It gets the wifi
connection status because it is sticky. The rssi state will remain
out of sync until the wifi state machine sends another update which may
not happen if rssi does not change significantly.
Make rssi sticky as well to make sure NetworkController has the last known
signal strength on wifi.
Bug: 6916156
Change-Id: Id7dd621c6dbc35d7354757c61aa18a3b1ba90593
GO idle time out causes issues with multi-channel capable client which
can take longer to connect.
Use the supplicant default detection when acting as a GO.
Bug: 7254008
Change-Id: I6c40081cfa83ca0ddbb764640a48c92d69e609fd
Other fixes
- 20s idle time out was added a work around for an earlier cavium issue. Reduce to 10s
- Reload network fix when supplicant issues an error for a persistent network
Bug: 7248890
Change-Id: I6cea7c88c75aaca40ddcb973404e93ec0f66cbc4
This code was never supposed to have been there. It just remained
from an old implementation and actually results in
CS getting the wrong network info when both wifi and p2p are connected
Exposing p2p network type to CS needs to be done differently.
Bug: 7233984
Change-Id: I84a6091b8236cf5bdfcef3e7f626163d629e372d
Fixed one setting that was migrated but not marked deprecated.
Removed a hidden setting that is no longer used by the new
power manager service.
Bug: 7231172
Change-Id: I332f020f876a18d519a1a20598a172f1c98036f7
- Add wfdInfo details in group to allow display stack to filter
- Handle provision discovery failure and reset
- Do a discovery after group removal
- Handle failure to reinvoke and fall back to negotiation
- Avoid multiple REMOVE_GROUP calls that lead to removal
of persisted network
Bug: 7210856
Change-Id: Ia2e613e9b1191b919a185f0411439341e2e151bc
- NPE fixes
- Remove group on CTRL-EVENT-DISCONNECTED since the supplicant sometimes misses
the group removed event
- Fix the pattern match since we sometimes end up creating group without passphrase
Bug: 7119140
Bug: 7210558
Change-Id: I2cf0be073aaaaa9b931ea9a79b0bf4bd6a2b32ff
