Android mobiles have many moving parts and it is inevitable that sooner or later there will be problems with the system or some applications. To properly report bugs and errors, the most common method is to create an error report and share it with the technical department of said application or mobile.
If you have ever experienced crashes or other app issues, chances are the app developers will ask you to send them a bug report. Below we explain what these Android error reports are, what they contain and what you can do with them.
What is an Android bug report
Bug reports are a useful resource for app developers to have a “snapshot” of what happened to their app on a mobile where it crashes. It’s often supplemented with a LogCat snippet, which is like a log of what’s happening on mobile.
The LogCat includes many clues about what is wrong with a mobile, but it may not be enough to diagnose a complex error. An error report provides more information, incorporating logs, stack traces, and more diagnostic information. As a user, you generally should not pay too much attention to it or create an error report, unless at some point you want to help solve an error that occurs with your mobile.
Content of a bug report
Some of the files contained in a bug report
Bug reports are basically a ZIP file containing a set of files corresponding to different diagnostic information, to which the creating user can optionally attach screenshots and a description. A normal report can be around 100 MB and contain around 400 files.
The files are mostly in TXT format, so they can be opened with any text editor, although reading a bug report is rocket science. The reports include many recordings of applications running on mobile and, although not usual, they may contain sensitive information. Android itself will remind you to only share them with users and apps you trust.
How to file a bug report on Android
There are several ways to file an Android bug report, although all of them require you to enable Developer Options. This is precisely where you will find the button to create a report, pressing Report an error. Then you have to choose if you want it to be an interactive report or a full report.
The main difference is that the interactive report will allow you to add a screenshot and descriptive text, if you tap on the notification that appears during the creation process. The full report takes longer to create and does not display a notification when it is created, so you cannot add more details or screenshots to it.
When the reports are ready, tap on their notification to open the Android share menu, from where you can send them to any app that supports sending ZIP files. If you report a bug, you will most often be asked to send it via email, but this can also be done via Telegram or similar apps.
If you prefer, you can also file a bug report using ADB commands. In this case, you have the possibility of obtaining the report directly on your PC, by using the command adb bugreport C:\MyBugReports. If you don’t specify a path, it is saved in the mobile’s bugreports folder.