Yes, but I fixed it by modifying android framework. There is another way: to add "android:directBootAware="true" in app's AndroidManifest.xml
在 2016年12月6日星期二 UTC+8下午11:55:27，Anatoliy Shuba写道： > > Hi, > > I have faced same issue. > My device doesn't need any lock or encryption but FallbackHome still > starts. > Did you solve that issue for you? > Thanks > > понедельник, 22 августа 2016 г., 7:22:12 UTC-4 пользователь kai zhao > написал: >> >> I try to run AndroidN on my device. The device *doesn't need any lock or >> encryption.* >> >> Issue: >> I find that ActivityManagerService starts Settings.FallbackHome before >> real Launcher. >> This process takes more than 1000ms, so I wanna remove FallbackHome >> process for quick-startup. >> >> Modify: >> original: ams.systemReady -> startHomeActivityLocked -> resolveIntent -> >> FallbackHome -> User unlocked and real home found -> real Launcher >> goal: ams.systemReady -> startHomeActivityLocked -> resolveIntent -> real >> Launcher >> >> Status: >> If I remove FallbackHome and modify PackageUserState, the resolveIntent >> and startHome will be failed. >> Anyone knows about this activity in AndroidN? >> >> Thanks. >> > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/android-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/android-developers/92ebe9f2-7806-44e1-b088-771dba814455%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
