Home
last modified time | relevance | path

Searched refs:consume (Results 1 – 25 of 51) sorted by relevance

123

/frameworks/compile/mclinker/lib/Target/Mips/
DMipsPLT.h35 Fragment* consume();
DMipsGOTPLT.h35 Fragment* consume();
DMipsGOTPLT.cpp51 Fragment* MipsGOTPLT::consume() in consume() function in mcld::MipsGOTPLT
DMipsPLT.cpp119 Fragment* MipsPLT::consume() in consume() function in mcld::MipsPLT
DMipsRelocator.cpp737 plt = getTarget().getPLT().consume(); in getPLTAddress()
739 Fragment* got = getTarget().getGOTPLT().consume(); in getPLTAddress()
/frameworks/base/docs/html-intl/intl/zh-cn/google/play/billing/
Dapi.jd18 <li><a href="#consume">消耗应用内商品</a>
45 …托管的商品在被购买后,必须先向 Google Play 发送消耗请求进行消耗,然后才能供用户再次购买。要详细了解应用内商品的消耗,请参阅<a href="#consume">消耗商品</a></p>
78 <h2 id="consume">消耗应用内商品</h2>
/frameworks/base/docs/html/google/play/billing/
Dapi.jd19 <li><a href="#consume">Consuming In-app Products</a>
48consume managed items within your application. You would typically implement consumption for items…
88 <h2 id="consume">Consuming In-app Products</h2>
123 <li>If the purchase was successful, consume the purchase by making a {@code consumePurchase} call.<…
127 …ser owns any outstanding consumable in-app products; if so, make sure to consume and provision tho…
130 <li>If there are any consumable in-app products, consume the items by calling {@code consumePurchas…
Dversions.jd30 <li>An API to consume a purchase of an inapp item. All purchases of one-time in-app items are consu…
Dbilling_reference.jd87 <td>Failure to consume since item is not owned</td>
/frameworks/base/docs/html/training/in-app-billing/
Dpurchase-iab-products.jd54consume the purchase to allow the user to buy it again. To learn how to consume purchases, see th…
66 // consume the gas and update the UI
110 …the method takes is the {@code Purchase} object representing the item to consume. The second argum…
111 <p>In this example, you want to consume the gas item that the user has previously purchased in your…
/frameworks/base/docs/html/training/basics/network-ops/
Dindex.jd45 consume XML data.</p>
80 <dd>Learn how to parse and consume XML data.</dd>
Dxml.jd25 <li><a href="#consume">Consume XML Data</a></li>
377 <h2 id="consume">Consume XML Data</h2>
/frameworks/native/libs/input/tests/
DInputPublisherAndConsumer_test.cpp92 status = mConsumer->consume(&mEventFactory, true /*consumeBatches*/, -1, &consumeSeq, &event); in PublishAndConsumeKeyEvent()
175 status = mConsumer->consume(&mEventFactory, true /*consumeBatches*/, -1, &consumeSeq, &event); in PublishAndConsumeMotionEvent()
/frameworks/base/docs/html/guide/components/
Dindex.jd40 …es and how you can use them so your activity does what the user expects and does not consume system
/frameworks/base/docs/html/google/gcm/
Dindex.jd33 up to 4kb of payload data (so apps like instant messaging can consume the message directly).
/frameworks/native/include/input/
DInputTransport.h303 status_t consume(InputEventFactoryInterface* factory, bool consumeBatches,
/frameworks/base/docs/html/training/basics/activity-lifecycle/
Dindex.jd57 user expects and does not consume system resources when your activity doesn't need them.</p>
Dpausing.jd70 <li>Stop animations or other ongoing actions that could consume CPU.</li>
/frameworks/base/cmds/uiautomator/cmds/uiautomator/
Duiautomator100 # look for --nohup: if found, consume it and trap SIG_HUP, otherwise just
/frameworks/native/cmds/flatland/
DREADME.txt16 that consume much CPU cycles, memory bandwidth, or might otherwise interfere
/frameworks/base/docs/html/training/displaying-bitmaps/
Dindex.jd45 consume your available memory budget leading to an application crash due to the dreaded
/frameworks/base/core/jni/
Dandroid_view_InputEventReceiver.cpp236 status_t status = mInputConsumer.consume(&mInputEventFactory, in consumeEvents()
/frameworks/native/opengl/specs/
DEGL_ANDROID_blob_cache.txt38 programming for a long time. It can consume seconds of CPU cycles during
/frameworks/base/docs/html/training/wearables/watch-faces/
Dperformance.jd138 <p>Animations are often computationally expensive and consume a significant amount of power. Most
/frameworks/base/docs/html/training/location/
Dreceive-location-updates.jd155 considered a coarse level of accuracy, and is likely to consume less
168 coarse level of accuracy, and is likely to consume less power.</li>

123