As the change of init feature flag on swb is ready, we will open
swb on those devices that supports this feature with more flexibility
since wiping sys property could be done at android regular releases
as enabling feature flag on server make it more flexible on schedule.
Test: manual
Bug: 283722412
Change-Id: Id5a75649c47ad826bb3d624ea68d4200c9ffe118
Enabled distance filtering. All AoA-related primers are disabled, the
rotation vector hardware is disabled and the AoA filter size is set to
the smallest value to save CPU.
Bug: b/237098661
Test: Manual confirmation
Change-Id: Ifc4a877bf2d608a00ae4a9153a99ace58e9618fd
It has an effect on following case:
If STA firstly connected with 6ghz channel AP and Application create p2p group without config, wpa_supplicant also tried to select STA-associated channel(in this case, i.e. 6ghz ch).
Bug: 281733591
Test: atest android.net.wifi.cts.ConcurrencyTest#testPersistentGroupOperation
Change-Id: I0015fb9ad602f585a6b1572cf13967b0a895f0f2
util_threshold only controls migration margin now. dvfs headroom has its
own new knob.
Bug: 261705301
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: I4223b3984003369e8fc7b2f0eac03bbe68569d6c
The country code updating from scan results generic case can cover setup wizard case.
Bug: 279625751
Test: manually verified generic case
Change-Id: I91815abfb4ec9e6c2bc324c9bf3eb6ffee7d6cab
note: add smartfeature.gstf that only used for Hotword
pipeline in AoC which is sharing to chre usage too.
On WHI_PRO
CHRE PDM Gain(gain=158)
CHRE AEC Gain(gain=-42)
CHRE SRC AEC Timeout(timeout=0)
This table also contains hotword gain control as
(Undocked)
Non Eraser gain (gain=220)
Eraser Pre gain (gain=220)
(Docked)
Non Eraser gain (gain=356)
Eraser Pre gain (gain=170)
Eraser Post gain (gain=186)
Test: end-to-end verify by CHRE
using aoc_audio_cfg to query gain as below
adb shell aoc_audio_cfg hotword_get_non_eraser_gain
adb shell aoc_audio_cfg hotword_get_eraser_post_gain
adb shell aoc_audio_cfg hotword_get_eraser_pre_gain
Bug: 271078701
Change-Id: I4e3416af224742d939c0928c6623705a01924581
enable load kernel modules in parallel but load some
specific modules in sequential
Test: reboot more than 500 times without failure
Bug: 229794277
Change-Id: I41cb5a09fb88ff7faa5ec12f71209b35cd941948
Signed-off-by: Chungkai Mei <chungkai@google.com>
Upstream has fixed relationship between uclamp_min and margin which
means uclamp_min value between 80-100% of capacity of the CPU is a valid
value and will not cause upmigration.
To keep the current hints in powerhint.json the same, we must update
uclamp_min to be capacity_orig_of(medium_cpu) + 1.
This change is dependent on uclamp vs fits margin in GKI, vendor
modules. And an improvement in sched_pixel to ignore the 25% boost if
the only reason to request the frequency is uclamp_min.
To cater for the later - we multiply each uclamp_min value with 1.25
- except ones that look intentionally set around capacity boundaries.
Bug: 261695590
Test: PtsUiBench
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: I1e6889ebea9877cb23708722a73e97177e6be185
