Skip to content
Browse files

Update issue templates

  • Loading branch information
mringwal committed Jan 6, 2020
1 parent fdfba5a commit 67548044c3db8dca396c793f492977f7c850aef9
Showing with 56 additions and 0 deletions.
  1. +36 −0 .github/ISSUE_TEMPLATE/
  2. +20 −0 .github/ISSUE_TEMPLATE/
@@ -0,0 +1,36 @@
name: Bug report
about: Create a report to help us improve
title: ''
labels: ''
assignees: ''


**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1. Run example '...'
2. Connect to/from remove device '...'
3. Start action '...'

**Expected behavior**
A clear and concise description of what you expected to happen.

**HCI Packet Logs**
For all Bluetooth issues, please provide a full packet log that includes initial pairing. You need to zip the packet log as GitHub does not know how to handle .pklg files.

How to get packet log depends on the port:
- For desktop ports, full packet logging is enabled by default and the packet log is available as `/tmp/hci_dump.pklg` (Mac/Linux), or `hci_dump.pklg' (Windows).
- For embedded ports, you can enable #define LOG_INFO in btstack_config.h and uncomment the call to 'hci_dump_open(..)' in the main() function to enable logging over UART Console or Segger RTT. Please capture text output and process using `btstack/tool/`. The tool will generate the text file into a .pklg file which can be analysed with Wireshark or Apple's PacketLogger tool.
- For ESP32: BTstack's `port/esp32/` script copies the current version of BTstack into the esp-idf folder. To enable packet logging, you need to edit esp-idf/components/btstack/main.c
**Environment: (please complete the following information):**
- Current BTstack branch: [e.g. develop]
- Bluetooth Controller [e.g. CSR 8510, TI CC2564C, ...]
- Remote device: [e.g. iPhone X with iOS 13.3]
**Additional context**
Add any other context about the problem here.
@@ -0,0 +1,20 @@
name: Feature request
about: Suggest an idea for this project
title: ''
labels: ''
assignees: ''


**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

0 comments on commit 6754804

Please sign in to comment.
You can’t perform that action at this time.