| /frameworks/av/media/libstagefright/foundation/ |
| D | ColorUtils.cpp | 194 ColorAspects::Transfer transfer) { in wrapColorAspectsIntoColorTransfer() argument
196 if (sTransfers.map(transfer, &res)) { in wrapColorAspectsIntoColorTransfer()
198 } else if (!isValid(transfer)) { in wrapColorAspectsIntoColorTransfer()
200 } else if (isDefined(transfer)) { in wrapColorAspectsIntoColorTransfer()
201 return kColorTransferExtendedStart + transfer; in wrapColorAspectsIntoColorTransfer()
204 return kColorTransferVendorStart + transfer; in wrapColorAspectsIntoColorTransfer()
210 int32_t transfer, ColorAspects::Transfer *aspect) { in unwrapColorAspectsFromColorTransfer() argument
211 if (sTransfers.map((ColorTransfer)transfer, aspect)) { in unwrapColorAspectsFromColorTransfer()
217 if (transfer >= (int32_t)kColorTransferVendorStart) { in unwrapColorAspectsFromColorTransfer()
221 if (transfer >= start && transfer < start + numTransfers) { in unwrapColorAspectsFromColorTransfer()
[all …]
|
| /frameworks/base/docs/html/training/beam-files/ |
| D | send-files.jd | 31 Android Beam file transfer. To send files, you request permission to use NFC and external
33 transfer.
36 The Android Beam file transfer feature has the following requirements:
40 Android Beam file transfer for large files is only available in Android 4.1 (API level 16)
44 Files you want to transfer must reside in external storage. To learn more about using
49 Each file you want to transfer must be world-readable. You can set this permission by
53 You must provide a file URI for the files you want to transfer. Android Beam file transfer
65 To allow your app to use Android Beam file transfer to send files from external storage using
122 <h3>Specify Android Beam file transfer</h3>
124 Since Android Beam file transfer is only available in Android 4.1 (API level 16) and later,
[all …]
|
| D | index.jd | 2 page.tags=NfcAdapter,Android Beam,share,file transfer
31 Android allows you to transfer large files between devices using the Android Beam file transfer
32 feature. This feature has a simple API and allows users to start the transfer process by simply
33 touching devices. In response, Android Beam file transfer automatically copies files from one
37 While the Android Beam file transfer API handles large amounts of data, the Android Beam NDEF
38 transfer API introduced in Android 4.0 (API level 14) handles small amounts of data such as
|
| D | receive-files.jd | 37 Android Beam file transfer copies files to a special directory on the receiving device. It also
44 When Android Beam file transfer finishes copying files to the receiving device, it posts a
97 <strong>Note:</strong> Android Beam file transfer is not the only source of an
105 To read files that Android Beam file transfer copies to the device, request the permission
129 Android Beam file transfer copies all the files in a single transfer to one directory
131 Android Beam file transfer notification points to the first transferred file. However, your
133 source other than Android Beam file transfer. To determine how you should handle the incoming
186 file transfer, the directory path points to the location of the other transferred files, if
210 Android Beam file transfer or from another app, but in both cases you can retrieve a directory
221 <strong>Note:</strong> For Android Beam file transfer, you receive a content URI in the
[all …]
|
| /frameworks/av/media/libnbaio/ |
| D | README.txt | 5 Note: as used here, "short transfer count" means the return value for
17 never return a short transfer count
22 return a short transfer count if not enough data
33 if configured to not block, then will return a short transfer count
38 return a short transfer count if not enough data
|
| /frameworks/av/include/media/stagefright/foundation/ |
| D | ColorUtils.h | 116 static int32_t wrapColorAspectsIntoColorTransfer(ColorAspects::Transfer transfer);
122 int32_t transfer, ColorAspects::Transfer *aspect);
128 int32_t range, int32_t standard, int32_t transfer, ColorAspects &aspects);
130 const ColorAspects &aspects, int32_t *range, int32_t *standard, int32_t *transfer);
135 int32_t *primaries, int32_t *transfer, int32_t *coeffs, bool *fullRange);
138 int32_t primaries, int32_t transfer, int32_t coeffs, bool fullRange,
160 const sp<AMessage> &format, int *range, int *standard, int *transfer);
|
| /frameworks/base/docs/html/training/sync-adapters/ |
| D | index.jd | 52 transfer schemes you design yourself:
59 Allows you to add data transfer code to the system in the form of callable components.
65 Allows you to automate data transfer based on a variety of criteria, including data changes,
73 The system only runs your data transfer when the device has network connectivity.
79 Allows you to centralize all of your app's data transfer tasks in one place, so that they
80 all run at the same time. Your data transfer is also scheduled in conjunction with data
89 integrate account management and authentication into your data transfer.
99 expectation that they transfer data regularly and efficiently, but not instantaneously. If
100 you need to do real-time data transfer, you should do it in an {@link android.os.AsyncTask} or
126 Learn how to encapsulate your data transfer code in a component that the sync
|
| D | creating-sync-adapter.jd | 53 The sync adapter component in your app encapsulates the code for the tasks that transfer
62 A class that wraps your data transfer code in an interface compatible with the sync adapter
77 find out how to load and schedule your data transfer.
92 data transfer code. Creating the class includes extending the sync adapter base class, defining
93 constructors for the class, and implementing the method where you define the data transfer
119 * Handle the transfer of data between a server and an
157 <h3>Add the data transfer code to onPerformSync()</h3>
159 The sync adapter component does not automatically do data transfer. Instead, it
160 encapsulates your data transfer code, so that the sync adapter framework can run the
161 data transfer in the background, without involvement from your app. When the framework is ready
[all …]
|
| D | creating-stub-provider.jd | 54 adapter to handle data transfer. To satisfy the sync adapter framework requirement for a
57 add a stub provider, you can then use a sync adapter to transfer data from any storage
201 create the component that encapsulates your data transfer code. This component is called a
|
| /frameworks/base/docs/html/training/efficient-downloads/ |
| D | efficient-network-access.jd | 32 <p>Using the wireless radio to transfer data is potentially one of your app's most significant sour…
41 <ol><li><b>Full power</b>: Used when a connection is active, allowing the device to transfer data a…
63 …transfer—plus an additional 5 seconds of tail time—followed by 12 seconds at the low e…
76 <p>Prefetching data is an effective way to reduce the number of independent data transfer sessions.…
114 Every time you initiate a connection—irrespective of the size of the associated data transfer…
116 …ed on indefinitely, resulting in a significant battery cost for almost no actual data transfer.</p>
118 <p>With that in mind it's important to bundle your data transfers and create a pending transfer que…
120 …The underlying philosophy of this approach is to transfer as much data as possible during each tra…
122 …d updates and regular prefetching should initiate the execution of your pending transfer queue.</p>
130 …transfer—such as downloading a full-sized image—should preempt regularly scheduled upd…
[all …]
|
| /frameworks/av/media/mtp/ |
| D | MtpDataPacket.cpp | 454 int length = transfer(request); in read()
462 int ret = transfer(request); in read()
481 int ret = transfer(request); in readData()
508 int length = transfer(request); in readDataHeader()
519 int ret = transfer(request); in writeDataHeader()
528 int ret = transfer(request); in write()
535 int ret = transfer(request); in write()
|
| D | MtpResponsePacket.cpp | 50 int ret = transfer(request); in read()
|
| D | MtpRequestPacket.cpp | 69 return transfer(request); in write()
|
| D | MtpPacket.h | 61 int transfer(struct usb_request* request);
|
| D | MtpPacket.cpp | 155 int MtpPacket::transfer(struct usb_request* request) { in transfer() function in android::MtpPacket
|
| /frameworks/base/media/mca/filterfw/java/android/filterfw/core/ |
| D | FinalPort.java | 39 super.transfer(null); in setFieldFrame()
|
| D | ProgramPort.java | 44 public synchronized void transfer(FilterContext context) { in transfer() method in ProgramPort
|
| D | InputPort.java | 84 public abstract void transfer(FilterContext context); in transfer() method in InputPort
|
| D | StreamPort.java | 95 public synchronized void transfer(FilterContext context) { in transfer() method in StreamPort
|
| D | FieldPort.java | 62 public synchronized void transfer(FilterContext context) { in transfer() method in FieldPort
|
| D | Filter.java | 276 getInputPort(name).transfer(context); in transferInputPortFrame()
287 inputPort.transfer(context); in initProgramInputs()
628 inputPort.transfer(context); in transferInputFrames()
|
| /frameworks/base/docs/html/training/wearables/data-layer/ |
| D | index.jd | 43 …automatically takes care of the transfer for you, conserving Bluetooth bandwidth by caching large …
66 class to transfer large data items, such as music and movie files, from a handheld to a wearable
67 device. The Channel API for data transfer has the following benefits:
115 <dd>Assets are binary blobs of data that you typically use to transfer images or media.</dd>
|
| /frameworks/av/media/libstagefright/webm/ |
| D | WebmElement.cpp | 391 int32_t primaries, transfer, coeffs; in VideoTrackEntry() local
394 aspects, &primaries, &transfer, &coeffs, &fullRange); in VideoTrackEntry()
399 colorInfo.push_back(new WebmUnsigned(kMkvTransferCharacteristics, transfer)); in VideoTrackEntry()
|
| /frameworks/base/docs/html/guide/topics/connectivity/ |
| D | index.jd | 17 the wireless radio can affect your choices on when, what, and how to transfer data in order to
|
| /frameworks/av/media/libstagefright/ |
| D | Utils.cpp | 158 int32_t transfer; in isHdr() local
159 if (format->findInt32("color-transfer", &transfer)) { in isHdr()
160 return transfer == ColorUtils::kColorTransferST2084 in isHdr()
161 || transfer == ColorUtils::kColorTransferHLG; in isHdr()
1221 int32_t range = 0, standard = 0, transfer = 0; in convertMessageToMetaDataColorAspects() local
1224 (void)msg->findInt32("color-transfer", &transfer); in convertMessageToMetaDataColorAspects()
1229 range, standard, transfer, colorAspects) != OK) { in convertMessageToMetaDataColorAspects()
|