Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Bruno Martins authored 6 years ago and Dhina17 committed 4 years ago

 * The framework manifest must now be split per device, since not
   every interface is supported. In this case, only DisplayModes
   and PictureAdjustment are supported.

Change-Id: I4e42e2b20347f4766fdd5ea3e2e5890654ce7e88
Signed-off-by: Atman <masteratman@gmail.com>
Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Bruno Martins authored 6 years ago and Dhina17 committed 4 years ago

 * Mentioning CodeAurora, AtFwd hal is implemented as an Android service
   and it starts from the system partition, that is, it's not a traditional
   vendor hal and hence it should be declared in the framework manifest.

Change-Id: I0aa37ae9b3baacf42dcfa54419f62fc528b00bcb
Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

GuaiYiHu authored 5 years ago and Dhina17 committed 4 years ago

[Atman's edit: Build a 8Mb DTBO parition]

Change-Id: Iad3fab45e2d676036a4073b1a2bce55889cc62c3
Signed-off-by: Atman <masteratman@gmail.com>
Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Demon Singur authored 6 years ago and Dhina17 committed 4 years ago

Change-Id: If8e2211e643bdb0ff67fb248e7fe33b78077a06e

Signed-off-by: Demon Singur <demonsingur@gmail.com>
Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Source built KeyMaster and Gatekeeper HALs crashed..
So,Good way that is move to Blobs

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

GuaiYiHu authored 5 years ago and Dhina17 committed 4 years ago

Change-Id: I58e2a50bd1e74ea11e523744ff8df285212b4d4d

Bruno Martins authored 5 years ago and Dhina17 committed 4 years ago

 * VNDK runtime isolation is kept disabled for now because that's also how Xiaomi is shipping P on their devices.

Change-Id: I43140442ab33f3e9633bb4f347e2bee9be97b447

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

-From onc-user-9-PKQ1.181021.001-V10.3.3.0.PFFINXM-release-keys

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

Signed-off-by: Dhina17 <dhinalogu@gmail.com>

* 512M disk is just too small for us and gets overfilled pretty quickly.

This reverts commit f5c43922.

Change-Id: I4bddc3fb35f81f2dce441cb269417c60c2b03956

* Our current HEAD of bootable/recovery seems to hate
  sdcards and I can't figure out how to fix it as gdb
  doesn't want to cooperate with me.
* By adding a separate recovery fstab that doesn't have
  any voldmanaged devices we can avoid crashing entire
  recovery and getting anyone stuck in it whenever they
  try to boot it.

Change-Id: Ie5d2dfedc5627f239c9bdf95ee32a96c54aa9934

This reverts commit 7e079391.

Change-Id: Idd3784f87123368435b1186d449eaae4da99928f

This reverts commit cec9091c.

Change-Id: Id44e00a5e188bc1fa072623d6010552aca8174ae

* No matter how hard QC tried to improve these features, they still suffer
  from stability issues, mainly due to the unpredictable nature of vmpressure
  they rely on.

Change-Id: Icd14c79298a3c268abffa06ed17a79dececf423a

* There's no reason in limiting this to 4 cores on msm8953.

Change-Id: I7b67c3853f75a22facb169a8e954bff37164e0d4

This partially reverts commit 77cc799c.

mido's modem is too old to be able to use qcrild in stable condition.
Keep some changes around.

Signed-off-by: Albert I <krascgq@outlook.co.id>
Change-Id: Ief5a0c4a8ad3d71195df47b8778478165fb1581f

Change-Id: I364001efbf02e8780ef7c3512fbb3452a6c3f672

Change-Id: I470b1c2ff430f12bdbfbd69341c7cfdfe972b7dd

* Due to the way newer TWRP versions are behaving, our relatively small
  persist partition gets overfilled with recovery logs very quickly.
* Let's just remove the recovery cache from persist on every boot to be sure
  that we always have enough space for anything that writes to persist.

Change-Id: Id1502dfb5e504504601a21efb7812b84a7155e58

* It should be persist.vendor.usb.config.extra, not persist.vendor.sys.usb.config.extra

Change-Id: Icc5531c5563f1975314be38f5f7567e1c0f5eb8d

* Historically, triple buffering was used to workaround missed VSYNC
  in GPU composition usecases on devices with high resolution panels.
  As a downside, an additional frame buffer increased input latency.
  Nowadays, most GPUs are fast enough to fit the VSYNC period, rendering
  triple framebuffers useless.
* Custom VSYNC offsets are intended to reduce input latency at cost of
  increased sync error counts. Our values were never calculated properly
  and were just taken from another device instead. That led to jank in
  some usecases.

Change-Id: I57ac4362ca28a9c128cc45c3f6e3734a24654955

* For some reason, booting with headphones plugged in results
  in a broken speaker output if FDE secure boot is enabled.
* Restarting audio HAL after decryption seems to resolve the issue.

Change-Id: Ie14b89841bf811f0fb09edb0a04fd28aafecde87