Specifically due to netd change:
http://go/aog/3530692
Add support for new oem_in hook.
Test: TreeHugger
Signed-off-by: Maciej Żenczykowski <maze@google.com>
Change-Id: Ibec85ae1303789018a8d4a95f48ca429fe49acda
-----BEGIN PGP SIGNATURE-----
iF0EABECAB0WIQRDQNE1cO+UXoOBCWTorT+BmrEOeAUCZ9i73wAKCRDorT+BmrEO
eE0jAJ9LUlDeVJV2JVbzsyWRdWRRhpFGkwCfbEbrFRYUgH7HHshxtjQlrRTLJ/U=
=bAod
-----END PGP SIGNATURE-----
gpgsig -----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgPpdpjxPACTIhnlvYz0GM4BR7FJ
+rYv3jMbfxNKD3JvcAAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
AAAAQKbZFn9A2+Vqax//krl8KOKH948OcStI/TNfz2IkyoLz1xzEZcssWL38FiuVK0dTdk
J+X3VntP2QgehBQFDvQgY=
-----END SSH SIGNATURE-----
Merge tag 'aml_tz6_351400020' into staging/lineage-23.0_merge-aml_tz6_351400020
aml_tz6_351400020 (13155446,com.google.android.go.tzdata6,com.google.android.tzdata6)
# -----BEGIN PGP SIGNATURE-----
#
# iF0EABECAB0WIQRDQNE1cO+UXoOBCWTorT+BmrEOeAUCZ9i73wAKCRDorT+BmrEO
# eE0jAJ9LUlDeVJV2JVbzsyWRdWRRhpFGkwCfbEbrFRYUgH7HHshxtjQlrRTLJ/U=
# =bAod
# -----END PGP SIGNATURE-----
# gpg: Signature made Tue Mar 18 02:18:39 2025 EET
# gpg: using DSA key 4340D13570EF945E83810964E8AD3F819AB10E78
# gpg: Good signature from "The Android Open Source Project <initial-contribution@android.com>" [ultimate]
# By Piotr Klasa (4) and others
# Via Android Build Coastguard Worker (9) and others
* tag 'aml_tz6_351400020': (21 commits)
Enable usb state update via udc sysfs
usb: fix usb state path in host mode
usb: migrate UsbDataSessionMonitor to libpixelusb
Use 2025-03-01 deqp level for GLES
Use 2025-03-01 deqp levels for Vulkan
Revert "Use 2025-03-01 deqp levels for GLES and Vulkan"
Use 2025-03-01 deqp levels for GLES and Vulkan
move common init perf settings to gs_common
Revert "move common init perf settings to gs_common"
move common init perf settings to gs_common
Enable open source multi akm for specific Broadcom project
pixelstats: gs101: remove firmware update path
init-display-sh: Allow writing to kmsg
Remove ResetUclamp profiles
Update IDisplay to V13-V14
display-dump: make display dump project-specific
Refactor: Use googleDeviceConfig namespace in gs101 BoardConfig
dump_power: add battery caretaker dump into bugreport
Set initial value for foreground_window group
Move all vendor_sched parameters and permissions to init.pixel.perf.rc
...
Change-Id: I296bc05a0b9bc48ee3ca478f305e7ab76f5941ee
USB_DUMMY_HCD is disabled in kernel 6.1, modify the usb state path in
host mode accordingly.
Bug: 388367091
Test: test on oriole
Flag: EXEMPT trivial bug fix
Change-Id: If85077fddcadd25d15777d4b1ff5be2a0528c253
Use the libpixelusb version of UsbDataSessionMonitor.
Bug: 388367091
Test: test on oriole
Flag: EXEMPT CP
Change-Id: I93b74fc9bb63c260e900ee5af73e66fb1559142d
Meeded for system server to monitor usb gadget state.
Grant hal_usb_impl read access as it's needed by UsbDataSessionMonitor.
Starting at board level api 202504 due to its dependency on aosp/3337514
10956 10956 W android.hardwar: type=1400 audit(0.0:327): avc: denied { read } for name="state" dev="sysfs" ino=84394 scontext=u:r:hal_usb_impl:s0 tcontext=u:object_r:sysfs_udc:s0 tclass=file permissive=0
Bug: 339241080
Test: tested on Oriole
Flag: android.hardware.usb.flags.enable_udc_sysfs_usb_state_update
Change-Id: Iac9384cc81090d71e0cda8a6ba83476af865fe33
Revert submission 31488081-deqp-2025-03-01
Reason for revert: Droidmonitor created revert due to b/393355394. Will be verifying through ABTD before submission.
Reverted changes: /q/submissionid:31488081-deqp-2025-03-01
Change-Id: I054aaf0583ab9d4976514ac46917b661a494e186
compared to ag/31352563 I did not transfer the settings for "write /sys/devices/system/cpu/cpuidle/current_governor teo", which caused the problem
Test: Verified if all values of transferred settings are as they should be after rebooting the device, and and checked that there are no new selinux errors for hal_power_default, verified all metrics that caused power regression in the previous commit on abtd
Bug: 335874870
Flag: EXEMPT not supported by this component yet
Change-Id: I7ad8dbd7fd2783017c5bae8181008db32b95e9b7
Test: Verified if all values of transferred settings are as they should be after rebooting the device, and and checked that there are no new selinux errors for hal_power_default
Bug: 335874870
Flag: EXEMPT not supported by this component yet
Change-Id: I7054fb3ab6f8fce9cf06c7691e8e1aea2453ca88
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: I2594e3741d5be1c055d364104639b3d55336a5a7
Bug: 386187651
Test: local test pass
Flag: EXEMPT refactor
Change-Id: I2886e26186b12ffe34df6aa559bdf66e3e8f059d
Signed-off-by: Spade Lee <spadelee@google.com>
