Bug Remote Control does not work after returning from standby/hibernation

[majstang]

Hi Soundgraph!
Nice to see something finally happens with the forum and maybe even your lack of engagement in your customers. The hope rises you guys could turn this around and deliver your promises. Keep up the good intensions. However the "To do list" is a really dark read for me. Despite three reminders about the bug "Remote Control does not work after returning from standby/hibernation" it is still not up there on the list. Why? This is the fourth reminder.
Keep in mind that much of your customers htpc experiences are dependent on your software and we are forced to live with your shortcomings every day and will hardly not give up our claims about you fixing annoying bugs.

This is how you reproduce the bug!

1. Issue with the Remote Control after returning from standby
When setting "[MCE remote] Power" button to act as "System Standby or Hibernation" in iMON Manager, there is a bug :
when returning from standby/hibernation, the first button pressed on the remote will not register (does nothing at all), only the 2nd press and following presses will work.
How to reproduce :
- Assign "[MCE remote] Power" button to "System Standby" in iMON Manager.
- When PC is in standby, press the Power button on the remote to wake up the PC.
- Now press any button on the remote 1 time (volume, anything) => nothing happens. (bug!)
- The 2nd time a button is pressed, the remote starts working again..
It seems that after returning from Standby, iMON Manager isn't ready to accept the very first remote command

[slash.kim]

Dear majstang,

I've been developing iMON Manager and iMEDIAN HD in SoundGraph. In order to serve better technical support, some SoundGraph developers including me will contact to you directly through this new User Forum.

For the issue you reported we already checked it in our QA team.
Though it looks iMON Manager can not accept the very first remote command, it may not true. After resume from standby/hibernation, iMON Manager need some time to initialize itself to communicate with driver. Before this initialization, the remote command will not accept. If the very first press of button on remote is taken right after resuming from standby, iMON Manager may not be initialized yet at that time.
Please give iMON Manager more time after resuming from standby/hibernation.

If you think it's not the initialization-timing issue, please let us know more in detail like iMON model including firmware version, system specification and OS information you are running.

Thanks

[majstang]

Hello slash.kim!
Thanks for your reply! No, this issue is not due to some timing problem of any kind. The issue seem to be an initializationprocess that is not properly finished. The second buttonpress kickstarts the driver and everything is back to normal after that.
The first buttonpress from remote does not work regardless the time you give the iMON Manager to reinitialize itself after waking up from standby/hibernation. The first buttonpress does not work 1 second after wake-up and it does not work after infinite amount of time after the last wake-up. The problem does not exist if you reboot PC each and every time, ONLY when using stand-by or hibernation of HTPC.
The issue persists regardless of iMON version. I have tried every version from 7.2 and forward. Im running Windows XP. The user who first reported about this bug (Alcahest) is running XP as well. I have the iMON inside.
Regarding you wanting firmware version i dont know how to get that. Theres no info on that or how to retrieve it. Regarding the system information you want to know i dont know what your after either? Please specify what is important for you to know to crack this case and i will get it for you.

Regards
majstang


.

[Alcahest]

Hi majstang, slash.kim,
Yes I reported the issue originally.
I can confirm it's not a timing issue. Regardless of how long you wait, the first button press will never do anything.

I have iMON OEM LCD on Antec case, it was replaced already for another problem (interference with other remotes).

Now, the hardware I have is 0xa1

majstang, you can see the firmware version at Option > Version update in iMON Manager.

Let me know if you need more infos.
See you,

Alcahest

[majstang]

Ah, thank you very much Alcahest! I completly missed that :o
Checking the iMON firmwareversion gives: 0x28.
Systemspecs:
Windows XP sp2 32-bit
Zalman HD160XT Plus (the built-in iMON solution didnt work as supposed to so i was forced to exchange that to an iMON inside)
Intel Core2 Quad CPU Q6600 2,4 Ghz
2 GB RAM
ATI Radeon HD3870
Asus P5E3 motherboard.

slash.kim let me know if you need more info.

Regards
Majstang

[slash.kim]

Dear majstang and Alcahest,

OK, then it looks somewhat different problem compared to the one we found on our side. If it is not the timing issue after standby or hibernation, we need check it more.

We'll add this issue to our To Do List and update in future release.

Dear Alcahest,
the problem is continuing on your system? If it is, please let me know the the specifications of your system.

Thanks and best regards,
slash.kim

[majstang]

Thanks slash.kim!

Would be great if you could revise the To Do List as soon as possible. Then maybe (if you fix this issue) there is some hope for Soundgraph after all.
The new forum and the new customer service is REALLY promising. From here things can only get better. Keep up the good work.

Regards
Majstang

[dk.jung]

Dear majstang,

After we make a new Forums, we set our working process as like this. Once we notice the issue and we will try to make duplicate this issue at our test lab. During our trying to duplicate, we will continuously try to communicate on the forums. After we make success to duplicate the issue at our test lab, then we notice this to the thread and post this issue to the to do list with a schedule according to its difficulty.

As you might know, if we fail to duplicate the issue at our test lab, it would be useless on the to do list with schedule and we might not keep our promise. So please be understood this situation and give us more information which can solve your issue as soon as possible.

Thanks and regards...

[Alcahest]

slash.kim, my system specs are as follows:

