In the second stage of Native Bridge initialization, it becomes process-specific. Native Bridge can be used by an Android application to load a native library in a different processor architecture than the current device. The other two states, kPreInitialized and kInitialized, are related to the creation of Android applications, as we know that all applications are forked from Zygote in Android. Let's look at the pre-initialization of Native Bridge first, as shown in the following diagram:
Pre-initialization of Native Bridge
During the creation of an application, the ForkAndSpecializeCommon function is called. ...
