-
-
Notifications
You must be signed in to change notification settings - Fork 13
Bugs
π π¦ π π π π
Bugs are part of an apps life. They mean you no harm, but they are not here to stay either π .
What are bugs?
- If the app crashes it is obviously a bug
- If something is behaving unexpectedly, it could be a bug.
In any case check that you are on the latest update, the bug might already be fixed.
If the bug isn't fixed, then report it π.
Create an issue ticket on GitHub: https://github.com/d4rken/bluemusic/issues
- Describe what you expected and what actually happened
- List the steps that someone else would have to take to reproduce the issue
- Describe your setup
- Your device type (e.g. Pixel 5)
- Android version (e.g. Android 13.1)
- The BVM version you're using
Include a debug log if you can reproduce the issue.
Hint: You can long press the "Changelog" entry in BVM's settings to copy the version to your clipboard.
A debug log is a recording of BVM's actions. You start the recording, reproduce the issue, then stop it and can share a text file with a chronological account of what BVM did.
To start recording a debug log:
- Go to settings in BVM by navigating to the Settings tab
- Find the
Supportentry in the settings list - Tap
Debug logon the support screen - The debug log will start recording (you'll see "Currently recording" status)
- Now reproduce the issue you want to record
- Once you have reproduced the issue, go back to Settings β Support β Debug log
- Tap to stop recording
- After a short moment you will get options to share the log file
The debug log will be recorded until you stop it, the recording will continue, even if you force-stop and restart BVM.
If you are troubleshooting issues related to Bluetooth connections or volume restoration, it is useful to:
- Start debug logging
- Disconnect your Bluetooth device
- Wait a few seconds
- Reconnect the device
- Wait for BVM to react (or not react)
- Stop the debug log
The debug log files contain sensitive information (e.g. device names, Bluetooth MAC). Only share them with trusted parties (e.g. the developer when troubleshooting an issue).
A good bug report includes:
- Clear description: What you expected vs what happened
- Steps to reproduce: Exact steps someone else can follow
-
Device info:
- Phone model
- Android version
- BVM version
- Whether you're using Free or Pro version
-
Bluetooth device info:
- Type of device (headphones, car stereo, speaker, etc.)
- Device name/model if known
- Debug log: If you can reproduce the issue
- Screenshots: If relevant to the issue
Before reporting a bug, check if:
- You're on the latest version of BVM
- The app has all required permissions
- Battery optimization isn't preventing BVM from running
- The Bluetooth device is properly paired
- You've configured the device in BVM (not just connected it)
- The timing settings are appropriate for your device
Remember: The more information you provide, the easier it is to fix the bug! π―