Fix issue #11256132: Add density bucket for all real numbers between 0 and ∞...

Well, how about 400.  400 is a real number.

Change-Id: I29ac61b7d629d582c7b68367365a7f81fcf679a2
Trace: add ALOGVs for easier debugging

Bug: 11071158
Change-Id: I08764db1742267dad88fd61f22c21df9b70f879e
Merge "Fix issue #11256132: Add density bucket for all real numbers between 0 and ∞..." into klp-dev
Merge "Plumb through physical device UUID and label." into klp-dev
Merge "Include external storage devices in DocumentsUI." into klp-dev
Merge "Make dump messages asynchronous." into klp-dev
Merge "Layoutlib: Add DateIntervalFormat_Delegate required by CalendarView" into klp-dev
Merge "Fix layoutlib for KK" into klp-dev
Merge "Log view root, input and looper state in bug reports." into klp-dev
Fix issues catching up to touch events after a short pause.

When the app spends more than half a second responding to a touch
event, the input dispatch eventually decides to stop sending it
events until it catches up.  (This is when the ANR clock starts.)
However, due to a bug in the timing logic, if the app eventually
does respond again we would resume delivery but only send one
event at a time until the queue was completely drained again.
This meant it could take a long time to catch up and process all
events.

The problem is that we were comparing the current time with the
waiting event time.  So when events became older than half a second,
we would simply stop streaming and end up serialized.

This change fixes the timing logic such that the streaming timeout
is based on the delivery time of the waiting event rather than
the event time itself.  Now we only stop streaming when it has
been over half a second since the waiting event was delivered
so we resume streaming immediately as soon as some waiting
events are handled.

Bug: 11278743
Change-Id: Ic8c68ee372a07f7caa4168eefcabf9b8a8ad5d87
Layoutlib Create: Remove references to java package class Objects.

Remove references to Java 7 class java.util.Objects and replace it with
a new class that can be loaded on Java 6.

Change-Id: Ibbd9b20b8bc89e247f1d0c48d743d06d1a4f0704
Relayout the immersive cling in the correct thread.

Bug: 11266364
Change-Id: Ia629262ff0c362a5a45b6c5822be080cefcb8c56
DO NOT MERGE Fix null pointer exception when updating rotation tile. (Bug 11111473)

This occurs when switching users on devices that
don't have a rotation lock quick settings tile.

Change-Id: I738ca15ca754be90cec7eaf3a8eda3e38ed96b33
(cherry picked from commit e8f50a1400d288e6fd7c20ec7947270e204ee57d)
Fix bug #11256076 Spinner text is too close from the opening triangle in RTL Locales

Background Drawable padding was not taken into account in RTL Locales

- make sure the Drawables are resolved before resolving padding
- during padding resolution take care about background padding

Change-Id: Ib0c722adf5341ab4fa2182a0d0ac2ca639e85cfc
Don't run the async query if being rendered in EditMode.

Skips the QueryHandler if the QuickContactBadge widget is being rendered
in edit mode.

Bug: 11288332
Change-Id: I04b115292f61afc7f515787fa4a396bc6ea56a16
Merge "Layoutlib Create: Remove references to java package class Objects." into klp-dev
Do not show immersive mode help in touch exploration mode.

Bug: 11277364
Change-Id: Ifafcbff38e34c0ef08d9a466d93ce591369183a3
Hide the print dialog if the printing activity is destroyed.

1. For an app to print it creates a PrintDocumentAdapter implementation
   which is passed to the print dialog activity. If the activity that
   created the adapter is destroyed then the adapter, which may rely on
   the activity state, may be in an invalid state. For example, an app
   creates an adapter and calls print resuting in the app activity and
   the print dialog activity being stacked. Now the user rotates the
   device which triggers the recreating of the activity stack (assume the
   app does not handle rotation). The recreated print dialog activity
   receives the intent that originally created it with containing the
   adapter that was constructed in the context of the old, now destroyed,
   app activity instance.

   To handle this we are limiting an app to be able to print only from
   and activity and when this activity is destroyed we mark the adapter
   as invalid which will result in hiding the print dialog activity. Note
   that if the app process is killed we already handle this in the print
   dialog activiy by registering a death recipient on the adapter binder.

2. In the PrintManager.PrintDocumentAdapterDelegate some of the state is
   accessed only on the main thread and some from miltiple threads. The
   code was trying to avoid locking for state that is not accessed by
   multiple threads but this is error prone and the benefit does not
   justify the complexity and added fragility. Now grabbing a lock all
   the time.

3. The PrintJobConfigActivity waits for it to bind to the print spooler
   service before instantiating its print controller and editor. However,
   these can be accessed by invoking some of the activity cycle callbacks.
   This change is adding null checks for the case where the activity
   callbacks are called before the binding to the spooler is completed.

bug:11242661

Change-Id: Id906b3170e4f0a0553772dfa62686f06fdca0eaf
Merge "Clear the caller identity when dumping print system state." into klp-dev
Merge "Printer list items have wrong width." into klp-dev