* This constantly crashes potentially because of the major BT stack
changes introduced in QRP1. We need to wait for QCOM to pick and
adapt this changes internally.
E AndroidRuntime: java.lang.NoSuchMethodError: No virtual method isBroadcastActive()Z in class Landroid/bluetooth/BluetoothAdapter;
or its super classes (declaration of 'android.bluetooth.BluetoothAdapter' appears in /apex/com.android.btservices/javalib/framework-bluetooth.jar)
Change-Id: I8a5537122f5487a17af4ddbb6f1febd91ba20245
Bug: 142752869
Test: atest frameworks/opt/net/wifi/tests/wifitests/
Test: Manual test, fake test code to enable SAE and SAE transition mode,
Client which support SAE will identify SAP enabled in SAE mode.
In transition mode, the non-support SAE client(likes P16 devices) can connect succeed.
But Client which support SAE (likes P18 devices) will fail to connect since current Pixel
driver not support the SAE connection. But SAP beacon show it secured by SAE which P18
will show correct security type (i.e. SAE) in wifi scan list.
Change-Id: I77d2143858b22ec32152265e713ea3254e913832
Note this isn't enough to enable MBB. The iface
HAL combination for STA+STA must also be enabled.
Bug: 173044646
Test: compiles
Change-Id: Ica955e1b8e8b8773a696f7c87e1d21c1ddf239d0
Already enabled on coral & redfin. Also enable it on sunfish to enable
more local testing.
Note: Does not enable the feature by default. Still needs a shell
command to turn on STA + STA in the HAL.
Bug: 173044646
Bug: 177780488
Test: Compiles
Change-Id: I0a74c7008d482c81106ef3e1d02bb0ccd7aa7542
Disable WPA2 to WPA3 auto-upgrade in P18 and P19 devices.
These devices do not support roaming in WPA3 networks. Reduce the
probability of roaming issues by using WPA2 and not upgrading to WPA3.
Bug: 169948620
Test: atest ClientModeImplTest ScanResultMatchInfoTest WifiCandidatesTest
Change-Id: Ice4ffc5299f53bf635b58a36e9b8f8d45f22da22
for sending network score to connectivity service
Bug: 166152800
Test: verified feature works on device
Change-Id: I495058c1ee0cbf703ca8ba0a1b2c93dc196f916e
Preinstalled overlays needn't be signed with the same cert
as the package it overlays, simply being preinstalled is
enough. Sign with the default cert instead for now, which
provides fewer special privileges.
Bug: 162195999
Change-Id: I524bf8ae1c3522add1a0c33ab23ea3026958f2a5
As resources were moved from the android package to the connectivity
resources package, migrate resources to a new overlay for the new
package.
Bug: 185850634
Test: m
Change-Id: I253f5b68856850c0d334f4260eb3e7705e729f18
ag/16564596 will change default value to false.
Configure correct overlay configuration.
Bug: 212488775
Test: manual test & build
Change-Id: Ib1925c591d24cd605bb08eb38b7e0b182e6f10f9
