Default to false if the property is not set.
Device init scripts will need to be adapted to restart
loc_launcher service when property change is detected.
Change-Id: Icbda789cd2a9a3391f437af2c07fc5127f2f09ab
This fixes enum-conversion warning due to implicit type enum casting
between linked_list and msg_q which happens only for status -6.
Change-Id: I27ba74c4d840b7ba0cb1017d69a30fc25b80d6b9
-Wreorder-ctor is a compile-time, Clang-only flag which is enabled by
default since Clang 12, which will warn whenever a specified field will
be initialized right after field specified below it. However, since it
doesn't sweep through all fields, compiler may miss some of them.
This order has been checked thoroughly through many trial and errors to
ensure that no such warns will be triggered anymore.
Change-Id: Id24cbb7277dc8d6c02767f8f365818ab6c017683
AOSP defaults to v1 on devices shipped with Q or earlier,
explicitly enable v2 for these devices to use 16-byte padding
e575f4ed96/libfscrypt/fscrypt.cpp (L205)
Change-Id: I20e5f31007a2c01bc993c09e644205bf23ebd8ae
This fixes GSI image overriding the default value
Bug: 153852350
Test: Manually verified after flashing the GSI image
Change-Id: I78b415862c420c23121ec03d6953814cd628ea9a
This reverts commit a13246a7fc.
This causes dac_override denials, set no_sehash_xattr on persist
in fstab instead to fix the issue.
Change-Id: I75f824d5b2beca5f7c3835045a7f568736e148f0
* Manually setting the doze status before entering the low-power mode
makes the doze mode not to be set correctly on sweet.
* The doze status is automatically set when entering the low-power mode
This reverts commit 10f101e143.
Change-Id: I4dfee2ffb351b9bc426268e437a26f9eaefec319
* These were renamed to vendor.camera.* properties whose definition
already exists in our current policy
Change-Id: I4392a7880d36b6b6d6aff4a6d9b43c1fc2bab950
* We aren't using QCOM's perfd but our blobs still check for this.
* To avoid unnecessary errors, let's just add it back.
Change-Id: Icc44b330f21a658cfa8ded691a6628d8f62c3649
* proprietary perfd blobs can finally be nuked without breaking goodix
* we could even map the functions to use libperfmgr powerhints in the future
Change-Id: I124652f3041761966a3e3bd97c757fecc39cc5fb
Kernels >4.7 will create a comp stream for each online CPU
and ignore /sys/block/max_compression_streams. This has been
backported to many 4.4 kernels as well.
Any device running a kernel with the upstream commit can safely remove
the parameter.
Upstream commit: 43209ea2d1
Change-Id: Ibb29b54a31f0fb5bd941d7709d15d571dd77ebf5
The default camera app can be *huge* in some cases, e.g. when the app in
question is Google Camera. The system will only pin up to the first 80
MiB of the APK file, as well as the first 80 MiB of its odex. There are
several problems with this:
- We could easily end up with 160 MiB of camera app files pinned,
which is a tall order with the 8 GiB of usable RAM that we have
- The data that gets pinned may not even be the most critical data for
launching the camera
Let's disable pinning of the camera app to save RAM.
Change-Id: I745e39b6ff212dfaf9213517d2a2be8ff7384e24
