The reason these files are moved to /vendor/etc/init/hw and
not /vendor/etc/init is because 'init' scans the /vendor/etc/init folder
for vendor service .rc fragments to import. That would either result
in duplicate imports or out-of-order imports of these hardware
specific .rc files and that *may* have unintended consequences.
In order to preserve the current import order for MTP, we move all
hardware specific .rc files to /vendor/etc/init/hw which is not
autoscanned by init BUT leave the init.${ro.hardware}.rc (i.e.
init.qcom.rc in this case) in root for 'init' to find.
Change-Id: I14531da05e2a3a256f734f8de96e1f1969c753f9
* Merge init.target.rc into init.qcom.rc
* Re-organise init triggers based on actual init sequence
* Clean up a little bit of whitespace
* Remove services for daemons not even present in stock
Change-Id: I6682040cfbc2aabe3886bd64f4277cc99172a7bf
This makes it such that we can be more versatile in applying
our power configuration (recovery, different init triggers, etc.)
This will not be included in init.qcom.rc until this is verified.
Change-Id: I3a721ee8f31129f80662c752c370e951a4f80c38
