topjohnwu 8d4c407201 Directly communicate with Activity ... Since Android Q does not allow launching activities from the background (Services/BroadcastReceivers) and our native process is root, directly launch activities and use it for communication between native and app. The target activity is not exported, so non-root apps cannot send an intent to fool Magisk Manager. This is as safe as the previous implementation, which uses protected system broadcasts. This also workaround broadcast limitations in many ROMs (especially in Chinese ROMs) which blocks the su request dialog if the app is frozen/force stopped by the system. Close #1326		2019-04-10 23:35:31 -04:00
..
core	Don't allow cloning root nodes	2019-04-08 12:30:57 -04:00
external	Build libsqlite.so only with magisk	2019-03-07 05:21:27 -05:00
include	Use our own device nodes for mirrors	2019-04-08 01:40:04 -04:00
magiskboot	Update tools docs	2019-03-28 04:54:06 -04:00
magiskhide	Use our own device nodes for mirrors	2019-04-08 01:40:04 -04:00
magiskpolicy	Add logging in magiskinit	2019-04-04 00:26:16 -04:00
resetprop	Make parse prop file a util function	2019-03-05 20:27:09 -05:00
su	Directly communicate with Activity	2019-04-10 23:35:31 -04:00
systemproperties	Some code adjustments	2019-02-24 23:09:34 -05:00
utils	Add boot_complete trigger back	2019-04-05 07:00:30 -04:00
.gitignore	Add entrypoint to build test	2019-04-01 02:46:09 -04:00
Android.mk	Add entrypoint to build test	2019-04-01 02:46:09 -04:00
Application.mk	Use separate flags for 64-bit	2019-04-05 15:17:59 -04:00