Update roboto font to 4.3

Change-Id: I18aceb350b64085faff93ebf0078e557ce20082f
am: Fix the privacy guard notification

 * The privacy guard notification was not showing everytime. Fix the
   logic and handle it in the right place so it hits both the create and
   resume startup path.

Change-Id: I80c88ffb0fcb4ed3ea64ceb228bb436975278ecc
Frameworks: privacy guard fix possible NPE

If the user flash a data app over recovery on clean flash
(like a lot themed apps or gapps packages are doing)
the user will get into a bootloop because of an NPE
due an unknown state of the user due that
installedUser == null

To fix it
Check if installUser exists if yes then
call the provider settings value for the current
user

PatchSet 2+3: message update
	      fix for real now

Change-Id: Ie5f94a0d0a11ae24fdfdc8372c0433b26793b66e
HALO: halo can save last position now

Change-Id: I5a608b02323ab9fdfa3922a3c9844e75c3a1ab09

fix

Change-Id: I00ced429cfcc90507b8cc14b228a74b8902e67e8
Fix halo button animations
Revert behavior of DateUtils.formatElapsedTime

Change Ib3c1e1aad05827df646aa18645cce19dffb7551f fixes the inability
to display more that 2-digit hour values, but also changes the behavior
of <10 minutes display by zero-padding the minutes. This makes
the Chronometer widget look different, and breaks Holo CTS.

Fix it so that for values under 600 seconds, the minutes don't
get padded

Change-Id: I34eb7f22e728c55bf3313ed1987ac32969cd5ed0
Fix DateUtils.formatElapsedTime, again

Remove extraneous "hours" argument in the <10 minutes case

Change-Id: I5a5913d2e0744f5783f8422cddc30603c7bd703f
LTE toggle: fix supported modes

Change-Id: Iba828b00072dadb4ec0058b7158f2187e1ac1f2d
Signed-off-by: Jonathan Steadman <xxwhitehawk@gmail.com>
LTE Toggle: add missing network mode NT_MODE_LTE_WCDMA

Change-Id: I93db32d4700568d79230350ff67e5dc0227a0c30
Signed-off-by: Jonathan Steadman <xxwhitehawk@gmail.com>
This works - it happens when you can't test your own rom
Revert removing FLAG_ACTIVITY_CLEAR_TOP from intent
Removing that flag from the intent provokes some apps not being able to finish pressing the back key.
This change doesn't affect other opened apps.

Change-Id: I81a47f8e648114d8e2144a3b9854ede299d67871
Send out USER_PRESENT broadcast on screen on if lockscreen is disabled.

This makes sure to turn off the notification LED on screen on when the
lockscreen is disabled by profile or e.g. by lockscreen toggle tile.

Change-Id: I0f6a5f9a021abd2799c22c744ab1180cee027409
Delay closing the notification area after swiping a little closer.

Use the same value as when removing all notifications.

Change-Id: Id11a48bc47487fd7763503dcbc769d9dbf5ad16a
When DPM is updated while lock screen is inhibited, don't
unconditionally enable lock screen.

Change-Id: Iab2af06eb8e41fbcfc6adfbeb5b42a9bbf446fe9
Don't consider input restricted when the lockscreen is disabled by an
app.

Fixes the secure lockscreen occasionally appearing when disabling the
lockscreen via tile.

Change-Id: I078584d0235c1cc958f89ce12ddf3cc1117a5687
Settings: External GPS Support (2/2)

- Ported feature from CM9

Submitted on behalf of a third-party: Cuong Bui

Change-Id: I324269dae1c621b38e2f624e0ce82bf600896ff6
update SystemUI's proguard.flags

Change-Id: I5aa73eddd3fea6cddeddaf94e202d8de870e7df5
 SystemUI: Update Swedish translation

Change-Id: I3062079d6d5f6ea0a6f633253f89bfe798d44952
Allow multiple emulated storages at the same time.

Only do multiuser mapping for primary emulated storage as per google docs.
Allow all non-primary emulated storage to have id other than 0 so that
it could be distinguished from the primary volume.

Change-Id: I7b70b9067fd6211055fb9074710f48107d7b0e8e
Avoid adding FORWARD_LOCK flag to an updated system app

Consider the following case:
1. An app exists in /system/app or /vendor/app. (i.e, it's a system app)
2. If the app would be updated as a forward-lock app by downloading from
   market(google play), then it would be installed in /data/app-private.
3. Moreover, if it would be updated by the whole system image (i.e, FOTA
   or something like that), then the app would be applied a FORWARD_LOCK
   flag.

The app SHOULD NOT have a FORWARD_LCOK flag. Because the resource path
of such app does not refer to the proper resources to access.

Change-Id: I0750f69a93a3115f4201029796b598507de3555f