Returning to wizard, enable migration.
Bring primary storage migration back into the adoption flow, and provide a path for long-lived notifications to re-launch into the Settings app. Also provide option to initiate migration if skipped during wizard. For now, estmiate migration size and time based on a Class 10 card. Follow other callback refactoring. Bug: 19993667 Change-Id: Ia0c28eb114bc6c8066c17b3142ed74f962140c91
This commit is contained in:
@@ -49,7 +49,7 @@ public class StorageWizardMoveProgress extends StorageWizardBase {
|
||||
|
||||
// Register for updates and push through current status
|
||||
getPackageManager().registerMoveCallback(mCallback, new Handler());
|
||||
mCallback.onStatusChanged(mMoveId, null, getPackageManager().getMoveStatus(mMoveId), -1);
|
||||
mCallback.onStatusChanged(mMoveId, getPackageManager().getMoveStatus(mMoveId), -1);
|
||||
}
|
||||
|
||||
@Override
|
||||
@@ -60,7 +60,7 @@ public class StorageWizardMoveProgress extends StorageWizardBase {
|
||||
|
||||
private final MoveCallback mCallback = new MoveCallback() {
|
||||
@Override
|
||||
public void onStatusChanged(int moveId, String moveTitle, int status, long estMillis) {
|
||||
public void onStatusChanged(int moveId, int status, long estMillis) {
|
||||
if (mMoveId != moveId) return;
|
||||
|
||||
if (PackageManager.isMoveStatusFinished(status)) {
|
||||
|
Reference in New Issue
Block a user