No HDMI signal after idle

pigos

New member
I own Neo G41V-4 from a couple of months and it is connected to a TV set via HDMI.
When I switch the TV source out of the G41V-4, for example to see the TV and then I come back to the HDMI port to access the G41V I got NO signal.
The only fix is to unplug the HDMI cable from the G41V and plug back again. This works until the next source switch when I got a black screen again.
Before the G41V on the same HDMI was installed a NEO Z64 and that was working perfectly, leaving the signal on also after days of disconnection.
Any hint or ideas?
Many thanks and regards
 
I have the same problem (Samsung TV 43RU7105)
Sometimes (not always) i have no image (when i turn off my TV (and back again) or change hdmi input).
I think the problem is the same when the device is running or in sleep mode.

Fix :
Maybe a BIOS update (but at the moment there is no BIOS update).

Note:
I already changed some BIOS settings with no result (default BIOS included).
 
Last edited:
Have you went to the 'Settings' > 'System' > 'Power & sleep', and make the screen 'Never' turn off, the PC 'Never' goes to sleep?
Please let me know then.
 
Hi Martin,
I set those two on "never" as one of the first things during G41V setup.
What I did not change are the "Advanced power settings" that are set on "balanced" from the beginning. Anyway the display setting there is set on "Never turn off"
Thanks
 
My power plan is also "Balanced (recommended)".
I set those two options to 'Never', and up until now, I tried to test this problem several times, but I can't replicate it on my end.
In order to exclude that the problem is caused by the settings of Windows OS, could you please try to manually re-install the Windows OS without changing BIOS options?
Just to check if the same problem still persist.
 
My power plan is also "Balanced (recommended)".
I set those two options to 'Never', and up until now, I tried to test this problem several times, but I can't replicate it on my end.
In order to exclude that the problem is caused by the settings of Windows OS, could you please try to manually re-install the Windows OS without changing BIOS options?
Just to check if the same problem still persist.
I don't think the problem is Windows OS.
One of the reasons is that i think that happened before without changing anything on the BIOS.

I already re-installed windows OS (with PXE, external USB) to other releases (latest is 20H2 from Microsoft but i tested Minix releases), i also used windows update and i already changed BIOS settings (and used default BIOS settings).

Saying that, the problem persists (not always).

I think the problem is BIOS but i am not sure.
 
Last edited:
My Windows version is 1903 (OS Build 18362.1139), and I have not yet replicated this problem.
I will test version 20H2 later.
 
My Windows version is 1903 (OS Build 18362.1139), and I have not yet replicated this problem.
I will test version 20H2 later.
I think the problem is :
-When connected to a 4k TV (Mine is samsung 43RU7105) (and turn the TV off or switch hdmi input).
(If there is a switch in the TV resolution)

