HomeSort by relevance Sort by last modified time
    Searched full:mechanism (Results 1051 - 1075 of 2621) sorted by null

<<41424344454647484950>>

  /frameworks/base/core/java/android/os/
DropBoxManager.java 333 // TODO: It may be useful to have some sort of notification mechanism
  /frameworks/base/core/java/android/util/
AttributeSet.java 34 * <p>This interface provides an efficient mechanism for retrieving
  /frameworks/base/core/java/android/view/
InputFilter.java 55 * The input filter mechanism is very low-level. At a minimum, it needs to ensure that it
  /frameworks/base/core/java/android/widget/
RemoteViewsAdapter.java 144 * garbage collected, and would cause us to leak activities due to the caching mechanism for
625 // Note: This is currently the most naive mechanism for deciding what to prune when
629 // mechanism.
753 // of items that are loaded as a result of the caching mechanism
    [all...]
  /frameworks/base/docs/html/tools/
device.jd 117 debugging through this computer. This security mechanism protects user devices because it ensures
  /frameworks/base/docs/html/training/in-app-billing/
purchase-iab-products.jd 107 <p>You can use the In-app Billing Version 3 API to track the ownership of purchased items in Google Play. Once an item is purchased, it is considered to be "owned" and cannot be purchased again from Google Play while in that state. You must send a consumption request for the item before Google Play makes it available for purchase again. All managed in-app products are consumable. How you use the consumption mechanism in your app is up to you. Typically, you would implement consumption for products with temporary benefits that users may want to purchase multiple times (for example, in-game currency or replenishable game tokens). You would typically not want to implement consumption for products that are purchased once and provide a permanent effect (for example, a premium upgrade).</p>
  /frameworks/base/docs/html/training/sharing/
send.jd 140 apps have the correct permission to access your provider. The preferred mechanism for providing
  /frameworks/base/services/java/com/android/server/location/
LocationFudger.java 280 * is the primary obfuscation mechanism. It just needs to be large
  /frameworks/base/services/java/com/android/server/power/
DisplayPowerState.java 38 * This mechanism enables multiple properties of the display power state to be animated
  /frameworks/base/tools/layoutlib/bridge/src/android/graphics/
BidiRenderer.java 108 * much as possible. This also implements a fallback mechanism to render characters that cannot
  /frameworks/compile/libbcc/bcinfo/BitReader_2_7/
BitcodeReader.h 228 /// @brief Cheap mechanism to just extract module triple
  /frameworks/compile/libbcc/bcinfo/BitReader_3_0/
BitcodeReader.h 222 /// @brief Cheap mechanism to just extract module triple
  /frameworks/native/include/gui/
IGraphicBufferProducer.h 44 * The underlying mechanism is a BufferQueue, which implements
  /frameworks/support/v4/java/android/support/v4/app/
NavUtils.java 150 * by using {@link TaskStackBuilder} or another similar mechanism to perform up navigation.</p>
  /hardware/ti/omap4xxx/security/tf_sdk/include/
pkcs11.h 276 CK_MECHANISM_TYPE mechanism; member in struct:CK_MECHANISM
  /hardware/ti/wlan/mac80211/config/
TQS_D_1.7.ini 21 SRState = 00 # Length: 1; Unit: Options (0: Disabled, 1: Enabled); Format: Decimal; Source: TI; Comment: Smart Reflax (proprietary mechanism of TI that identify the silicon process specific params) state
22 SRF1 = 09 04 19 10 08 00 F7 EF E6 DE 00 00 00 00 0F 3F # Length: 16; Unit: SRF1 values; Format: Signed; Source: TI; Comment: The table holds the specific parameters for using the SmartReflex mechanism
23 SRF2 = 09 04 19 10 08 00 F7 EF E6 DE 00 00 00 00 00 00 # Length: 16; Unit: SRF2 values; Format: Signed; Source: TI; Comment: The table holds the specific parameters for using the SmartReflex mechanism
24 SRF3 = 09 04 19 10 08 00 F7 EF E6 DE 00 00 00 00 00 00 # Length: 16; Unit: SRF3 values; Format: Signed; Source: TI; Comment: The table holds the specific parameters for using the SmartReflex mechanism
  /hardware/ti/wlan/mac80211/ti-utils/ini_files/128x/
