Installer: Use nanoTime instead of currentTimeMillis

It is possible for the Installer to timeout even though the elapsed
time of 100,000 ms has not elapsed.  This can happen if the system
clock changes while we are running something from the Installer.

The documentation says not to use currentTimeMillis for determining
timeouts and recommends using nanoTime() instead.

Change-Id: I376d5b0fad8eefcdeabbb7ed89ebd3d1d3c96ba0
AccountManagerService: initialize cursors within try/finally block

Change-Id: I8368fa390e94f36fd9c65a34631f320247e5e33e
FWB: Hide carrier in keyguard option (1/2)

Change-Id: I39f8d60ec8087b4754f4a0af98d11294ac496cc8
Signed-off-by: LorDClockaN <davor@losinj.com>

Conflicts:
	core/java/android/provider/Settings.java
lockscreen notifications: inline some trivial methods

...

Change-Id: Ice5996ec1947d547ada7e813aec0135a3daddb72

Conflicts:
	packages/Keyguard/src/com/android/keyguard/NotificationHostView.java
NotificationHostyView : Partial revert vanir's commit
BackupManagerService: Unbreak "adb restore"

The new restoreOneFile() logic aborts the loop whenever the result
isn't an actual successful restore. The problem is that a normal
backup will have plenty of non-restore cycles (APKs that are already
present being the most common), so this breaks regular "adb restore".

Go back to the original logic of completing the loop as long as the tar
file has data (or an explicit abort is generated)

Change-Id: I808cdc1c3b374e29d8438c7051e37c24a7a9d991
BackupMangerService: Pass result code in non-interactive calls

Non-interactive calls are made by Nextbit.  Continue to expose
detailed error codes for all failures.

Also:
- avoid overwriting the non-okay result codes; and
- re-enable version mismatches enforcement.

Change-Id: I54983d8f270285942db20eaff1e6de4229ec781e