Currently, config_networkAvoidBadWifi is customized in aosp
for only 2 Verizon mccmncs: 310-004 and 311-480.
However, from TAM feedback, there are few mccmncs
which are not customized yet. Explicitly add them for different devices.
Test: manual
Bug: 270006176
Change-Id: I46ec45354ae72a6a758aba2c2a31af92f1da4038
(cherry picked from commit cc270214edfe849dc71314455aa28994a7939150)
(cherry picked from commit ca61a1318a)
Merged-In: I46ec45354ae72a6a758aba2c2a31af92f1da4038
This flag will not take effect if the system is configured to
avoid bad wifis. Set it to 1 globally. Then it will sprint
into effect for all mcc/mncs where config_networkAvoidBadWifi is 0.
For carriers that don't need this behavior change but
config_networkAvoidBadWifi is 0, set activelyPreferBadwifi
to 0 for their mccmncs.
Test: manual
Bug: 270006176
Change-Id: I4b6fe4964e8fd5d61978f1433dcbbd9e9b10ffc3
(cherry picked from commit 3357b8cf949b9e632d10759ba8bc700b72ac2242)
(cherry picked from commit f848c4d77f)
Merged-In: I4b6fe4964e8fd5d61978f1433dcbbd9e9b10ffc3
Monitorffs needs to check the state of usb extcon and gadget state
to pull up USB gadget. Therefore, this patch provide extcon and gadget
state to monitorffs.
Bug: 263435622
Test: verified pass
Change-Id: Icbfe2a2839b3225b56de35ab949aa1758d27d9a6
(cherry picked from commit 5e713fa131)
Merged-In: Icbfe2a2839b3225b56de35ab949aa1758d27d9a6
This change migrates IUsbGadget implementation to AIDL.
Bug: 261027750
Test: USB function switch success and AIDL service is running.
Change-Id: I7cc7070d875c26bc42f99aef84d5e5a41606223f
Signed-off-by: Ricky Niu <rickyniu@google.com>
- Add more PLMNs for specificed carrier configuration
- Add configuration to use full response time in SUPL NI session to
benifit accuracy
- Fix miscalculate TTFF and RSP problem due to unexpected stop command
Bug: 260996867
Bug: 260153806
Bug: 260795209
Verify test: b/262702990
Test: VtsHalGnssTargetTest pass
CtsLocationGnssTestCases pass
PtsChreTestCases pass
Change-Id: I1255a31adbb77e5d476af070046d1f1a12fa1771
As the latest Mali DDK exposes a Vulkan 1.3 driver
also setup the device properties accordingly.
Bug: 259507479
Change-Id: I593e4881f3e211b98c641e5546578b6e64036703
dock-defend is enabled in kernel code.
Bug: 262322247
Test: dock-defend is enabled by default
Change-Id: Ibbd83fc2442e2a6d68d7f506ccd29d452947931c
Signed-off-by: Jack Wu <wjack@google.com>
am skip reason: Merged-In Ifb3f692284eec45ca0c17838c1f39eaf2661650d with SHA-1 dbf314e10c is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2338117
Change-Id: Ib8a25be8bb337db6d37f550ca8cbce2ac2709962
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ifb3f692284eec45ca0c17838c1f39eaf2661650d with SHA-1 13a10adc05 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2338117
Change-Id: Idcacb50d46fded7b1af2bbe32833b421b27f8b21
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ifb3f692284eec45ca0c17838c1f39eaf2661650d with SHA-1 13a10adc05 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2338117
Change-Id: Id9b98dda329258b3bfad60ecba1ad346ddaeff10
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ifb3f692284eec45ca0c17838c1f39eaf2661650d with SHA-1 13a10adc05 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2338117
Change-Id: I8d9f060864da3860ca834df5dee0bce3af2d460e
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
the file node was removed so also remove these
dummy setting
Bug: 260806701
Change-Id: I23044f7f32cf4b2b2cc93205ec5751525f05ee7f
Signed-off-by: Chungkai Mei <chungkai@google.com>
Add support for copying prebuilt kernel modules like fips140.ko into the
vendor ramdisk. These kernel modules are different in the following
ways:
- They do not appear in vendor_boot.modules.load provided by the
kernel build system.
- We want to put their names at the very beginning of the output
modules.load file to ensure that they are loaded prior to all other
modules.
We define a new Makefile variable named
BOARD_PREBUILT_VENDOR_RAMDISK_KERNEL_MODULES. For every filename on this
list, we verify that the file exists in $(KERNEL_MODULE_DIR), and if it
does, we include its name in the modules.load for the vendor boot
ramdisk.
Bug: 194712883
Change-Id: Iff8923c2492296b8eb4d24ec94bbfccc19f4e8f5
Modify the logging mask file path to instead point to the new history
directory, as well as include more files (right now only logging mask
history and logging enabled history).
Bug: 259174982
Test: Manually build and inspect bugreport to make sure files are
included
Change-Id: I1a57e0f4fea66929803fac350547b706d7442b26
Merged-In: I1a57e0f4fea66929803fac350547b706d7442b26
