Decrease the log level to '3', which would only log KERN_ERR
and lower, onto the console. This is to avoid false-positives
in the test cases that may emit excessive logs, ultimately
leading to a watchdog bark.
Change-Id: I7967272de8e425e93035cd937982bfb3aee19597
This patch removed the old writeout policy tune which was never touched since
2009. In the meantime, most of Android devices are equipped with over 4GB DRAM
and very fast flash storages like UFS, which becomes more like desktop or
servers in 2009. So, it'd be worth to go back to use the default kernel configs.
Bug: 136483670
Bug: 137190999
Bug: 152936751
Test: check value output
Change-Id: I1ebbf9f1f27a921103db51e96a50aadd6ec0dde8
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
Signed-off-by: Martin Liu <liumartin@google.com>
If we set 2048KB ra value in the beginning of the
boot process, services initialized at this time would
keep 2048KB ra value even though we adjust the ra value
to 128KB after boot completion.
This may cause memory pressure.
Bug: 174700194
Signed-off-by: Randall Huang <huangrandall@google.com>
Change-Id: I97ee0ee9511eaada011f2634afd68d68cdca4570
Previously we found that the effect of using sched_boost is very
similar to skipping EAS. Since sched_boost is not used because of
CONFIG_SCHED_WALT not enabled, we can boost performance this way.
Bug: 119932121
Test: launch time and app launch time are better than EAS
Change-Id: Idf8026c258b6c36417c9be9b5c87f7b4bfa3f50d
* By default, AOSP uses the 'US' country code for wifi.
* When a SIM is present, Android can check the correct country
(using information from the SIM itself) and it can set the correct
country code.
* However, if no SIM is present or if the phone is in airplane mode,
Android will just use 'US' as country code and it will disable access to
a lot of frequencies.
To bypass this issue, set the default country code to '00': this
is the "world regulatory domain" and it contains generic settings.
When a SIM is inserted, Android will overwrite the default setting with
the correct country code.
Copy from Google:
12b500667e/init.hardware.rc (524)
Change-Id: If7537357f282c51549f754cd385bc1ab9a9a109c
Signed-off-by: Roberto Sartori <roberto.sartori.android@gmail.com>
Signed-off-by: dogpoopy <dogpoopy.dev@proton.me>
Signed-off-by: bagaskara815 <bagaskara815@gmail.com>
With my previous CL [1], we can override
rounded_corner_content_padding
at the Framework resource layer rather than the SysUI resource layer.
No matter whether
persist.sys.ime.can_render_gestural_nav_buttons
is enabled or not, there should be no observable behavior change in
this CL.
[1]: I0c3717c0bdfc928167c6eba06247b37caabf33b9
24d6b891f572f7be419d3acc9793ca68d062cf35
Bug: 215554582
Test: Manually verified as follows.
1. Build aosp_coral-userdebug and flash it
2. adb shell cmd overlay lookup android \
android:dimen/rounded_corner_content_padding
-> 70.0px
3. adb shell cmd overlay lookup com.android.systemui \
com.android.systemui:dimen/rounded_corner_content_padding
-> 70.0px
Change-Id: I391a504482f25c17f9b67f7eb8f56f362da71ae0
* This constantly crashes potentially because of the major BT stack
changes introduced in QRP1. We need to wait for QCOM to pick and
adapt this changes internally.
E AndroidRuntime: java.lang.NoSuchMethodError: No virtual method isBroadcastActive()Z in class Landroid/bluetooth/BluetoothAdapter;
or its super classes (declaration of 'android.bluetooth.BluetoothAdapter' appears in /apex/com.android.btservices/javalib/framework-bluetooth.jar)
Change-Id: I8a5537122f5487a17af4ddbb6f1febd91ba20245
* For some reason setting minimum brightness value to 0 prevents system from setting anything lower than 128, which
set via "config_screenBrightnessSettingDefault" overlay.
Change-Id: I246a1537c6d0d84f583f6d823c0a6b32bb77f6e8
* It's largely for testing purposes and it consumes
a large amount of memory. If your hardware doesn't
have graphics then it can be useful, which isn't the
case for shipped devices.
Change-Id: I2348718ad3afba846498572161fa7e83dd8b7ce9
debug.stagefright.omx_default_rank=0
was used to rank OMX SW codecs lower than OMX HW codecs
but we have removed all OMX SW codecs now.
Change-Id: Idf55ec02c2c0f4d2fa73f949cffef0d820a54570
* Android 14 allows using /cache as scratch partition. This applies only
to non-A/B devices and provides much faster overlayfs setup.
Change-Id: I2fd13fbe3dbd9c36e569f59022a59bc9068ffa79
Rotator down scaler is causing additional delays that are better
handled by SDE/GL composition.
Bug: b/73168288
Test: Launch the application from homescreen by tapping its coin, and
measure the frame miss ratio within the maximizing window
animation.
Result: Frame misses 11.5% -> 6.5% (full record in b/78773861)
Change-Id: If41987f64d6db8e7cad2fb2c87f25432ed4ea3db
---
Enable the persist.sys.fuse.passthrough.enable flag for the device
configuration to enable the FUSE passthrough feature.
This feature has been enabled on Cuttlefish, Wembley and Redbull devices for
months and no issues have been detected yet.
Bug: 168023149
Test: 'adb shell getprop | grep persist.sys.fuse.passthrough.enable',
ScopedStorageTest
Signed-off-by: Alessio Balsini <balsini@google.com>
Change-Id: I3f39b02af436f7e508bb70efc702565a667a051c
