The license declaration can't be handled in Android.bp currently.
So keep them in Android.bp.
Bug: 310058310
Test: NA
Change-Id: I3e25fa07f6b3e1bffaf585d69e342c651b50f6ef
am skip reason: Merged-In Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b with SHA-1 662e1bc915 is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2819677
Change-Id: Ibae31049dc107670bbc5d13bfac967ebf19c8e55
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
Set `avb_keys=no_such_key` for the vendor_dlkm dynamic kernel partition
to allow booting unlocked devices with a custom kernel. This allows a
few things:
1) Dogfooders can flash a custom kernel without wiping their device.
This can help developers track down hard-to-reproduce bugs without
rolling out a patch to the whole dogfooder population.
2) Developers can uprev their device's kernel without wiping their
device or packaging the kernel with an Android platform build.
Note: we are using "no_such_key" to ensure an AVB keys file doesn't
accidentally get created.
Test: Flash CI build. Then flash custom kernel on top.
Bug: 274825778
Change-Id: Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b
Merged-In: Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b
Set `avb_keys=no_such_key` for the vendor_dlkm dynamic kernel partition
to allow booting unlocked devices with a custom kernel. This allows a
few things:
1) Dogfooders can flash a custom kernel without wiping their device.
This can help developers track down hard-to-reproduce bugs without
rolling out a patch to the whole dogfooder population.
2) Developers can uprev their device's kernel without wiping their
device or packaging the kernel with an Android platform build.
Note: we are using "no_such_key" to ensure an AVB keys file doesn't
accidentally get created.
Test: Flash CI build. Then flash custom kernel on top.
Bug: 274825778
Change-Id: Iee542cf5ab4973ee9cb2c1fe66d00b642fdf525b
Trigger fsck on mount of /data if the value of ro.preventative_fsck is
not equal to the contents of /metadata/vold/preventative_fsck, then set
the file to the property to prevent future runs
See b/305658663 for context
Bug: 305658663
Test: Make sure fsck run after first boot and not after second
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:1bc693d338e8d26307d51bb6731d8e94f1df33f9)
Merged-In: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
Change-Id: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
am skip reason: Merged-In Ib4ec351fd5f2d59d161578440e8c0d36f8b68a6f with SHA-1 c6b5b5990a is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2774918
Change-Id: Id486c53997b232c2b02d18d1c7a6d773f1319110
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ib4ec351fd5f2d59d161578440e8c0d36f8b68a6f with SHA-1 c6b5b5990a is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2774918
Change-Id: I8f0576cf46996c9ff8d02cf69b0c05345e26de64
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ib4ec351fd5f2d59d161578440e8c0d36f8b68a6f with SHA-1 c6b5b5990a is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2774918
Change-Id: I1b75b5a02f0f999fd15d601fa4932b0c9f50ca8f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
am skip reason: Merged-In Ib4ec351fd5f2d59d161578440e8c0d36f8b68a6f with SHA-1 c6b5b5990a is already in history
Original change: https://android-review.googlesource.com/c/device/google/gs101/+/2774918
Change-Id: I51a81140c8882e60540742f189eb9edabd51cc62
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This reverts commit b8a0da464b.
Reason for revert: Increased jank reported, especially on the Pixel tablet
Bug: 301846142
Bug: 298975477
Change-Id: I8aa4f335cd61ef2800238424aeac2cedd6dcfb67
Many host applications expect and ask for lower resolution streams when
streaming from a USB webcam. To support those applications, this CL
adds support for 640x480 and 640x360 streams.
Bug: 301170431
Test: Manually tested that the resolution is advertised and streamed.
Change-Id: I78e9f97575784996aac94e576c7f23b0874a8d09
If Usb.cpp cannot write a zero value to the USB_DATA_PATH file, display
the message of "Not able to turn off usb connection notification".
Test: refactoring CL. Existing tests still pass.
Bug: 301016122
Change-Id: I0c5b7c4dc5bfe21ba17058536b5014eb5d69d1f3
Indicate to the kernel that the usb gadget is pulled up
by writing to `update_sdp_enum_timeout` sysfs node. Write
to this node will inform the kernel that it can lower the SDP
timeout alarm value which is used to detect an SDP port
vs a DCP.
ported from c5c5b127a7ed0db559d286284fe77b656bef6945
Bug: 275687235
Test: Check `update_sdp_enum_timeout` is written into after usb
gadget is pulled up. Verify that the alarm timeout lowers.
Change-Id: Id3ae7e7a20b236cec6604414a7f81860e868bdd0
Signed-off-by: Amit Sunil Dhamne <amitsd@google.com>
Write to /sys/class/typec/port<...>/device/update_sdp_enum_timeout
to reduce SDP enumeration timeout value when device is in charger
mode. This will enable faster detection of a DCP port.
ported from 6710e31a629f81cf308e1099f75a01c82db6d006
Test: Validate (in charger mode) that the sysfs attribute is 1
(meaning lower sdp timeout value is being used). Read dmesg to
see print showing timeout value is 5000ms.
Bug: 275687235
Change-Id: I1bc872911d7f1eab26e62fe6f12fba05608e0f83
Signed-off-by: Amit Sunil Dhamne <amitsd@google.com>
There are some regression reports. Disable them completely for now.
Bug: 297496375
Change-Id: I2a2b4d13366d3173c441e8ccad456a67ddd3a16b
Signed-off-by: Qais Yousef <qyousef@google.com>
- set lmkd's swap_free_low_percentage to 100
- decrease swappiness to 60
This tweak also aligns the policy with P23.
Test: boots with correct settings
Bug: 299975853
Change-Id: I0ed7088ddf2ff2fa0feca2197e5cc03c7f5c6778
Signed-off-by: Martin Liu <liumartin@google.com>
