Black Scrren at Startup Live TV

[ppasteur]

I know this is a known issue and I posted the below in an existing topic. Then I noticed it had been labeled as "Solved" No idea if anyone will look at it So I will try a new topic.
Hopefully this does not violate any rules.

The issue has not been fixed for me with the current release. I am getting a 15 to 30 second or so black screen on startup with two Nvidia Shield Pro 2019 clients and a couple of Win 10 client setups (20250603). Which I just forced an update on. It seems this is the latest available through MS. Now has the animation, but did not before.

I just installed the 20250708 update on the Shield clients and it did not fix the issue. This is when setup to open with Live TV.

Not sure if it is pertinent, but I am not seeing the animation on these. It just sits at the black screen for too long.

This is no longer true. I do see the animation and hear sound, then get the black screen for 15 to 30 seconds before the live TV stream opens. Then there is a slight freeze of the video, before normal startup.

FWIW here are the parts to my system.

Hardware Model HDHR4-2US
Firmware Version 20250623
Device ID 104EA976

Hardware Model HDHR5-4US
Firmware Version 20250623
Device ID 107086F1

Hardware Model HDHR5-4K
Firmware Version 20250623
ATSC3-DRM SD20230420
Device ID 1080AB39

2 record engines on Shields Version 20250606
Synology NAS Record engine Version 20250130beta1

BTW. I just tried running the app on my phone with the latest update 20250708... Android 15. There was no delay. So it does seem to be client related.

[ppasteur]

I have gotten no reply or acknowledgement on this continuing problem.

I would like to know if SD is aware that the most recent up date has not fixed the 15 to 30 second black screen delay when opening Live TV.

Another thread reporting the same problem was marked as Solved. I just want to make sure that SD is aware that the latest release did not solve the problem for everyone.

I would be happy to take part in troubleshooting if it would be helpful.

Just please let me know whether this is still being worked on.

THX

[signcarver]

I would first remove/disable engines on android devices as updates to android often cause issues with them and for many hasn't really been practical to have such for a few years (yes it can work but I don't suggest it). Though it has happened on occasion since no code in engine changed, typically an update to android will update to same app version number (should also be on 20250708, i will try to verify what it reports but I don't typically have android based engines running as android updates have caused many headaches for me this may be an indication that you didn't update the android clients as you thought).

Since you have engines on shields, I would take care and remove the drives, uninstall and reinstall app (uninstall will erase your recordings made on shield engine that is why you must take care when engines are on shields).

I would also make sure recording engine is updated to latest on your NAS as well (I believe should be on 20250506 even on beta channel), depending on how you installed record engine, it may be as simple as restarting your nas, or the package but you may need a more manual approach (depends on how you installed)

Other things to consider: on android, for ui to load, it must be able to download such via internet. When an engine is detected, it will use a engine for live tv. IPV6 will be the preferred method of communicating with devices/engines, particularly on android my vpn's have had issue as it discovers via ipv6 just fine but shortly after discover all ipv6 unicast requests go out to the cloud while ipv4 works with local just fine.