From a0ec9dc8c8a6ff52a131bb40c381f64811b189ef Mon Sep 17 00:00:00 2001 From: Michael Bestas Date: Sun, 17 Jun 2018 18:47:00 +0300 Subject: legacy: Add rules for init.qcom.bt.sh * Turns out we need to use init.qcom.bt.sh instead of running hci_qcomm_init directly, as that causes BT to take longer than 10 seconds to enable on first time it's enabled after boot Change-Id: I0ee4a645d3828429b2deb0464f78090f49c9eb7b --- legacy-common/bluetooth_loader.te | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/legacy-common/bluetooth_loader.te b/legacy-common/bluetooth_loader.te index 6b5837c..b969bdc 100644 --- a/legacy-common/bluetooth_loader.te +++ b/legacy-common/bluetooth_loader.te @@ -4,8 +4,15 @@ type bluetooth_loader_exec, exec_type, file_type; # Started by init init_daemon_domain(bluetooth_loader) -# Get persist.service.bdroid.*, bluetooth.* and wcnss property values -get_prop(bluetooth_loader, bluetooth_prop) +# Execute init.qcom.bt.sh +allow bluetooth_loader qti_init_shell_exec:file entrypoint; + +# Run hci_qcomm_init and log without changing domain +allow bluetooth_loader bluetooth_loader_exec:file execute_no_trans; +allow bluetooth_loader vendor_toolbox_exec:file execute_no_trans; + +# Set persist.service.bdroid.*, bluetooth.* and get wcnss property values +set_prop(bluetooth_loader, bluetooth_prop) get_prop(bluetooth_loader, wcnss_prop) # Access the serial device -- cgit v1.2.3