| /frameworks/av/media/libstagefright/codecs/amrnb/common/include/ |
| D | mult.h | 111 Word32 product; in mult() local
117 SMULBB product, var1, var2 in mult()
118 MOV product, product, ASR #15 in mult()
119 CMP product, 0x7FFF in mult()
120 MOVGE product, 0x7FFF in mult()
123 return ((Word16) product); in mult()
132 Word32 product;
138 : "=r"(product)
142 : "=r"(product)
143 : "r"(product)
[all …]
|
| D | mac_32.h | 112 Word16 product; in Mac_32() local
116 product = mult(L_var1_hi, L_var2_lo, pOverflow); in Mac_32()
117 L_var3 = L_mac(L_var3, product, 1, pOverflow); in Mac_32()
119 product = mult(L_var1_lo, L_var2_hi, pOverflow); in Mac_32()
120 L_var3 = L_mac(L_var3, product, 1, pOverflow); in Mac_32()
131 Word16 product; in Mac_32_16() local
135 product = mult(L_var1_lo, var2, pOverflow); in Mac_32_16()
136 L_var3 = L_mac(L_var3, product, 1, pOverflow); in Mac_32_16()
|
| D | l_mult.h | 112 Word32 product; in L_mult() local
118 SMULBB product, var1, var2 in L_mult()
119 QADD result, product, product in L_mult()
132 Word32 product;
137 : "=r"(product)
143 : "r"(product), "r"(product)
|
| D | basic_op_arm_v5.h | 226 Word32 product; in L_mult() local
232 SMULBB product, var1, var2 in L_mult()
233 QADD result, product, product in L_mult()
265 Word32 product; in L_msu() local
272 SMULBB product, var1, var2 in L_msu()
273 QDSUB result, L_var3, product in L_msu()
396 Word32 product; in mult() local
402 SMULBB product, var1, var2 in mult()
403 MOV product, product, ASR #15 in mult()
404 CMP product, 0x7FFF in mult()
[all …]
|
| D | l_msu.h | 111 Word32 product; in L_msu() local
118 SMULBB product, var1, var2 in L_msu()
119 QDSUB result, L_var3, product in L_msu()
132 Word32 product;
138 : "=r"(product)
144 : "r"(ra), "r"(product)
|
| D | basic_op.h | 171 Word16 product; in Mac_32() local
175 product = mult(L_var1_hi, L_var2_lo, pOverflow); in Mac_32()
176 L_var3 = L_mac(L_var3, product, 1, pOverflow); in Mac_32()
178 product = mult(L_var1_lo, L_var2_hi, pOverflow); in Mac_32()
179 L_var3 = L_mac(L_var3, product, 1, pOverflow); in Mac_32()
214 Word16 product; in Mac_32_16() local
218 product = mult(L_var1_lo, var2, pOverflow); in Mac_32_16()
219 L_var3 = L_mac(L_var3, product, 1, pOverflow); in Mac_32_16()
|
| D | basic_op_arm_gcc_v5.h | 246 Word32 product; in L_mult() local
251 : "=r"(product) in L_mult()
257 : "r"(product), "r"(product) in L_mult()
291 Word32 product; in L_msu() local
297 : "=r"(product) in L_msu()
303 : "r"(ra), "r"(product) in L_msu()
481 Word32 product; in mult() local
494 : "=&r*i"(product) in mult()
498 return ((Word16) product); in mult()
|
| D | basic_op_c_equivalent.h | 455 register Word32 product; in mult() local
457 product = ((Word32) var1 * var2) >> 15; in mult()
463 if (product > 0x00007fffL) in mult()
466 product = (Word32) MAX_16; in mult()
472 return ((Word16) product); in mult()
|
| /frameworks/base/docs/html/training/in-app-billing/ |
| D | list-iab-products.jd | 32 <p>Before publishing your In-app Billing application, you'll need to define the product list of dig…
35 …>From the Developer Console, you can define product information for in-app products and associate …
37 <p>To add new in-app products to your product list:</p>
44 …product, then complete the form to specify the product information such as the item’s unique produ…
45 <li>Once you have completed the form, activate the product so that your application can purchase it…
49 …e in-app products that are associated with your application (such as the product’s price, title, d…
50 …product IDs for the products explicitly. You can manually find the product IDs from the Developer …
51 <p>To retrieve the product details, call {@code queryInventoryAsync(boolean, List, QueryInventoryFi…
53 <li>The first input argument indicates whether product details should be retrieved (should be set t…
54 <li>The {@code List} argument consists of one or more product IDs (also called SKUs) for the produc…
|
| D | test-iab-app.jd | 31 …product IDs.By using reserved product IDs instead of actual product IDs, you can test the purchas…
35 <p>To test your In-app Billing Version 3 application using your own product IDs:
|
| /frameworks/base/docs/html/google/play/billing/ |
| D | billing_admin.jd | 28 few administrative tasks, including setting up and maintaining your product list on the Google Play
32 Google Wallet merchant account to create a product list and issue refunds to your users. If you
44 <p>The Google Play Developer Console provides a product list for each of your published
46 listed on an application's product list. Each application has its own product list; you cannot sell
47 items that are listed in another application's product list.</p>
49 <p>You can access an application's product list by clicking the <strong>In-App Products</strong>
55 <p>A product list specifies items you are selling in an application — in-app products,
56 …ions, or a combination of both. For each item, the product list contains information such as a pro…
57 product description, and price. The product list stores only metadata about the items
64 <strong>Figure 1.</strong> You can access an application's product list by clicking the
[all …]
|
| D | api.jd | 44 <p>You define your products using the Google Play Developer Console, including product type, SKU, p…
48 …sending a consumption request to Google Play. To learn more about in-app product consumption, see …
51 <p>A subscription is a product type offered in In-app Billing that lets you sell
74 …is successful, Google Play returns a {@code Bundle} containing a list of product IDs of the purcha…
75 …f product IDs in the query request. If the request is successful, Google Play returns a {@code Bun…
77 …product is not owned by the user, you can initiate a purchase for it. To start a purchase request,…
94 successfully purchases an in-app product, that purchase is recorded in Google
95 Play. Once an in-app product is purchased, it is considered to be "owned".
97 must send a consumption request for the "owned" in-app product before Google
98 Play makes it available for purchase again. Consuming the in-app product reverts
[all …]
|
| D | billing_reference.jd | 67 <td>Requested product is not available for purchase</td>
95 …product details for a list of product IDs. In the response {@code Bundle} sent by Google Play, the…
97 <p class="table-caption" id="product-details-table">
98 <strong>Table 2.</strong> Description of JSON fields with product item details returned from a {@co…
106 <td>The product ID for the product.</td>
110 <td>Value must be “inapp” for an in-app product or "subs" for
133 <td>Title of the product.</td>
137 <td>Description of the product.</td>
189 …<td>The item's product identifier. Every item has a product ID, which you must specify in the appl…
193 <td>The time the product was purchased, in milliseconds since the epoch (Jan 1, 1970).</td>
|
| D | billing_testing.jd | 161 special item that has a reserved product ID. Each reserved product ID returns a specific static
163 reserved product IDs. Also, you cannot specify the form of payment when you make a billing request
164 with a reserved product ID. Figure 1 shows the checkout flow for the reserved item that has the
165 product ID android.test.purchased.</p>
172 <p>You do not need to list the reserved products in your application's product list. Google Play
173 already knows about the reserved product IDs. Also, you do not need to upload your application to
174 the Developer Console to perform static response tests with the reserved product IDs. You can simply
176 reserved product IDs.</p>
184 <p>There are four reserved product IDs for testing static In-app Billing responses:</p>
188 <p>When you make an In-app Billing request with this product ID, Google Play responds as
[all …]
|
| D | billing_overview.jd | 73 product details from Google Play, order in-app products, and quickly restore
74 items based on users' product ownership</li>
96 the user has purchased an in-app product there is no refund window.</p>
100 only one app. That is, one application cannot purchase an in-app product
104 <p>In-app Billing supports different product types to give you flexibility in
110 …@docRoot}google/play/billing/api.html#producttypes">Learn more about the product types supported b…
116 <p>You can create a product list of
119 information such as the item’s unique product ID (also called its SKU), product
121 purchases for that product.</p>
125 products and product list, see
[all …]
|
| D | billing_subscriptions.jd | 52 <p>A <em>subscription</em> is a product type offered in In-app Billing that
61 products and add them to a product list, then set a price and optional trial
76 from the app's product details page in the Play Store app. For more information
116 product list for the app, then configure these attributes for each subscription
117 product:</p>
124 <li>Title: The title of the subscription product</li>
148 subscription, you can publish a new subscription product ID at a new price,
149 then offer it in your app instead of the original product. Users who have
278 subscription in your product list, set a valid number of days for the trial
283 period per subscription product.</p>
[all …]
|
| /frameworks/rs/ |
| D | CleanSpec.mk | 52 $(call add-clean-step, rm -rf $(OUT_DIR)/target/product/*/obj/SHARED_LIBRARIES/lib*.bc_intermediate…
53 $(call add-clean-step, rm -rf $(OUT_DIR)/target/product/*/obj/SHARED_LIBRARIES/librs*_intermediates)
54 $(call add-clean-step, rm -rf $(OUT_DIR)/target/product/*/obj/SHARED_LIBRARIES/libhellocomputendk_i…
|
| D | update_rs_prebuilts.sh | 127 sys_lib_dir=$MY_ANDROID_DIR/out/target/product/${SYS_NAMES[$i]}/system/lib
128 obj_lib_dir=$MY_ANDROID_DIR/out/target/product/${SYS_NAMES[$i]}/obj/lib
|
| /frameworks/multidex/ |
| D | NOTICE | 10 This product includes software developed as part of
22 This product includes software developed at
|
| /frameworks/native/libs/input/ |
| D | InputDevice.cpp | 59 if (deviceIdentifier.vendor !=0 && deviceIdentifier.product != 0) { in getInputDeviceConfigurationFilePathByDeviceIdentifier()
64 deviceIdentifier.vendor, deviceIdentifier.product, in getInputDeviceConfigurationFilePathByDeviceIdentifier()
75 deviceIdentifier.vendor, deviceIdentifier.product), in getInputDeviceConfigurationFilePathByDeviceIdentifier()
|
| /frameworks/native/include/input/ |
| D | InputDevice.h | 30 bus(0), vendor(0), product(0), version(0) { in InputDeviceIdentifier()
39 uint16_t product; member
|
| /frameworks/ml/bordeaux/service/src/android/bordeaux/services/ |
| D | BaseCluster.java | 105 double product = 0f; in computeDistance() local
107 product += vector1[i] * vector2[i]; in computeDistance()
109 double radian = Math.acos(Math.min(product, 1f)); in computeDistance()
|
| /frameworks/base/services/core/jni/ |
| D | com_android_server_UsbHostManager.cpp | 73 char *product = usb_device_get_product_name(device); in usb_device_added() local
78 jstring productName = AndroidRuntime::NewStringLatin1(env, product); in usb_device_added()
91 free(product); in usb_device_added()
|
| /frameworks/base/docs/html/tools/building/ |
| D | plugin-for-gradle.jd | 52 product and build configurations for the same module. This is useful when you want to
330 Build variants are combinations of product flavors and build types. Product flavors represent
331 product build versions of an app, such as free and paid. Build types represent the build
333 generates APKs for each combination of product flavor and build type.</p>
340 <p>Adding two product flavors, <em>demo</em> and <em>full</em> along
384 and two <em>dimensions</em> of product flavors, one for app type (demo or full) and one for
400 <p class="note"><strong>Note:</strong> The build type and product flavor source directories are opt…
402 as you add build types and product flavors to the build configuration files. The build system does …
407 the default <em>debug</em> and <em>release</em> build variants in projects with no product flavors,
415 <p>For projects that define a set of product flavors, the build system merges the build type, produ…
[all …]
|
| D | configuring-gradle.jd | 34 to show you how to use build variants based on product flavors and build types.</p>
220 <p>The build system uses <em>product flavors</em> to create different product versions of your app.
221 Each product version of your app can have different features or device requirements. The build
222 system also uses build types to apply different build and packaging settings to each product versio…
223 Each product flavor and build type combination forms a build variant. The build system generates a
229 and two product flavors for app type (demo and full). For more information on advanced uses of
236 <p>To create different product versions of your app:</p>
239 <li>Define product flavors in the build file.</li>
252 <h3>Define product flavors in the build file</h3>
254 <p>To define two product flavors, edit the build file for the app module to add the following
[all …]
|