Fix OOBE crash/DoS after receiving 0-byte WAP push.

Add a try/catch block around the code in WapPushOverSms.dispatchWapPdu(),
so we don't get into a reboot trap on receiving weirdly formed messages.
Only catch ArrayIndexOutOfBoundsException, which is difficult to
prevent inside dispatchWapPdu() for 0-byte PDUs or other unusual
contents. The caller should probably catch any unhandled exceptions of other types and log them with stack traces.

Bug: 11967705
Change-Id: Iabfec68d2564dd438d45c80cdba877bf19fa0397
UICC : delete adn cache after SIM REFRESH RESET

delete ADN cache after SIM REFRESH RESET for updating the SIM contacts

Bug: 12751374
Change-Id: I2d707dca3e76271f203b1b86212947e3287a8ed1
Fix isSameNamedOperatorConsideredRoaming [DO NOT MERGE]

Does a loop checking data based on your current network,
but exits out based on the result of the first check rather
than doing the rest of the checks.

Bug: 11408729
Bug: 12121959
Change-Id: I37f98682702ec19467f374d64a23e15fb87e9697
Switch from SIM to carrier info for wifi country

Now will also inform when no known country too.

bug:11062898
Change-Id: I4a938119c1c06898b39b3bcc6124031d2f66dd71
Telephony: Add + for international number for MT SMS

Add + if international number is not having + at starting.

Bug: 10951615
Bug: 11599528
Change-Id: I0000b0685181f17ba6b5b0eaaba60a77971e7908
Handle provisioning APN by turning off/on data.

This is a start and two tests succeed:

Tested expired AT&T SIM and waiting 15min for alarm to fire.
Tested a provisioned Verizon SIM and works normally.

I've NOT tested AT&T where I've properly completed the provisioning.
I've NOT tested T-Mobile SIM either provisioned or not-provisioned.
I've NOT tested provisioning over WiFi.
I've NOT tested that WiFi <-> Mobile works
I've NOT tested voice calls, SMS, MMS
...

The current bug is below, but it is poorly named either it should be
renamed or a new bug created.

Bug: 13190133
Change-Id: I0a09f642614cd27a8655e9dae764b8999ce485b8
Merge tag 'android-4.4.3_r1.1' into kitkat

Android 4.4.3 release 1.1
Don't write blank baseband version

* There's no point in setting the baseband version if the returned value
  is blank anyway.

Change-Id: Ica9973a8b790c0de6afa10bc131257a3a03f18a0
Fix order of '+' in call forwarding return result in RTL locales

The '+' is presented at the end of the phone number
instead of in the front.
Phone numbers should be presented left-to-right even
for right-to-left oriented languages (e.g. Hebrew),
hence the '+' should be placed accordingly.

Change-Id: I07d89078de4d81609e08099f93fc929a81ec172b
Merge pull request #1 from LiquidSmooth/kitkat

merge latest liquid changes