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
* Move from fstab.default to fstab.qcom for better compatibility
* Xiaomi hardcode androidboot.fstab_suffix=default in bootloader so let's force load qcom
* Also remove fstab.emmc and recovery.fstab as they're not used
* Inline fstab with sm8250
* Move qcom recovery init script to Android.bp
Since we dropped dynamic thermal profile implementation, set the default thermal profile to 0 (Disabled) and let mi_thermald driver does it's magic.
Signed-off-by: Joey Huab <joey@evolution-x.org>
* cnss_diag doesn't exist in proprietary-files.txt,
and it doesn't make sense to leave residual services in init.target.rc.
Co-authored-by: MB <mb150996@gmail.com>
Co-authored-by: Aquarius223 <2777968262@qq.com>
Change-Id: I0f9cef6beb8bd2c593a628a057b97cc4d82842d2
Fix for:
W/libperfmgr( 670): Failed to write to node: /dev/stune/top-app/schedtune.boost with value: 10, fd: -1
W libperfmgr: Failed to write to node: /dev/cpu_dma_latency with value: 61, fd: -1
Change-Id: Ieb385110f236ab12549aea198639708068fb6156
* Some of these scripts are unused on lito, so remove them
* Also remove factory scripts, meant for eng
Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: I19cb6c84a4767cdc790f3ad42c256ca20ecde629
The idea is to allow us to not depend on stock QTI Bluetooth HAL, as MAC
addresses fetched from NVRAM by nv_mac script will be saved as hex-encoded
files. We can decode back saved files to then the Bluetooth one be set using
persist property so it can be read by Bluetooth HAL.
This is loosely based on similar techniques used on Mi 9 and ZenFone Max Pro M2.
Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: I74d07c3c3125a04962c37fe8bfcc8385d1fd3398
* Used by GCAM for DSP-accelerated HDR processing
* Arguably we should label /vendor/dsp/cdsp/fastrpc_shell_3 to
same_process_hal_file like Pixels, but the partition is prebuilt thus
we're unable to relabel it.
* Copy the file to writable tmpfs, setup attributes and bind mount back
to workaround the limitation.
[ghostrider-reborn]:
Allow adsp/cdsprpcd and neuralnetworks HAL to access fastrpc_shell_3
[kras edit:
1. rename some contexts as per qva/kona
2. extend to allow camera HAL and VPP service to access it as well]
Co-authored-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Change-Id: Ide90e5c7307d413db5ece736e859559f06679545
Specifying avb=<vbmeta-partition> is only necessary for first entry of
partition groups that use same vbmeta partition. The following entry can have
<vbmeta-parititon> part omitted.
Test: None
Link: https://source.android.com/devices/architecture/kernel/mounting-partitions-early#fstab-entries
Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: I5a42fd3de72c400acfae56d6a1e1b85c22a79537
Required to retrieve MAC addresses and save them somewhere in /data/vendor
so stock QTI Bluetooth HAL can read and set correct one, otherwise the HAL
will set a randomized one that always starts with ff:dd.
cnss-daemon isn't affected since nv_mac will write directly to
/mnt/vendor/persist/wlan_mac.bin to be read by WLAN driver.
Signed-off-by: Albert I <kras@raphielgang.org>
Change-Id: I2d95de397c3bab9e3c55171bf0ff833346bef32e
/dev/hw_random should be readable by system_server for EntropyMixer to
be able to use it.
Bug: http://b/179086242
Test: adb shell logcat | grep Entropy
Test: android.permission.cts.FileSystemPermissionTest#testDevHwRandomLockedDown
Change-Id: I7dd7faf300f5ce3cab8d02c69be7915238cf61da
