From 5bc5079e134af76df7965b19f61c8de69e7432a4 Mon Sep 17 00:00:00 2001 From: Kavish Devar Date: Mon, 11 May 2026 22:12:39 +0530 Subject: [PATCH] update android bug report template --- .github/ISSUE_TEMPLATE/01-bug-report-android.yml | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/01-bug-report-android.yml b/.github/ISSUE_TEMPLATE/01-bug-report-android.yml index 8591801..5b8d6a2 100644 --- a/.github/ISSUE_TEMPLATE/01-bug-report-android.yml +++ b/.github/ISSUE_TEMPLATE/01-bug-report-android.yml @@ -1,7 +1,6 @@ name: Bug report (Android) description: Report a bug in the Android app labels: ["bug", "android"] -title: "[Android] " body: - type: markdown attributes: @@ -88,11 +87,13 @@ body: label: Logs description: | If you are rooted, give the app root access, open the app, go to `Settings → Troubleshooting → Collect Logs`, and attach the resulting file here. + Without logs most bugs are very hard to diagnose. If you are not, follow these instructions: - (Needs access to a computer, and USB/Wireless Debugging under developer options enabled) - Get the uid: Linux/Mac: `adb shell dumpsys package me.kavishdevar.librepods | grep uid` - Start logs: `adb logcat --uid=,1002 >> librepods-logs.txt` (1002 is for bluetooth) + + Commands: + - Get the uid: Linux/Mac: `adb shell dumpsys package me.kavishdevar.librepods | grep uid` + - Start logs: `adb logcat --uid=,1002 >> librepods-logs.txt` (1002 is for bluetooth) Steps for proper logs - force close the app