It is now set in the common init.rc file.
Bug: 392622882
Flag: EXEMPT not supported for init.rc files
Signed-off-by: Qais Yousef <qyousef@google.com>
Change-Id: I3cdbd40e205d2ae9be49e97c9ef7cc32222852e9
compared to ag/31352563 I did not transfer the settings for "write /sys/devices/system/cpu/cpuidle/current_governor teo", which caused the problem
Test: Verified if all values of transferred settings are as they should be after rebooting the device, and and checked that there are no new selinux errors for hal_power_default, verified all metrics that caused power regression in the previous commit on abtd
Bug: 335874870
Flag: EXEMPT not supported by this component yet
Change-Id: I3485325c7416fbc812eaec7da00e337840125053
Test: Verified if all values of transferred settings are as they should be after rebooting the device, and and checked that there are no new selinux errors for hal_power_default
Bug: 335874870
Flag: EXEMPT not supported by this component yet
Change-Id: I595d69d9fa241489e1a4b7fe407d6f74f8c62039
For multi-window foreground app group.
Bug: 200769420
Change-Id: I2b65feb4732e33b27155dcfaf0b64a38b1b01026
Test: build pass
Flag: NONE vendor init file does not support flag
Bug: 335874870
Test: Checked that permissions and values for all affected files are correct (ls -l, cat)
Flag: EXEMPT not supported by this component yet
Change-Id: Ifbea91bce20e046a6e1b92295814a27e99f41dbe
Add task profiles and set permissions.
Bug: 355612114
Flag: NONE init rc file does not support flag
Test: build pass
Change-Id: I4b285a95b5a9d3934a5b95ba57424a89a98f9b2a
Since pixel performance has a shared configuration,
we need to move override values into late init.
Bug: 381100494
Test: Boot
Flag: EXEMPT bug fix
Change-Id: I20d38e481d43d1068a6faebec298446929812ffb
Set InputDispatche and InputReader prefer idle explicitly, which is a
workaround and should be removed after they become ADPF.
Bug: 366146314
Flag: NONE init rc file change does not support flags
Test: tasks set as expected
Change-Id: I38afa16f8f85e6aea31ddd5367c2e2d4a3249ced
Bug: 347122505
Test: check the priority and latency of input thread in Perffeto
Flag: NONE early device setting updates
Change-Id: I3977722564241817575d94b2d2023eac6939ce1c
The mq-deadline I/O scheduler is more stable than BFQ. Additionally, the
boot time is shorter with the mq-deadline I/O scheduler. It only changes the scheduler on new kernel.
Bug: 186902601
Test: forrest build
Change-Id: I51605b32afb4340d416fe4923570bb3f4af24ab8
Signed-off-by: Ocean Chen <oceanchen@google.com>
The preferred_idle_mask is changed during boot time, but it does not
restore to the default setitng as in powerhint, so some node may keep
the wrong value when framework restarts.
Bug: 248621289
Test: build pass
Flag: NONE init rc file change does not support flags
Change-Id: I892b99b79ff2dd9c02cc874026b43b06bded6f59
Remove irrelevant copy and paste content. None of the zuma
devices ever included these services and these sockets are
not doing anything.
Bug: 234559097
Test: presubmit
Flag: EXEMPT dead code removal
Change-Id: I8664262708b89016227d7df076e7c8d70a53de07
This change is to allow the CPU Idle Histogram Stats to be dumped in
bugreports so that there is more insight into the idle behavior of
devices in the field.
Test: Build/Flash
Test: Collect histogram log
Bug: 344908619
Flag: EXEMPT bugfix
Change-Id: Ib6e4772737a8c1f22ac8ba31c40099baeab43853
Signed-off-by: Vishvam Mazumdar <vmazumdar@google.com>
This reverts commit 721a8358c6.
Reason for revert: 24Q3 has been cut, relanding the original commit ef68e9b578.
Change-Id: I7882ebafd66d126df9ccbe2124617fbf4ed73eb5
Bug: 347272991
During boot, this CL adds the following sequence of actions:
1. mount original efs partitions(most likely f2fs) on /mnt/vendor/efs
2. copy files in /mnt/vendor/efs to /data/vendor/copied/efs.img
3. fsync all the files in /data/vendor/copied/efs.img
4. rename /data/vendor/copied/efs.img to /data/vendor/copied/efs
5. bind-mount /data/vendor/copied/efs to /mnt/vendor/efs
6. repeat 1-5 for efs_backup and modem_userdata
The original EFS partitions are mounted and only used for file
copying, no destructive action done on original efs partitions.
Test: reformat /data as ext4, boot the device
Bug: 319335586
Change-Id: Ide78be316778acfc5c582c4a7b78853796cf4c1e
Revert submission 26822004
Reason for revert: Potential culprit for b/339099720- verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.
Reverted changes: /q/submissionid:26822004
Change-Id: Ie9598a3b3b56c8ce26f475079798c44314696f44
During boot, this CL adds the following sequence of actions:
1. mount original efs partitions(most likely f2fs) on /mnt/vendor/efs
2. copy files in /mnt/vendor/efs to /data/vendor/copied/efs.img
3. fsync all the files in /data/vendor/copied/efs.img
4. rename /data/vendor/copied/efs.img to /data/vendor/copied/efs
5. bind-mount /data/vendor/copied/efs to /mnt/vendor/efs
6. repeat 1-5 for efs_backup and modem_userdata
The original EFS partitions are mounted and only used for file
copying, no destructive action done on original efs partitions.
Test: reformat /data as ext4, boot the device
Bug: 319335586
Change-Id: I4c4024b4cad18199226f5644f98254b2230574d6
Next CLs in this stack will make changes to persist/efs mount process
This CL will first move relevant code to a separate file for easier
review.
To support booting under 16K page size, we need to copy files on
persist partition(F2FS, which does not support 16K page size)
to data partition(which will would be EXT4 for dev option enabled
devices).
Bug: 319335586
Change-Id: I2750eb8b53431037cecc972448799409345f5ca3
From field data, sometimes kcompactd is
pretty activated and can impact critical
CUJs. Disable it first to mitigate the
impact.
Bug: 332916849
Test: boot
Change-Id: I87cdcf184afb5fe10e873162b94bd3bf54b1acbd
Signed-off-by: Martin Liu <liumartin@google.com>
DisplayPort kernel driver passes error code/status to hardware composer
via the dp_hotplug_error_code sysfs file. When HWC receives/consumes
the error, it will write "0" into that file to reset the error code. So
this file must be readable and writable by the HWC code running with
"system" user/group permissions.
Previously we used to set the ownership to system:system, but in order
to be more consistent with the rest of sysfs files in that directory,
we can use root:graphics instead with permissions 0664. HWC runs
under the "graphics" group, so this should allow HWC write access.
Bug: 324953626
Test: checked permissions of dp_hotplug_error_code sysfs
Change-Id: Idf65acc12d158a78565c41f4e2aea24362e2cdff
We have observed more reclaiming activities as upstream
has changed how PCP high is calculated since 5.15 kernel.
Re-align the level back to 5.10 first so we can monitor
how it impacts the MM metrics.
Bug: 309409009
Test: boot
Change-Id: I7ac1eb88a8dae7c823330a2c75aec9547bd5c427
Signed-off-by: Martin Liu <liumartin@google.com>
