Difference between revisions of "Android boot time improvements"
(add proposal page) |
|||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
; Summary: Android boot time improvements | ; Summary: Android boot time improvements | ||
; Proposer: Artemi Ivanov | ; Proposer: Artemi Ivanov | ||
| + | ; Status: Selected to be sponsored by the CE Workgroup | ||
== Description == | == Description == | ||
| Line 30: | Line 31: | ||
== Comments == | == Comments == | ||
| + | |||
| + | 0xlab already doing this. | ||
| + | * boot dropped from 30 seconds to 15 seconds | ||
[[Category:Project proposals 2013]] | [[Category:Project proposals 2013]] | ||
| + | [[Category:Project proposals 2015]] | ||
Latest revision as of 07:37, 22 May 2015
- Summary
- Android boot time improvements
- Proposer
- Artemi Ivanov
- Status
- Selected to be sponsored by the CE Workgroup
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
Efforts: 6-8 weeks
Contractor Candidates
Comments
0xlab already doing this.
- boot dropped from 30 seconds to 15 seconds
