I tried looking up that "no vspace available" error (which is the real error message) and found no explanation. I wonder whether it's something like trying to map a .so segment as memory that's both executable and writeable but it's no longer allowed? And IIRC Android's runtime linker was rewritten sometime around Android ~4 because the original was not very well written, so that might be the cause of the incompatibility. Come to think of it, the large parts of libc that were also completely replaced (mostly with code from OpenBSD and FreeBSD IIRC) because they were terribly buggy will probably cause compatibility issues too.