RR Doesn't Resume Music after Hibernate

**RoyN** · 06-24-2005, 12:53 AM

Hmm, I'll try tomorrow. what is the DISadvantage, if any, to adding hibernateaware=1?

**Wiredwrx** · 06-24-2005, 01:41 AM

Originally Posted by RoyN

Hmm, I'll try tomorrow. what is the DISadvantage, if any, to adding hibernateaware=1?

I think I added hibernateaware=true, or false, or whatever. It is in the thread somewhere.

Michael

**RoyN** · 06-24-2005, 01:45 AM

Yeah, yeah, that is well documented in this thread.. it disables RR's "awareness" of hibernation, I'm still, however, trying to understand what if any is the disadvantage to doing that...

**guino** · 06-24-2005, 02:34 AM

On hibernation, RR will close/open any ports it has opened, and stop music playback then resume it.. if hibernateaware=false is present, it will simply ignore the hibernation process and let the applications/windows handle it on their own. I am amazed that after so much talk of hibernation issues you have not yet tried it.

**RoyN** · 06-24-2005, 02:41 AM

Amazed you might be... I mentioned, however more than once that I would test as soon as I could get to my carpc, unfortunately I have been having a ton of problems on it... and my other computers dont have the issue, so nothing to test on them... that particulat unit that presents the bug will hopefully be exposed to the test tomorrow...

**RoyN** · 06-24-2005, 06:53 PM

I too confirm that hibernateaware=false fixes it for me

**RoyN** · 06-24-2005, 07:08 PM

Guino, now that I think more about this, what kind of ports are you openning and closing? Would they pose a problem if not opened/closed appropriately?

I could suggest 3 levels of hibernationawareness... 0 (ignore) 1 (close ports, etc, ignore music) 2 (as uhave now, stop music, start music)...

That way we can still benefit from the recovery from hibernation for ports and such, but wont have problems with music that doesnt start

**guino** · 06-24-2005, 11:03 PM

I'd go as far as to add that hibernate "level" support but there's no ground basis to assume that it's winamp and not the com port stuff that's messing up the resume.. the only reason why I close the com ports is because some serial devices may prevent the computer from hibernating if not closed. If hibernateaware=false works for you, then there's no benefit whatsoever in closing the serial ports on your system.. The ports RR closes are the GPS, Serial Sensor and XM -- Only if they're setup in RRConfig (doesn't control anything used in external apps).

**RoyN** · 06-25-2005, 04:16 AM

OK Guino, I'll post back if I have any issues...

For now, FD treats its own hibernation (in my case OEM GPS), I dont have any sensors to test, so hibernateaware=false is great for me!

I'll keep you posted, once again sorry for the delay in testing this stuff out...

Cheers!

PS: could you add a hibernateaware option in RRConfig whenever you have some time..

**rampage101** · 09-29-2005, 12:06 AM

Well, after just experiencing this myself. I've got some more details to add.

* Running winamp by itself and hibernating/resuming works fine. Which would lead me to believe it the front end (RR).
* ONRESUME CTRLLEFT doesn't help.
* My situation: I need to just move the mouse and everything is good.
* Using hiberateaware=false works for the audio, but my clock doesn't resume until I move my mouse.