| /ndk/build/gmsl/ |
| README | 6 2. To use the GMSL in your Makefile make sure that you have the files
15 to your Makefile(s).
|
| /ndk/tests/device/test-basic-exceptions/ |
| README | 4 Normally, the only thing needed is adding -fexceptions to your LOCAL_CFLAGS
5 and that's it. Alternatively, use it in APP_CFLAGS to add the flag to all your
|
| /prebuilts/misc/common/swig/include/2.0.11/perl5/ |
| perlfragments.swg | 3 Create a file with this name, 'perlfragments.swg', in your working
13 <your code here>;
|
| /prebuilts/misc/common/swig/include/2.0.11/python/ |
| pyfragments.swg | 3 Create a file with this name, 'pyfragments.swg', in your working
13 <your code here>;
|
| /prebuilts/misc/common/swig/include/2.0.11/ruby/ |
| rubyfragments.swg | 3 Create a file with this name, 'rubyfragments.swg', in your working
13 <your code here>;
|
| /prebuilts/misc/common/swig/include/2.0.11/tcl/ |
| tclfragments.swg | 3 Create a file with this name, 'tclfragments.swg', in your working
13 <your code here>;
|
| /sdk/testapps/jarCheckTests1/app/ |
| project.properties | 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
7 # "ant.properties", and override values to adapt the script to your
|
| /sdk/testapps/jarCheckTests2/app/ |
| project.properties | 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
7 # "ant.properties", and override values to adapt the script to your
|
| /sdk/testapps/jarCheckTests3/app/ |
| project.properties | 2 # Do not modify this file -- YOUR CHANGES WILL BE ERASED!
7 # "ant.properties", and override values to adapt the script to your
|
| /frameworks/base/docs/html/training/auto/start/ |
| index.jd | 47 <p>You can enable your existing audio and messaging apps developed for
49 vehicle-specific hardware differences. To enable your app for Auto, your
50 app must target Android 5.0 (API level 21) or higher. Your app?s manifest must
55 setting up your development environment and meeting the the minimum requirements
67 update your app project</a></strong> - Android 5.0 (API level 21) provides new
84 <p>The Auto features that your app can access are controlled
85 by the settings in your app manifest and a separate XML configuration file.
86 Before adding Auto features to your app, you must first define the Auto
87 XML configuration file and add a manifest entry referencing your XML file.</p
[all...] |
| /frameworks/base/docs/html/training/performance/battery/network/ |
| analyze-data.jd | 19 In the previous section, you tagged your app code with traffic identifiers, ran tests, and
21 collected and directs you to actions for improving your app's networking performance and
33 to send or receive data, and with keeping the mobile radio active for long periods. If your app
66 If the network traffic for your app looks similar to the graph in Figure 2, you are in good
74 If the network traffic for your app looks more like the graph in Figure 1, it's time to take a
75 harder look at how your app accesses the network. You should start by analyzing what types of
76 network traffic your app is generating.
83 When you look at the network traffic generated by your app, you need to understand the source of
84 the traffic, so you can optimize it appropriately. Frequent network activity generated by your
87 how to analyze the types of network traffic being generated by your app and directs you t
[all...] |
| index.jd | 5 page.metaDescription=Learn how to optimize your app to reduce battery drain and use network resources efficiently.
16 Requests that your app makes to the network are a major cause of battery drain because they turn
24 This lesson shows you how to tag your app's source code to categorize, visualize and color
25 your network requests according to how they are initiated. From there, each category
26 identifies areas of your app that you can make more battery-efficient.
38 Learn how to instrument your app's code and gather data on its use of network resources.
46 Learn how to analyze your app's use of network resources in response to user actions
55 Learn how to optimize your app's use of network resources in response to user actions
64 Learn how to optimize your app's requests for network resources to reduce
73 Learn how to optimize your app's requests for network resources and to reduc
[all...] |
| /frameworks/base/docs/html/about/ |
| start.jd | 10 and monetize your app.</p>
32 the Android user experience. Although you may know what a user will <em>do</em> with your app, you
33 should pause to focus on how a user will <em>interact</em> with it. Your design should be sleek,
42 <p>Once your design is finalized, all you need are the tools to turn your app ideas into reality.
45 With the power of Android, there's no limit to the power of your apps.</p>
55 <p>Now your app is complete. You've built it to support a variety of screen sizes and
56 densities, and tested it on the Android emulator and on real devices. You're ready to ship your app.</p>
58 <p>How you proceed depends on a variety of factors, such as your monetization strategy and which
59 types of devices your app supports. Everything you need to get started with this process i
[all...] |
| /frameworks/base/docs/html/google/play/licensing/ |
| index.jd | 2 page.metaDescription=Information on using the licensing feature of Google Play to protect your apps.
9 applications that you publish on Google Play. With Google Play Licensing, your application can
20 <p>The licensing service is a secure means of controlling access to your applications. When an
22 response using a key pair that is uniquely associated with the application. Your application
34 to initiate the download of an APK expansion file. In which case, the request that your application
36 URL of the expansion files. For information about downloading expansion files for your application,
41 your applications, read the following documents:</p>
50 <dd>Explains how to set up your Google Play account, development environment, and
51 testing environment in order to add licensing to your app.</dd>
53 Licensing to Your App</a></strong></dt
[all...] |
| overview.jd | 12 <li>Licensing allows you to verify your app was purchased from Google Play</li>
13 <li>Your app maintains control of how it enforces its licensing status</li>
35 <p>The request starts when your application makes a request to a service hosted by
38 the result to your application, which can allow or disallow further use of the
49 <p class="img-caption"><strong>Figure 1.</strong> Your application initiates a
62 information about the application and user—your application and the Google Play client work
65 <p>To help you add licensing to your application, the Android SDK provides a downloadable set of
66 library sources that you can include in your application project: the Google Market
67 Licensing package. The License Verification Library (LVL) is a library you can add to your
70 the LVL added to your application, your application can determine its licensing status for th
[all...] |
| /frameworks/base/docs/html/training/basics/activity-lifecycle/ |
| index.jd | 39 <p>As a user navigates through, out of, and back to your app, the
40 {@link android.app.Activity} instances in your app transition between different states in their
41 lifecycle. For instance, when your
46 lifecycle methods on your activity as it moves into the background (where the activity is no
49 <p>Within the lifecycle callback methods, you can declare how your activity behaves when the
56 android.app.Activity} instance receives and how you can use them so your activity does what the
57 user expects and does not consume system resources when your activity doesn't need them.</p>
63 <dd>Learn the basics about the activity lifecycle, how the user can launch your app, and how
66 <dd>Learn what happens when your activity is paused (partially obscured) and resumed and what you
69 <dd>Learn what happens when the user completely leaves your activity and returns to it.</dd
[all...] |
| /external/libusb/ |
| PORTING | 13 your target platform.
15 In terms of USB I/O, your backend provides functionality to submit
17 layers, based on the async interface). Your backend must also provide
20 Your backend must also provide an event handling function to "reap" ongoing
30 For libusb to work, your event handling function obviously needs to be called
31 at various points in time. Your backend must provide a set of file descriptors
36 which can be passed to poll(). If something similar is not true for your
48 Your implementations of these functions will need to call various internal
52 You probably want to skim over *all* the documentation before starting your
64 1. Modify configure.ac to detect your platform appropriately (see the OS_LINU
[all...] |
| /frameworks/base/docs/html/distribute/analyze/ |
| improve-roi.jd | 1 page.title=Improve Your Marketing ROI
2 page.metaDescription=Combine the power of Analytics with other data sources to understand the performance of each of your marketing channels.
8 You want to get your apps in the hands of as many interested people as
19 download your app using different ad networks, formats, and payment methods.
28 ROI analysis for each of your marketing channels. You can tailor
29 your acquisition strategies and maximize in-app revenue. Here is an example
95 Depending on your business objectives you can approach acquisition marketing
97 picture in order to optimize your campaigns — factoring engagement and
115 You can use a wide range of networks to drive installs of your apps. With
117 you setup your URLs to pass the correct parameters, you'll see networ
[all...] |
| start.jd | 2 page.metaDescription=Get advanced insight into how players discover and play your games.
11 measuring your app's use by writing one line of code ? or less! Google
13 options to fit your needs. Take a look at these options and choose the right
19 help you make the best decisions about your app, by reviewing the <a href=
37 your Google Analytics account</a>.</li>
38 <li>Write down your tracking ID. </li>
39 <li>Initialize Google Analytics in your app to start measuring activity immediately.</li>
45 step-by-step implementation guide</a> to get Google Analytics working in your
55 Plugin, you add Google Analytics to your app as an in-line part of your
[all...] |
| /frameworks/base/docs/html/distribute/engage/ |
| beta.jd | 11 feedback on early versions of your app, then make improvements and correct
20 <p>Testing your app with a select group of users will give you a chance to fix any technical or user experience issues before you release it widely, so that you can be confident about releasing the best version of your app to the majority of your users. Feedback from your test users won't affect your app?s public rating.</p>
35 has the link to be able to join your beta with just one click. One of the
43 restrict which users can access your beta, you have a new option: you can
46 to join your beta via a one-click opt-in link.
52 can also move closed betas to an open beta while maintaining your existin
[all...] |
| /frameworks/base/docs/html/distribute/users/ |
| experiments.jd | 11 for your app is vital. Store Listing Experiments let you test combinations of
29 your experiments.
37 <li>Start testing with your app icon, because it can have a huge impact on
38 whether users pick your app from search results and category lists.
41 <li>Test all of your listing?s attributes; after icons, test screenshots and
44 your store listing?s page.
48 <h3 id="graphics">Tips for your graphics and text</h3>
50 <li>Create up to three alternatives for your hi-res icon, feature graphic,
54 <li>Set up a Global experiment for graphics against your default language or
60 confirm and improve your findings
[all...] |
| your-listing.jd | 2 page.metaDescription=Make your listing page compelling and integrate it into your marketing campaigns.
9 Your Google Play app listings are a vital part of your app marketing, from
24 Be sure to supply a variety of high-quality graphic assets to showcase your
25 apps or brand on Google Play search results and your product details pages.
42 (sometimes referred to as the app icon) is the first impression of your app.
44 important to make sure your launcher icon is crisp and high quality. To do
46 of the icon in your apps. Learn more about <a href=
61 Be sure to showcase how your apps look, their important features, and wha
[all...] |
| /frameworks/base/docs/html/training/wearables/apps/ |
| creating-app-china.jd | 13 <li><a href="#ChinaSDK">Support Your App on Android Wear for China</a></li>
41 drop it into your app. You do not need to write any new code. Instead, you change several project
42 configuration settings, and re-compile your app.
50 <h2 id = "ChinaSDK">Support Your App on Android Wear for China</h2>
53 <p>In order to support your wearable app on all handsets, you must download and add the Google Play
54 Services 7.8.87 client library as a Maven repository in your project, configure your
55 development project to use it, and re-compile your app.
61 repository to your project:</p>
68 from the downloaded zip file, and placing it into the root directory of your project
[all...] |
| /frameworks/base/docs/html/distribute/googleplay/edu/ |
| start.jd | 13 <li><a href="#prepare">Prepare Your Apps</a></li>
14 <li><a href="#publish">Publish Your Apps</a></li>
22 processes you currently use to manage your Android or Chrome apps.
46 Console</a>, where you?ll manage your details, apps, and payments.
54 Prepare Your Apps
59 By participating in Google Play for Education you?ll be placing your apps
61 there are specific guidelines and policies your apps should meet and specific
72 your apps. See the <a href=
78 Also, make sure that you're familiar with the policies that your app must
108 Assess your app against the criteria listed in the <a href
[all...] |
| /frameworks/base/docs/html/guide/topics/manifest/ |
| supports-screens-element.jd | 27 <dd itemprop="description">Lets you specify the screen sizes your application supports and enable <a
29 larger than what your application supports. It's important that you always use this element in your
30 application to specify the screen sizes your application supports.
34 extra work to make your application work on screens larger than a handset device. However, it's
35 often important that you optimize your application's UI for different screen sizes by providing <a
40 <p>However, if your application does not work well when resized to fit different screen sizes, you
41 can use the attributes of the {@code <supports-screens>} element to control whether your
46 results, screen compatibility mode will scale your UI by emulating a <em>normal</em> size
48 causes pixelation and blurring of your UI, so it's better if you optimize your UI for larg
[all...] |
