Hello everyone,
I am working on an android-based device odroid, and it has no
implementation of reset factory settings.
here's the code on my android:
package com.android.settings;
import com.android.internal.widget.LockPatternUtils;
import android.app.Activity;
import android.app.AlertDialog;
import android.content.Context;
import android.content.Intent;
import android.os.Bundle;
import android.os.ServiceManager;
import android.os.SystemProperties;
import android.text.TextUtils;
import android.util.Log;
import android.view.LayoutInflater;
import android.view.View;
import android.widget.Button;
/**
* Confirm and execute a reset of the device to a clean "just out of
the box"
* state. Multiple confirmations are required: first, a general "are
you sure
* you want to do this?" prompt, followed by a keyguard pattern trace
if the user
* has defined one, followed by a final strongly-worded "THIS WILL
ERASE EVERYTHING
* ON THE PHONE" prompt. If at any time the phone is allowed to go to
sleep, is
* locked, et cetera, then the confirmation sequence is abandoned.
*/
public class MasterClear extends Activity {
private static final int KEYGUARD_REQUEST = 55;
private LayoutInflater mInflater;
private LockPatternUtils mLockUtils;
private View mInitialView;
private Button mInitiateButton;
private View mFinalView;
private Button mFinalButton;
/**
* The user has gone through the multiple confirmation, so now we
go ahead
* and invoke the Checkin Service to reset the device to its
factory-default
* state (rebooting in the process).
*/
private Button.OnClickListener mFinalClickListener = new
Button.OnClickListener() {
public void onClick(View v) {
if (Utils.isMonkeyRunning()) {
return;
}
sendBroadcast(new
Intent("android.intent.action.MASTER_CLEAR"));
// Intent handling is asynchronous -- assume it will
happen soon.
}
};
/**
* Keyguard validation is run using the standard {...@link
ConfirmLockPattern}
* component as a subactivity
* @param request the request code to be returned once
confirmation finishes
* @return true if confirmation launched
*/
private boolean runKeyguardConfirmation(int request) {
return new ChooseLockSettingsHelper(this)
.launchConfirmationActivity(request,
getText(R.string.master_clear_gesture_prompt),
getText(R.string.master_clear_gesture_explanation));
}
@Override
protected void onActivityResult(int requestCode, int resultCode,
Intent data) {
super.onActivityResult(requestCode, resultCode, data);
if (requestCode != KEYGUARD_REQUEST) {
return;
}
// If the user entered a valid keyguard trace, present the
final
// confirmation prompt; otherwise, go back to the initial
state.
if (resultCode == Activity.RESULT_OK) {
establishFinalConfirmationState();
} else if (resultCode == Activity.RESULT_CANCELED) {
finish();
} else {
establishInitialState();
}
}
/**
* If the user clicks to begin the reset sequence, we next require
a
* keyguard confirmation if the user has currently enabled one.
If there
* is no keyguard available, we simply go to the final
confirmation prompt.
*/
private Button.OnClickListener mInitiateListener = new
Button.OnClickListener() {
public void onClick(View v) {
if (!runKeyguardConfirmation(KEYGUARD_REQUEST)) {
establishFinalConfirmationState();
}
}
};
/**
* Configure the UI for the final confirmation interaction
*/
private void establishFinalConfirmationState() {
if (mFinalView == null) {
mFinalView =
mInflater.inflate(R.layout.master_clear_final, null);
mFinalButton =
(Button)
mFinalView.findViewById(R.id.execute_master_clear);
mFinalButton.setOnClickListener(mFinalClickListener);
}
setContentView(mFinalView);
}
/**
* In its initial state, the activity presents a button for the
user to
* click in order to initiate a confirmation sequence. This
method is
* called from various other points in the code to reset the
activity to
* this base state.
*
* <p>Reinflating views from resources is expensive and prevents
us from
* caching widget pointers, so we use a single-inflate pattern:
we lazy-
* inflate each view, caching all of the widget pointers we'll
need at the
* time, then simply reuse the inflated views directly whenever we
need
* to change contents.
*/
private void establishInitialState() {
if (mInitialView == null) {
mInitialView =
mInflater.inflate(R.layout.master_clear_primary, null);
mInitiateButton =
(Button)
mInitialView.findViewById(R.id.initiate_master_clear);
mInitiateButton.setOnClickListener(mInitiateListener);
}
setContentView(mInitialView);
}
@Override
protected void onCreate(Bundle savedState) {
super.onCreate(savedState);
mInitialView = null;
mFinalView = null;
mInflater = LayoutInflater.from(this);
mLockUtils = new LockPatternUtils(this);
establishInitialState();
}
/** Abandon all progress through the confirmation sequence by
returning
* to the initial view any time the activity is interrupted (e.g.
by
* idle timeout).
*/
@Override
public void onPause() {
super.onPause();
establishInitialState();
}
}
I am wondering if manually deleting the application inside /data/app/
and deleting it in /data/data/ will somehow leave no trace of it.
odroid has no /proc/mtd which I could probably use to restore the
original images so one of my choices is to restore it by deleting the
settings.. though I feel like it can have an undesirable effect.
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-kernel
