* MediaTek's r_submix has a few modifications over the AOSP one, mainly
PCM dumping, which we already disabled with [1] and some misc changes
which we don't really need, therefore move to the AOSP module.
[1]: afca579
[Shirayuki39]: We're also already building the AOSP module
Change-Id: Ie7ae303501d305dde5fe943187f45105be1e02b8
Signed-off-by: claxten10 <claxten10@gmail.com>
Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
Signed-off-by: KimelaZX <mmikailrei@gmail.com>
MediaTek switched from 2 independant AP interfaces to a single AP_BRIDGED interface, the exact reason why is unknown.
Change-Id: I41d210e0dfc11ba4f1ee007ab19aaf4f70745e76
Signed-off-by: Cyber Knight <cyberknight755@gmail.com>
Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
Signed-off-by: KimelaZX <mmikailrei@gmail.com>
this caused the error "module "android.hardware.audio.common@2.0-util" variant "android_arm64_armv8-2a-dotprod_cortex-a76_shared": cflags: Expected all branches of a select on condition soong_config_variable("android_hardware_audio", "skip_speaker_layout_channel_mask_field") to have type string, found bool"
Signed-off-by: KimelaZX <mmikailrei@gmail.com>
* Also drop no-op imports
Signed-off-by: Sarthak Roy <sarthakroy2002@gmail.com>
Change-Id: I22dcf417b7feb2379ed77761bd851317e0c8a955
Signed-off-by: KimelaZX <mmikailrei@gmail.com>
In a previous commit bb0838b5114419b4f8ecff67c0b6fb728399c7b7, the gc_urgent_sleep_time for F2FS was aggressively set to 50ms to optimize GC.
This change, however, led to performance regressions on most devices, particularly of those running in 4.19+ kernels.
From our tests, the heightened CPU and I/O activity from this aggressive garbage collection setting is the likely cause.
To address this, we're revising the gc_urgent_sleep_time parameter to strike a balance between aggressive GC and device performance, taking
bb0838b5114419b4f8ecff67c0b6fb728399c7b7 goal into consideration.
Furthermore, the dirty writeout policy has been aligned with the latest configurations used in Pixel devices,
and cp_interval has been adjusted to surpass dirty_expire_centisecs for improved power efficiency during idle times.
[ChrisCatto]: Do not set dirty_background_ratio to 10 because that is the default value for us anyways.
Test: booted partner device, monitor performance
Change-Id: Ie4d0c870d734e915aaebcc53e64acdabac47b6dc
Signed-off-by: minaripenguin <minaripenguin@users.noreply.github.com>
Signed-off-by: KimelaZX <mmikailrei@gmail.com>
* We don't even use this as our panels does not support high touch polling rate, fck you transsion
* Also breaks pure AOSP builds
Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
Signed-off-by: KimelaZX <mmikailrei@gmail.com>
this caused the error: "module "vendor.lineage.health-service.default" variant "android_vendor_arm64_armv8-2a-dotprod_cortex-a76": cflags: Expected all branches of a select on condition soong_config_variable("lineage_health", "charging_control_supports_bypass") to have type string, found bool"
Signed-off-by: KimelaZX <mmikailrei@gmail.com>
in latest changes of Lineage-23.1 this has been dropped, so switching to prebuilt. also add NFC NXP AIDL fixed!
Signed-off-by: KimelaZX <mmikailrei@gmail.com>
* This partition is never used in AOSP ROMs, and does not even get mounted at all
* Judging by the contents, this only contains logs when booted to Transsion's Trash OS like tranlog.txt
Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
Signed-off-by: KimelaZX <mmikailrei@gmail.com>
which enables
sha256 for Pixel devices, we should do the same thing for CuttleFish.
Bug: 178983355
Test: ,
and checks sha256 is used for dm-verity partitions.
Signed-off-by: KimelaZX <mmikailrei@gmail.com>
The Vulkan backend is the intended production configuration and what we
shipped gs101 with.
Also checked remaining gpu configuration and minimized textual
differences from the gs101 device.mk for easier comparison.
Bug: 223406172
Test: Launcher, YouTube video playback, Pixel Camera preview & shot
Change-Id: I85e3c34ef424f7cef97bcfb6f5a10746fc0b9804
Signed-off-by: Ido <dev.xyzuniverse@gmail.com>
Signed-off-by: fjrXTR <fajarslebew31@gmail.com>
* When blur is being rendered, there's a possibility we tapped the screen
while the blur is still shown, which overrides our EXPENSIVE_RENDERING
CPU freq boosts with the values from interaction, which are lower.
* Ensure CPU freq. remain high during blur (or other expensive renders)
by ending the INTERACTION hint.
test:
- open qs (or other actions that produce blur)
- cat /sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq
- should output 2000000
Change-Id: If0094c5e1013c092a057d66faa2d1280450523f4
Signed-off-by: claxten10 <claxten10@gmail.com>
Signed-off-by: Shirayuki39 <lorddemecrius83@proton.me>
Signed-off-by: KimelaZX <mmikailrei@gmail.com>
