Mac mini doesn't connect back with hdtv

Discussion in 'Mac mini' started by detz, Dec 22, 2013.

  1. detz macrumors 65816

    Jun 29, 2007
    I have my mini hooked up to my tv so I can watch movies and it's becoming an issue that when I switch back to my mini from another input it says no input and often requires a reboot to get it to come back. All the energy saving stuff is off, it's as iff it can't find the monitor when it comes back because if I connect via remote share there are no displays.

    Any thoughts?
  2. blanka macrumors 68000

    Jul 30, 2012
    What is your display connection cable?
    Did you try hitting the power button twice (on the mini)?
  3. detz thread starter macrumors 65816

    Jun 29, 2007

    What does hitting it twice do?
  4. blanka macrumors 68000

    Jul 30, 2012
    It puts the mac to sleep, then wakes it back up.
    For me it fixes an accidental blue screen. It feels like the display connection is re-negotiated when waking from sleep.
  5. edwardthefifth macrumors newbie

    Aug 11, 2004
    This seems to be a Mavericks problem

    I started having the exact same issue after installing Mavericks, and if you search the internet, it seems to be rather common.

    People complain about the issue when the Mini wakes up from sleep, but like the OP, I have my Mini set to not go to sleep.

    However, after the Mini is idle for a while, all of the sudden the HDMI output doesn't work, so the Mini doesn't recognize either my stereo or TV (I feed HDMI out from the mini to my receiver then to my TV).

    I can still control the mini via my Macbook Air via Screen Sharing, and everything runs fine except for the sound and video. For instance, if I open iTunes, the music will play. It simply plays through the Mini's internal speaker because as the OP said, anything connected to HDMI is not recognized.

    I've yet to find a solution. It's been posted that the 10.8.5 update fixed this issue, but it didn't do so for me.
  6. iPhil macrumors 68040


    I have energy saving ON -- my '11 mini direct HDMI connection - I have computer/monitor sleep after 75 mins or so of inactive....

    Then after that time I just double tap on spacebar to wake up from "blue screen - no input" after the double tap action = I get log-in screen ...

    The Blue screen even happens under Lion / ML = Just a quick double tap on spacebar solves the issue for me ...
  7. edwardthefifth macrumors newbie

    Aug 11, 2004
    In all this time, I've still been unable to solve this issue on my end, but I might have found a solution. The problem is that the solution costs almost $100, so before I spend the money, I thought I'd reach out and see if anyone else has any other ideas.

    My problem is not that the computer doesn't wake from sleep correctly. I keep my mini running full time. I connect my mini to my receiver via HDMI and then my receiver outputs HDMI to the TV. Once I switch inputs on the receiver and the mini is not the active input on the receiver, the mini and the receiver are usually unable to reconnect when I later do make the mini the input unless I restart the computer.

    This site ( sounds like it explains my problem exactly:

    "The apparent problems of an HTPC not showing a picture or sound or even sometimes both can be caused by an HDMI handshake issue. In a nutshell, it basically means that the HTPC does not connect or loses its video or audio connection with the TV and entertainment system. It presents itself with a blank screen, a “no video signal” message from the TV, or static/snow; this can happen with or without sound if you have it connected it to your AV Receiver. It even happens when you have a box that is “always on” but is more common coming out of sleep mode"

    The site also has a fairly expensive solution:

    "Get an HDMI Detective Plus at I lied before when I said there wasn’t a fix. There is one, and it’s drop-dead simple – the problem is that it costs $85. The HDMI Detective works by cloning the EDID of the TV and AVR when they are powered on and broadcasting it even when they aren’t. So to the GPU, or any connected CE device (the HDMI Detective is a common “goto” device for EDID issues in the CI market), always receives the same, clean, EDID."

    I expect this HDMI Detective Plus to do the trick, but might anyone have any last tips I can try before I spend the money?



Share This Page