Samsung TV's

David Li wrote:

We have done thousands of Samsung IP TVs....shouldn't be an issue when authenticated cleanly.
 

I know you have but most of the regularly used tv's in the house are high end Samsungs so any reports of issues with this specific driver raise alarm bells for me. I've got a lot on my plate this month and don't need any additional headaches.

Ok, but remember - it's not the Driver. It's the TV.

I haven't yet as I'm out of town until mid next week.  Its currently working with the serial, but I will try David's suggestion to see if it works.  Was just a bit weird that it happened after I downloaded the new driver, but if I'm the only one it happened to then it likely is as David said, the TV's in my house (its happened on both Samsung TV's).  I am still messing with a lot of things so could be something within my system that caused it.

I'll report back when I try the fix.

 

David Li wrote:

Ok, but remember - it's not the Driver. It's the TV.
 

Fair enough but it doesn't really change the circumstances. If I get into a car accident I don't especially care who caused it. As a practical matter the car is still wrecked, and I still have to deal with the fallout lol

Finally decided to update the Samsung TV driver and immediately started having the symptoms described in the first post. Deleted all tv's/tokens and reauthenticated with no success. Rolled back to the previous Samsung TV driver and had to pair the sets again but everything immediately started working as it should.

I'll just sick with the previous driver since I don't really have a compelling need to upgrade. The only reason I experimented with it at all is because I have some time to kill over the next few days.

What I am not hearing you post is that you power cycled the TV (ie - pulled the power cable and waited) with the tokens deleted.

We did probably 300 Samsung TVs just today. Stuff works.