Closed Hedda closed 8 years ago
This should not effect MrMC as it does not dyload any private Android libs. App bundled dynamic libs are not restricted, only private Android libs. This change is aimed at Apps that access private Android API through direct dyloading.
FYI, not sure if this behavioral changes regarding dynamically linking in Android "N" (7.0?) will directly affect MrMC/SPMC/Kodi as is, but as it could so please read;
http://android-developers.blogspot.se/2016/06/improving-stability-with-private-cc.html
and
https://developer.android.com/preview/behavior-changes.html#ndk
NDK Apps Linking to Platform Libraries
Starting in Android N, the system prevents apps from dynamically linking against non-NDK libraries, which may cause your app to crash. This change in behavior aims to create a consistent app experience across platform updates and different devices. Even though your code might not be linking against private libraries, it's possible that a third-party static library in your app could be doing so. Therefore, all developers should check to make sure that their apps do not crash on devices running Android N. If your app uses native code, you should only be using public NDK APIs.