In Android 14 and higher, the platform reduces the maximum
memory that can be locked using mlock() to 64 KB per process.
In previous versions, the limit was 64 MB per process.
The new restriction promotes better memory management
across apps and the system.
Test: CtsInitTestCases#MemLockLimit
Signed-off-by: Ashok Mutyala <quic_amutyala@quicinc.com>
Change-Id: I883bff0c1e4bd540a1fae9ab0ea35ebdf4da5255
Since Ext4 doesn't implement "-o sync", it commits metadata at every 5 secs.
This may cause /metadata corruption.
Bug: 162883014
Change-Id: Icd38754bad1b1529d01165ea8c703c214d20bb4b
Signed-off-by: Randall Huang <huangrandall@google.com>
Making these partitions erofs saves ~674MB, which lets us reserve
significantly more space on /product.
Change-Id: I88984f6137c0bc9f01da742a7a485445c2162157
No longer needed now init listens for property changes on a
separate thread.
Bug: 186580823
Test: Cuttlefish boots successfully
Change-Id: Ief3a546d2154231d18957c2f703bd128966d7288
These are critical for display performance and should not be balanced
in order to improve latency and responsiveness.
And also affine them.
Change-Id: If49ecb8757d133a7fad0d7946837b35403e57c2a
For easy transition from SchedTune to UtilClamp, direct access to these
cgroups should be abstracted by using task profiles. Replace writepid
commands with new task_profiles command.
Bug: 155419956
Test: change .rc file and confirm task profile is applied
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Change-Id: Ide373c283359cf4b73af4cb0813d8c0306942595
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
Holi supports linux based charging and not via ADSP,
hence remove the modem partition mount logic.
This improves the entry time into power-off charging mode.
Change-Id: I69337e773f6078bc0847b7db199fc21e8c975a8a
[TP0]touchpanel: tp_fw_update_work: fw_name = tp/19825/FW_S6SY792_SAMSUNG.bin
[TP0]touchpanel: fw_name_fae is tp/19825/FW_S6SY792_SAMSUNG_FAE.bin
sec-s6sy792 2-0048: Direct firmware load for tp/19825/FW_S6SY792_SAMSUNG_FAE.bin failed with error -2
sec-s6sy792 2-0048: Falling back to sysfs fallback for: tp/19825/FW_S6SY792_SAMSUNG_FAE.bin
[TP0]touchpanel: retry times 0
[TP]sec-s6sy792: sec_fw_update is called, force update:0
[TP]sec-s6sy792: img version in bin is 0x28240117, img version in ic is 0x28240117
[TP]sec-s6sy792: config version in bin is 0x28240108, config version in ic is 0x28240108
[TP]touch_interface: read block_1, free once.
[TP]touch_interface: read block_1, kzalloc success(len:1152, buf_size:1152).
[TP]sec-s6sy792: update firmware state: no need update!
[TP0]touchpanel: release all touch point and key, clear tp touch down flag
[TP]touch_interface: read block_2, kzalloc success(len:1, buf_size:256).
[TP]sec-s6sy792: sec_change_to_np_mode: change to np_mode time: 0 success!
[TP]sec-s6sy792: sec_enable_fingerprint_mode: touchhold_enable: 0 success!
[TP]sec-s6sy792: sec_enable_black_gesture, enable = 0
[TP]sec-s6sy792: sec_enable_black_gesture: 0 times change black gesture success
[TP]sec-s6sy792: limit_switch is 1
[TP]sec-s6sy792: sec_enable_charge_mode: state: 0 success!
[TP]sec-s6sy792: sec_enable_headset_mode: state: 0 success!
[TP0]touchpanel: add qos request in touch driver.
[TP0]touchpanel: fw update finished
Change-Id: Iba517b59fe2856ed6f991c07e0362b1be203af45
* This is read by the feature enabler client. OOS already
does this but we want to make sure we're doing this for
users upgrading from Lineage 18.1.
Change-Id: I1d112d9cea6f3d0e87cdf12898587c7bacf8de9c
