| /prebuilts/go/linux-x86/src/cmd/pprof/ |
| README | 8 to follow in your own.
|
| /prebuilts/ndk/current/sources/cxx-stl/stlport/stlport/stl/ |
| _ioserr.h | 11 # error STLport iostreams header cannot be used; your compiler do not support it.
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/plat-mac/ |
| bgenlocations.py | 3 # Edit this file to reflect where things should be on your system.
29 # if you want to commit your changes to the CVS repository this should refer to
30 # your source directory, not your installed directory.
|
| /prebuilts/tools/common/m2/repository/com/sun/xml/bind/mvn/jaxb-codemodel-parent/2.2.11/ |
| jaxb-codemodel-parent-2.2.11.pom | 26 enclosed by brackets [] replaced by your own identifying information:
30 If you wish your version of this file to be governed by only the CDDL or
31 only the GPL Version 2, indicate your decision by adding "[Contributor]
34 recipient has the option to distribute your version of this file under
|
| /system/core/logd/ |
| README.auditd | 8 To enable the audit subsystem, you must add this to your
|
| /toolchain/binutils/binutils-2.25/etc/ |
| add-log.vi | 10 in your $HOME/.exrc and when you type control-X in move-around-mode,
|
| /frameworks/base/docs/html/training/camera/ |
| photobasics.jd | 48 running your client app. Integrating photos is only a small part of your
57 <p>If an essential function of your application is taking pictures, then restrict
59 that your application depends on having a camera, put a <a
61 <uses-feature>}</a> tag in your manifest file:</p>
71 <p>If your application uses, but does not require a camera in order to function, instead set {@code
73 camera to download your application. It's then your responsibility to check for the availability
76 If a camera is not available, you should then disable your camera features.</p>
84 and some code to handle the image data when focus returns to your activity.</p
[all...] |
| /frameworks/base/docs/html/training/testing/start/ |
| index.jd | 59 <p>When using Android Studio to write any of your tests, your test code must go
61 your project, Android Studio includes both source sets, corresponding to the
80 your app under test. The system runs your test APK and your app under tests in
81 the same process, so your tests can invoke methods and modify fields in the
82 app, and automate user interaction with your app.</p>
117 described above are just terms that help distinguish the tests that run on your
147 tests to minimize execution time when your tests have no Android framewor
[all...] |
| /frameworks/base/core/java/android/content/ |
| SearchRecentSuggestionsProvider.java | 28 * This superclass can be used to create a simple search suggestions provider for your application.
38 * <li>Create a Content Provider within your application by extending
42 * <i>configures</i> the provider to match the requirements of your searchable activity.</li>
43 * <li>Create a manifest entry describing your provider. Typically this would be as simple
48 * android:authorities="your.suggestion.authority" /></pre>
51 * your code. This is done automatically by the system Content Resolver, when the search dialog
53 * <li>In order for the Content Resolver to do this, you must update your searchable activity's
54 * XML configuration file with information about your content provider. The following additions
57 * android:searchSuggestAuthority="your.suggestion.authority"
60 * <li>In your searchable activities, capture any user-generated queries and record the
[all...] |
| /frameworks/base/docs/html/guide/topics/search/ |
| search-dialog.jd | 22 <li><a href="#LifeCycle">The impact of the search dialog on your activity lifecycle</a></li>
62 <p>When you're ready to add search functionality to your application, Android helps you implement
64 search widget that you can insert in your layout. Both the search dialog and the widget can deliver
65 the user's search query to a specific activity in your application. This way, the user can initiate
74 <li>Search suggestions that match actual results in your application data</li>
77 <p>This guide shows you how to set up your application to provide a search interface
89 <p>Before you begin, you should decide whether you'll implement your search interface using the
102 you can place anywhere in your layout. By default, the search widget behaves like a standard {@link
117 set up your application for this kind of assisted search, you need the following:</p>
124 <p>The {@link android.app.Activity} that receives the search query, searches your
[all...] |
| /frameworks/base/core/java/android/app/job/ |
| JobService.java | 36 * you will implement your job logic.</p>
37 * <p>This service executes each incoming job on a {@link android.os.Handler} running on your
38 * application's main thread. This means that you <b>must</b> offload your execution logic to
39 * another thread/handler/{@link android.os.AsyncTask} of your choosing. Not doing so will result
221 * Override this method with the callback logic for your job. Any such logic needs to be
222 * performed on a separate thread, as this function is executed on your application's main
227 * @return True if your service needs to process the work (on a separate thread). False if
233 * This method is called if the system has determined that you must stop execution of your job
238 * {@link android.app.job.JobInfo.Builder#setRequiredNetworkType(int)}, yet while your
241 * idle maintenance window. You are solely responsible for the behaviour of your applicatio
[all...] |
| /frameworks/base/docs/html/training/sync-adapters/ |
| creating-authenticator.jd | 43 The sync adapter framework assumes that your sync adapter transfers data between device storage
45 framework expects you to provide a component called an authenticator as part of your sync
50 Even if your app doesn't use accounts, you still need to provide an authenticator component.
65 To add a stub authenticator component to your app, create a class that extends
139 In order for the sync adapter framework to access your authenticator, you must create a bound
141 to call your authenticator and pass data between the authenticator and the framework.
179 To plug your authenticator component into the sync adapter and account frameworks, you need to
181 account type you've created for your sync adapter and declares user interface elements
182 that the system displays if you want to make your account type visible to the user. Declare this
183 metadata in a XML file stored in the {@code /res/xml/} directory in your app project
[all...] |
| /frameworks/base/docs/html/tv/ |
| index.jd | 6 page.metaDescription=Bring your apps, games, and content to the biggest screen in the house.
54 <a class="landing-down-arrow" href="#reimagine-your-app">
62 <div class="landing-section" style="background-color:#f5f5f5" id="reimagine-your-app">
66 <div class="landing-h1">Reimagine Your App</div>
68 Design your app to shine on the biggest screen in the house.
77 and light. <br>Bring your content forward to let users enjoy it with a minimum of
93 Android TV lets you engage your users in a new, shared environment.<br>
94 Find out how to get your app ready for its big-screen debut.
122 Help users find your content quickly with in-app searching.
135 Suggest content from your app to keep your users coming back
[all...] |
| /frameworks/base/docs/html/guide/topics/manifest/ |
| compatible-screens-element.jd | 38 element</strong>. Using this element can dramatically reduce the potential user base for your
39 application, by not allowing users to install your application if they have a device with a screen
47 <p>If you want to set only a minimum screen <em>size</em> for your your application, then you
49 <supports-screens>}</a> element. For example, if you want your application to be available
52 <supports-screens>}</a> element allows you to declare that your application does not
54 Play) will filter your application accordingly. You can also use the <a
56 <supports-screens>}</a> element to declare whether the system should resize your
114 <p>If your application is compatible with only small and normal screens, regardless
118 configuration with which your application is <em>not</em> compatible. Here's what the manifes
[all...] |
| /frameworks/base/docs/html/training/graphics/opengl/ |
| draw.jd | 47 structure (the original coordinates) of the shapes you use in your program change during the course
49 android.opengl.GLSurfaceView.Renderer#onSurfaceCreated onSurfaceCreated()} method of your renderer
112 the OpenGL ES environment. To compile this code, create a utility method in your renderer class:</p>
129 <p>In order to draw your shape, you must compile the shader code, add them to a OpenGL ES program
130 object and then link the program. Do this in your drawn object?s constructor, so it is only done
135 not know the content of your shaders at runtime, you should build your code such that they only
167 <p>At this point, you are ready to add the actual calls that draw your shape. Drawing shapes with
169 to draw and how to draw it. Since drawing options can vary by shape, it's a good idea to have your
213 {@code draw()} method from within your renderer?s {@lin
[all...] |
| /frameworks/base/docs/html/training/sharing/ |
| receive.jd | 19 <li><a href="#update-manifest">Update Your Manifest</a></li>
33 <p>Just as your application can send data to other applications, so too can it easily receive data
34 from applications. Think about how users interact with your application, and what data types you
43 <h2 id="update-manifest">Update Your Manifest</h2>
49 define an intent filter in your manifest, using the
52 element. For example, if your application handles receiving text content, a single image of any
53 type, or multiple images of any type, your manifest would look like:</p>
80 it to {@link android.content.Context#startActivity(android.content.Intent) startActivity()}, your
81 application will be listed as an option in the intent chooser. If the user selects your application,
83 is then up to you to handle the content appropriately within your code and UI.</p
[all...] |
| /frameworks/base/docs/html/google/play/billing/ |
| billing_admin.jd | 31 <li>Setting up and maintaining your product list on the Google Play Developer Console.</li>
38 already have a publisher account on Google Play, you can use your existing account. You do not
43 <p>If you want to create a product list and issue refunds to your users, you must have a
49 <p>The Google Play Developer Console provides a product list for each of your published
55 page for an app that is listed in your developer account. The link to the
60 Updating Your App's Manifest</a>.</p>
67 <p>The product list stores only metadata about the items you are selling in your app.
69 the digital content that you sell in your apps.</p>
87 comma-separated values (CSV) file. Adding items one at a time is useful if your
89 product list for testing purposes. The CSV file method is useful if your app has a larg
[all...] |
| billing_subscriptions.jd | 4 page.metaDescription=Create a steady revenue stream by selling subscriptions to your content.
32 <p>Subscriptions let you sell content, services, or features in your app with
48 <li>Users purchase your subscriptions from inside your apps, rather than
61 lets you sell content, services, or features to users from inside your app with
74 <p>When users purchase subscriptions in your apps, Google Play handles all
75 checkout details so your apps never have to directly process any financial
78 This ensures a consistent and familiar purchase flow for your users.</p>
89 content (for example, from your web site or another service).
91 sign into your other services. For more information about the API, see <
[all...] |
| /frameworks/base/docs/html/training/wearables/apps/ |
| always-on.jd | 1 page.title=Keeping Your App Visible
30 so you should carefully consider that impact when adding this feature to your app.
44 <p>This lesson describes how to enable your wearable app to be always-on, update the screen
50 <p>For new and existing projects, you can add ambient mode support to your Wear app by updating
51 your development project configuration. After you complete the project configuration, extend the
53 class, which provides all the methods you need to enable ambient mode in your app. The following
56 <h3 id="ConfigureProject">Configure your development project</h3>
58 <p>In order to support ambient mode in your Wear app, you must update your Android SDK and configure
59 your development project. Follow these steps to make the necessary changes:</p
[all...] |
| /frameworks/base/docs/html/guide/practices/ui_guidelines/ |
| icon_design.jd | 14 <li>Your icons should follow the general specification in this document.</li>
70 your product. Streamlining the graphic style will also make the UI seem more
74 of your application?s user interface that match the general styles used by the
83 <dd>A Launcher icon is a graphic that represents your application on the
93 <dd>Status bar icons are used to represent notifications from your
106 <p>To get started creating your icons more quickly, you can download
118 template pack archive before you start designing your icons.</p>
123 any compatible image-editing program, although your ability to work directly
143 screen sizes and resolutions. When you design the icons for your application,
144 it's important keep in mind that your application may be installed on any o
[all...] |
| /frameworks/base/docs/html/ndk/guides/ |
| cpp-support.jd | 100 <h3>How to set your runtime</h3>
102 <p>Use the {@code APP_STL} variable in your <a href="{@docRoot}ndk/guides/application_mk.html">
104 the "Name" column in Table 1 as your setting. For example:</p>
110 <p>You may only select one runtime for your app, and can only do in
114 For more information on how to use these runtimes with your own toolchain, see <a href="{@docRoot}ndk/guides/standalone_toolchain.html">Standalone Toolchain</a>.</p>
160 build the library from sources by adding the following line to your {@code Application.mk}
161 file, or setting it in your environment prior to building: </p>
182 NDK to rebuild {@code libc++} from sources by adding the following line to your
183 {@code Application.mk} file, or setting it in your environment prior to building: </p>
198 <p>If you are using your own toolchain, use:</p
[all...] |
| /frameworks/support/v4/java/android/support/v4/app/ |
| ActionBarDrawerToggle.java | 46 * <p>To use <code>ActionBarDrawerToggle</code>, create one in your Activity and call through
47 * to the following methods corresponding to your Activity callbacks:</p>
54 * <p>Call {@link #syncState()} from your <code>Activity</code>'s
60 * {@link DrawerLayout.DrawerListener}, or if you are already providing your own listener,
61 * call through to each of the listener methods from your own.</p>
285 * <p>This should be called from your <code>Activity</code>'s
380 * This method should always be called by your <code>Activity</code>'s
396 * This method should be called by your <code>Activity</code>'s
398 * If it returns true, your <code>onOptionsItemSelected</code> method should return true and
417 * {@link DrawerLayout.DrawerListener} callback method. If you do not use your
[all...] |
| /frameworks/base/docs/html/guide/topics/ui/accessibility/ |
| apps.jd | 54 services make your application more accessible even if you do not make any accessibility changes
55 to your code. However, there are steps you should take to optimize the accessibility of your
56 application and ensure a pleasant experience for all your users.</p>
58 <p>Making sure your application is accessible to all users requires only a few steps, particularly
59 when you create your user interface with the components provided by the Android framework. If you
60 use only the standard components for your application, the steps are:</p>
63 <li>Add descriptive text to user interface controls in your application using the
74 <li>Test your application using only accessibility navigation services and features. Turn on
77 and then try using your application using only directional controls. For more information o
[all...] |
| /cts/hostsidetests/security/src/android/cts/security/ |
| PerfEventParanoidTest.java | 42 + "to your device kernel's defconfig and apply the\n"
43 + "appropriate patches for your kernel located here:\n"
|
| /developers/build/prebuilts/androidtv/sample-inputs/app/src/main/res/values/ |
| strings.xml | 29 <string name="rich_settings_browse_title">TV Inputs by Your Company</string>
30 <string name="feed_error_message">No feed. Check your connection!</string>
|
