Live Updates: COVID-19 Cases
  • World 30,815,278
    World
    Confirmed: 30,815,278
    Active: 7,420,084
    Recovered: 22,436,962
    Death: 958,232
  • USA 6,943,461
    USA
    Confirmed: 6,943,461
    Active: 2,545,409
    Recovered: 4,194,597
    Death: 203,455
  • India 5,351,723
    India
    Confirmed: 5,351,723
    Active: 1,016,032
    Recovered: 4,249,648
    Death: 86,043
  • Brazil 4,503,002
    Brazil
    Confirmed: 4,503,002
    Active: 577,828
    Recovered: 3,789,139
    Death: 136,035
  • Russia 1,097,251
    Russia
    Confirmed: 1,097,251
    Active: 171,450
    Recovered: 906,462
    Death: 19,339
  • Peru 756,412
    Peru
    Confirmed: 756,412
    Active: 124,334
    Recovered: 600,795
    Death: 31,283
  • Mexico 688,954
    Mexico
    Confirmed: 688,954
    Active: 123,959
    Recovered: 492,192
    Death: 72,803
  • Spain 659,334
    Spain
    Confirmed: 659,334
    Active: 628,839
    Recovered: ?
    Death: 30,495
  • South Africa 657,627
    South Africa
    Confirmed: 657,627
    Active: 54,926
    Recovered: 586,844
    Death: 15,857
  • Chile 444,674
    Chile
    Confirmed: 444,674
    Active: 14,319
    Recovered: 418,101
    Death: 12,254
  • France 428,696
    France
    Confirmed: 428,696
    Active: 305,873
    Recovered: 91,574
    Death: 31,249
  • Iran 419,043
    Iran
    Confirmed: 419,043
    Active: 37,293
    Recovered: 357,632
    Death: 24,118
  • UK 390,358
    UK
    Confirmed: 390,358
    Active: 348,599
    Recovered: ?
    Death: 41,759
  • Bangladesh 347,372
    Bangladesh
    Confirmed: 347,372
    Active: 88,073
    Recovered: 254,386
    Death: 4,913
  • Saudi Arabia 329,271
    Saudi Arabia
    Confirmed: 329,271
    Active: 15,383
    Recovered: 309,430
    Death: 4,458
  • Pakistan 305,031
    Pakistan
    Confirmed: 305,031
    Active: 6,572
    Recovered: 292,044
    Death: 6,415
  • Turkey 301,348
    Turkey
    Confirmed: 301,348
    Active: 27,786
    Recovered: 266,117
    Death: 7,445
  • Italy 296,569
    Italy
    Confirmed: 296,569
    Active: 43,161
    Recovered: 217,716
    Death: 35,692
  • Germany 271,672
    Germany
    Confirmed: 271,672
    Active: 19,206
    Recovered: 243,000
    Death: 9,466
  • Canada 142,745
    Canada
    Confirmed: 142,745
    Active: 9,362
    Recovered: 124,172
    Death: 9,211
  • Netherlands 91,934
    Netherlands
    Confirmed: 91,934
    Active: 85,659
    Recovered: ?
    Death: 6,275
  • China 85,269
    China
    Confirmed: 85,269
    Active: 171
    Recovered: 80,464
    Death: 4,634
  • Australia 26,885
    Australia
    Confirmed: 26,885
    Active: 2,079
    Recovered: 23,962
    Death: 844
  • S. Korea 22,893
    S. Korea
    Confirmed: 22,893
    Active: 2,545
    Recovered: 19,970
    Death: 378
  • New Zealand 1,811
    New Zealand
    Confirmed: 1,811
    Active: 67
    Recovered: 1,719
    Death: 25

UPDATE (Solved): Disney+ app not working on Samsung TV with smart hub

Author at TechGenyz Tech

The Disney App on a few selected Samsung smart TV models is reportedly not working, and a few users have taken to the online Samsung forum to get assistance on this urgent matter, and subsequently made Samsung aware of the problem.

One user reports, “After a couple of months of using the Disney App on my Samsung TV without issue, it recently stopped working. Whenever I open the app on the tv, I receive the below message and after a few seconds the app closes – We’re having a problem. Exiting the App. Error Code: 1016 – App_Config_Failure.

She further adds that the power cycling the TV is not working in this case, the TV does not have the ability to clear the app cache, she cannot delete the Disney app and that the “reset Smart Hbu” option has been rendered useless too in this case.

The problem is not on Disney app’s part since Disney+ has never seen that particular error code (1016). The problem might be that Samsung had rolled out a Smart Hub update in early February; however. Since there was no accompanying Disney+ roll out, the app now is incompatible with the TV.

The solution to the problem seems to vary from user to user because another user mentioned that the problem on his smart TV has been resolved. The Samsung Moderator had suggested changing the DNS number manually by clicking on Menu> Network> Network status>IP settings on the TV remote, and thereby manually assigning the DNS server value to 8.8.8.8.

A lot of other users complained about the same problem. Furthermore, the problem does not appear to be limited to Samsung Smart Hubs only. Another user has complained that his TV bearing the model number UE55KS8000L, which does not have a smart hub, is also facing the same problem. Furthermore, this error is not limited to the US only since a few of the users outside of the US have the same grievances.

A Samsung moderator on the official forum mentioned that the issue has now been resolved. Users facing the issue can try the below steps or visit this link for detailed troubleshooting.

Cold booting your TV is a little different than simply turning it off and back on. When you turn it off, it is really in standby. A cold boot actually shuts the TV down and reboots it, like restarting a laptop. This can solve issues you may be having with apps, glitches in the menu, picture issues, etc.

There are two ways to cold boot your TV.

With the Remote: For most people, the easiest way is to hold down the Power button on the Samsung TV remote until the TV turns off and on again. This should only take about 5 seconds.

With the Plug: If you do not have the remote, unplug your TV from the wall outlet or surge protector, leave it unplugged for 30 seconds, and then plug it back in.

Note: If you switch off a surge protector with other devices plugged into it (such as your router), give them time to power up and reconnect before testing any functions on your TV.

Samsung smart TVs running Tizen OS including all models from 2016 onwards are compatible with the Disney+ app. The Disney+ app doesn’t support Samsung TVs using the Orsay OS or the built-in Web browser.

Career

Subscribe