Google Git
Sign in
android/platform/frameworks/support/c4f6980f03d9ab8ce74574d6294308ad98dff759
commit
c4f6980f03d9ab8ce74574d6294308ad98dff759
[log]
author
samratdebroy <[email protected]>
Wed Mar 11 16:41:23 2026 -0400
committer
samratdebroy <[email protected]>
Mon Mar 16 13:52:48 2026 -0400
tree
b7f5e6b0d995708cbbfe2298009176b033e5c1b5
parent
1df60e14269e6cd93a1e794b2c2f2d4ba32f85e7 [diff]
Rename EntityManager in scenecore to EntityRegistry

It doesn't really actively manage anything.
"Registry" is a more established naming pattern for what
essentially just passively wraps look-up tables.

Note: This is a different name from the SceneNodeRegistry used in the Impl
layers because there are no "Nodes" at the API layer. We also drop the "Scene" because this class strictly deals with entities and no ScenePose.

Test: Unit tests
BUG: 491799042
Change-Id: I6365aa9b84461147ebe762dca4757a292e9d4bf5
26 files changed
tree: b7f5e6b0d995708cbbfe2298009176b033e5c1b5
  1. .github/
  2. .idea/
  3. activity/
  4. androidx-settings-plugins/
  5. annotation/
  6. appcompat/
  7. appfunctions/
  8. appsearch/
  9. arch/
  10. asynclayoutinflater/
  11. autofill/
  12. benchmark/
  13. binarycompatibilityvalidator/
  14. biometric/
  15. browser/
  16. buildSrc/
  17. buildSrc-tests/
  18. busytown/
  19. camera/
  20. car/
  21. cardview/
  22. collection/
  23. compose/
  24. concurrent/
  25. constraintlayout/
  26. coordinatorlayout/
  27. core/
  28. credentials/
  29. cursoradapter/
  30. customview/
  31. datastore/
  32. development/
  33. docs/
  34. docs-public/
  35. docs-tip-of-tree/
  36. documentfile/
  37. draganddrop/
  38. drawerlayout/
  39. dynamicanimation/
  40. emoji/
  41. emoji2/
  42. enterprise/
  43. exifinterface/
  44. external/
  45. fragment/
  46. glance/
  47. gradle/
  48. graphics/
  49. gridlayout/
  50. health/
  51. heifwriter/
  52. hilt/
  53. ink/
  54. input/
  55. inspection/
  56. interpolator/
  57. javascriptengine/
  58. kotlin-js-store/
  59. kruth/
  60. leanback/
  61. lifecycle/
  62. lint/
  63. lint-checks/
  64. loader/
  65. media/
  66. mediarouter/
  67. metrics/
  68. navigation/
  69. navigation3/
  70. navigationevent/
  71. paging/
  72. palette/
  73. pdf/
  74. percentlayout/
  75. photopicker/
  76. placeholder/
  77. placeholder-tests/
  78. playground-common/
  79. playground-projects/
  80. preference/
  81. print/
  82. privacysandbox/
  83. profileinstaller/
  84. recommendation/
  85. recyclerview/
  86. resourceinspection/
  87. room3/
  88. safeparcel/
  89. samples/
  90. savedstate/
  91. security/
  92. sharetarget/
  93. slidingpanelayout/
  94. sqlite/
  95. stableaidl/
  96. startup/
  97. swiperefreshlayout/
  98. test/
  99. testutils/
  100. text/
  101. tracing/
  102. transition/
  103. tv/
  104. tvprovider/
  105. vectordrawable/
  106. versionedparcelable/
  107. viewpager/
  108. viewpager2/
  109. wear/
  110. webgpu/
  111. webkit/
  112. window/
  113. work/
  114. xr/
  115. .gitignore
  116. build.gradle
  117. cleanBuild.sh
  118. code-review.md
  119. CONTRIBUTING.md
  120. gradle.properties
  121. gradlew
  122. libraryversions.toml
  123. license-baseline.txt
  124. LICENSE.txt
  125. MOLECULE_UI_OWNERS
  126. OWNERS
  127. PREUPLOAD.cfg
  128. README.md
  129. settings.gradle
  130. studiow
  131. TEXT_OWNERS
README.md

Android Jetpack

Revved up by Develocity

Jetpack is a suite of libraries, tools, and guidance to help developers write high-quality apps easier. These components help you follow best practices, free you from writing boilerplate code, and simplify complex tasks, so you can focus on the code you care about.

Jetpack comprises the androidx.* package libraries, unbundled from the platform APIs. This means that it offers backward compatibility and is updated more frequently than the Android platform, making sure you always have access to the latest and greatest versions of the Jetpack components.

Our official AARs and JARs binaries are distributed through Google Maven.

You can learn more about using it from Android Jetpack landing page.

Contribution Guide

For contributions via GitHub, see the GitHub Contribution Guide.

Note: The contributions workflow via GitHub is currently experimental - only contributions to the following projects are being accepted at this time:

Code Review Etiquette

When contributing to Jetpack, follow the code review etiquette.

Accepted Types of Contributions

  • Bug fixes - needs a corresponding bug report in the Android Issue Tracker
  • Each bug fix is expected to come with tests
  • Fixing spelling errors
  • Updating documentation
  • Adding new tests to the area that is not currently covered by tests
  • New features to existing libraries if the feature request bug has been approved by an AndroidX team member.

We are not currently accepting new modules.

Checking Out the Code

Head over to the onboarding docs to learn more about getting set up and the development workflow!

Continuous integration

Our continuous integration system builds all in progress (and potentially unstable) libraries as new changes are merged. You can manually download these AARs and JARs for your experimentation.

Password and Contributor Agreement before making a change

Before uploading your first contribution, you will need setup a password and agree to the contribution agreement:

Generate a HTTPS password: https://android-review.googlesource.com/new-password

Agree to the Google Contributor Licenses Agreement: https://android-review.googlesource.com/settings/new-agreement

Getting reviewed

  • After you run repo upload, open r.android.com
  • Sign in into your account (or create one if you do not have one yet)
  • Add an appropriate reviewer (use git log to find who did most modifications on the file you are fixing or check the OWNERS file in the project's directory)

Handling binary dependencies

AndroidX uses git to store all the binary Gradle dependencies. They are stored in prebuilts/androidx/internal and prebuilts/androidx/external directories in your checkout. All the dependencies in these directories are also available from google(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.