Home | History | Annotate | Download | only in source
      1 page.title=Report Bugs
      2 @jd:body
      3 
      4 <!--
      5     Copyright 2015 The Android Open Source Project
      6 
      7     Licensed under the Apache License, Version 2.0 (the "License");
      8     you may not use this file except in compliance with the License.
      9     You may obtain a copy of the License at
     10 
     11         http://www.apache.org/licenses/LICENSE-2.0
     12 
     13     Unless required by applicable law or agreed to in writing, software
     14     distributed under the License is distributed on an "AS IS" BASIS,
     15     WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
     16     See the License for the specific language governing permissions and
     17     limitations under the License.
     18 -->
     19 <p>Thank you for your interest in Android! One of the best ways you can help us
     20 improve Android is to let us know about any problems you find with it.</p>
     21 <p class="note"><strong>Note:</strong> For security vulnerabilities, please use
     22 the AOSP bug tracker <a
     23 href="https://code.google.com/p/android/issues/entry?template=Security%20bug%20report">Security
     24 bug report</a> template. See <a
     25 href="{@docRoot}security/overview/updates-resources.html#report-issues">Reporting
     26 Security Issues</a> for additional details.</p>
     27 <p>Here's how to report <strong>non-security</strong> bugs:</p>
     28 <ul>
     29 <li>
     30 <p><a href="https://code.google.com/p/android/issues/advsearch">Search for
     31 your bug</a> to see if anyone has already reported it. Don't forget to
     32 search for all issues, not just open ones, as your issue might already
     33 have been reported and closed. To help you find the most popular results,
     34 sort the result by number of stars.</p>
     35 </li>
     36 <li>
     37 <p>If you find your issue and it's important to you, star it! That's how we know which bugs are most important to fix.</p>
     38 </li>
     39 <li>
     40 <p>If no one has reported your bug, file the bug. You can use one of these templates:</p>
     41 <ul>
     42 <li>
     43 <p><a href="https://code.google.com/p/android/issues/entry?template=User%20bug%20report">Bug in your Device</a> - 
     44 use this if you are a user reporting a bug in a device you own</p>
     45 </li>
     46 <li>
     47 <p><a href="https://code.google.com/p/android/issues/entry?template=Developer%20bug%20report">Bug in the Software</a> - 
     48 use this if you found a bug in the course of developing an app</p>
     49 </li>
     50 <li>
     51 <p><a href="https://code.google.com/p/android/issues/entry?template=Feature%20request">Feature Request</a> - 
     52 use this for a feature you'd like to see in a future verison</p>
     53 </li>
     54 </ul>
     55 </li>
     56 </ul>
     57 <p>Keep in mind that an issue tracker is not a user support forum. It is a list
     58 of pending technical tasks, along with information relevant for those tasks,
     59 and information about progress on those tasks including which ones might
     60 get worked on in the short term.</p>
     61 <p>This issue tracker is narrowly focused on the Android Open Source Project.
     62 Issues with retail devices need to be reported through those devices' support
     63 channels, especially for devices other than Nexus. Issues with applications
     64 that aren't part of AOSP need to be reported with those applications'
     65 developers; that is also the case for Google applications.</p>
     66 <p>Please note that we can't guarantee that any particular bug can be fixed in
     67 any particular release. To see what happens to your bug once you report it,
     68 read <a href="life-of-a-bug.html">Life of a Bug</a>.</p>
     69 <p>In general, please put as much information in bugs as you can. Just a one liner
     70 telling us something isn't working is usually useless, and will probably be
     71 closed without any action. The more detail you provide, the more likely your
     72 issue is to be resolved.</p>
     73