DEV.co
Open-Source Observability · F0x1d

LogFox

LogFox is an Android logcat reader application built in Kotlin that allows developers to capture, filter, and export device logs. It supports multiple access methods (Shizuku, root, ADB) and includes crash/ANR detection with notifications.

Source: GitHub — github.com/F0x1d/LogFox
1.2k
GitHub stars
63
Forks
Kotlin
Primary language
GPL-3.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
RepositoryF0x1d/LogFox
OwnerF0x1d
Primary languageKotlin
LicenseGPL-3.0 — OSI-approved
Stars1.2k
Forks63
Open issues16
Latest releasev2.1.10-79 (2026-03-01)
Last updated2026-06-25
Sourcehttps://github.com/F0x1d/LogFox

What LogFox is

A Kotlin-based Android tool for real-time logcat monitoring with filtering, log recording to ZIP archives, Java/JNI crash detection, and Material You UI. Requires ADB, root, or Shizuku for elevated log access.

Quickstart

Get the LogFox source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/F0x1d/LogFox.gitcd LogFox# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Android App Debugging in Development

On-device logcat reader eliminates need for desktop ADB setup; useful for rapid iteration, field testing, and crash triage during development cycles.

Crash & ANR Monitoring

Built-in detection of Java/JNI crashes and ANRs with notification support enables developers to catch issues in real time without external monitoring infrastructure.

Log Export & Device Diagnostics

Recording and ZIP export with device info facilitates bug reporting workflows and remote diagnostics when users report issues in production.

Implementation considerations

  • Kotlin/Android expertise required; not applicable to non-Android projects or backend systems.
  • Access method (ADB, root, or Shizuku) must be available in target deployment environment; Shizuku requires additional system compatibility.
  • GPL-3.0 license applies to any distribution or modification; internal use for testing has fewer obligations, but any redistribution requires source release.
  • No indication of multi-device or networked log aggregation; suitable only for single-device or local debugging.
  • Latest release (v2.1.10-79, Mar 2026) and recent commits (Jun 2026) suggest active maintenance; 16 open issues suggest ongoing refinement.

When to avoid it — and what to weigh

  • Need Enterprise Monitoring — No integration with centralized logging platforms (Splunk, DataDog, etc.) or remote telemetry; single-device analysis only.
  • Require Long-Term Log Retention — No indication of persistent storage, cloud sync, or archival features; designed for immediate inspection rather than historical audit trails.
  • Production End-User Support — Requires elevated device permissions (root/ADB/Shizuku); not suitable for non-technical end users or consumer applications.
  • Need Closed-Source or Proprietary Control — GPL-3.0 license mandates source disclosure if distributed; commercial redistribution or closed-source derivatives are not permitted.

License & commercial use

GPL-3.0 (GNU General Public License v3.0). Copyleft license requiring source disclosure and license propagation for any distributed derivative or combined work. Free to use and modify internally.

Internal/non-distributed use for commercial Android debugging is permitted under GPL-3.0. However, any commercial redistribution, SaaS offering, or closed-source derivative requires release of full source under GPL-3.0. Requires legal review if bundling into a proprietary product. Contributor intent and enforcement history unknown.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityLow
DEV.co fitGood
Assessment confidenceHigh
Security considerations

LogFox reads device logs, which may contain sensitive data (authentication tokens, PII, credentials). No encryption or access control mentioned for exported logs; stored as plaintext ZIP. Users must manage log export security and retention. Device-level permissions (root/ADB/Shizuku) grant elevated access; only install from trusted sources. Source is open for audit; no security certifications or audits mentioned.

Alternatives to consider

Android Studio Logcat

Built-in IDE solution with full Android development tooling; no separate app installation; tighter integration with debugger and profiler. Requires desktop/laptop.

Crash Handler or Firebase Crashlytics

Cloud-based crash analytics with remote monitoring, multi-device aggregation, and issue grouping. Requires SDK integration and network connectivity; not local-only.

Frida or Similar Mobile Analysis Tools

Runtime instrumentation and inspection; more powerful for security testing and deep inspection. Steeper learning curve; broader scope than simple log reading.

Software development agency

Build on LogFox with DEV.co software developers

Download from F-Droid or review the source on GitHub. Verify GPL-3.0 license compliance if integrating into commercial products. Consider security implications of log export and data retention.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

LogFox FAQ

Can I use LogFox in a commercial product?
Depends on your use case. Internal/non-distributed use for debugging is allowed. Any commercial redistribution, bundling, or SaaS offering requires releasing full source under GPL-3.0 and likely legal review.
What Android versions are supported?
Not explicitly stated in README. Latest release date and Material You design suggest Android 12+, but official minimum version is not documented. Check GitHub releases or build metadata.
How do I export logs for bug reports?
LogFox includes a 'record logs and export to ZIP with device info' feature. Exact workflow and file format not detailed in README; refer to app UI or GitHub documentation.
Does LogFox work without root or ADB?
Yes, via Shizuku if available on the device. Shizuku is a separate system that provides elevated access without root; availability depends on device compatibility and manufacturer support.

Custom software development services

DEV.co is a software development agency delivering custom software development services to companies building on open source. Our software developers and web developers design, integrate, and ship production systems — spanning web development, APIs, AI, data, and cloud. If LogFox is part of your open-source observability roadmap, our team can implement, customize, migrate, and maintain it.

Evaluate LogFox for Your Android Debugging Workflow

Download from F-Droid or review the source on GitHub. Verify GPL-3.0 license compliance if integrating into commercial products. Consider security implications of log export and data retention.