Keyguard: Distinguish the TextView id of pinEntry

Both KeyguardSimPinView and KeyguardPinView have the same id of pinEntry
for their TextView of the password. When one of them is created in the
mSecurityViewContainer, the other one will get the wrong TextView of the
same id pinEntry.

Change the id pinEntry in KeyguardSimPinView to simPinEntry.

This fixes CYAN-3822,CYAN-3887

CRs-Fixed: 661955

Change-Id: Ia75d1d1f74530e6671d534000f9ce49cb1f814c4

Conflicts:
	packages/Keyguard/res/layout/msim_keyguard_sim_pin_view.xml
SystemUI: Update UserTile from Google 4.4 code

Change-Id: I867167b83897636a3e28d08849e018a3b25caad7

Conflicts:
	packages/SystemUI/src/com/android/systemui/quicksettings/UserTile.java
HOVER: Option to only show up in Fullscreen-Mode [1/2]

Change-Id: I913fce9e54fc0c79f0b3406a4173bb4b55fd6e25
Add UUID (re-)scan support for vold-mounted volume (1/2)

Consider the following scenario:
* Using physical primary only storage cofigurations with the sdcard
  daemon
* On first boot, the UUID is plumbed to the framework via vold, but this
  is only done when a volume is mounted (via the extractMetadata()
  function).
* When the framework crashes/restarts, vold does not need to mount any
  volumes (as the sdcard daemon will still be running), which means
  that the UUID is never plumbed to the framework upon restart.
* MediaProvider will continuously crash with an NPE due to the UUID being
  null.

Workaround the issue by adding "scanuuid" to the "vdc volume" command
list, and trigger a scan when the framework detects that a volume is
mounted but the UUID is null.

Change-Id: I01fceadf85dac97fbf19c41eb865abed714fe0f4