How to provide a bug/issue report

[andythedev]

I see a number of users complaining about problems with their ROM but providing little or no detail which can make it hard to help them. Here's a little guide I've come up with to help users and devs alike.

Step 1: What is your issue
Precisely explain what your issue is and when it occured.

I can't connect to my Logitech K380 bluetooth keyboard after updating from Build 1 to Build 2.

Step 2: How have you tried to resolve this
Talk through the steps you have taken to fix the problem yourself.

Unpairing the device, restarting the phone and toggling bluetooth doesn't seem to have any effect.

Step 3: How do others reproduce the error
Explain how other users of the forum can reproduce this issue. Document the expected behavior and actual behavior.

To replicate, turn on bluetooth in the settings menu, select your bluetooth keyboard, type in the pairing code and hit enter.

Expected behavior: A notification stating "Bluetooth Device Connected"
Actual behavior: Under the device name is the message "Unable to connect"

Step 4 (Optional): Provide a log
Connect to your phone via an ADB shell and type the following. Replace 'bluetooth' with a string which is related to your issue.
Type

logcat | grep -i bluetooth

Here is the logcat output

08-31 10:41:49.406  9699  9699 I BluetoothDevice: createBond() for device 34:88:5D:42:**:** called by pid: 9699 tid: 9699
08-31 10:41:49.407 15768 15781 D A2dpService: getA2DPService(): returning [email protected]
08-31 10:41:49.470 15768 15788 I BluetoothBondStateMachine: Bond address is:34:88:5D:42:**:**
08-31 10:41:49.470 15768 15788 I BluetoothBondStateMachine: Entering PendingCommandState State
08-31 10:41:49.471 15768 15786 I BluetoothBondStateMachine: bondStateChangeCallback: Status: 0 Address: 34:88:5D:42:**:** newState: 1
08-31 10:41:49.474 15768 15788 I BluetoothBondStateMachine: Bond State Change Intent:34:88:5D:42:**:** OldState: 10 NewState: 11
08-31 10:42:24.492 15768 15786 I BluetoothBondStateMachine: bondStateChangeCallback: Status: 10 Address: 34:88:5D:42:**:** newState: 0
08-31 10:42:24.492 15768 15788 D BluetoothAdapterProperties: Failed to remove device: 34:88:5D:42:**:**
08-31 10:42:24.494 15768 15788 I BluetoothBondStateMachine: Bond State Change Intent:34:88:5D:42:**:** OldState: 11 NewState: 10
08-31 10:42:24.497 15768 15788 D A2dpService: getA2DPService(): returning [email protected]
08-31 10:42:24.498 15768 15788 I BluetoothBondStateMachine: StableState(): Entering Off State

--------------------------------------------------------------------
Sources
The information provided was based on personal experience and inspired by the Atom Issue Template.

 

[s1ck-IT]

Made my day

While reading this, i haven't realised that this is just an example for a good bug/issue report..
because you exactly describe the problem i have with bluetooth speakers, bluetooth headphone, xiaomi roidmi, a noname bluetooth stick and my Logitech k480 keyboard
searching xda up and down i can't find people having such issues..

Question: Are you having the same issues or am i a lonely guy?

Best regards

 

[andythedev]

While reading this, i haven't realised that this is just an example for a good bug/issue report..
because you exactly describe the problem i have with bluetooth speakers, bluetooth headphone, xiaomi roidmi, a noname bluetooth stick and my Logitech k480 keyboard
searching xda up and down i can't find people having such issues..

Question: Are you having the same issues or am i a lonely guy?

Best regards

Hi there,
Unfortunately my examples were sourced from an issue with a previous ROM that have since been resolved. I'd advise you contact your ROM developer if you're having bluetooth issues.

Happy bug reporting