* They should be dealt with in ROM overlays and current profile URL points to a 404 page
Change-Id: I92f3ded52dda04f6cec5709d51c84b32f39d8095
Signed-off-by: firebird11 <hbgassel@gmail.com>
Also set interval to 40 instead of default 60 since HBM mode is a thing
Change-Id: Idade7f5e786c350e58160e0ed49cd3e7de98951c
Signed-off-by: firebird11 <hbgassel@gmail.com>
Signed-off-by: c79 <vexed@riseup.net>
Signed-off-by: Sandeep P S <sandymankara11@gmail.com>
The stock ROM enables this because our vibrator supports subtle "tick"
vibration effects. Enable it in our device tree as well to make pulling
down the notification shade/QS panel feel slightly more interactive.
Signed-off-by: aswin7469 <aswinas@pixysos.com>
Signed-off-by: Sandeep-FED <sandymankara11@gmail.com>
This is a squash of:
Author: Minchan Kim <minchan@google.com>
Date: Mon Oct 14 14:22:45 2019 -0700
Enable zram writeback job scheduler
Bug: 140882488
Change-Id: I5489a7ce7a8d73306a6ecf69f57d338b2b0eaad2
Signed-off-by: Minchan Kim <minchan@google.com>
Author: Minchan Kim <minchan@google.com>
Date: Tue Nov 26 06:48:48 2019 -0800
fstab: correct zram parameter names
There was a report about warning during boot.
[libfs_mgr]Warning: unknown flag: zram_loopback_path=/data/per_boot/zram_swap
[libfs_mgr]Warning: unknown flag: zram_loopback_size=512M
We don't use zram_loopback_path any longer so remove it.
We also changed zram_loopback_size with zram_backingdev_size so correct it.
Bug: 145116439
Test: confirmed there is no warning and zram backing device was configured
Change-Id: Iafb355999cd4995f34bf67259a8a39993ae8326a
Signed-off-by: Minchan Kim <minchan@google.com>
Signed-off-by: aswin7469 <aswinas@pixysos.com>
Signed-off-by: Sandeep-FED <sandymankara11@gmail.com>
* Currently we use the Display-P3 color space for display composition
across all color modes on op8. We do this to facilitate a new version
of Adaptive color mode; this forces display to always use P3 color
calibration.
* It turns out that in op8's case using P3 color calibration for sRGB
content, even when the content is accurately converted to P3, degrades
color accuracy for certain sRGB colors. To fix this, we revert back to
pre-op8 behavior, where we let SurfaceFlinger choose the most
appropriate color space for composition, for all color modes used on op8
*except* for Adaptive color mode.
Bug: 137140317
Bug: 137053654
Change-Id: I8670f76aa8c7c513e5a6db291c970a20609d032d
* This is only available on Nexus/Pixel devices. Already implemented
in LiveDisplay for devices that have the proper profile in the
QDCM calibration file or provide the commands via sysfs node.
Change-Id: I1dbeafdef930bcfeb2b950b3adce293307abff85
There's no point to keep using custom pref to set minimum refresh rate
when AOSP smooth display feature behaves in the exact same way in
our case.
Change-Id: I497918a9c9687443a9438fb6291769f6e51d9379
The pinner now asks the runtime for these files.
Test: adb shell dumpsys pinner
Bug: 144773394
Change-Id: I8de2a2935901cbd3eaa50ce2d8aa09f61080ba02
Merged-In: Ie633ea788dab3389a3407ec9a461b5837befca46
This change yields considerable SQLite performance gains. It should be generally safe as this device has irremovable battery.
Some OEMs have been doing this for years.
Signed-off-by: Jesse Chan <jc@lineageos.org>
Change-Id: I50d9b3d9f019772fedc7066675249116d5e441e4
Signed-off-by: chandu078 <chandudyavanapelli03@gmail.com>
Signed-off-by: aswin7469 <aswinas@pixysos.com>
This change replaces the '/system/lib64/libsurfaceflinger.so' pin, as
the file was removed in ag/12524602. The updated pin relies on
go/aog/1552085, as system_service needs read access to SurfaceFlinger.
Bug: 176197656
Test: adb shell dumpsys pinner (coral)
- shows that /system/bin/surfaceflinger is successfully pinned
adb logcat | grep PinnerService (coral)
- no longer shows a file-not-found error in PinnerService
Change-Id: Iae2a96c5fe4b1f5698d21de9970140321d11c460
* sRGB on Natural and Boosted
Unmanaged on Saturated
P3 on Automatic
* Set color mode to Natural by default
* Adjust display composition color spaces
Change-Id: If73eafa82395e80acf84445fcab2f1ce25a33e23
Signed-off-by: aswin7469 <aswinas@pixysos.com>
* This is only available on Nexus/Pixel devices. Already implemented
in LiveDisplay for devices that have the proper profile in the
QDCM calibration file or provide the commands via sysfs node.
Change-Id: I1dbeafdef930bcfeb2b950b3adce293307abff85
