Waiting for boot to complete...

[Tierney0115]

Some of my devices often fail to boot and the STF log shows waiting for boot to complete. This always happened after 1-2 days after reboot these devices and only reboot those devices could solve the problem.

The functional devices show 1 immediately after 'adb -s XXXX shell getprop sys.boot_completed' command, and the problem devices show 1 after more than 2 mins.

Is there some problems with my android phones themselves or the bug of the ADB?

Thanks

[chenpig1123]

I have the same problem, I think the adbd is down, the status of some devices are online just for few minutes, then you can see it has no answers after you input "adb shell..." in your terminal, so stf log out "waiting for boot...".

[Tierney0115]

All the problem devices are Android 6.0 system. Are you using Android 6.0 for a long time without this kind of problem? Thanks

[chenpig1123]

I use the Android 6.0 rom on a nexus5, and I never have this problem, but on HuaWei Mate8(Android 6.0) this problem happens, maybe android 6.0 is not the reason.

[Tierney0115]

@chenpig1123 Are you connecting the devices with Linux PC? Are you using the PC with USB hub and how many devices are you using at same time? Thanks.

[chenpig1123]

@Tierney0115 Ubuntu14.04 + USB hub, and only 8 devices, all devices(2.x, 4.x, 5.0, 6.0) worked except the Mate8.

[Tierney0115]

@chenpig1123 Thanks. Are other devices also Huawei or not?

[rseek]

same problem, stf-provider service is deployed on ubuntu 14.04, only one device (Nexus 4, Android 5.1.1) is connected and some x86 emulators

[chenpig1123]

Another way this problem can happen, execute the command: adb shell getprop | grep completed

and maybe you can see two props: dev.bootcomplete: 1 sys.boot_completed: 1

Now you perharps get to know the reason. If not, open the waitbootcomplete.js in the adbkit of node_modules, and if your devices don't have the sys.boot_completed prop, you always get the reply "Waiting for boot to completed".

[Nisim761]

Another way this problem can happen, execute the command: adb shell getprop | grep completed

and maybe you can see two props: dev.bootcomplete: 1 sys.boot_completed: 1

Now you perharps get to know the reason. If not, open the waitbootcomplete.js in the adbkit of node_modules, and if your devices don't have the sys.boot_completed prop, you always get the reply "Waiting for boot to completed".

I am using both of the options you mentioned. Both props return 1 about 5 seconds before the gui finished launching, which means that the emulator is not yet ready to be manipulated. For example, i am looking for an app i installed during previous execution, and the results returned is false. But waiting an extra 5 seconds, until the gui finishes launching, will cause the return value to be true as it should be.

[testifyqa]

Did you ever solve this? Struggling with this issue currently and at my wits end a bit