Access ProtectedAppsActivity from SystemUI Recents page if any components are protected.

Change-Id: I873b471babaa802bc4caabbb3c3a23da9555df57
SystemUI: Fix RemoteDisplayTile crash on clean boot

Previously a patch was put up to fix adding/removing tiles due to a race
condition and not checking with the executor was still active at the
time of onPrepare(), but we did not add the check to unPrepare(). This
bug only seems to surface on a clean boot.

Add the same check to unPrepare() to avoid crashing.

Change-Id: I7485ebed41aac94987305b436777bec45beac762
Signed-off-by: Roman Birg <roman@cyngn.com>
frameworks: fix setting default ringtone for multi sim

The defualt value for the ringtone expects a "_" between the setting and
the requested sim subscription. This was not being respected in the
mediascanner when it set the default ringtones, resulting in the setting
value being "ringtone2" instead of "ringtone_2".

Change-Id: I4a9147d579183229cc3300e71194e6f5ab74fbc6
Signed-off-by: Roman Birg <roman@cyngn.com>
Automatic translation import

Change-Id: I7d0558e52d0fe54b2dc5df11201b7bb128407a6a
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