How to Report Bugs & Send Feedback on Android Beta

Reporting bugs and sending feedback on Android beta software helps developers fix issues before the final release. This guide shows you how to submit clear, useful reports directly from your device or via the web, and what to do if your report doesn’t go through.

What You’ll Need

An Android device enrolled in the beta program (e.g., Android Beta for Pixel or a manufacturer’s beta).
A Google account (for the Android Beta community and feedback forms).
Access to the device’s Settings app and, ideally, a stable internet connection.
Optional: The exact steps to reproduce the bug and any screenshots or screen recordings.

Step-by-Step

Reproduce the bug. Before reporting, try to trigger the issue again. Note the exact steps you took, what you expected to happen, and what actually happened. This information is critical for developers.
Use the built-in feedback tool (recommended). On most Android beta versions, go to Settings > About phone (or About device), then tap Send feedback about this device (or similar). This opens a form pre-filled with your device model, Android version, and build number—essential details for the report.
Describe the issue clearly. In the feedback form, write a concise title (e.g., “Wi-Fi disconnects after screen off”) and a detailed description. Include:
- Steps to reproduce (numbered).
- What you expected to happen.
- What actually happened (including any error messages).
- How often it occurs (always, sometimes, rarely).
Attach screenshots or screen recordings. Use the paperclip or camera icon in the feedback form to attach files. If the bug is visual, a screenshot is very helpful. For crashes or animations, a short screen recording (using the built-in screen recorder) is even better.
Include system logs (for crashes). If the app crashes, the feedback tool often includes a “Send system logs” checkbox. Make sure it’s checked. If not, you can capture logs manually using the Android Debug Bridge (ADB) on a computer—but that’s advanced and optional.
Submit the report. Review your report for clarity and completeness, then tap Send. You’ll usually get a confirmation that your feedback was submitted.
Use the web form (alternative). If the built-in tool isn’t available, go to the Android Beta Feedback page (search for it) and sign in with your Google account. You’ll need to select your device and enter the same details as above.
Post in the community (for broader issues). For general questions or to see if others have the same issue, visit the official Android Beta community (e.g., the Google Issue Tracker or the Android Beta Reddit). Search before posting to avoid duplicates.

Common Mistakes

Vague descriptions. “App crashes” is unhelpful. Always include steps to reproduce and what you were doing.
Omitting device info. Without your build number and device model, developers can’t match the bug to a specific variant.
Reporting duplicate issues. Search the feedback channel first. Duplicates waste time and can dilute attention.
Not attaching logs. For crashes, logs are often the only way to find the root cause.
Using the wrong channel. Don’t use a Play Store review to report a beta bug—use the designated feedback tool.

Tips

Be specific about timing. Mention when the bug started (e.g., after the latest update, after installing a certain app).
Use bullet points. In the description, break down steps and observations into a list—it’s easier to read.
Include screenshots of error messages. Text can be mistyped; a screenshot is exact.
Check for workarounds. If you found a temporary fix, mention it—it can help others and hint at the cause.
Keep a copy of your report. If you want to follow up, you’ll need the details.

Troubleshooting

If the feedback tool doesn’t open or crashes: Try restarting your device, then go to Settings > Apps > See all apps > (three-dot menu) > Show system > find “Google Play services” or “Feedback” and clear its cache. If that fails, use the web form.

If your report doesn’t submit: Check your internet connection. The form may also fail if you’re not signed in to a Google account on the device. Sign in, then retry.

If you can’t find the “Send feedback” option: On some devices, it’s under Settings > System > About phone, or in the “Tips & support” app. Search your Settings for “feedback” to locate it.

If you think your report was ignored: Reports are reviewed in bulk, not individually. You won’t get a personal reply. Check the issue tracker or community to see if others have reported the same thing—if so, add your voice there.

Frequently Asked Questions

Q: Do I need to be rooted to report a bug?
A: No, the built-in feedback tool works on stock, non-rooted devices.

Q: Can I report a bug in a third-party app?
A: Yes, but it’s better to report it to the app developer directly. The beta feedback tool is mainly for system issues.

Q: How long until my bug is fixed?
A: It varies. Some bugs are fixed in days, others take weeks or months, and some are never fixed. The beta program’s purpose is to catch issues before release.

Q: Will I get a response?
A: Generally no. The feedback system is one-way. If you need interaction, post in the community or issue tracker.

Q: What if the bug is about a Google app like Gmail?
A: Use the in-app feedback option (usually in the app’s menu under “Help & feedback”) rather than the system feedback tool.

Q: Should I report a bug if I’m not sure it’s a bug?
A: Yes, report it anyway. It’s better to have false positives than to miss a real issue.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →