/frameworks/ml/bordeaux/service/src/android/bordeaux/services/ |
D | TimeStatsAggregator.java | 80 HashMap<String, String> features = in getFeatureValue() local 82 if (features.containsKey(featureName)) { in getFeatureValue() 83 feature.put(featureName, features.get(featureName)); in getFeatureValue() 135 HashMap<String, String> features = new HashMap<String, String>(); in getAllTimeFeatures() local 143 features.put(PERIOD_OF_DAY, DAYTIME); in getAllTimeFeatures() 145 features.put(PERIOD_OF_DAY, NIGHTTIME); in getAllTimeFeatures() 147 features.put(TIME_OF_DAY, mFakeTimeOfDay); in getAllTimeFeatures() 149 features.put(PERIOD_OF_DAY, getPeriodOfDay(time.hour)); in getAllTimeFeatures() 150 features.put(TIME_OF_DAY, getTimeOfDay(time.hour)); in getAllTimeFeatures() 154 features.put(DAY_OF_WEEK, mFakeDayOfWeek); in getAllTimeFeatures() [all …]
|
D | FeatureAssembly.java | 54 public boolean registerFeaturePair(String[] features) { in registerFeaturePair() argument 55 if (features.length != 2 || in registerFeaturePair() 56 !mPossibleFeatures.contains(features[0]) || in registerFeaturePair() 57 !mPossibleFeatures.contains(features[1])) { in registerFeaturePair() 60 mUseFeatures.add(features[0]); in registerFeaturePair() 61 mUseFeatures.add(features[1]); in registerFeaturePair() 62 mUsePairedFeatures.add(Pair.create(features[0], features[1])); in registerFeaturePair() 77 Map<String, String> features = mAggregatorManager.getDataMap(f); in getFeatureMap() local 80 if (features.size() > 1) { in getFeatureMap() 83 featureMap.putAll(features); in getFeatureMap()
|
D | Predictor.java | 118 Map<String, String> features = getSampleFeatures(); in getTopCandidates() local 119 List<Map.Entry<String, Double> > topApps = mPredictor.findTopClasses(features, topK); in getTopCandidates() 143 String[] features = value.split(FEATURE_SEPARATOR); in setPredictorParameter() local 144 result = mFeatureAssembly.registerFeaturePair(features); in setPredictorParameter()
|
/frameworks/base/core/java/android/content/pm/ |
D | FeatureGroupInfo.java | 33 public FeatureInfo[] features; field in FeatureGroupInfo 39 features = other.features; in FeatureGroupInfo() 49 dest.writeTypedArray(features, flags); in writeToParcel() 56 group.features = source.createTypedArray(FeatureInfo.CREATOR);
|
/frameworks/base/docs/html/training/tv/start/ |
D | hardware.jd | 12 <li><a href="#handle-features">Handle Unsupported Hardware Features</a></li> 21 include some of the hardware features found on other Android devices, such as touch screens, 30 hardware features, and discusses the requirements for handling controllers for TV devices. 63 <h2 id="handle-features">Handle Unsupported Hardware Features</h2> 67 hardware features being unavailable. This section discusses what hardware features are typically 68 not available for TV, how to detect missing hardware features, and suggests alternatives to 69 using these features. 73 <h3 id="unsupported-features">Unsupported TV hardware features</h3> 76 TVs have a different purpose from other devices, and so they do not have hardware features that 78 the following features for a TV device: [all …]
|
/frameworks/compile/libbcc/lib/Support/ |
D | CompilerConfig.cpp | 103 llvm::StringMap<bool> features; in initializeArch() local 104 llvm::sys::getHostCPUFeatures(features); in initializeArch() 127 if (features.count("hwdiv-arm") && features["hwdiv-arm"]) in initializeArch() 130 if (features.count("hwdiv") && features["hwdiv"]) in initializeArch()
|
/frameworks/base/docs/html/distribute/monetize/ |
D | freemium.jd | 16 user, such as additional app features. 25 A basic approach is to offer a free download with limited features or full 26 features for a limited time. Then use an in-app purchase to unlock the full, 47 A more advanced approach is to offer a range of features and content items 49 levels, playing pieces, or other game features. In apps you can offer 50 features or functionality that enhance the user experience either by 51 extending existing features or offering new ones. Using this approach you can 65 your apps, and add the mechanisms to unlock features or deliver content.
|
D | subscriptions.jd | 38 A more advanced approach is to offer specific features or content items as 40 features or content for free or part of the initial purchase and extended 41 features or content as subscriptions. You can have multiple subscriptions 52 API into your apps, and add the mechanisms to unlock subscribed features or
|
/frameworks/opt/bitmap/src/com/android/bitmap/drawable/ |
D | ExtendedBitmapDrawable.java | 93 if ((mOpts.features & ExtendedOptions.FEATURE_STATE_CHANGES) != 0) { in onOptsChanged() 674 public final int features; field in ExtendedBitmapDrawable.ExtendedOptions 746 public ExtendedOptions(final int features) { in ExtendedOptions() argument 747 this(features, null, null); in ExtendedOptions() 753 public ExtendedOptions(final int features, final Drawable placeholder, in ExtendedOptions() argument 755 this.features = features; in ExtendedOptions() 772 if ((features & FEATURE_ORDERED_DISPLAY) != 0 && decodeAggregator == null) { in validate() 777 if ((features & FEATURE_PARALLAX) != 0 && parallaxSpeedMultiplier <= 1) { in validate() 782 if ((features & FEATURE_STATE_CHANGES) != 0) { in validate()
|
/frameworks/base/docs/html/guide/topics/manifest/ |
D | uses-feature-element.jd | 2 page.tags=filtering,features,google play filters,permissions 13 <li><a href="#declared">Filtering based on explicitly declared features</a></li> 14 <li><a href="#implicit">Filtering based on implicit features</a></li> 16 <li><a href="#testing">Testing the features required by your application</a></li> 19 <li><a href="#features-reference">Features Reference</a> 21 <li><a href="#hw-features">Hardware features</a></li> 22 <li><a href="#sw-features">Software features</a></li> 38 <p style="margin-top:1em;">By specifying the features that your application requires, 44 Google Play uses features as the basis for filtering, please read <a 69 any external entity of the set of hardware and software features on which your [all …]
|
/frameworks/base/core/java/android/accounts/ |
D | AbstractAccountAuthenticator.java | 119 String authTokenType, String[] features, Bundle options) in addAccount() argument 124 + ", features " + (features == null ? "[]" : Arrays.toString(features))); in addAccount() 130 accountType, authTokenType, features, options); in addAccount() 252 Account account, String[] features) throws RemoteException { in hasFeatures() argument 256 new AccountAuthenticatorResponse(response), account, features); in hasFeatures() 482 Account account, String[] features) throws NetworkErrorException; in hasFeatures() argument
|
/frameworks/base/docs/html/distribute/stories/ |
D | games.jd | 10 lets you add great social features to your games quickly, without having to 12 variety of other features — all from within your app. Google provides 19 advantage of Google Play game services — the features they've added and
|
/frameworks/native/opengl/tools/glgen2/registry/ |
D | reg.py | 856 def markRequired(self, features, required): argument 862 for typeElem in features.findall('type'): 864 for enumElem in features.findall('enum'): 872 for cmdElem in features.findall('command'): 967 for features in interface.findall('require'): 968 for t in features.findall('type'): 971 for e in features.findall('enum'): 974 for c in features.findall('command'): 1001 features = [] 1013 features.append(fi) [all …]
|
/frameworks/base/docs/html/guide/topics/ui/accessibility/ |
D | index.jd | 49 <p>Android provides accessibility features and services for helping these users navigate their 55 enhanced usability features such as audio prompting, physical feedback, and alternative navigation 66 <dd>Development practices and API features to ensure your application is accessible to users with 77 <dd>How to use API features to build services that make other applications more accessible for
|
/frameworks/base/docs/html/training/material/ |
D | compatibility.jd | 23 <p>Some material design features like the material theme and custom activity transitions are 25 use of these features when running on devices that support material design and still be compatible 67 <p>The <a href="{@docRoot}tools/support-library/features.html#v7">v7 Support Libraries</a> 68 r21 and above includes the following material design features:</p> 128 <p>To use these features in versions of Android earlier than 5.0 (API level 21), include the 143 <p>The following features are available only in Android 5.0 (API level 21) and above:</p> 156 features:</p> 169 attributes in your manifest file. To use the material design features in Android 5.0, set
|
/frameworks/compile/mclinker/tools/mcld/lib/ |
D | TripleOptions.cpp | 158 llvm::SubtargetFeatures features; in parse() local 160 features.AddFeature(m_MAttrs[i]); in parse() 161 feature_str = features.getString(); in parse()
|
/frameworks/base/docs/html/guide/practices/ |
D | compatibility.jd | 12 <li><a href="#Features">Device features</a></li> 77 device configuration. Because Android runs on a wide range of device configurations, some features … 88 <p>Android supports a variety of features your app can leverage through platform APIs. Some 89 features are hardware-based (such as a compass sensor), some are software-based (such as app 92 features.</p> 97 disabling optional features at runtime and <a 105 <li><a href="#Features">Device features</a> 111 <h3 id="Features">Device features</h3> 113 <p>In order for you to manage your app’s availability based on device features, 137 <p>Google Play Store compares the features your app requires to the features available on [all …]
|
/frameworks/ml/bordeaux/learning/predictor_histogram/java/android/bordeaux/learning/ |
D | HistogramPredictor.java | 202 public List<Map.Entry<String, Double> > findTopClasses(Map<String, String> features, int topK) { in findTopClasses() argument 212 if (features.containsKey(featureName)) { in findTopClasses() 213 String featureValue = features.get(featureName); in findTopClasses() 274 public void addSample(String sampleId, Map<String, String> features) { in addSample() argument 275 for (Map.Entry<String, String> entry : features.entrySet()) { in addSample()
|
/frameworks/base/docs/html-intl/intl/ja/training/tv/start/ |
D | hardware.jd | 12 <li><a href="#handle-features">サポートされていないハードウェア機能を処理する</a></li> 50 <h2 id="handle-features">サポートされていないハードウェア機能を処理する</h2> 57 <h3 id="unsupported-features">サポートされていない TV ハードウェア機能</h3> 167 …="{@docRoot}guide/topics/manifest/uses-feature-element.html#permissions-features">{@code uses-feat… 171 <h3 id="check-features">ハードウェア機能をチェックする</h2> 222 Log.d("Camera test", "No camera available. View and edit features only.");
|
/frameworks/base/core/java/android/provider/ |
D | CallLog.java | 388 int presentation, int callType, int features, PhoneAccountHandle accountHandle, in addCall() argument 390 return addCall(ci, context, number, presentation, callType, features, accountHandle, in addCall() 420 int presentation, int callType, int features, PhoneAccountHandle accountHandle, in addCall() argument 458 values.put(FEATURES, features); in addCall()
|
/frameworks/base/tools/aapt/ |
D | Command.cpp | 490 KeyedVector<String8, bool> features; member 517 const size_t numFeatures = grp.features.size(); in printFeatureGroup() 519 const bool required = grp.features[i]; in printFeatureGroup() 521 const String8& featureName = grp.features.keyAt(i); in printFeatureGroup() 530 if (grp.features.indexOfKey(impliedFeature.name) >= 0) { in printFeatureGroup() 557 grp->features.add(String8("android.hardware.camera"), true); in addParentFeatures() 560 grp->features.add(String8("android.hardware.location"), true); in addParentFeatures() 562 grp->features.add(String8("android.hardware.touchscreen"), true); in addParentFeatures() 564 grp->features.add(String8("android.hardware.touchscreen.multitouch"), true); in addParentFeatures() 565 grp->features.add(String8("android.hardware.touchscreen"), true); in addParentFeatures() [all …]
|
/frameworks/base/docs/html/guide/topics/media/ |
D | camera.jd | 22 <li><a href="#check-camera-features">Checking camera features</a></li> 31 <li><a href="#camera-features">Camera Features</a> 34 <li><a href="#using-features">Using camera features</a></li> 57 <p>The Android framework includes support for various cameras and camera features available on 117 related features.</p> 128 <li><strong>Camera Features</strong> - Your application must also declare use of camera features, 133 <p>For a list of camera features, see the manifest 134 <a href="{@docRoot}guide/topics/manifest/uses-feature-element.html#hw-features">Features 136 <p>Adding camera features to your manifest causes Google Play to prevent your application from 137 being installed to devices that do not include a camera or do not support the camera features you [all …]
|
/frameworks/base/docs/html/tools/support-library/ |
D | index.jd | 16 <li><a href="{@docRoot}tools/support-library/features.html"> 26 backward-compatible versions of Android framework APIs as well as features that are only available 28 level. This design means that your applications can use the libraries' features and still be 31 <p>This guide provides information about what features are enabled by the Support Libraries, 39 …and the APIs that it uses. Using the features the libraries provide can help you improve the look … 46 of features. In order to effectively use the libraries, it is important to consider what features 47 you want to support and understand what features are supported by each library at what Android 49 <a href="{@docRoot}tools/support-library/features.html">Support Library Features</a> guide. 69 <dt>Changes for <a href="features.html#v4">v4 support library:</a></dt> 96 <dt>Changes for <a href="features.html#v4">v4 support library:</a></dt> [all …]
|
/frameworks/base/docs/html/guide/ |
D | index.jd | 57 <p>You can query the availability of device features at runtime if any app features require 58 specific hardware such as a camera. If necessary, you can also declare features your app requires
|
/frameworks/base/docs/html/distribute/essentials/best-practices/ |
D | apps.jd | 28 Build your apps to make best use of the unique Android features, such as 39 Add the power of Google features your users already love, such as 79 rollouts</a> features to test with users before launch. 168 Billing</a> to offer subscriptions to extended features. 237 your apps</a> to offer new and better features, or retire those that
|