Gitiles
Code Review Sign In
review.blissroms.org / platform_frameworks_support / a2c596edf8ff3f9cb092e94d460a9e1985a584a5
commita2c596edf8ff3f9cb092e94d460a9e1985a584a5[log] [tgz]
authorAga Madurska <amad@google.com>Thu Nov 09 15:40:37 2017 +0000
committerAlan Viverette <alanv@google.com>Mon Nov 20 15:50:34 2017 +0000
tree216983118caf79b05bc4d700221dfb5757805308
parente00a16bc7a72580ba002e90efe65b6d10a4c6c38 [diff]
Add support for smart resume to AmbientMode.

The behavior of the class is now as follows:
1. If attached to an Activity which implements the
AmbientMode.AmbientCollbackProvider then ambient
mode is set to enabled and will pass callback to
the supplied callback.

2. If attached to an Activity which does not implement
the callback mentioned above: enables smart auto resume.

3. If not attached to any Activity as all - no
ambient support and no smart resume support.

Bug: 64540413
Test: run ./gradlew wear:connectedCheck

Change-Id: Id5873140109870bb74d997b01994988410b2c725
6 files changed
tree: 216983118caf79b05bc4d700221dfb5757805308
  1. .idea/
  2. annotations/
  3. api/
  4. app-toolkit/
  5. buildSrc/
  6. car/
  7. compat/
  8. content/
  9. core-ui/
  10. core-utils/
  11. customtabs/
  12. design/
  13. development/
  14. dynamic-animation/
  15. emoji/
  16. exifinterface/
  17. fragment/
  18. frameworks/
  19. gradle/
  20. graphics/
  21. lifecycle/
  22. media-compat/
  23. paging/
  24. percent/
  25. persistence/
  26. recommendation/
  27. recyclerview-selection/
  28. room/
  29. samples/
  30. scripts/
  31. testutils/
  32. transition/
  33. tv-provider/
  34. v13/
  35. v14/
  36. v17/
  37. v4/
  38. v7/
  39. wear/
  40. webkit/
  41. .gitignore
  42. Android.mk
  43. build.gradle
  44. CleanSpec.mk
  45. gradle.properties
  46. gradlew
  47. LICENSE.txt
  48. makeFlatfootRepo.sh
  49. OWNERS
  50. pathmap.mk
  51. PREUPLOAD.cfg
  52. README.md
  53. settings.gradle
README.md

AOSP Support Library Contribution Guide

Accepted Types of Contributions

  • Bug fixes (needs a corresponding bug report in b.android.com)
  • 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

We are not currently accepting new modules, features, or behavior changes.

Checking Out the Code

NOTE: You will need to use Linux or Mac OS. Building under Windows is not currently supported.

Follow the “Downloading the Source” guide to install and set up repo tool, but instead of running the listed repo commands to initialize the repository, run the folowing:

repo init -u https://android.googlesource.com/platform/manifest -b ub-supportlib-master

Now your repository is set to pull only what you need for building and running support library. Download the code (and grab a coffee while we pull down 7GB):

repo sync -j8 -c

You will use this command to sync your checkout in the future - it’s similar to git fetch

Using Android Studio

Open path/to/checkout/frameworks/support/ in Android Studio. Now you're ready edit, run, and test!

If you get “Unregistered VCS root detected” click “Add root” to enable git integration for Android Studio.

If you see any warnings (red underlines) run Build > Clean Project.

Optional - Full Build

You can do most of your work from Android Studio, however you can also build the full support library from command line:

cd path/to/checkout/frameworks/support/
./gradlew createArchive

Running Tests

Single Test Class or Method

  1. Open the desired test file in Android Studio.
  2. Right-click on a test class or @Test method name and select Run FooBarTest

Full Test Package

  1. In the project side panel open the desired module.
  2. Find the directory with the tests
  3. Right-click on the directory and select Run android.support.foobar

Running Sample Apps

Support library has a set of Android applications that exercise support library code. These applications can be useful when you want to debug a real running application, or reproduce a problem interactively, before writing test code.

These applications are named support-*-demos (e.g. support-4v-demos or support-leanback-demos. You can run them by clicking Run > Run ... and choosing the desired application.

Making a change

cd path/to/checkout/frameworks/support/
repo start my_branch_name .
(make needed modifications)
git commit -a
repo upload --current-branch .

If you see the following prompt, choose always:

Run hook scripts from https://android.googlesource.com/platform/manifest (yes/always/NO)?

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)