/frameworks/base/services/core/jni/ |
D | com_android_server_lights_LightsService.cpp | 67 Devices* devices; in init_native() local 69 devices = (Devices*)malloc(sizeof(Devices)); in init_native() 73 devices->lights[LIGHT_INDEX_BACKLIGHT] in init_native() 75 devices->lights[LIGHT_INDEX_KEYBOARD] in init_native() 77 devices->lights[LIGHT_INDEX_BUTTONS] in init_native() 79 devices->lights[LIGHT_INDEX_BATTERY] in init_native() 81 devices->lights[LIGHT_INDEX_NOTIFICATIONS] in init_native() 83 devices->lights[LIGHT_INDEX_ATTENTION] in init_native() 85 devices->lights[LIGHT_INDEX_BLUETOOTH] in init_native() 87 devices->lights[LIGHT_INDEX_WIFI] in init_native() [all …]
|
/frameworks/av/services/audiopolicy/engineconfigurable/src/ |
D | InputSource.cpp | 47 status_t Element<audio_source_t>::set(audio_devices_t devices) in set() argument 49 if (devices != AUDIO_DEVICE_NONE) { in set() 50 devices |= AUDIO_DEVICE_BIT_IN; in set() 52 if (!audio_is_input_device(devices)) { in set() 54 __FUNCTION__, devices, getName().c_str()); in set() 57 ALOGD("%s: 0x%X for input source %s", __FUNCTION__, devices, getName().c_str()); in set() 58 mApplicableDevices = devices; in set()
|
D | Strategy.cpp | 47 status_t Element<routing_strategy>::set<audio_devices_t>(audio_devices_t devices) in set() argument 49 if (!audio_is_output_devices(devices) || devices == AUDIO_DEVICE_NONE) { in set() 51 __FUNCTION__, devices, getName().c_str()); in set() 54 ALOGD("%s: 0x%X for strategy %s", __FUNCTION__, devices, getName().c_str()); in set() 55 mApplicableDevices = devices; in set()
|
/frameworks/av/services/audiopolicy/ |
D | audio_policy.conf | 91 devices { 110 devices speaker 119 devices AUDIO_DEVICE_IN_BUILTIN_MIC 133 devices AUDIO_DEVICE_OUT_REMOTE_SUBMIX 141 devices AUDIO_DEVICE_IN_REMOTE_SUBMIX
|
/frameworks/av/services/audiopolicy/common/managerdefinitions/src/ |
D | DeviceDescriptor.cpp | 79 void DeviceVector::add(const DeviceVector &devices) in add() argument 81 for (size_t i = 0; i < devices.size(); i++) { in add() 82 sp<DeviceDescriptor> device = devices.itemAt(i); in add() 123 audio_devices_t devices = AUDIO_DEVICE_NONE; in getDevicesFromHwModule() local 126 devices |= itemAt(i)->type(); in getDevicesFromHwModule() 129 return devices; in getDevicesFromHwModule() 164 DeviceVector devices; in getDevicesFromType() local 171 devices.add(itemAt(i)); in getDevicesFromType() 177 return devices; in getDevicesFromType() 183 DeviceVector devices; in getDevicesFromTypeAddr() local [all …]
|
D | ConfigParsingUtils.cpp | 101 status_t ConfigParsingUtils::loadHwModuleDevice(cnode *root, DeviceVector &devices) in loadHwModuleDevice() argument 145 devices.add(deviceDesc); in loadHwModuleDevice() 177 DeviceVector devices; in loadHwModuleProfile() local 178 loadDevicesFromTag(node->value, devices, module->getDeclaredDevices()); in loadHwModuleProfile() 179 profile->setSupportedDevices(devices); in loadHwModuleProfile() 228 DeviceVector devices; in loadHwModule() local 231 status_t tmpStatus = loadHwModuleDevice(node, devices); in loadHwModule() 237 module->setDeclaredDevices(devices); in loadHwModule() 288 void ConfigParsingUtils::loadDevicesFromTag(const char *tag, DeviceVector &devices, in loadDevicesFromTag() argument 304 devices.add(dev); in loadDevicesFromTag() [all …]
|
/frameworks/base/packages/SystemUI/src/com/android/systemui/qs/tiles/ |
D | CastTile.java | 122 final Set<CastDevice> devices = mController.getCastDevices(); in handleUpdateState() local 124 for (CastDevice device : devices) { in handleUpdateState() 139 mDetailAdapter.updateItems(devices); in handleUpdateState() 234 private void updateItems(Set<CastDevice> devices) { in updateItems() argument 237 if (devices != null && !devices.isEmpty()) { in updateItems() 239 for (CastDevice device : devices) { in updateItems() 253 for (CastDevice device : devices) { in updateItems() 256 items = new Item[devices.size()]; in updateItems() 260 if (!devices.contains(device)) continue; in updateItems()
|
/frameworks/av/services/audiopolicy/engineconfigurable/parameter-framework/examples/Settings/ |
D | device_for_strategy_phone.pfw | 91 # Fallback BT Sco devices in case of FORCE_BT_SCO 121 # Fallback BT Sco devices in case of FORCE_BT_SCO 151 # Fallback BT Sco devices in case of FORCE_BT_SCO 181 # Fallback BT Sco devices in case of FORCE_BT_SCO 208 # Fallback BT Sco devices in case of FORCE_BT_SCO 258 # Fallback BT Sco devices in case of FORCE_BT_SCO 296 # Fallback BT Sco devices in case of FORCE_BT_SCO 324 # Fallback BT Sco devices in case of FORCE_BT_SCO 352 # Fallback BT Sco devices in case of FORCE_BT_SCO 380 # Fallback BT Sco devices in case of FORCE_BT_SCO [all …]
|
/frameworks/base/docs/html/training/tv/start/ |
D | index.jd | 18 Android offers a rich user experience that's optimized for apps running on large screen devices, 26 existing apps to also run on TV devices. However, the user interaction model for TV is 27 substantially different from phone and tablet devices. In order to make your app successful on TV 28 devices, you must design new layouts that can be easily understood from 10 feet away, and provide 35 hardware features that are not typically available on TV devices. 52 app project to run on TV devices.</dd> 56 features, and manage controller devices.</dd>
|
/frameworks/base/docs/html/guide/webapps/ |
D | index.jd | 13 client-side application (developed using the Android SDK and installed on user devices in an APK) 15 browser—there's nothing to install on user devices).</p> 17 <p>If you chose to provide a web-based app for Android-powered devices, you can rest 30 <p>To start developing web pages for Android-powered devices, see the following documents:</p> 35 <dd>How to properly size your web app on Android-powered devices and support 37 application that you at least expect to be available on Android-powered devices (which you should 38 assume for anything you publish on the web), but especially if you're targeting mobile devices 49 Android-powered devices.</dd>
|
D | best-practices.jd | 31 <p>Developing web pages and web applications for mobile devices presents a different set of 35 devices.</p> 39 <li>Redirect mobile devices to a dedicated mobile version of your web site 44 devices. If necessary, you can also identify the specific operating system in the User Agent string 46 <p class="note"><strong>Note:</strong> Large screen Android-powered devices that should be served 54 <li>Use a valid markup DOCTYPE that's appropriate for mobile devices 57 ensures specific markup for your web site that works best on mobile devices. For instance, it does 58 not allow HTML frames or nested tables, which perform poorly on mobile devices. Along with the 83 <p>For more information about how to use viewport meta data for Android-powered devices, read <a 89 <p>Because mobile devices typically have a connection speed far slower than a desktop
|
/frameworks/base/docs/html/training/connect-devices-wirelessly/ |
D | index.jd | 35 enable communication with other devices on the same local network, and even 36 devices which are not on a network, but are physically nearby. The addition of 44 connecting to other devices from your application. Specifically, it 59 <dd>Learn how to fetch a list of nearby peer devices, create an access point 60 for legacy devices, and connect to other devices capable of Wi-Fi P2P 64 <dd>Learn how to discover services published by nearby devices without being
|
/frameworks/base/tools/preload2/src/com/android/preload/ |
D | Main.java | 184 IDevice devices[] = DeviceUtils.findDevices(DEFAULT_TIMEOUT_MILLIS); in initDevice() local 185 if (devices == null || devices.length == 0) { in initDevice() 191 DeviceWrapper deviceWrappers[] = new DeviceWrapper[devices.length]; in initDevice() 192 for (int i = 0; i < devices.length; i++) { in initDevice() 193 deviceWrappers[i] = new DeviceWrapper(devices[i]); in initDevice()
|
/frameworks/base/docs/html/training/wearables/data-layer/ |
D | index.jd | 7 <!-- Required platform, tools, add-ons, devices, knowledge, etc. --> 35 returns a successful result code. If the devices are not connected, an error is returned. A 37 devices may disconnect after receiving the result code. 69 <li>Transfer large data files between two or more connected devices, without 77 connected devices.</li> 90 devices. For instance, don't try to open low-level sockets to create a communication 95 user saves a note on a handheld, it automatically appears on both of the user's Wear devices. To 96 synchronize data between devices, Google’s servers host a cloud node in the network of devices. The 97 system synchronizes data to directly connected devices, the cloud node, and to wearable devices 102 handheld and wearable devices.</p>
|
/frameworks/av/services/audioflinger/ |
D | AudioHwDevice.cpp | 37 audio_devices_t devices, in openOutputStream() argument 53 status_t status = outputStream->open(handle, devices, config, address); in openOutputStream() 78 status = outputStream->open(handle, devices, &originalConfig, address); in openOutputStream()
|
/frameworks/base/docs/html/training/multiple-apks/ |
D | index.jd | 13 <!-- Required platform, tools, add-ons, devices, knowledge, etc. --> 39 the right devices, as well as the smart way to avoid pitfalls such as unnecessary redundancy across 41 devices on Google Play. By going through any of these lessons, you'll know how to develop 42 multiple APKs the smart way, make sure they're targeting the devices you want them to, 56 <dd>Learn how to target Android devices by screen size using multiple APKs. Also learn how to 61 <dd>Learn how to target Android devices based on their support for GL texture. Also learn 66 <dd>Learn how to target different Android devices based on more than one configuration
|
/frameworks/base/packages/MtpDocumentsProvider/src/com/android/mtp/ |
D | RootScanner.java | 136 final MtpDeviceRecord[] devices = mManager.getDevices(); in run() local 139 for (final MtpDeviceRecord device : devices) { in run() 156 for (final MtpDeviceRecord device : devices) { in run() 181 if (devices.length == 0) { in run()
|
/frameworks/base/core/java/android/bluetooth/ |
D | BluetoothManager.java | 176 List<BluetoothDevice> devices = new ArrayList<BluetoothDevice>(); in getDevicesMatchingConnectionStates() local 181 if (iGatt == null) return devices; in getDevicesMatchingConnectionStates() 182 devices = iGatt.getDevicesMatchingConnectionStates(states); in getDevicesMatchingConnectionStates() 187 return devices; in getDevicesMatchingConnectionStates()
|
/frameworks/base/docs/html/about/ |
D | android.jd | 9 <p>Android powers hundreds of millions of mobile devices in more than 190 12 Android devices for the first time and start looking for apps, games, 26 <blockquote>Every day more than a million new Android devices are activated worldwide.</blockquote> 51 <blockquote>Easily optimize a single binary for phones, tablets, and other devices.</blockquote> 56 devices—from phones to tablets and beyond.</p> 77 device or create virtual devices that emulate any hardware configuration.</p> 95 devices or focus on specific segments, devices, or ranges of hardware 110 <p>Preinstalled on billions of Android devices around the world,
|
D | index.jd | 9 <p>Android powers hundreds of millions of mobile devices in more than 190 12 Android devices for the first time and start looking for apps, games, 34 <blockquote>Every day more than 1 million new Android devices are activated worldwide.</blockquote> 60 <blockquote>Easily optimize a single binary for phones, tablets, and other devices.</blockquote> 65 devices—from phones to tablets and beyond.</p> 86 device or create virtual devices that emulate any hardware configuration.</p> 104 devices or focus on specific segments, devices, or ranges of hardware 119 <p>Preinstalled on hundreds of millions of Android devices around the world,
|
/frameworks/base/docs/html/guide/practices/ |
D | compatibility.jd | 33 <p>Android is designed to run on many different types of devices, from phones 35 the range of devices provides a huge potential audience for your app. In order for your app 36 to be successful on all these devices, it should tolerate some feature variability 46 experience on a variety of devices. 49 which types of devices can install your app from Google Play Store. This page explains how you can 50 control which devices have access to your apps, and how to prepare your apps to make sure they 52 to different devices, read <a href="{@docRoot}training/basics/supporting-devices/index.html" 72 only devices that are Android compatible include Google Play Store. So you can rest assured that 78 are not available on all devices. For example, some devices may not include a 80 of a compass sensor, then your app is compatible only with devices that [all …]
|
/frameworks/base/media/java/android/media/ |
D | AudioRecordingConfiguration.java | 130 final AudioDeviceInfo[] devices = in getAudioDevice() local 132 for (int j = 0; j < devices.length; j++) { in getAudioDevice() 133 if (devices[j].getId() == devId) { in getAudioDevice() 134 return devices[j]; in getAudioDevice()
|
/frameworks/base/docs/html/guide/topics/connectivity/ |
D | bluetooth.jd | 15 <li><a href="#QueryingPairedDevices">Querying paired devices</a></li> 16 <li><a href="#DiscoveringDevices">Discovering devices</a></li> 50 which allows a device to wirelessly exchange data with other Bluetooth devices. 53 connect to other Bluetooth devices, enabling point-to-point and multipoint 59 <li>Scan for other Bluetooth devices</li> 60 <li>Query the local Bluetooth adapter for paired Bluetooth devices</li> 62 <li>Connect to other devices through service discovery</li> 63 <li>Transfer data to and from other devices</li> 69 and communicating between Android devices. For Bluetooth devices with low power requirements, 77 Bluetooth, finding devices that are either paired or available in the local [all …]
|
/frameworks/base/docs/html/training/search/ |
D | backward-compat.jd | 32 devices, but want to target Android 3.0 or later versions. When you do this, your application 34 older devices:</p> 44 <p>To invoke the search dialog on older devices, call {@link 46 menu item from the options menu. Because Android 3.0 and higher devices show the 67 android.widget.SearchView} does not occur on older devices. In our example code, this happens in
|
/frameworks/base/docs/html/guide/topics/connectivity/usb/ |
D | index.jd | 20 readers; and much more. This gives Android-powered devices that do not have host capabilities the 22 Android-powered devices and must adhere to the <a href= 24 host mode, the Android-powered device acts as the host. Examples of devices include digital 25 cameras, keyboards, mice, and game controllers. USB devices that are designed for a wide range of 38 library to support a broader range of devices. Device manufacturers can choose whether or not to 42 dependant on the device's hardware, regardless of platform level. You can filter for devices that
|