Themes: Only kill launchers if overlays or icons changed

There is no need to kill the launcher for every coponent changed.
The only ones that really concern us in regards to killing launchers
are MODIFIES_OVERLAYS and MODIFIES_ICONS

Change-Id: I840b8e2ecd4b52a33f352809c5d3d2c7e92ce85e
Add ANT to the list of toggleable airplane mode radios

Adding ANT to the list of toggleable radios allows ANT to behave in the same way as Wifi or
Bluetooth in regards to operation during airplane mode: when airplane mode is turned on, ANT is
disabled, but can be re-enabled by the user at any time.

Change-Id: Idb9e9499fd7a7fccee8c459779ec86bf24e1373e
Clean up quick settings tile code.

- Fix up coding style
- Add copyright headers
- Fix some multi-user bugs
- Streamline code

Change-Id: I0a118f7154bdd8cfdacdd7fdf8b76241010179de
Use actual storage type of sdcard/usb (1/2).

Change-Id: Icaf0d246ab3bdd0614c8bb7a22f8b2b95cbe9c7e
TODO: Provide drawable for usb storage (someone please).
core: use 'normal' value for notification led off

Users can set this value to 250, 500, 1000, 2500 or 5000ms only,
but it's 2000ms by default.

With this patch, 'Normal' string is shown instead of 'By default'
and pulse speed goes to 1 sec.

Change-Id: Idb18ac345bd9eb1a5b795776faa60e2fb5bc258b
Fix API check derpage

Change-Id: Ib2086febae4c4f3c2caec77d8a78dcb1d0dfc978
watermark: Place watermark in the bottom-right when both deltax and deltaty are 0

The default behavior is to replicate the watermark all over the screen but this can
be too intrusive. The repetition is controlled by deltax and deltay and if they are
both 0 the watermark will actually be drawn off-screen and thus not shown.

We take advantage of this to add a special behavior when they are both 0 that simply
places them in the bottom right. This patch doesn't take UI elements into account and
may actually overlay soft-buttons and other chrome.

Change-Id: I4cff1326b8aaecdbc471eaf48e95bc2865181366
ProximitySensor: check for correct MaxRange value

Use TYPICAL_PROXIMITY_THRESHOLD for devices that returns incorrect mProximitySensor.getMaximumRange() value;

Presto's proximity sensor returns values: 0.0f(near) or 5.0f(far).
mProximitySensor.getMaximumRange() must return proximity sensor's availible range, but it always return 0, so mProximityThreshold is also 0.

So boolean positive = distance >= 0.0f && distance < mProximityThreshold;  positive will never be
true.
The cause of this problem is proprietary sensor.msm8660.so, it must set proper Range and Resolution for proximity sensor.

Change-Id: I0cf81fd20f210115cbd6db10c0070b12f1c57336