Timeline for How to determine the boot order of auto-starting apps?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 10, 2021 at 9:31 | answer | added | Crow | timeline score: 0 | |
| Mar 4, 2021 at 4:53 | comment | added | Irfan Latif | The only exception is that if you are using Magisk to bind mount Xposed modded files (and not actually replacing them in filesystem) and bind mount is delayed on boot so that an app is started before that. But this should not happen technically since Magisk is loaded very early in boot process. | |
| Mar 4, 2021 at 4:52 | comment | added | Irfan Latif |
Andoid fires ACTION_BOOT_COMPLETED broadcast once system_server is fully up on boot. Any app with android.permission.RECEIVE_BOOT_COMPLETED can receive the broadcast and start a service or whatever. There's no boot order that Android defines. // As Robert said, Xposed replaces core framework libraries in /system. So whenever zygote forks an app, it's loaded with modded libraries.
|
|
| Mar 3, 2021 at 19:36 | comment | added | Robert | If Xposed is installed then the initial Dalvik VM instance "Zygote" is altered in the boot process. Every app that is started forks the Zygote process and thus includes Xposed. This is my understanding of how Xposed works. Therefore it should be impossible for an app to start before Xposed. May be this is a timing problem in the boot process? What device do you use and how have you installed Xposed? | |
| Mar 3, 2021 at 15:05 | history | asked | Zirui Wang | CC BY-SA 4.0 |