These sometimes trigger binder calls, that can cause jank on the
first frame of expanding the panel.
Bug: 30442298
Change-Id: Id60fd5ee9732515cd6f9645c7ab307c949dfc506
This feature isn't generally useful on this screen and provides
an additional mechanism for falsing, so it should be disabled.
Fixes bug 30443528
Change-Id: Ibdba485917b5e66780ff4915f48ff2014f195eca
- Add null checks to avoid crashing in transient state with no
enabled packages during user switch.
Bug: 30574163
Change-Id: I316373e900d4be35be7691b50057d0701b7fb4a5
We still check for security errors of non-system apps trying to send
protected broadcasts at the front.
However, the WTF check for system apps sending non-protected broadcasts
is now moved down to where we actually resolve the receivers, so we
can loosed then check to make it okay as long as you are sending an
explicit intent to only appropriately protected receivers.
Change-Id: I5214c6c26a60de083f1f9578bcc5e95ba19f7001
- Normally when a user is unlocked, SM scans all updated apps
since the last scan to see if their manifest shortcuts have changed.
- There was a known issue that's been fixed already that'd result
in all shortcuts being removed.
- To work around this issue, let's scan all packages after the next
user unlock.
- This can be done by just renaming the XML attribute name to persist
the last app scan time.
Bug 30591723
Change-Id: Ie9f723ef30a1c991990d981193841cb203c094ad
* changes:
Remove lock contention when unlocking users
Only get trace name if tracing is enabled
Fix multi-window drag jank if vsync-app is before vsync-sf
Prior to N, our widgets were not converting MarginLayoutParams
properly between ViewGroups. The fix intrudced some issues in
older apps as the broken conversion code would hide developer
errors. This CL guards the change with a target API check so
that we don't affect older apps.
Bug: 30378230
Change-Id: I215281d261b553c3b4cedcd29ea0a861df809471
Add metrics log when fingerprint swipe to expand/collapse notification
panel is handled, and increment the notification and quick setting open
count correspondingly.
Bug: 29257528
Change-Id: Ic24c6463a4400711874602157e2fcadc7f0f6da6
Bug: 30587465
Someday maybe the technology will exist to
allow sharing a simple constant between
Java and C++, but today is not that day.
Change-Id: I17694746cb8712058133cd5ea10c47b9909f740b
If vsync-app is a couple of ms before vsync-sf, we handle the touch
in SystemUI at vsync-app. Then, we have extremely little time to resize
all the stacks in activity manager until vsync-sf, so sometimes this is
done before vsync-sf tick, and sometimes after, which leads to jank.
Figure out the difference of vsync-app and vsync-sf in SystemUI and then
post the updates to be processed at vsync-sf so we have the whole 16ms
to process the change.
Change-Id: Ibe7cb6dfe9fbfe2d3e68e522a95a75138fb0dcf1
Fixes: 30437123
