Magisk/native/jni
topjohnwu e02e46d0fc Detect volume down key combo for safe mode
It is possible that a module is breaking the device so bad that zygote
cannot even be started. In this case, system_server cannot start and
detect the safe mode key combo, set the persist property, and reboot.

Also on old Android versions, the system directly goes to safe mode
after detecting a key combo without rebooting, defeating the purpose of
Magisk's safe mode protection if we only check for the persist property.

Directly adding key combo check natively in magiskd allows us to enter
Magisk safe mode before the system is even aware of it.
2020-05-19 04:57:47 -07:00
..
core Detect volume down key combo for safe mode 2020-05-19 04:57:47 -07:00
external Update BusyBox 2020-05-02 03:42:42 -07:00
include Don't expose module_list 2020-05-18 05:36:02 -07:00
init Detect volume down key combo for safe mode 2020-05-19 04:57:47 -07:00
magiskboot Revert DTB patches to in-place binary patches 2020-05-05 01:03:09 -07:00
magiskhide magiskhide: fix late_prop_key setprop, reorganize props slightly 2020-05-18 23:31:22 -07:00
magiskpolicy Add untrusted_app_29 for Android 11 2020-04-20 21:50:52 -07:00
resetprop Update resetprop to partially use system impl 2020-05-07 23:54:00 -07:00
su Make version reporting consistent 2020-03-23 01:17:13 -07:00
systemproperties Update resetprop to partially use system impl 2020-05-07 23:54:00 -07:00
utils Detect volume down key combo for safe mode 2020-05-19 04:57:47 -07:00
.gitignore Add entrypoint to build test 2019-04-01 02:46:09 -04:00
Android.mk Force remove AVB for 2SI since it may bootloop some devices 2020-05-05 03:29:36 -07:00
Application.mk native: fix slower build on non-Windows platforms 2020-05-09 04:41:07 -07:00