This flag will enable the BLASTBufferQueue adapter for use by ViewRootImpl.
BLASTSync and the BLASTBufferQueue in SurfaceView are still behind seperate flags.
Bug: 168506246
Test: Days of manual testing on multiple devices (stressed: app switching, rotation, SurfaceView, PIP, Split-screen). Multiple presubmits. 5 passing runs of flicker. Systrace inspection. App startup perf tests. Inspection of jankstats from experiment based flip in R dogfood.
Change-Id: I2b6e37884d938d327479977becbbce8e38e521f0
These are APIs that have @UnsupportedAppUsage but for which we don't
have any evidence of them currently being used, so should be safe to
remove from the unsupported list.
This is a resubmit of ag/12929664 with some APIs excluded that caused
test failures; see bugs 171886397, 171888296, 171864568.
APIs excluded:
Landroid/bluetooth/le/ScanRecord;->parseFromBytes([B)Landroid/bluetooth/le/ScanRecord;
Landroid/os/Process;->myPpid()I
Landroid/os/SharedMemory;->getFd()I
Landroid/hardware/input/InputManager;->INJECT_INPUT_EVENT_MODE_WAIT_FOR_FINISH:I
Bug: 170729553
Test: Treehugger
Change-Id: I8285daa8530260251ecad6f3f38f98e263629ca7
New flag: Settings.Global.SHOW_NEW_NOTIF_DISMISS
- Do not backup to other devices
- To be removed before release
Usage:
adb shell settings put global show_new_notif_dismiss [0|1]
- 0 to disable
- 1 to enable
Test: treehugger
Bug: 171817112
Change-Id: I8712a7f8a2bac6483afd52ede9e478f8b08d661d
These are APIs that have @UnsupportedAppUsage but for which we don't
have any evidence of them currently being used, so should be safe to
remove from the unsupported list.
Bug: 170729553
Test: Treehugger
Change-Id: I4c8fd0006f950de9955242e93968fb0996ceb372
Introduce Settings.Global.hdmi_cec_version. Stores an integer value
based on the CEC version constants defined in the HDMI-CEC
specification.
Defaults to v1.4b.
Bug: 166227067
Test: atest HdmiControlServiceTest
Change-Id: If3d85991230c00af4482076d90bf9a730ab385ae
Renamed panic to "emergency" or "emergency gesture" to
avoid speculation once source code is accessible to
parties without full context.
Bug: 169946710
Test: rebuild
Change-Id: Ic05405dabb04ae59960ea60ab3618fc8e6a741b2
This migrates flags inside QuotaController to DeviceConfig.
DeviceConfig is the recommended way and using it means
that we only operate/parse the set of flags that changed instead of
every single flag whenever one of them changes.
This uses the JobScheduler DeviceConfig namespace instead of creating a
wholly separate namespace just for the controller.
Bug: 124466289
Test: atest CtsJobSchedulerTestCases
Test: atest FrameworksMockingServicesTests:ConnectivityControllerTest
Test: atest FrameworksMockingServicesTests:JobSchedulerServiceTest
Test: atest FrameworksMockingServicesTests:JobStatusTest
Test: atest FrameworksMockingServicesTests:QuotaControllerTest
Test: atest FrameworksServicesTests:JobStoreTest
Change-Id: Id397dccc6d9c40bac1a9837addcab514f509a721
This migrates flags inside AppStandbyController to DeviceConfig.
DeviceConfig is the recommended way and using it means
that we only operate/parse the set of flags that changed instead of
every single flag whenever one of them changes.
Bug: 124466289
Test: atest AppIdleHostTest
Test: atest CtsUsageStatsTestCases:UsageStatsTest
Test: atest FrameworksServicesTests:AppIdleHistoryTests
Test: atest FrameworksServicesTests:AppStandbyControllerTests
Change-Id: I1aa5afc7f96e121bceccce44def4b86883b0a3c9
We set magnification capabilities all by default, but if the user
is using full-screen magnification before migration, we will set it to
full-screen.If the above situation happens, we show a prompt dialog to
inform theuser the new feature when using full-screen magnification
first time.
Note the default value will be applied if the user erases all datas.
Test: 1. Enable/Disalbe full-screen magnification and observe
the values after flashing.
2. Erase all datas and observes the settings values.
atest SettingsBackupTest
Bug: 162525393
Change-Id: I3dc749c2414f3aa9162c0f2a31b512c5e6a3ae80
ANGLE global settings variables have an unnecessary prefix, remove it.
Bug: b/170982184
Test: atest CtsAngleIntegrationHostTestCases
Change-Id: Id98e69820c90ede16cec8e798c0c77200b951966
Those annotations could be inferred by some tools (like Kotlin), but the
https://checkerframework.org/ doesn't check inherited annotations
complaining about all equals() invocations that get nullable argument.
The change was generated by running
find . -name \*.java | xargs sed -i 's/public boolean equals(Object /public boolean equals(@Nullable Object /'
in the frameworks/base directory and by automatically adding and
formatting required imports if needed. No manual edits.
Bug: 170883422
Test: Annotation change only. Should have not impact.
Exempt-From-Owner-Approval: Mechanical change not specific to any component.
Change-Id: I5eedb571c9d78862115dfdc5dae1cf2a35343580
Based on the CONVERSATION_TYPE flag, shows only priority conversations
or all conversations. Defaults to showing all conversations.
Test: locally
Bug: 169783793
Change-Id: I4cb62cc9e4f9e5e488247d97b5624be97a94f8b0
Test: manual - flashed the phone and verified the logging and statsd sampling with default settings
Bug: 131859447, 162927074
Change-Id: I2637100b4945732f7bd792831749ca2614971c5e
The WebView fallback mechanism was removed in Q and replaced with code
to migrate the state of upgraded devices to the new configuration. This
is no longer necessary; remove the logic to simplify the code.
The notion of a WebView provider being designated as the fallback is
kept, as this is still used by the code which checks if there is no
valid provider at all at boot time and tries to fix the situation by
re-enabling the fallback provider for all users - this was added for
b/132815849 and should suffice for any devices which haven't executed
the fallback migration code.
Bug: 129470358
Test: atest WebViewUpdateServiceTest
Change-Id: I4de777b650fb793903f6df74a7ff639190d8b0a9
Add new Settings.Global.SHOW_NEW_LOCKSCREEN property. When enabled, new
lockscreen & aod UI + transitions will show. This is a temporary flag for the
purposes of protoyping which will be removed before release. Therefore, it should
not be backed up.
To toggle the flag (value = 0 is disabled, value = 1 is enabled):
adb shell settings put global show_new_lockscreen <value>
Test: manual
Bug: 170228350
Change-Id: I3b40b1de9bb80d43218fa1e8661fba47b50e9888
Add values to track activation, intensity level, and persistence state
Add an activity action to open the subpage directly
Test: builds
Bug: b/128465252
Change-Id: Icc9989254bc044377c162a8d94eec37723d86c19
The feature is disabled by default and can be in one of 3 modes:
disabled, permissive and block. In permissive we only log but
don't block the touch. This knob is implemented in a global setting
block_untrusted_touches. It can also be disabled per occluding app using
app-compat infrastructure, so if you disable for a certain app, overlays
of that app won't have the chance of blocking touches. More details
on these on go/try-cross-uid-touches.
Each window has 3 modes related to touch occlusion: ALLOW, USE_OPACITY
or BLOCK_UNTRUSTRED. Check code comments for the meaning of each. If the
feature is turned off for the app, then the mode is ALLOW. Else if it's
a SAW, then it's USE_OPACITY. Else it's BLOCK_UNTRUSTED. These states
are passed to InputDispatcher, who then perform the proper checks and
blocks or not the touch.
If input dispatcher deems the touch unsafe, depending on the feature
mode, we filter out such touches and log a message to logcat.
I also introduce a global (secure) setting
MAXIMUM_OBSCURING_OPACITY_FOR_TOUCH which represents the maximum
opacity allowed per UID that's obscuring the touch-consuming window
according to some rules, which are discussed in topic CL for
InputDispatcher code. This maximum is initially set to 0.8, but we'll
be conducting local experiments to determine the final value.
Test: atest WindowUntrustedTouchTest
Test: atest inputflinger_tests inputflinger_benchmarks libinput_tests
Test: go/try-cross-uid-touches for manual testing
Bug: 158002302
Change-Id: I462858ad5f0d11b1261748489385e6409e38e4b1
When the user changes, populate the global config with the current
user's setting state. For new users, don't keep the previous user's
preference
Test: manual, switched between users
Bug: b/110991537
Change-Id: Iae412bccd64784a597ed8d493f1bda4984841cac
