If it helps, here is what we found<div>You need to create the network, have the others join it, then share the activity with the neighbourhood after they have already joined. </div><div>If the activity was shared before the other XOs had joined the ad hoc network they couldnt see the activity and could not see invitations to join.</div>
<div><div><br clear="all">Kind regards<br>Tabitha Roder<br>eLearning specialist and olpc volunteer<br><a href="mailto:tabitha@tabitha.net.nz" target="_blank">tabitha@tabitha.net.nz</a><br>Cell +64 21 482229<br><a href="http://tabitharoder.wordpress.com/" target="_blank">http://tabitharoder.wordpress.com/</a><br>
<br>
<br><br><div class="gmail_quote">On 24 October 2010 22:07, James Cameron <span dir="ltr"><<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
G'day Jonathan,<br>
<br>
You did not mention the software version you are using, so I'm presuming<br>
you are using the current release 10.1.2 also known as build os852.<br>
<br>
1.<br>
<br>
The most likely cause of the symptom you describe is laptops going into<br>
idle suspend. There is a known problem where this will prevent the<br>
neighbourhood view from being updated as activities are shared (#10363).<br>
<br>
You can workaround this by turning off Automatic Power Management in My<br>
Settings -> Power. A future release (10.1.3 due in December) may<br>
suppress idle suspend when an activity is shared from a laptop, but not<br>
prevent it on the other laptops in a group.<br>
<br>
2.<br>
<br>
The second most likely cause is noisy radio environment (#10397).<br>
<br>
Each ad-hoc group has within it one laptop that is the timing master for<br>
the group. The role moves from laptop to laptop dynamically, under<br>
control of the firmware in the wireless card. The purpose of the timing<br>
master is to ensure that the other laptops in the group only transmit<br>
when no other laptop in the group is transmitting.<br>
<br>
When there is another ad-hoc group nearby, with it's own timing master,<br>
there is very little coordination, and so the transmissions can occur at<br>
the same time, resulting in several laptops not receiving them.<br>
<br>
Further, the transmission of "new shared activity" is done as a<br>
"multicast" packet using the slowest data rate, and is done only every<br>
three minutes after the first transmission! Three minutes is an<br>
eternity in class time. So if the first packet is lost, it can take a<br>
long time before the second packet is heard.<br>
<br>
You can workaround this by (a) restricting the number of nearby ad-hoc<br>
networks, by increasing the distance between groups, (b) ensuring all<br>
laptops in the same room join the same ad-hoc network, (c) using an<br>
access point for the timing master, or (d) stopping the shared activity,<br>
starting a new activity, and sharing it once more.<br>
<br>
3.<br>
<br>
The third most likely cause is that not all laptops "saw" each other in<br>
the neighbourhood view before the activity was shared.<br>
<br>
You can workaround this by checking that all laptops can see each other<br>
in that view before sharing an activity. The cause of not seeing one<br>
another relates to #2 above.<br>
<br>
References:<br>
<br>
<a href="http://dev.laptop.org/ticket/10363" target="_blank">http://dev.laptop.org/ticket/10363</a><br>
<a href="http://dev.laptop.org/ticket/10397" target="_blank">http://dev.laptop.org/ticket/10397</a><br>
<font color="#888888"><br>
--<br>
James Cameron<br>
<a href="http://quozl.linux.org.au/" target="_blank">http://quozl.linux.org.au/</a><br>
_______________________________________________<br>
OLPC-AU mailing list<br>
<a href="mailto:OLPC-AU@lists.laptop.org">OLPC-AU@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/olpc-au" target="_blank">http://lists.laptop.org/listinfo/olpc-au</a><br>
</font></blockquote></div><br></div></div>