- Removing expensive calls to map coordinates of front task to the tasks
behind it, instead relying on the precalculated task rects that we
already compute on each stack change update. To prevent rounding
issues, the task rects are now float rects.
- Also fixing crash when RecentsActivity starts before the SystemUI
component (only an issue when pushing SysUI apks)
Change-Id: Ia84e9b9d165c0ce171c7fe3797e561ef24157a0a
f3a62fbc58bbc7f081a53248cae48a8951294e8f added support for drawing
the background draweable when resizing an activity window.
However, after some additional discussion we decided that
R.styleable.Window_windowResizingBackground and
R.integer.config_windowResizingBackgroundColorARGB are not needed.
We use R.styleable.Window_windowBackground for the background
drawable and fallback to using R.styleable.Window_windowBackgroundFallback
which is now public if the first isn't set.
Bug: 24534744
Change-Id: Ia0507e25a1893ea941d259f1d4e88ce500dda154
- Moving all references of SystemServicesProxy and RecentsTaskLoader to
a single static instance in Recents. This ensures that we only refer
to an instance that is created with the application context.
- Moving ActivityInfo cache into RecentsTaskLoader with the other caches
which allows us to invalidate it less frequently. This requires the
loader to handle package changes to invalidate the cached infos
accordingly.
- Cleaned up old code to handle case where the Recents component for
secondary users might not be initialized (fixed in ag/773159)
- Moving the package monitor to the background thread.
- Cleaning user interaction and visibility changes to events.
- Fixed issue with sending events from binder thread.
Change-Id: Ie785347055736f6dd7802f32454f77073e20b83e
- Removing broadcasts for communicating with the Recents activity from
the component in favor of using events.
Change-Id: I2ddfde911bd1fd1b2d63bb84a0e7f0338f955df6
- Removing old broadcasts in favor of direct aidl interface between
system and secondary users. Also moving user specific implementation
into RecentsImpl, allowing Recents to handle proxying between users.
Change-Id: I4bd5ef1d1ee47309b7c754f50a5e8b2e2aab988f
After reset (docking) Pixel C Keyboard that was previously paired with
a device goes into so-called non-discoverable mode, where it will
establish connection only with device that it has connected before. When
scanning for available devices we need to wait till the keyboard starts
advertising itself as discoverable, and only then try to pair.
Also, let's flush the device cache when we attach the base to make sure
the device that we seen before and cached again in the right state after
reset.
Bug: 24915541
Change-Id: I136c1c4235080a25529b4b1c2b1da9bc18508811
Ensure that the user has had a chance to see it for a few
seconds after screen recording has ended.
Bug: 19121797
Change-Id: I52b69b2029439d42163ead5dc8748889b4f61934
In the new ranking, notifications with fullscreen
intents always take priority over those without,
such that when you get a call and a message
in succession, you would always see the
call on top and are able to pick it up.
Bug: 22778349
Change-Id: Ia9aaf009998fc9493f513dc71f2649d38ccf7a79
