HomeSort by relevance Sort by last modified time
    Searched full:manufacturers (Results 1 - 25 of 399) sorted by null

1 2 3 4 5 6 7 8 91011>>

  /sdk/eclipse/plugins/com.android.ide.eclipse.adt/src/com/android/ide/eclipse/adt/internal/editors/layout/configuration/
DeviceMenuListener.java 109 Map<String, List<Device>> manufacturers = new TreeMap<String, List<Device>>(); local
117 if (manufacturers.containsKey(device.getManufacturer())) {
118 devices = manufacturers.get(device.getManufacturer());
121 manufacturers.put(device.getManufacturer(), devices);
126 for (List<Device> devices : manufacturers.values()) {
128 if (manufacturers.size() > 1) {
146 for (List<Device> devices : manufacturers.values()) {
  /docs/source.android.com/src/compatibility/
overview.jd 21 manufacturers to develop compatible Android devices.</p>
24 Android community, including users, developers, and device manufacturers.</p>
27 for their apps with many devices in users' hands; device manufacturers rely
53 <p><em>Enable device manufacturers to differentiate while being
57 manufacturers the flexibility to create unique devices that are nonetheless
63 device manufacturers. The testing tool (CTS) is free, open source, and
  /docs/source.android.com/src/devices/
drm.jd 53 content across a variety of DRM schemes. For device manufacturers, content owners, and Internet digital media providers
144 <li>Device manufacturers must provide a secure bootloader. The chain of trust from the bootloader must extend through any software or firmware components involved in the security implementation, such as the ARM TrustZone protected application and any components involved in the enforcement of the secure video path. </li>
147 <li>Device manufacturers must provide an implementation of the Widevine Level 1 OEMCrypto API that performs all key processing and decryption in a trusted environment.</li>
157 <li>Device manufacturers must provide a secure bootloader. The chain of trust from the bootloader must extend through any software or firmware components involved in the security implementation, such as the TrustZone protected application. </li>
160 <li>Device manufacturers must provide an implementation of the Widevine Level 2 OEMCrypto API that performs all key processing and decryption in a trusted environment.</li>
161 <li>Device manufacturers must provide a bootloader that loads signed system images only. For devices that allow users to load a custom operating system or gain root privileges on the device by unlocking the bootloader, device manufacturers must support the following:
163 <li>Device manufacturers must provide a bootloader that allows a Widevine key-box to be written only when the bootloader is in a locked state.</li>
174 <p>Device manufacturers must provide a bootloader that loads signed system images only. For devices that allow users to load a custom operating system or gain root privileges on the device by unlocking the bootloader, device manufacturers must support the following:</p
    [all...]
  /frameworks/base/docs/html/tools/adk/
index.jd 5 <p>The Accessory Development Kit (ADK) is a reference implementation for hardware manufacturers and
  /docs/source.android.com/src/devices/tech/security/
se-linux.jd 35 manufacturers to gather information about errors so they may refine their
106 <p>Manufacturers should not remove existing security settings. Otherwise, they
156 <p>As device manufacturers begin to customize SELinux, they should first audit
206 for steps. We recommend device manufacturers start with the default Android
269 their SELinux implementations thoroughly. As manufacturers implement SELinux,
282 and viewable locally on the device. Manufacturers should examine the SELinux output
286 <p>With this output, manufacturers can readily identify when system users or
287 components are in violation of SELinux policy. Manufacturers can then repair
309 resolve them. </p> <h2 id="help">Help</h2> Device manufacturers are strongly
  /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/linux/
if_frad.h 5 * handler. This allows other FRAD manufacturers to use the DLCI
  /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/sysroot/usr/include/linux/
if_frad.h 5 * handler. This allows other FRAD manufacturers to use the DLCI
  /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.7-4.6/sysroot/usr/include/linux/
if_frad.h 5 * handler. This allows other FRAD manufacturers to use the DLCI
  /docs/source.android.com/src/
index.jd 56 Compatibility program defines the technical details of the Android platform and provides tools for device manufacturers to
  /frameworks/base/docs/html/about/versions/
android-2.0-highlights.jd 88 synchronization, including Exchange accounts. (Handset manufacturers can
103 Handset manufacturers can choose whether or not to include Exchange support
  /docs/source.android.com/src/source/
faqs.jd 85 This current stable branch is the one that manufacturers port to their
98 device manufacturers want to ship the latest software they can. Developers,
227 Device manufacturers should contact <a
231 <p>Google Play is only licensed to handset manufacturers shipping devices.
242 code is open, anyone can use it to build any kind of device. However, if manufacturers
279 <h3 id="how-are-device-manufacturers-compatibility-claims-validated">How are device manufacturers' compatibility claims validated?</h3>
290 <p>The Compatibility Test Suite is a tool used by device manufacturers to help
303 viewed by anyone. CTS reports can be shared as widely as manufacturers
441 those fixes to the manufacturers of the products through the open source project.</p
    [all...]
  /external/aac/
NOTICE 19 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
  /external/aac/libAACdec/src/
aacdec_hcr_bit.h 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
debug.h 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
ldfiltbank.h 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
overlapadd.h 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
rvlcbit.h 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
rvlcconceal.h 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
  /external/aac/libAACenc/src/
aacenc_hcr.cpp 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
aacenc_hcr.h 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
aacenc_pns.h 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
bandwidth.h 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
chaosmeasure.h 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
ms_stereo.h 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license
noisedet.h 21 the ISO/IEC MPEG audio standards. Please note that most manufacturers of Android devices already license

Completed in 725 milliseconds

1 2 3 4 5 6 7 8 91011>>