The rendering pipeline expects frame vsync times as
System.nanoTime(). When the frame vsync time is behind
the most recent frame, the render request is dropped [*].
This reverts the value back to System.nanoTime() which
was accidentally changed in ag/15819081.
* frameworks/base/libs/hwui/renderthread/TimeLord.cpp:46
Bug: 217046739
Test: ???
Change-Id: I21d8737e7acb5ac13bfbcf150006415431d874aa
Some 1p apps may not provide all the resources in the apk, need to
reply air update to download other language resources
Bug: 213980690
Test: Test apps that the locale in <locale-config> more than
resources.
Change-Id: I1c050ffc8bba76df42832a3641ddcba1111afd33
Was attempting to adjust padding on a View that didn't exist.
Also adding additional conditional behavior for similar issues:
- Fix the padding at the bottom based upon insets.
- Only trigger mini resolver for ResolverActivity itself.
- Add comments defining mini resolver.
Test: atest ResolverActivityTest
Test: Manual test of rotation not crashing and padding looking better.
Bug: 222497968
Bug: 175433480
Change-Id: Ie38787f61dc523bd812b828ec16830b91f61ce0b
- Close blank layout after title disappear when search bar is expanded.
Bug: b/227287277
Test: local, see b/227287277#6
Change-Id: I6b5f6990cacf6da9e17b743519ae554af32f691d
Listener to ACTION_USER_SWITCH intent and update the settings key when
user switched.
Bug: 231575466
Test: 1. set different settings keys for different user.
2. switch between users and see if the setting value is correct.
Change-Id: Ia1afcb6121b296b293bef0ba7d0a0be25b857554
AIDL can't accept subclasses, see more info in the bug
Bug: 223022163
Fixes: 223022163
Test: launch WSJ, click on share
Change-Id: I0015fda3a6fb741b109f7d3d00df1da6f7d64863
If the navigation bar color view is not opaque, we shouldn't clip the
background drawable. Otherwise, the view hierarchy cannot fill surface
buffer, and the un-filled area would display things previously drawn on
it, which is not expected.
Fix: 204834350
Test: Open a doc in Docs in split-screen, and scroll down to the end.
Change-Id: I050f3fa301412b71a7ae15d60fb49853c4be161e
This was a regression introduced in ag/17913997 because
I missed that the legacy code included the ternary
`? 0 : 1` to convert from boolean to int value in this
(not-type-safe, see b/231577676) API call.
Bug: 231491021
Bug: 231577676
Test: compile/presubmit. This doesn't prove that the fix
works (we must just not have coverage, or we would've
caught the regression the first time) but it does validate
the syntax and confirm that there are no other unintended
changes (stray keystrokes...). The fix is trivial; this CL
simply restores the exact behavior pre- ag/17913997.
Change-Id: I706dee50e074da3ca40cde5b83abfd076a271959
The feature punts to QPR so disable or remove code from the build
time.
Bug: 222185402
Test: build pass and can boot to home
Test: make sure the toolbar using local implementation
Change-Id: Idad82c3c46ddce0731a26f4599de01eecb0e52c3
* changes:
If something is suppressed from the notification list don't bubble it
Tell NoMan to update the auto-expand flag
Allow SysUI to update BubbleMetadata#FLAG_AUTO_EXPAND_BUBBLE
To distinguish the requirement between all numeric and not all numeric
when COMPLEXITY_HIGH.
Note:
The second param of applyComplexity() changed back from
withNonNumericCharacters to isPin.
This was changed from isPin to withNonNumericCharacters in Change
I3227d4d8e6825b5c4ea525828d7e09f52702065b without changing the caller.
This currently not causing any issues because applyComplexity() only
used by KeyguardManager.getMinLockLength(), which currently never be
called with COMPLEXITY_HIGH.
Fix: 227149118
Fix: 173167839
Test: manual & robolectric
Change-Id: I7e0d4a1edf42327452b7d9a564258b26865c056e
Includes general information as well as the system and app actions (or
media actions if there are no app actions)
Bug: 204173025
Bug: 199490119
Test: manual - check notification content from aosp notification listener
Change-Id: I6a15e443ad8f1fa17bd76e52c002909faa1c44db
