Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:applications (Results 176 - 200 of 4211) sorted by null

1 2 3 4 5 6 78 91011>>

/frameworks/base/docs/html/tools/help/
index.jd	6 applications for the Android platform. The tools are classified into two groups: SDK tools 13 The SDK tools are required if you are developing Android applications. The most important SDK tools 23 <dd>Lets you debug Android applications.</dd> 36 your applications in an actual Android run-time environment.</dd> 51 to stress-test applications that you are developing, in a random yet repeatable manner.</dd> 62 <dd>Lets you access the SQLite data files created and used by Android applications.</dd>
/frameworks/base/docs/html/about/versions/
android-2.3.jd	51 developers build internet telephony applications. Using the API, applications can offer 57 package. The key class is {@link android.net.sip.SipManager}, which applications 59 audio calls. Once an audio call is established, applications can mute calls, 60 turn on speaker mode, send DTMF tones, and more. Applications can also use the 65 applications should use the {@link android.net.sip.SipManager#isApiSupported 69 <p>To use the SIP API, applications must request permission from the user by 75 their applications are not discoverable to users whose devices do not include 92 platform notifies applications by broadcasting an Intent, appending the tag's 93 NDEF messages to the Intent as extras. Applications can create Intent filters t     [all...]
android-3.1-highlights.jd	89 (keyboards, mice, game controllers) and digital cameras. Applications can build 159 <p>A new high-performance Wi-Fi lock lets applications maintain 176 <p>The Android 3.1 platform includes an updated set of standard applications 274 applications running on the platform. The API provides a way to interact across 281 applications that the hardware is available.</p> 296 <p>To learn more about how to develop applications that interact with 303 an API that lets applications manage connected peripherals. On devices that 304 support host mode, applications can use the API to identify and communicate with 308 <p>To learn more about how to develop applications that interact with 316 these capabilities to let users interact with their applications using mice     [all...]
android-1.5-highlights.jd	121 <li>Google applications (not available in the Android 1.5 System Image that is 125 Email applications</li> 178 <p>Applications can now use a new element in their manifest files, <a 198 <li>LocationManager - Applications can get location change updates via 204 applications</li>
android-2.2.jd	85 <p>The Android platform now allows applications to request installation onto the 90 their applications by means of a new attribute of <code>&lt;manifest&gt;</code> 102 versa), through Manage Applications in the user settings.</p> 104 <p>By default, the system installs all applications onto the device's internal 106 means that the system will always install legacy applications onto internal 114 suitable for all applications, particularly because the external media may be 119 application, including a discussion of what types of applications should and 127 applications can use to backup and restore user data, to ensure that users can 158 <li>The platform provides new speech-recognition APIs that allow applications to have a richer interaction with the available voice recognizer. For example, the APIs are sufficient to integrate voice recognition deeply into an IME.</li> 179 administrator" applications that can control security features of the device     [all...]
/frameworks/base/docs/html/tools/publishing/
publishing_overview.jd	24 <p>Publishing is the general process that makes your Android applications available to users. When you 39 However, you can also release applications by sending them directly to users or by letting users 108 <p>You can release your Android applications several ways. Usually, you release applications 109 through an application marketplace such as Google Play, but you can also release applications 118 useful if you want to distribute your applications to a large global audience. 123 <h4 id="publishing-market">Releasing Your Applications on Google Play</h4> 126 your Android applications to users around the world. When you release your applications through 128 identify market trends, and control who your applications are being distributed to. You also hav     [all...]
versioning.jd	1 page.title=Versioning Your Applications 12 <li>How you version your applications affects how users upgrade </li> 42 <li>Other applications &mdash; including other applications that you publish as 69 <p>The value is an integer so that other applications can programmatically 81 user (see <code>android:versionName</code>, below). Applications and publishing 91 for any internal purpose, other than to enable applications to display it to 121 <p>The Android framework provides an API to let applications query the system 123 applications use the
/developers/samples/android/ui/actionbarcompat/ActionBarCompat-SearchView/src/main/src/com/example/android/actionbarcompat/searchview/
AppListFragment.java	39 * A ListFragment which displays a list of applications currently on the device, with 44 // Stores the full list of applications installed on the device 56 // Retrieve all of the applications installed on this device 67 // Set the ListView's Adapter to display the filtered applications 73 // If the installed applications is not loaded yet, hide the list 183 * Simple AsyncTask which retrieves the installed applications from the {@link PackageManager} 190 // Load all installed applications on the device
/libcore/luni/src/main/java/org/xml/sax/
Parser.java	28 * applications to register handlers for different types of events 61 * however, they must throw a SAX exception. Applications may 83 * <p>Applications may register a new or different entity resolver 102 * <p>Applications may register a new or different 121 * <p>Applications may register a new or different handler in the 140 * <p>Applications may register a new or different handler in the 159 * <p>Applications may not invoke this method while a parse is in
/external/chromium_org/chrome/browser/
shell_integration_linux_unittest.cc	202 // Shortcut in applications directory. 206 base::FilePath apps_path = temp_dir.path().AppendASCII("applications"); 225 // Shortcut in applications directory with NoDisplay=true. 229 base::FilePath apps_path = temp_dir.path().AppendASCII("applications"); 240 // Doesn't count as being in applications menu. 248 // Shortcut on desktop and in applications directory. 256 base::FilePath apps_path = temp_dir2.path().AppendASCII("applications"); 288 // Test that it searches $XDG_DATA_HOME/applications. 295 // Create a file in a non-applications directory. This should be ignored. 300 temp_dir.path().AppendASCII("applications")));     [all...]
/external/chromium_org/native_client_sdk/src/doc/devguide/devcycle/
running.rst	15 This document describes how to run Native Client applications during 18 The workflow for PNaCl applications is straightfoward and will only be discussed 19 briefly. For NaCl applications distributed through the web-store, there is a 22 Portable Native Client (PNaCl) applications 25 Running PNaCl applications from the open web is enabled in Chrome version 31 and 27 applications locally. An application that uses a PNaCl module can be tested 33 local server built in, and the process of using it to run PNaCl applications is 36 Native Client applications and the Chrome Web Store 39 Before reading about how to run Native Client applications, it's important to 40 understand a little bit about how Native Client applications are distributed     [all...]
/frameworks/base/docs/html/training/articles/
security-tips.jd	71 applications.</p> 76 the ability to limit data access to particular applications, nor do they 114 to your own application or exported to allow access by other applications. 116 applications with access to your {@link android.content.ContentProvider}, mark them as <code><a 124 that will be exported for use by other applications, you can specify a single 177 <p>Because Android sandboxes applications from each other, applications must explicitly 202 applications, such as a {@link android.content.ContentProvider}. 207 protection level</a> on permissions for IPC communication between applications 224 uncommon for most applications, because the <     [all...]
/external/chromium_org/native_client_sdk/src/doc/devguide/coding/
application-structure.rst	41 Applications that are published in the `Chrome Web Store 88 Native Client applications have two types of manifest files: a Chrome Web Store 93 ``manifest.json``, is required for applications that are published in the Chrome 102 required for all Native Client applications. The extension for this file is 105 Manifest files for applications that use PNaCl are simple. Here is the manifest 121 For Chrome Web Store applications that do not use PNaCl, a typical manifest file 146 For applications that use the :ref:`glibc<c_libraries>` 148 shared libraries that the applications use. This is discussed in detail in 150 see some example manifest files, build some of the example applications in the
/external/chromium_org/third_party/npapi/npspy/extern/nspr/
prwin16.h	70 ** Note that stdio is not operational at all on Win16 GUI applications. 72 ** .DLL for command line applications only. NSPR's test cases are 73 ** almost exclusively command line applications. 168 ** Get the exception context for Win16 MFC applications threads 172 ** Set the exception context for Win16 MFC applications threads
/external/sepolicy/
app.te	84 # Allow all applications to read downloaded files 88 # Allow applications to communicate with netd via /dev/socket/dnsproxyd 92 # Allow applications to communicate with drmserver over binder 95 # Allow applications to communicate with mediaserver over binder 98 # Allow applications to make outbound tcp connections to any port
/external/chromium_org/chrome/browser/ui/ash/launcher/
multi_profile_browser_status_monitor.cc	38 // Handle apps in browser tabs: Add the new applications. 42 // Remove old (tabbed V1) applications. 57 // Handle apps in browser tabs: Add new (tabbed V1) applications.
/external/chromium_org/chrome/common/extensions/docs/templates/articles/
app_codelab_10_publishing.html	12 <li> Ratings and reviews provide a great way to see the quality of applications.</li> 24 <p>The Chrome Web Store has a special <a href="https://chrome.google.com/webstore/developer/dashboard">dashboard for Developers</a> that lets you upload new applications and update existing ones.</p> 29 <li> Compress your applications root directory (the folder containing the &#39;manifest.json&#39; file).</li>
/external/srtp/crypto/
Makefile	42 # test applications 57 @echo "running libcryptomodule test applications..." 65 @echo "libcryptomodule test applications passed."
Makefile.in	42 # test applications 57 @echo "running libcryptomodule test applications..." 65 @echo "libcryptomodule test applications passed."
/frameworks/base/docs/html/guide/components/
index.jd	20 <p>Today we?ve released a static library that exposes the same Fragments API (as well as the new LoaderManager and a few other classes) so that applications compatible with Android 1.6 or later can use fragments to create tablet-compatible user interfaces. </p> 26 <p>A good practice in creating responsive applications is to make sure your main UI thread 52 applications using Intent APIs and the ActionProvider object.</p>
/frameworks/base/docs/html/guide/topics/data/
install-location.jd	12 <li>Some types of applications should <strong>not</strong> allow installation on the external 14 <li>Installing on the external storage is ideal for large applications that are not tightly 21 <li><a href="#ShouldNot">Applications That Should NOT Install on External Storage</a></li> 22 <li><a href="#Should">Applications That Should Install on External Storage</a></li> 80 from the device and all applications running on the external storage are immediately killed.</p> 87 on devices running API Level 8 (Android 2.2) or greater. Existing applications that were built prior 119 <h2 id="ShouldNot">Applications That Should NOT Install on External Storage</h2> 126 this can break some types of applications in a more serious way. In order for your application to 136 your application when applications installed on external storage have become available to the 173 applications. However, if you're certain that your application should never be installed on th     [all...]
/frameworks/base/location/lib/java/com/android/location/provider/
LocationRequestUnbundled.java	22 * This class is an interface to LocationRequests for unbundled applications. 25 * applications, and must remain API stable. See README.txt in the root 58 * but will receive locations triggered by other applications. Your application
/prebuilts/tools/common/proguard/proguard4.7/examples/ant/
applications3.xml	1 <!-- This Ant build file illustrates how to process applications, 5 <project name="Applications" default="obfuscate" basedir="../.."> 35 <!-- Preserve all public applications. -->
/external/jpeg/
jerror.c	10 * stderr is the right thing to do. Many applications will want to replace 40 * The message table is made an external symbol just in case any applications 59 * Applications may override this if they want to get control back after 84 * Applications may override this method to send JPEG messages somewhere 89 * Most Windows applications will still prefer to override this routine, 153 * Few applications should need to override this method.
/external/qemu/distrib/jpeg-6b/
jerror.c	10 * stderr is the right thing to do. Many applications will want to replace 40 * The message table is made an external symbol just in case any applications 59 * Applications may override this if they want to get control back after 84 * Applications may override this method to send JPEG messages somewhere 89 * Most Windows applications will still prefer to override this routine, 153 * Few applications should need to override this method.

Completed in 883 milliseconds

1 2 3 4 5 6 78 91011>>