* 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
Enable backpressure for client composition to avoid jank due to
HWC queue stuffing.
Test: 1. Open Camera
2. Swipe horizontally to go back to previous app.
Bug: 138083790
Change-Id: I3d26aa470c1660b23bd97133f39858f92638aca8
This is a surfaceflinger debugging feature that we don't care about, so
disable it to reduce overhead.
Change-Id: Iaf6417d101f1a79bfadf85f779a614ed0460c56d
Set debug.sf.latch_unsignaled=1 is used to allow surfaceflinger to
latch unsignal buffers that can give more time for buffer to render.
But if the buffer takes longer time to finish, it will block whole
display pipeline result to jank.
Bug: 157964883
Test: scrolling, launch
Change-Id: I56c3e05921de5fc9569bf3f93fde03022a64b6a4
getPreferenceScreen().findPreference() does not find preferences
within another PreferenceCategory. That breaks hidin the proximity
category on devices which do not support it.
Change-Id: Ic7d840df7a71905b5b697954a279de51d8d0408a
Patched to remove com.qti.permission.BIND_QTI_IMS_SERVICE and
Landroid/telephony/TelephonyBaseUtilsStub;->isMiuiRom()
Full patch: https://paste.myself5.de/zitiketuto.diff
Change-Id: I1ecff29d7089bffa50d41acb6b55c6d8e36d1d9c
Updating kernel target level to Android R
checkvintf Error
checkvintf E : files are incompatible:
Runtime info and framework compatibility matrix are
incompatible: Kernel FCM version is not specified, but kernel version
4.19.95 is found. Fix by specifying kernel FCM version in device
checkvintf E : manifest. For example, for a *-r kernel:
checkvintf E : <kernel target-level="5"/>
checkvintf E : INCOMPATIBLE
Bug: 148823278
Change-Id: Ia30013045b0fe15abc859dda503aed790aaeeb76
They live within the bluetooth apex now.
Change-Id: I01ef1d665ce05b7ce5b1ee03129ccf3ce6058634
Signed-off-by: Alexander Martinz <amartinz@shiftphones.com>
* It turns out moving this to class main doesn't work as well
as some had thought it would, so restore the previous logic
to use class hal, and restart if the backend isn't up yet
Change-Id: Ib8b417d89108dcf80d0d159e8d84e5327944b2a1
