<div class="gmail_quote">On Mon, Jan 9, 2012 at 6:10 PM, John Watlington <span dir="ltr"><<a href="mailto:wad@laptop.org">wad@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
On Jan 7, 2012, at 8:49 PM, Chris Leonard wrote:<br>
> On Sat, Jan 7, 2012 at 6:40 PM, Alan Eliasen <<a href="mailto:eliasen@mindspring.com">eliasen@mindspring.com</a>> wrote:<br>
>> Does anyone have any comments about the XO-3 announcement here?<br>
>><br>
>> <a href="http://tinyurl.com/74vd7ec" target="_blank">http://tinyurl.com/74vd7ec</a><br>
>><br>
>> I'd think that the smart people who are actually doing all the work<br>
>> here might have talked about it more!<br>
<br>
</div>Fortunately, I still am an OLPC employee!<br>
XO-3 has been condensing for the last year, mostly as an industrial<br>
design effort while XO-1.75 (which has been discussed on this list,<br>
and distributed to a number of developers) provided the platform for<br>
hardware and software development.<br>
<div class="im"><br>
>> I'm also curious about the power claims. What is its power<br>
>> consumption and charging requirements? Has it actually been<br>
>> demonstrated to be chargeable by "solar panels, hand cranks and other<br>
>> alternative power sources?" Especially ones not requiring systems which<br>
>> cost many times more than the price of the laptop, nor require someone<br>
>> with the green skin color of the XO to crank.<br>
</div>> ...<br>
<div class="im">> If you've been following XO-1.75 development on this list, it might be<br>
> helpful to think of the XO-1.75 as an evolutionary step towards the<br>
</div>> XO-3.0...<br>
<br>
Right! At this stage in development, the XO-1.75 actually consumes<br>
one to two watts less than the XO-3, due to the low power PixelQi<br>
screen and the DCON architecture used throughout the XO-1 laptops.<br>
We intend on providing those in a later B-stage XO-3 tablet, but need<br>
to get a PixelQi display of appropriate size and a new DCON developed.<br>
Theoretically, the power consumption of the laptop and the tablet should<br>
be equal (given the same screen size).<br>
<br>
We not only support input from solar panels (accepting input voltages<br>
from 11 to 24V on the DC input) we also support maximum power point<br>
tracking on the input if it is sensed to have a "high" input impedance (such<br>
as a solar cell). Solar power is used to charge laptops in both XO-1<br>
and XO-1.5 deployments. XO-1.75 has the same DC input/battery, and<br>
operates using less power --- it finally reaches the power goals that OLPC<br>
set six years ago.<br>
<br>
With a 2 to 3W power consumption, a laptop/tablet becomes feasible<br>
to use with power coming from a hand crank providing 10W --- crank<br>
for five minutes to get twenty minutes of use. We support charging<br>
at up to 25W, close to the limit of human powered charging, for more<br>
ambitious quick charging schemes (such as treadmills or stationary<br>
bikes). If this is used as a backup for solar charging, it becomes<br>
even more acceptable.<br>
<br>
> ...I'm really excited by the possibilities that a virtual<br>
<div class="im">> keyboard on the tablet XO-3.0 will represent for ease of localization,<br>
> no more messy, physical, custom silk-screening of rubber membranes as<br>
> a limitation on the potentially available keyboard options, just<br>
> invoke different file(s) for a new keyboard layout.<br>
<br>
</div>It is the elimination of the keyboard that excites me most about a tablet.<br>
It is difficult to prevent keyboard breakage, and the keyboard customization<br>
that we recommend so kids can work in their own alphabet impacts<br>
delivery times and production volumes.<br>
<div class="im"><br>
> My current understanding is that the firmware will be the latest and<br>
> greatest in Open Firmware, with OLPC's specific needs being addressed<br>
> by contributions from OLPC coders. If you've been watching the devel<br>
> list, you've probably seen a fair amount of traffic about Fedora on<br>
> ARM. Just like Sugar on earlier XO models, the Sugar UI on the<br>
> XO-1.75 (and XO-3) sits on top of what is basically a Fedora Linux OS<br>
> spin,. Obviously the packages are a little different (they are ported<br>
> to ARM) but they still come from Fedora repos.<br>
<br>
</div>With an ARM SoC, we are finally being forced to consider specialised<br>
builds of Fedora as hard floating point support is required for the best<br>
performance. But we haven't gone there yet.<br>
<div class="im"><br>
> Being an ARM processor, it is not a huge mental leap to imagine that<br>
> Android code can be used. although I'm not sure why you would do that in<br>
> an educational setting, but "open" means "open", so sure, why not let<br>
> people know about that possibility and bask in the Android spotlight<br>
> at CES.<br>
</div>With the laptops, support for Windows was a requirement for some<br>
customers even though they didn't actually purchases any laptops w. Windows installed. Android is the equivalent for<br>
tablets --- if you don't support it, you are viewed as deficient.</blockquote><div><br></div><div>(TL;DR - I don't think Android is as big a - real or perceived - requirement as Windows was. Plus large 1-to-1 projects seem to be moving towards heterogeneous technology solutions so we'll have to figure out better ways of cross-platform support in educational technologies either way.)</div>
<div><br></div><div>I'm wondering whether that equivalence will really hold true in the future.</div><div><br></div><div>It's my understanding and underlying assumption that there's not just the "the kids gotta learn to use Windows because that's what the workplace expects them to know" argument. One other reason why some countries/projects were and/or are keen on having Windows compatibility is so teachers can continue using existing software solutions for administrative purposes or what not.</div>
<div><br></div><div>Now first of all it seems like at least some projects are moving towards giving pupils and teachers different devices with different operating systems (in many cases dual-boot for teachers). Uruguay's Plan Ceibal is certainly experimenting with this approach as is Costa Rica in its project with Fundación Quirós Tanzi. Plus if I'm not mistaken other RFPs will soon be out there which also call for different machines for pupils and teachers with the potential of running a dual-boot setup.</div>
<div><br></div><div>Secondly, and probably more importantly, neither of the aforementioned assumptions are really true with Android. I've yet to hear the argument that pupils absolutely need to use Android (or iOS for that matter) based devices today because that's what they gotta know tomorrow. Plus there frankly speaking aren't too many apps focused on education (regardless of for learning or administration) available for Android today (<a href="https://market.android.com/apps/EDUCATION?feature=category-nav">https://market.android.com/apps/EDUCATION?feature=category-nav</a>). I had a tough time finding German ones when I recently tested the Samsung Galaxy Tab 10.1 and the number of Spanish ones seems relatively small as well (and don't even get me started on Quechua, Aymara, Dari or Amharic). In combination with the absence of many years of Microsoft lobbying this gives Android vs. Sugar a much smaller pull factor than in the previous Windows vs. Sugar situation.</div>
<div><br></div><div>I therefore believe that OLPC should have an easier time doing the necessary groundwork when it comes to what Sameer in a related context called "managing perceptions" and the associated expectations by key stakeholders. This should hopefully also translate into more friendly RFPs.</div>
<div><br></div><div>Last but not least I strongly believe that all players in this area have to move towards more educational technology compatibility across hardware and software platforms (and a number of other areas such as monitoring, assessment, TOC calculations, etc. but that's for another time;-). While a homogeneous technology solution would maybe make some lives easier I think that especially in (very) large scale 1-to-1 projects we'll increasingly see a mix'n'match of heterogeneous solutions. IIRC Plan Ceibal today uses at least 3 different hardware platforms (XO-1, XO-1.5/1.5HS, JumPC/Olidata - soon to be joined by XO-1.75s) and a variety of different versions of Sugar, SoaS, and Ubuntu. As such we'll all have to find better ways of co-existance which don't put unnecessary burdens on pupils, teachers, administrators, and parents.</div>
<div><br></div><div>Cheers,</div><div>Christoph</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
> None of this information has been hidden from public view. In fact<br>
> there is a lot more in terms of details on the wiki, but being a wiki,<br>
> the details are subject to change. :-)<br>
</div>Or more likely, obscured by all the old, out of date or speculative, info.<br>
See <a href="http://wiki.laptop.org/go/XO_3_A1" target="_blank">http://wiki.laptop.org/go/XO_3_A1</a> for the latest prototype info.<br>
<div class="im"><br>
> I anxiously await the results of the helicopter drop test :-)<br>
</div>I thought tablets could fly...<br>
<br>
Cheers,<br>
wad<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Christoph Derndorfer<div><br></div><div><div>volunteer, OLPC (Austria) [<a href="http://www.olpc.at/" target="_blank">www.olpc.at</a>]<br><div>editor, OLPC News [<a href="http://www.olpcnews.com/" target="_blank">www.olpcnews.com</a>]<br>
contributor, TechnikBasteln [<a href="http://www.technikbasteln.net/" target="_blank">www.technikbasteln.net</a>]</div></div><div><br></div><div>e-mail: <a href="mailto:christoph@derndorfer.eu" target="_blank">christoph@derndorfer.eu</a></div>
<div><br></div></div><br>