Telephony: Add support for Sprint TW "System select" choices.

Also fixes the no-roaming bug due to the lack of the CDMA_RM_DOMESTIC
option, which forces CDMA_RM_HOME when opening the "Mobile networks"
settings screen.

From CM 10.2: I32129efe217e5f79372aab49e45c668393c3dc2a.

Change-Id: If3de040144e96253ba869cfbcfe8902597ce92b8
Mms: Fix multipart SMS on Sprint.

Use MmsConfig defaults for enableMultipartSMS (true) and maxMessageTextSize
(2000).

Change-Id: Id49c22297f4a651ebbeb83a15dcc52a7e769419d
Merge "Telephony: Add support for Sprint TW "System select" choices." into cm-11.0
Fix parameters for interactive governor

Two commits to the kernel broke the interactive governor. They resulted
in having both cores being stuck online and at a minimum frequency of
1026 MHz at all times while the screen was turned on.

The interactive governor was updated in two commits;
https://github.com/TeamApexQ/android_kernel_samsung_d2/commit/e12a8e83d922eb3800dd459dd3c3068bde8a04c2
https://github.com/TeamApexQ/android_kernel_samsung_d2/commit/c42353f0e809472b0cb2dd5831d61340debbe559

Effectively, what they do, is test if any online core's load exceeds
up_threshold_any_cpu_load, and if any (could be other) core's frequency
exceeds up_threshold_any_cpu_freq. If both of these conditions are true,
it forces ALL CPU cores up to sync_freq, which in our case was set to
960 MHz, which does not exist in our frequency tables. It would pick the
next frequency up, which was 1026 MHz. We also update the sync_freq to
reflect this.
Conflicts:
	rootdir/etc/init.qcom.post_boot.sh

Change-Id: If31ec8dc410c5051ae545b0e7e045afa5e137649
qcom-common: Enable use of FFMPEG codecs for extended formats

Change-Id: I5f07f87d3f33408db400666e2df1aea601e5d3df
qcom-common: Setup mk files to honor the 8974 devices.

Change-Id: I115a7b6294b5c07b97a646b1cc71e8890eee5701
Add ffmpeg codecs to 8974

Change-Id: Iadf66a00a742ab37b68195c8bb048e1d4457f523
lpm.rc init: Fix charger mode and update pm paths.

lpm.rc is only processed by init when the device boots into charger
mode. In charger mode, init does not trigger the 'early-boot' and 'boot'
actions at all. It runs the 'charger' action instead.

Before this patch even core services were not started in charger mode,
as class_start was part of the non-existing 'boot' action.

Insert usecases for different platforms and add pm paths for msm8974
to init.qcom.lpm_boot.sh

Change-Id: I2d1e794a5a288abca33a59a00ae49ef02d111950
Revert "lpm.rc init: Fix charger mode and update pm paths."

This reverts commit ad66f016f0ca31b049a777dca9e9e5b66afbc5b5.

Change-Id: I4ae9ba465f61fa650c6dc722dfc44932dee84eac
qcom-common: Remove duplicate overlay

* This is a duplicate of the config in vendor/cm

Change-Id: I21f9c3d44fb5fe22e142adc308ee890fcb2d2030
qcom-common: remove cpufreq permissions now set by uevent

Change-Id: I7dbe1a604310d80a58a641ce7ebb086ac5644186
qcom-common: Remove mpeg4/h263/h264 ffmpeg entries

Change-Id: Id050873cea4db0488846f3c1f746887339a2c970
Merge branch 'cm-11.0' of https://github.com/CyanogenMod/android_device_samsung_qcom-common into kitkat

Conflicts:
	rootdir/etc/init.qcom.post_boot.sh