Instead of keeping track of confirmations per-package, track
a global confirmation per-user. If the panic signal is received,
reshow the cling at most once per-user per-reboot.
Ensure the nav bar becomes visible after the panic signal.
Usually this happens as a side effect of showing the keyguard.
However, in the case where there is no keyguard (Security = None)
show the transient nav bar temporarily as a hint.
Also listen to the correct observer uri to pick up confirmation
setting changes.
Bug:12242125
Change-Id: Ic95e2a8630ec3802b8ef462fcaa92366b9343a3f
* commit '7ef544f07f3bb78d3a49c5cd60ad667964cedd57':
add google cast feature page edit other feature pages for consistent call to action paragraph and remove 'preview' notice from Drive page
* commit 'dac4429f21caffea61b626797afd142db5025e42':
add google cast feature page edit other feature pages for consistent call to action paragraph and remove 'preview' notice from Drive page
* commit '08d28f59bd74ab4109cf5343ef056a8d4b796ef6':
add google cast feature page edit other feature pages for consistent call to action paragraph and remove 'preview' notice from Drive page
* commit '6d1d21340fe6ca84fdef76dd6f9ba7c315b7a73e':
add google cast feature page edit other feature pages for consistent call to action paragraph and remove 'preview' notice from Drive page
* commit '11bb34da5f68f70f3350199e3578445d9a1eaae3':
add google cast feature page edit other feature pages for consistent call to action paragraph and remove 'preview' notice from Drive page
* commit '9854f69f75352e473e34410b0b298b7c7f04434a':
add google cast feature page edit other feature pages for consistent call to action paragraph and remove 'preview' notice from Drive page
Modified ActivityView to inject touch events it receives back into
its activity container. The container then injects the event into
the input system along with the display id of the underlying virtual
display.
Change-Id: I23d018a2f7dd30f1f833f522eb7f143b43d8e637
At least part of what is broken. Other stuff still seems to be.
Change-Id: I367dc0377bd5b4e59d9d9b68f3506bf1d64aa591
(cherry picked from commit 32bb5fae353b5bb6275e75952e89c514c7369cee)
Modified ActivityView to inject touch events it receives back into
its activity container. The container then injects the event into
the input system along with the display id of the underlying virtual
display.
Enhanced the input system to support concurrent dispatch of touch
events on multiple displays which is required for this to work.
Change-Id: I9cf1870db3be6f99a52ed9a1e3ceafe42c940093
In scanPackageLI(), the first provider to claim an authority wins
over any other later providers. To match this behavior, this changes
ProviderIntentResolver to ignore later providers with the same
ComponentName.
Without this behavior, AM.getContentProvider() could end up wedged
waiting for a provider that generateApplicationProvidersLocked()
never decided to spin up.
Bug: 12956224
Change-Id: I37d3e6e9cf3eea2cac4c0e914134f6c83b2fc2bf
Remove all of the pieces except the PointerController and SpriteController over
to frameworks/native in preparation for inputflinger. Those two need to stay in
frameworks/base for now because they depend on Skia currently. In the long run
they should be merged into either the InputManager or the WindowManager rather
than as a part of the inputservice / inputflinger.
Try 2.
Change-Id: I84259356d3eb8efc5aefb9d6b311b5fc590ea3ed
