OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
full:applications
(Results
376 - 400
of
4211
) sorted by null
<<
11
12
13
14
15
16
17
18
19
20
>>
/external/zlib/src/contrib/puff/
README
22
puff.c may also be useful in
applications
where code size or memory usage is a
28
applications
, but if you must ...
/external/zlib/src/
inftrees.h
6
/* WARNING: this file should *not* be used by
applications
. It is
8
subject to change.
Applications
should only use zlib.h.
/frameworks/base/core/java/android/content/pm/
IPackageManager.aidl
156
* Retrieve all
applications
that are marked as persistent.
276
* all
applications
. If the currently available free storage
281
* all
applications
are deleted (based on last accessed time)
284
* the cache files from all
applications
will clear up
299
* all
applications
. If the currently available free storage
304
* all
applications
are deleted (based on last accessed time)
307
* the cache files from all
applications
will clear up
322
* Delete all the cache files in an
applications
cache directory
/frameworks/base/core/java/android/nfc/tech/
NfcV.java
29
* <p>The primary NFC-V I/O operation is {@link #transceive}.
Applications
must
96
* <p>
Applications
must not append the CRC to the payload,
/frameworks/base/docs/html/google/play/licensing/
overview.jd
109
license responses for the
applications
you publish with that account.</p>
158
user is on an airplane). For most
applications
, the use of
174
across multiple
applications
. A full test environment is also available through
176
applications
before publishing them, even if you don't have access to a
185
applications
that you publish through Google Play. The service is not
186
designed to let you control access to
applications
that are not published
218
access to your
applications
. It effectively replaces the Copy Protection
220
gives you wider distribution potential for your
applications
. </p>
/frameworks/base/docs/html/guide/topics/connectivity/nfc/
index.jd
32
applications
of data that is relevant to the application. It also goes over how to work with the
33
NDEF data in your
applications
and gives an overview of the framework APIs that support the basic
/frameworks/base/docs/html/guide/topics/providers/
content-providers.jd
67
other
applications
. However, you do need your own provider to provide custom search
69
paste complex data or files from your application to other
applications
.
/frameworks/base/docs/html/tools/debugging/
debugging-devtools.jd
8
number of settings on your device that will make it easier to test and debug your
applications
.</p>
11
third party
applications
. If you'd like to install the Dev Tools application
debugging-projects.jd
19
along with DDMS, to debug your
applications
. To access the debugger and
30
<li>Debug - Displays previously and currently debugged Android
applications
and its currently
/frameworks/base/docs/html/training/in-app-billing/
index.jd
28
<p>In this class, you'll learn how to perform common In-app Billing operations from Android
applications
.</p>
29
<p>In-app billing is a service hosted on Google Play that lets you charge for digital content or for upgrades in your app. The In-app Billing API makes it easy for you to integrate In-app Billing into your
applications
. You can request product details from Google Play, issue orders for in-app products, and quickly retrieve ownership information based on users' purchase history. You can also query the Google Play service for details about in-app products, such as local pricing and availability. Google Play provides a checkout interface that makes user interactions with the In-app Billing service seamless, and provides a more intuitive experience to your users.</p>
/frameworks/base/docs/html-intl/ja/guide/publishing/
preparing.jd
26
<p>????????????????????????????<a href="{@docRoot}tools/publishing/publishing.html">Publishing Your
Applications
</a> ??????????????? </p>
99
<p>?????????????????????????<a href="{@docRoot}tools/publishing/versioning.html">Versioning Your
Applications
</a>????????</p>
/frameworks/base/services/java/com/android/server/location/
LocationBlacklist.java
35
* Allows
applications
to be blacklisted from location updates at run-time.
37
* This is a silent blacklist.
Applications
can still call Location Manager
/frameworks/ex/common/java/com/android/common/
GoogleLogTags.logtags
19
# used by Google Mobile Services
applications
. These definitions are part of
20
# the platform even when the Google
applications
are not.
/hardware/samsung_slsi/exynos5/mobicore/daemon/Daemon/Server/public/
NetlinkServer.h
142
* Check for sessions started by
applications
that died(exited)
143
* Remove the connections to
applications
that are not active anymore
/libcore/luni/src/main/java/org/w3c/dom/ls/
LSSerializerFilter.java
18
* <code>LSSerializerFilter</code>s provide
applications
the ability to
36
* <p> DOM
applications
must not raise exceptions in a filter. The effect of
/prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/alsa/
global.h
43
* Most
applications
probably do not need them.
109
* notification object.
Applications
don't access its contents directly.
/prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/sysroot/usr/lib/
libdl.a
7
ELF ? 4 ( U????E?D$?E?D$?E?$??????? Using 'dlopen' in statically linked
applications
requires at runtime the shared libraries from the glibc version used for linking GCC: (GNU) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) .symtab .strtab .shstrtab .rel.text .data .bss .gnu.warning.dlopen .comment .note.GNU-stack @ ! % d + d 0 ? ? D * M , , ] D ?
32
ELF ? 4 ( U????E?D$?E?D$?E?D$?E?$??????? Using 'dlmopen' in statically linked
applications
requires at runtime the shared libraries from the glibc version used for linking GCC: (GNU) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) .symtab .strtab .shstrtab .rel.text .data .bss .gnu.warning.dlmopen .comment .note.GNU-stack @ ( % h + h 0 ? ? E * N - - ^ D ?
/prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/sysroot/usr/lib/xen/
libdl.a
7
ELF ? 4 ( U????E?D$?E?D$?E?$??????? Using 'dlopen' in statically linked
applications
requires at runtime the shared libraries from the glibc version used for linking GCC: (GNU) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) .symtab .strtab .shstrtab .rel.text .data .bss .gnu.warning.dlopen .comment .note.GNU-stack @ ! % d + d 0 ? ? D * M , , ] D ?
32
ELF ? 4 ( U????E?D$?E?D$?E?D$?E?$??????? Using 'dlmopen' in statically linked
applications
requires at runtime the shared libraries from the glibc version used for linking GCC: (GNU) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) .symtab .strtab .shstrtab .rel.text .data .bss .gnu.warning.dlmopen .comment .note.GNU-stack @ ( % h + h 0 ? ? E * N - - ^ D ?
/prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/sysroot/usr/include/alsa/
global.h
43
* Most
applications
probably do not need them.
109
* notification object.
Applications
don't access its contents directly.
/prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/sysroot/usr/lib/
libdl.a
7
ELF ? 4 ( U????E?D$?E?D$?E?$??????? Using 'dlopen' in statically linked
applications
requires at runtime the shared libraries from the glibc version used for linking GCC: (GNU) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) .symtab .strtab .shstrtab .rel.text .data .bss .gnu.warning.dlopen .comment .note.GNU-stack @ ! % d + d 0 ? ? D * M , , ] D ?
32
ELF ? 4 ( U????E?D$?E?D$?E?D$?E?$??????? Using 'dlmopen' in statically linked
applications
requires at runtime the shared libraries from the glibc version used for linking GCC: (GNU) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) .symtab .strtab .shstrtab .rel.text .data .bss .gnu.warning.dlmopen .comment .note.GNU-stack @ ( % h + h 0 ? ? E * N - - ^ D ?
/prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/sysroot/usr/lib/xen/
libdl.a
7
ELF ? 4 ( U????E?D$?E?D$?E?$??????? Using 'dlopen' in statically linked
applications
requires at runtime the shared libraries from the glibc version used for linking GCC: (GNU) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) .symtab .strtab .shstrtab .rel.text .data .bss .gnu.warning.dlopen .comment .note.GNU-stack @ ! % d + d 0 ? ? D * M , , ] D ?
32
ELF ? 4 ( U????E?D$?E?D$?E?D$?E?$??????? Using 'dlmopen' in statically linked
applications
requires at runtime the shared libraries from the glibc version used for linking GCC: (GNU) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) .symtab .strtab .shstrtab .rel.text .data .bss .gnu.warning.dlmopen .comment .note.GNU-stack @ ( % h + h 0 ? ? E * N - - ^ D ?
/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.7-4.6/sysroot/usr/include/alsa/
global.h
43
* Most
applications
probably do not need them.
109
* notification object.
Applications
don't access its contents directly.
/prebuilts/python/darwin-x86/2.7.5/lib/python2.7/plat-mac/lib-scriptpackages/_builtinSuites/
builtin_Suite.py
33
"""run: Run an application. Most
applications
will open an empty, untitled window.
52
"""reopen: Reactivate a running application. Some
applications
will open a new untitled window if no window is open.
/prebuilts/tools/common/proguard/proguard4.7/docs/
license.html
25
applications
, commercial or not. Your code obviously remains yours after
43
applications
: Apache Ant, Apache Maven, the Google Android SDK, the Eclipse
/prebuilts/tools/common/proguard/proguard4.7/examples/
scala.pro
3
#
applications
, including the Scala runtime.
41
# Preserve all public
applications
.
Completed in 1141 milliseconds
<<
11
12
13
14
15
16
17
18
19
20
>>