MediaPortal - another resume from standby (S3) problem (1 Viewer)

[craigparris1]

TV-Server Version: 1.0 Final
MediaPortal Version: 1.0 Final
MediaPortal Skin: Blue3 4:3
Windows Version: XP Service Pack 3
CPU Type: AMD
HDD: ~500GB
Memory: 2GB
Motherboard: Gigabyte
Video Card: 8500GT
Video Card Driver:
Sound Card:
Sound Card AC3:
Sound Card Driver:
1. TV Card: Leadtek Winfast DTV1000S
1. TV Card Type:
1. TV Card Driver:
2. TV Card: Leadtek Winfast DTV1000S
2. TV Card Type:
2. TV Card Driver:
3. TV Card:
3. TV Card Type:
3. TV Card Driver:
4. TV Card:
4. TV Card Type:
4. TV Card Driver:
MPEG2 Video Codec:
MPEG2 Audio Codec:
h.264 Video Codec:
Satelite/CableTV Provider:
HTPC Case:
Cooling:
Power Supply:
Remote: Leadtek
TV: Analog
TV - HTPC Connection:

Hi guys,

I've been trying to get S3 resume working correctly with MediaPortal 1.0 Final. I recently upgraded from 1.0 RC3 - which I had finally got resuming perfectly everytime. I hadn't specifically noted down the configuration settings in RC3, but I've now tried all sorts of combinations with 1.0 Final and still can't get a reliable solution. The problem that is occurring is one which is reported by other people - when the PC resumes, there is just a black screen, which is the non-responsive MediaPortal client front-end. This probably happens 1 out of every 7 or 8 resumes (other times the PC resumes straight away and MediaPortal is ready to go).

As I said, though, with RC3 I had it working fine everytime I restored (for the couple of months that I had RC3 installed).

I read through various posts (tried the S3hack fix), and then decided I would try the MPStandbyHandler, but this didn't work either. After looking at the MPStandbyHandler log and then looking at the MediaPortal logs in more detail, is that they had one particular thing in common - here is the example from the MediaPortal.log file:

OnResume - OnResume called but !_suspended

The MPStandbyHandler log has a similar line - about OnResume being called but "not suspended".

Full MediaPortal and TV-Server logs are attached from the time of a cold boot of the machine, through to standby, then manually resuming. For the example logs attached, I had MediaPortal configured to restart on resume - but it did not restart. I'm guessing the the "OnResume called but !_suspended" message has something to do with the app not properly going through all the steps that should be performed on resume.

Hopefully someone can give me some pointers on where the problem lies.

Thanks,
Craig

 

[craigparris1]

Some more info

A bump for this thread, as I've discovered something else that is probably related to my problem.

I was looking at another couple of threads relating to standby/resume problems, and noticed in this thread, when I looked at the attached log file - which is as follows:

2009-01-26 00:00:46.427397 [Info.][MPMain]: Main: WM_POWERBROADCAST: 4
2009-01-26 00:00:46.428373 [Info.][MPMain]: Main: Windows is suspending
2009-01-26 00:00:46.434232 [Info.][MPMain]: Main: Stopping playback
2009-01-26 00:00:46.440091 [Info.][MPMain]: Main: Stopping recorder
2009-01-26 00:00:46.441068 [Info.][MPMain]: Main: Stopping AutoPlay
2009-01-26 00:00:46.444974 [Info.][MPMain]: Main: OnSuspend - Done
2009-01-26 04:54:15.122239 [Info.][MPMain]: Main: WM_POWERBROADCAST: 18
2009-01-26 04:54:15.123215 [Info.][MPMain]: Main: Windows has resumed from standby or hibernate mode to handle a requested event
2009-01-26 04:54:15.124192 [Info.][MPMain]: Main: OnResumeAutomatic - Starting recorder
2009-01-26 04:54:15.125168 [Info.][MPMain]: TvCardCollection: TVPlugin detected -> no TVE2 card setup
2009-01-26 04:54:15.127121 [Info.][CommandProcessor]: Commandprocessor: Starting
2009-01-26 04:54:15.128098 [Info.][MPMain]: Recorder: start
2009-01-26 04:54:16.115339 [Info.][MPMain]: Main: OnResumeAutomatic - Done
2009-01-26 06:17:06.862621 [Info.][MPMain]: Main: WM_POWERBROADCAST: 4
2009-01-26 06:17:06.863597 [Info.][MPMain]: Main: Windows is suspending