I have a second G41V-4 connected to a LG32LF5800 TV (1080p) and i never experienced that problem. (I need to say that i rarely watch TV with this LG (TV source, SD resolution) and if i ever changed to TV source i never experienced that isse.
Are you testing with a 4k TV?

@pigos
Can you tell us which TV you have? (Brand and model )
It is a 4k TV?
 
Last edited:
Hi, I'm having the same issue with HDMI went connected to my Samsung 4K TV and I switch from PC to TV I loose the picture.
I have to restart the MINIX in order to get the picture back on the TV via HDMI. I checked and changed cable same no changes.
Any suggestions.

Thank You
 
First post and unfortunately another post that echoes the above problems. Samsung QLED 4K series 6.

It's almost certainly a Samsung (or other TV OEM) issue - perhaps an unchanging image convinces the TV that the attached device is not functioning or even powered off. The 'green' or other protective settings on many consumer devices may be well-intended but they can cause headaches also. Protecting people from themselves may save the OEMs some support calls in some cases but obviously such measures can unintentionally create other problems.

HDMI input 4 has a game controller icon - I moved from HDMI1 to HDMI4 thinking its behavior might differ (always on) but there has been no change.

It's a play in four or five acts to turn the TV on and get Minix to be recognized again. Rebooting the Minix isn't a guarantee of success - power must usually be cycled. Even though the boot process is relatively quick the TV thinks the port is empty and displays a 'no source detected' message. I have a remote desktop app installed on Minix/Windows 10 that allows control, reboot, shut down etc from a tablet or a phone (or another computer) but that is obviously an additional layer of complexity.

The most surefire method is to disconnect/reconnect HDMI but that causes the Samsung TV to start from scratch in detecting and identifying the device. Time-consuming, repetitive and defeats the purpose.

When I first set up and configured the Minix I used a standard computer monitor and, unsurprisingly, had no issues with signal cutoff especially as my first task is usually to disable any and all power-saving and/or sleep functions, including USB power-saving and any other devices/ports from within device manager. In other words, the monitor would display the Minix image for 2 minutes, 2 hrs or 24 hrs or beyond.

I have an HDMI splitter sitting around doing nothing - for experimental purpose I may place it between the Minix and the Samsung and see if it might prevent sleep or disconnect or idle or whatever term you like.

EDIT #1: I was mentally prepared to return the Samsung for an LG or other brand but I see that LG owners have a similar issue.

EDIT #2: Intel Graphics 600 control panel has no setting to modify such as sleep, keep awake, prevent power-down etc.

EDIT #3: I had an Android-based Minix NEO X8-H Plus model connected to a different Samsung TV for about 2-3 years. Never had a single problem similar to this even with screen dim or power save enabled. I may do some mix-n-match with the Android NEO and the Windows NEO to various TVs and report back.

EDIT #4: Although it sounds crazy/illogical some people troubleshooting video/monitor issues have tried switching HDMI cables. Supposedly the cables all do the same job but...

EDIT #5: I have noticed that Windows regards the Samsung TV as a 'Standard Non-PNP (Plug N Play) Monitor.' The generic Windows driver version dates from 2006 (!) and there are no user-changeable settings. I've done searches for Samsung drivers but have yet to find anything and I'm not sure they exist.

EDIT #6: Although Samsung does not list/offer Windows drivers for its TVs, it obviously offers drivers for its computer monitors. On a try-anything-once hunch, I downloaded and installed a driver for a Smart Monitor (chosen mostly at random). Oddly, the installation dialogue was in Korean but I got through it. Now my monitor is listed as the Samsung model. Various screenshots attached. My Minix picture through the Samsung TV is clear and normal as it was before although it does list itself as SDR (standard dynamic range). Possible issue but will deal with it later. This change may not make a blind bit of difference and I can always revert to a generic monitor setting but it is at least a software-only chance to make an A/B comparison.

smartmon.jpg


installer1.jpg


m50.jpg
 
Last edited:
Since making this change the system has been idle for 2-3 stretches of 2-3 hrs each. I occasionally turned the TV on to check and it didn't give me 'no signal detected' or 'no source detected.' The TV is off and I will leave it overnight and check it in the morning and report here.
 
Since making this change the system has been idle for 2-3 stretches of 2-3 hrs each. I occasionally turned the TV on to check and it didn't give me 'no signal detected' or 'no source detected.' The TV is off and I will leave it overnight and check it in the morning and report here.
Are you using MINIX HDMI cable (that came with the device )?
 
Last edited:
Are you using MINIX HDMI cable (that came with the device )?

No, I am not. I couldn't tell you which cable came with it - I've got a dozen or so and most look alike. For all I know I left the original cable still bundled up in the package and set it aside.

I just turned the TV on and the Minix screen/desktop is still visible after 10 idle hours. No issues with sleep, 'no signal detected,' 'no source detected' problems etc.

I admit that I downloaded the Intel Graphics 600 control panel so it would detect and download new drivers for the video card but as far as I can recall that has been the only change in addition to the monitor driver I installed.

My working theories:
-The Windows 10 monitor driver, both Pnp and Non-Pnp version, was written in 2006. In fairness to Microsoft they couldn't have anticipated the changes in technology and use that followed, the advent of streaming devices, mini-PCs and so forth when they wrote the driver nor could they have anticipated that flat-panel TVs would be used as monitors by many. On the other hand 15 years is plenty of time to rewrite the driver especially considering Windows 10 was released in 2015. Does this mean they're still using a driver from Windows Vista? It would seem so.

-Some aspect (probably hard-coded) of the driver for the graphics card and/or the monitor was telling Samsung TV that the signal was lost, idle, etc. no matter how many times and ways sleep functions and power-down functions were disabled in Windows settings.

-The reversion back to SDR (standard dynamic range) MAY have helped to correct the problem although my TV is, I believe, still configured to use HDR for that HDMI port.

-Force-feeding Windows with a monitor driver from the TV's same OEM may have overcome the sleep/no signal issue. The problem now is that Windows Update tends to run roughshod over hardware configuration vis-a-vis drivers.

Editorial aside: Windows Update has suffered greatly from 'scope creep.' It once was used to quickly distribute much-needed patches and address security vulnerabilities/exploits. It now has been hijacked to push all manner of MS products and to rope the end-user into the MS 'ecosystem' by larding up his machine with the Edge browser, Skype, OneDrive and other software the end-user may neither want nor need.

Windows Update is like painting a wall and having the brush come to life and paint the carpet as well.

Most of us have learned to compensate for Windows' many quirks and faults by becoming very handy with Device Manager, arcane settings, registry edits, Group Policies etc. When we finally get the house of cards set up and balanced we don't want it knocked over by new builds that almost always fix what wasn't broken. The debate about Windows Update rages in many corners of the internet - I won't drag it all here - except to say that merely being able to pause updates for 7 days is an insult and a joke. Being hounded to update, reboot, etc. is annoying and often counterproductive.

With this in mind, I use a utility that blocks WU.
https://www.ghacks.net/2020/06/04/wu10man-is-an-open-source-tool-for-disabling-windows-10-updates/

The only problem I've found with it is that occasionally some software installations will fail with a generic error message (eg error 19 or 35). Reenabling Windows Update temporarily usually eliminates the problem.

Of course, some of you may want the latest and so-called greatest. Totally up to you. My last two go-rounds with WU resulted in:

1) E-mail and other programs being unable to connect to Gmail and other servers that rely on encryption for passwords, security, etc. Testing with a virtual machine and a pre-updated version of Windows had no issues. I had no choice but to roll the update back.

