Two fstabs are needed to support different data unit
number (dun) size for ufs and emmc hardwares. This
needs different encryption flag in fstab to address
the difference in dun size.
Change-Id: Ifb0e9132fc91e3281401ac49ad70c695a22c9df5
* Enabling the services allows them to start at their proper stage (class main)
* Enable them on boot to ensure they are enabled before class main starts
Change-Id: I71c3fcb72b38d247d304fda2fa6b2cc76baa0db2
* These modules are disabled by default and started by
init.class_main.sh which we do not ship. Start them from init.qcom.rc
on post-fs-data instead, just like qcrild.
Change-Id: Ifa907b5e33d8d3d08e64baaabfb8e3e450925e96
This reverts commit 867af09b6b.
* The boot_completed settings are the default settings already
and switching the settings while booting does not bring a
noticeable improvement.
Change-Id: I7a61e2fa8558b074d5c3d7b19c548b4fde00d918
* Xiaomi adds the audio_hw_socket here, but it needs
their changes in the audio HAL, hence it's useless
for us.
Change-Id: Idf38468ad709623b60b694f458e71d0565ce6fb6
* missed in commit:
66573bbfea
davinci: Drop SSR blobs and set SSR restart_level in init.qcom.rc
Change-Id: I32fc08c9ad36b9c8ebfc019fc87a19eece18f0b4
Change-Id: I5078d9579e894c0b1a7b30a2984b1ba096843e0e
* Setup davinci sku when device is global or chinese.
* Move the nfc manifest entry to davinci hardware sku
variant.
Change-Id: I76ac75cd80f85efa6dfa68753602d934a11000a3
Signed-off-by: Arian <arian.kulmer@web.de>
-Set max_comp_streams to num of cores since upstream also moves this to
percpu.
Bug: 38249616
Test: boot and run zram-perf showing better performance
Change-Id: I0b92b246d773db85aa03d033b2cecee54347cbd1
This addresses an underlying problem since /dev/hw_random is used. The
issue is that EntropyMixer, which runs in system_server, needs to read
from /dev/hw_random, but thanks to our qualcomm ueventd, EntropyMixer
can never accress this node, resulting in warnings like this:
W EntropyMixer: Failed to add HW RNG output to entropy pool
W EntropyMixer: java.io.FileNotFoundException: /dev/hw_random (Permission denied)
AOSP ueventd handles this well, so just remove this line to get things
back to stage. This issue was never exposed because Google derps the
logging here, which is already fixed on Pie.
c78a463e87
Change-Id: I42c9aaa8f57306536e51c0a17febad57a5a77581
* Don't enable adb
* Actually mount persist
* Don't split on charger to init.qcom.rc and init.target.rc
Change-Id: Ia4d6d1e417056a6b87358e384bd7a0bedcca1d63
