When we dock with Pixel C keyboard we normally expect to find it, and so
we perform a low latency scan (which uses highest duty cycle). But if
keyboard is not charged or if tablet mode trigger misfires (because
there was a magnetic object in proximity?) we may not find the keyboard
and will continue scanning indefinitely, impacting WiFi performance and
draining battery. To avoid this scenario let's stop scan if we do not
find "our" device in 30 seconds.
Also remove STATE_WAITING_FOR_STATE_PAIRED as it was unused.
Change-Id: I4bf1a9a163d3165eaa5e8f1cc2d2938465d454af
(cherry picked from commit 6c12c3a6538591b5fa6e11cb4f583aa494e0ce5c)
Signed-off-by: David Riley <davidriley@google.com>
The notifications are now measured at wrap_content such
that the layout still looks good even if the text
was ommited instead of arbitrarily making it bigger.
This also fixes some small rounding issues where the
expanded notification was just a pixel bigger than
the collapsed version.
Bug: 26185377
Change-Id: Ie3339ff75680ab512446605055304576e058f588
Also caching the notification minheight in the algorithm
far less agressively, because it led to bugs.
Change-Id: I57155103bf2700be2e98e686fdd0077ce8e8405b
The notification algorithm had some state which was simply
dropped on rotation and therefore weird things could happen.
This is now fixed.
Change-Id: Ibb3d007b3298f745743bd3a5889bccebebf8105a
Also fixed a bug where the guts didn't have the
right size and in general cleaned up the intrinsic
height. The guts also animate nicely and the position
of their animation starts on the finger.
Change-Id: I62447dd77ace36161740dfdf3d18103524e2eb21
The views were based on a legacy systemUI notification.
We are now creating it in Notification.java in order to
always have the latest visuals and avoiding duplicate work.
Change-Id: I3f544cad069a8eab34d4464404d020e06d7f6626
The notification children didn't respect the given dimensions
when measuring and was simply measuring itself as high as desired.
This lead to a bug where the parent could crash when a layer was
set on it.
We are now measuring the container at most with the height of
the given size and let children draw over our view bounds.
In oder to still allow touch in those regions we also
override the touch rect.
This also simplifies the rest of the touch handling.
Bug: 26159274
Change-Id: I728553a6386455e6632e2511be8a3e7cb447e89b
- Also cleaning up the Task to remove some confusing nomenclature
related to task properties. Now there is a single icon and title,
and we keep a copy of the TaskDescription for future icon loading.
- Also changing a few cases where we should be calling isFreeformTask()
Bug: 26221779
Change-Id: Iac20cc7b4912f76c14232a323981ab2e8f62628a
- Fixing regression where we were clobbering the freeform stack order
- Ensure there is padding between tasks
- Fix the header bar animation
Change-Id: I69ced3e3cb2f0c761ddf0c3bd00b17c847d74c0b
* changes:
Allowing tasks to be swiped away in the history view.
Loading activity icons in History view.
Ensuring that the undocked task is visible in Overview.