2) Logins and passwords for all web sites in Chrome including Google/Gmail being wrecked/forgotten and forgotten repeatedly no matter how many times they are entered. This issue with 2020 1st half and 2nd half builds of Windows 10 has been widely reported. A flurry of workarounds, hacks, etc. have been tried with little success. Making matters worse, attempts to roll back the update as Microsoft supposedly offers does not work. You are stuck. Most have admitted defeat and reinstalled Windows from scratch. I'm on build 1909 and sticking with it for now.

Anyway, back on topic: I have my Minix configured as above and things seem to be holding steady. If you are a Samsung or an LG owner I suggest trying to install a driver from the same OEM as your TV by hook or by crook and seeing how you fare. Good luck.
 
Last edited:
I don't understand too much about cables but i can tell you this:
I had problems (hdmi display issues) connecting U22-XJ to my Samsung 4k TV, so i comnect the minix original hdmi cable (1 meter) and now i don't have problems (problem solved).

So, the cable you use will improve the image (quality, etc) and the smaller the cable the better.
I will test G41V-4 also with another hdmi cable, see my posts above.
 
One additional note: when a Samsung TV detects an HDMI input it will prompt the user to set it up from one of four categories including OTT/Set-Top Box and PC.

Despite all I have written already on the subject this may be the critical junction because the OTT/Set-Top Box allows one to choose Minix from the list of OEMs. It's a Minix box, after all, so why not? In addition, supposedly this offers the ability to use the Samsung Smart Remote to control the Minix.

I say: ignore the 'help' and use the PC option instead as I did this time around. There is a chance that the TV configures or utilizes the HDMI port differently depending on the type of device specified. It just may be that telling the Samsung TV you have a PC connected (which, of course, you do) is the key to getting it to stay that way consistently.

I never have been able to successfully control any Minix with a Samsung Smart Remote although my Samsung 'dumb' remote did work with an Android-based Minix on a different TV. I have a bluetooth-enabled mini-keyboard/touchpad remote that I use for the Minix box anyway.

Again, it's all trial and error at this point but errors seem to be decreasing.
 
Back
Top