Windows XP SP3 w/ all updates.
Antec Fusion v2 (Black) with iMON OEM LCD module.
Dual Core E2180 @ 2.66 Ghz
Geforce 8500GT fanless+HDMI
Asus P5K-VM w/ bios 1001

Let me know if any info is missing.
See you,

Alcahest

[majstang]

+Hello!

Thanks for the information dk.jung! I don't think you guys should have any problems duplicating this issue. Im sure a lot of people besides alcahest and me have the same issue. Would be great if somebody else could speak up if they suffer from the same issue. This problem is not OS specific either, because i just installed Vista 32-bit only for testing this issue and the result was the same. The first buttonpress did not work after waking up system from hibernation, regardless of time given for iMON to reinitialize itself. The second buttonpress did work...exactly like in Windows XP. This issue seem to be a classical stand-by/hibernation problem so many softwares suffered from quite many years ago. In that sence they didn't reinitializing properly after stand-by/hibernation. I have encounter many softwares with the same problem, but in most cases they stopped working all together after waking up from stand-by/hibernation. This is some years ago when stand-by/hibernation wasn't widely used or non-functioning on most systems.
It's time you guys update/rebuild your driver, cuz its really old. Most of the files is from 2003-2004, no wonder there's problems.

Regards
Majstang

[slash.kim]

slash.kim, my system specs are as follows:

Windows XP SP3 w/ all updates.
Antec Fusion v2 (Black) with iMON OEM LCD module.
Dual Core E2180 @ 2.66 Ghz
Geforce 8500GT fanless+HDMI
Asus P5K-VM w/ bios 1001

Let me know if any info is missing.
See you,

Alcahest

Dear Alcahest,

Thank you for the information.
If we'd like to get more information to reproduce it, I'll ask you again.

Thanks,
slash.kim

[slash.kim]

+Hello!

Thanks for the information dk.jung! I don't think you guys should have any problems duplicating this issue. Im sure a lot of people besides alcahest and me have the same issue. Would be great if somebody else could speak up if they suffer from the same issue. This problem is not OS specific either, because i just installed Vista 32-bit only for testing this issue and the result was the same. The first buttonpress did not work after waking up system from hibernation, regardless of time given for iMON to reinitialize itself. The second buttonpress did work...exactly like in Windows XP. This issue seem to be a classical stand-by/hibernation problem so many softwares suffered from quite many years ago. In that sence they didn't reinitializing properly after stand-by/hibernation. I have encounter many softwares with the same problem, but in most cases they stopped working all together after waking up from stand-by/hibernation. This is some years ago when stand-by/hibernation wasn't widely used or non-functioning on most systems.
It's time you guys update/rebuild your driver, cuz its really old. Most of the files is from 2003-2004, no wonder there's problems.

Regards
Majstang

Dear Majstang,

Thank you for testing on Vista. As you said, it looks non-OS specific problem. However, there's a possibility that it is a system-specific one, because much many users might saying about this if this problem occurs on all systems.

The firmware 0x28(yours) and 0xa1(Alcahest's) shows the "SG Remote Control Device" driver is running as iMON device driver. This driver was certified by WHQL of Microsoft and the driver files may not have a problem even it was made in several years before.

And could you let me know one more thing; what's the color of iMON Indicator on Desktop when before/after the first pressing after resuming from standby/hibernation?

Scott// Please check this issue again. If needed, we purchase the same motherboard.

Dear all users, it would be very helpful to sort out this problem if other users having the same problem post his/her system's specification and the firmware version of iMON here.

Thanks and best regards,
slash.kim

[majstang]

Hello slash.kim!

Thanks for your reply! Maybe many users have this issue but does not see it as a big deal. For me however it is i big deal because this little problem skrews with my macros in my homeautomatization system and it's driving me mad. A sertain step in the macro fails each and every time, forcing me to make even more complicated macros to deal with the iMON issue. Well, it's a hassle for sure.

Back to your question:
what's the color of iMON Indicator on Desktop when before/after the first pressing after resuming from standby/hibernation?

Windows XP: It's blue when system is resumed from hibernation (before the first press) and blue after the first press. No indicator reaction when doing this first press.
Windows Vista: It's grey when system is resumed from hibernation (before the first press) and grey after the first press. No indicator reaction when doing this first press.

Only time the indicator turns yellow is when going in to hibernation, but this has no bearing on the problem.

Regards
majstang

[slash.kim]

Dear majstang,

Thanks for your help.
Our test team is now trying to reproduce the problem. If we could reproduce it, we'll be able to sort out this problem.

Thanks and best regards,
slash.kim

[majstang]

Hello slash.kim!

One last question before waiting for your test results. Do Soundgraph use other drivers besides "SG Remote Control Device" for the hardware? If so maybe there is a possibility to use that instead?

Update: Did check the To Do List and saw this issue was up there and to be fixed late Aug. This means you guys managed to reproduce our problem. Great work guys! This is how a forum and customer service should be runned. Keep it up!
Soundgraph is back and it is nice :D

Regards
majstang

[slash.kim]

Dear majstang,

Thank you for more information.

Finally, our test team succeeded to reproduce the problem and we'll fix this bug in future release as described in To Do List.

Thanks and best regards,
slash.kim