/external/e2fsprogs/tests/f_unsorted_EAs/ |
expect.1 | 5 Pass 3: Checking directory connectivity
|
expect.2 | 3 Pass 3: Checking directory connectivity
|
/external/e2fsprogs/tests/f_unused_itable/ |
expect.2 | 3 Pass 3: Checking directory connectivity
|
/external/e2fsprogs/tests/f_valid_ea_in_inode/ |
expect.1 | 3 Pass 3: Checking directory connectivity
|
/external/e2fsprogs/tests/f_zero_group/ |
expect.2 | 3 Pass 3: Checking directory connectivity
|
/external/e2fsprogs/tests/f_zero_inode_size/ |
expect.2 | 3 Pass 3: Checking directory connectivity
|
expect.1 | 4 Pass 3: Checking directory connectivity
|
/external/e2fsprogs/tests/f_zero_super/ |
expect.2 | 3 Pass 3: Checking directory connectivity
|
/frameworks/ex/common/java/com/android/common/ |
NetworkConnectivityListener.java | 33 * A wrapper for a broadcast receiver that provides network connectivity 35 * @deprecated Code tempted to use this class should simply listen for connectivity intents 50 /** Network connectivity information */ 54 * In case of a Disconnect, the connectivity manager may have 55 * already established, or may be attempting to establish, connectivity 110 /** This state is returned if there is connectivity to any network **/ 113 * This state is returned if there is no connectivity to any network. This is set 116 * <li>When connectivity is lost to one network, and there is no other available 118 * <li>When connectivity is lost to one network, and the attempt to switch to 133 * This method starts listening for network connectivity state changes [all...] |
/frameworks/base/docs/html/training/monitoring-device-state/ |
manifest-receivers.jd | 7 previous.title=Determining and Monitoring the Connectivity Status 8 previous.link=connectivity-monitoring.html 57 <p>Using this technique, if you determine that connectivity has been lost, you can disable all of 58 your receivers except the connectivity-change receiver. Conversely, once you are connected you can 59 stop listening for connectivity changes and simply check to see if you're online immediately before 63 Simply enable a broadcast receiver that listens for connectivity changes and initiates the
|
connectivity-monitoring.jd | 1 page.title=Determining and Monitoring the Connectivity Status 21 <li><a href="#MonitorChanges">Monitor for Changes in Connectivity</a></li> 46 to query the active network and determine if it has Internet connectivity.</p> 60 <p>Device connectivity can be provided by mobile data, WiMAX, Wi-Fi, and ethernet connections. By 70 <p>Having disabled your updates, it's important that you listen for changes in connectivity in order 74 <h2 id="MonitorChanges">Monitor for Changes in Connectivity</h2> 78 "android.net.conn.CONNECTIVITY_CHANGE"}) action whenever the connectivity details have changed. You 84 <p>Changes to a device's connectivity can be very frequent—this broadcast is triggered 87 It's generally sufficient to simply check for Internet connectivity before beginning an update and, 88 should there be none, suspend further updates until connectivity is restored.</p [all...] |
index.jd | 30 <p>By taking steps such as disabling background service updates when you lose connectivity, or 51 <dt><b><a href="connectivity-monitoring.html">Determining and Monitoring the Connectivity 53 <dd>Without Internet connectivity you can't update your app from an online source. Learn how to 54 check the connectivity status to alter your background update rate. You'll also learn to check for 55 Wi-Fi or mobile connectivity before beginning high-bandwidth operations.</dd>
|
/packages/apps/Email/src/com/android/email/ |
EmailConnectivityManager.java | 36 * particular, this class provides callbacks for connectivity lost, connectivity restored, and 37 * background setting changed, as well as providing a method that waits for connectivity 56 // The monitor lock we use while waiting for connectivity 66 // The thread waiting for connectivity 68 // Whether or not we're registered with the system connectivity manager 94 * Called when network connectivity has been restored; this method should be overridden by 102 * Called when network connectivity has been lost; this method should be overridden by 141 * Request current connectivity status 142 * @return whether there is connectivity at this tim [all...] |
/external/e2fsprogs/tests/f_bad_local_jnl/ |
expect.1 | 8 Pass 3: Checking directory connectivity
|
/external/e2fsprogs/tests/f_baddir2/ |
expect.1 | 6 Pass 3: Checking directory connectivity
|
/external/e2fsprogs/tests/f_dir_bad_mode/ |
expect.1 | 6 Pass 3: Checking directory connectivity
|
/external/e2fsprogs/tests/f_dirlink/ |
expect.1 | 8 Pass 3: Checking directory connectivity
|
/external/e2fsprogs/tests/f_fast_symlink_extents/ |
expect.1 | 5 Pass 3: Checking directory connectivity
|
/external/e2fsprogs/tests/f_file_acl_high/ |
expect.1 | 6 Pass 3: Checking directory connectivity
|
/external/e2fsprogs/tests/f_hurd/ |
expect.1 | 6 Pass 3: Checking directory connectivity
|
/external/e2fsprogs/tests/f_okgroup/ |
expect.1 | 5 Pass 3: Checking directory connectivity
|
/frameworks/base/docs/html/training/ |
building-connectivity.jd | 1 page.title=Building Apps with Connectivity & the Cloud
|
/development/tools/emulator/test-apps/ConnectivityTest/ |
AndroidManifest.xml | 17 package="com.android.emulator.connectivity.test" 23 <instrumentation android:targetPackage="com.android.emulator.connectivity.test" android:name="android.test.InstrumentationTestRunner" /> 24 <application android:label="Connectivity Test">
|
/external/chromium_org/chrome/browser/resources/feedback/js/ |
event_handler.js | 25 'mlocfejafidcakdddnndjdngfmncfbeg', // Connectivity Diagnostics 26 'ganomidahfnpdchomfgdoppjmmedlhia', // Connectivity Diagnostics 27 'eemlkeanncmjljgehlbplemhmdmalhdc', // Connectivity Diagnostics 28 'kodldpbjkkmmnilagfdheibampofhaom', // Connectivity Diagnostics
|
/external/e2fsprogs/tests/f_big_sparse/ |
expect.1 | 10 Pass 3: Checking directory connectivity
|