3 ms·
I have never seen anything but a native crash for drm code issues. I would be willing to bet some type of drm is still the problem here.
by bleah1000 6y ago
I have never seen anything but a native crash for drm code issues. I would be willing to bet some type of drm is still the problem here.
- mmastrac 6y agoUnfortunately based on some quick analysis it looks like there _was_ a change in JNI - previously JNI method handles were pointer-like and now they are opaque integers. Definitely not DRM in this case. Apps crash in the default mode. Hacking the device so that SetJniType is called with kPointer makes it all work. https://android.googlesource.com/platform/art/+/master/runtime/runtime.h#924 https://android.googlesource.com/platform/art/+/master/runti...