Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:applications (Results 551 - 575 of 4211) sorted by null

<<21222324252627282930>>

/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> 281 The former ensures that the service can be bound to by external applications. 282 The latter then enforces that only external applications that hold the 354 <p>Applications can check whether their HCE service is the default service for a 363 <h2 id="PaymentApps">Payment Applications</h2> 366 "payment" category as payment applications. The Android 4.4 release contains a     [all...]
/frameworks/base/docs/html/sdk/installing/
studio.jd	41 3.1 Subject to the terms of this License Agreement, Google grants you a limited, worldwide, royalty-free, non-assignable and non-exclusive license to use the SDK solely to develop applications to run on the Android platform. 51 3.6 You agree that the form and nature of the SDK that Google provides may change without prior notice to you and that future versions of the SDK may be incompatible with applications developed on previous versions of the SDK. You agree that Google may stop (permanently or temporarily) providing the SDK (or any features within the SDK) to you or to users generally at Google's sole discretion, without prior notice to you. 59 4.1 Google agrees that it obtains no right, title or interest from you (or your licensors) under this License Agreement in or to any software applications that you develop using the SDK, including any intellectual property rights that subsist in those applications. 61 4.2 You agree to use the SDK and write applications only for purposes that are permitted by (a) this License Agreement and (b) any applicable law, regulation or generally accepted practices or guidelines in the relevant jurisdictions (including any laws regarding the export of data or software to and from the United States or other relevant countries). 63 4.3 You agree that if you use the SDK to develop applications for general public users, you will protect the privacy and legal rights of those users. If the users provide you with user names, passwords, or other login information or personal information, you must make the users aware that the information will be available to your application, and you must provide legally adequate privacy notice and protection for those users. If your application stores personal or sensitive information provided by users, it must do so securely. If the user provides your application with Google Account information, your application may only use that information to access the user's Google Account when, and for the limited purposes for which, the user has given you permission to do so. 67 4.5 You agree that you are solely responsible for (and that Google has no responsibility to you or to any third party for) any data, content, or resources that you create, transmit or display through Android and/or applications for Android, and for the consequences of your actions (including any loss or damage which Google may suffer) by doing so. 73 5.1 You agree that you are responsible for maintaining the confidentiality of any developer credentials that may be issued to you by Google or which you may choose yourself and that you will be solely responsible for all applications that are developed under your developer credentials. 82 <h3>7. Third Party Applications</h3> 83 7.1 If you use the SDK to run applications developed by a third party or that access data, content or resources provided by a third party, yo (…)     [all...]
/external/chromium_org/native_client_sdk/src/doc/devguide/devcycle/
dynamic-loading.rst	22 applications with the glibc library in the Native Client SDK. Before reading 54 | | | licenses | commercial, closed-source applications. For| 60 For proprietary (closed-source) applications, your options are to either 73 common dynamically linked libraries such as libc.so between applications. 134 One significant difference between newlib and glibc applications is that glibc 135 applications must explicitly list and deploy the shared libraries that they 159 Applications built with the glibc toolchain will by dynamically linked by 170 at runtime (after the application is already running). Many applications load 175 Native Client manifest file for glibc applications. 213 .nmf files for details on how to build dynamically linked applications     [all...]
/frameworks/base/docs/html/guide/topics/manifest/
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, 343 <li>It lets applications describe the framework API revision that they 345 <li>It lets the system negotiate the installation of applications on the user's 346 device, such that version-incompatible applications are not installed.</li> 352 <p>Applications can use a manifest element provided by the framework API &mdash; 433 <p>Android applications are generally forward-compatible with new versions o     [all...]
/frameworks/base/docs/html/about/versions/
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/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
/bionic/libc/netbsd/net/
reentrant.h	43 * be used by non-threaded applications without unreasonable overhead. 46 * applications. 63 * threaded applications.
/docs/source.android.com/src/compatibility/
overview.jd	36 greatly that developers must design different versions of their applications 50 users can only see applications which they can actually run.</p> 56 Android relevant to running third-party applications, which allows device
/docs/source.android.com/src/devices/tech/test_infra/tradefed/
index.jd	45 framework, the system, and the hardware, but has little or no influence over existing applications. 57 compatibility with existing applications.</p> 95 the prior two usecases in that the service builder does not control the devices or the applications
/external/chromium/chrome/browser/
background_application_list_model.cc	272 // We only care about extensions that are background applications 292 // initialized to determine the current set of background applications. If that 298 // Discover current background applications, compare with previous list, which
/external/chromium_org/third_party/icu/source/tools/pkgdata/
pkgdata.1.in	59 applications that use ICU. The typical reason to package files using 64 Packaged data also allow applications to be distributed with fewer 81 data directory. Such packaging is easy to use for applications resource
/external/icu4c/tools/pkgdata/
pkgdata.1.in	59 applications that use ICU. The typical reason to package files using 64 Packaged data also allow applications to be distributed with fewer 81 data directory. Such packaging is easy to use for applications resource
/external/qemu/distrib/sdl-1.2.15/Xcode/TemplatesForXcodeLeopard/SDL Application/___PROJECTNAME___.xcodeproj/
project.pbxproj	150 productInstallPath = "$(HOME)/Applications"; 218 INSTALL_PATH = "$(HOME)/Applications"; 232 INSTALL_PATH = "$(HOME)/Applications";
/external/qemu/distrib/sdl-1.2.15/Xcode/TemplatesForXcodeLeopard/SDL Cocoa Application/___PROJECTNAME___.xcodeproj/
project.pbxproj	153 productInstallPath = "$(HOME)/Applications"; 230 INSTALL_PATH = "$(HOME)/Applications"; 244 INSTALL_PATH = "$(HOME)/Applications";
/external/qemu/distrib/sdl-1.2.15/Xcode/TemplatesForXcodeSnowLeopard/SDL Application/___PROJECTNAME___.xcodeproj/
project.pbxproj	150 productInstallPath = "$(HOME)/Applications"; 218 INSTALL_PATH = "$(HOME)/Applications"; 232 INSTALL_PATH = "$(HOME)/Applications";
/external/qemu/distrib/sdl-1.2.15/Xcode/TemplatesForXcodeSnowLeopard/SDL Cocoa Application/___PROJECTNAME___.xcodeproj/
project.pbxproj	153 productInstallPath = "$(HOME)/Applications"; 230 INSTALL_PATH = "$(HOME)/Applications"; 244 INSTALL_PATH = "$(HOME)/Applications";
/external/qemu/distrib/sdl-1.2.15/Xcode/TemplatesForXcodeTiger/SDL Application/SDLApp.xcodeproj/
project.pbxproj	167 productInstallPath = "$(HOME)/Applications"; 237 INSTALL_PATH = "$(HOME)/Applications"; 254 INSTALL_PATH = "$(HOME)/Applications";
/external/qemu/distrib/sdl-1.2.15/Xcode/TemplatesForXcodeTiger/SDL Cocoa Application/SDLCocoaApp.xcodeproj/
project.pbxproj	170 productInstallPath = "$(HOME)/Applications"; 249 INSTALL_PATH = "$(HOME)/Applications"; 266 INSTALL_PATH = "$(HOME)/Applications";
/frameworks/base/core/java/android/app/
UiModeManager.java	27 * allow applications to control UI modes of the device. 61 * implement to provide their own interface. However, applications can 82 * implement to provide their own interface. However, applications can
/frameworks/base/core/java/android/bluetooth/
BluetoothManager.java	80 * This can be used by applications like status bar which would just like 112 * This can be used by applications like status bar which would just like 152 * This can be used by applications like status bar which would just like
/frameworks/base/core/java/android/nfc/tech/
IsoDep.java	31 * <p>The primary ISO-DEP I/O operation is {@link #transceive}. Applications must 152 * <p>Applications must only send the INF payload, and not the start of frame and 153 * end of frame indicators. Applications do not need to fragment the payload, it
/frameworks/base/core/java/android/view/textservice/
TextServicesManager.java	32 * System API to the overall text services, which arbitrates interaction between applications 36 * The user can change the current text services in Settings. And also applications can specify 53 * <li> Multiple <strong>client applications</strong> arbitrate with the text service
/frameworks/base/core/java/android/webkit/
WebStorage.java	27 * application cache to power offline Web applications. Use of the Application 206 * This class should not be instantiated directly, applications must only use 209 * applications using it would receive a non-functional instance of this class (there was no
/frameworks/base/docs/html/training/sharing/
receive.jd	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 35 want to receive from other applications. For example, a social networking application would likely

Completed in 918 milliseconds

<<21222324252627282930>>