Sm7125-common is still using non-AB update.
non-AB code will be moved to a separated namespace, add
deprecated-ota to sm6150-common namespace list ahead of time to avoid
breakage.
Test: th
Bug: 324360816
Change-Id: I909064be36e8febe80492cf010eb6eac3d6bc33d
The health AIDL HAL service provides functionalities of charger,
therefore system charger at /system/bin/charger is deprecated.
On top of that, QTI health AIDL HAL service enables suspend by
default, the equivalent of setting ro.charger.enable_suspend
for legacy charger.
Change-Id: I59c23e7974cea1174b0161f31a535fa3afa1e5c9
Add an trigger to start the fingerprint HAL immediately
after /data is mounted. Keeps to avoid race
conditions, but ensures the HAL is available early enough for
first-boot SetupWizard enrollment.
This fixes the issue where fingerprint setup fails during initial
device setup but works after skipping and opening Settings.
Signed-off-by: aminfauzi <aremean0107@gmail.com>
When blur is enabled,
There is severe lag in; Launcher3 while scrolling apps in App drawer, Scrolling through recents and occasionally on QS pull down.
Explicitly disabling the "Enable GL comp backpressure" prop seems to slove the issue.
Lag & janks are gone now, even with blur.
Change-Id: Ia82d84d6ee867caa52ae93b72fbff132070bf808
Signed-off-by: helliscloser <mrumais@gmail.com>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
Turns on `debug.sf.enable_adpf_cpu_hint` to allow SurfaceFlinger to utilize Android Dynamic Performance Framework CPU hints, improving overall UI responsiveness and frame pacing on Snapdragon devices.
Change-Id: Ia715ab89ffc8a18130904e5588f9e4b487a20faa
- All latest soc use it by default. with this cache can improve performance by reusing composition, This can result in smoother UI performance and potentially lower power consumption
- cons: It does increase memory usage because the system needs to store these results, but its not a big issue cause most devices are 12gb ver. and fine for 8gb also
Signed-off-by: Ghosuto <clash.raja10@gmail.com>
Enable comprehensive ART optimizations including VDEX and ODEX
generation for all system components to improve first-boot
performance and reduce application startup latency.
Configuration:
- WITH_DEXPREOPT := true # Global dexpreopt enable
- DEX_PREOPT_DEFAULT := generate-vdex-and-image # VDEX+ODEX gen
- WITH_DEXPREOPT_DEBUG_INFO := false # Exclude debug symbols
Results:
- Verified generation of .odex files (optimized dex)
- Verified generation of .vdex files (verification dex)
- ART images created for core system components
- First boot time significantly reduced
- Application startup latency improved
Test procedure:
1. Full system build with 'm evolution' command
2. Verified artifacts in:
- system/framework/oat/arm64/*.odex
- system/framework/oat/arm64/*.vdex
- system/app/*/oat/arm64/*.odex
- system/priv-app/*/oat/arm64/*.vdex
3. Confirmed valid ART runtime loading during boot
Signed-off-by: johnmart19 <johnivan19999@gmail.com>
Signed-off-by: Quince <quinceroms@gmail.com>
Log:
07-08 14:11:18.637 1300 1300 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.qti.hardware.capabilityconfigstore@1.0-service": library "vendor.qti.hardware.capabilityconfigstore@1.0.so" not found: needed by main executable
07-08 14:11:18.724 1366 1366 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/vppservice": library "vendor.qti.hardware.capabilityconfigstore@1.0.so" not found: needed by /vendor/lib64/libvpplibrary.so in namespace (default)
07-08 14:11:23.638 3100 3100 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.qti.hardware.capabilityconfigstore@1.0-service": library "vendor.qti.hardware.capabilityconfigstore@1.0.so" not found: needed by main executable
07-08 14:11:28.644 3177 3177 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.qti.hardware.capabilityconfigstore@1.0-service": library "vendor.qti.hardware.capabilityconfigstore@1.0.so" not found: needed by main executable
07-08 14:11:33.651 3194 3194 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.qti.hardware.capabilityconfigstore@1.0-service": library "vendor.qti.hardware.capabilityconfigstore@1.0.so" not found: needed by main executable
07-08 14:11:28.395 5816 5816 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.qti.hardware.capabilityconfigstore@1.0-service": library "vendor.qti.hardware.capabilityconfigstore@1.0.so" not found: needed by main executable
07-08 14:11:45.348 7112 7112 F linker : CANNOT LINK EXECUTABLE "/vendor/bin/hw/vendor.qti.hardware.capabilityconfigstore@1.0-service": library "vendor.qti.hardware.capabilityconfigstore@1.0.so" not found: needed by main executable
This enables camera apps (and other whitelisted apps) to use auxiliary sensors without HAL restrictions, preventing crashes when switching lenses.
Signed-off-by: aminfauzi <aremean0107@gmail.com>
From dumpsys media.camera, the vendor tag showed EIS type = 2, which corresponds to:
0 → None
1 → EIS v2
2 → EIS v3
3 → OIS
4 → OIS + EIS
So your blobs natively support EIS v3 (type 2).
If you force is_type=4 (OIS+EIS) but your device only has EIS (no OIS hardware), the HAL may either:
silently fall back to EIS v3 (type 2), or misbehave / crash in certain modes
- Add PRODUCT_COPY_FILES entry to install excluded-input-devices.xml
into /vendor/etc
- Ensures vibrator HAL ignores blacklisted input devices
- Prevents duplicate or unintended haptic feedback
- Improves consistency of vibration across UI and apps
- Increase blocks-per-second range from 24–979200 to 36–979200
- Prevents codec operation at extremely low block rates
- Reduces risk of underruns and playback instability
- Improves scheduling efficiency and smoother video performance
Trade-off: drops support for extreme low-FPS edge cases, but ensures
better stability across typical playback/recording scenarios.
- Enable ZRAM with LZ4 compression and tuned swappiness
- Adjust CPU hispeed freqs and minimums for better responsiveness
- Configure schedutil governor for both clusters
- Lower migration thresholds for smoother task distribution
- Tune core_ctl for balanced performance vs. idle drain
- Re-enable sleep states for improved standby battery
- Set up bw_hwmon and mem_latency governors on interconnects
- Cleaned out unnecessary/duplicate entries from script
Overall effect: smoother UI, faster app response, and better
multitasking with minimal idle power impact.
The legacy 2.0 multihal does not support ScopedWakelock handling,
causing non-wakeup sensors (e.g. BMI160 gyroscope) to stall unless
the screen is actively touched.
Migrate to android.hardware.sensors@2.1-service.multihal_realme_sm7125
to properly integrate ScopedWakelock and per-event wakelock tracking.
This resolves issues where the gyroscope only reported data
while the device was awake, ensuring continuous event delivery
even when idle.
Tested:
- Gyroscope events stream without requiring screen touches
- dumpsys sensorservice shows correct flags and batching
- No regressions observed in other HAL sensors
- Replaced static performance governor with dynamic schedutil for all cores
- Tuned up_rate_limit_us and down_rate_limit_us for smooth everyday performance
- Set scaling_min and scaling_max frequencies according to Kryo 465 Gold/Silver cores
- Configured core_ctl for little cluster (min_cpus, busy thresholds, offline delay)
- Disabled core_ctl on big cluster to let scheduler manage ramp-up efficiently
- Adjusted b.L scheduler parameters (sched_downmigrate, sched_upmigrate, group migrate)
- Set sched_little_cluster_coloc_fmin_khz for smoother colocation
- Applied sched_load_boost per CPU for better responsiveness
- Configured input boost frequency and duration for UI snappiness
- Updated memory and bus DCVS parameters for balanced performance/power
- Maintained conservative power optimizations (cpusets, sleep modes, kswapd, I/O scheduler)
This commit ensures a universal setup for normal daily use and gaming while
avoiding overheating and maintaining high FPS
