* E init : [libfs_mgr] Skipping '/dev/block/bootdevice/by-name/qmcs' during mount_all
* E init : [libfs_mgr] Skipping '/dev/block/bootdevice/by-name/vm-persist' during mount_all
This fixes the slow boot problem
Change-Id: Ic35ae826d940f9521df443b6616122a1793711cf
No longer needed now init listens for property changes on a
separate thread.
Bug: 186580823
Test: Cuttlefish boots successfully
Change-Id: Ief3a546d2154231d18957c2f703bd128966d7288
build/make/core/board_config.mk:1001: error: BOARD_API_LEVEL must not
set manully. The build system automatically sets this value..
Change-Id: If59ae9dea6cb13701d7217a1c0a355d4e07113eb
Without this, the camera will be stuck for 10 seconds before the preview is displayed.
* W ServiceManagerCppClient: Service vendor.samsung.hardware.hyper.ISehHyPer/default didn't start. Returning NULL
* E HYPER_NATIVE_VINTF: Couldn't access HyPer Hal
* E HYPER_NATIVE_VINTF: Acquire on JNI, HyPerHalVersion is NULL
* E CHI : [SS_ERR ]: [CHI ]: chxextensionmodule.cpp: ExecuteMemBoost: 25099: MemBoost open fail by 0
* I CHI : [SS_LOW ]: [CHI ]: chxsecperf.cpp: AcquirePerfLock: 1157: 0] OPEN_CAMERA (1000)
* I CHI : [SS_LOW ]: [CHI ]: chxsecperf.cpp: AcquirePerfLock: 1014: OverheatLevel [0~6](0xFFFFFFFF)
* I CHI : [SS_LOW ]: [CHI ]: chxsecperf.cpp: AcquireHyperVInt: 1355: AcquireHyperVInt : maxlimit[3360000], minlimit[2092800], duration[3000]
* I ServiceManagerCppClient: Waiting for service 'vendor.samsung.hardware.hyper.ISehHyPer/default' on '/dev/binder'...
Thanks luk1337 for pointing it out.
Change-Id: I1505ec2ecd7185a47f9bf9bb39a77f475adbe27c
In Android 14, prioritization of partitions is emphasized, diverging
from previous versions where priorities were respected universally.
Overlay precedence now plays a critical role, with the following
partition order dictating overlay precedence:
- system
- vendor
- odm
- oem
- product
- system_ext
When multiple overlays contend for the same resources, the order of
overlays becomes crucial. An overlay takes precedence over others if it
has configurations following its own. This prioritization, while
impactful for GSI compatibility, is essential for maintaining order and
functionality.
Change-Id: I8b7568dcc418dbbd1ccb39e2d0dc66504f19fcdd
* Make parameter of type RilData (second last one) passed to SecRil::RequestComplete()
in OnGetSmscAddressDone() be NULL, so that the framework passes an empty value when sending SMS
* Before U this value was not being used, on U the value returned is "SMSC",format_specifier
which is considered invalid when passed back to RIL for sending SMS, however when an empty value
is passed RIL will select the default SMSC, like it did on T and sending SMS works again
* For the SMSC patch, SecRil::RequestComplete() in OnGetSmscAddressDone()
now looks like this instead: (code**)(), the parameters stayed the same
Change-Id: I608be406969d7fa58f15ef36340aff4ad1ce9fd0
Co-authored-by: Tim Zimmermann <tim@linux4.de>
Signed-off-by: chaptsand <chaptsand@gmail.com>
Use 64-bit dex2oat for better dexopt time.
Bug: 153380900
Test: boot and install an application
Change-Id: I3e7a6e6e9385ff6564d1a2e6dda004ebb061f095
(cherry picked from commit 126f03be80f57a8a0411842011152d9381589b78)
Merged-In: I3e7a6e6e9385ff6564d1a2e6dda004ebb061f095
This sets log_level to 0
10-14 14:17:17.674 14629 14629 I sensors-hal: get_system_config:67, log_level: 0
This is done especially to disable spammy logging of oplus ambient light sensor events
10-14 14:17:12.821 12603 14590 I sensors-hal: handle_oplus_ambient_light_event:157, oplus_ambient_light: ts=3858719100254, lux=11, data_c=0, delta_ms=0, data_cnt=0
Change-Id: Ib097c172bb01ae62dec542a76b289a9641764bc2
Because vndk prebuilt has SONAME set to libcrypto.so, it prevents linker
from loading libcrypto.so built from source.
Change-Id: Ic9e29f7b00b469163f48ea407fc9b5d5e90816c8
Needed to work around a Qualcomm HAL prebuilt.
Bug: 203713560
Bug: 258322017
Bug: 254854421
Test: Forrest
Change-Id: I4eebc60f10fbea6a66127ed3e08441db32536f78
Qcom has issues that prevent it from working with a hermetic
partition build.
Bug: 205632228
Test: Presubmits
Change-Id: I490a29da38a6f68e7dd3650d8140cb11adaa8c7a
Due to visible gamma shifts on our panels, we should make the switchings
to happen conservatively.
With idle timer >= touch timer, idle timer now always takes precedence,
but we're leaving touch timer property to immediately switch back to
120 Hz on touch input events.
Change-Id: If8b1e00a2d2213c4d2288ab28fad4ba0826a36e8
Signed-off-by: Park Ju Hyung <qkrwngud825@gmail.com>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
