| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Change-Id: I4c93b1235a3b3afe985c539b89e8a0785d03fdbe
|
| | |
|
| |
|
|
| |
Change-Id: Ib28c335a4a036701d5f758491c678ce3b40b1784
|
| |
|
|
|
|
|
| |
The reason why I wanted to place that in enchilada instead in sdm845-common is because a device-specific thing
I don't know if fajita has the same sensors (of this type) as enchilada but I don't want to mix them up.
Change-Id: I16d261a1f123055721e8ff4fda91f2b6dcd4bb86
|
| |
|
|
|
|
|
| |
* Typical renames to get proper lunch
* rename overlay-lineage to overlay-aicp and deleted everything within it
Change-Id: Ib3d7c54cfa15909d4d8a4127e58756404ad46a86
|
| |
|
|
|
|
| |
Will be added back after bringup
Change-Id: Icc3f7af0dba1b3da42ec449dc3075cf9aaa96ff3
|
| |
|
|
|
|
| |
Seems like our overlays get ignored otherwise.
Change-Id: Ic03bac31922a57f548accd3c16417fa683565530
|
| |
|
|
|
|
|
|
|
| |
Bring back old usage of status_bar_height, status_bar_height_portrait,
and status_bar_height_landscape by set the size containing cutout size.
Bug: 216782082
Test: make
Change-Id: I0bf97352bc07e45d7694f9512266f08e7139c103
|
| |
|
|
|
|
| |
There's not much of a purpose to have this in the device tree.
Change-Id: I67751642b2f34576106a39a83e21996010215c3d
|
| |
|
|
| |
Change-Id: I367bc78aa19b0362018c8c0f9551153f4037571b
|
| |
|
|
| |
Change-Id: I1ed473bcc8af3ee43f0cea0991095240cf617a3d
|
| |
|
|
| |
Change-Id: I589d097af0a8d31df51bc55b07e7eb640dd99874
|
| |
|
|
|
|
|
|
| |
* 28dp * (450dpi / 160) = 78.75px, this will cause the height
of the status bar to be displayed incorrectly under some apps,
so restore it to its original value.
Change-Id: I82685a0ab33bb08daeaf87b74c93e80aba16c055
|
| |
|
|
|
|
| |
* This is better for user facing stuff than 'ONEPLUS A6003'.
Change-Id: I1f380699692c07b2fcc03fa83adc292b6d899cf7
|
| |
|
|
|
|
|
|
|
| |
With the new added APIs, we don't need to overlay status_bar_height that
contains cutout size and quick_qs_offset_height anymore.
Bug: 186604541
Test: make
Change-Id: I36d869866ed03d3996b7b0d8cc6d3f6bb6ab624d
|
| |
|
|
|
|
|
|
| |
No longer needed.
This reverts commit e35dfd72e7dc1e70afb4ec0719fc141d796fc8df.
Change-Id: Iae9c4257a98dd4ba47ef9992b1dec133ccc56764
|
| |
|
|
|
|
|
|
|
|
| |
* NoCutOutOverlay packages have been moved to fwb in S. That means
we don't need to keep a copy in the device tree, just directly
use the one in fwb and adapt config.xml to our devices.
Change-Id: I45b381c7e45f92e60a8608b3c201c5e48892b0ae
Signed-off-by: Ratoriku <a1063021545@gmail.com>
Signed-off-by: Bruno Martins <bgcngm@gmail.com>
|
| |
|
|
|
|
| |
Commented out 'writepid' should speed up auth a bit.
Change-Id: Ida62664e725fc3e594155cd2db3a157bb3188df2
|
| |
|
|
| |
Change-Id: I2889502b5ab53439cf26ea5863c4659c2e216053
|
| |
|
|
| |
Change-Id: Ieeca84e5a296f617748afee9a8ea604cf048403a
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Google's prebuilt cgroups.json and task_profiles.json for products
launched with previous API levels only covers
ro.product.first_api_level >= 28. [1]
OnePlus 6 was launched with Oreo MR1 (API level 27), so schedtune and
task groups are completely broken. Since the system also checks
/vendor/etc for vendor profiles, make a copy of cgroups_28.json
and task_profiles_28.json and ship them to /vendor/etc. Profiles
for previous API levels are all the same anyway.
Test: boot and check /dev/stune/
[1] system/core/libprocessgroup/profiles/
Signed-off-by: Chenyang Zhong <zhongcy95@gmail.com>
Change-Id: I65fe622a804a720a97b43d8092cc8a37703f4b64
|
| |
|
|
| |
Change-Id: I64d11103ddb8f9dce70b9bc110745d4aafd667dc
|
| |
|
|
| |
Change-Id: I0e89fcab283b957b9d4262ae07e269cbc6dd433d
|
| |
|
|
| |
Change-Id: I6a2eb3c59e7cf5a6a74a128310737f81bdeedc93
|
| |
|
|
| |
Change-Id: If9dfa5c8a9dfd2f6d7e0cfc78d4f193bb2266c48
|
| |
|
|
|
| |
Signed-off-by: AnierinB <anierin@evolution-x.org>
Change-Id: I9e0d5a5b190edc416ec12c65494a640b3cd6ce57
|
| |
|
|
| |
Change-Id: I8c83c30762025d1ff8091ce75bf4d3784c5a6f76
|
| |
|
|
|
|
|
|
|
|
|
| |
* Because of config_roundedCornerMultipleRadius being set to
obnoxiously high value we end up having too high corner
border radius for Android recents.
* Also we still need to set rounded_corner_radius to something
other than 0 so that we'll have our rounded border drawables
applied. I guess that 8dp is a fair value for that.
Change-Id: Ib39ac6c4aaf6c00c247b2945e4f0a71ab0789df5
|
| |
|
|
| |
Change-Id: I89ce857d15804f9a9361ff3825a9426a9382c578
|
| |
|
|
| |
Change-Id: Ifbf18f79a1d0f173cb5b83bdf0178db2a5f1373e
|
| |
|
|
|
|
|
|
| |
* TARGET_DEVICE isn't really used for generating props
anymore as tools/buildinfo_common.sh is using
PRODUCT_DEVICE instead.
Change-Id: Ic042b209a3af5d611d3a460a9add5f9e6e475918
|
| |
|
|
|
|
| |
Bug: 77599627
Test: lunch [see entries in list]
Change-Id: Id44fcfec47eeb979a745f879031f1bec7359a633
|
| |
|
|
| |
Change-Id: I45edeb3ae20f374cd4510bad83b3a51059a7e743
|
| |
|
|
| |
Change-Id: I26b6277e89ff9a26daa7d2ae16c50e873eddecfa
|
| |
|
|
|
|
| |
* We aren't an emulator!
Change-Id: If28267b9309327a77edc49c1b0069e380717b416
|
| |
|
|
|
|
|
| |
Bug: 112876936
Test: manual
Change-Id: Ibcefa4b50713c451a398409c1bc941cd833921f2
(cherry picked from commit 2a3d90837c0811ce31705ae135e5eb517f38403b)
|
| |
|
|
|
|
|
| |
Bug: 112876936
Test: Go to Settings > Developer Options > Simulate display with cutout > "No cutout". Cutout should be hidden. Rotate screen, take screenshots, screenrecord should all work.
Change-Id: I66684d8254fd3c1ee6851e67c0b09d176d4c02af
(cherry picked from commit dcc48dc9071c37c8b9fe7caee96585d20d149060)
|
| |
|
|
| |
Change-Id: I3a05344f949eae581f1f17cc33b1df475d3e6760
|
| |
|
|
| |
Change-Id: I4a8f81b2eb05dafc2b022daddb210eb3100e36f0
|
| |
|
|
| |
Change-Id: I9f81f684d491ed447b7bdb2ca70f558bf75ebc67
|
| |
|
|
| |
Change-Id: I229b626136cc7c63f83436cd3cd1ba0e960a945e
|
| |
|
|
| |
Change-Id: I6256a215bfeb4ece746ba7553b9963f476e3db17
|
| |
|
|
|
|
| |
This reverts commit e3f5c9daf3912f4a7eaf849c8970bdaeff14090c.
Change-Id: I94c684b34a4c2951aea4e05b50ff1561ea7ff0ff
|
| |
|
|
| |
Change-Id: I74423ebc978585065fe0b2acb58bff8cefcef577
|
| |
|
|
| |
Change-Id: I8cac10e18fe17931c5e6f18b57718a976e598f62
|
| |
|
|
| |
Change-Id: I48c5601293336919804b6aaefbd52f575c04bbf5
|
| |
|
|
| |
Change-Id: I897dcdaa48e676c579f222151c45558709bb0635
|
| |
|
|
| |
Change-Id: Ib24e0a33a97ce3b528dac52dfb01b56f7e954c67
|
| |
|
|
| |
Change-Id: I91cf06f371238c44c8a03dbd8bdb0f30db8ebadf
|
| |
|
|
|
|
|
|
|
|
|
| |
When being in dark environments, turning screen off, then moving to
bright environments and turning screen on, sometimes it happens that the
light sensor emits an initial light sample of 1 lux, which causes the
automatic brightness controller to ramp down the brightness even though
the ambient brightness is high. Avoid the controller using those samples
by giving the light sensor some time to warm up.
Change-Id: I81dcb41a25ff0c9f0cf3265da7054ac7ebcbcc34
|