Just got my OSSC back from repairs today and it works fine on my TV now. Huge thanks to BuckoA51, lynxtosg, and everyone else who was helping with troubleshooting.
Looks like faulty HDMI transmitter was indeed the culprit.
Okay, I’ve now done an exact like-for-like settings test and still no signal. I’m going to go ahead and start the process of getting my OSSC exchanged now. A huge thanks to everyone who replied in this thread.
As for harrumph’s input, I am on a different TV firmware than lynxtosg. I’m on the newest firmware (1356) and lynxtosg is on 1325 according to his TV profile info. I’m doubting that’s the culprit but he can update and check if he wants. Note that there’s no way to downgrade firmware on Samsung TVs, though, so if that IS actually the problem, he’ll be screwed too.
Awesome, yes. That’s the EXACT same TV I have. But mine won’t even display that when I turn on the OSSC. I just get the no signal screen as per my second picture.
So I’m thinking what BuckoA51 said is true and there’s something wrong with my OSSC’s HDMI transmitter.
But, of course, just to be 100% sure, I would really appreciate it if you could tell me your TV’s settings and your OSSC’s settings so I can duplicate them and rule out any other possibility that something’s wrong.
First off, I 100% appreciate the help, lynxtosg, don’t think I don’t. But just to make sure I’m not messing with a bunch of settings for a lost cause, when you turn your OSSC on with no system hooked into it, does your TV show this
or
this?
Okay, I was able to try it with all the TVs in the house.
Results:
Worked with Samsung MU6070 (as previously reported) and Samsung H5201 (UN40H5201AFXZA).
Did NOT work with Samsung RU7100 (as previously reported) or Toshiba LF621 (43LF621U19). In both cases it showed no signal.
Since it’s working fine with lynxtosg’s RU7100, does it sound like it’s a case of a messed up HDMI transmitter? Should I try to get a replacement unit?
Cookie | Duration | Description |
---|---|---|
_gat | 1 minute | This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. |
Cookie | Duration | Description |
---|---|---|
__gads | 1 year 24 days | The __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
Cookie | Duration | Description |
---|---|---|
IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
Cookie | Duration | Description |
---|---|---|
ct_checked_emails | session | No description |
ct_has_scrolled | session | No description |
ct_mouse_moved | session | No description |
ct_screen_info | session | No description |
wordpress_apbct_antibot | session | No description |
wp_woocommerce_session_9cc3598a6315be16da4f85bb374cf6a5 | 2 days | No description |