If your app is being downloaded by other people and crashing on remote devices, you may want to look into an Android error reporting library (referenced in this SO post). If it's just on your own local device, you can use LogCat. Even if the device wasn't connected to a host machine when the crash occurred, connected the device and issuing an adb logcat command will download the entire logcat history (at least to the extent that it is buffered which is usually a loooot of log data, it's just not infinite). Do either of those options answer your question? If not can you attempt to clarify what you're looking for a bit more?

We use our home-grown system inside the company and it serves us very well. It's an android library that send crash reports to server and server that receives reports and makes some analytics. Server groups exceptions by exception name, stacktrace, message. It helps to identify most critical issues that need to be fixed. Our service is in public beta now so everyone can try it. You can create account at http://watchcat.co or you can just take a look how it works using demo access http://watchcat.co/reports/index.php?demo.

我一直在Android和iOS应用中使用cratercism——我在techcrunch上听说过它们。到目前为止，他们都很满意!

Flurry analytics为你提供崩溃信息、硬件型号、android版本和实时应用使用统计数据。在新的SDK中，他们似乎提供了更详细的崩溃信息http://www.flurry.com/flurry-crash-analytics.html。

使用这个来捕获异常细节:

String stackTrace = Log.getStackTraceString(exception); 

保存在数据库中，并维护日志。

有一个叫做fabric的工具，这是一个崩溃分析工具，它可以让你在应用程序实时部署和开发期间获得崩溃报告。 将这个工具添加到您的应用程序也很简单。 当应用程序崩溃时，可以从fabric查看崩溃报告。IO仪表盘。THW报告被自动捕获。它不会询问用户的权限。他/她是否想要发送错误/崩溃报告。 这是完全免费的… https://get.fabric.io/