PowerScheduler++ test versions (2 Viewers)

[Ballermann]

AW: PowerScheduler++ Test Versions - 1.1.8.0 for MP 1.2.0 RC and final

Hello Michael,

ok - I will do my best with new logging files

I made some more "wake-up-for-recording-test-runs" - actually I would like to show up under what conditions I did and what kind of results I got - I hope it´s not too confusing...

I will repeat testrun #3 / #5, which were not working and will post the server logfile (tv.log) and the client log file (mediaportal.log) as mentioned in the first post.

• - return to homescreen before S3/S4
  could be made as option for PS client plugin
  --> would be great to implement as an option for the client
  
• - stop live tv before S3/S4
  - exit MePo before S3/S4
  - Pause between steps before S3/S4 = xxxx ms
  would not work since it would take too much time to complete before S3/S4 is entered (PS++ just gets an event that S3/S4 is beginning now and S3/S4 does not wait for any activity to be completed...)
  --> really no chance of combining "return to homescreen + stop + exit" before S3/S4?
  I am asking again because the testruns which were not working have been exactly the runs where PS++ brought up the action to bring system into S3 pls see my tests at the end of post
  
• - "keep tv-service alive" before S3/S4
  tvservice is kept alive on transitions to S3/S4 (at least by design )
  --> ok
• - stop / start / restart tv-Service.exe when reactivating / resuming system
  this option is already implemented (Advanced tab in PS++ server plugin config)
  --> you are talking about "reinitialize"? is it possible to make it more "transparent"?
  it seems like tvservice is kept running before S3/S4 and "just" restarted when resuming or is it already restarted/reinitialized before
  S3/S4 and again when resuming?
• - Pause between steps before reactivating / resuming = xxxx ms
  which steps do you mean?
  --> I meant the steps I suggested to bring into PS++, for example:
  return to homescreen [pause 1000ms], stop (live tv) [pause 1000ms], exit MePo before S3/S4 [pause 1000ms], sending into S3/S4)

So, here you will find my test-run-overview - as written before I hope it`s not confusing
By the way, actually I am testzing my RAM (8GB) for errors because the idea came up that there are "just" problems with
the hybrid-mode of standby... maybe because of a hardware error in the RAM...

Recording-Testruns with 1.2.1 Final & PS++ 1.1.8 (singleseat system)
(sorry for bad translation of all settings... (I do have a german version of win7)

**** 1st recording - testrun: ****

Windows-Powersettings :
blanking screen: never; energy saving mode: never
standard action for ending : shut down ; energy-button: Hibernate (S4)
Saving Energy: deactivate: never ; hybrid stdby: on ; hibernate: never ; Timer for activation: on

PS++ Settings:
- PS++ forces system to stdby after 5min - Hibernate (S4)
- Wake up for events

"way how system went to stdby" before scheduled record:
Automatic S4-hibernation (….when idle for 5 minutes)

Result: Success! Recording started!

Comment: when Switched on TV during recording there was no blank screen / screen off, instead of that the homescreen of MP was continuously on!

screen-blanking-testrun (because homescreen of MP was continuously on):
switched Windows-Powersettings to: blank screen after 2min
result: working! Screen is blanking, MePo still running in background, activating screen by remote is working!


**** 2nd recording - testrun: ****

Windows-Powersettings :
blanking screen: after 2min (changed to 1st run) / energy saving mode: never (unchanged)
standard action for ending : shut down (unchanged) / energy-button: S4 (unchanged)
Saving Energy: deactivate: never (unchanged) ; hybrid stdby: on (unchanged) ;
hibernate: never (unchanged) ; Timer for activation: on (unchanged)

PS++ Settings: (unchanged)
- PS++ forces system to stdby after 5min - Hibernate (S4) (unchanged)
- Wake up for events…

"way how system went to stdby" before scheduled record: (changed to 1st run)
Remote: Green Button (mapped to: "no condition: Action: Suspend - confirmed by “cursor left + ok”)

Result: Success! Recording started!

**** 3rd recording - testrun: ****

Windows-Powersettings :
blanking screen: after 2min (unchanged) / energy saving mode: never (unchanged)
standard action for ending : shut down (unchanged) / energy-button: S4 (unchanged)
Saving Energy: deactivate: never (unchanged) ; hybrid stdby: on (unchanged) ;
hibernate: never (unchanged) ; Timer for activation: on (unchanged)

PS++ Settings:
- PS++ forces system to stdby after 5min - Hibernate (S3) (changed to 2nd run)
- Wake up for events…

"way how system went to stdby" before scheduled record:
Automatic S3-hibernation (….when idle for 5 minutes)

---> Result: NO START – TIMER LOST!

**** 4th recording - testrun: ****

Windows-Powersettings :
blanking screen: after 2min (unchanged) / energy saving mode: never (unchanged)
standard action for ending : shut down (unchanged) / energy-button: S4 (unchanged)
Saving Energy: deactivate: never (unchanged) ; hybrid stdby: on (unchanged) ;
hibernate: never (unchanged) ; Timer for activation: on (unchanged)

PS++ Settings:
- PS++ forces system to stdby after 5min - Hibernate (S3) (unchanged)
- Wake up for events…

"way how system went to stdby" before scheduled record:
Remote: Green Button (mapped to: "no condition: Action: Suspend - confirmed by “cursor left + ok”)

Result: Success! Recording started!


5th recording – testrun: Repeat of 3rd test-run (automatic S3)

---> Result: NO START – TIMER LOST!


After that runs I switched back PS++ to automatic S4-Mode (when idle for 5min) - like 2nd run - and programmed 2 recordings
for the last night with 2 hours in between and sended system via remote / MePo-Menu to S4 - recordings were working!!!

 

[Ballermann]

AW: PowerScheduler++ Test Versions - 1.1.8.0 for MP 1.2.0 RC and final

So... here we go... another run which wasn`t working - same settings like
#3 / # 5 (automatic S3 via PS++)

