Unlock KeyStore on successfull Quick Unlock

KeyStore is normally unlocked after a successful Password Unlock, but it is not covered in the case of using the Quick Unlock option. Fixed to unlock KeyStore on successful Quick Unlock.

Change-Id: I7e49292286eacc681c633290cf5262e5c37403f4
adjust navbar logic

Change-Id: I4ce315ca7138f731ae072fc9a99a3ca6c968b739
Signed-off-by: Roman Birg <romanbirg@gmail.com>
Merge "Unlock KeyStore on successfull Quick Unlock" into jb
 frameworks: update Swedish translation

Change-Id: I3e3613772e1a3ebaf54d50af2cb4a77bbd5a021b
Merge "adjust navbar logic" into jb
base: External BT GPS

Change-Id: I869320d42f40e8b762b8b27702ea4495403f8fc5
Credit: Cuong <cuongbui@gmail.com>
Fix up public API breakage

Change-Id: I0be602584ca0ea62e7bdb9d4c6bfbf67f97b6d90
ProcessStats: Fix another crasher

Prevent occurences of:

java.util.NoSuchElementException
	at java.util.StringTokenizer.nextToken(StringTokenizer.java:208)
	at com.android.internal.os.ProcessStats.getCpuSpeedTimes(ProcessStats.java:574)
	at com.android.internal.os.ProcessStats.getLastCpuSpeedTimes(ProcessStats.java:546)
	at com.android.server.am.ActivityManagerService.updateCpuStatsNow(ActivityManagerService.java:1676)
	at com.android.server.am.ActivityManagerService.batteryNeedsCpuUpdate(ActivityManagerService.java:1728)
	at com.android.internal.os.BatteryStatsImpl$MyHandler.handleMessage(BatteryStatsImpl.java:129)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:137)
	at com.android.server.am.ActivityManagerService$AThread.run(ActivityManagerService.java:1431)

Change-Id: I66f30739455dd726b708467f814f53c445f327b2
SystemUI: Battery Icon updates for tablets

updated the XMLs needed for tablets
Signed-off-by: Adam Fisch <adammfisch@gmail.com>
telephony: Add Sony RIL for Qualcomm basebands

Change-Id: If50e220e54f0539cd84a472580507c227683152b
HTCQualcommRIL: add HTC hack to stop displaying SIM unlock screen

Change-Id: I7d3cc0c38cfee33a31a22d947cf3e09cd9bcb134
telephony: SemcRIL: updated for jellybean and cleanup

Change-Id: I71d3f5288fb74486f0f77596f586104966345499
Roboto: Fix for Unicode Character U+1EE1

LATIN SMALL LETTER O WITH HORN AND TILDE (U+1EE1) looked like
LATIN SMALL LETTER O WITH TILDE (U+00F5)

Change-Id: Ic9fa3432bcd6c36eadd82f2f48d1166d0fcc8b80
SamsungRIL: Fix data connection after pin unlock

If the user has PIN-locked his phone, data connectivity will not
work because the RIL sends APPSTATE_UNKNOWN and does not update
it to APPSTATE_READY. We inject the state update if there's a
signal change.

Change-Id: Id64e95ebcadd1d7ff181f8d9c2ee4f18e6ae48f1
Smdk4210RIL: switch video and voicePrivacy, readability

Change-Id: I168abd4c11c576681d8d4774dfb751da8d19a49c
fix NAT detection in SipService

The NAT detection in SipService just checks if the client IP is a
private address. In this case keep alive is enforced. But if you
use a server which also has a private address, keep alive should not
be enabled to save battery.
This patch modifies the NAT detection to also check the server IP.
If both are private, NAT is not detected.

Change-Id: If4baaf1866253ca6c432e5cc4b07e3ebd9de6ba1
SamsungCDMAQualcommRIL: Switch to CDMA subscription.

	- Utilize CDMA stack, allows shared RIL to handle subscriptions.
	- Fixes ICCID registering in About Phone.
	- Roaming works.
	- Everything, theoretically, works compared to gsm stack.

Change-Id: Ia96b9381df9358bb4a91710ba3092e64ced84025
frameworks/base: Handle Out of Memory Exception when creating video thumbnails.

Adds code to handle an out of memory exception when generating the thumbnail
from a recently recorded video clip.

Change-Id: Ifcbe007272ffef85744fca1414ea5eacccd0154c
CRs-Fixed: 277571
Signed-off-by: Shalaj Jain <shalajj@codeaurora.org>
SystemUI: Fix data activity overlay not being removed when data is disabled

If mobile data connection is disabled while there is active data
activity, the data activity overlay will not be removed and will
be stuck there. This patch fixes that.

Change-Id: I4cc1a14bb2e2d85687752657608e5989adfe9af1
PowerManagerService: fix getAutoBrightnessValue for btn/kbd

getAutoBrightnessValue calculations are correct only for LCD
backlight brightness values increasing with higher light values.
Skip the calculation for the reversed button/keyboard backlight
arrays, where the backlight brightness decreases with increasing
light values.

Change-Id: Ib72b8325fe2b0f83780e91dc94eea2e38061224b