topjohnwu 80cd85b061 Try to use broadcast for su logging and notify ... In commit 8d4c407, native Magisk always launches an activity for communicating with Magisk Manager. While this works extremely well, since it also workaround stupid OEMs that blocks broadcasts, it has a problem: launching an activity will claim the focus of the device, which could be super annoying in some circumstances. This commit adds a new feature to run a broadcast test on boot complete. If Magisk Manager successfully receives the broadcast, it will toggle a setting in magiskd so all future su loggings and notifies will always use broadcasts instead of launching activities. Fix #1412		2019-05-13 02:01:10 -07:00
..
applets.cpp	Use wrapper script on system with APEX	2019-04-03 17:25:47 -04:00
bootstages.cpp	Try to use broadcast for su logging and notify	2019-05-13 02:01:10 -07:00
daemon.cpp	Try to use broadcast for su logging and notify	2019-05-13 02:01:10 -07:00
db.cpp	Try to use broadcast for su logging and notify	2019-05-13 02:01:10 -07:00
init.cpp	Add hi6250 support	2019-05-05 11:45:21 -07:00
magisk.cpp	Try to use broadcast for su logging and notify	2019-05-13 02:01:10 -07:00
magiskrc.h	Remove requirement to use early-init daemon	2019-04-24 00:13:48 -04:00
scripting.cpp	Add boot_complete trigger back	2019-04-05 07:00:30 -04:00
socket.cpp	Separate scripting code	2019-02-15 20:45:05 -05:00