Remote fails to bring XBMC out of standby after upgrade to OE 3.2

[alen0038]

Problem after upgrading from 3.06. Fusion build - Asrock E350M1, using Asrock remote. In XBMC I use "Dim" screensaver, 10 min and "Put display to sleep" (30min). After display is put to sleep, my Asrock IR remote does not "wake" the XBMC anymore. I can connect via SSH, everything works ok. Web interface also works, inviting remote and pressing any key gets back to XBMC, after that remote works fine. Running IRW via SSH - the key presses are recognized. Every keypress is somehow "buffered", and after waking XBMC via web interface (and disable-ing power-saving), all the key presses are played back. Interesting timestamps in attached XBMC log:

• 21:39:38 - DPMS power-saving enabled (no reaction for pressed keys on the remote)
• 21:45:19 - pressed a key via webserver
• 21:45:25 - DPMS power-saving disabled, all remote keypresses made during power-save are replayed.

Logs:

During standby: cat /var/log/messages | paste http://sprunge.us/JNTN

cat /storage/.xbmc/temp/xbmc.log | paste http://sprunge.us/gBZH

lsmod http://sprunge.us/jfbV

dmesg http://sprunge.us/iTgT

lspci -vvv http://sprunge.us/QRMb

cat /proc/bus/input/devices | paste http://sprunge.us/WhOF

cat /proc/acpi/wakeup http://sprunge.us/gRII

cat /var/log/Xorg.0.0.log http://sprunge.us/EQbN

After standby: OpenELEC:~ # cat /var/log/Xorg.0.0.log | paste http://sprunge.us/hgIX

OpenELEC:~ # cat /proc/acpi/wakeup | paste http://sprunge.us/gQAb

OpenELEC:~ # cat /storage/.xbmc/temp/xbmc.log | paste http://sprunge.us/WJHi

OpenELEC:~ # cat /var/log/messages | paste http://sprunge.us/MXOF

[bleader]

I apparently have the same issue, maybe some differences, I tried to plug a keyboard and was able to wake it up.

Same update from 3.0.6 to 3.2, I also am running an Asrock E350M1 but I was on generic build before the update, I guess that should still be the case then.

[ardentmusician]

I have the same issue, except that I cannot get it to wake with the Android app. I have to either SSH into it and reboot it, or force it down with the power button and back up. I am running a Fusion build on a Zotac 'book'.

A fix for this would be appreciated.

http://www.openelec.tv/forum/67-display/66911-cannot-resume-display-from-sleep-with-3-1-7

[bleader]

Same here, yatse (alternative android app) cannot wake it up, remote in maraschino doesn't work either. but a real keyboard worked fine to avoid reboot.

[jenkins101]

This is probably a xbmc issue please report it to them too...

could be a driver issue please add links to a logs zip from your systems

[ardentmusician]

What drivers were updated by the update to 3.2.0?

[jenkins101]

from what?

[bleader]

updated to 3.2.1, seems fixed for me.

[alen0038]

Upgraded to 3.2.3., also no problems. Thanks to the devs, problem got fixed :-)