Ok, so it's not working. The problem is not neon detection, it's the fact that the OS picks up OFAndroidLib.so for arm instead of x86. Meaning: the fix delays the crash, but doesn't prevent it.
Another hint: OF from 3 months ago doesn't crash! Perhaps some third party that was introduced/updated is incompatible with this? Or something changed in the compilation process?
The absurd thing is that the phone returns "armv7" for "os.arch", and not x86, so you can't really blame the OS for picking up arm...
One of the ways to resolve this is to figure out what is feature ID:0x20e00149.. and then understand where are we using that..
Another way I thought of is not counting on the OS for lib selection at all. Compile arm and x86 to different names and use x86 as fallback if arm loading as crashed (provided that this crash is catchable, or by detecting the architecture correctly somehow).
What do you think?
UPDATE: here's a post exactly on the issue. Works on x86 devices, but doesn't work on asus devices with the arm emulation. The solution involves "having the same set of libs names and numbers for each architecture". Not sure what is means... I tried looking through the libs to find any discrepencies between arm and x86 folders, and found only one - glu, that doesn't contain an x86 lib. Can it be related??