| /frameworks/base/core/java/android/database/ |
| package.html | 3 Contains classes to explore data returned through a content provider.
|
| /external/tcpdump/missing/ |
| getaddrinfo.c | 141 struct explore { struct
152 static const struct explore explore[] = { variable in typeref:struct:explore
301 const struct explore *ex;
353 for (ex = explore; ex->e_af >= 0; ex++) {
397 for (ex = explore; ex->e_af >= 0; ex++) {
450 for (ex = explore; ex->e_af >= 0; ex++) {
|
| /frameworks/base/docs/html/guide/ |
| index.jd | 33 Fundamentals</a>. Then explore other topics — from
|
| /packages/apps/Email/tests/src/com/android/email/activity/setup/ |
| AccountSetupIncomingTests.java | 130 * TODO: A series of tests to explore the logic around security models & ports
|
| AccountSetupOutgoingTests.java | 125 * TODO: A series of tests to explore the logic around security models & ports
|
| /bootable/bootloader/legacy/arch_msm7k/ |
| clock.c | 170 #if EXPLORE
|
| /external/stlport/etc/ |
| ChangeLog-5.1 | [all...] |
| /frameworks/base/docs/html/resources/articles/ |
| index.jd | 111 <dd>Explore the UI changes that were introduced in Android 1.5, compared with the UI provided in Android 1.0 and 1.1.</dd>
116 <dd>Explore the UI changes that were introduced in Android 1.6, compared with the UI provided in Android 1.5. In particular, this article discusses changes to RelativeLayouts and click listeners.</dd>
|
| /bionic/libc/netbsd/net/ |
| getaddrinfo.c | 141 struct explore { struct
152 static const struct explore explore[] = { variable in typeref:struct:explore
377 const struct explore *ex;
422 for (ex = explore; ex->e_af >= 0; ex++) {
466 for (ex = explore; ex->e_af >= 0; ex++) {
518 for (ex = explore; ex->e_af >= 0; ex++) {
[all...] |
| /frameworks/base/docs/html/sdk/ |
| android-1.6-highlights.jd | 133 <li>Inside a category, users can explore titles that are <em>Top paid</em>, <em>Top free</em>, and <em>Just in</em>.</li>
|
| installing.jd | 467 <p><strong>Explore the development tools</strong></p>
493 <p><strong>Explore some code</strong></p>
|
| /frameworks/base/docs/html/guide/topics/ui/ |
| index.jd | 200 <p>Once you've grappled the fundamentals of creating a user interface, you can explore
|
| /external/qemu/android/utils/ |
| timezone.c | 708 /* we didn't find it, this may come from localized versions of Windows. we're going to explore the registry,
|
| /frameworks/base/docs/html/resources/tutorials/testing/ |
| helloandroid_test.jd | 487 <strong>Explore the Android instrumentation framework</strong>
|
| /external/e2fsprogs/ext2ed/doc/ |
| ext2ed-design.sgml | 271 so that I could explore the connections between them - Test my assumptions,
397 <Title>Starting to explore</Title>
400 With the above tool in my pocket, I started to explore the ext2 filesystem
446 At this point, I started to explore the block groups. I will not detail here
[all...] |
| /development/simulator/app/ |
| DeviceManager.cpp | 554 * and GenerateConsoleCtrlEvent()). Need to explore.
[all...] |
| /frameworks/base/docs/html/guide/developing/tools/ |
| adb.jd | 414 <p>To use <code>sqlite3</code>, enter a remote shell on the emulator instance, as described above, then invoke the tool using the <code>sqlite3</code> command. Optionally, when invoking <code>sqlite3</code> you can specify the full path to the database you want to explore. Emulator/device instances store SQLite3 databases in the folder <code><span chatdir="1"><span chatindex="259474B4B070F261">/data/data/<em><package_name></em>/databases</span></span>/</code>. </p>
|
| /ndk/build/platforms/android-3/arch-arm/usr/lib/ |
| libc.so | |
| /ndk/build/platforms/android-4/arch-arm/usr/lib/ |
| libc.so | |
| /ndk/build/platforms/android-5/arch-arm/usr/lib/ |
| libc.so | |
| /ndk/build/platforms/android-5/arch-x86/usr/lib/ |
| libc.so | |
| /ndk/build/platforms/android-8/arch-arm/usr/lib/ |
| libc.so | |
| /ndk/build/platforms/android-8/arch-x86/usr/lib/ |
| libc.so | |
| /development/samples/SearchableDictionary/res/raw/ |
| definitions.txt | [all...] |
| /external/netcat/ |
| README | 419 nowadays is a popular thing to explore. A simple example data-generator is
[all...] |
