| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 7377541
Change-Id: I097f2288ebfc2b4a9782cbced19d9c36d0703acb
|
|
|
|
|
| |
Bug: 7227463
Change-Id: Iaa0df7522edc38d25fae2bbda8d24490e997e733
|
|
|
|
|
| |
Bug: 7427185
Change-Id: Ie669dff01af0865ea50305f3b48cf3f7af92cf6f
|
|
|
|
|
|
|
|
| |
Handling group removal at disconnect causes issues where supplicant keeps
the group and then the next invocation fails
Bug: 7403755
Change-Id: Iea7e5ec98486607f8e2c4a55be3743e0545a9da7
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Defer supplicant state change event so we do not miss it
Bug: 7394390
Change-Id: Ibae6cef6be42a6cb45dc20ba4fa5060d8e459217
|
|/
|
|
|
|
|
|
|
| |
Reset timeout for single interface architecture
Fix persistence reinvocation handling on the receive side
Bug: 7379336
Change-Id: Iacca0bd6dcbeb42af63bf2078e8cf3126e4e74a7
|
|
|
|
|
| |
Bug: 7379336
Change-Id: I20ead7e8c0d855be523bdfd8d9cb9eaa4b8fcac1
|
|
|
|
|
|
|
|
| |
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
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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 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
|
|/
|
|
|
| |
Bug: 7357742
Change-Id: I4d12d137b9d5ebf5c6739cbd4405de3f90a3d846
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|/
|
|
|
| |
Bug: 7326726
Change-Id: I6cca47a70cc0f29c68f922618cdcc181fb919a05
|
|
|
|
|
|
| |
had local changes from b/7318044
Change-Id: Idc6907d648a07d36f93dee859e361e9655cdd8e6
|
|
|
|
|
| |
Bug: 7318044
Change-Id: Icf27e823453eeaba901aad6f3f8eedea242794f9
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Remove all @Deprecated @hide settings, and clean up any stragglers.
Bug: 7232125
Change-Id: Ibf67093c728d4a28565129b923edb1701d3b2789
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| | |
| | |
| | |
| | |
| | | |
* changes:
Update references to migrated global settings.
Handle user switched for settings changes.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
|/
|
|
|
| |
BUg: 7223590
Change-Id: Id92699ae48ea75f94638fcc3bd776b863911985b
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
| |
Our device only supports STA & GC concurrency
Change-Id: I4f16c959a6f4e7ad5610dcae67be830d741f162c
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 7188646
Change-Id: I69f2c2581004b08730407930fb056cc1fe54feec
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
- Specificy max GO intent for WFD
- Increase GO idle time out to 20s and use it for GO and client
- Fix connection broadcast
Change-Id: Ia0e28bc9eb3e23d2830a6c814c5a537ca0bcd5db
|
| |
| |
| |
| |
| |
| |
| | |
Also reduce scan interval for STA scans to one minute.
Bug: 7138968
Change-Id: I03620f6d462e4ec90d9bb25bbfe709f63173df21
|
|/
|
|
| |
Change-Id: I7872dbea7dc30c57960af95e86eb8e4c7f8e92dc
|
|
|
|
|
| |
Bug: 7175460
Change-Id: Ibf5e063603866289b3dbae278bc384b833e4a75e
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Various wifi settings that are explicitly defaulted did not get their
default code properly converted to refer to the correct settings
database table.
A collection of moved-to-Global settings that had not yet been
marked @deprecated in the Secure.* namespace are now so marked.
Also updated the namespace used to refer to wifi settings from the
Wifi Service. These changes are cosmetic, but they do eliminate a
number of runtime log messages.
Bug 7153671
Change-Id: I9e5b6464d025cfb480ef97373996e38e82f90593
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Listen to screen broadcast all the time to avoid situations of losing
this information when wifi is turned on and off
Avoid duplicate suspend commands to driver
Bug: 7156907
Change-Id: I162b7ba249ae8925119a534229045965c0c13d1f
|
|/
|
|
|
|
|
| |
This is needed to work well with cavium dongle and 2 seconds
was too aggressive to let a client scan and connect.
Change-Id: Id3f1e3711333365c1e90827fb92675fd5dbc49da
|
|
|
|
|
|
|
|
|
| |
We were not handling disabling suspend optimization during DHCP. This can
cause problems with certain routers when screen is off (and suspend optimizations
enabled).
Bug: 7106423
Change-Id: Ib762fff2edec28d7c6990263d4b641566e971213
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Supplicant now passes as an ascii encoded string that allows it to
pass any sequence of bytes for a SSID. see src/utils/common.c in supplicant
for details of the implementation.
We create a SSID structure WifiSsid in framework to store the ssid and handle
the conversion appropriately when required for printing and for an application.
At this point, we still do not handle non-printable octets from an application perspective
for connectivity
Bug: 7110903
Change-Id: I520e5ee23baed4867b8b408bbb3eda5c9e92b6bf
|
|
|
|
| |
Change-Id: I6a57d90f3750590db4ac5d538956b989d9589501
|
|\ |
|