* changes:
Added DRIVER_ATTENTION_MONITORING_STATE to HAL layer.
Added DRIVER_ATTENTION_MONITORING_WARNING to HAL layer.
Added HANDS_ON_DETECTION_WARNING to HAL layer.
Added HANDS_ON_DETECTION_DRIVER_STATE to HAL layer
- Add an event to know the device is suspended
- More status code
- Add pub_sub_id in the datapath request to build the relationship
Bug: 247913151
Test: build
Change-Id: I77733c1bca821b77fdab7ed1ed03c1e54c9373b2
* changes:
Added CRUISE_CONTROL_COMMAND to HAL layer.
Added CRUISE_CONTROL_STATE to HAL layer.
Added CRUISE_CONTROL_TYPE to HAL layer.
Added EMERGENCY_LANE_KEEP_ASSIST_STATE to HAL layer.
Renamed ADAPTIVE_CRUISE_CONTROL_ENABLED to CRUISE_CONTROL_ENABLED in HAL
Maximum MLO association link count can be an input for MLO scoring
logic. If the candidate AP has less number of links to associate,
scroring logic can give a weightage to an AP with matching links as
station Assumption here is when the environment becomes better, the
AP with less score now can be a better choice.
Bug: 269336948
Test: m android.hardware.wifi-update-api
Change-Id: Iac0c82203c9e1a23637c757f5b92f5b213bb5da6
Deprecated onPmkCacheAdded() callback function and
added a new onPmkSaCacheAdded() callback function to
include the connected AP BSSID. This will help framework
to include BSSID information as a key to store PMKSA.
Bug: 260042356
Test: atest vts
Test: Manual - Tested WPA3 STA - AP connection multiple times and
confirmed that PMKSA cache is added and supplicant is using
the PMKSA cache entries for open authentication.
Change-Id: I9fc7da7f4ba60e45ddeee9a41654c74f128fe3d6
We need to check the first api level that the vendor shipped with.
Also check P010 support in the preamble of the relevant test rather than in allocate(), since otherwise either allocate() may incorrectly skip some tests or allocate() may succeed but with the wrong layout information.
Bug: 257442231
Test: VtsHalGraphicsMapperV4_0TargetTest
Change-Id: I00ae5aa01117704158c38f0689e91df99473e208
Multi-link llstat parsing codes in wifi legacy hal, specifically
'copyLinkStat' and 'copyPeerInfo', pass the output container parameter
'std::vector<>' by value instead of by reference. The result is the
copied 'LinkStats' list and 'WifiPeerInfo' list are discarded when
'copyLinkStat' and 'copyPeerInfo' return. The empty links list are
passed to framework and fails validity check in Wi-Fi framework and
leads to system server crash.
Fix this issue by passing 'stats' and 'peers' by reference.
Bug: 269049672
Test: Manual Test with multi-link llstat implementation integrated
Change-Id: If8c366213af2ffcb9f7b3c904e1541ed0ac2fea4
in the Vendor HAL service.
Bug: 266521428
Test: Vendor HAL gTest suite
(see the modified test case)
Change-Id: I86e0c465b9f9d2f31413d75727e36b42c2b6b88a
Also update the IWifiChip VTS test to reflect
this change.
Bug: 266521428
Test: atest VtsHalWifiChipTargetTest
Change-Id: I537588c405d8a01091a6818020084acbe2679e14
* changes:
Adding VTS tests for IAudioControl#registerModuleChangeCallback
Add default implementation for dynamic volume config feature
Adding support for dynamic audio gain config
Framework populates MLO link information from scan cache. In roaming
use cases, framework may not have the scan result for the roamed AP.
So, always get the MLO link parameters from the supplicant. Add static
parameters apMldMacAddress, apLinkMacAddress and frequency of the
link. Dynamic parameters like RSSI, link speed..etc. are queried from
signal poll.
Bug: 268230307
Test: m android.hardware.wifi.supplicant-update-api
Change-Id: I7ffb23a8ead63a385cd00d26969529e2943fcff1
Disable dynamicsProcessing in presubmit temporary because it's currently
not following the range definition, and needs customize inRange method
implementationm which will be a followup.
Bug: 258124419
Test: atest --test-mapping hardware/interfaces/audio/aidl/vts:presubmit
Change-Id: Ib38145896d66b65c093c247c86a9fba76489ba84
