Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 191713a5 authored by Guang Zhu's avatar Guang Zhu
Browse files

Move where prop dev.bootcomplete is set 

Currently test harnesses depends on this flag to determine when
the system is fully booted, and start dismissing keyguard, launch
tests etc. However, the flag is usually set when the boot animation
is still running, and typically about 5 seconds before keyguard is
up etc. Moving to to when BOOT_COMPLETE broadcast is sent makes it
work more reliable.

We also discussed about using sys.boot_completed instead,
unfortunately this flag is not in all platform and we still have
backwards compatibility to maintain in order to drive unbundled
tests.

Change-Id: I99b084cd70d8e4bcfe490ddeca868136d32712e2
parent dc893578

policy/src/com/android/internal/policy/impl/PhoneWindowManager.java

+0 −1
Original line number Diff line number Diff line
@@ -3456,7 +3456,6 @@ public class PhoneWindowManager implements WindowManagerPolicy { 
    public void systemReady() {

        // tell the keyguard

        mKeyguardMediator.onSystemReady();

        android.os.SystemProperties.set("dev.bootcomplete", "1"); 

        synchronized (mLock) {

            updateOrientationListenerLp();

            mSystemReady = true;

services/java/com/android/server/am/ActivityManagerService.java

+1 −0
Original line number Diff line number Diff line
@@ -4045,6 +4045,7 @@ public final class ActivityManagerService extends ActivityManagerNative 
                mHandler.sendMessageDelayed(nmsg, POWER_CHECK_DELAY);

                // Tell anyone interested that we are done booting!

                SystemProperties.set("sys.boot_completed", "1");

                SystemProperties.set("dev.bootcomplete", "1");

                broadcastIntentLocked(null, null,

                        new Intent(Intent.ACTION_BOOT_COMPLETED, null),

                        null, null, 0, null, null,