Google Git
Sign in
android / platform / frameworks / support / 82f21b2f6d39b9aa0c0d415863c0658cb9f7a978
commit82f21b2f6d39b9aa0c0d415863c0658cb9f7a978[log] [tgz]
authorNeda Topoljanac <tneda@google.com>Mon Oct 13 20:22:15 2025 +0000
committerNeda Topoljanac <tneda@google.com>Fri Oct 17 20:30:09 2025 +0000
tree71dd10e04030765394e5f88b4f3b4231b2a5e901
parentc31c9a5aaa5dcfefed516f1eac7829ac5e46377f [diff]
Use optimized hash and equals in resources

Previously, we implemented hashCode and equals, but for Dynamic data
protos we just used toByteArray, which is not efficient, but we don't
expect too much usage of it.

However, now with aosp/3691292 there is a proper way of hashing
dynamic data by looking and its content all the way to the last
leaf, and we should use that in Resources and Triggers too.

Additionally, fix equals and hashCode methods in DynamicProtoHasEquals
- the problem is that initial switch case per type was on the Dynamic
builder object but it was comparing instance to proto classes and was
never true. Fix is to have the first pass and switch on dynamic builder
and then internal methods would translate it to proto and to the
comparison of inner cases.

Bug: 431678176
Test: Existing ones
Change-Id: Ie128f66caeb4e8969bfc70225790509d850b5658
5 files changed
tree: 71dd10e04030765394e5f88b4f3b4231b2a5e901
  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. performance/
  76. photopicker/
  77. placeholder/
  78. placeholder-tests/
  79. playground-common/
  80. playground-projects/
  81. preference/
  82. print/
  83. privacysandbox/
  84. profileinstaller/
  85. recommendation/
  86. recyclerview/
  87. remotecallback/
  88. resourceinspection/
  89. room/
  90. room3/
  91. safeparcel/
  92. samples/
  93. savedstate/
  94. security/
  95. sharetarget/
  96. slidingpanelayout/
  97. sqlite/
  98. stableaidl/
  99. startup/
  100. swiperefreshlayout/
  101. test/
  102. testutils/
  103. text/
  104. tracing/
  105. transition/
  106. tv/
  107. tvprovider/
  108. vectordrawable/
  109. versionedparcelable/
  110. viewpager/
  111. viewpager2/
  112. wear/
  113. webkit/
  114. window/
  115. work/
  116. xr/
  117. .gitignore
  118. build.gradle
  119. cleanBuild.sh
  120. code-review.md
  121. CONTRIBUTING.md
  122. gradle.properties
  123. gradlew
  124. libraryversions.toml
  125. license-baseline.txt
  126. LICENSE.txt
  127. OWNERS
  128. PREUPLOAD.cfg
  129. README.md
  130. settings.gradle
  131. studiow
  132. 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.