Receipts for a Flaky APK: Capture an Android Bug Report Before You Wipe Anything
A sideloaded app crashes the moment you hit export. You reinstall it, it works once, then it dies again. You message the developer, and their first reply is always the same: “Can you send logs?” By then you’ve uninstalled it twice and the evidence is gone.
Android has a built‑in evidence locker: the bug report. One button in the power menu snapshots system logs, crash traces and device state into a zip, right after the failure, with nothing extra to install. My rule for anything I sideload, my own Byteslip builds included: crash → capture → then troubleshoot. Never the other way around. (Pixel Phone Help 6398243 covers the Bug report shortcut and Power + Volume up.)
When a Screenshot Isn’t Enough
- Screenshot is fine for layout glitches, wrong text, or a clear error message on screen.
- Take a bug report when the app crashes or closes itself, freezes (“isn’t responding”), drains battery, loses its network connection, or only breaks sometimes. The cause of those is in the logs, not on the screen.
- Take both when you’re reporting to someone else: the screenshot shows what happened, the report shows why.
What You Need
- Developer options enabled (two minutes, steps below).
- A repro: the exact taps that make the APK fail. Write down the time it happens. It makes finding the crash in a huge log far easier.
- Somewhere private to stash the zip first: your own Drive or a folder on the phone.
- No third‑party apps required to capture.
Grab the Receipts
Step 1: Become a developer
Settings > About phone → tap Build number 7 times. Do this before the next crash, because you won’t want to be hunting for it mid‑bug.
Step 2: Enable Bug report shortcut
Settings > System > Developer options.
Turn on Bug report shortcut. (Pixel Help for support cases also mentions USB debugging. Only enable that if someone actually asks.)
Step 3: Reproduce, then capture fast
Make the APK misbehave, then press and hold Power + Volume up until the power menu appears → tap Bug report.
Wait for the “bug report ready” notification (Pixel Help: it can take around 2 minutes, and the phone may vibrate). Keep using the phone normally while it builds.
Alternate: Developer options → Take bug report / Bug report if the power‑menu item isn’t there.
Step 4: Share it on purpose, then lock up
Tap the notification to share. Save it to your own Drive or files first, then decide who gets it. Don’t fire it straight into a public chat.
When you’re done collecting receipts: Developer options → turn off Use developer options.
Samsung Galaxy
Enable Developer options the same way (Build number). Bug report shortcut and Take bug report live under Developer options. Whether it shows in the power menu depends on your One UI version. Search Settings for Bug report if you can’t find it.
What’s in the Zip (and Why Not to Email It Blindly)
- A giant text log (the
bugreport‑….txtinside the zip) with system and app logs from around the time of the crash. That’s where the developer looks for the stack trace. - Crash and freeze traces plus a snapshot of system services and device state.
- Your stuff: installed apps list, account names, Wi‑Fi network names, device identifiers, and bits of app and notification activity. Treat it like handing over an unlocked phone for a few minutes.
Privacy rule: send it only to a developer or support team you trust, and privately: email or a direct file share, never a public GitHub issue or Discord channel. If a dev wants it public, offer to paste just the crash lines instead. Turn Developer options off afterward if you don’t need them.
Next moves: receipts first, then prove who’s guilty with Safe Mode. If you’re comfortable with a computer, USB debugging lets you pull the same report with adb bugreport straight to your desk.
Capture Within a Minute
Official docs
Pixel: Send feedback about your Pixel to Google (bug report shortcut). Samsung: enable Developer options via Build number (ANS10003430); Bug report shortcut is under Developer options on One UI.