Reporting A Problem - Android
These steps should help you as the user communicate issues effectively to the developer.
- 1 Post at particular Thread that you have encounter problem
- 2 Do Not Use The Private Message Button
- 3 Read OP Pages At least twice
- 4 Follow ALL the instructions given
- 5 Check to see if your issue or a similar issue has already been reported.
- 6 Give a Proper Report
- 7 Do not ask or force the OP/Developers to fix the problem
- 8 Take your third party installation problem away
- 9 Stop Asking Whether Will This Work Or Not
- 10 Press thanks button to user/devs that helped you
- 11 Provide logcats whenever possible
Post at particular Thread that you have encounter problem
- If you have a problem/bug to report on XXX Rom.Report on XXX Rom Thread & not YYY Rom.
- If there's a Solution/FAQ Page for the particular rom do report on the thread instead of the [DEV] thread
- Doesn't require you to open a thread on the Android Development Forum (It's just spam there, we hate it).
Do Not Use The Private Message Button
- Please Never Ever Send Any PM to developers just to report the bug you encountered. Post it on the particular thread that is mentioned.
- Developers/OP will have an eye on it, so you don't need to send a PM to report your issue.
- Do appreciate the work of the developers & respect that they have their own time too. Keep your question(s) on the thread.
Read OP Pages At least twice
- The place where you should have all the info you need.
- Read every single notice/quote/information/instruction/faq/other's written page
- Do not just head to the download section and press the download
- Look at every info on which particular thing you need and what you should do to install it
Follow ALL the instructions given
- When the OP posts Wipe Cache & Dalvik, it means to select that particular option only.
- If the OP posted "Use Only Select/Recommend Kernel", please flash/install that particular kernel only.
- Follow all the steps properly(No skipping steps!).
Check to see if your issue or a similar issue has already been reported.
- Let's say you have setting fc's everytime you enable the sound option. Do a search to see whether other users have reported it or not.
- If the particular problem/bug has been reported, there is no need for another user to report it (Duplicating post). If the bug is still open, feel free to add additional information such as logs.
Give a Proper Report
Effective bug reports are the most likely to be fixed. Your bug reports should include:
- A clear summary - Clearly describe the issue in a few sentences.
- Steps to reproduce the issue - How did your issue occur? This is the most important part of any bug report.
- Results - What happens if all the steps are followed? Precisely describe the observed result (e.g. If you have a random reboot upon selecting theme manager, report that it's due to the theme manager instead of just saying "I have random reboot").
- Reproducibility - Can you reproduce the issue? Is your bug consistent/unavoidable, or is it intermittent or once thus far?
- Include if you tried to wipe & cache.
- Include the kernel you are running on.
- Include what build version you are running.
- If possible, please provide a screenshot.
- Always provide a log. Use adb logcat (see below) - this is very valuable to developers and will probably expedite the fix.
Do not ask or force the OP/Developers to fix the problem
- No matter what problem you are having, no words such as "Please" will fix the problem.
- Developers have their own time, they choose to fix what they want - you don't pay for what you download.
Take your third party installation problem away
- Let say you have installed a third party mod (Ex: Beats Audio) ,if you encountered any problem please post on the beats audio thread instead
- If You having problem by supercharging or installing any third party patch do take to the particular thread or keep it on your own.
Stop Asking Whether Will This Work Or Not
- Facepalm: Please try it yourself or see comments by other users.
- If you want to know just install and test it yourself
- If your afraid bricking then never go near a development thread. There's always a Risk!
Provide logcats whenever possible
- Dmesg using simple terminal emulator on your device:
$ su # dmesg >/mnt/sdcard/dmesg.txt # logcat -d -v time >/mnt/sdcard/logcat.txt
Attach dmesg.txt and logcat.txt to your problem report.