AOD might be off but it can become visible when the user double taps
or lifts the phone. We should prepare the window manager for these
cases.
Test: turn AOD on and off, set screen lock to 'None', double tap display
Bug: 110938816
Change-Id: I6f2db86579d5b86a86fcd1a4515ee77c78460c9d
AOD might be off but it can become visible when the user double taps
or lifts the phone. We should prepare the window manager for these
cases.
Test: turn AOD on and off, set screen lock to 'None', double tap display
Fixes: 110938816
Change-Id: I6f2db86579d5b86a86fcd1a4515ee77c78460c9d
Merged-In: I6f2db86579d5b86a86fcd1a4515ee77c78460c9d
Arbitrary delays were introduced a while ago to deal with device
specific issues but these delays ended up affecting battery life
significantly. Although removing them completely isn't possible,
they can be reduced to more conservative values.
Test: cover prox. sensor multiple times with multiple durations
Fixes: 110902271
Change-Id: I2731fc7a5414f796e96a6c97959c395b10c32faa
Codepoints that are encoded to 4 bytes in UTF-8 are not allowed in
Modified UTF-8. They instead should be encoded as surrogate pairs in the
same way that CESU-8 allows for surrogate pairs. This will also cause 4
byte UTF-8 codes to be represented in 6 bytes.
Bug: 37140916
Test: aapt2_tests
Change-Id: I155dc24f166139d1d36a16bac088dcfcd59eb321
Pass --include-annotation-classes tools/metalava/stub-annotations
to metalava so that the stubs end up in the final jar. They will be
post-processed with metalava --rewrite-annotations to avoid affecting
the public SDK.
Bug: 110532131
Test: m out/target/common/obj/JAVA_LIBRARIES/metalava_android_stubs_current_intermediates/classes.jar
Change-Id: Icb9268a72aa7de82ed6ad88aef9ac813796f9bf9
Merged-In: I116643925a3a9594e8590c3714e93d0fb0ac372f
This CL logically reverts the following CL (and some subsequent
changes) to stop restoring spell checker related secure settings.
* Ib8382f0296f0726b64494d3b1fd8237e13adb540
06cbaddb87
Reason for revert:
Although we believe it would be great if we can seamlessly migrate to
a new phone with keeping spell checker related settings, there still
remain several tricky scenarios.
* We are not ready to distinguish whether a certain spell checker
related setting was explicitly set by the user or programmatically
set by some components in the previoud device. This includes the
case where TextServicesManagerService (TSMS) itself automatically
updates those settings e.g. by selecting a default spell checker
service from the pre-installed ones. We are not sure if trying to
migrate such an auto-selected setting to a new device actually
makes sense, especially if it happens without any user
confirmation.
* We have a strict rule about what spell checker service can be
selected automatically, and the rule has been that only
pre-installed spell checker services can be automatically selected
by the system, unless some system components that have
WRITE_SECURE_SETTINGS permission overrides it. Mechanically
selecting a spell checker service just because it was enabled in
the previous device may not fit this model well.
* Unlike IMEs, currently the Android OS allows only one spell checker
service to be enabled. This means that if the new device doesn't
have the corresponding spell checker service, the user will lose
spell checking functionality even if the device pre-installs
functional spell checker service. This problem is hard to notice
because unlike IMEs spell checker service does not have its own UI.
* Also unlike IMEs, spell checker related secure settings are still
hidden and not published as public APIs. Those settings do not
have no official compatibility story across devices yet.
* It is also possible that the default spell checker service in the
previous device is not published to all the devices thus there is
no way for the the new device to install it.
This CL therefore excludes spell checker related settings from
backup/restore, as a short-term answer to above scenarios until we
come up with better ideas to deal nicely with them.
Bug: 110367605
Test: atest FrameworksCoreTests:android.provider.SettingsBackupTest
Test: atest FrameworksCoreTests:android.provider.SettingsValidatorsTest
Change-Id: I8e4a0d4b3b758a84d5a075fa52851b1e8dd707eb
When a service is disconnected mServices will be updated
to no longer contain the service binding. In order to
prevent an accidental double-bind for services bound directly
in ManagedServices due to not detecting a service is still bound,
make sure that if the service is still bound that we don't rebind.
Bug: 77821801
Test: atest FrameworksUiServicesTests:ManagedServicesTest
Test: manual - check service bound after force-stop/app update
Test: manual - check service not re-bound after disabling a component
Change-Id: Id600357ad0b84f157cf9666680bf53b7fe125d96
(cherry picked from commit d814134e9ee652de5b54c7c20c8eb3c1a8f590df)
Before, a new translation was only calculated when the device enters
AOD, and then, during time tick, we would only move it 5px wich isn't
enough.
Now, the translation varies 5dps vertically on every time tick.
Fixes: 110888643
Test: take screenshots for N minutes and compare them
Change-Id: Ia3f239d669b83aad0d97d8d7a7f7374f4890777d
Merged-In: Ia3f239d669b83aad0d97d8d7a7f7374f4890777d
Activate WM animation and remove scrims when
fading keyguard from the pulsing state to prettify
animation on new devices.
Test: wake up with fp from pulsing to launcher
Test: wake up with fp from pulsing to app
Fixes: 110824274
Change-Id: I0446f26939a2e25cd50d0d39f3fc703019196f7a
Otherwise there is a big performance hit in all kinds of
situations where we do operations with the region, specifically
when:
- updating input windows
- insetting the cutout during layout
- touch dispatch
Test: DisplayCutoutTest, WmDisplayCutoutTest
Bug: 110464019
Bug: 110452325
Change-Id: I94a25c3794ecd33b8b7204ca308ac91623498f13
Add a "debug.hwui.skia_atrace_enabled" property that allows to
record a systrace with skia drawing ops. App need to be restarted
after setting the new propety to true.
Test: collected skia trace with systemui
Change-Id: I2d1c5911714bfc911894f633ec2df2f6bb953b48
Before this CL, when TextView's textSize attribute was set to 0sp in
XML, the text would still be visible on the screen, as the actual
textSize set was non zero. On the other hand, if the text size was set
to 0sp programmatically, the text would not be visible. This was a P
regression, as on O the text would be invisible in both cases.
This CL fixes the attribute reading stage in TextView, allowing the
application of a 0 text size on the view.
Bug: 110251171
Test: atest CtsWidgetTestCases:android.widget.cts.TextViewTest
Change-Id: I3798361e182f45a67cd0a69d40e09e559375aa20
