Google Git
Sign in
android / platform / frameworks / support / 125448ca43165ecf404f792f7d402402fe0ea70e
commit125448ca43165ecf404f792f7d402402fe0ea70e[log] [tgz]
authorSean Kelley <[email protected]>Tue Apr 26 17:26:10 2022 -0700
committerSean Kelley <[email protected]>Tue May 17 09:44:48 2022 -0700
tree9c434c538bf19b0a73c98bdc41025b9f5309c835
parent1d0bdb5edf9c9ddcadb5943d1dc442bd1a3a517e [diff]
Add exercise/passive listener/health event APIs

Relnote: """Measure
      - Callback methods were updated to include the name of the
        callback: registerCallback -> registerMeasureCallback.
    Passive
      - Added Health Events APIs. The first supported Health Event is
        fall detection.
      - Moved to a new set of listener APIs:
        - The broadcast was replaced by the PassiveListenerService.
        - The existing listeners were replaced with a single listener:
          PassiveListenerCallback
    Exercise
      - ExerciseState.ENDED was added and will be used instead of the
        multiple existing end states, with an end reason used to specify
        why the exercise has ended.
      - ExerciseUpdate now delivers exercise state through
        ExerciseStateInfo which contains both the current state and an
        end reason if appropriate.
    Added experimental DataTypes
      - ELEVATION_LOSS
      - GOLF_SHOT_COUNT
"""

Test: ./gradlew :health:health-services-client:assemble
Bug: 227475943
Change-Id: I22c27d70ddfbd3f8164cff1eedea53f5d956a25f
42 files changed
tree: 9c434c538bf19b0a73c98bdc41025b9f5309c835
  1. .github/
  2. .idea/
  3. activity/
  4. ads/
  5. annotation/
  6. appcompat/
  7. appsearch/
  8. arch/
  9. asynclayoutinflater/
  10. autofill/
  11. benchmark/
  12. biometric/
  13. bluetooth/
  14. browser/
  15. buildSrc/
  16. buildSrc-tests/
  17. busytown/
  18. camera/
  19. car/
  20. cardview/
  21. collection/
  22. collection2/
  23. compose/
  24. concurrent/
  25. contentpager/
  26. coordinatorlayout/
  27. core/
  28. cursoradapter/
  29. customview/
  30. datastore/
  31. development/
  32. docs/
  33. docs-public/
  34. docs-tip-of-tree/
  35. documentfile/
  36. draganddrop/
  37. drawerlayout/
  38. dynamicanimation/
  39. emoji/
  40. emoji2/
  41. enterprise/
  42. exifinterface/
  43. external/
  44. fakeannotations/
  45. fragment/
  46. frameworks/
  47. glance/
  48. gradle/
  49. gridlayout/
  50. health/
  51. heifwriter/
  52. hilt/
  53. ink/
  54. inspection/
  55. interpolator/
  56. jetifier/
  57. leanback/
  58. lifecycle/
  59. lint-checks/
  60. lint-demos/
  61. loader/
  62. media/
  63. media2/
  64. mediarouter/
  65. metrics/
  66. navigation/
  67. paging/
  68. palette/
  69. percentlayout/
  70. placeholder-tests/
  71. playground-common/
  72. preference/
  73. print/
  74. profileinstaller/
  75. recommendation/
  76. recyclerview/
  77. remotecallback/
  78. resourceinspection/
  79. room/
  80. samples/
  81. savedstate/
  82. security/
  83. sharetarget/
  84. slice/
  85. slidingpanelayout/
  86. sqlite/
  87. startup/
  88. swiperefreshlayout/
  89. test/
  90. testutils/
  91. text/
  92. tracing/
  93. transition/
  94. tvprovider/
  95. vectordrawable/
  96. versionedparcelable/
  97. viewpager/
  98. viewpager2/
  99. wear/
  100. webkit/
  101. window/
  102. work/
  103. .gitignore
  104. .mailmap
  105. build.gradle
  106. cleanBuild.sh
  107. code-review.md
  108. CONTRIBUTING.md
  109. gradle.properties
  110. gradlew
  111. include-composite-deps.gradle
  112. libraryversions.toml
  113. LICENSE.txt
  114. OWNERS
  115. PREUPLOAD.cfg
  116. README.md
  117. settings.gradle
  118. studiow
  119. TEXT_OWNERS
README.md

Android Jetpack

Revved up by Gradle Enterprise

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(), jcenter(), or mavenCentral(). We store copies of these dependencies to have hermetic builds. You can pull in a new dependency using our importMaven tool.