On API levels lower than 16, the two unwind methods we use (libcorkscrew and libunwind) are not present, so we default to our own simple unwinder.
Currently, the simple unwinder is only able to capture the top-most frame in a crash. If you notice this for a crash report coming from a device between API 16 and 22, the crash could be happening in a very inlined context.
To verify if you’re seeing full crash info on your dashboard, open the device logcat containing the tombstone of the native crash. If there’s a mismatch of information, please reach out to us at email@example.com.