home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Talk
Help to narrow down S3 Resume bug
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="craigparris1" data-source="post: 395883" data-attributes="member: 75254"><p>Hi guys,</p><p></p><p>Here's a bit more info on my personal experiences with these standby/resume issues - particularly now that I've had a perfectly working system for about two weeks. Every resume from standby, MediaPortal has worked as expected - no remote control problems, no "TV service is not started" problems. It's great!</p><p></p><p>Here's what I've done of late: as I reported earlier in this thread, I had a small .Net app which I'd written myself to try and trap all the suspends/resumes properly and do the appropriate actions .... but, the problem was, even that app wasn't always getting the power event notification from the OS. I put some extra code into the app, as a backup measure, to basically use a file on the local C: drive to try and identify if a suspend or resume had happened, but hadn't been triggered properly by the power event notification. Essentially, when a suspend happens properly, a file gets created, then when a resume happens properly the file gets deleted. I've then got a timer as well which is looking for this file - if it finds it and the date/time of the file is more than 15 minutes, it's pretty safe to assume that the last resume wasn't notified correctly to the .Net app, so it just does the resume routine via the timer.</p><p></p><p>So far, this seems to be working fine (for about two weeks or so). Previously, I was pretty much having resume problems every second day.</p><p></p><p>I've also implemented this fix: <a href="https://forum.team-mediaportal.com/newcomers-forum-240/windows-defender-breaks-localhost-56258/" target="_blank">Windows Defender breaks localhost</a>, which seems to have resolved the issue where TV streaming wouldn't start sometimes after resume (saying the TV-server was not available). I wasn't actually using Windows Defender - but hey, if it fixes the problem then that's all that matters!</p><p></p><p>To be honest, jameson_uk, this probably doesn't actually help you much in your investigations, because at the end of the day I haven't actually solved the problem, I've just got a working "workaround" ...... but that suits me just fine for now!</p><p></p><p>Cheers,</p><p>Craig</p></blockquote><p></p>
[QUOTE="craigparris1, post: 395883, member: 75254"] Hi guys, Here's a bit more info on my personal experiences with these standby/resume issues - particularly now that I've had a perfectly working system for about two weeks. Every resume from standby, MediaPortal has worked as expected - no remote control problems, no "TV service is not started" problems. It's great! Here's what I've done of late: as I reported earlier in this thread, I had a small .Net app which I'd written myself to try and trap all the suspends/resumes properly and do the appropriate actions .... but, the problem was, even that app wasn't always getting the power event notification from the OS. I put some extra code into the app, as a backup measure, to basically use a file on the local C: drive to try and identify if a suspend or resume had happened, but hadn't been triggered properly by the power event notification. Essentially, when a suspend happens properly, a file gets created, then when a resume happens properly the file gets deleted. I've then got a timer as well which is looking for this file - if it finds it and the date/time of the file is more than 15 minutes, it's pretty safe to assume that the last resume wasn't notified correctly to the .Net app, so it just does the resume routine via the timer. So far, this seems to be working fine (for about two weeks or so). Previously, I was pretty much having resume problems every second day. I've also implemented this fix: [URL="https://forum.team-mediaportal.com/newcomers-forum-240/windows-defender-breaks-localhost-56258/"]Windows Defender breaks localhost[/URL], which seems to have resolved the issue where TV streaming wouldn't start sometimes after resume (saying the TV-server was not available). I wasn't actually using Windows Defender - but hey, if it fixes the problem then that's all that matters! To be honest, jameson_uk, this probably doesn't actually help you much in your investigations, because at the end of the day I haven't actually solved the problem, I've just got a working "workaround" ...... but that suits me just fine for now! Cheers, Craig [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Help to narrow down S3 Resume bug
Contact us
RSS
Top
Bottom