#8592 HIGH 8.2.1: bug or feature? XO hogs CPU trying to find Mesh while already connected to Access Point

[Zarro Boogs per Child]

#8592: bug or feature?  XO hogs CPU trying to find Mesh while already connected to
Access Point
--------------------------+-------------------------------------------------
   Reporter:  thomaswamm  |       Owner:  marco                            
       Type:  defect      |      Status:  new                              
   Priority:  high        |   Milestone:  8.2.1                            
  Component:  sugar       |     Version:  Development build as of this date
 Resolution:              |    Keywords:  relnote                          
Next_action:  diagnose    |    Verified:  0                                
  Blockedby:  4074, 6944  |    Blocking:  8098                             
--------------------------+-------------------------------------------------

Comment(by mtd):

 Replying to [comment:14 gregorio]:
 > Anyone who knows what this means to end users can write the blurb.

 I think you did a really good job; here's my stab at it (sorry, I did not
 have enough time to make it shorter, etc.)

 Please wait for the network to reconnect when waking up: when the XO wakes
 from being suspended it will search for a Mesh connection (e.g. another
 XO) before trying to reconnect to the last AP that was in use. Please wait
 until it tries to connect to that AP before trying to manually connect to
 an AP in the Neighborhood view.  If you do not and click on the AP icon
 before the mesh icons stop pulsing, one mesh icon will continue to pulse
 forever (or until you click on a mesh icon, wait for it and the other mesh
 icons to stop pulsing, and click on the desired AP again).

 > Thanks,
 >
 > Greg S

 Martin

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