GitLab

Change-Id: I2ce25df529f4b281dcc04c8983d78d53e1520f5a

Change-Id: I7e790b4fc436c9aa8f660647973f0795e3ce84e0

* Move platform specific definitions to platform trees
* Declare dependency on hardware/samsung
* Delete unused releasetools
* Add common postrecoveryboot script
* Remove init.qcom.class_core.sh
* Remove init.qcom.class_main.sh
* Remove init.qcom.early_boot.sh
* Remove init.qcom.efs_sync.sh
* Remove init.qcom.post_boot.sh
* Remove init.qcom.ril.sh
* Remove init.qcom.sh
* Remove init.qcom.syspart_fixup.sh
* Remove init.qcom.thermal_conf.sh
* Remove thermal configs, move to platform trees
* Remove init.qcom.usb.sh
* Remove init.qcom.lpm_boot.sh
* Move QCOM_BSP to platform/device repos
* Move mic mute overlay option to qcom-common
* Move reboot to download option to qcom-common
* Move common overlay options to qcom-common
* Move lpm.rc to msm8660-common
* Provide both 8660/8960 and 8974 power saving options for recovery

Change-Id: I4b11b63e36b243a2a23594dc88b4f3e506f01d53

If we aren't installing any of the files that are used as the
destinations of the links then we shouldn't bother installing
the script that creates the links either.

Change-Id: I16495104c0ae44b35361f4b400e6fb9a19d6f3b1

Change-Id: Id050873cea4db0488846f3c1f746887339a2c970

Change-Id: I7dbe1a604310d80a58a641ce7ebb086ac5644186

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

Change-Id: I21f9c3d44fb5fe22e142adc308ee890fcb2d2030

This reverts commit ad66f016.

Change-Id: I4ae9ba465f61fa650c6dc722dfc44932dee84eac

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

Change-Id: Iadf66a00a742ab37b68195c8bb048e1d4457f523

Change-Id: I115a7b6294b5c07b97a646b1cc71e8890eee5701

Change-Id: I5f07f87d3f33408db400666e2df1aea601e5d3df

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

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

Change-Id: Id49c22297f4a651ebbeb83a15dcc52a7e769419d

Change-Id: I6705b9f280ea9c8099b72ad7addb000fc1e4db2f

Change-Id: Ifd3930a68625497ceb660a3aeba1fab43cbc26eb

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

Change-Id: Ibb1d8b695c10d32bdd314fa355c197e8248c4b1a

Change-Id: I51b0efa1f399b2679253f100dfce84f3a774e7e3

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

Change-Id: I682343a057c6c784523d5c298425474f8c7923bb

Change-Id: I95773d0442cc64027d52c037c86675c6c012b2e4

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

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

Change-Id: I4bba27fce572e4e0d5fd4b68cb79b4f73ab2c629

 * The default value is too fast and causes jitter

Change-Id: Ic25a07325f34fc18cd6b5e31494de045abe13b46

Change-Id: I9bd3aa447d2eab9f85503e9c522d2b1a1a648033

 * Non-pro 8974 is not equipped for this.

Change-Id: I6d2e74549e2a0cc40174b3ac471d3d67b1b284cb

 * Enable devfreq governor

Change-Id: I4e211a09d3e33df8254a94c02b0ae52539bb2883

This reverts commit 0c822365.

Change-Id: I34ac3d1b2039818aa43244cf3aed487e5fe5f250

 * Don't copy all this thermald junk
 * Add media_codecs

Change-Id: I76fb67a5b45e0b24e12e56b438299c5dc529c938

Change-Id: I679dd5a84f02aa5f9bb10b1bd95fb340609f6e6a

Due to the sub-standard chips used on some SoC revs, some apexqtmo
devices have a need for higher levels of thermal throttling. Break the
MSM8260a out from the rest of the MSM8960's by platformid, and assign
more aggressive thermal throttling if an affected cpu is detected.

Change-Id: I5c34915e64e83b204448190bd365c47d0ea5ebf9

For smoother scaling on interactive governor.

Change-Id: I86bc9f9dca02889303a37cff17e583ac8e5b8477

* fixup the path for hlte's msm8974 powersettings
Change-Id: I0802cc122b606b08f58731febd8bf050d22f4c59

Change-Id: I745c07fe55316d305fccad7f26c94f1db63b0408