HomeSort by relevance Sort by last modified time
    Searched full:drain (Results 76 - 100 of 294) sorted by null

1 2 34 5 6 7 8 91011>>

  /external/qemu/slirp-android/
socket.h 69 #define SS_FWDRAIN 0x040 /* We received a FIN, drain data and set SS_FCANTSENDMORE */
  /frameworks/base/docs/html/training/efficient-downloads/
index.jd 39 <dd>This lesson introduces the wireless radio state machine, explains how your app?s connectivity model interacts with it, and how you can minimize your data connection and use prefetching and bundling to minimize the battery drain associated with your data transfers.</dd>
efficient-network-access.jd 32 <p>Using the wireless radio to transfer data is potentially one of your app's most significant sources of battery drain. To minimize the battery drain associated with network activity, it's critical that you understand how your connectivity model will affect the underlying radio hardware.</p>
34 <p>This lesson introduces the wireless radio state machine and explains how your app's connectivity model interacts with it. It goes on to propose ways to minimize your data connections, use prefetching, and bundle your transfers in order to minimize the battery drain associated with your data transfers.</p>
46 <p>While the low and idle states drain significantly less battery, they also introduce significant latency to network requests. Returning to full power from the low state takes around 1.5 seconds, while moving from idle to full can take over 2 seconds.</p>
82 <p>However, used too aggressively, prefetching introduces the risk of increasing battery drain and bandwidth use&mdash;as well as download quota&mdash;by downloading data that isn't used. It's also important to ensure that prefetching doesn't delay application startup while the app waits for the prefetch to complete. In practical terms that might mean processing data progressively, or initiating consecutive transfers prioritized such that the data required for application startup is downloaded and processed first.</p>
  /cts/tests/tests/os/src/android/os/cts/
ParcelFileDescriptorProcessTest.java 157 // even though closed we should still drain pipe
171 // even though dead we should still drain pipe
  /external/chromium/net/http/
http_network_transaction.h 185 // Called when we don't need to drain the response body or have drained it.
255 // The size in bytes of the buffer we use to drain the response body that
  /external/chromium_org/net/http/
http_pipelined_connection_impl.h 138 // Attempts to drain the response body for |stream| so that the pipeline may
140 void Drain(HttpPipelinedStream* stream, HttpNetworkSession* session);
http_network_transaction.h 222 // Called when we don't need to drain the response body or have drained it.
300 // The size in bytes of the buffer we use to drain the response body that
http_response_body_drainer_unittest.cc 129 virtual void Drain(HttpNetworkSession*) OVERRIDE {}
http_stream_base.h 145 virtual void Drain(HttpNetworkSession* session) = 0;
  /external/clang/test/Analysis/
misc-ps-eager-assume.m 24 - (void)drain;
64 [pool drain];
  /frameworks/av/services/audioflinger/
Threads.h 342 MIXER_DRAIN_TRACK, // drain currently playing track
343 MIXER_DRAIN_ALL, // fully drain the hardware
597 // mDrainSequence contains current drain sequence on bits 31-1. The drain sequence is
598 // incremented each time a drain is requested or a flush() or standby() occurs.
599 // Bit 0 is set when the drain() command is called at the HAL and indicates a callback is
    [all...]
  /external/chromium_org/chromeos/disks/
disk_mount_manager_unittest.cc 256 // Cros disks will respond asynchronoulsy, so let's drain the message loop.
300 // Cros disks will respond asynchronoulsy, so let's drain the message loop.
363 // Cros disks will respond asynchronoulsy, so let's drain the message loop.
  /external/chromium_org/net/quic/congestion_control/
inter_arrival_sender.cc 371 // Did we drain the network buffers in our expected pace?
408 // Use our drain rate and our kMinBitrateReduction to go to our
459 // To drain all build up buffer within one RTT we need to reduce the
  /external/chromium/third_party/libevent/
buffer.c 129 /* We drain the input buffer on success */
241 /* Drain one more character if needed */
  /external/chromium_org/third_party/libevent/
buffer.c 129 /* We drain the input buffer on success */
241 /* Drain one more character if needed */
  /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.4.3/sysroot/usr/include/pulse/
context.h 202 /** Drain the context. If there is nothing to drain, the function returns NULL */
  /prebuilts/gcc/linux-x86/host/i686-linux-glibc2.7-4.6/sysroot/usr/include/pulse/
context.h 202 /** Drain the context. If there is nothing to drain, the function returns NULL */
  /prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.7-4.6/sysroot/usr/include/pulse/
context.h 202 /** Drain the context. If there is nothing to drain, the function returns NULL */
  /developers/samples/android/background/alarms/Scheduler/src/com/example/android/scheduler/
SampleAlarmReceiver.java 68 * to minimize the drain on the device battery.
  /external/chromium/chrome/browser/net/
connection_tester_unittest.cc 187 // Drain the tasks on the message loop.
  /external/chromium/chrome/browser/sync/glue/
ui_model_worker.cc 84 // Drain any final tasks manually until the SyncerThread tells us it has
  /external/chromium_org/chrome/browser/net/
connection_tester_unittest.cc 205 // Drain the tasks on the message loop.
  /external/chromium_org/net/quic/
quic_http_stream.h 62 virtual void Drain(HttpNetworkSession* session) OVERRIDE;
  /external/chromium_org/net/spdy/
spdy_http_stream.h 76 virtual void Drain(HttpNetworkSession* session) OVERRIDE;
  /external/chromium_org/net/url_request/
url_request_http_job_unittest.cc 251 virtual void Drain(HttpNetworkSession* session) OVERRIDE {}

Completed in 911 milliseconds

1 2 34 5 6 7 8 91011>>