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
..
jni	Directly communicate with Activity	2019-04-10 23:35:31 -04:00
src/main	Full project restructuring	2019-01-30 03:10:12 -05:00
.gitignore	Support Android Q new init setup	2019-03-03 06:35:25 -05:00
build.gradle	Add entrypoint to build test	2019-04-01 02:46:09 -04:00