Lines Matching defs:state
88 * Internal vold volume state constants
174 * Mounted OBB tracking information. Used to track the current state of all
446 String state = getVolumeState(path);
448 if (state.equals(Environment.MEDIA_UNMOUNTED)) {
453 } else if (state.equals(Environment.MEDIA_SHARED)) {
455 * Bootstrap UMS enabled state since vold indicates
509 private void updatePublicVolumeState(String path, String state) {
515 if (mLegacyState.equals(state)) {
516 Slog.w(TAG, String.format("Duplicate state transition (%s -> %s)", mLegacyState, state));
520 if (Environment.MEDIA_UNMOUNTED.equals(state)) {
531 } else if (Environment.MEDIA_MOUNTED.equals(state)) {
537 mLegacyState = state;
543 bl.mListener.onStorageStateChanged(path, oldState, state);
566 * Determine media state and UMS detection status
569 String state = Environment.MEDIA_REMOVED;
576 // FMT: <label> <mountpoint> <state>
584 state = Environment.MEDIA_REMOVED;
586 state = Environment.MEDIA_UNMOUNTED;
588 state = Environment.MEDIA_MOUNTED;
591 state = Environment.MEDIA_SHARED;
594 throw new Exception(String.format("Unexpected state %d", st));
597 if (state != null) {
598 if (DEBUG_EVENTS) Slog.i(TAG, "Updating valid state " + state);
599 updatePublicVolumeState(path, state);
602 Slog.e(TAG, "Error processing initial volume state", e);
641 * One of the volumes we're managing has changed state.
642 * Format: "NNN Volume <label> <path> state changed
690 * This event gets trumped if we're already in BAD_REMOVAL state
751 if (DEBUG_EVENTS) Slog.i(TAG, "updating volume state for media bad removal nofs and unmountable");
757 if (DEBUG_EVENTS) Slog.i(TAG, "updating volume state checking");
761 if (DEBUG_EVENTS) Slog.i(TAG, "updating volume state mounted");
769 if (DEBUG_EVENTS) Slog.i(TAG, "Updating volume state media mounted");
845 if (DEBUG_EVENTS) Slog.i(TAG, " updating volume state :: media nofs");
853 if (DEBUG_EVENTS) Slog.i(TAG, "updating volume state media corrupt");
881 * to make sure we dont end up in an instable state and kill some core
897 // Redundant probably. But no harm in updating state again.
1111 String state = getVolumeState(path);
1113 if (state.equals(Environment.MEDIA_SHARED)) {
1122 } else if (state.equals(Environment.MEDIA_CHECKING)) {
1129 while (state.equals(Environment.MEDIA_CHECKING) && (retries-- >=0)) {
1136 state = Environment.getExternalStorageState();
1143 if (state.equals(Environment.MEDIA_MOUNTED)) {
1201 * The mountVolume() call will have set the storage state and sent the necessary
1214 * @return state of the volume at the specified mount point
1466 * Because a mounted container has active internal state which cannot be
1622 * The binder died before we could link it, so clean up our state
1752 Slog.i(TAG, "Flushing all OBB state for path " + path);
1774 Slog.i(TAG, "Removing state for " + obbState.filename);