LogKitty - Instant Debuggery

Your app just crashed. The stack trace is on a laptop across the room, attached to a cable you don't have.

LogKitty puts logcat on the phone itself: a floating overlay above the app you're testing, streaming live while the bug is actually happening. Watch the error arrive. Tap it. Find out why. Never leave the app.

ONE-TIME SETUP (ANDROID'S RULE, NOT OURS)

Android guards the system log behind the READ_LOGS permission, which no app can request with a normal prompt. Grant it once — LogKitty walks you through it on first launch:

• ADB: adb shell pm grant com.hereliesaz.logkitty android.permission.READ_LOGS

• Shizuku: tap "Grant with Shizuku". No computer

• Root: flip on Root Access

Until then, LogKitty can only show its own logs. On Android 13+, the system may also ask you to confirm.

A LOG THAT STAYS OUT OF YOUR WAY

• Collapsed, it's one line: the newest thing your device said

• Pull it to half or full screen to scroll and read stack traces

• It steps aside on the home screen

• Tune opacity, text size, font, colors and order until it disappears into your workflow

FIND THE LINE THAT MATTERS

• A tab per app, filtered by that app's user ID — not by guessing at tags

• Context Mode follows whichever app is on screen and filters to it (Usage Access or root)

• Follow Debug App: pick an app in Developer options → Select debug app, and its tab opens

• Filter by level, tag or keyword. Banish noisy tags forever

• Long stack traces fold to a few frames; one tap opens the rest

• When a monitored app crashes, its log opens on its own, already on the right tab

TRACE THE BUG

• Tap any line for a diagnosis: what it means, why it usually happens, how to fix it, and the surrounding lines as evidence. Built-in explanations for NullPointerException, OutOfMemoryError, ANRs and network failures; everything else gets a read of its context

• One tap narrows a tab to Crashes, Errors, Warnings, Network, Memory or ANRs

• Context Mode keeps a timeline of what was on screen, so you can see what happened right before it broke

READ YOUR OWN CRASHES, UNSCRAMBLED

• Load your R8/ProGuard mapping.txt and obfuscated traces come back with real class, method and line names — live

• Load your unstripped .so files or native-debug-symbols.zip and native crash frames name their functions

• With root, the full native crash report (tombstone) is saved with your session logs

SEE WHAT IT COSTS (OPTIONAL DEVELOPER STATS)

Without root: crash and ANR history for the app you're watching. With root: CPU per thread, memory, GPU frame timing and live network connections. If the device won't tell, LogKitty says "unavailable." It doesn't make numbers up.

FIND THE BATTERY DRAIN (ROOT)

Who's keeping the phone awake: the app's wake locks ranked by how long each was held, its scheduled jobs and alarms and the components behind them, and any sensor or location request it forgot to let go of — with battery level, temperature and charging state alongside. Requires root; without it, this section shows as unavailable.

KEEP THE EVIDENCE

• Copy a line or a whole section to the clipboard

• Save logs to files you can read later, offline

• Per-app session logs that clean themselves up on a schedule you choose

PRIVATE BY DESIGN

Your logs stay on your device. No accounts, no analytics, no server — LogKitty never uploads anything you capture. Logs can contain personal data that other apps write into them, so share saved logs with care.

FOR PEOPLE WHO SHIP

Built for Android developers, QA testers and power users who know ADB, Shizuku or root. If those words mean nothing to you, LogKitty isn't for you yet. If they do: unplug the cable.