| /frameworks/native/cmds/flatland/ |
| D | README.txt | 28 in between each benchmark sample run. Regardless of the scenario being
49 The first column is simply a description of the scenario that's being
50 simulated. The second column indicates the resolution at which the scenario
53 scenario takes to complete.
57 fast - This indicates that frames of the scenario completed too fast to be
60 result, the scenario was skipped.
62 slow - This indicates that frames of the scenario took too long to
64 simulating a scenario that is obviously impractical on this device, the
65 scenario was skipped.
67 varies - This indicates that the scenario was measured, but it did not
[all …]
|
| D | Main.cpp | 689 const char* scenario = "Scenario"; in printResultsTableHeader() local
690 size_t len = strlen(scenario); in printResultsTableHeader()
|
| /frameworks/support/v7/recyclerview/tests/src/android/support/v7/widget/ |
| D | BaseWrapContentTest.java | 123 protected void testScenerio(Scenario scenario) throws Throwable { in testScenerio() argument
138 List<Snapshot> s1 = runScenario(scenario, matchParent, null); in testScenerio()
141 List<Snapshot> s2 = runScenario(scenario, wrapContent, s1); in testScenerio()
151 public List<Snapshot> runScenario(Scenario scenario, ViewGroup.LayoutParams lp, in runScenario() argument
157 RecyclerView.LayoutManager layoutManager = scenario.createLayoutManager(); in runScenario()
163 mTestAdapter = new TestAdapter(scenario.getSeedAdapterSize()); in runScenario()
170 for (Step step : scenario.mStepList) { in runScenario()
|
| /frameworks/base/docs/html/training/cloudsave/ |
| D | conflict-res.jd | 141 <p>Consider the scenario illustrated in Table 1. Suppose the player initially
247 <p>To illustrate, consider the scenario illustrated by Table 2. After the
328 <p><em>(*): x represents data that is irrelevant to our scenario.</em></p>
424 <p><em>(*): x represents data that is irrelevant to our scenario.</em></p>
465 Table 4 illustrates this, based on the scenario from Table 3. Note the following:</p>
|
| /frameworks/base/docs/html/guide/topics/ui/layout/ |
| D | relative.jd | 72 view declared in the hierarchy. The example below demonstrates such a scenario.</p>
|
| D | gridview.jd | 93 position (zero-based) of the selected item (in a real world scenario, the position could be used to
|
| /frameworks/base/docs/html/guide/practices/ |
| D | screens-distribution.jd | 102 <compatible-screens>}</a> element for the reverse scenario (when your application is not
173 <supports-screens>}</a> element for the reverse scenario (when your application is not compatible
|
| D | optimizing-for-3.0.jd | 523 <supports-screens>}</a> element for the reverse scenario (when your application is not compatible
584 <compatible-screens>}</a> element for the reverse scenario (when your application is not
647 <p>In the worst-case scenario, however, you can avoid orientation changes by using the <a
|
| /frameworks/base/docs/html/topic/performance/power/network/ |
| D | action-app-traffic.jd | 119 In this scenario, the problem is that an app is running a background process that keeps
|
| /frameworks/base/docs/html/guide/webapps/ |
| D | webview.jd | 46 <p>A common scenario in which using {@link android.webkit.WebView} is helpful is when you want to
52 <p>Another scenario in which {@link android.webkit.WebView} can help is if your application provides
|
| /frameworks/base/docs/html/about/versions/nougat/ |
| D | android-7.0-changes.jd | 403 directly, you should still test your app for this scenario.
814 must be able to gracefully handle this scenario. Otherwise, it crashes
885 the system requires user confirmation. In this scenario, apps should expect
|
| /frameworks/base/docs/html/training/design-navigation/ |
| D | multiple-sizes.jd | 95 …<p>In this scenario, the left pane is completely hidden in portrait mode. However, <em>to ensure t…
|
| /frameworks/base/docs/html/training/basics/activity-lifecycle/ |
| D | stopping.jd | 67 android.app.Activity#onResume()} (4). Notice that no matter what scenario causes the activity to
|
| /frameworks/base/docs/html/training/tv/discovery/ |
| D | recommendations.jd | 28 content. An ideal scenario for many TV users is: sit down, turn on, and watch. The fewest steps
|
| /frameworks/base/docs/html/training/gestures/ |
| D | scale.jd | 185 common scenario is <em>panning</em>, which is when a user's dragging motion causes scrolling
|
| D | scroll.jd | 49 necessary for special scenarios. This lesson describes such a scenario: displaying
|
| /frameworks/base/docs/html/google/play/billing/ |
| D | billing_promotions.jd | 140 Your app should also support the scenario where a user redeems a promo code
|
| /frameworks/base/docs/html/topic/arc/ |
| D | index.jd | 150 educational settings, it's a good idea to keep this scenario in mind.
|
| /frameworks/base/docs/html/training/scheduling/ |
| D | alarms.jd | 82 <p>A common scenario for triggering an operation outside the lifetime of your app is
|
| /frameworks/base/docs/html/training/articles/ |
| D | wear-permissions.jd | 107 scenario is the applicable one when Wear requests this data.</p>
|
| /frameworks/base/docs/html/guide/topics/appwidgets/ |
| D | host.jd | 279 For example, many hosts align icons and widgets in a grid. In this scenario,
|
| /frameworks/base/docs/html/topic/performance/ |
| D | launch-time.jd | 190 A warm start displays the same on-screen behavior as a cold start scenario:
|
| /frameworks/base/docs/html/guide/topics/location/ |
| D | strategies.jd | 354 scenario also describes good practices for when you should start and stop listening for the
|
| /frameworks/base/docs/html/guide/topics/providers/ |
| D | calendar-provider.jd | 521 scenario, a default time zone is supplied.</li>
534 scenario, you can use an {@link
|
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| D | activity_task_design.jd | 583 activity. This scenario demonstrates launching the Maps application.
761 This scenario shows how the user can switch between two tasks. In
|