HomeSort by relevance Sort by last modified time
    Searched full:applications (Results 626 - 650 of 4986) sorted by null

<<21222324252627282930>>

  /frameworks/base/docs/html/guide/topics/manifest/
receiver-element.jd 28 applications to receive intents that are broadcast by the system or by other
29 applications, even when other components of the application are not running.
61 receive are those sent by components of the same application or applications
71 receiver is intended to receive intents broadcast by the system or other applications,
166 This allows components in different applications to share a process, reducing
application-element.jd 117 should only be specified by applications with an activity that handles the
172 available to applications, to improve performance for many common 2D graphics
176 responsiveness overall, even for applications that do not explicitly make use
203 <dd>Whether or not the application is a game. The system may group together applications classifed
204 as games or display them separately from other applications.
213 when the phone is first set up. Third-party applications will not normally
224 process; if you're using a shared user ID to allow multiple applications to use a process, they all
270 The subclass is optional; most applications won't need one.
293 is {@code "false"}. Applications should not normally set this flag;
294 persistence mode is intended only for certain system applications.</dd
    [all...]
uses-sdk-element.jd 63 <a href="{@docRoot}tools/publishing/versioning.html">Versioning Your Applications</a>.
164 as a filter, however, when presenting users with applications available for
191 <p>The Android platform provides a framework API that applications can use to
199 <li>A set of permissions that applications can request, as well as permission
210 that existing applications can still use them. In a very small number of cases,
354 <li>It lets applications describe the framework API revision that they
356 <li>It lets the system negotiate the installation of applications on the user's
357 device, such that version-incompatible applications are not installed.</li>
363 <p>Applications can use a manifest element provided by the framework API &mdash;
444 <p>Android applications are generally forward-compatible with new versions o
    [all...]
  /frameworks/base/docs/html/tools/debugging/
index.jd 19 <p>The Android SDK provides most of the tools that you need to debug your applications. You need
54 via DDMS. If you want to debug multiple applications, attaching to each port might become
81 attach to this static debugging port and debug all the applications that are running on the
92 debug and profile your applications:</p>
118 applications:</p>
  /frameworks/base/docs/html/training/camera/
cameradirect.jd 38 from existing camera applications. However, if you want to build a specialized camera application
187 <p>Most camera applications lock the display into landscape mode because that is the natural
239 applications, including new instances of your own application.</p>
265 // applications. Applications should release the camera immediately
  /frameworks/base/docs/html/training/sharing/
send.jd 39 from other applications by specifying them in your manifest.</p>
41 <p>Sending and receiving data between applications with intents is most commonly used for social
43 favorite applications.</p>
89 <li>If no applications match, Android displays a system message.</li>
110 <p class="note"><strong>Note:</strong> Some e-mail applications, such as Gmail, expect a
  /frameworks/base/services/core/java/com/android/server/location/
LocationFudger.java 32 * Contains the logic to obfuscate (fudge) locations for coarse applications.
34 * <p>The goal is just to prevent applications with only
57 * This is the fastest interval that applications can receive coarse
122 * Best location accuracy allowed for coarse applications.
344 * allowed for coarse applications and all derived values.
  /libcore/luni/src/main/java/org/xml/sax/ext/
EntityResolver2.java 41 * resolution. <em>Old Style</em> applications won't know about this interface;
46 * Both <em>Old Style</em> and <em>Transitional Mode</em> applications will
48 * <em>New style</em> applications will fail to run except on SAX2 parsers
64 * Allows applications to provide an external subset for documents
137 * Allows applications to map references to external entities into input
  /packages/apps/Launcher3/res/values-fr/
strings.xml 24 <string name="uid_name" msgid="7820867637514617527">"Applications de base Android"</string>
42 <string name="group_applications" msgid="3797214114206693605">"Applications"</string>
54 <string name="all_apps_button_label" msgid="9110807029020582876">"Applications"</string>
61 <string name="accessibility_all_apps_button" msgid="2603132375383800483">"Applications"</string>
86 <string name="apps_customize_apps_scroll_format" msgid="370005296147130238">"Page des applications %1$d sur %2$d"</string>
  /frameworks/base/core/java/android/hardware/
