Bug: 36367381
Test: Boot and check stune configuration effect on sysfs
Change-Id: I838c31d164684a5d88550c92284b65bb50f2ed56
Signed-off-by: Andres Oportus <andresoportus@google.com>
Signed-off-by: Arian <arian.kulmer@web.de>
* The following things are left in devices, because they're device specific
- voip compress properties
- HVDCP properties
- audio configs
- power profile
- rounded corner configuration
- partition configuration
- FOD
- camera motor
- NFC
- board-info
- fstab
- ipa and graphics firmware
- shipping and manifest target level
Co-authored-by: Adithya R <gh0strider.2k18.reborn@gmail.com>
Co-authored-by: Arian <arian.kulmer@web.de>
Change-Id: I8bef29041f8f239361b999fc8ab1a43cc2ebb86b
Add owners for new lcd brightness and max_brightness node
/sys/class/backlight/panel0-backlight/brightness
/sys/class/backlight/panel0-backlight/max_brightness
Change-Id: I939ed22dc880a3536d95b397dbc7bed9288bc5df
Change ownership of UFS RPMB bsg node so that TZ RPMB service
can open this node without root permissions.
Change-Id: I285e2ae26094677d91ad8486457af86e7aaabbb9
Disabling UFS clock scaling during boot time helps in reducing
IO delays, which helps in reducing the total boot time.
This change will disable UFS clock scaling during early-init and
enable it back after boot completion.
Change-Id: Ib3490a8155610aea399ac2f63aa4a71bee299c6e
Mount of tracefs in /sys/kernel/debug/tracing will fail when DEBUG_FS
is disabled. So, mount tracefs in /sys/kernel/tracing to still use all the
tracing abilities when CONFIG_DEBUG_FS is disabled
Change-Id: Ib37332c3f1108d7c4798717f0f009c891db72850
This changes removes tftp and rmt storage service definitions
from main .rc file as these services are defined in respective
local .rc files.
Change-Id: Ibbd1fda31b7fd950590d6a15b7aca3bb08d84f4b
move sensors specific boot up commands from global init.qcom.rc to component
specific rc files , which are part of individual component projects.
Change-Id: Ib0410cd0af8d77573bd320063982b504b1b1d1d5
add wakelock group and BLOCK_SuSPEND capabilities to vendor.sensors
to acess wake-lock sysfs nodes
Change-Id: I193836d097f15f5bfbe1645909ae70f3f870f972
Make charger binary run as system instead of root. Since it
needs to handle input key events, add input as a supplemental
group in addition to system and graphics.
Change-Id: Id1dc46f335087147b7d8cf674664c26f0b511de1
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