TQS_D_1.0.ini 21 SRState = 00 # Length: 1; Unit: Options (0: Disabled, 1: Enabled); Format: Decimal; Source: TI; Comment: Smart Reflax (proprietary mechanism of TI that identify the silicon process specific params) state
22 SRF1 = 09 04 19 10 08 00 F7 EF E6 DE 00 00 00 00 0F 3F # Length: 16; Unit: SRF1 values; Format: Signed; Source: TI; Comment: The table holds the specific parameters for using the SmartReflex mechanism
23 SRF2 = 09 04 19 10 08 00 F7 EF E6 DE 00 00 00 00 00 00 # Length: 16; Unit: SRF2 values; Format: Signed; Source: TI; Comment: The table holds the specific parameters for using the SmartReflex mechanism
24 SRF3 = 09 04 19 10 08 00 F7 EF E6 DE 00 00 00 00 00 00 # Length: 16; Unit: SRF3 values; Format: Signed; Source: TI; Comment: The table holds the specific parameters for using the SmartReflex mechanism
TQS_D_1.7.ini 21 SRState = 00 # Length: 1; Unit: Options (0: Disabled, 1: Enabled); Format: Decimal; Source: TI; Comment: Smart Reflax (proprietary mechanism of TI that identify the silicon process specific params) state
22 SRF1 = 09 04 19 10 08 00 F7 EF E6 DE 00 00 00 00 0F 3F # Length: 16; Unit: SRF1 values; Format: Signed; Source: TI; Comment: The table holds the specific parameters for using the SmartReflex mechanism
23 SRF2 = 09 04 19 10 08 00 F7 EF E6 DE 00 00 00 00 00 00 # Length: 16; Unit: SRF2 values; Format: Signed; Source: TI; Comment: The table holds the specific parameters for using the SmartReflex mechanism
24 SRF3 = 09 04 19 10 08 00 F7 EF E6 DE 00 00 00 00 00 00 # Length: 16; Unit: SRF3 values; Format: Signed; Source: TI; Comment: The table holds the specific parameters for using the SmartReflex mechanism
  /libcore/dalvik/src/main/java/dalvik/system/
DexFile.java 125 * mechanism. This function should not be called directly by an
  /libcore/luni/src/main/java/javax/xml/xpath/
XPathFactory.java 25 *<p>See {@link #newInstance(String uri)} for lookup mechanism.</p>
  /libcore/luni/src/main/java/libcore/reflect/
AnnotationFactory.java 171 * <br>Note, actual underlying implementation mechanism does not matter - it may
  /packages/apps/Email/src/com/android/email/mail/transport/
SmtpSender.java 147 LogUtils.d(Logging.LOG_TAG, "No valid authentication mechanism found.");
  /packages/providers/ContactsProvider/tests/src/com/android/providers/contacts/
GlobalSearchSupportTest.java 272 * uses the currently-supported mechanism of identifying the contact by the lookup key,
  /packages/providers/DownloadProvider/docs/
index.html 221 The first mechanism is expected to be fairly robust (the implementation is quite simple, based on projection maps, which are highly
223 higher risk of being compromised. Therefore, sensitive information stored in unrestricted columns (for which the first mechanism
247 The <code>URI</code> column is visible to the initiating application, which is a mild security risk. It should be hidden, but the OTA update mechanism relies on it to check duplicate downloads and to display the download that's currently ongoing in the settings app. If another string column was exposed to the initiating applications, the OTA update mechanism could use that one, and <code>URI</code> could then be hidden. For Cupcake, without changing the database schema, the <code>ENTITY</code> column could be re-used as it's currently unused.
274 Getting rid of <code>OTHER_UID</code> would be beneficial for the download manager, but the existing functionality has to be worked around. At this point, the idea that I consider the most likely would be to have checkin and market implement =ContentProvider= wrappers around their downloads, and expose those content providers to whichever app they want, with whichever security mechanism they wish to have.
320 <tr><td > 1003 </td><td > 1.0 <b>YES</b> </td><td > &nbsp; </td><td > Security </td><td > The download manager provides a mechanism that prevents arbitrary applications from accessing meta-data about current and past downloads. </td><td > In 1.0, known holes between apps </td></tr>
332 <tr><td > 2003 </td><td > 1.0 <b>YES</b> </td><td > &nbsp; </td><td > Flaky Downloads </td><td > The download manager has mechanism that prevent excessive retries of downloads that consistently fail or get interrupted. </td><td > &nbsp; </td></tr>
    [all...]
  /pdk/apps/CameraITS/pymodules/its/
device.py 36 forwarded over adb is the transport mechanism used.

Completed in 1103 milliseconds

<<41424344454647484950>>