| 4e1f32efceee1db37bfb1e2624b434dbfb055686 |
|
07-Sep-2016 |
Mitchell Wills <mwills@google.com> |
Add a flag to indicate if a ScanData is for a scan for all channels
BUG=30897947
Change-Id: I989a25dd3df3f473090b76b4e3cb798a2d513490
/frameworks/opt/net/wifi/tests/wifitests/src/com/android/server/wifi/scanner/SupplicantPnoScannerTest.java
|
| 1bf983a4211f547593a60523e43112ecdb5c8997 |
|
15-Aug-2016 |
Roshan Pius <rpius@google.com> |
SupplicantWifiScannerImpl: Restart PNO on settings change
When a new network is added, ConnectivityManager will stop/restart PNO
scans. However because of the 5 second debounce logic in HwPnoDebouncer,
this toggle will not be sent to wpa_supplicant. So, force restart PNO in
SupplicantWifiScannerImpl whenever there is a change in the network list .
PS: wpa_supplicant already has some internal logic to handle network
additions when PNO scans are running. But, not sure if this is working
as intended.
BUG: 30833790
Change-Id: Ib328abd866298a8a672a2f19fc863ee515dcbe74
TEST: Added unit tests
/frameworks/opt/net/wifi/tests/wifitests/src/com/android/server/wifi/scanner/SupplicantPnoScannerTest.java
|
| e483fd4a3151e59b3d0a596572b4d9f035fa8424 |
|
09-Aug-2016 |
Roshan Pius <rpius@google.com> |
SupplicantWifiScannerImpl: Ignore PNO stop failure
Ignore PNO stop failures when resetting the |mCurrentPnoState| flag. The
stop PNO command failure indicates that wpa_supplicant has already
stopped PNO scan internally. So, we should reset our flag to reflect that.
Otherwise, the next attempt to turn on PNO scans will be silently ignored by
|SupplicantWifiScannerImpl|.
BUG: 30764879
Change-Id: If75993ebe3bfc853628a96a698bb5806f0da5962
TEST: Unit tests
TEST: `act.py -c connectivity_basic.config -tb basic_wifi_tethering -tc
TelLiveDataTest:test_lte_wifi_switching`
/frameworks/opt/net/wifi/tests/wifitests/src/com/android/server/wifi/scanner/SupplicantPnoScannerTest.java
|
| ee0ab818341d44614ffe56ae73ecc08b974c2cbb |
|
20-May-2016 |
Roshan Pius <rpius@google.com> |
Change clock for time interval/elapsed measurments
1. Use the clock retrieved from WifiInjector in more modules: QNS,
Scanner, WifiConfigManager.
2. Use |elapsedRealtime| for time interval/elapsed measurments. Things
like scan results, config elements still continue to use
|currentTimeMillis|
Also,
1. Had to make |tryEnableQualifiedNetwork| public to prevent mockito from
calling the real method in WifiConfigManager.
2. Move keystore also into WifiInjector.
BUG: 28299258
BUG: 28824635
Change-Id: I91272aa5665abb741da7530d8920d09c8c5ea41f
TEST: Compiles & unit-test passes
/frameworks/opt/net/wifi/tests/wifitests/src/com/android/server/wifi/scanner/SupplicantPnoScannerTest.java
|
| a8367288377cbaed6371256ca837b7aa22280706 |
|
11-Apr-2016 |
Mitchell Wills <mwills@google.com> |
Move WifiScanner related code to scanner package
Change-Id: I73d01fe4d0de99a4e9758353cacf1d7a790cf040
/frameworks/opt/net/wifi/tests/wifitests/src/com/android/server/wifi/scanner/SupplicantPnoScannerTest.java
|