| d3edfde51bd069a63e820282421d1a534fcf00ce |
09-Aug-2014 |
Adam Lesinski <adamlesinski@google.com> |
Add FeatureGroup to PackageInfo
FeatureGroups replace top-level FeatureInfo objects.
FeatureGroups inherit top-level FeatureInfos but override
them if the feature names are the same.
Bug:16822121
Change-Id: I80b2cb778a0fbcb4521efce986fba641e0914290
ndroidManifest.xml
|
| d7a94da476e9b783acf0673ed938cc3fc2cc6ba5 |
25-Jul-2014 |
Adam Lesinski <adamlesinski@google.com> |
Have AEP GL feature depend on GLES 3.1 in badging
AAPT dump badging should output the uses-gl-es tag with
a version of 3.1 when android.hardware.opengles.aep is
declared as a feature.
Change-Id: I8affc6dad574c8303c6ba9810ad8e6e205ea9506
ndroidManifest.xml
|
| 2c72b6822debb08fe997926eedc110f62d287d34 |
24-Jun-2014 |
Adam Lesinski <adamlesinski@google.com> |
Add <feature-group> tag and change aapt badging
A <feature-group> represents a set of features required
for an app to be compatible with a device. Multiple
<feature-group> elements represent a logical 'or'
of required features.
Features defined in the old way with <uses-feature> tags
under the <manifest> tag are automatically added to each
feature-group defined.
Defining a <feature-group> means that any default
features are not included (such as android.hardware.touchscreen)
and declared permissions do not imply any features.
Change-Id: I45626f0fdc546e47bcf2aead7ef05ebcca12b023
ndroid.mk
ndroidManifest.xml
es/values/values.xml
|