Starting March 27, 2025, we recommend using android-latest-release instead of aosp-main to build and contribute to AOSP. For more information, see Changes to AOSP.
Discussion groups, contacts, and additional resources
Stay organized with collections
Save and categorize content based on your preferences.
This page provides several ways to contact Google or communicate with other
Android developers.
Discussion groups
Discussion groups are intended for developers working with the Android platform.
Our users help each other, and many experts post to these groups, including
members of the Open Handset Alliance. You're welcome to join and post to any
group, as long as you follow the Discussion group rules.
The following table lists discussion groups available to Android
developers. To join any of these discussion groups, click the link in the
Subscription links column.
Group name
Description
Subscription links
android-building
A group for discussion and help with building the Android source code, and with the build system. If you've just checked out the source code and have questions about how to turn it into binaries, start here.
This group is for developers who want to port Android to a new device. If you're wondering how to combine the Android source code with your hardware, this is the right group for you. Here you can discuss the specifics of porting Android to individual devices, from obtaining toolchains and merging kernel driver all the way to configuring or modifying apps for your specific configuration.
The following rules outline what's expected of subscribers to the discussion
groups:
Be friendly: Showing courtesy and respect to others is a vital part of the
Android culture, and Google expects everyone participating in the Android
community to be courteous. Being courteous doesn't mean
that you can't constructively disagree with each other, but it does mean that
you must be polite when doing so. There's never a reason to be antagonistic or
dismissive toward anyone; if you think there is, think again before you post.
Mobile development is serious business, but it's also a lot of fun, so help
Google strive to be one of the friendliest communities in all of open source.
Google doesn't have a formal policy on dealing with troublemakers, and we hope
we never need one. That said, Google pledges to do our best to be fair and
always try to warn someone before banning them. If you see someone being rude
or disrespectful, call them out on it. This is your group, and you don't have
to accept someone else being disrespectful just because it wasn't directed at
you. Just remember to be polite and courteous yourself!
Post only to the most relevant group for your message. Most of these groups
are for technical discussions of Android or users helping each other.
Generally Google doesn't put hard restrictions on the topics discussed in a
group. As long as the topic is relevant to Android in some way, it's welcome.
Google welcomes announcements and discussion of products, libraries,
publications, and other interesting Android-related news, but don't cross-post.
Google even welcomes (polite!) discussion of articles and ideas critical of
Android—after all, Google can't improve if we don't listen.
In working groups, stay on topic. Some of our groups are considered working
groups or groups intended to be used to support the completion of specific
tasks. In these groups, off-topic conversation isn't welcomed. Instead,
start general discussions in a different group.
Avoid spam. Google hates spam almost as passionately as we love courtesy and
respect, so we reserve the right to limit spam-like discussions.
Outright spam results in the spammer being immediately and permanently
banned from the list.
Search the group archives to see whether your question has already
been discussed. Searching for an answer before posting a new question avoids
time-wasting, redundant discussions.
Use a clear, relevant message subject. Clear subjects help everyone, both
those trying to answer your question and those looking for information.
Give plenty of details in your post. Code or log snippets,
pointers to screenshots, and similar details get better results and make
for better discussions. For a great guide to phrasing your questions, read
How to ask questions the smart way.
Contacts
This section lists options for contacting Google about AOSP and Android.
While Google reads every message received, Google can't respond to each of them.
we promise to contact you if we can help!
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 2025-06-12 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 2025-06-12 UTC."],[],[],null,["# Discussion groups, contacts, and additional resources\n\nThis page provides several ways to contact Google or communicate with other\nAndroid developers.\n\nDiscussion groups\n-----------------\n\nDiscussion groups are intended for developers working with the Android platform.\nOur users help each other, and many experts post to these groups, including\nmembers of the Open Handset Alliance. You're welcome to join and post to any\ngroup, as long as you follow the [Discussion group rules](#mailing).\n\nThe following table lists discussion groups available to Android\ndevelopers. To join any of these discussion groups, click the link in the\nSubscription links column.\n\n| Group name | Description | Subscription links |\n|------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| android-building | A group for discussion and help with building the Android source code, and with the build system. If you've just checked out the source code and have questions about how to turn it into binaries, start here. | [Subscribe through email](mailto:android-building+subscribe@googlegroups.com) or [Subscribe through Google Groups](https://groups.google.com/forum/?fromgroups#!forum/android-building) |\n| android-porting | This group is for developers who want to port Android to a new device. If you're wondering how to combine the Android source code with your hardware, this is the right group for you. Here you can discuss the specifics of porting Android to individual devices, from obtaining toolchains and merging kernel driver all the way to configuring or modifying apps for your specific configuration. | [Subscribe through email](mailto:android-porting+subscribe@googlegroups.com) or [Subscribe through Google Groups](https://groups.google.com/forum/?fromgroups#!forum/android-porting) |\n| android-contrib | This group is for developers who want to contribute code to Android. This is a working list, and isn't appropriate for general discussion. | [Subscribe through email](mailto:android-contrib+subscribe@googlegroups.com) or [Subscribe through Google Groups](https://groups.google.com/forum/?fromgroups#!forum/android-contrib) |\n\n### Discussion group rules\n\nThe following rules outline what's expected of subscribers to the discussion\ngroups:\n\n- Be friendly: Showing courtesy and respect to others is a vital part of the\n Android culture, and Google expects everyone participating in the Android\n community to be courteous. Being courteous doesn't mean\n that you can't constructively disagree with each other, but it does mean that\n you must be polite when doing so. There's never a reason to be antagonistic or\n dismissive toward anyone; if you think there is, think again before you post.\n Mobile development is serious business, but it's also a lot of fun, so help\n Google strive to be one of the friendliest communities in all of open source.\n\n Google doesn't have a formal policy on dealing with troublemakers, and we hope\n we never need one. That said, Google pledges to do our best to be fair and\n always try to warn someone before banning them. If you see someone being rude\n or disrespectful, call them out on it. This is your group, and you don't have\n to accept someone else being disrespectful just because it wasn't directed at\n you. Just remember to be polite and courteous yourself!\n | **Note:** If you see an outrageous violation, want to report spam, feel strongly about something, or just want to chat, contact the group owners.\n- Post only to the most relevant group for your message. Most of these groups\n are for technical discussions of Android or users helping each other.\n Generally Google doesn't put hard restrictions on the topics discussed in a\n group. As long as the topic is relevant to Android in some way, it's welcome.\n Google welcomes announcements and discussion of products, libraries,\n publications, and other interesting Android-related news, but don't cross-post.\n Google even welcomes (polite!) discussion of articles and ideas critical of\n Android---after all, Google can't improve if we don't listen.\n\n- In working groups, stay on topic. Some of our groups are considered *working\n groups* or groups intended to be used to support the completion of specific\n tasks. In these groups, off-topic conversation isn't welcomed. Instead,\n start general discussions in a different group.\n\n- Avoid spam. Google hates spam almost as passionately as we love courtesy and\n respect, so we reserve the right to limit spam-like discussions.\n Outright spam results in the spammer being immediately and permanently\n banned from the list.\n\n- Search the group archives to see whether your question has already\n been discussed. Searching for an answer before posting a new question avoids\n time-wasting, redundant discussions.\n\n- Use a clear, relevant message subject. Clear subjects help everyone, both\n those trying to answer your question and those looking for information.\n\n- Give plenty of details in your post. Code or log snippets,\n pointers to screenshots, and similar details get better results and make\n for better discussions. For a great guide to phrasing your questions, read\n [How to ask questions the smart way](http://www.catb.org/%7Eesr/faqs/smart-questions.html).\n\nContacts\n--------\n\nThis section lists options for contacting Google about AOSP and Android.\nWhile Google reads every message received, Google can't respond to each of them.\nwe promise to contact you if we can help!\n\n### License Google Mobile Services\n\nFor general information about Google Mobile Services, visit the\n[Google Mobile Services (GMS) marketing site](https://www.android.com/gms/).\n\nTo inquire about licensing GMS, use the\n[GMS contact form](https://www.android.com/gms/contact/) form.\n\n### Inquire about Android partnership\n\nIf you are creating a Android-compatible device and want to inquire about\npartnership, visit [Become an Android partner](https://docs.partner.android.com).\n\n### Follow Android brand guidelines\n\nIf you're a partner and are looking to use Android branding, refer to\nthe [Partner marketing hub](https://partnermarketinghub.withgoogle.com/brands/android/overview/brand-introduction/).\n\n### Report an AOSP bug\n\nTo report bugs for Android and AOSP, refer to [Report AOSP bug](/docs/setup/contribute/report-bugs).\n\nAdditional resources\n--------------------\n\nFollowing are some additional resources you might use to supplement your\nAndroid knowledge.\n\n### Additional resources for AOSP developers\n\n- [Marketing page for latest Android release](https://www.android.com/android-14/)\n- [Android blog](https://blog.google/products/android/)\n- [Google security blog](https://security.googleblog.com/)\n- [Google safety center](https://safety.google/security/)\n\n### Additional resources for app developers\n\n- [Android app developer's site](http://developer.android.com/)\n- [Android app developer's YouTube channel](https://www.youtube.com/channel/UCVHFbqXqoYvEWM1Ddxl0QDg)\n- [Google app developer's blog](https://android-developers.googleblog.com/)"]]