Is it the JVM throwing incomprehensible stack traces? Or is it the android SDK throwing slightly less but still uselss stack traces? I often see the later, wh

Is it the JVM throwing incomprehensible stack traces? Or is it the android SDK throwing slightly less but still uselss stack traces? I often see the later, which is just poor error/exception handling by the developers. I very rarely (sometimes, but not enough to get annoyed) see the JVM printing out stack traces.