On 06/02/2016 11:44 AM, Amit Pundir wrote:
On 2 June 2016 at 15:10, Jorge Ramirez jorge.ramirez-ortiz@linaro.org wrote:
On 06/02/2016 11:20 AM, Amit Pundir wrote:
On 2 June 2016 at 12:41, Jorge Ramirez jorge.ramirez-ortiz@linaro.org wrote:
the LISA pm [1] tools also check for a property to determine if the Android system booted properly; to do that, it calls devlib [2] boot_completed = boolean(self.getprop('sys.boot_completed'))
We fail this test on the HiKey AOSP. Anyone knows if there is any reason for this is not being set? or should devlib just remove this check?
I have a fairly old (May 14) AOSP build but Hikey does set that property. I rely on that property too when I'm too lazy to switch on the display :)
This is what I see:
hikey:/ # getprop | grep boot [dev.bootcomplete]: [1] [init.svc.bootanim]: [stopped] [ro.boot.console]: [ttyFIQ0] [ro.boot.hardware]: [hikey] [ro.boot.selinux]: [permissive] [ro.bootimage.build.date]: [Sat May 14 15:28:06 IST 2016] [ro.bootimage.build.date.utc]: [1463219886] [ro.bootimage.build.fingerprint]: [generic/hikey/hikey:6.0.1/MASTER/pundir05141528:userdebug/test-keys] [ro.bootloader]: [unknown] [ro.bootmode]: [unknown] [ro.runtime.firstboot]: [39332] [service.bootanim.exit]: [1] [sys.boot_completed]: [1]
Regards, Amit Pundir
thanks Amit. I see the following on my end
hikey:/ $ getprop | grep boot [service.bootanim.exit]: [0] hikey:/ $ getprop | grep boot [init.svc.bootanim]: [running]
--> Boot Animation is still running. Are you sure you have booted to UI? I doiubt that. Can you please check or share your logcat for failures.
ah ok I see errors... attached.