Check explicitly for null listeners in NMS, throwing
IllegalArgumentException (on the small list of exceptions
that survive RPC boundaries) with a message.
Normally this situation is caused by listeners that attempt to
perform NM-related actions before they are bound. Check for
this case in the base NLS class and avoid the call to NM if we
know it will fail.
Although it's tempting to throw an IllegalStateException on the
client side, preserve the existing semantics for backwards-compatibility
purposes. That is, silently fail (or return null) - and provide a
log warning.
Bug:12805707
Change-Id: I0d92fd0d460a8592e8a23fd8fd718ae2ba3bd4c7
* commit '7594767e55e011101ed9341f01d40730fdbd4cc7':
add document about GoogleApiClient and one about GoogleAuthUtil also remove the Authorization document from the Google Services section. bug:10679818
* commit 'aa318b2851042c6f98723446f33469a6545c7294':
add document about GoogleApiClient and one about GoogleAuthUtil also remove the Authorization document from the Google Services section. bug:10679818
* commit '879592d89a78383a9e3cd29d53357f34337e5f04':
add document about GoogleApiClient and one about GoogleAuthUtil also remove the Authorization document from the Google Services section. bug:10679818
* commit 'bc64716cfb1269d07b64f89c3b46800afa5dc266':
add document about GoogleApiClient and one about GoogleAuthUtil also remove the Authorization document from the Google Services section. bug:10679818
* commit 'a2739fa795981f597b044e93a5c552051cfe1c00':
add document about GoogleApiClient and one about GoogleAuthUtil also remove the Authorization document from the Google Services section. bug:10679818
* commit 'a4c5bba07e121569ab504b2191ee576f09407f5b':
add document about GoogleApiClient and one about GoogleAuthUtil also remove the Authorization document from the Google Services section. bug:10679818
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
