Finally managed to track this one down. I had a few hoops to jump through to get the ndk-gdb debugger to attach to the app process - I had to add a Thread.sleep in the java activity for a couple seconds to give the debugger time to attach before it crashed.
Anyhow it was due to a module that has an issue with JUCE on Android - danlin's FontAwesome wrapper module.
Thank you for sending me your stack trace. In deed, the problem is that danlin's FontAwesome wrapper is calling juce::Typeface::createSystemTypefaceFor before JUCE is fully initialized. This is because juce::Typeface::createSystemTypefaceFor is called from the static initializer of a global instance of FontAwesomeHelperhere. This is another example of why it is bad to have global variables. It is better to replace this with a singleton object. You can use juce_DeclareSingleton and friends for this (modules/juce_core/memory/juce_Singleton.h).