crda sends wifi regulatory settings to driver through netlink
socket which requires root preivilege to run.
Change-Id: Ib68f0cb895e7e5a255608afe731a84e063dbd7ed
Dynamically enabling the hcidump logs when the property
bluetooth.hcidump.enabled=true is set. By default this property is
not set.
CRs-fixed: 323983
Change-Id: I127a638c17fb8447f8b9a1472c7a9270ef0bad84
During initialization the system partition needs to be
remounted as read-write in order for changes to be made
to the /system partition (e.g. creating target-specific
symlinks, etc.). Earlier this was done in the post-fs
stage where Android property service has not been
initialized. This change moves these initializations to
the early-boot stage.
Update the wifi initialization script to use command
line parameters since getprop is not yet available in
early-boot. Also fix bug in 8974 changes that breaks
8960 and other targets.
Call audio init script from wifi script rather than
directly from syspart-fixup since retrieving Android
property is not yet available.
TODO: Init sequence needs to be redone for cleanup
and boot up speed.
Change-Id: I2a7338af91df951d0a4617d4f54db123aca839e3
Move system property settings such as LCD density to early-boot.
This ensures the properties are set before any service is
started.
CRs-Fixed: 390942
Change-Id: Iba5dfb5b55f33904bd09d4b618b5399d7bda8cbd
Audio subsystem has to read the qcom.bluetooth.soc property
to create the correct soft links in UCM files which will
be read by HAL.
Change-Id: Iaf5ac39578dae2ebd09b19733c1cc2768b4fd1e8
Some of the qcom services require to remount system partition with read-write
permission. But since all of them running as independent asyncronous services
so this can cause some issue.
init.post_fs.sh is responsible to call all such services syncronously and
in the end remount system partition as read-only.
Change-Id: I4c03a67df5eb429b2ede633f81135e8b5c457673