Report and track bugs  |  Android Open Source Project
Skip to main content
Docs
What's new?
Release notes
Latest security bulletins
Latest Compatibility Definition Document (CDD)
Site updates
Getting Started
About
Start
Download
Builds
Test
Create
Contribute
Community
Tools, build, and related reference
Security
Overview
Bulletins
Features
Testing
Best Practices
Core Topics
Architecture
Audio
Camera
Connectivity
Data
Display
Fonts
Graphics
Interaction
Media
Performance
Permissions
Power
Runtime
Settings
Storage
Tests
Updates
Virtualization
Compatibility
Compatibility Definition Document (CDD)
Compatibility Test Suite (CTS)
Android Devices
Cuttlefish
Enterprise
TV
Automotive
Overview
Software Defined Vehicle
In-vehicle Infotainment
Release Details
Reference
HIDL
HAL
Trade Federation
Security Test Suite
Android Code Search
/
English
Deutsch
Español – América Latina
Français
Indonesia
Italiano
Polski
Português – Brasil
Tiếng Việt
Türkçe
Русский
עברית
العربيّة
فارسی
हिंदी
বাংলা
ภาษาไทย
中文 – 简体
中文 – 繁體
日本語
한국어
Sign in
Documentation
What's New?
Getting Started
Security
Core Topics
Compatibility
Android Devices
Automotive
Reference
Docs
More
What's New?
Getting Started
Security
Core Topics
Compatibility
Android Devices
Automotive
Reference
Android Code Search
Overview
About
AOSP overview
FAQ
Start
Try Android development
Understand terminology
Set up for AOSP development (9.0 or later)
Set up for AOSP development (2.3 - 8.0)
Download
Download the Android source
Troubleshoot and fix sync issues
Source control tools
Build
Build overview
Build Android
Use feature launch flags
Feature launch flag overview
Determine flag usage and type
Declare an aconfig flag
Wrap code change in feature launch flag
Set feature launch flag values
Change a flag's value at runtime
Declare and use a build flag
Test code within feature launch flags
Build kernels
Build Pixel kernels
Convert from Make to Soong
Implement Java SDK library
Android Rust
Introduction
Android Rust modules
Binary modules
Library modules
Test modules
Fuzz modules
Source generators
Source generators overview
Bindgen bindings modules
Protobuf modules
Hello Rust example
Android Rust patterns
Rust IDE setup
Compile with Jack (6.0 - 8.1)
Create
Source control workflow
Custom device development
Add a new device type
Build for 32-bit and 64-bit architectures
Use reference boards
Create a software bill of materials (SBOM)
Configure and handle update ownership for apps
Test
Test a build
Flash with Fastboot
Flash with Android Flash Tool
Test with the cuttlefish emulator
Use Android Emulator virtual devices
Contribute
Overview
Android Code Search
Contributor license agreements and headers
Release lifecycle
Submit code changes
Contribute to upstream projects
Git source editor
Review a change
Download build artifacts
Report and track bugs
Code with respect
AOSP Java code style for contributors
API guidelines
Overview
Android async and nonblocking API guidelines
Android API client-side caching guidelines
Community
Code of conduct
Discussion groups, contacts, and additional resources
Tools, build, and related reference
Overview
Android.bp file format
Kernel branches and their build systems
Codenames, tags, and build numbers
Fastboot key combinations
Repo command reference
What's new?
Release notes
Latest security bulletins
Latest Compatibility Definition Document (CDD)
Site updates
Getting Started
About
Start
Download
Builds
Test
Create
Contribute
Community
Tools, build, and related reference
Security
Overview
Bulletins
Features
Testing
Best Practices
Core Topics
Architecture
Audio
Camera
Connectivity
Data
Display
Fonts
Graphics
Interaction
Media
Performance
Permissions
Power
Runtime
Settings
Storage
Tests
Updates
Virtualization
Compatibility
Compatibility Definition Document (CDD)
Compatibility Test Suite (CTS)
Android Devices
Cuttlefish
Enterprise
TV
Automotive
Overview
Software Defined Vehicle
In-vehicle Infotainment
Release Details
Reference
HIDL
HAL
Trade Federation
Security Test Suite
Effective in 2026, to align with our trunk stable development model and ensure platform stability for the ecosystem, we will publish source code to AOSP in Q2 and Q4. For building and contributing to AOSP, use android-latest-release. The android-latest-release manifest branch will always reference the most recent release pushed to AOSP. For more information, see Changes to AOSP.
AOSP
Docs
Getting Started
Report and track bugs
Stay organized with collections
Save and categorize content based on your preferences.
You can help improve Android by reporting issues and requesting new features
using the Google Issue Tracker.
Google Issue Tracker is a tool used by
Google to track AOSP issues and feature requests. The Issue Tracker is available
outside of Google for use by external public and partner users who need to
collaborate with Google teams on specific issues and features.
To learn the basics of the Google Issue Tracker,
see the
Google Issue Tracker.
Note: Use the Google Issue Tracker only to report an AOSP bug or
request an AOSP feature. If you need immediate help with AOSP, Android phones,
Android app development, or other non-AOSP issues, refer to
Android community and contacts.
Report a bug
To report an AOSP bug:
With
all open bugs
as the basis for your search, use the Issue Tracker's search field to see if
anyone has already reported your issue or feature. Don't forget to also search
closed and fixed bugs. To help you find the most popular results, sort the
result by number of stars. For details on using the search field, refer to
Issue Searches
If you find your issue and it's important to you,
star it!
The number of stars on an issue helps Google to determine its priority.
If no one has reported your issue, create a new bug.
Refer to the section of this document that relates to the component for
your bug. Bug components identify the area of Android for which the bug
applies.
If the bug is related to security, refer to the Security.
If the bug is related to AOSP, refer to Platform.
If the bug is related to developer tools, refer to
Android developer tools.
If the bug refers to incorrect documentation, refer to
Documentation.
Fill out the provided template:
If the issue is a bug, include the steps to reproduce the bug in the
comments. A comment that only states something isn't working is likely to
require further information. The amount of detail that you provide,
including log files and even a patch set, helps Google address your issue.
If the issue is a feature request, provide explicit details on the
proposed feature, including the problem solved and design considerations.
Click Create. The bug report is created for Google to review.
Note: When reporting a new AOSP bug, make sure that the component is under
the Android Public Tracker.
To learn how to track the bug's status, refer to Track bug status.
Bug components
The following four sections are designed to help you search for and report bugs
using the correct component.
Security
If you find an issue that impacts the security of Android or components in
Pixel devices, file a bug using the instructions in
Reporting security issues.
Additionally, security bugs are eligible for the
Android and Google Devices Reward Program.
Platform
If you have an issue or feature request that impacts an aspect of the Android
platform, file your bug by clicking the bug icon next to the relevant component
area:
Browse all platform issues
Browse bugs
File a bug
Accessibility
bug_report
ART
bug_report
Browser
bug_report
CTS
bug_report
Framework
bug_report
Graphics
bug_report
Kernel (GKI)
bug_report
16kB
bug_report
Media
bug_report
Instant Apps
bug_report
Libcore
bug_report
Networking
bug_report
System
bug_report
Generic System Image
bug_report
Text
bug_report
Things
bug_report
Wear
bug_report
Android developer tools
If you have an issue or feature request that impacts an aspect of the Android
developer tools file your bug by clicking the bug icon next to the relevant
component area in the following table.
Note: Because the tools have different requirements, read the
General Bug filing details and the linked details for the tool.
Browse all Developer Tools issues
Browse bugs
Details
File a bug
adb
bug_report
Android
Studio
Information specific for Android
Studio bugs
bug_report
C++
Issues in Android Studio
bug_report
Emulator or System Images
Information specific for Emulator bugs
bug_report
Gradle
Information specific for Gradle
bugs
bug_report
Apply Changes
Information specific for Apply
Changes bugs
bug_report
Lint
bug_report
NDK
NDK compiler or build system issues. Not for API requests or bugs. APIs are
part of the OS, and requests related to them should be filed in one of the previous Platform components
(if you don't know which, use Framework).
bug_report
Profilers
bug_report
Jetpack (androidx)
bug_report
Jetpack (androidx) Test
bug_report
Games SDK
bug_report
Documentation
If you have an issue or feature request that impacts an aspect of the Android
documentation, file your bug by clicking the bug icon next to the relevant
component area:
Browse bugs
File a bug
developer.android.com (app developer documentation)
bug_report
source.android.com (AOSP documentation)
bug_report
DMA Interoperability Request
If you would like to submit a DMA Interoperability request for Android, use
the relevant component area:
File a request
Browse requests
Create a new public request
Public requests
Create a new private request
DMA content feed request on Pixel
In the European Economic Area (EEA), Pixel displays DMA online search engine
(OSE) choice screens that lets users select their preferred OSE. If a user
selects a particular provider in the OSE choice screen, that provider can elect
to have its content feed displayed on the Pixel screen that is displayed when
users swipe right from Pixel's home screen.
If you're a provider that participates in the DMA OSE choice screen in any
Member State and are interested in showing your content on Pixel's -1 screen,
please file a bug to contact us:
Create a new private request
Track bug status
Newly created bugs are always marked with a status of New. AOSP maintainers
periodically review and triage bugs by changing their status and potentially
assigning them to someone. Bugs are triaged into one of three categories:
Needs more information. The bug report doesn't have enough
information for someone to prioritize or properly analyze the bug. The bug
report is put on a list (New + Hotlist:NeedsInfo) until you provide
the requested information. After some period of time, if no additional
information is provided, the bug is given a status indicating that it won't be
acted upon.
The bug is Assigned to someone and, optionally, reprioritized. The bug
report has been recognized as an adequately-detailed report of a legitimate
issue. The bug's is properly prioritized or is reprioritized. Finally, the
bug is assigned to a specific contributor to assess and analyze.
Typically, a bug remains as Assigned until someone intends to resolve the
bug, at which point it is assigned an Accepted status. However, an
assignee might not change a bug's status to Accepted and, instead, just
fix the bug and assign a Fixed or Fixed (verified) status.
The bug won't be acted upon. A bug falls into this category for several
reasons, such as the bug is a duplicate of another bug, the bug is infeasible to
fix, or the bug represents functionality that is working as intended.
Note: This process represents a typical process for AOSP bugs. Your bug's
progression through different statuses might vary slightly.Note: Android contains a lot of software and gets a correspondingly large number
of bugs. As a result, sometimes bugs don't make it through all of the statuses
in a formal progression. Google tries to keep the system up to date, but often
does so using periodic bug sweeps where it reviews the database and make
updates. Also, Google can't guarantee the completion of a bug fix in time for
any specific release.
To track bug status:
Open the bug and look at the priority, status, and comments fields. For
explanations of priority and status, refer to the
Issue fields.
(optional) respond to any questions or comments in the comments field.
Bugs marked with a Fixed (verified) status are included in a future release
of Android.
Additional information for specific statuses
Following is further explanation for a few bug statuses (in addition to the
information provided in the Issue Tracker
Issue fields documentation):
Won't fix (Intended behavior): An AOSP maintainer has
determined that the behavior described isn't a bug, but is the intended
behavior. This status is also commonly referred to as "working as
intended (WAI)." For feature requests, an AOSP maintainer has determined
that the request isn't going to be implemented in Android.
Won't fix (Infeasible): The changes that are needed to
address the issue aren't reasonably possible. This status is also used for
issues reported that can't be handled in AOSP, typically because it's related
to a customized device or to an external app, or the reporter mistook
the Issue Tracker as a help forum.
Fixed (Verified): This bug has been fixed, and is included
in a formal release.
Fixed: This bug has been fixed (or feature implemented) in
a source tree, but might not yet been included in a formal release.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2026-06-17 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-06-17 UTC."],[],[]]
Build
Android repository
Requirements
Downloading
Preview binaries
Factory images
Driver binaries
Connect
@Android on X
@AndroidDev on X
Android Blog
Google Security Blog
Platform on Google Groups
Building on Google Groups
Porting on Google Groups
Get help
Android Help Center
Pixel Help Center
www.android.com
Google Mobile Services
Stack Overflow
Issue Tracker
About Android
Community
Legal
License
Privacy
Site feedback
Manage cookies
English
Deutsch
Español – América Latina
Français
Indonesia
Italiano
Polski
Português – Brasil
Tiếng Việt
Türkçe
Русский
עברית
العربيّة
فارسی
हिंदी
বাংলা
ภาษาไทย
中文 – 简体
中文 – 繁體
日本語
한국어