Camera.java 96 * use by other applications. Applications should release the camera
138 * applications.
256 * applications.
314 * the same camera is opened by other applications, this will throw a
318 * otherwise it will remain locked and be unavailable to other applications.
365 * given hal API version. If the same camera is opened by other applications
370 * otherwise it will remain locked and be unavailable to other applications.
572 * <p>Since API level 14, camera is automatically locked for applications in
573 * {@link android.media.MediaRecorder#start()}. Applications can use th
    [all...]
  /frameworks/base/docs/html/tools/building/
building-cmdline-ant.jd 29 <li><a href="{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a></li>
49 "{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>, particularly once
52 getting started, however, you can quickly run your applications on an emulator or your own
135 "{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>.</p>
154 <a href="{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>.</p>
194 <em>Settings &gt; Applications &gt; Unknown sources</em>.)</p>
241 first time, it won't show up in the application launcher or be accessible by other applications.
267 <strong>Settings > Applications > Development</strong>.</li>
304 <p>As you begin developing Android applications, understand that all Android applications must b
    [all...]
building-cmdline.jd 32 Signing Your Applications</a></li>
54 "{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>, particularly once
57 getting started, however, you can quickly run your applications on an emulator or your own
162 "{@docRoot}tools/publishing/app-signing.html">Signing Your Applications</a>.</p>
234 <em>Settings &gt; Applications &gt; Unknown sources</em>.)</p>
281 first time, it won't show up in the application launcher or be accessible by other applications.
307 <strong>Settings > Applications > Development</strong>.</li>
344 <p>As you begin developing Android applications, understand that all Android applications must be
363 Applications</a>, which provides a thorough guide to application signing on Android and what i
    [all...]
  /frameworks/base/docs/html/about/versions/
