Changes

* COLD MAIN (to homescreen) start**Endpoints: the endpoints are process start and visual completeness (i.e. the homescreen is fully drawn). We believe the bottleneck is the main thread. A possibly important event for perceived performance is when the first frame is drawn*** Neither endpoint is available in the profiler. Surrogates are <code>Application.onCreate</code> or <code>*Activity.onCreate</code> or to the first frame is drawn (the last two have profiler markers)**Bottleneck: we believe it's the main thread**Misc: a possibly important event for perceived performance is when the first frame is drawn * WARM MAIN (to homescreen) start**Endpoints: the endpoints are <code>IntentReceiverActivity.onCreate</code> and visual completeness. See **Bottleneck: see COLD MAIN**Misc: see COLD MAIN for the bottleneck and other details * COLD VIEW start**Endpoints: the endpoints are process start and <code>GeckoSession.load</code>. ***The bottleneck latter endpoint is available as a profiler marker**Bottleneck: unknown. A **Misc: a possibly important event for perceived performance is when the first frame is drawn *WARM VIEW start*The latter endpoint is available as a profiler marker*Endpoints: <code>IntentReceiverActivity.onCreate</code> and <code>GeckoSession.load</code>* WARM *Bottleneck: see COLD VIEW start**Misc: see COLD VIEW