On Wednesday, October 02, 2013 11:27 PM, Artemi Ivanov wrote: > >; Summary: Android boot time improvements >; Proposer: Artemi Ivanov > >== Description == >Android boot time could be dramatically improved by leveraging >checkpoints/snapshots approaches (might be sufficient for variety of >products/use cases), on the other side it would be great to study deeper >if Android cold boot speed could be improved, at least for >automotive/IVI scenarios (get display/video/audio enabled early) > >== Related work == >* 0xlab survey - Shorten Device Boot Time for Automotive IVI and >Navigation Systems; Implement Checkpointing for Android; Android Boot >Time Optimization >* CELF Boot time page - http://elinux.org/Boot_Time > >== Scope == >* Leverage most powerful hw platforms (multicore Cortex-A15 SOCs, fast >storage, etc.) >* Get max of what could be optimized at bootcode/kernel level (this >could be done in a week or so - using boottime cook books) >* Try to get Android booting to UI/video/audio in a couple of seconds >range (i.e. custom/automotive-focused use-case)... >* Compare results with snapshots/checkpoints implementation
Thanks for this proposal. Just to clarify - are you describing getting the Android framework up quickly, or doing a side-load of AV functionality in order to get to a specific feature (video playback) quickly? If the former, I have walked my own trail of tears on this path. It's a difficult problem, due to the architecture of the system. If you have some new insights here I'm very interested (at least personally). If you're talking about side-loading, then how do you envision handing the switchover of resources to java-based software, once the system is up? Thanks, -- Tim BTW: elinux page is at: http://elinux.org/Android_boot_time_improvements _______________________________________________ Celinux-dev mailing list Celinux-dev@lists.celinuxforum.org https://lists.celinuxforum.org/mailman/listinfo/celinux-dev