**** 6th recording - testrun: ****

Windows-Powersettings :
blanking screen: after 2min (unchanged) / energy saving mode: never (unchanged)
standard action for ending : shut down (unchanged) / energy-button: S4 (unchanged)
Saving Energy: deactivate: never (unchanged) ; hybrid stdby: on (unchanged) ;
hibernate: never (unchanged) ; Timer for activation: on (unchanged)

PS++ Settings:
- PS++ forces system to stdby after 5min - Hibernate (S3) (like #3 / #5)
- Wake up for events…

"way how system went to stdby" before scheduled record:
Automatic S3-hibernation (….when idle for 5 minutes)

---> Result: NO START – TIMER LOST!

Record should have been started at 16:00, booting up / resuming 1min before at 15:59.
System went idle and powered down (to S3) at approx. 15:47
No Wake up at 15:59!
Manual wakeup via Mouse at approx. 16:05.
I wasn`t able to find a mediaportal.log (?!),
the tv.log (for the specific time-span) you can find attached.
Hope you will find something usable

 

[rRalv]

Re: AW: PowerScheduler++ Test Versions - 1.1.8.0 for MP 1.2.0 RC and final

---> Result: NO START – TIMER LOST!

Hi Ballermann.

Have you enabled EPG at TV cards?

From MePo 1.1.0 I had a strange problem with EPG. The system did not wake up because EPG generated errors with some channels that left the system unstable and did not wake up.

Now I use WebEPG.

 

[michael_t]

AW: PowerScheduler++ Test Versions - 1.1.8.0 for MP 1.2.0 RC and final

...
Record should have been started at 16:00, booting up / resuming 1min before at 15:59.
System went idle and powered down (to S3) at approx. 15:47
No Wake up at 15:59!
Manual wakeup via Mouse at approx. 16:05.
I wasn`t able to find a mediaportal.log (?!),
the tv.log (for the specific time-span) you can find attached.
Hope you will find something usable

Please read the wiki how to provide proper logs. Set the PS++ check interval to 15 seconds. Then you should do two testruns: once the situation where you have no working wakeup (automatic standby to S3) and once the working situation (automatic standby to S4) and provide the logs for both.

Michael

 

[Ballermann]

AW: Re: AW: PowerScheduler++ Test Versions - 1.1.8.0 for MP 1.2.0 RC and final

Have you enabled EPG at TV cards?

Yes, I do.
I just disabled EPG and made a test. No change

Please read the wiki how to provide proper logs. Set the PS++ check interval to 15 seconds. Then you should do two testruns: once the situation where you have no working wakeup (automatic standby to S3) and once the working situation (automatic standby to S4) and provide the logs for both.

Thanks for the link Michael! I will do so and will post here again.

Another "strange" thing happened last night / today:
As I was heading to bed and switched off the system by pressing "power" at the MCE-remote (not at the harmony) - the system went to S3, as I was starting the system with pressing the power-button today again, it was resuming MePo and then went straight to S4! Another press of power button at the MCE-remote brought it back to MePo... maybe another hint?

The Mapping of the remote says Power=Green Button (Green button is (normally) opening up the menu with the question "sleep: yes / no")

(Windows-Powersettings and PS++ Settings had been unchanged:
blanking screen: after 2min (unchanged) / energy saving mode: never (unchanged) standard action for ending : shut down (unchanged) / energy-button: S4 (unchanged) Saving Energy: deactivate: never (unchanged) ; hybrid stdby: on (unchanged) ; hibernate: never (unchanged) ; Timer for activation: on (unchanged); PS++ forces system to stdby after 5min - Hibernate (S3) (like #3 / #5 / #6); Wake up for events enabled)

Is there a buggy setting I did in the power options or is Win7 SP1 + (almost newest) updates buggy itself?
Should I deactivate hybrid-stndby?

Before I start going on with posting my problems I want to say "thanks a lot Michael" for the plugin itself and for your patience in helping me

 

[Ballermann]

AW: PowerScheduler++ Test Versions for MP 1.2.x / 1.3 Alpha

So, here we go again, I attached some logs.

Very strange (again)...
I made a test of S3 out of debug-mode (wake-up at 16:43) - working
another test out of S3 (fm debug-mode) (wake at 17:09) - NOT working - manual start at 17:20 - Client had problems finding Server!
...tv.log and mediaportal.log to find in "S3.rar"

Testrun out of S4 fm debug (wake-up at 17:39: - working
...tv.log and mediaportal.log to find in "S4.rar"

Thanks a lot again!

 

[michael_t]

AW: PowerScheduler++ Test Versions for MP 1.2.x / 1.3 Alpha

From what you sent I can see that your tvservice has problems with de-initializing the TV controller on suspend. In the test run at 17:01 (suspend to S3) it hangs in the step "Remove filter from graph: mdapifilter0" while it had no problems in the first test run at 16:35. So it seems to me that you have a (more or less) sporadic problem with your tv card installation that causes tvservice not to wakeup at the time scheduled.

Nevertheless I would urgently recommend you to increase the PS++ check interval to 15 seconds and repeat the S3 tests. It might be that the delay in removing the filters overlaps with the next PS++ check interval (in your case only five seconds later) and thus the problem arises...

So please increase the check interval and provide comprehensive logs (the whole zip-Archive)! It costs me lots of time to analyse your problem. So I will no longer try to help you if you are not willing to take my advice, since this is waste of time for both of us.

Michael

 

[torbjorns]

Re: PowerScheduler++ Test Versions for MP 1.2.x / 1.3 Alpha

Hi Folks, and thanks for all effort you do for MP geeting better.
My concern is that after the upgrade from 1.1.3 to 1.2.0 I can no longer wake up my computer with my remote(pc button only). It works putting into sleep S3 though from remote. Im not sure where to address this problem so I start here. But either the powerscheduler or the ps++ made it work...

 

[michael_t]

AW: Re: PowerScheduler++ Test Versions for MP 1.2.x / 1.3 Alpha

Waking up your PC by remote has nothing to do with MediaPortal or PowerScheduler. It is an operating system functionality in combination with hardware. Your hardware (IR receiver) detects that the remote is sending a special code ("On") and wakes up (switches on) your PC. At the moment it is running again, the operating system continues the execution of the suspended programs and Mediaportal / PowerScheduler are active again...

So first you should try to get your PC waking up from S3 by remote without complications by Mediaportal / PowerScheduler. Deactivate MP client and MP TV server (tvservice), set your Windows power settings to "balanced", select default values and set your PC's power button action to "Sleep". If there is any, you should also check your remote's software / drivers. Then try to suspend the system and wake it up with the power button. Repeat the same with your remote. If everything is working, you can reactivate Mediaportal and work on your PowerScheduler configuration...

Michael

 

[Ballermann]

AW: PowerScheduler++ Test Versions for MP 1.2.x / 1.3 Alpha

Hello Michael,

Nevertheless I would urgently recommend you to increase the PS++ check interval to 15 seconds and repeat the S3 tests. It might be that the delay in removing the filters overlaps with the next PS++ check interval (in your case only five seconds later) and thus the problem arises...

I don`t want to count the chickens before they're hatched - but the wake-up problem really could be solved by your solution with increasing the check interval! First test-runs with 25sec were working!!
I will test around a bit more (in future also with 1.2.5) - if an error is occuring again I will send (full!) logs.

...provide comprehensive logs (the whole zip-Archive)! It costs me lots of time to analyse your problem. So I will no longer try to help you if you are not willing to take my advice, since this is waste of time for both of us.

Sorry for not sending full logs - if I remember right in the first post there was written some time ago something like
"provide me with tv.log and mediaportal.log" - so I thought it is fully sufficient to attach just those two files.

In case an problem is coming up again I will attach full logs for sure.

Thanks a lot in advance!!