I think the suggeston was that the same call to native code accomplish the antipiracy check and some critical part of application functionality.
But I'm not sure that native code is any harder to patch, and there are still identifiable syscalls or calls back up to java for i/o to show where it tries to accomplish verification. On Aug 24, 10:15 am, Hugo Visser <botte...@gmail.com> wrote: > No, that won't do it, since the entry point is always Java / Dalvik > byte code. Since you can decompile and patch that with relative ease, > you can just make the native calls to the crc check library no-ops or > whatever and you're done without patching any native lib. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
