next »

[BruceM]

As requested, I'm reporting on my experience with update.1, build 703.

On the positive side, power management is very nice.  It's convenient to be able to close the lid and leave the XO unplugged for hours without worrying that the batteries will run down.

On the negative side of power management, it often drops the wireless connection when it's asleep, so when you wake it up you have to remember to see if you're connected and possibly reconnect. Sometimes when it wakes up it doesn't show any wireless points, not even its own three meshes.  A reboot is required to fix it (restarting Sugar doesn't do it).

Sometimes when it wakes up (especially after a relatively long period), the keyboard and touch pad will be completely unresponsive.  The only solution I've found is to reboot by power-cycling the XO.

I've also noticed a proliferation of media names.  For example, if you have an SD card called DISK plugged in, after a few sleep/wake cycles you will have /media/DISK, /media/DISK-1, /media/DISK-2, etc.  Only the highest-numbered one is the actual SD card.  This does not affect access to the media via the Journal, but only from linux.  The same can happen with USB sticks.  Rebooting eliminates the extra names.

The Journal seems to have some quirks. Sometimes when you try to open the metainfo for an activity (e.g., to see keywords etc.), it resumes the activity instead.  (After you quit and try to open the metadata a subsequent time, however, the metadata open correctly.)  (I think this may just happen on activities on external media, but I'm not sure.) 

Sometimes attempting to open metadata for an activity resumes a *different* activity!

Sometimes clicking "-" in the metadata does not delete the activity (does nothing except highlight the "-").

There is some surprising behavior with copying files.  For example, if you copy a pdf file from a USB stick to the Journal, and from the Journal to an SD card, only the metadata but not the file content might be copied.  I have observed the same with rtf and html files ("kept"  from Write); "kept" txt files don't seem to have this problem.

Some activities seem to be broken:

The News Reader launches, and allows you to add feeds, but doesn't remember them, so you have to add them again each time it is started. Also, when you click on a news item to see the full entry, it does nothing (doesn't launch Browse).

The xo-get activity shows "starting" for a while, then quits.  (xo-get.py does work from the command line, however.)

The opera activity does not work (although opera can be launched from the command line); this is a documented problem.

Finally, sugar-control-panel -s/-g radio doesn't work (produces an error).

[infomaven]

I concur with much that you report - I did an olpc-update from 656 and had a number of the same issues. Power management gets in the way when trying to stream audio through Totem - first the screen blacks out, on resume wireless does not come up (your description is right on) -- with the time out on power management, streaming audio is impossible.

Also lost access to addons such as fluendo, flash and opera (opera no longer runs from Terminal command line even though files are still on machine, mostly in the versions/usr/656 directories. "opera" worked before, "totem' still runs from command line, but not opera. Argh.

If I stick to wanting streaming audio (which is a high priority for me - long story) I think I have to start over and go back to an activated 656 update and wait for better control of on/off/on again power management.   Sometimes I just wanna leave it on!

Also had same issue with Journal and lack of access to metadata - and that was with internal files as well as external. You are brave with your trying out the SD cards what with alll the reports of SD card corruption with this build. (Did you install a fix?)  I was too afraid to try (dont have SD memory to burn at the moment....)

Thanks for the clear notes on your experience. I was having problems framing them, and your words help.

[BruceM]

Brave?  Stupid?  I don't know.  I didn't do anything special to avoid the SD card problem, so maybe I've been lucky.  A problem with the SD card did show up today; although it is inserted, it does not show up in the Journal.  I can access the card without any trouble from the Terminal.  This has happened a couple of times in the past, but ejecting the card and reinserting it has always solved the problem (i.e., when I reinserted it, it showed up in the Journal).  I have tried that several times today, however, and even deleted the .olpc.store directory, in case that had got corrupted, but so far nothing will get the card to show up in the Journal, although I can use it fine from the Terminal.  Very annoying.  I'm not sure what to try next.