GitLab

System UI acts on behalf of the current foreground user and should
thus be allowed to connect to WiFi networks, even if it actually runs
as user 0.

BUG=28799309

Change-Id: I50c3bdf30c9a1fd7780b47cac3f8ff3d0fb34f36

Bug:29360310
Change-Id: I00f83d9413d4673c3419b8dd6444db1efbf8ff1b

Change-Id: Ia212840fcf781740d5e185d3e3c2e30a477e25f0
Fixes: 29250616

The SignificantChange state machine doesn't actually have a concept of
if Wifi is on or not. This will simply ensure that it is not possible to
cause a crash.

Change-Id: I8ff87364bf7d5c87f0519b6cdc32d164facf30eb
Fixes: 29237535

Change-Id: Ia212840fcf781740d5e185d3e3c2e30a477e25f0
Fixes: 29250616

Adds a wifi metric that records the capture duration period represented
by the WifiLog proto. This is to improve the way wifiLogs are weighted when
aggregated.
Modified WifiMetrics to use the Clock wrapper of SystemClock to
facilitate unit tests.

BUG=29185886

Change-Id: I61dd2b481c26f0ea21bcb280ce1d40f3d73b7625

The SignificantChange state machine doesn't actually have a concept of
if Wifi is on or not. This will simply ensure that it is not possible to
cause a crash.

Change-Id: I8ff87364bf7d5c87f0519b6cdc32d164facf30eb
Fixes: 29237535

When the WiFi code is sufficiently mature, we'll use
this patch to return to using small ring buffers
on all builds.

Note that this patch is not a literal/full revert of
CL:1048267. The reason for the more focused change
is to minimize merge conflicts, in case other code
changes by the time this CL lands.

BUG=28822174
TEST=unit tests

Change-Id: I9facadf8aaf779e0627b15815a426b86bde692a1

Change-Id: Ifb500e3f745b5e2493ffa016a06f23120e80910a

am: 96cc4860

Change-Id: Iae9d523d364079407f500d00f96db951c3d7f994

am: e1809380

Change-Id: I15921c5f5903d66052cb48d851913672077a190c

am: e3c37daf

Change-Id: Ic33a155d3f19e39279a7d8b47ee63da217539c47

Deal correctly with short strings am: 1921acbf am: 49fefde1 am: 444e06c4 am: 0f37e416 am: 04fdb2ce am: 05e02971 am: 8e0899fa
am: 15a72380

Change-Id: If1f7862c71755f10eca68bfbcedcda431e39c0ff

Deal correctly with short strings am: 1921acbf am: 49fefde1 am: 444e06c4 am: 0f37e416 am: 04fdb2ce am: 05e02971
am: 8e0899fa

Change-Id: I0be9d821272c24f8d9d89771a49c678f10e73bbc

Deal correctly with short strings am: 1921acbf am: 49fefde1 am: 444e06c4 am: 0f37e416 am: 04fdb2ce
am: 05e02971

Change-Id: I71ac60266ed175da39c1235432d7f99c59ee2157

am: 04fdb2ce

Change-Id: I4232ea7bec8566cd35aee630863c432373fbcb1f

am: 0f37e416

Change-Id: I4794005c53ae7d99627de25722c846c2a45b856c

am: 444e06c4

Change-Id: Ied4ebd36b8e373b830d61869723caa3e8eeb32c3

am: 49fefde1

Change-Id: I595d98088be7d1bced40d34160bd114c9617d97d

am: 1921acbf

Change-Id: I5ffb8a5518678e3dfdd930acdd57c1aa5ab21650

Today the association to an AP can be rejected because of either
the rejection from the AP or the STA host driver time-out. The
WiFi framework receives the same ASSOC_REJECT messages for both
scenarios. Cut down the blacklist time value to 5 mins for now.
When we can differentiate these two types of rejections,
the blacklist time for the real AP rejection can go back to
30 minutes.

Bug: 28899826
Change-Id: I785e13140bfdfbefbae17320c247ae1c8134fa92

Modify |CMD_GET_LINK_LAYER_STATS| handling to return a null object when
the stats cannot be retrieved from wifi HAL. We've added a
feature check in |WifiServiceImpl.reportActivityInfo| method to check if
the device supports link layer stats reporting or not. So, there is no
need to fake an empty object if the retrieval fails.

BUG:29117407
Change-Id: Iaf8e060912611773398210785ebfaae7371db77c

Some devices rely on Setup Wizard to set a persistent country
code.
This CL honors the persistent option, fixing corresponding 5GHz AP
problem.
This also includes addtional unit tests for this change.

BUG=28127280
TEST=compile
TEST=runtest frameworks-wifi
Change-Id: I2f36216e143d0ac4959f26a9965def061a06aabf

Allow immediate single scan for scenarios such as user allows
untrusted networks, user forces a connectivity scan, and etc.
The minimum scan interval is enforced only for the screen state
change and connection state change cases.

Also removed the scan started by WCM for user selected network.
We connect to the user selected network by directly invoking
the wpa_supplicant select_network. Now WCM always sets the
'forceSelectNetwork' parameter to false when calling into
WifiQualifiedNetworkSelector.selectQualifiedNetwork(). So deleted
the unused variable mForceSelectNetwork.

Bug: 29103349
Change-Id: I1dd77af0cf7de85a96afac63de1344daab192968

This will fix an NPE whenever no scansettings are available.
The stop of the recurring alarm should not introduce a permanent
stop though since the whole processPendingScans function is dependant
on mPendingBackgroundScanSettings != null.

Anyway, as soon as mPendingBackgroundScanSettings is changed,
the processPendingScans function will be called, either directly
or indirectly through handleScanPeriod().

Crash call stack:
java.lang.NullPointerException: Attempt to read from field
'int com.android.server.wifi.WifiNative$ScanSettings.base_period_ms'
on a null object reference

at com.android.server.wifi.scanner.SupplicantWifiScannerImpl.processPendingScans
(SupplicantWifiScannerImpl.java:395)

Bug: 29113658
Author: Ola Olsson <ola.olsson@sonymobile.com>
Change-Id: Ibf08c9d6c5e476052449ef11d82ce005e50bd4fd