the first couple of entries are from the MP client registering that the PC is going into suspend, and running the corresponding routines for this. In my MediaPortal.log file, I don't see any of these lines. I see a WM_POWERBROADCAST: 6 (as opposed to 4 which is in hjbaard's log) .... then I see the same WM_POWERBROADCAST: 18, which I'm assuming is the "resume" notification.

Can someone advise if this is likely an issue with my PC or with MediaPortal itself?

Cheers,
Craig

 

[chemelli]

which version of MP are you running ?

Sorry I cannot remember in which the "resume from S3 trick" was added but for sure in the latest public SVN.

It's in Configuration - General (near the end)

Simone

 

[craigparris1]

Hi Simone,

I am running 1.0 Final and had got the updated Configuration.exe from one of the other threads about standby/resume problems. The issue is, though, as you'll see from my logs - similar to Pascal's problem at the end of this page - is that the MediaPortal client isn't getting a notification that Windows goes into suspend, so when I resume the PC, MediaPortal doesn't think it should run the OnResume routine. This is the problem.

Cheers,
Craig

 

[Eyep0p]

have that black screen problem too.
if i press a key on the keyboard, mediaportal continues starting fine.
don't know if its the same problem like yours.

solved for me with this: https://forum.team-mediaportal.com/...gs-when-getting-out-standby-50788/#post347360

 

[onyx666]

i have exact the same problem as above , only a reboot helps.
also stanbyhandler gives same log.
it looks like pc goes into standby to quick so standbyhandlet does not see it has to do the resume steps

 

[Jupek]

I have same problem with RC4 and Vista. Tried "useS3Hack" but that didn't helped. Also I have noticed that this sometimes work sometimes not. Everything worked several days and HTPC woke to every recording and when I tried to manually wake HTPC MP client opened nicely and was responsive. I allready thought that I finally had now working setup but sadly last night when I tried to manually wake machine client wouldn't woke up and I had to terminate the process manually. So still looking for resolution to this and I'm willing to run test routines/logging if that helps. Here are my latest logs if those helps.

Is it btw normal behaviour that when single seat setup wake for recording it won't start screen and MP client? According some log events even unattanded wake up procedure is not same everytime which is a little weird I think. Also it is a little weird that for example my external display plugin notice wake up just fine but MP client core won't...and on a same machine same time TVService notice wake up events just fine as far I can see according the logs.

As in many post have been said when system wakes automaticly for recording, screen and for example external display remain black for me. IF everything is fine with client and it is alive when I press for example cursor button on my remote client then wake up. For me it would be just fine but if that leads to problem that client won't wake up properly when waked up manually then it is bad....can't remember how it worked on RC3...

 

[joystick]

the black screen is related to an unresponive TVservice-> at least that's what I figured out. Once I restarted the TVservice (remotely) MP client did show up again.

For me the only solution is activating "Re-Initialize TVService after standby option"

The problem I still have though (which is not bothering me atm) is that I do not get a remote connection with remot Clients due to the SQLBrowsser not restarting properly after standby....

cheers

joystick

 

[Jupek]

the black screen is related to an unresponive TVservice-> at least that's what I figured out. Once I restarted the TVservice (remotely) MP client did show up again

I activated that feature. Restarted TVService and tried again...no luck. Found out that client was unresponsive morning again after recording. Any more ideas...anyone?

 

[joystick]

have you tried MPstandbyhandler, and restart tvservice on resume? Maybe also restart the Tv Cards.
This should definately help.

cheers