| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
- Extracted veux-user 12 SKQ1.211006.001 V13.0.4.0.SKCMIXM
Signed-off-by: kleidione <kleidione@gmail.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- Specifies whether to decouple the interactive state of the
device from the display on/off state.
When false, setInteractive (true) will be called before the display is turned on
and setInteractive (false) will be called after the display is turned off.
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
|
|
| |
- [ 7206.619148] type=1400 audit(1666291831.667:316): avc: denied { ioctl } for comm="sensors@2.1-ser" path="socket:[441443]" dev="sockfs" ino=441443 ioctlcmd=0xc502 scontext=u:r:hal_sensors_default:s0 tcontext=u:r:hal_sensors_default:s0 tclass=qipcrtr_socket permissive=0
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
* first-boot is set to quicken to reduce first boot times
* we are installing with speed-profile to have balance
between time taken to optimise and runtime performance
* once device is in idle+charging, bg dexopt will compile
for maximum runtime performance
[ghostrider-reborn]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a squash of the following commits:
1. Optimise dex flags for a faster boot
* Used multiple threads and speed profile to hasten the first boot
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
Change-Id: I2cce5ddf7d50308511e81436fcac613b2c6537bf
2. Rework dex flags again
When I went through https://source.android.com/devices/tech/dalvik/configure my previous configs felt wrong, this one should be perfect (I hope).
Even though there is a slight trade-off for boot time by using the speed profile, we do make up for it by using 8 threads.
PRODUCT_DEX_PREOPT_DEFAULT_COMPILER_FILTER attempts to compile all prebuilts fully optimised to speed level, thus the phone doesnt need to deal with it.
I also do know that this might be a trade-off on size, but I do see the first boot time is more worthy to trade-off.
The speed level mentioned here runs dex verification and compiles all AOT methods.
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
Signed-off-by: Omkar Chandorkar <gotenksIN@aosip.dev>
Change-Id: Ic0156ff8956a7c5f53820be6db438f6f6399d3c0
3. Switch certain dexopt profiles to verify
Prebuilt apps like Gmail/Google App, will be updated by google play, and there is no need spend time and space optimising what is going to be replaced.
Switch to Google's recommendation of using verify for an OTA package.
Applications still stay on speed.
Instead, replace the install profile with speed-profile making apps perform better.
Signed-off-by: baalajimaestro <me@baalajimaestro.me>
Change-Id: I2cce5ddf7d50308511e81436fcac613b2c6537bf
|
| |
|
|
|
|
|
| |
its value is 1 in coral sources: https://android.googlesource.com/device/google/coral/+/refs/heads/master/product.prop
also fixes Android Auto related issues
|
| |
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
| |
- According to https://source.android.com/docs/core/graphics/unsignaled-buffer-latch
|
|
|
|
|
|
|
|
|
| |
If the prop debug.hwui.skia_atrace_enabled is enabled, too many
skia tracing calls will be printed in every frame. This has obvious
overhead on performance/power, and can cause many janks. So disable
it by default, and user can set it manually if necessary.
Change-Id: I5d470b22a643634bdd7db9f307c29deae6ff176f
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
| |
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
|
|
| |
* ref: P-404/android_device_qcom_common@87fc9c5
This causes weird inconsistent scrolling behaviors, even on v5.4
|
|
|
|
|
| |
In weaker SOCs, AVC 3.1 seems to pull less load on the CPU/GPU
and therefore using it has performance advantages in screen recording
|
|
|
|
| |
Change-Id: I93b25c5d0989c83d1c8d7b7946a083771febdddd
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
| |
Signed-off-by: kleidione <kleidione@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Credits:
https://github.com/xiaomi-sm8250-devs/android_device_xiaomi_sm8250-common
- Adapte to pixelexperiece
- Drop doze
- Drop fod and pop camera
- Add Clear speaker
- Adapte SEPolicy credis: [Sebastiano Barezzi, Chenyang Zhong]
Co-authored-by: Sebastiano Barezzi <barezzisebastiano@gmail.com>
Co-authored-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Co-authored-by: kubersharma001 <kubersharma001@gmail.com>
Co-authored-by: TheScarastic <warabhishek@gmail.com>
Co-authored-by: Joey <joey@lineageos.org>
Signed-off-by: kleidione <kleidione@gmail.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
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
|