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
..
src/main	Directly communicate with Activity	2019-04-10 23:35:31 -04:00
.gitignore	Separate backend logic from frontend UI	2018-12-13 04:35:50 -05:00
build.gradle	Update dependencies	2019-04-10 05:17:03 -04:00
proguard-rules.pro	Use R8 full mode	2019-04-02 16:32:40 -04:00