- Add a event node for SYSTEM_UI;
- Add a separate SYSTEM_UI profile.
Bug: 393196667
Test: adb shell dumpsys android.hardware.power.IPower/default
Flag: NONE powerhal doesn't have a flag yet
Change-Id: I53c5b2bb168b15ad965798a68f631c8a7b94a5e1
And reduce DownRateLimitUs to 500us as the system should be more
reactive now when something needs to rampup quickly.
Enable pertask iowait boost too as with auto dvfs headroom enabled all
tasks will start form 0 util_avg and this could impact iowait tasks
without this being enabled to help them migrate up to bigger cores.
Camera use cases should still use their own default DownRateLimitUs and
disable this feature to keep their dvfs_headroom tuning intact.
Bug: 392622882
Flag: EXEMPT powerhints are not compatible with flagging
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: I105807d89592992d0f8a2b8a7dab9b2b161be147
This CL adds a powerhint for AA mode to mask storming hint. DISPLAY_IDLE masks DISPLAY_UPDATE_IMMINENT and CPU_LOAD_RESET when Android Auto property is set. When navigation in Android Auto, the two hint with action to boost memlat is costly.
Bug: 380188115
Change-Id: I825a56ac32a0ecdc8b441af9cb64e81b1d04f9a6
Test: Local test with desktop_head_unit_internal
Flag: EXEMPT powerhint change
dbc has been added as a binary to the driver kernel v6.1.
And all dbc sysfs node has been removed.
Bug: 377913163
Bug: 384978512
Flag: EXEMPT clean up only
Change-Id: I42c60ec3535763666d0e5f6a4d702492b077d0c3
Signed-off-by: Zouberou Sayibou <zouberou@google.com>
Set bluetooth.profile.hap.enabled_by_default to false
bug: 386323913
Test: m
Flag: EXEMPT, properties change only for feature config
Change-Id: Idf007e77b3b9b4713a0660b94b3c1e121b2f5115
For cross akm roaming function, we have two ways in supplicant :
1. Open source way.
2. Broadcom specific way.
Originally, Broadcom projects follow way 2 due to the limitation of the driver.
For now, we plan to move all Broadcom projects to follow way 1 to make supplicant code clean and downsteam without conflict.
For those projects which is ready for way 1, we control it to follow way 1 with WIFI_BRCM_OPEN_SOURCE_MULTI_AKM config.
For the rest of Broadcom projects, we still follow way 2 until the multiple AKMs is fully supported by driver and verified.
For ongoing Broadcom project, we also need to exercise the open source path in supplicant to do multiple AKM configuration to comply with WFA Wifi 7 AKM24 specification (b/331896542).
Bug: 246871098
Test: AU drop test
Test: Cross AKM roaming test
Flag: EXEMPT enable control flag for aosp akms
Change-Id: Ia9a8b65c6f3e3af4315ffc37c27339d7a1386ad2
am skip reason: Merged-In Ic19ff6af1a86f94853e8d2c65012ee247ae25bde with SHA-1 e5364a3e49 is already in history
Original change: https://android-review.googlesource.com/c/device/google/shusky/+/3413302
Change-Id: If6b1b4975cf25f60d76e0c71d9b450f6a834f1d4
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
AAOS_on_phone targets need to override these properties, without
that builds are failing.
Bug: 382710252
Test: local build
Change-Id: I8eb4f6f904370caed9d87745331ff9b2ead1a2cd
This change introduces "is APF enabled" system properties, and
uses them as trigger conditions for APF nodes / pre-APF nodes.
By default APF nodes are active, and pre-APF nodes are inactive,
which maintains the situation before this change.
A future experiment will flip "is APF enabled" system properties,
deactivating APF nodes and activating pre-APF nodes. For more
info see go/pixel-perf-apf-experiment.
Bug: 365855872
Test: set vendor.powerhal.apf_enabled=false, vendor.powerhal.apf_disabled=true, observe auto_prefer_fit
procfs value staying "false" and instead preferred_idle_mask_mid
changing to 0x1ff during app launches
Flag: NONE powerhint change does not support flags
Change-Id: I85b5dc812132f229c2cc8583aaadd31d7eedc178
Signed-off-by: Dmitry Skiba <dskiba@google.com>
Revert submission 30661505-tdm_amplitude_limitation_removal_dvl
Reason for revert: short time to properly test before 25q1 cut-off.
Reverted changes: /q/submissionid:30661505-tdm_amplitude_limitation_removal_dvl
Bug: 318476589
Change-Id: I7d0fc0f64aa41cd901797cfc4a81eb41e7de1c05
Remove the voltage restriction for haptics since DVL is enabled. This
will allow FW control for exertion protection of the motor, and allow
for stronger output for audio-haptics.
Bug: 318476589
Flag: EXEMPT config xml change
Test: dumpsys vibrator_manager and accel measurement
Change-Id: Ic8ece936df599725ad1ab66089b0f66a3791e422
Set the CPU frequencies of FIXED_PERFORMANCE to align with Thermal CPU Light level.
Bug: 327070837
Test: Boot to home
Flag: NONE powerhal doesn't have a flag yet
Change-Id: Ibb698b608c21c2a4f81354f852cb077345907947
Remove thermal JSON Schema Checker first to avoid the false positive
because it cannot support the current thermalHAL design.
This reverts commit 97871af7ae.
Bug: 380370209
Test: build
Flag: EXEMPT disable config checker
Change-Id: I771d748373520399201b06799737496bfd9c8bad
Bug: 380369950
Test: PTE PQM-BT LE audio unicast test
Flag: EXEMPT The Samsung Galaxy Buds 3 pro users are able to disable LE audio in Settings app
Change-Id: I142d38d66e844aab35a72733e84374df72158042
Bug: 380024887
Test: BLE scan test and check wakelock time
Flag: EXEMPT project configuration patch.
Change-Id: Iafce4fea2e80e1eac076ce2258f62bbe5159513a
