Searched refs:behavior (Results 1 – 13 of 13) sorted by relevance
42 * behavior in the hardware binder (ref b/36122635).63 * resources may not be released right away due to asynchronos behavior in the hardware binder.
67 * might rely in the old (wrong) behavior.
78 * The expected behavior here is for GNSS HAL to set all the flags that applies.
139 * writing, the behavior is undefined, except that it must not cause
94 * @param mips AllocationMipmapControl specifies desired mipmap behavior for109 * @param mips AllocationMipmapControl specifies desired mipmap behavior for125 * @param mips AllocationMipmapControl specifies desired mipmap behavior553 * freed), this may result in undefined behavior
427 * pressed, turning the screen on. This behavior (turning on the screen when429 * settings. Changes in settings do not impact the behavior of the sensor:451 * device remains locked in a non-interactive state (dozing). This behavior454 * Changes in settings do not impact the behavior of the sensor: only
244 * it is not called, the default camera HAL behavior is to store real YUV
728 * RSSI values controlling clustering behavior per spec. RSSI values are specified without a sign,1024 * The match behavior is specified in details in the NAN spec.1034 * The match behavior is specified in details in the NAN spec.
214 * allow for the asynchronous behavior. If it is not enabled queue/dequeue
1495 * Set carrier restrictions. Expected modem behavior:
2098 * Expected modem behavior:
993 uint32 behavior; member
726 * is global behavior as GAIN or GAIN_TRANSIENT expects all sounds played