It appears sometimes the Choreographer will call you with an
old frame (i.e. an animation time in the past).
Bug: 6457615
Change-Id: I7135e2f4f524c14fe4f58f9a367f764b66d68edc
This fixes an issue where the swipe-up gesture for search was broken
on phones and tablets. Because the underlying window was slippery,
there was a race condition between the touch moving outside the window
and the layout flag change in the search panel being noticed.
As a result, the code would sometimes inadvertently dismiss
the search panel even though the gesture was successful.
It also changes the timing slightly so we show the search
panel longer for quick gestures.
Change-Id: I30c04b21d3367db4d41c01f23e27edf366711462
Clean up related to new Vibration policy.
The vibrate behavior is now only derived from:
- presence of a vibrator on the device
- current ringer mode selected: NORMAL, VIBRATE or SILENT
If no vibrator is present the ringer mode can only be NORMAL or SILENT.
The control of ringer mode via volume keys when volume keys control the "master"
stream type (RING on phones, MUSIC on tablets) is as follows:
If a vibrator is present:
VOL- and volume equals 1: NORMAL => VIBRATE
VOL- and volume equals 0 and not continuous press: VIBRATE => SILENT
VOL+ and in SILENT mode: SILENT => VIBRATE
VOL+ and in VIBRATE mode: VIBRATE => NORMAL, volume = 1
If no vibrator is present:
VOL- and volume equals 0 and not continuous press: NORMAL => SILENT
VOL+ and in SILENT mode: SILENT => NORMAL, volume = 0
VIBRATE_ON and VIBRATE_IN_SILENT settings are not stored/retreived any more.
AudioService checks and corrects ringer mode and stream volumes if necessary when reading from
DB at boot time.
Also:
Added dump for stream volumes in AudioService.
Added device names missing in AudioSystem for USB accessory and USB device.
Issue: 6036529
Issue: 6414950
Issue: 6448163
Change-Id: I77fb821ec63e4e566320cac2701b4ac466e86aef
This fixes several layout issues on phones and tablets with MultiWaveView.
It adds a new background scrim to be shown behind the MultiWaveView
on the navigation bar.
MultiWaveView is updated to handle gravity constraints which makes layouts
much more flexible across devices.
Change-Id: I64068f4eaa81ef6c464247049117d53432fcacbd
Also be sure to cancel the longpress listeners when things
change.
Finally, increase the longpress timeout to 1.5x normal
longpress.
Bug: 6441520
Change-Id: Icea4d2a5c98a9a51a15f0762454de9e5cd454c50
Use the Choreographer for timing animations. Ideally we would
rewrite this code to use the animation framework instead, but
this change to use the Choreographer directly is easier and less
intrusive for now.
Change-Id: Ibb322de9424d4d109203951d48263766200ed7e8
Anything below PRIORITY_LOW will usually be hidden (unless
the NotificationManagerService has a compelling reason to
adjust the priority).
Bug: 6357857
Change-Id: Ic8a806a6db87b0473014a5d006279991272a44ea
We use the new TYPE_NAVIGATION_BAR_PANEL for this instead of
TYPE_STATUS_BAR_PANEL (which is indeed above the status bar,
but far below the navigation bar, which is the window type
used for the system bar now.)
Bug: 6319161 (ticker underneath system bar)
Bug: 6437342 (missing clear all button on system bar)
Change-Id: Ib58c0003c4c81db64edca2c1bbc2d764c3237ed0
On sw600 devices we show the notification panel in a smaller
rectangle, centered in portrait and left-aligned in
landscape.
Also remove a bunch of -large resources that shouldn't be
used anymore.
Bug: 6297838
Change-Id: I8ed3445ccb7df16e30870a4322d89786467c54df
On devices that had external storage, permissions weren't set correctly
on non-forward-locked applications. Also, moving forward locked
applications didn't work since DefaultContainerService wasn't able to
read it.
Fixed some faulty unit tests as well.
Bug: 6427212
Change-Id: I5c1f0bf5278549069c78939f0708c4c43a7d4006
It's too easy to press if it's *all* the way to the right,
though, so there a 2dp margin separating it from the bezel.
Bug: 6399312
Change-Id: If4ebcd4cfcee0c667bcc6142af86c04445f41fea
Two parts to this:
1. We were looking at the measured height of the close view
for a lot of our computations, which---particularly with
recent changes that dispense with the old 3-window
implementation---is increasingly unreliable
2. We were overestimating the minY that the panel must be
pulled down before animation starts. It was enforced
jankiness!
Bug: 5359178
Change-Id: Ie09b62226b7b0977527348b5527478665ece1df8
