AppZygote: start with the correct instruction set
This allows triggering native-bridge initialization if needed. Test: CtsExternalServiceTestCases android.externalservice.cts.ExternalServiceTest testBindExternalServiceWithZygote for Q.sdk_gphone_x86_arm.armeabi-v7a Bug: 143143718 Change-Id: If105c4283879407c4fcee33fa6086772d43609a3
This commit is contained in:
@@ -21,6 +21,8 @@ import android.util.Log;
|
||||
|
||||
import com.android.internal.annotations.GuardedBy;
|
||||
|
||||
import dalvik.system.VMRuntime;
|
||||
|
||||
/**
|
||||
* AppZygote is responsible for interfacing with an application-specific zygote.
|
||||
*
|
||||
@@ -113,7 +115,7 @@ public class AppZygote {
|
||||
"app_zygote", // seInfo
|
||||
abi, // abi
|
||||
abi, // acceptedAbiList
|
||||
null, // instructionSet
|
||||
VMRuntime.getInstructionSet(abi), // instructionSet
|
||||
mZygoteUidGidMin,
|
||||
mZygoteUidGidMax);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user