Forums - Android 10, ADSP, and .so permissions failures

Using NP SDK 1.36, Android Studio 3.6 in August 2020, I was able to build and execute machine learning code using NDK with a custom-written JNI, by setting ADSP_LIBRARY_PATH exactly as per the instructions at https://developer.qualcomm.com/docs/snpe/dsp_runtime.html (section "For Android APKs").

Using NP SDK 1.36, Android Studio 4.0 today, testing on a Samsung A70 and a Samsung S8, it seems that the DSP .so libs expect to be able to spawn command shells and such, and it fails. My hypothesis is that as per https://developer.android.com/about/versions/10/behavior-changes-10, untrusted apps can no longer execute code out of the native library dir (that is only my best guess at this point).

In my JNI layer, I can execute zdl::SNPE::SNPEFactory::getLibraryVersion() no problem, which means libSNPE.so is loaded and aceessible. However, even after setting ADSP_LIBRARY_PATH as per the Qualcomm recommended method, the call to zdl::SNPE::SNPEFactory::isRuntimeAvailable(zdl::DlSystem::Runtime_t::DSP) creates a litany of logcat spew in my unit tests (and returns false) (see below)

I do not use the snpe-release.aar package because our application is native code, we expose our native APIs to Java via JNI.

Is there a way to have our native libXYZ.so depend on libSNPE.so and all the SNPE DSP libs, while using snpe-release.aar and platform-validator.aar to deliver the SNPE so files, or is that a recipe for disaster?

Any concrete guidance welcome.

Logcat when running on Samsung A70 with Android 10 (Snapdragon 675):