[MeeGo-ivi] Question on IVI startup/resume/shutdown

[Nasa]

Pavel,

Good breakdown of the times.  Some of the items you mentioned
infer some other requirements.  Assuming Meego is handling
audio:

1. Remember what source was last used
2. Remember where in that source you were at

And some others based on your statements

1. The system uses cold boots
   -- may not be a hard requirement based on power availability



I don't believe there are hooks right now for the 1st two and
cold boots (depending on hardware) would really struggle to meet
the time from cold boots.


Nasa

----- "Pavel Konopelko (P.)" <pkonopel at visteon.com> wrote:

> Nasa,
> 
> Nasa wrote on 2011-03-17:
> > So...
> > 
> > I was wondering, what is the thinking about how
> > IVI will be started? shutdown? resumed?
> > 
> > I know from previous post, the goal of starting
> > up in less than 2 seconds was mentioned (although
> > how that was to be measured never was fleshed out).
> > But I don't recall anything about the other 2.
> 
> The requirements on start up timing are usually more detailed than
> that.  They will vary depending on the specific OEM and product, but
> would typically be in the following range:
> 
> - splash screen (possibly animated): 1s
> - early audio (chimes and gongs): 1-2s
> - early video (rear view camera, etc.): 2-5s
> - audio from AM/FM tuner (when it was the last heard source): 2-4s
> - audio from digital radio (when it was the last heard source): 4s
> - audio from digital media including audio CDs (when it was the last
> heard source): 10s
> - HMI in the last active state and fully functional: 10s
> - speech recognition fully functional: 10-12s
> - Bluetooth phone functionality available (connection, phone book
> access, etc.): 15s
> 
> The time is measured from the power on reset (i.e. the head unit is
> powered down).
> 
> > In the hobbiest world; things like hibernation, stand-by,
> > and cold boot are all discussed regularly as the typical
> > user expectation of turn key - hear music doesn't
> > actual happen (standby is close, but not quite).
> > 
> > In Meego I'm not sure what the suggested strategy for
> > that is going to be.  Has it been thought about and/or
> > discussed?  I have some ideas, but I wanted to hear
> > what the smart people have to say on this (smart != me).
> 
> In terms of the requirements, those listed above are common place in
> automotive industry.  We must meet them [or at least do not get in the
> way--see below] in order make MeeGo IVI a viable platform choice.
> 
> The current head unit design typically relies on dedicated hardware to
> meet some of the above requirements.  For example, it is rather common
> to use a dedicated microcontroller to listen to the vehicle bus(es)
> and control e.g. the internal audio amplifier to produce chimes and
> gongs upon command received via network while the 'big guy' running
> e.g. MeeGo is starting up.  Once it is up and running it would take
> over the amplifier control.
> 
> 
> Regards,
> --Pavel Konopelko
> 
> 
> > 
> > Nasa _______________________________________________ MeeGo-ivi
> mailing
> > list MeeGo-ivi at lists.meego.com
> http://lists.meego.com/listinfo/meego-ivi
> >