In favor of using boot control HAL under recovery.
Bug: 34254109
Test: TreeHugger
This is a combination of 2 commits.
This is the 1st commit message:
Revert^2 "Build libgptutils with Android.bp.""
This reverts commit 215189f0b9ff44d28c2b4ace0abb26854b201271.
The previous landing broke checkbuild targets due to namespace issue. As
libgptutils.msm8998 was exposed to global namespace (previously guarded
via conditionals in Android.mk), but had a missing dependency on
nonexposed msm8998 kernel headers.
The relanding adds a Soong namespace of hardware/qcom/msm8998, to ensure
modules only getting built as needed.
Bug: 34254109
Test: Sideload on taimen.
Test: `m -j checkbuild` with aosp_x86-eng
Change-Id: I4a7c4cedcf58c7735172d989912e4f7afad1eaed
Merged-In: I4a7c4cedcf58c7735172d989912e4f7afad1eaed
(cherry picked from commit e74c7611d2cbea03ec8ec1559787a7a57b2bf767)
This is the commit message #2:
Revert^2 "Deprecate PRODUCT_STATIC_BOOT_CONTROL_HAL.""
This reverts commit d83c2cc22b3f037e94cd4ad7e19f5985da13a8b8.
The previous landing broke checkbuild targets due to namespace issue.
See the commit message for hardware/qcom/msm8998 change.
Bug: 34254109
Test: Build and boot taimen on device to home screen.
Test: Sideload on taimen.
Change-Id: I775026345eb5fc0ec580ba4ca0282835106a1d35
Merged-In: I775026345eb5fc0ec580ba4ca0282835106a1d35
(cherry picked from commit 4fa8e490208bef42faccf204381dc35ad1cfed46)
Window animations now have rounded corners, meaning that
the shader that we use is more expensive than it used to be.
Because of this, we need to adjust the SF offsets, to make sure
that we'll have enough time to finish the GPU composition without
dropping frames.
These offsets as similar to blueline's, adjusted slightly because
we were getting false "frame missed" signals if composition
starts too early.
Change-Id: I8173e12b006bc1cab6b4cb0b3a5db9f9b3489819
All servicemanagers are started in rootdir/init.rc's `on init`
trigger, so there's no need to start them manually in device specific
rc files.
Test: boot
Change-Id: Ibdea8d5289322aae49af50e325beb793936ea525
* This was mildly acceptable in August as a way of chasing the CTS
match dragon, but our platform is September now and this just leads
to confusion. We can try to find "working" fingerprint sometime
else.
Change-Id: I99b304a958c79e8e7a7603fbbc2e8d43ed37187e
mata has a notch, but this was never set, so users were still able to
do things like enabling the network traffic monitor or setting the clock
position to center, both of which would not be fully visible due to the
notch.
Change-Id: I2aaa0c06b23b40aac120c325ce15fb0992463520
With PQ1A.190105.045, Essential tweaked the volume curve for music
streams playing on the phone speaker. Before, the perceived loudness
would increase far too quickly as the user increased the volume to 50%.
Now, the perceived loudness increases in a more smooth and expected way.
Change-Id: Ie67b8ea3ba28b5b2fbe77760f67fc0d46b1f9b7e
* Note: This includes a horri-bad setting of platform security level
in order to pass a CTS profile match.
Change-Id: I957c27f2300d48b66769dec1727c6636feb460ac
* Also allow vendor_init to set them.
* Resolves: init: Unable to set property 'persist.radio.VT_CAM_INTERFACE' to '2' in property file '/vendor/build.prop': SELinux permission check failed
Change-Id: Ib5c667be91dadeaadae53a819faa281df561afcb
/sys/class/graphics/fb3
During the folding of init.mata.hdmi.sh into init.mata.rc, a few
ownership/permission changes were accidentally excluded, resulting in DP
Alt Mode breaking.
Add these changes back in to fix DP Alt Mode.
Change-Id: I48e265ab7b2f1ecd61a1d5c88e085e36dad34df1
* Starting with PQ1A.190105.077, we need to make sure to use the
aarch64-linux-android- toolchain due to kernel GCC_TOOLCHAIN_DIR
logic updates
Change-Id: Ib75c5f06b27ab8979d28a3446e36d73e29846769
* Note: vendor security patch level not updated as Essential, yet
again, did not set one in PQ1A.190105.077
Change-Id: I81221db992bda78222cab52521d5ca8f79ca65c2
