Remove keypad from WPS configuration method of BSS enrollee
becuase JB UI does NOT support keypad, only supports pbc and
display.
Change-Id: I9ab6f1514805e8307b46e38261f1c657568aeb59
Signed-off-by: Yoshihiko Ikenaga <yoshihiko.ikenaga@jp.sony.com>
Reading empty and not updating was resulting in retaining old values
in a config. Also, fix matching phase2 entries.
Additionally, allow configuring subset of enterprise fields. Necessary
since password cannot be read back from supplicant.
Change-Id: I83a01690a0cf7cad1457a674f50f1e3a1a0441b5
To remove any doubt about how java is doing its byte/integer arithmetic
use readUnsignedByte instead of readByte.
Change-Id: I5bdc200ed0cda51ad739804ac1d8d13c043424ec
- Clean up handling of mSavedPeerConfig
- Add argument protection
- Split out WPS handling on GO into a separate API. This was almost hacky
right now for applications and was working in an undocumented way
- Refactor connect function call and fix updating group capability
Change-Id: I26211c72ad60c6b6c939ad7473fcf2fc633f3010
This was a hidden API that has little value in being exposed due to
persistence now being supported on the platform.
The only use case for this is NFC, and we are going to add support
for that in official way
Change-Id: I20d97c8fd81e50fc610b4983b613e26ebaa72578
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
