| 9439d708170c7dd6c985453fd1999bbe8445eddf |
|
25-Oct-2016 |
Alan Viverette <alanv@google.com> |
Move all support library projects to use a single compilation unit
Also cleans up build files to include annotations as an explicit import,
set compileSdkVersion consistently to currentSdk, and remove unnecessary
lines. Removes obsolete API directories in VDC / AVDC.
Because NotificationCompatBase was using @removed APIs, updated that class
to use reflection. Also fixes method visibility in VDC / AVDC.
Bug: 29630077
Test: make and gradle builds successful
Change-Id: Ia9208246837347ce3d8df4adbe6b0ce406d3844a
/frameworks/support/v7/mediarouter/Android.mk
|
| 3bac6aa6a8caca1b8b3f9ea1f362f9b86f8a1a53 |
|
26-Sep-2016 |
Donghyun Cho <donghyun@google.com> |
Merge "MediaRouter: Apply styles in chooser dialog based on isLightTheme"
|
| 166da1fa21cc24216730da32c9b81c591349db87 |
|
23-Sep-2016 |
Donghyun Cho <donghyun@google.com> |
MediaRouter: Apply styles in chooser dialog based on isLightTheme
Unlike the controller dialog, colors of some components (background,
title) used in the chooser dialog is chosen based on the current theme,
while other components (icons, texts) are based on the isLightTheme
attribute. Therefore, when an application overrides the isLightTheme
attribute, the chooser dialog could become unusable.
This CL revisited the way of styling and theming of media router dialog
using theme overlay, so the appropriate theme overlay will be chosen and
applied based on the isLightTheme attribute.
In addition, this CL also includes the following:
- Use a custom text view for title instead of setting framework
dialog's title.
- Make the chooser dialog inherit AppCompatDialog not Dialog.
- When getting resources for views in the dialog, set the right
Context.
Bug: 28040912, Bug: 30500649
Test: Tested with Support7Demo app and checked theme.
Change-Id: I4d5104e1231435f0b0721fd0af91255d0fff6afc
/frameworks/support/v7/mediarouter/Android.mk
|
| 6e3bff7a3853a7e123a8a2909aacb75fd5c25953 |
|
22-Sep-2016 |
Vladislav Kaznacheev <kaznacheev@google.com> |
Fix sdk version for api24-specific libraries
SDK level for some api24 static libraries is still set
to "current". This means that using newer APIs in
these libraries would go undetected.
Changing to 24.
Test: try using API 25 in code under /api24, should fail
Change-Id: I8e48594427f3fd9a5a6d80090e79860f75e1b441
/frameworks/support/v7/mediarouter/Android.mk
|
| 7b59d3ae599949c7c6b4c5806b4dda7f41147690 |
|
13-Jun-2016 |
Alan Viverette <alanv@google.com> |
Remove old API check artifacts, invoke gradle from old make target
Fixes paths in build.gradle so they are relative to the project root,
rather than the current directory.
Bug: 28124434
Change-Id: Ieeae97cd789a6addf3282f2c43cd754ca8e84c57
/frameworks/support/v7/mediarouter/Android.mk
|
| 3c141cd9c1cfecd9352b82d9dae4d9601fabd4e6 |
|
11-Jun-2016 |
Yigit Boyar <yboyar@google.com> |
Revert "Remove old API check artifacts, invoke gradle from old make target"
This reverts commit 009647bbfa5efef608d6a660fc8ba191d876b1ed.
Change-Id: I59deae2a7180f58bc0c770f7b3f70962c8d2f73f
/frameworks/support/v7/mediarouter/Android.mk
|
| 009647bbfa5efef608d6a660fc8ba191d876b1ed |
|
09-Jun-2016 |
Alan Viverette <alanv@google.com> |
Remove old API check artifacts, invoke gradle from old make target
Fixes paths in build.gradle so they are relative to the project root,
rather than the current directory.
Bug: 28124434
Change-Id: I8cde9db47d60ec1220d35fce5ef6fd2c6e97b1f8
/frameworks/support/v7/mediarouter/Android.mk
|
| df153998b2e93117ec6fd9b799130a4fd7cc5960 |
|
04-May-2016 |
Kirill Grouchnikov <kirillg@google.com> |
Bump minSdk to 9 everywhere where it was < 9
Change-Id: Icebaa867824aa8eeda44206155670d5e390d35b3
/frameworks/support/v7/mediarouter/Android.mk
|
| 6759b1021d8198ad1d239bb30e5a102b99624bce |
|
25-Feb-2016 |
Adam Lesinski <adamlesinski@google.com> |
Build support libs with AAPT2
Use AAPT2 to build the framework support libraries. Apps built with AAPT2 can more efficiently
link against these libraries by specifying their module name in LOCAL_STATIC_ANDROID_LIBRARIES.
Ex:
LOCAL_STATIC_ANDROID_LIBRARIES := android-support-v7-appcompat android-support-v4
Apps built with AAPT2 do not need to specify --auto-add-overlay or --extra-packages, as these
are automatically added as needed by the build system.
This change will not affect any apps that currently depend on the support libraries.
This is because they import the resources directly.
We use LOCAL_JAR_EXCLUDE_FILES := none only to support javac when building javadoc.
Jack builds are correct because the build system passes in the latest generated R.java
ahead of any previous ones packaged in classes.jack. This means we can dynamically reference
a support lib module, correctly seeing non-final R.java. Then at app package time, we only
include the final R.java generated by the AAPT2 packaging step.
Bug:25958912
Change-Id: I6577a91e4d428dd29fecaa86a26be43d4da8310c
/frameworks/support/v7/mediarouter/Android.mk
|
| 57f39186667b8acef1a0ebeda585c357a751a8b3 |
|
02-Apr-2016 |
Adam Lesinski <adamlesinski@google.com> |
Revert "Build support libs with AAPT2"
This reverts commit 66b8608151c5923de3c9877bc03218d83f6b3beb.
Change-Id: I2178c0336bef8386e1f36ff3816b6dbf1e6a64d0
/frameworks/support/v7/mediarouter/Android.mk
|
| 66b8608151c5923de3c9877bc03218d83f6b3beb |
|
25-Feb-2016 |
Adam Lesinski <adamlesinski@google.com> |
Build support libs with AAPT2
Use AAPT2 to build the framework support libraries. Apps built with AAPT2 can more efficiently
link against these libraries by specifying their module name in LOCAL_STATIC_ANDROID_LIBRARIES.
Ex:
LOCAL_STATIC_ANDROID_LIBRARIES := android-support-v7-appcompat android-support-v4
Apps built with AAPT2 do not need to specify --auto-add-overlay or --extra-packages, as these
are automatically added as needed by the build system.
This change will not affect any apps that currently depend on the support libraries.
This is because they import the resources directly.
We use LOCAL_JAR_EXCLUDE_FILES := none only to support javac when building javadoc.
Jack builds are correct because the build system passes in the latest generated R.java
ahead of any previous ones packaged in classes.jack. This means we can dynamically reference
a support lib module, correctly seeing non-final R.java. Then at app package time, we only
include the final R.java generated by the AAPT2 packaging step.
Bug:25958912
Change-Id: I5235b73ac68f2050d089aefc3163901ff80f2d46
/frameworks/support/v7/mediarouter/Android.mk
|
| 4ac91fa3f14db2f25345595fb921497c11d4e5c0 |
|
31-Mar-2016 |
Adam Lesinski <adamlesinski@google.com> |
Revert "Build support libs with AAPT2"
This reverts commit 0dac8d82e2a249d7c9c42ab259389e11cac15400.
Change-Id: I830fb18162b6eea8dde9e38f9dc39b02449ec846
/frameworks/support/v7/mediarouter/Android.mk
|
| 0dac8d82e2a249d7c9c42ab259389e11cac15400 |
|
25-Feb-2016 |
Adam Lesinski <adamlesinski@google.com> |
Build support libs with AAPT2
Use AAPT2 to build the framework support libraries. Apps built with AAPT2 can more efficiently
link against these libraries by specifying their module name in LOCAL_STATIC_ANDROID_LIBRARIES.
Ex:
LOCAL_STATIC_ANDROID_LIBRARIES := android-support-v7-appcompat android-support-v4
Apps built with AAPT2 do not need to specify --auto-add-overlay or --extra-packages, as these
are automatically added as needed by the build system.
This change will not affect any apps that currently depend on the support libraries.
This is because they import the resources directly.
We use LOCAL_JAR_EXCLUDE_FILES := none only to support javac when building javadoc.
Jack builds are correct because the build system passes in the latest generated R.java
ahead of any previous ones packaged in classes.jack. This means we can dynamically reference
a support lib module, correctly seeing non-final R.java. Then at app package time, we only
include the final R.java generated by the AAPT2 packaging step.
Bug:25958912
Change-Id: I71bff080ff2694aa3df1c8a67d933e2daab0f245
/frameworks/support/v7/mediarouter/Android.mk
|
| e1cd5a1f80010eece43cb4608505fd39f4832c00 |
|
25-Feb-2016 |
Neil Fuller <nfuller@google.com> |
Pin support libraries to Java 1.7 so they can be used with dx
The .jar artifacts must contain v51 class files to prevent them
being rejected by dx.
Bug: 26753820
Bug: 27353172
Bug: 27338966
Change-Id: I03a881a86bb6e3fcaa4ccb33e6c0615157ee363f
/frameworks/support/v7/mediarouter/Android.mk
|
| 5002eef9e0ae91eea8b73b02fc5a5d1cb5b894f1 |
|
08-Feb-2016 |
Narayan Kamath <narayan@google.com> |
mediarouter: Fix api-check rule.
We're asking doclava to generate stubs for v7.app, so we
must point it at the corresponding sources. This also includes
an API update because the previous API definition was incorrectly
generated. It had no access to source so it would lose all
@deprecated information.
It's probably an error to overlap API definitions like this, and
that should be cleaned up in a follow up change.
(cherry picked from commit 65469b1fd471cba714505cacbda99ec82e27c0a4)
Change-Id: I5f311d8702ef44f03f7ce7f0f11a10f81a5be0d0
/frameworks/support/v7/mediarouter/Android.mk
|
| 82b55491586ac50a0f95b60e39a3c18d068941cf |
|
22-Jan-2016 |
Chris Banes <chrisbanes@google.com> |
Update support lib to use correct current SDK
BUG: 26714403
Change-Id: I2153dbda365f4552a14df1f432239bddfbbbef00
/frameworks/support/v7/mediarouter/Android.mk
|
| 96d4428ba99ad068679fca129e179e8187770d75 |
|
10-Nov-2015 |
Insun Kang <insun@google.com> |
MediaRouter: Let SystemMRP use a new framework API of v24
Bug: 24777080
Change-Id: I63d896f5cbee206b569a750899626fed7d8140a0
/frameworks/support/v7/mediarouter/Android.mk
|
| 95ad49b720f4990d39d05f7e46a5c7bc83afc9d6 |
|
19-Oct-2015 |
Chris Banes <chrisbanes@google.com> |
Fix multi source folder API checking
For libraries which have seperate source folders
per API level, the API generation doesn't currently
work correctly. When generating the stubs, we need to
input all source files, not just the final module.
This has uncovered some file in support-v4 which should
not be public API.
BUG: 20822048
Change-Id: I6216b9688e745db212959a07fcdc21bdd0aa5ab2
/frameworks/support/v7/mediarouter/Android.mk
|
| 005482649154d0970693b3967241eb4d2cb22003 |
|
19-Aug-2015 |
Jaewan Kim <jaewan@google.com> |
MediaRouter: Show full height of the artwork
Here's the spec.
- When artwork is available, the full height of the artwork is shown
(not cropped).
- When artwork is only available in portrait format, the art is
proportionally scaled to fit 16:9 ratio. Also, the background behind
the art is color-sampled using the artwork's dominant color.
Bug: 23117558
Change-Id: I6c1ce0aa465f47848fcc66b52d0b4aae5bd23aeb
/frameworks/support/v7/mediarouter/Android.mk
|
| c06f9cfb73483e8ec554cdda029cea9a2c20a970 |
|
17-Jul-2015 |
Dongwon Kang <dwkang@google.com> |
MediaRouter: use AlertDialog in support library which supports material theme
Bug: 22491447
Change-Id: Id4a023e82c8169d516abbba7240ec4624d8b049d
/frameworks/support/v7/mediarouter/Android.mk
|
| 33a0fe195c12aab6d30f7d801b167d1d10d226f8 |
|
17-Jul-2015 |
Dongwon Kang <dwkang@google.com> |
Revert "MediaRouter: use AlertDialog in support library which supports material theme"
This reverts commit d5451959bc11309b1a077ceb909170627e0ec47c.
/frameworks/support/v7/mediarouter/Android.mk
|
| d5451959bc11309b1a077ceb909170627e0ec47c |
|
16-Jul-2015 |
Dongwon Kang <dwkang@google.com> |
MediaRouter: use AlertDialog in support library which supports material theme
Bug: 22491447
Change-Id: Id2cbff1296bf43373e5aec49bd5575acaf51ca72
/frameworks/support/v7/mediarouter/Android.mk
|
| 639640523bdb81cc5a2ac2a1ebbe0c4e13a2c82b |
|
30-Apr-2015 |
Chris Banes <chrisbanes@google.com> |
Use doclava's new stubpackages wildcard support
Depends-on: Ibd49cc0348e2767b2c0fe6f14e7253b6d8e04c7b
Change-Id: I740a2b55156a3d5d296be390b799f9118b1820df
/frameworks/support/v7/mediarouter/Android.mk
|
| f62fcdec92e2f96ec61579392ed2b593cff35b39 |
|
25-Feb-2015 |
Chris Banes <chrisbanes@google.com> |
Generate API files for the support libraries
make update-support-api
make check-support-api (run automatically on sdk builds)
BUG: 19478450
Change-Id: Idd0f12c457b7dc084a66158de452969d7afdb8dc
/frameworks/support/v7/mediarouter/Android.mk
|
| fcec1282de632ec009109ae3f93a25fea97fc170 |
|
18-Nov-2014 |
Griff Hazen <griff@google.com> |
Compile support library libs at proper sdk levels
Fix a few cases of current -> 21 and one case of current -> 18.
This helps avoid future level sdk features from sneaking in.
Bug: 18429742
Change-Id: Id9671eaaa7ee0638951b414f7d2127592eb264d2
/frameworks/support/v7/mediarouter/Android.mk
|
| 16b9c32acfd3e6c96bd5571742bd09927f53bffe |
|
21-May-2013 |
Ying Wang <wangying@google.com> |
Clean up dist files.
Change-Id: Ib22ec5e867955a71d4e42db0d2c56775fe37a4ae
/frameworks/support/v7/mediarouter/Android.mk
|
| 11417b1cfde8f1749905f2d735623af9214148af |
|
27-Apr-2013 |
Jeff Brown <jeffbrown@google.com> |
Add media router picker UI.
Introduced the concept of a MediaRouteSelector which is the means
by which an application states the route capabilities of routes
that it would like to discover.
Added selectors to the addCallback method along with several
other methods to assist with discovery. Callbacks can specify
flags to perform active scans of routes or to disable filtering
of route events.
Added a workaround to scan for wifi displays on JB MR1.
Refactored the route descriptor objects to use the builder pattern
instead of simply documenting that they should be immutable
since several developers have already tripped over this.
The UI is feature complete but not final.
Bug: 8175766
Change-Id: I54ebb7488222746b0c07292e65b9ded1b9d720fa
/frameworks/support/v7/mediarouter/Android.mk
|
| b507e525a61ed761eecfc2eaaf19af7e8db5dca5 |
|
20-Mar-2013 |
Jeff Brown <jeffbrown@google.com> |
Move support library media router to v7 package.
Resolved some TODOs related to missing resources.
Bug: 8175766
Change-Id: I57632d0a961de58a5dd53e889b4fd39832b5fba0
/frameworks/support/v7/mediarouter/Android.mk
|