The android Compatability Defination Document has no requirements on any native executables being present. However, in practice they are because nobody has any reason to remove them.
I'd suspect that the /system/bin/am utility would be a slightly safer bet, seeing as it is basically a command line interface for intents, but then again I suppose it would be an easier binary for some device maker to remove than dalvikvm, so It's hard to be sure. On Feb 5, 1:53 pm, Jin Chiu <[email protected]> wrote: > Can I rely on dalvikvm to be reliable on all Android devices? I would > like to use it to send an intent from a native component, which due to > legacy design, does not have access to a JNI context. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en

