In the kernel, it is possible for the DisplayPort Alt Mode
driver to queue an Enter Mode message to the tcpm and have
that message be interupted by a Power Role or Vconn swap,
which results in the Port Partner never entering Alt Mode.
Add a debounce that checks to make sure that the port partner
enters Alt Mode when DisplayPort Alt Mode is active on the
port. On trigger, reattempt to send Enter Mode through the
tcpm up to 2 times.
Test: Manual test on device - put device into Preferred
Source role, test to see if Alt Mode reentry triggers
when original entry is interrupted by PR Swap from
monitor.
Bug: 308383356
Change-Id: I96563c9900a01e428850e4873371bcdb0225aa07
Signed-off-by: RD Babiera <rdbabiera@google.com>
Set `avb_keys=no_such_key` for dynamic kernel partitions 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: Ibf3cee491404b9efc18c49936edf64c2e3084adf
Report COMPLIANCE_WARNING_INPUT_POWER_LIMITED instead of
COMPLIANCE_WARNING_OTHER to flag incompatible chargers. The underlying
logic that generates the warning remains the same, what's changed is
the enum that's being used.
The purpose of the change is to have a warning type that better
represents what actually happens and free up COMPLIANCE_WARNING_OTHER
that was intended to act as a fallback reason code.
The flag enable_input_power_limited_warning controls whether to switch
to the new enum, while the flag enable_usb_data_compliance_warning
controls the new enums that are added as FlaggedApi in the framework.
Both flags need to be on to enable the change.
Bug: 308700954
Test: manual tests with local flag override
Change-Id: I6595706d1b83d533fc2d3e29086773270e045ede
Checks syntax and simple brace balances for all JSON files.
Test: Edit any json file and try upload
Bug: 127794899
Change-Id: Ia302d5aa13328ca4e0c7c2c8b10bf54c2542a1ff
Cherry-picked from 19eb98145d.
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
Change-Id: Ie6b9fc94752d91e77e8fc48979216917c1fd9ec3
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
Cherry-picked from http://ag/25163335.
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
Change-Id: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
Change-Id: Ie6b9fc94752d91e77e8fc48979216917c1fd9ec3
Merged-In: Ie6b9fc94752d91e77e8fc48979216917c1fd9ec3
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
Cherry-picked from http://ag/25163335.
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
Change-Id: I1263d2d55fe22d994ae8c8654b1e75ad9e4ddafe
Change-Id: Ie6b9fc94752d91e77e8fc48979216917c1fd9ec3
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
By the legal requirement, Pixel devices shipped in 2024 shall show the
default browser/search engine selector. The SearchSelector app provides
the selector flow and a non-dismissable notification to comply the
requirement.
This feature is approved for 24Q1 and is required to cherrypick to
selected Pixel devices.
Test: Flash a ROM build and validated the permission being granted by
default.
Bug: 298575926
Bug: 302280560
Change-Id: I895b9f0ed3980e31714ae0ee18071dab8b9039ec
Revert submission 25144243-Initial SearchSelector Drop
Reason for revert: DroidMonitor-triggered revert due to a breakage, bug b/307486020
Bug: 307486020
Reverted changes: /q/submissionid:25144243-Initial+SearchSelector+Drop
Change-Id: I141000a9bc18409652f8824f686793f1e4fdeb3d
By the legal requirement, Pixel devices shipped in 2024 shall show the
default browser/search engine selector. The SearchSelector app provides
the selector flow and a non-dismissable notification to comply the
requirement.
This feature is approved for 24Q1 and is required to cherrypick to
selected Pixel devices.
Test: Flash a ROM build and validated the permission being granted by
default.
Bug: 298575926
Bug: 302280560
Change-Id: I86a4d77579039cd76c813103d91e56021ebda361
