| /developers/samples/android/wearable/wear/Notifications/ |
| CONTRIB.md | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
13 * If you work for a company that wants to allow you to contribute your work,
19 accept your pull requests.
23 1. Submit an issue describing your proposed change to the repo in question.
24 1. The repo owner will respond to your issue promptly.
25 1. If your proposed change is accepted, and you haven't already done so, sign a
27 1. Fork the desired repo, develop and test your code changes.
28 1. Ensure that your code adheres to the existing style in the sample to which
33 1. Ensure that your code has an appropriate set of unit tests which all pass
[all...] |
| /developers/samples/android/wearable/wear/Quiz/ |
| CONTRIB.md | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
13 * If you work for a company that wants to allow you to contribute your work,
19 accept your pull requests.
23 1. Submit an issue describing your proposed change to the repo in question.
24 1. The repo owner will respond to your issue promptly.
25 1. If your proposed change is accepted, and you haven't already done so, sign a
27 1. Fork the desired repo, develop and test your code changes.
28 1. Ensure that your code adheres to the existing style in the sample to which
33 1. Ensure that your code has an appropriate set of unit tests which all pass
[all...] |
| /developers/samples/android/wearable/wear/RecipeAssistant/ |
| CONTRIB.md | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
13 * If you work for a company that wants to allow you to contribute your work,
19 accept your pull requests.
23 1. Submit an issue describing your proposed change to the repo in question.
24 1. The repo owner will respond to your issue promptly.
25 1. If your proposed change is accepted, and you haven't already done so, sign a
27 1. Fork the desired repo, develop and test your code changes.
28 1. Ensure that your code adheres to the existing style in the sample to which
33 1. Ensure that your code has an appropriate set of unit tests which all pass
[all...] |
| /developers/samples/android/wearable/wear/SkeletonWearableApp/ |
| CONTRIB.md | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
13 * If you work for a company that wants to allow you to contribute your work,
19 accept your pull requests.
23 1. Submit an issue describing your proposed change to the repo in question.
24 1. The repo owner will respond to your issue promptly.
25 1. If your proposed change is accepted, and you haven't already done so, sign a
27 1. Fork the desired repo, develop and test your code changes.
28 1. Ensure that your code adheres to the existing style in the sample to which
33 1. Ensure that your code has an appropriate set of unit tests which all pass
[all...] |
| /developers/samples/android/wearable/wear/SpeedTracker/ |
| CONTRIB.md | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
13 * If you work for a company that wants to allow you to contribute your work,
19 accept your pull requests.
23 1. Submit an issue describing your proposed change to the repo in question.
24 1. The repo owner will respond to your issue promptly.
25 1. If your proposed change is accepted, and you haven't already done so, sign a
27 1. Fork the desired repo, develop and test your code changes.
28 1. Ensure that your code adheres to the existing style in the sample to which
33 1. Ensure that your code has an appropriate set of unit tests which all pass
[all...] |
| /developers/samples/android/wearable/wear/SynchronizedNotifications/ |
| CONTRIB.md | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
13 * If you work for a company that wants to allow you to contribute your work,
19 accept your pull requests.
23 1. Submit an issue describing your proposed change to the repo in question.
24 1. The repo owner will respond to your issue promptly.
25 1. If your proposed change is accepted, and you haven't already done so, sign a
27 1. Fork the desired repo, develop and test your code changes.
28 1. Ensure that your code adheres to the existing style in the sample to which
33 1. Ensure that your code has an appropriate set of unit tests which all pass
[all...] |
| /developers/samples/android/wearable/wear/Timer/ |
| CONTRIB.md | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
13 * If you work for a company that wants to allow you to contribute your work,
19 accept your pull requests.
23 1. Submit an issue describing your proposed change to the repo in question.
24 1. The repo owner will respond to your issue promptly.
25 1. If your proposed change is accepted, and you haven't already done so, sign a
27 1. Fork the desired repo, develop and test your code changes.
28 1. Ensure that your code adheres to the existing style in the sample to which
33 1. Ensure that your code has an appropriate set of unit tests which all pass
[all...] |
| /developers/samples/android/wearable/wear/WatchFace/ |
| CONTRIB.md | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
13 * If you work for a company that wants to allow you to contribute your work,
19 accept your pull requests.
23 1. Submit an issue describing your proposed change to the repo in question.
24 1. The repo owner will respond to your issue promptly.
25 1. If your proposed change is accepted, and you haven't already done so, sign a
27 1. Fork the desired repo, develop and test your code changes.
28 1. Ensure that your code adheres to the existing style in the sample to which
33 1. Ensure that your code has an appropriate set of unit tests which all pass
[all...] |
| /developers/samples/android/wearable/wear/WatchViewStub/ |
| CONTRIB.md | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
13 * If you work for a company that wants to allow you to contribute your work,
19 accept your pull requests.
23 1. Submit an issue describing your proposed change to the repo in question.
24 1. The repo owner will respond to your issue promptly.
25 1. If your proposed change is accepted, and you haven't already done so, sign a
27 1. Fork the desired repo, develop and test your code changes.
28 1. Ensure that your code adheres to the existing style in the sample to which
33 1. Ensure that your code has an appropriate set of unit tests which all pass
[all...] |
| /developers/samples/android/wearable/wear/WearSpeakerSample/ |
| CONTRIBUTING | 1 # How to become a contributor and submit your own code
5 We'd love to accept your sample apps and patches! Before we can take them, we
13 * If you work for a company that wants to allow you to contribute your work,
19 accept your pull requests.
23 1. Submit an issue describing your proposed change to the repo in question.
24 1. The repo owner will respond to your issue promptly.
25 1. If your proposed change is accepted, and you haven't already done so, sign a
27 1. Fork the desired repo, develop and test your code changes.
28 1. Ensure that your code adheres to the existing style in the sample to which
33 1. Ensure that your code has an appropriate set of unit tests which all pass
[all...] |
| /frameworks/base/docs/html/distribute/engage/ |
| analytics.jd | 2 page.metaDescription=Use Google Analytics to learn what your users like and what keeps them coming back.
14 Link your Google Play Developer Console with Google Analytics to learn much
15 more about how users interact with your app — before and after they
20 Start by discovering how many people visit your Google Play listing page,
21 where they come from, and how many go on to install your app. Once the app is
22 launched, use Google Analytics to see which of your features are most
29 update your landing page and your app. <a href=
35 takes just a few moments. You can also link your Google Analytics account to
36 Admob to start gaining more user insights to improve your in-app marketing
[all...] |
| /frameworks/base/docs/html/training/in-app-billing/ |
| test-iab-app.jd | 1 page.title=Testing Your In-app Billing Application
17 <li><a href="#PlayItemTest">Test with Your Own Product IDs</a></li>
28 <p>To ensure that In-app Billing is functioning correctly in your application, you should test the test the application before you publish it on Google Play. Early testing also helps to ensure that the user flow for purchasing in-app items is not confusing or slow, and that users can see their newly purchased items in a timely way.</p>
31 Test your In-app Billing application with static responses by using Google Play?s reserved product IDs.By using reserved product IDs instead of actual product IDs, you can test the purchase flow without specifying an actual payment method or transferring money. To learn more about the reserved product IDs, see <a href="{@docRoot}google/play/billing/billing_testing.html">Testing In-app Billing</a>.
33 <h2 id="PlayItemTest">Test with Your Own Product IDs</h2>
34 <p>Because Google Play does not allow you to use your developer account to directly purchase in-app products that you have created yourself, you'll need to create test acccounts under your developer account profile. To create a test account, simply enter a valid Google email address. Users with these test accounts will then be able to make in-app-billing purchases from uploaded, unpublished applications that you manage.</p>
35 <p>To test your In-app Billing Version 3 application using your own product IDs:
37 <li>In the Developer Console, add one or more tester accounts to the developer account that you are using to publish your application
[all...] |
| /frameworks/base/docs/html/training/performance/battery/network/ |
| action-server-traffic.jd | 19 Network traffic sent by server programs to your app can be challenging to optimize. A
20 solution to this problem is for your appp to periodically poll the server to check for updates.
21 This approach can waste network connection and power when your app starts up a device's radio,
23 for the to notify your app when it has new data, but figuring out how to send a notification
24 from your server to potentially thousands of devices was previously no easy feat.
29 service solves this communication problem by allowing your servers to send notifications to
30 instances of your app wherever they are installed, enabling greater network efficiency and
44 app server to your app. Using GCM, your app server uses a message-passing
45 mechanism to notify your app that there is new data available. This approach eliminates networ
[all...] |
| /development/ndk/platforms/android-9/arch-mips/include/asm/ |
| war.h | 27 #error Check setting of R4600_V1_INDEX_ICACHEOP_WAR for your platform
31 #error Check setting of R4600_V1_HIT_CACHEOP_WAR for your platform
35 #error Check setting of R4600_V2_HIT_CACHEOP_WAR for your platform
39 #error Check setting of R5432_CP0_INTERRUPT_WAR for your platform
42 #error Check setting of BCM1250_M3_WAR for your platform
46 #error Check setting of SIBYTE_1956_WAR for your platform
50 #error Check setting of MIPS4K_ICACHE_REFILL_WAR for your platform
54 #error Check setting of MIPS_CACHE_SYNC_WAR for your platform
57 #error Check setting of TX49XX_ICACHE_INDEX_INV_WAR for your platform
61 #error Check setting of RM9000_CDEX_SMP_WAR for your platfor
[all...] |
| /frameworks/base/docs/html/distribute/users/ |
| banners.jd | 1 page.title=Add An App Install Banner On Your Mobile Website
2 page.metaDescription=Add a native app install banner to your mobile website and allow visitors to install your app straight from your site.
28 Add a native app install banner to your mobile website and offer visitors the
29 added convenience of installing your app or game straight from your site.
35 class="external-link">add a native app install banner</a> to your mobile
44 manifest file. In the manifest you define how your app will appear on the
46 over the banner for your Web App. Then, as long as your site is delivere
[all...] |
| /prebuilts/ndk/current/platforms/android-12/arch-mips/usr/include/asm/ |
| war.h | 27 #error Check setting of R4600_V1_INDEX_ICACHEOP_WAR for your platform
31 #error Check setting of R4600_V1_HIT_CACHEOP_WAR for your platform
35 #error Check setting of R4600_V2_HIT_CACHEOP_WAR for your platform
39 #error Check setting of R5432_CP0_INTERRUPT_WAR for your platform
42 #error Check setting of BCM1250_M3_WAR for your platform
46 #error Check setting of SIBYTE_1956_WAR for your platform
50 #error Check setting of MIPS4K_ICACHE_REFILL_WAR for your platform
54 #error Check setting of MIPS_CACHE_SYNC_WAR for your platform
57 #error Check setting of TX49XX_ICACHE_INDEX_INV_WAR for your platform
61 #error Check setting of RM9000_CDEX_SMP_WAR for your platfor
[all...] |
| /prebuilts/ndk/current/platforms/android-13/arch-mips/usr/include/asm/ |
| war.h | 27 #error Check setting of R4600_V1_INDEX_ICACHEOP_WAR for your platform
31 #error Check setting of R4600_V1_HIT_CACHEOP_WAR for your platform
35 #error Check setting of R4600_V2_HIT_CACHEOP_WAR for your platform
39 #error Check setting of R5432_CP0_INTERRUPT_WAR for your platform
42 #error Check setting of BCM1250_M3_WAR for your platform
46 #error Check setting of SIBYTE_1956_WAR for your platform
50 #error Check setting of MIPS4K_ICACHE_REFILL_WAR for your platform
54 #error Check setting of MIPS_CACHE_SYNC_WAR for your platform
57 #error Check setting of TX49XX_ICACHE_INDEX_INV_WAR for your platform
61 #error Check setting of RM9000_CDEX_SMP_WAR for your platfor
[all...] |
| /prebuilts/ndk/current/platforms/android-14/arch-mips/usr/include/asm/ |
| war.h | 27 #error Check setting of R4600_V1_INDEX_ICACHEOP_WAR for your platform
31 #error Check setting of R4600_V1_HIT_CACHEOP_WAR for your platform
35 #error Check setting of R4600_V2_HIT_CACHEOP_WAR for your platform
39 #error Check setting of R5432_CP0_INTERRUPT_WAR for your platform
42 #error Check setting of BCM1250_M3_WAR for your platform
46 #error Check setting of SIBYTE_1956_WAR for your platform
50 #error Check setting of MIPS4K_ICACHE_REFILL_WAR for your platform
54 #error Check setting of MIPS_CACHE_SYNC_WAR for your platform
57 #error Check setting of TX49XX_ICACHE_INDEX_INV_WAR for your platform
61 #error Check setting of RM9000_CDEX_SMP_WAR for your platfor
[all...] |
| /prebuilts/ndk/current/platforms/android-15/arch-mips/usr/include/asm/ |
| war.h | 27 #error Check setting of R4600_V1_INDEX_ICACHEOP_WAR for your platform
31 #error Check setting of R4600_V1_HIT_CACHEOP_WAR for your platform
35 #error Check setting of R4600_V2_HIT_CACHEOP_WAR for your platform
39 #error Check setting of R5432_CP0_INTERRUPT_WAR for your platform
42 #error Check setting of BCM1250_M3_WAR for your platform
46 #error Check setting of SIBYTE_1956_WAR for your platform
50 #error Check setting of MIPS4K_ICACHE_REFILL_WAR for your platform
54 #error Check setting of MIPS_CACHE_SYNC_WAR for your platform
57 #error Check setting of TX49XX_ICACHE_INDEX_INV_WAR for your platform
61 #error Check setting of RM9000_CDEX_SMP_WAR for your platfor
[all...] |
| /prebuilts/ndk/current/platforms/android-16/arch-mips/usr/include/asm/ |
| war.h | 27 #error Check setting of R4600_V1_INDEX_ICACHEOP_WAR for your platform
31 #error Check setting of R4600_V1_HIT_CACHEOP_WAR for your platform
35 #error Check setting of R4600_V2_HIT_CACHEOP_WAR for your platform
39 #error Check setting of R5432_CP0_INTERRUPT_WAR for your platform
42 #error Check setting of BCM1250_M3_WAR for your platform
46 #error Check setting of SIBYTE_1956_WAR for your platform
50 #error Check setting of MIPS4K_ICACHE_REFILL_WAR for your platform
54 #error Check setting of MIPS_CACHE_SYNC_WAR for your platform
57 #error Check setting of TX49XX_ICACHE_INDEX_INV_WAR for your platform
61 #error Check setting of RM9000_CDEX_SMP_WAR for your platfor
[all...] |
| /prebuilts/ndk/current/platforms/android-17/arch-mips/usr/include/asm/ |
| war.h | 27 #error Check setting of R4600_V1_INDEX_ICACHEOP_WAR for your platform
31 #error Check setting of R4600_V1_HIT_CACHEOP_WAR for your platform
35 #error Check setting of R4600_V2_HIT_CACHEOP_WAR for your platform
39 #error Check setting of R5432_CP0_INTERRUPT_WAR for your platform
42 #error Check setting of BCM1250_M3_WAR for your platform
46 #error Check setting of SIBYTE_1956_WAR for your platform
50 #error Check setting of MIPS4K_ICACHE_REFILL_WAR for your platform
54 #error Check setting of MIPS_CACHE_SYNC_WAR for your platform
57 #error Check setting of TX49XX_ICACHE_INDEX_INV_WAR for your platform
61 #error Check setting of RM9000_CDEX_SMP_WAR for your platfor
[all...] |
| /prebuilts/ndk/current/platforms/android-18/arch-mips/usr/include/asm/ |
| war.h | 27 #error Check setting of R4600_V1_INDEX_ICACHEOP_WAR for your platform
31 #error Check setting of R4600_V1_HIT_CACHEOP_WAR for your platform
35 #error Check setting of R4600_V2_HIT_CACHEOP_WAR for your platform
39 #error Check setting of R5432_CP0_INTERRUPT_WAR for your platform
42 #error Check setting of BCM1250_M3_WAR for your platform
46 #error Check setting of SIBYTE_1956_WAR for your platform
50 #error Check setting of MIPS4K_ICACHE_REFILL_WAR for your platform
54 #error Check setting of MIPS_CACHE_SYNC_WAR for your platform
57 #error Check setting of TX49XX_ICACHE_INDEX_INV_WAR for your platform
61 #error Check setting of RM9000_CDEX_SMP_WAR for your platfor
[all...] |
| /prebuilts/ndk/current/platforms/android-19/arch-mips/usr/include/asm/ |
| war.h | 27 #error Check setting of R4600_V1_INDEX_ICACHEOP_WAR for your platform
31 #error Check setting of R4600_V1_HIT_CACHEOP_WAR for your platform
35 #error Check setting of R4600_V2_HIT_CACHEOP_WAR for your platform
39 #error Check setting of R5432_CP0_INTERRUPT_WAR for your platform
42 #error Check setting of BCM1250_M3_WAR for your platform
46 #error Check setting of SIBYTE_1956_WAR for your platform
50 #error Check setting of MIPS4K_ICACHE_REFILL_WAR for your platform
54 #error Check setting of MIPS_CACHE_SYNC_WAR for your platform
57 #error Check setting of TX49XX_ICACHE_INDEX_INV_WAR for your platform
61 #error Check setting of RM9000_CDEX_SMP_WAR for your platfor
[all...] |
| /prebuilts/ndk/current/platforms/android-9/arch-mips/usr/include/asm/ |
| war.h | 27 #error Check setting of R4600_V1_INDEX_ICACHEOP_WAR for your platform
31 #error Check setting of R4600_V1_HIT_CACHEOP_WAR for your platform
35 #error Check setting of R4600_V2_HIT_CACHEOP_WAR for your platform
39 #error Check setting of R5432_CP0_INTERRUPT_WAR for your platform
42 #error Check setting of BCM1250_M3_WAR for your platform
46 #error Check setting of SIBYTE_1956_WAR for your platform
50 #error Check setting of MIPS4K_ICACHE_REFILL_WAR for your platform
54 #error Check setting of MIPS_CACHE_SYNC_WAR for your platform
57 #error Check setting of TX49XX_ICACHE_INDEX_INV_WAR for your platform
61 #error Check setting of RM9000_CDEX_SMP_WAR for your platfor
[all...] |
| /frameworks/base/docs/html/distribute/analyze/ |
| understand-user-value.jd | 1 page.title=Understand the Value of Your Users
2 page.metaDescription=Understand what makes users come back to your app and improve retention.
10 exactly alike. You can explore what makes your different groups of users
11 unique and, in turn, how these groups respond to your app content, features,
12 and monetization strategies. The more you understand about what your users
13 respond to, the better you can tailor your apps to meet their needs.
22 the power to value your users in the way that makes the most sense to you.
26 By using Google Analytics goals, you can define specific actions in your app
27 that mean the most to your business: perhaps it?s important that your user
[all...] |
