overlay: overlay the overlay with moar overlays

We need to overlay our own verizon eri.xml's these break other devices (namely toro)
by causing a roaming icon. Without them, we get "Roaming Indicator Off" instead of
"Verizon Wireless". Which I'm fine with, but most end users stab me over it.

Need to switch to using PRODUCT_PACKAGES_OVERLAY instead of DEVICE_PACKAGES_OVERLAY
or it won't take precedence.

Change-Id: Ieba26464ae1872644de213544bd970a9cdd46efc
overlay: use DEVICE_PACKAGE_OVERLAYS

This is the old behavior. It was included in a commit
that overrode vendor/cm which we don't need to do anymore.

Change-Id: I64ebb5b9e60124359f875c291429839d7c8d7282
qcom-common: allow multiple hardware tunables includes

Change-Id: I95773d0442cc64027d52c037c86675c6c012b2e4
Merge "overlay: use DEVICE_PACKAGE_OVERLAYS" into cm-11.0
overlay: add sprint eri.xml for mcc310/mnc120

Change-Id: I682343a057c6c784523d5c298425474f8c7923bb
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
qcom-common: Don't use CM PowerHAL for all targets

Change-Id: I51b0efa1f399b2679253f100dfce84f3a774e7e3
qcom-common: TARGET_POWERHAL_VARIANT = cm

 * Use this for all Samsungs by default. Individual devices can
   override if they choose.

Change-Id: Ibb1d8b695c10d32bdd314fa355c197e8248c4b1a
qcom-common: proper eri overlay

Change-Id: Ifd3930a68625497ceb660a3aeba1fab43cbc26eb
overlay: add r970-specific eri overlays

Change-Id: I6705b9f280ea9c8099b72ad7addb000fc1e4db2f
Merge "overlay: add r970-specific eri overlays" into cm-11.0
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