In my testing so far, just running this command at the shell after using the shutdown scripts (but not actually suspending) seemed to start everything back up successfully, so I would be interested in any further testing you do on this. That script doesn't exit (not checked why, just assumed that was normal, certainly it continues running after a reboot of my core...) when I executed it I used the & character as well... I guess the only untidiness is that it will be a job in that bash session, but that bash session in a script will soon terminate and leave the orphaned process running, just like a normally booted system, so do you think this is a real issue?

The only problem might be that the script is started within the resume hook. Don't know how the resume system handles a script not exiting.

Agreed on the WOL point, will try that.

Not a big issue, I also used the ethtool directly in my scripts. I just noticed the other script today 

Also, will look into the suspend to disk option... I think I have a disk somewhere, just not sure what I have to do to prepare it for this... doesn't 0710 MDs detect HDDs and use them as swap? Does it need to be partitioned and formated first? As what?

Yes, it does detect swap partitions on HDDs and uses them. (Which is something I'd like to avoid, as I use a CF card for suspend to disk). You need to create a swap partition and possibly also do a mkswap on it. Also see the suspend wiki article for more information, there is some special considerations for LMCE.

br,
sambuca

ok, I tried your script, and it works fine for me. I used suspend to disk, but that should be the same from lmce's perspective.
It stops all devices and lastly kills the launch manager.

At resume, it does nothing (yet). You said you started the devices using Start_LocalDevices.sh, but that it does not start the MD DCE device? Not sure what you mean by that? The App server? Didn't have time to try this though, my wife wanted to use the TV 

But I did try to run the lmce_launch_manager.sh at resume via a resume hook, and that sort of worked. It started the launch manager and every device successfully, but it seemed like the resume script didn't end. I even tried to wrap the lmce_launch_manager.sh in a script with the fork (&) char at the end, but the script still did not return to the console. Didn't have time to try repeated suspend/resumes with this configuration though.

Btw. I noticed there is a enable_wol.sh script in /usr/pluto/bin folder. I guess it might be good to use that instead of the ethtool directly?

And one final suggestion: I've read (and experienced first hand) that suspend to disk is easier to get to work than suspend to ram. This is because when resuming from disk normal BIOS POST happens and starts the graphics card normally, in contrast to resume from ram where the OS needs to do much stuff. Maybe you will have more success trying s-to-disk?

I hope to do some more testing later this week.

br,
sambuca

ooh, I like that idea..

I'll assume you will use a PC of some sorts to take the pictures and show the preview, although you don't mention that specifically.

Regarding 1. to 3. I suppose it might be possible to patch something together using various linux programs, but other might be able to give you more pointers.
I think 4. would easily be accomplished by having the pictures folder mounted to the computer, and using MessageSend or SQL directly to make the files with "use as screensaver". Perhaps create a add_to_screensaver.sh script that is called when the picture has been taken.

It'll be interesting to see how this turns out.

br,
sambuca

I'll give it a go. I was out of town this weekend, if not I would probably have tested it already 

I already have a working suspend/resume on one of my MDs, so I think this should be easy to test. But I also have had my share of problems with suspending, or more correctly resuming. In 704 I had suspend to ram working, but when 710 came out, they had removed the s2ram utility.. bummer. To make a long story short, I instead set it up to suspend to disk using a compact flash card.

btw, nice work Colin 

Have you looked at the http://wiki.linuxmce.org/index.php/Suspend page ? It describes how to set up hibernation, and also how to add script execution on suspend/resume.
Doesn't help with the dependency issue though 

Great work by the way, I think you are very close to a working solution. If you see in the wiki article mentioned, I did a very crude script to kill the processes I knew were running. But I didn't think of using the SQL approach you use.

sambuca

Hi

If this is a Xine related issue, I think the Xine forum/list/whatever might be of more help. Once that is figured out, you should be able to find information about how to set options for Xine in this forum (pretty sure I've seen such posts).

Not sure if upgrading Xine is easy, depends on how LMCE controls it. The key here is the Xine_player, and some searches should provide information about it, and if it requires a patched Xine.

br, sambuca

Hi nite_man,

Maybe its the default behaviour? I'm not at home right now, so I can't test it.
Does pressing the correct Fx button during video playback open the main menu, but not the remote button?

Hi everyone,

I've added parsing of the configuration file to the MO and opening of the web browser from within the VMC viewer. This should enable much more of the original MOs functionality (set scenarios, view alerts etc.).

But it does not inform you of any events like (I think) the original mo does, because Java does not allow call interception, which is what the Symbian orbiter uses to alert you. (LMCE calls your phone, and the PlutoMO intercept it, and does its magic). Please correct me if I am wrong
It would be possible to intercept SMS in the JavaMO, but it would require a change in LMCE to send SMS instead of calling your phone. I don't even know if most phone providers support sending SMS via land line/VOIP?

Time to bring out your phones and start testing 

br,
sambuca

Hi,

On my default install, I have some of those (if not all) functions on the color buttons. I have a Hauppage remote, btw.

If not, I think you can alter/add the functionality for different remote buttons in the advanced device admin page for the remote. Can't remember the details, search the forums or the wiki.

br,
sambuca

Ok, I got time to do some more work on the JavaMO. 

I fixed some issues related to disconnect/reconnects. I ran into them when testing follow me. It disconnected, but it never succesfully reconnected. I'm not sure but perhaps hari's version handled reconnects better.
Anyway, it should work now.
For those who like to read log files etc, it is now possible to close the VMCViewer/Orbiter, open the log, close it and then reopen the viewer with a "Orbiter" menu entry when it is connected.

The new version has been published on my website. (see previous post for url  )

br,
sambuca

It's probably a combination of hard disk, bios and linux that gives you problem with using the 250G disk. Maybe you can find some more information on the Internet. I remember to have read something about bios settings wrt. disk size and linux, but it was some time ago, not sure it applies.

br, sambuca

Hi,

I can confirm buleks issue.
As for playing files and moving them to other MDs, I did have some problems with that but can't exactly remember what..

br,
sambuca

Hmm,
As far as I can see, the jar file size is the same as the Midlet-Jar-Size. It also installs fine on my SonyEricsson phone. Maybe there is some caching/proxy in your providers network?
At least I can't think of anything else at this moment.

br,
sambuca

Hi Dan,

Would you mind trying again? I changed the reference to SELECT_COMMAND, so maybe it works now. I cannot see anything wrong with the code, but maybe some devices are a bit picky.

(It was the list, hari The phone tries to access CommandListener.SELECT_COMMAND when I use the SELECT_COMMAND reference in the code. The class extends List and implements CommandListener, the SELECT_COMMAND is in the List class)

br,
sambuca

I did a preliminary check-in of my current VMC code. It is still very much a work in progress.

Still much to do, though I am not sure whether all the code in the original mo is used for lmce. Maybe someone can shed some light on this?

br,
sambuca