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

..

connect.cpp

Directly communicate with Activity

2019-04-10 23:35:31 -04:00

pts.cpp

Clean/refactor includes

2019-02-10 03:57:51 -05:00

pts.h

Fix SIGWINCH never followed

2018-11-20 04:40:42 -05:00

su_daemon.cpp

Modernize database code (again)

2019-03-06 08:16:12 -05:00

su.cpp

Use our own function to parse int

2019-03-07 20:31:35 -05:00

su.h

Modernize database code (again)

2019-03-06 08:16:12 -05:00