#11995 NORM Not Tri: DCON/final plymouth screen not guaranteed to be unfrozen before welcome activity starts cycling

[Zarro Boogs per Child]

#11995: DCON/final plymouth screen not guaranteed to be unfrozen before welcome
activity starts cycling
--------------------------------------+-------------------------------------
           Reporter:  greenfeld       |       Owner:  godiard                          
               Type:  defect          |      Status:  new                              
           Priority:  normal          |   Milestone:  Not Triaged                      
          Component:  other-activity  |     Version:  Development build as of this date
         Resolution:                  |    Keywords:                                   
        Next_action:  diagnose        |    Verified:  0                                
Deployment_affected:                  |   Blockedby:                                   
           Blocking:                  |  
--------------------------------------+-------------------------------------

Comment(by dsd):

 Going a bit off topic now, just wanted to clarify one thing: Gonzalo
 suggested that he's concerned that the DCON is being unfrozen too late (in
 the normal boot case). Actually its being unfrozen too early in this case.
 Regarding normal boot (ignoring welcome and intro screen considerations):

 The design is that the XO buddy icon in the center of the screen is
 present from the moment that you hit the power button (shown by the
 firmware), throughout the boot anim, until the XO "owner" icon is drawn in
 the center of the screen in sugar. This reinforces the concept that the
 owner icon on the screen is 'you' and that it doesn't go away.

 At the moment, the DCON is frozen late in the boot anim so that the XO
 owner icon doesn't get lost from the screen, but sugar unfreezes it too
 early, around 3 seconds before the XO owner icon is drawn, so there is an
 uncomfortable blank space in the middle of the screen towards the end of
 the otherwise-visually-perfect boot process :) There is a ticket about
 this.

-- 
Ticket URL: <http://dev.laptop.org/ticket/11995#comment:6>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system