Logcat
Logcat is an Android debug logging framework that displays device logcat output directly in a floating window on the phone, eliminating the need for Android Studio or ADB connections. It integrates as a debug-only dependency (via JitPack) and requires no manual initialization or code changes.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | getActivity/Logcat |
| Owner | getActivity |
| Primary language | Java |
| License | Apache-2.0 — OSI-approved |
| Stars | 987 |
| Forks | 121 |
| Open issues | 1 |
| Latest release | 13.2 (2026-05-22) |
| Last updated | 2026-05-22 |
| Source | https://github.com/getActivity/Logcat |
What Logcat is
Java-based Android library (Apache 2.0) that intercepts and displays Logcat output via a floating-window UI. Deploys only in debug builds (stripped from release APKs), requires compileSdkVersion 34+, AndroidX, Gradle 7.4+, and JDK 1.8+. Latest version 13.2 is actively maintained and uses JitPack distribution.
Get the Logcat source
Clone the repository and explore it locally.
git clone https://github.com/getActivity/Logcat.gitcd Logcat# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Add JitPack repository URL to Gradle configuration (settings.gradle for Gradle 7.0+; build.gradle for earlier versions).
- Declare debugImplementation dependency only; library automatically activates on debug builds and requires no onCreate() calls or initialization code.
- Ensure compileSdkVersion is set to 34 or higher; projects using older Support libraries should migrate to AndroidX first.
- Request floating-window permissions in AndroidManifest.xml or handle runtime permission grants; library displays a notification entrance for user access.
- Verify build fails with AAPT manifest <property> errors; if so, upgrade Gradle to 7.4+ and Android Gradle Plugin to 7.1.0+.
When to avoid it — and what to weigh
- Production or Release Builds — Library is designed strictly for debug mode and should never ship to end-users; confirm build configuration strips it from release APKs.
- Projects Below compileSdkVersion 34 — Requires SDK 34+; older projects must upgrade to use this version. Older version 12.5 supports Support library, but migration to AndroidX is recommended.
- Remote or Server-Side Log Aggregation — This is a device-side viewer only; it does not capture, upload, or centralize logs for backend analysis or long-term retention.
- Projects Unable to Upgrade Gradle/AGP — Requires Gradle 7.4+ and Android Gradle Plugin 7.1.0+; projects on older build tooling will encounter compilation errors without upgrade.
License & commercial use
Licensed under Apache License 2.0 (Apache-2.0), a permissive OSI-approved license allowing free use, modification, and distribution with proper attribution and liability disclaimers.
Apache 2.0 permits commercial use, including in proprietary applications, provided the license text and copyright notice are included in distributions. However, this is a debug-only library intended for development and testing, not shipping in production. Commercial users should confirm it is excluded from release builds and consider any liability implications of debug tooling in their apps.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Good |
| Assessment confidence | High |
Library requests SYSTEM_ALERT_WINDOW permission to display floating windows; users must explicitly grant this. As a debug-only tool, it does not execute in production, reducing attack surface. However, ensure debugImplementation scope is respected in build configuration; accidental inclusion in release builds would expose sensitive logs to end-users. No encryption or secure log storage is mentioned; logs are retained in-memory and can be copied/shared by the user.
Alternatives to consider
Android Studio Logcat (built-in)
Free, official, and no library integration needed; requires USB connection and development machine, which is impractical for remote/field testing.
Timber (Jake Wharton)
Lightweight logging facade with tag-based filtering and custom tree implementations; does not provide on-device UI, requiring external log capture tools.
Stetho (Facebook)
On-device Chrome DevTools inspection for Android; broader feature set for debugging UI and network, but heavier footprint and requires Chrome browser on host.
Build on Logcat with DEV.co software developers
Add Logcat to your debug builds today. Integrate in minutes with a single Gradle dependency—no code changes required. Ideal for QA, field testing, and rapid issue triage.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
Logcat FAQ
Will Logcat be included in my production APK?
Does this library require special permissions in AndroidManifest.xml?
Can I use this with Support library (pre-AndroidX) projects?
What Gradle and AGP versions are required?
Work with a software development agency
From first prototype to production, DEV.co delivers software development services around tools like Logcat. Our software development agency staffs experienced software developers and web developers for custom software development, web development, integrations, and ongoing support across open-source observability and beyond.
Ready to simplify Android debugging?
Add Logcat to your debug builds today. Integrate in minutes with a single Gradle dependency—no code changes required. Ideal for QA, field testing, and rapid issue triage.