Lines Matching full:bug
24 allow anyone to see your report, which may put users at risk until the bug is
32 - [Search for your bug](http://code.google.com/p/android/issues/advsearch) to see if anyone has already reported it.
36 - If no one's reported your bug, file the bug. You can use one of these templates:
38 - [Bug in your Device](http://code.google.com/p/android/issues/entry?template=User%20bug%20report) - use this if you are a user reporting a bug in a device you own
40 - [Bug in the Software](http://code.google.com/p/android/issues/entry?template=Developer%20bug%20report) - use this if you found a bug in the course of developing an app
44 Please note that we can't guarantee that any particular bug can be fixed in
45 any particular release. To see what happens to your bug once you report it,
46 read [Life of a Bug](life-of-a-bug.html).
51 issue is to be resolved. Below, there are some examples of a good bug report
52 and a poor bug report.
54 ## A Poor Bug Report ##
68 This is a poor bug report because it doesn't provide any context for the
71 it. In other words, this bug report doesn't provide enough information for
74 ## A Good Bug Report ##
78 Interesting bug, while using Eclipse 3.3.1.1 with m37a of android and the following code:
