[Bug Fix] Fail the first remote control input after standby/hibernation

[majstang]

Soundgraph, do you know the postponed:
[Bug Fix] Fail the first remote control input after standby/hibernation.
was sorted when you fixed the:
From Version History: (7) [Bug Fix] After waking up from S3/S4, it takes long time for iMON to start to work. And after Keyboard or Mouse action iMON starts to work.
Way to go SG, even if it wasnt intended! Those two bugs were interrelated ;)
Many thanks to you ShIvADeSt! You ROCK! Without your help it would have taken a lot longer for SG to fix this bug. You pretty much gave them the complete solution.
Puh, now i can rest my case and leave this forum for good or at least a very long time :) Now its time to enjoy my fully functional HTPC :D

Regards Majstang

[Alcahest]

Strange, the "Fail the first remote control input after standby/hibernation" bug is still there for me.

Using _only_ the Power button on the remote (that I set up to act as Standby in iMON):

PC is on, I press the button one time. PC goes to sleep.
From PC in standby, I press the button 1 time, it wakes up the PC.

From there, if I press the button again, iMON will *NOT* react on the first input (if it worked, it should put the pc back to sleep again)...

[majstang]

Strange, the "Fail the first remote control input after standby/hibernation" bug is still there for me.

Using _only_ the Power button on the remote (that I set up to act as Standby in iMON):

PC is on, I press the button one time. PC goes to sleep.
From PC in standby, I press the button 1 time, it wakes up the PC.

From there, if I press the button again, iMON will *NOT* react on the first input (if it worked, it should put the pc back to sleep again)...

Hmm...yes, that is wierd! I do not use standby, but testing the exact same actions you did, but with hibernation instead gives a positive result, at least for me. Every other first buttoncommand works like a charm when resuming from hibernation. Would be intresting to know your results with hibernation as well. Cant test stanby my self cuz it doesnt work since i installed my watercooling system.

[Alcahest]

Ok, I think i found out.

In iMON Manager, at:
Settings > Windows Commands > Power Management Command.

If i set:
Power Button (PC Case) as the Power button on the remote, and in XP Power settings I set the Power button to act as standby, then the bug is NOT there, iMON reacts instantly to first input after resume from standby/hibernate.

However If i set:
"System Standby" or "Hibernate" as the Power button (on remote), the bug IS there.

I prefer having the Power Button on the PC case switch off the PC completely and having the Power buton on the remote put the PC to standby... so for me the bug is still there.

Is that coherent with your findings?

[majstang]

No, for me it works regardless of setting for the powerbutton in Windows Power Management. The RC Powerbutton is set to hibernate. Makes me wonder if it could be some issue with your case powerbutton maybe?

[Alcahest]

Indeed it's odd.
I'm on XP SP3 if that makes any difference. I don't think there's any issue with my case Power Button.

I also run OS services and apps to a minimum so don't see what could interfere.

But, yeah for me the bug is NOT solved. I hope Soundgraph can take a look at it in further details in the future.
Later,

Alcahest

[majstang]

I have XP SP2 and i also installed a Microsoft hibernationfix a long time ago named KB909095, but would be very surprised if these have any effect on the issue at hand. Hopefully the SG guys could shed some light over this. They are after all the masters of the sourcecode and that gives them a whole another insight in things. Good luck!

Majstang

[ShIvADeSt]

I tested resumin after sleep mode - and it worked fine. Simply no need to use my util coz iMon awakes immediatly after system start. I'll test some timesandif there were faults- I'll post.

[majstang]

Hi ShIvADeSt!

Thanks for making things clear for the Soundgrap guys. Your util made the difference for em to crack this. However it is somewhat unclear what you did test in your last post. You say "I tested resumin after sleep mode - and it worked fine. Simply no need to use my util coz iMon awakes immediatly after system start". Do you refering to the [Bug] Fail the first remote control input after standby/hibernation or do you refering to [Bug was fixed in v7.63.0831] After waking up from S3/S4, it takes long time for iMON to start to work. And after Keyboard or Mouse action iMON starts to work?

Maybe you tested what was failing for Alcahest but working for me...this was:
Setting RC Powerbutton in iMON to hibernate/standby and setting Power Button on the PC case to switch off the HTPC completely (in Windows Power Management). Then hibernate/standby the HTPC and then wake it up (resume). When HTPC is fully woken up see what happens if you standby/hibernate it again. For me it did hibernate for Alcahest nothing happened. The conclusion was the first buttonpress/input fails after resuming from hibernation/standby for Alcahest but working for me. This is really odd and i cant understand why. Maybe you could, with your programming skills, make more sence of the situation?

[ShIvADeSt]

Yes here wassome misunderstood both from me and You.
First - I did wrong when pos in this topic, coz this topicnot for resume after standby. sorry, my mistake.
Second - Pls read To-Do list. The subject is not fixed yet. They planned it on 30 september - Read more carefully changelog and to-do list.
After all it well be clearly to You - the Subj is not fixed, but will be soon.

To make some fixes from my side. I dont know mechanism which use iMonto enumerate all devices and I dont really good programm devices. My hobby is WinAPI and all from this. Working with devices is more hard coz need to know thin things about em.

[majstang]

Second - Pls read To-Do list. The subject is not fixed yet. They planned it on 30 september - Read more carefully changelog and to-do list.
After all it well be clearly to You - the Subj is not fixed, but will be soon.

Yes, i know this as i wrote in my starting post in this thread! That is somewhat why i started this thread, cuz when SG fixed your bug: From Version History: (7) [Bug Fix] After waking up from S3/S4, it takes long time for iMON to start to work. And after Keyboard or Mouse action iMON starts to work.
They also fixed mine despite they say it is postponed til Sep 30.
I do not have [Bug] Fail the first remote control input after standby/hibernation any longer. Alcahest does still have the bug with certain settings in iMON manager and we can not understand why. My system works perfect now and my thought was it had something to do with your Utility and the code in it. SG themselves said, when they saw your code, they had overlooked something in thier sourcecode. I bet this is a WinAPI based issue otherwise it wouldnt be working for me right now. But surley the reason it does not fully work for Alcahest may very well be the fact we have different iMON hardware and FW-version (devices).

[ShIvADeSt]

Yes, i know this as i wrote in my starting post in this thread! That is somewhat why i started this thread, cuz when SG fixed your bug: From Version History: (7) [Bug Fix] After waking up from S3/S4, it takes long time for iMON to start to work. And after Keyboard or Mouse action iMON starts to work.
They also fixed mine despite they say it is postponed til Sep 30.
I do not have [Bug] Fail the first remote control input after standby/hibernation any longer. Alcahest does still have the bug with certain settings in iMON manager and we can not understand why. My system works perfect now and my thought was it had something to do with your Utility and the code in it. SG themselves said, when they saw your code, they had overlooked something in thier sourcecode. I bet this is a WinAPI based issue otherwise it wouldnt be working for me right now. But surley the reason it does not fully work for Alcahest may very well be the fact we have different iMON hardware and FW-version (devices).
May be so. I dont have issue with first input fail too. And shortly I dont care about FIRST input ^^ I can press button twice and get same result as once.

[johnny.hur]

Dear All,

[Bug Fix] Fail the first remote control input after standby/hibernation.
[Bug Fix] After waking up from S3/S4, it takes long time for iMON to start to work. And after Keyboard or Mouse action iMON starts to work.
These issues are different each other.
“Fail the first remote control input after standby/hibernation.” happens after waking up completely from S3/S4.
Some users still have this problem and it is not fixed yet.

Alcahest// Please wait for a while till we fix it.

Regards,
Johnny Hur