| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
These are critical for display performance and should not be balanced
in order to improve latency and responsiveness.
Change-Id: I0248e26a7154c689c0d3f11dabe14a1b149353f9
Signed-off-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
|
| |
|
|
|
|
|
| |
04-22 09:15:37.459 19569 19569 I auditd : type=1400 audit(0.0:570): avc: denied { search } for comm="pool-2-thread-1" name="zram0" dev="sysfs" ino=48559 scontext=u:r:system_app:s0 tcontext=u:object_r:sysfs_zram:s0 tclass=dir permissive=0
04-22 09:15:37.459 19569 19569 I auditd : type=1400 audit(0.0:571): avc: denied { search } for comm="pool-2-thread-1" name="zram0" dev="sysfs" ino=48559 scontext=u:r:system_app:s0 tcontext=u:object_r:sysfs_zram:s0 tclass=dir permissive=0
|
| |
|
|
|
|
| |
Signed-off-by: Albert I <kras@raphielgang.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Used by GCAM for DSP-accelerated HDR processing
* Arguably we should label /vendor/dsp/cdsp/fastrpc_shell_3 to
same_process_hal_file like Pixels, but the partition is prebuilt thus
we're unable to relabel it.
* Copy the file to writable tmpfs, setup attributes and bind mount back
to workaround the limitation.
[ghostrider-reborn]:
Allow adsp/cdsprpcd and neuralnetworks HAL to access fastrpc_shell_3
[kras edit:
1. rename some contexts as per qva/kona
2. extend to allow camera HAL and VPP service to access it as well]
Co-authored-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
|
|
|
|
|
|
| |
* Update PTN_SWAP_LIST to reflect partition entry changes
to BOOT LUN and handle "multiimgoem", "multiimgqti"
partitions, similar to other BOOT LUN partitions.
|
|
|
|
|
| |
Do fsync after writing partition entries to ensure data
is actually written before rebooting device.
|
| |
|
| |
|
| |
|
|
|
|
| |
* This is no longer used after switching to QTI 1.1 impl.
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
* Use default color mode for all color modes
* Enable QDCM combined mode and disable factory mode
* Drop LiveDisplay's color mode support as it conflicts with AOSP display
color adjustment
* Rest of configuration is kanged off Pixel's overlay
Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: Ib26033fe00a6cc1e8c7d8f93da417516e31a52e3
|
|
|
|
|
|
|
| |
- Extracted veux-user 12 SKQ1.211006.001 V13.0.2.0.SKCMIXM
Signed-off-by: kleidione <kleidione@gmail.com>
Co-authored-by: johnmart19 <johnivan19999@gmail.com>
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
|
|
| |
The ndk_platform backend will soon be deprecated because the ndk backend
can serve the same purpose. This is to eliminate the confusion about
having two variants (ndk and ndk_platform) for the same ndk backend.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Based on observing it's values, xiaomi.sensor.aod reports
the following events:
3.0: Dark environment
4.0: Bright environment
5.0: Switched from bright to dark environment
3.0 does not seem to be triggered anymore after bright
environment has been reported.
- Enable brightness buckets in doze to disable animation
between the brightness levels.
|
|
|
|
|
|
|
| |
Co-Authored-By: AngeloGioacchino Del Regno <kholk11@gmail.com>
Co-Authored-By: IMMANUEL44 <immanuelr44@gmail.com>
Signed-off-by: Anar Jabiyev <cebiyevanar@gmail.com>
Change-Id: I9b785c9ad6d77780ef9ac4bc8545bf4d2795132d
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
|
|
|
| |
According to AOSP docs [1] apps should use xxhdpi resources
for 440 dpi density.
[1] https://developer.android.com/reference/android/util/DisplayMetrics#DENSITY_440
|
|
|
|
| |
* Prevents halo ring/effect on front camera
|
| |
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
|
|
|
|
|
| |
- 2850 seems too low a value let's increase it to 3850 is more pleasing to the eye
- Ref:
https://android.googlesource.com/platform/frameworks/base/+/android-13.0.0_r4/core/res/res/values/config.xml#829
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
|
|
| |
- Not needed for AOSP BT
Change-Id: I4219d2b32fab128ab3c1bd0a33856ec53dca0c98
|
|
|
|
| |
Change-Id: Id11965102d7d5dce50f989c99810cda6a43aa1ec
|
|
|
|
| |
Signed-off-by: daniml3 <daniel@danielml.dev>
|
|
|
|
| |
- Extracted veux-user 12 SKQ1.211006.001 V13.0.2.0.SKCMIXM
|
|
|
|
|
|
|
|
|
| |
* These are currently in FrameworksResTarget, but were
moved to sysprops in Android 13.
https://android.googlesource.com/platform/system/libsysprop/+/976d33062b51e77edde44faad1a6e801c5dc0188%5E%21/#F0
Change-Id: I5bff67a15c537e8a47a19f30776fca6bf2c9fbe5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The class of device is a string with a list of uint8t values:
90,2,12
The meaning is as follows:
{Service Field, Major class, Minor class}
Service Field: 0x5A -> 90
Bit 17: Networking
Bit 19: Capturing
Bit 20: Object Transfer
Bit 22: Telephony
MAJOR_CLASS: 0x02 -> 2 (Phone)
MINOR_CLASS: 0x0C -> 12 (Smart Phone)
Bug: 217452259
Test: make -j; -- check that bluetooth.device.class_of_device is
correct
Change-Id: I24fd57bacbf6786a26f7079e7a6e9857dbe170d1
|
|
|
|
|
|
| |
Bug: 217448211
Test: atest BluetoothInstrumentationTests
Change-Id: I9312b9b70b51603aca6da6f4081533ab73c1614d
|
|
|
|
|
|
| |
Bug: 217448211
Test: make -j
Change-Id: Idd7e52b7822915ed61299f1c0b29bf87ca0339fe
|
|
|
|
|
|
| |
Bug: 214499288
Change-Id: I83757ae6a053ec6b10b08322c4e76d988f1a4a48
Test: Presubmit
|
|
|
|
|
|
|
|
|
|
|
| |
Bug: http://b/215753485
This warning is introduced in clang-r445002. In code where the bitwise
operation was used to avoid short-ciruit evaluation, make that explicit
by introducing temporary variables.
Test: build with clang-r445002.
Change-Id: Ia7ccf1d48922d926313f691888d26c3e314c1056
|
|
|
|
|
|
| |
error: build/make/target/product/gsi_keys.mk does not exist..
Change-Id: I7ac37f3e104f1bc6dce504ca29fcbf078127b399
|
|
|
|
|
|
| |
Test: make android.hardware.sensors@aidl-multihal
Fix: 206867060
Change-Id: I9b78a0f25117d11fdf4beb1e0913393c1c14620d
|
|
|
|
|
|
|
| |
Bug: 220306859
Test: atest
Tag: #feature
Change-Id: I300369d36399ffb558b98bafc2478b872d09faba
|
|
|
|
|
|
| |
- Its set in default.prop
Change-Id: I8d94738978b3ef3f146a938a592500437bfc1b00
|
|
|
|
|
|
|
| |
* Size decreased from 148 mb to 12 mb.
Signed-off-by: Jabiyeff <cebiyevanar@gmail.com>
Change-Id: If680f2b0511f9e348973ea2a98f9f832745f6d79
|
|
|
|
|
|
|
| |
* qcom-camera topic hasn't been ported to 19.1
* Keep building vendor.qti.hardware.camera.device@1.0 interface lib, IMS stack and possibly camera HAL still needs it
Change-Id: I87bcd5b54ad986d5844df50de243fc1a18507198
|
|
|
|
|
|
|
|
|
|
| |
Enable display kernel driver idle timer, which allows dropping to lower
refresh rate earlier and without additional overhead.
Bug: 160682800
Test: track idle timer through systrace
Test: zone test, scrolling
Change-Id: I6e82b58026d7b31cf0cabc0db7bb6277f6731d12
|
|
|
|
| |
Change-Id: Ic0fbdc97961808eba939b5785a4e1c2a275bed63
|
|
|
|
|
|
|
|
|
| |
- I need to revist this later, rollback for now.
- Keep prop to set frame rate multiple threshold to 120 because https://github.com/search?q=Ie4d5c8c9a45079306ad51e1607ae72eb9493ee0c&type=commits
This reverts commit 5fece213ba7bf9c4cfd85f3e1873d1e3291bb551.
Change-Id: I95ad1841a2a4206b681a8503c190dc7ddf4b2cf3
|
|
|
|
| |
Change-Id: I591b4ae4bc0adaa5f57e19ccb5d06dd5f1a42fcd
|
|
|
|
|
|
|
| |
- Our device doesn't support doze
- Fixes AOD flickering issues
Change-Id: I44855e85f7d9e26666a8efb79afc202c69770615
|
|
|
|
| |
Change-Id: Ic8ce5064ca3e27432331ac679b7dd3df166089
|