[Feature]: QuickBars Logging System

[Trooped]

Short Feature Title

QuickBars Logging System

What area does this affect?

User Interface (UI/UX), Code Quality

The Problem

While QuickBars currently uses the standard Android logging system (android.util.Log), these logs are "Developer-Only." They output to Logcat, which is volatile and requires Android Studio or an ADB terminal to view.

For the average user on an Android TV stick, these logs are invisible and disappear as soon as the buffer fills up. When a user reports a bug or a crash, I have no way to see the stack trace or errors unless the user happens to be a developer with a debugger handy.

When I started building the app, I didn't have much experience and didn't understand the importance of implementing this from the start. Better late than never!

The Proposed Solution

I suggest implementing a managed logging system that bridges the gap between raw Logcat and persistent user-side reports:

• The Silent Buffer (Performance First): Instead of constant disk writes (which can wear out cheap TV stick storage), the app should maintain a Circular Memory Buffer (e.g., the last 1,000 lines). Logs are only written to a physical file in the Downloads folder when a user explicitly clicks "Export Debug Report" or a fatal crash is caught.

• Logging Levels: Implementation of standard levels (DEBUG, INFO, WARNING, ERROR) to allow for filtering.

• Module-Based Tagging: Categorizing logs by functional areas so we can isolate issues quickly:

  • [WS] – WebSocket/Home Assistant connection logic.
  • [UI] – Overlay rendering and Remote Control navigation.
  • [PERM] – Android Permission handling (Overlay/Accessibility).
  • [SVC] – Background service lifecycle.
  • and more, based on needs...

• Privacy-First Scrubbing: A regex-based interceptor to redact Long-Lived Access Tokens, internal IPs, and passwords before they are written to the export file.

Screenshots or Video

No response

Visuals / Mockups

No response

Additional Information

Please let me know if you have any suggestions, especially if you have experience with logging in Android applications.

Home Assistant Context (Optional)

No response

Readiness Check

• I have confirmed this isn't already a feature/setting in the app by also searching the guide.
• I understand that this is an open-source project managed alongside a full-time job and B.Sc. studies by Omri, and PRs and Issues may take some time.
• I am willing to help provide more information upon request, and test beta builds of this feature.