Searched refs:devices (Results 1 – 11 of 11) sorted by relevance
13 seen on Android devices, it is possible to use bionic on the host too.17 If your code is specific to Android devices, use `__ANDROID__`. This isn't
100 expect 64-bit-only devices within the next few years.105 This doesn't generally affect Android devices, because on devices
97 out the cpu very quickly on Pixel devices, and don't affect the results.
347 // if available, and fall back to no-ops or regular close on pre-Q devices.
368 [example](https://source.android.com/devices/tech/debug/native-crash#fortify).
125 If there are multiple devices connected to the system, use `-s <SERIAL>`
178 To lock the CPU frequency, use the sysfs interface at `/sys/devices/system/cpu/cpu*/cpufreq/`.184 Some devices have a `perf-setup.sh` script that locks CPU and GPU frequencies. Some TradeFed
52 If you need to support Android devices running OS169 Compatibility Test Suite (CTS) that all Android devices must pass. They171 them more likely to fail on specific devices, or on future releases ---449 ## Use of IFUNC in libc (True for all API levels on devices running Q)455 devices, and is similar to what other OSes already did. Because the zygote
345 __u64 devices; member
230 struct vfio_pci_dependent_device devices[]; member
118 Android devices). The format of this dumped data is the same format as130 SIGRTMAX - 19 (which is 45 on Android devices). When this220 Android devices). The best way to see the exact signal being used is to345 to a file when the signal SIGRTMAX - 18 (which is 46 on Android devices)714 devices.