When closing the QS panel the alarm did the normal
transformation, regardless whether we were in a
detail state. This lead to the alarm overlapping
with the title.
Bug: 17581501
Change-Id: I0318f6778063af11f388e6c7fe8bbb30105ca246
In the spooler we have the renderer reading a file to visualize
content and the app writing a file to produce the content. Since
we have to swap the file under the renderer we have a mutex file
provider that both parties can request, use when released, and
release when required. This enables us to request the file which
closes the renderer and when the renderer is closed ask the app
to write some more pages, then open the renderer, and so on. The
mutex file provider was throwing of a thread that does not own
the file thries to relase it which is not needed, this should be
just a nop.
bug:17607134
Change-Id: Id6a2ce92d70077f57978b95315648faf02c13c68
Rather than using announceForAccessibility, which will provide the
wrong experience for Braille users, send a
AccessibilityEvent.TYPE_WINDOW_STATE_CHANGED.
Bug: 17578404
Change-Id: I3e2c465511cf2135f216d01d29319a057ebbfbda
Fixes a bug where the force lock gesture was not available
when an accessibility service was active, but touch exploration
wasn't.
Bug: 17514298
Change-Id: Ib42e28f643559040ad5f24d45456b0a41008c647
Change the listening in CastControllerImpl so that it will always
at least passive discovery when callbacks are added. When discovering
is set this will switch to request discovery. This allows the
status bar to catch disconnect callbacks when QS is not discovering.
Bug: 17555869
Change-Id: Id2a80b98f6c7ca7e6a4d0ff00315d10a109e8259
The spooler communicates with he remote PDF renderer asynchronously.
When print is confirmed we close the renderer, destroy it, and unbind
from its service. If we unbind from the service after the print activiy
is finished we get a crash. The bug was that we did not wait until we
disconnect from the remote renderer before finishing the print activity.
bug:17583115
Change-Id: I55b0135f9c5658b3a4fda2901b8b3bdef044e211
This change fixes several issues in how the display's power state
was coordinated to ensure that the display is not turned on until
the pulse is ready to be shown. It also greatly simplifies the
wakelock logic and makes it completely deterministic instead of
relying on timed delays.
Bug: 17516245
Change-Id: If2b96845a010f2d05c610970257d898f32ccacb7
Instead of clearing the Statusbarwindow buffer in the beginning
we now draw the scrim with mode SRC and therefore a whole screen
of overdraw is saved!
Bug: 17287256
Change-Id: I29f14a2c3d4cb087c422ae6f486d23d7f8ec173b
- Reactivate our configured keyguard falsing swipe threshold
for secure keyguards, but only when dozing.
- Add DozeLog helper to capture/maintain interesting events
about the doze + unlock process, enabled by default, but
only on devices that start dozing at least once.
- Dump summary counts + logged events to dumpsys output.
- Pass notification pulse "instance" as an extra to the scheduled
intent, so we can log accordingly.
Bug:17496795
Change-Id: I7e88f93bfc967bdc06550cf1fe5e74d535edd774
Instead of comparing MediaControllers via reference equality
(which is never true), go deeper and check whether the two
controllers are connected to the same IBinder.
Bug: 17571414
Change-Id: Id25d70be0a60d1900e977310dedcc7063552e018
When user chooses to save to PDF we open the document chooser UI.
Now if the user now backs to the print UI without choosing a file,
the print UI has all options disabled and the back button does
not work - the user is stuck. This is because we were not
transitioning the print UI in the correct state.
bug:17557454
Change-Id: I385129e106ed41564b89137ca54d409127ba8ff0