android-1.5.jd 18 <li><a href="#apps">Built-in Applications</a></li>
52 skins, sample applications, and more. The downloadable platform is fully
234 <p>Applications can now use a new element in their manifest files, <a
252 <li>LocationManager - Applications can get location change updates via
258 applications</li>
271 <h2 id="apps">Built-in Applications</h2>
274 built-in applications:</p>
android-2.0.1.jd 16 <li><a href="#apps">Built-in Applications</a></li>
54 skins, sample applications, and more. The downloadable platform
128 <h2 id="apps">Built-in Applications</h2>
131 built-in applications:</p>
250 <li>Debug- and release-mode application signing. Release-mode signing includes integrated support for <code>zipalign</code> optimization. For more information, see <a href="{@docRoot}tools/publishing/app-signing.html#releasecompile">Signing Your Applications</a>.</li>
287 applications apply necessary styles to the {@link
  /frameworks/base/docs/html/training/connect-devices-wirelessly/
nsd.jd 38 requests. This is useful for a variety of peer-to-peer applications such as file
44 from other applications doing the same. Finally, this lesson shows you how
100 conflicts with other applications. For instance, assuming
102 other installed applications that use the same port. Instead, use the device's
105 known by other applications at compile-time. Instead, the applications can get
330 other applications from thinking it's still active and attempting to connect to
  /frameworks/base/docs/html/guide/topics/connectivity/nfc/
hce.jd 21 <li><a href="#PaymentApps">Payment Applications</a>
68 the host CPU on which Android applications are running directly, instead of routing the NFC
109 any user interface. This is a natural fit for many HCE applications like loyalty or transit cards,
123 select applications, centered around an Application ID (AID). An AID
133 collisions with other applications.</p>
286 The former ensures that the service can be bound to by external applications.
287 The latter then enforces that only external applications that hold the
361 <p>Applications can check whether their HCE service is the default service for a
368 <h2 id="PaymentApps">Payment Applications</h2>
371 "payment" category as payment applications. The Android 4.4 release contains
    [all...]
  /external/chromium_org/chrome/app/resources/
google_chrome_strings_fr.xtb 17 <translation id="4167057906098955729">Vous pouvez consulter ici toutes les notifications qui vous sont transmises depuis les applications, les extensions et les sites Web Chrome.</translation>
33 <translation id="2896252579017640304">Lancer des applications Google Chrome</translation>
53 <translation id="3080151273017101988">Poursuivre l'exécution d'applications en arrière-plan après la fermeture de Google Chrome</translation>
58 <translation id="7060865993964054389">Lanceur d'applications Google Chrome</translation>
81 <translation id="1434626383986940139">Applications Chrome Canary</translation>
89 <translation id="345168553362876363">Le lanceur d'applications Google Chrome est une plate-forme autonome pour les applications Google Chrome.</translation>
93 <translation id="3149510190863420837">Applications Chrome</translation>
167 <translation id="1469002951682717133">Lanceur d'applications Google Chrome</translation>
168 <translation id="8568392309447938879">Vous devez être connecté à Chrome pour utiliser les applications. Cela permet de synchroniser vos applications, vos favoris, votre historique, vos mots de passe et (…)
    [all...]
  /external/chromium_org/native_client_sdk/doc_generated/devguide/devcycle/
dynamic-loading.html 27 applications with the glibc library in the Native Client SDK. Before reading
69 commercial, closed-source applications. For
85 <p>For proprietary (closed-source) applications, your options are to either
97 common dynamically linked libraries such as libc.so between applications.
171 <p>One significant difference between newlib and glibc applications is that glibc
172 applications must explicitly list and deploy the shared libraries that they
191 <p>Applications built with the glibc toolchain will by dynamically linked by
200 at runtime (after the application is already running). Many applications load
205 Native Client manifest file for glibc applications.</p>
235 .nmf files for details on how to build dynamically linked applications
    [all...]
  /external/chromium_org/native_client_sdk/src/doc/devguide/devcycle/
dynamic-loading.rst 19 applications with the glibc library in the Native Client SDK. Before reading
50 | commercial, closed-source applications. For | | licenses |
56 For proprietary (closed-source) applications, your options are to either
69 common dynamically linked libraries such as libc.so between applications.
137 One significant difference between newlib and glibc applications is that glibc
138 applications must explicitly list and deploy the shared libraries that they
162 Applications built with the glibc toolchain will by dynamically linked by
173 at runtime (after the application is already running). Many applications load
178 Native Client manifest file for glibc applications.
216 .nmf files for details on how to build dynamically linked applications
    [all...]
  /frameworks/base/core/java/android/net/
VpnService.java 51 * VpnService is a base class for applications to extend and build their
62 * <p>Letting applications intercept packets raises huge security concerns.
121 * permission so that other applications cannot abuse it.
334 * action. Applications overriding this method must identify the intent
614 * If this method is called at least once, only applications added through this method (and
615 * no others) are allowed access. Else (if this method is never called), all applications
616 * are allowed by default. If some applications are added, other, un-added applications
619 * A {@link Builder} may have only a set of allowed applications OR a set of disallowed
648 * By default, all applications are allowed access, except for those denied through thi
    [all...]
  /external/chromium_org/native_client_sdk/doc_generated/sdk/
examples.html 5 <p>Every Native Client SDK bundle comes with a folder of example applications.
16 Native Client applications you must specifically enable Native Client in Chrome:</p>
178 <code>/Applications/Google Chrome.app/Contents/MacOS/Google Chrome</code> for
180 <code>Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary</code>
196 packaged applications. The examples that use these features must be run as
197 packaged applications, by using the following command:</p>
  /external/chromium_org/native_client_sdk/src/doc/sdk/
examples.rst 8 Every Native Client SDK bundle comes with a folder of example applications.
25 Native Client applications you must specifically enable Native Client in Chrome:
215 ``/Applications/Google Chrome.app/Contents/MacOS/Google Chrome`` for
217 ``Applications/Google Chrome Canary.app/Contents/MacOS/Google Chrome Canary``
236 packaged applications. The examples that use these features must be run as
237 packaged applications, by using the following command::
  /external/chromium_org/third_party/libjpeg_turbo/
change.log 99 parameter structs; this may be useful in some applications.
104 extensions but claim to be version 1.01. Applications that generate their
153 This change requires applications to be recompiled, but does not require
201 may be of use in other applications.
205 decoding modes available to suspending-input applications. However,
206 existing applications that use suspending input will need to be changed
  /frameworks/base/docs/html/guide/practices/
screen-compat-mode.jd 48 <p>Screen compatibility mode is an escape hatch for applications that are not properly designed
53 then it might encounter some rendering issues on larger screens. For applications with this
67 Android 1.5, almost all applications should be developed against Android 1.6 or greater and
85 assist applications on the latest tablet devices when the applications have not yet
192 layout resizing. Normally, only applications that are already built against Android 3.2 (or
  /libcore/luni/src/main/java/org/xml/sax/
XMLReader.java 228 * <p>Applications may register a new or different resolver in the
254 * <p>Applications may register a new or different handler in the
281 * <p>Applications may register a new or different handler in the
307 * highly recommended that all SAX applications implement an
310 * <p>Applications may register a new or different handler in the
343 * <p>Applications may not invoke this method while a parse is in

Completed in 1679 milliseconds

<<21222324252627282930>>