No audio after wake up, until I go into Settings

DoNotEatDesiccant · June 18, 2016 at 11:27 PM

Problem: After waking my system from suspend, there is no audio output via HDMI until I enter Settings

100% consistent Repro Steps:
1. System is working fine (plays audio/video no problem)
2. Suspend system
3. Wake up system
4. There is no audio output when navigating through menus, or playing videos
5. Go to System > Settings > System menu
6. Audio is now working, and will continue to work until the next suspend

LibreELEC: 7.0.1
Hardware: Dell Studio 1737 laptop. GPU is AMD RV635. Audio/video are output via HDMI cable, to a projector.
In "Audio output" settings, I have the Audio output device set to "ALSA: HDA ATI, HDMI"

Debug Log (hope I got this right): Y92VVMeh

Same issue occurred in OpenELEC 7.0 beta 3. Prior to that, it was not happening in Kodibuntu.

DoNotEatDesiccant · July 18, 2016 at 12:55 AM

I tried adding a wakeup script, as per the Kodi wiki. See the section titled "No Audio and/or corrupted video on Wakeup from Suspend" (Chromebox - Official Kodi Wiki)

That took care of the audio issue, but now the video resolution is messed up on wake instead (640x480, despite it saying 1280x800 in the Settings menu). So that's even worse.

Seriously, this is a 100% reproducible issue. Nobody can help?

**lrusak** · July 18, 2016 at 7:21 AM Official Post

try this

system --> system --> audio output --> keep output device allive --> always

Settings/System - Official Kodi Wiki

strra · August 5, 2016 at 5:31 AM

I'm having the exact same issue. Has anyone figured out a fix for this yet? lrusak's suggestion didn't work, unfortunately.

sakos · November 6, 2016 at 12:32 PM

UP! Same problem.
The chromcast workaround does nothing.

FeepingCreature · November 22, 2016 at 5:19 PM

The Chromebox workaround works here.

If you're not using a Chromebox, you have to adjust the monitor output name in the script.

Use "xrandr" to list the available outputs, then change the --output parameter in the script to match your device. For me it was HDMI-0 instead of HDMI1.

sakos · November 29, 2016 at 5:54 PM

Quote from FeepingCreature

The Chromebox workaround works here.

If you're not using a Chromebox, you have to adjust the monitor output name in the script.

Use "xrandr" to list the available outputs, then change the --output parameter in the script to match your device. For me it was HDMI-0 instead of HDMI1.

The Chromebox way did not work for me.
This is my solution.

DoNotEatDesiccant · February 18, 2017 at 9:33 PM

I gave up and went back to Kodibuntu for the last 8 months. However, the recent update to Kodi 17 completely messed up my Kodibuntu install. I'm getting weird scrolling tearing on the interface. Seems like the fix is to use the closed-source AMD drivers, but the video card is too old to be supported. That, plus Kodibuntu no longer being officially suppoted, means... back to LibreELEC. Which means back to the "no audio on wake" issue.

I'm running v7.95.3 BETA, because I want that Kodi v17 goodness. I decided, what the heck, let's try this stuff out again. sakos's suggestion just caused my entire display to refresh every time I navigated to a new menu item. So, back to the Chromebox solution. Like before, it resolved the audio issue, but this time there was an even worse video issue. The interface was all while and aqua, impossible to make anything out. This time, I decided to try to understand the script.

Looks like xrandr is shutting off HDMI video and audio, then turning HDMI video and audio back on. Well, that's silly. Why do I need to turn off HDMI audio and video, if the machine is going to sleep anyway? I commented out that first xrandr line. Result: When waking up the laptop, audio is working, but video is set to a lower resolution. Hmm. Why do I need to turn HDMI video back on with xrandr? Surely that happens automatically on wake? So I took out the "--auto" portion of the script. Result: on wake, audio is working and video is at the same resolution it was when I put it to sleep!

Here's the script I'm using, modified from the chromebox solution:

Code

s#!/bin/sh
case $1 in
   pre)
     #xrandr --output HDMI-0 --off --set "audio" "off";
     ;;
   post)
     xrandr --output HDMI-0 --set "audio" "on";
     ;;
esac

I could probably just delete that first xrandr line instead of commenting it out, but I don't know enough about linux to say for sure. Commenting out felt safer. Hopefully this helps others having this same problem.

Note that I'm using HDMI-0 instead of HDMI1. I got that by running xrandr with no arguments, to see what my device was listed as.

sakos · February 19, 2017 at 12:30 PM

Quote from DoNotEatDesiccant

I wonder why your display is refreshed every time, as my solution runs only once when the PC wakes up.
Anyway, I like your suggested solution. It works fine on my HTPC. In my case it is enough to run the "post" command.
Thanks!

kszabo · February 26, 2017 at 9:13 PM

My advice is this xyz.power script in /storage/.config/sleep.d

Bash

#!/bin/sh
case "$1" in
pre)
;;
post)
xrandr --output HDMI-0 --set "audio" "on"
;;
esac