for the Wifi VTS tests.
Main method is getBridgedWifiApIface_1_6, which
allows us to configure the chip based on the
Bridged AP IfaceConcurrencyType, rather than
the AP IfaceType like in getBridgedWifiApIface_1_5.
Implementations were largely copied from
wifi_hidl_test_utils and wifi_hidl_test_utils_1_5.
Bug: 283402709
Test: atest VtsHalHostapdTargetTest
# tested on a Bluejay device that supports
# the AddAccessPointWithDualBandConfig test
Change-Id: I2571876149fc14c8de02e1cec9934dd052cada5c
Merged-In: I2571876149fc14c8de02e1cec9934dd052cada5c
for the Wifi VTS tests.
Main method is getBridgedWifiApIface_1_6, which
allows us to configure the chip based on the
Bridged AP IfaceConcurrencyType, rather than
the AP IfaceType like in getBridgedWifiApIface_1_5.
Implementations were largely copied from
wifi_hidl_test_utils and wifi_hidl_test_utils_1_5.
Bug: 283402709
Test: atest VtsHalHostapdTargetTest
# tested on a Bluejay device that supports
# the AddAccessPointWithDualBandConfig test
Change-Id: I2571876149fc14c8de02e1cec9934dd052cada5c
Merged-In: I2571876149fc14c8de02e1cec9934dd052cada5c
for the Wifi VTS tests.
Main method is getBridgedWifiApIface_1_6, which
allows us to configure the chip based on the
Bridged AP IfaceConcurrencyType, rather than
the AP IfaceType like in getBridgedWifiApIface_1_5.
Implementations were largely copied from
wifi_hidl_test_utils and wifi_hidl_test_utils_1_5.
Bug: 283402709
Test: atest VtsHalHostapdTargetTest
# tested on a Bluejay device that supports
# the AddAccessPointWithDualBandConfig test
Change-Id: I2571876149fc14c8de02e1cec9934dd052cada5c
APF is support is mandatory since VSR 14. Before that, the APF
requirement is optional. Vendors can opted into upgrading their
HAL to AIDL, so the VTS need to check if vendor API level on the device
and only mandate the APF capability check if the vendor API level is
greater or equal to 14.
Bug: 283181837
Test: atest VtsHalWifiStaIfaceTargetTest
Change-Id: I21513187d4ca99d721d0e9dc5e243adad77ab8c6
supplicant_test_utils::initializeService() only stop Supplicant,
don't start it. refer Android T code, It should start Supplicant
when initializeService().
Bug: 279572212
Test: VtsHalWifiSupplicantP2pIfaceTargetTest pass
Change-Id: I9f4b3e21ee0865eb95d71f7f832b2eb405de9607
SetStrictConversativePeerMode HAL API is added in
AIDL version 2. So if the HAL interface version is
less than 2, skip the test.
Bug: 278169264
Bug: 277318919
Test: atest VtsHalWifiSupplicantStaNetworkTargetTest
Change-Id: I7f8ace88b0f37679ecaedd5370b47e220c437d50
This change adds a missing newline character to the end of dump() for
the default health and wifi int
Add missing newline to health/wifi AIDL interfaces
This change adds a missing newline character to the end of dump() for
health and wifi.
Test: Take a bugreport and verify that the "X was the duration of
dumpsys Y" lines aren't preceded by the final line of the dump.
Test: Run "dumpsys android.hardware.health.IHealth/default" and verify
that the new line exists.
Test: Run "dumpsys android.hardware.wifi.IWifi/default" and verify that
the new line exists.
Bug: 278081288
Change-Id: I173dd174b5bab808c6296f7163982393e60ba0c6
VtsHalWifiHostapdV1_2TargetTest.
Test currently sets up a new interface
and uses that interface's name. On Pixel,
the new interface is wlan1, which does not
seem to support the OpenAccessPointWithoutAcs
configuration. However, the default SAP
interface wlan0 does support it.
The method to get the default interface name
is taken from this file before ag/19202002
was merged.
Bug: 270509029
Test: atest VtsHalWifiHostapdV1_2TargetTest
(on a Bramble device running rvc-qpr3-release)
Change-Id: Ic3c516f452dfb54f155246073a9bca20dbecaa0f
Update the aidl API documentation to describe how setDtimMultiplier API
is supposed to work, i.e. we can call this API to set a maximum DTIM
multiplier value to use in driver, any larger value must not be accepted
and meanwhile it allows to set a specific multiplier by OEMs. Try to
make the description clear and avoid the ambiguity.
Bug: 266256943
Test: m
Change-Id: Ic7d2284a25e32d1b0752cf2bc832c069f646fcea
dump method is called.
This should prevent a race condition
between stop() and dump().
stop() already acquires the global lock
when it calls validateAndCall().
Bug: 274641043
Test: adb shell dumpsys wifi # validates dump()
Change-Id: Ie2df0861308954cd2e399c9604d4ae0dcddf95fb
VTS test for IWifiChip#getFeatureSet.
Some implementations of the legacy HAL,
such as Goldfish, do not have any
supported features.
Bug: 273886122
Test: atest VtsHalWifiChipTargetTest
(tested on Cuttlefish)
Change-Id: I3ca22187cab0e77d36a28908e57ff4970535e4ae
Since Android U, VSR 5.3.12 mentioned the Android Packet Filtering must
be supported by CHIPSETs and DEVICEs launching on Android 14 or higher.
This VTS was added to check if APF is supported properly.
Given the limitation of the VTS testing environment, the first version
of the test case only checks: if the APF is supported by WiFi chips with
version 4 and more than 1024 bytes of usable memory.
Bug: 259309511
Test: atest VtsHalWifiStaIfaceTargetTest
Change-Id: I3ee2a980a4440db232738a23c1633aaff3562d95
If STA and NAN share the same iface wlan0, Wi-Fi vendor HAL service
sends eventDisabled to NAN framework when STA setMacAddress to wlan0.
This disables NAN when STA is turned on.
Since NAN always uses its own random MAC instead of using MAC of STA,
this action is not necessary and gets NAN kicked off for no benefits.
We add a build time configuration to optionally disable this behavior.
Bug: 273426515
Test: manually test
Change-Id: Ifc71b7e8d09eac1b66b9e18c70e0e6d202683ff6
Use a new structure to passdown:
- AFC information queried based on frequency
- AFC information queried based on channel number
- expiration time
This change is per chip vendor request. Based on AFC server support,
either frequency based information or channel based information may be
empty. If both are empty, then it indicate the driver should not allow
any standard power transmission on 6Ghz.
Bug: 262791660
Test: compile
Test: Manually verified information is passed down with local framework
change
Change-Id: Id1d014a6113f6863b98ef8239a5a52d3863aa758
explain why the linter is disabled.
If the linter were enabled, we would run into a
build failure because fixed-size arrays are not
supported on SDK Level < 33. The interface indicates
min_sdk_version 30 due to mainline requirements,
but the interface will only be accessed by devices
running Android U.
Bug: 267819850
Test: m
Change-Id: Ifed2223d1c5f4bf46329ed72fa622b730e99cde1
* changes:
Rename getCapabilities to getFeatureSet in the Vendor HAL implementation.
Rename getCapabilities to getFeatureSet in IWifiChip and IWifiStaIface.
NewApi was recently updated to support linting methods in
the system, module_lib, and system_server sdks, and was
demoted to a warning due to the new issues it finds.
Baseline all the new issues that NewApi can be made an error
again.
These cls were generated automatically by a script that
copied the NewApi issues from the reference baselines.
Bug: 268261262
Test: m lint-check
Change-Id: I22f3b3575b6ea00d72d143019d9eed028aa98b56
in IWifiChip and IWifiStaIface.
Main purpose is to distinguish between
the 2 capability methods in IWifiChip:
- getCapabilities (renamed here)
- getWifiChipCapabilities
Bug: 267819850
Test: atest VtsHalWifiChipTargetTest \
VtsHalWifiStaIfaceTargetTest
Change-Id: I03c15d652d02aef99b219c2d630b69acb4d9e43c
we changed to store event information in bitmap format
so that overlapping events can be handled.
Bug: 270650316
Test: startPublishRequest_1_6
Change-Id: I6f3cb8026d54dfa692bfd6eb64b24005ba663a1f
Signed-off-by: dheda.shin <dheda.shin@samsung.com>
Re-assign the value according to the Wifi Aware R4.0 section 9.5.21.1
Also correct several comments.
Bug: 269440402
Test: build
Change-Id: Ib3dd6365b2a28f871ec6ae3775ee8b9e9481475f
types in the Vendor HAL interface.
Specs should be included in the
relevant places.
Bug: 267819850
Test: m
Change-Id: I1f213774ebf5dc297225a5cabb757d2956d67bf4
* changes:
Update usages of WifiRadioCombinationMatrix in the Vendor HAL service.
Remove the WifiRadioCombinationsMatrix type from the Vendor HAL interface.
Vendor HAL interface.
We can return a list of WifiRadioCombinations instead.
Bug: 267819850
Test: atest VtsHalWifiChipTargetTest
Change-Id: I0f57df6262d36917dfd8cc3e27d6781e9b7c8dbf
After adding ag/21179155, auto join flag is
not set for every p2p connect command. The tests
are passing an unknown peer MAC address to connect(). To
pass the tests, the connect should trigger a scan and
try to find this unknown mac address. So set join flag
to true to run the same scan logic.
Bug: 268236829
Bug: 218608010
Test: atest VtsHalWifiSupplicantP2pIfaceTargetTest
Change-Id: Id5baa0f599d11a3563780aae15ff3cea0407060c
XML parsing logic.
Fixes a minor memory leak that results from
not freeing that buffer.
Bug: 269520490
Test: Manual test
1. Create several XML files under
/vendor/etc/wifi/vendor_hals
2. Modify the codepath to run the
initVendorHalsDescriptorList method
(does not run by default on Pixel).
3. Check that the XML parsing logic is
working as intended.
Change-Id: I42944169b70c759998d94e8523d2aa55d0366ffd
Interface combinations in legacy-hal is predefined with
'WIFI_HAL_INTERFACE_COMBINATIONS' build flag. This change
allows the WiFi HAL to request all the possible interface
concurrency combinations via vendor HAL API,
wifi_get_supported_iface_concurrency_matrix(). Thus build time
dependency can be removed by querying the combination at runtime.
Bug: 249351396
Change-Id: I3bc85ac013490949aab71a00f60028bf5daee68c
Merged-In: I3bc85ac013490949aab71a00f60028bf5daee68c
Test: Build successfully
Signed-off-by: Purushottam Kushwaha <quic_pkushwah@quicinc.com>
(cherry picked from commit f68b9a2709)
Add capability fields for TID-to-Link mapping negotiation support for
both station and access point.
Bug: 268219346
Test: atest VtsHalWifiSupplicantStaIfaceTargetTest
Change-Id: Iaf82cdb8a0c3e57135487c95750f53ab1d6fc187
- 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
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
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
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
Skip P2P tests if P2P is not supported.
Bug: 200064365
Test: run vts -m VtsHalWifiSupplicantP2pV1_4TargetTest
Change-Id: I6ba23bb27f24700980cab28d1ff806e5efc65ec9
(cherry picked from commit b676061cd5)
(cherry picked from commit 4d81b6562dca69a3334bcb87756539fbdaedcd2d)
Implementation of Wi-Fi P2P Technical Specification v1.7 - Section 4.2.8
"IP Address Allocation in EAPOL-Key Frames (4-Way Handshake)".
Changes includes,
1. API to configure the IP addresses in supplicant for P2P GO to
provide the IP address to client in EAPOL handshake.
2. Send the received IP address information to framework via
p2p group started event.
Bug: 170056953
Test: Manual - Establish P2P connection & confirmed from sniffer logs
and logcat logs that IP addresse is allocated via EAPOL exchange.
Ping works after connection.
Change-Id: I2662fde9ca645aa5e34b21678d1a47cbf26ef3d3
The maximum number of Simultaneous Transmit Receive (STR) links used in
Multi-Link Operation can be different from the maximum radios supported
by the chip.Explicitly mention the max links as max STR links. Update
the description and usage of the capability field.
Bug: 267963579
Test: m android.hardware.wifi-update-api
Change-Id: I5691fcc44c60821766fe41e67624e458ba051059
Unlike the default constructor, create() populates
the weak_ptr_this_ variable, which is needed for
callbacks from the legacy hal.
Bug: 265857332
Test: Manual test - connect to an AP and walk away
from it. Check that the RSSI callback is
triggered in the framework.
Change-Id: I1a10a75c07ea59a3e01b9bb68d9d393bbd20d29d
The AOSP-version of wifi hal apex now contains the VINTF fragment in it.
Bug: 247018693
Bug: 266885060
Test: atest CtsWifiTestCases
Merged-In: Id8f196386967c3023cb5ee308d31b8cdeed7df0b
Change-Id: Id8f196386967c3023cb5ee308d31b8cdeed7df0b
The AOSP-version of wifi hal apex now contains the VINTF fragment in it.
Bug: 247018693
Bug: 266885060
Test: atest CtsWifiTestCases
Change-Id: Id8f196386967c3023cb5ee308d31b8cdeed7df0b
NAN is not supported by Cuttlefish, so check
for Aware support before running any related
tests.
Also fix the incorrect function call in
CreateP2pIface.
Bug: 263762326
Test: atest VtsHalWifiChipTargetTest
(tested on Cuttlefish and Bluejay)
Change-Id: I3ec52fcc18aedad157dbc17d19078dde216261fb
HAL API support for setting max permissible power on a range of
frequencies. Unspecified frequencies will get reverted to their
respective default values.
Also add capability flag for this new API.
Bug: 242917176
Test: make -j128
Test: Manually verified the framework can call the HAL API
Change-Id: I14ac494124b51ca0b85c394eefe6332c4b382d19
In the API, we can enable/disalbe STA-connected indoor or DFS channels for WFA GO, SAP and Wi-Fi Aware.
Bug: 207669954
Test: m android.hardware.wifi-update-api
Change-Id: I8513bc265fe8fc4f43d9e4b508d8c361f3455fd7
When convert byte to uint16, if the byte represent a negative number,
the high 8 bit of the uint16 will be all 1, which causes a mismatch.
Same as HIDL, convert byte to unit8 then fill into the uint16
Bug: 263690436
Test: cts SingleDeviceTest
Change-Id: Id9462dce48d2a2558c6b5c104866da66ce951b0e
Added the check for TLSV1.3 feature support in
SetMinimumTlsVersionEapPhase1Param test
Bug: 261922145
Test: atest SupplicantStaNetworkAidlTest
Change-Id: I26e7796d4d83e72e0098d5aa6ee520824bda23b1
With MLO, WiFi 7 supports establishing multiple links between the
Station and Access Point. Each of the link has its own stats.
To maintain backward compatibility, if multi link stats is not supported
by vendor, always fallback to single link layer stats.
Bug: 246988155
Test: hardware/interfaces/wifi/aidl/default/tests/runtests.sh
Change-Id: Iede8ce771f0e58975222808b1870e5e2e179384c
Due to the introduction of multi links, StaLinkLayerStats carries stats
for multiple links as a vector. For LegacyLinkLayerStats, only single
link will be available. So convertLegacyLinkLayerStatsToAidl() push the
stats for single link as the first element of the link vector.Fix the
unit test to index the first link.
Bug: 246988155
Test: hardware/interfaces/wifi/aidl/default/tests/runtests.sh
Change-Id: I8c9a8beca6bda6cf894edb616cdfe54f09d029f7
Currently framework gets the connected AP frequency
information by checking the scan cache & through signal
poll command. But these mechanisms doesn't work if framework
scan cache is not updated with the connected AP information
(For example in case of roaming and force connection without scan).
To fix this modified supplicant state change interface
and included the frequency of the connected channel in the
state change event.
Bug: 240299862
Test: atest vts
Test: Manual - Tested STA - AP connection and verfied the data
from debug logs.
Change-Id: I936bd3256420de38cdfee740e43972bc262ec4b8
Added a new field in chip capabilities to get the
maximum number of concurrent TDLS sessions supported
by the chip
Bug: 240247868
Test: Manual - STA connect/disconnect
Change-Id: I62fcd2d4a562b088cdeb4b04f72cfe55ed61241c
Added a new field in chip capabilities to get the
maximum number of concurrent TDLS sessions supported
by the chip
Bug: 240247868
Test: Manual - STA connect/disconnect
Test: m android.hardware.wifi-update-api
Change-Id: Ie2a4129241f40fc9eba28105b8ea3c06b27a8492
Define a new AIDL API to get capabilities from the vendor chip.
Bug: 231497844
Test: m android.hardware.wifi-update-api
Change-Id: I3c1cfce4df2101125a628f230b938b3be0f80311
Added a new StaIfaceCallback method to indicate that
the operating frequency of the BSS is changed
due to channel switch announcement from the AP.
Bug: 195617184
Test: Manually triggered channel switch through peer AP hostapd command
and verified the new frequency in STA logs.
Change-Id: I9dd59d7c5d4ddc5f3443f8b6786cfea9beec4f3c
Create a snapshot of hardware_legacy for legacy HIDL, to avoid any build breakage due to new hardware_legacy for the new AIDL. Should be removed with the HIDL when we finish the switch
Bug: 205044134
Test: build and CtsWifiTest
Change-Id: Ib1068112f6c90f2a41b68e20027d959c95798120
Supplicant and Hostapd tests have a dependency on
the Vendor HAL in order to do setup/cleanup,
such as bringing up an interface.
This change will make the tests compatible with either
the HIDL or AIDL Vendor HAL, depending on which
is available.
Bug: 205044134
Test: atest VtsHalHostapdTargetTest
atest VtsHalWifiSupplicantStaIfaceTargetTest \
VtsHalWifiSupplicantStaNetworkTargetTest \
VtsHalWifiSupplicantP2pIfaceTargetTest
Tests were run using both the HIDL and AIDL
Vendor HALs.
Change-Id: I1f6b15016414a0bf614703315b47b5b47d3a1e50
This change is for Enrollee to send the DPP connection status
result frame to configurator. The changes includes,
1. Modified the existing onDppSuccessConfigReceived callback function
to indicate that configurator has requested for the connection status
result frame.
2. New callback function to indicate that the connection status result
frame is sent.
3. Defined connection status code.
Bug: 235844564
Test: m android.hardware.wifi.supplicant-update-api
Test: Manual - Ran DPP tests and confirmed that
connection status frame is processed correctly
Change-Id: I45866707971c874c9270e7316a7b86fe0953d95a
Add a callback to notify MLO link status changes due to
- Multi-Link Reconfiguration (AP Removal)
- TID to link mapping updates
Bug: 247119055
Bug: 248289182
Test: mm -j
Change-Id: I1010cfb3ef608466a46d54e1ef2ae4e665504210
TID-to-link mapping, which is introduced in IEEE 802.11be standard
allows an Access Point and a Station to determine how uplink and
downlink QoS traffic corresponding to TID values between 0 and 7 will be
assigned to the setup multi links.
This commit adds an interface to TID-to-link mapping in existing MloLink
AIDL.
BUG: 247119055
Test: mm -j
Change-Id: I3ef6e37d9857606020a8e0580c82ca8ab1b8bf82
The GO interface MAC address would be used to calculate the link-local
IPv6 address of the GO in the GC side.
Test: m
Bug: 233912758
Change-Id: I8cdae90a2703d446dafbdfba8f99c191b751f552
ASan is not meant to be enabled in production binaries, and the fuzzer
"sanitizer" is only intended to be used with fuzz targets. So disable
both of them.
Change-Id: Ice7d8d3fd6621077d485b430d9e06fb3ba240e87
When device supports two AP interfaces (i.e. {AP, 2}. not a bridged case),
the AP interface name might be observed from the getPredefinedApIfaceNames.
Check if the interface name is used or not when creating a new interface.
Bug: 244387442
Test: Manual test by commands
adb shell cmd wifi start-softap tetheredAp open -b 2
adb shell cmd wifi start-lohs lohs open -b 5
Change-Id: I59b3796895ee09452a9650c4dc138ad9e143282e
Previously, the build rules assumed that the target supports both 64 and
32 bit architectures, which isn't true for 32-bit-only targets. That
caused build breakage on such targets. Fixing that by building the
modules only for the first architecture (64 on 64-only or 64/32 target,
and 32 on 32-only target).
Bug: 241916304
Test: build the 32-bit-only target
Merged-In: I5353ab1561622eae12e2dff87eb0f17b47c3773d
Change-Id: I5353ab1561622eae12e2dff87eb0f17b47c3773d
(cherry picked from commit 3ab5c90104)
As libwifi-hal is migrated to soong, the service is migrated to soong as
well.
Bug: 240099735
Test: CtsWifiTestCases
Merged-In: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
Change-Id: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
(cherry picked from commit c4ac3355a6)
Previously, the build rules assumed that the target supports both 64 and
32 bit architectures, which isn't true for 32-bit-only targets. That
caused build breakage on such targets. Fixing that by building the
modules only for the first architecture (64 on 64-only or 64/32 target,
and 32 on 32-only target).
Bug: 241916304
Test: build the 32-bit-only target
Change-Id: I5353ab1561622eae12e2dff87eb0f17b47c3773d
As libwifi-hal is migrated to soong, the service is migrated to soong as
well.
Bug: 240099735
Test: CtsWifiTestCases
Change-Id: Ie5a4ec6658d5f6aa3d4902c9c3c4b3bef9ff1cde
wifi hal is stopped before starting wifi.
Bug: 234853504
Test: atest VtsHalWifiSupplicantV1_0TargetTest # HIDL service
Change-Id: I413c3803a6607a72cc3aa8a5fa208551be1b1032
(cherry picked from commit bfe60cda4d)
Merged-In: I413c3803a6607a72cc3aa8a5fa208551be1b1032
wifi hal is stopped before starting wifi.
Bug: 234853504
Test: atest VtsHalWifiSupplicantV1_0TargetTest # HIDL service
Change-Id: I413c3803a6607a72cc3aa8a5fa208551be1b1032
(cherry picked from commit bfe60cda4d)
wifi hal is stopped before starting wifi.
Bug: 234853504
Test: atest VtsHalWifiSupplicantV1_0TargetTest # HIDL service
Change-Id: I413c3803a6607a72cc3aa8a5fa208551be1b1032
Some are still in VNDK because they are used in other VNDK libs.
Bug: 234181591
Test: m
Merged-In: If999df9c78a20df931177da11742b1c5de19bc08
Change-Id: If999df9c78a20df931177da11742b1c5de19bc08
Some are still in VNDK because they are used in other VNDK libs.
Ignore-AOSP-First: some libs are still in internal master only.
Bug: 234181591
Test: m
Merged-In: If999df9c78a20df931177da11742b1c5de19bc08
Change-Id: If999df9c78a20df931177da11742b1c5de19bc08
(cherry picked from commit 5527adfd7f)
Some are still in VNDK because they are used in other VNDK libs.
Ignore-AOSP-First: some libs are still in internal master only.
Bug: 234181591
Test: m
Change-Id: If999df9c78a20df931177da11742b1c5de19bc08
While appending the newly received buffer to ring buffer list,
check the size of the first buffer in the ring buffer list.
If it is invalid(zero size or exceeding the max allowed size),
return failure & clear all the ring buffers.
Bug: 232477451
Test: vts test - 1.6/default/tests/runtests.sh
Test: Manual - Ran basic wifi tests & checked bugreports
Change-Id: Iaa41262f534914b971fe178053f1974248a46e70
To lower the instantaneous battery current draw of WiFi, we provide
a way to allow PowerManager to enable/disable Tx power limits.
In the legacy HAL, we call the API in Broadcom HAL to
enable/disable WiFi TX power limits.
Bug: 215193418
Test: New APIs work fine
Change-Id: I1fbe71c3380514e2eba96adc5902d2028a55e006
