Toshiba TV not able to detect UMS after firmware upgrade

General discussion about Universal Media Server (no support or requests)
Pan Borowik
Posts: 8
Joined: Sun May 21, 2017 2:44 am

Toshiba TV not able to detect UMS after firmware upgrade

Post by Pan Borowik »

Hi,

I've used UMS for a while with a Toshiba 47L7453d TV, and it worked OK. Lately I've updated the firmware of the TV and the problems started.
Namely, the TV does not see the server.
Thing is, after I turn on the TV it gets detected as Toshiba-LCDTV as is used to. But to connect to DLNA I need to start "Home" screen on TV (the one with applications and services like DLNA).
As soon as I open the "Home" screen, the device becomes inactive in UMS (grayed out), and the Home app cannot connect to the UMS. It can see the windows upnp server, so the connection itself is fine.
Any ideas? Maybe someone can share some general config for Toshiba?
User avatar
Sami32
Posts: 851
Joined: Mon Apr 11, 2016 5:09 am

Re: Toshiba TV not able to detect UMS after firmware upgrade

Post by Sami32 »

As a general note, you should have posted in the "General help/support". But as you already posted, better to continue here.

You should post your full trace log, as explained in the 3 first comments that you will found if you click on the red link into my signature.

After that, you should receive help ;)
Pan Borowik
Posts: 8
Joined: Sun May 21, 2017 2:44 am

Re: Toshiba TV not able to detect UMS after firmware upgrade

Post by Pan Borowik »

Sami32 wrote:Same problem here - I don't have log :/

What is your firmware version ?
Hello,
firmware version I've got from Toshiba page is V8_1_97_10_01_1 2015/11/5

The TV is not mine, it's in my parents house, but I will try to get the tracelog remotely and post it here ASAP.
User avatar
Sami32
Posts: 851
Joined: Mon Apr 11, 2016 5:09 am

Re: Toshiba TV not able to detect UMS after firmware upgrade

Post by Sami32 »

Hello,

I'm not sure what do you mean by "from Toshiba page" ? from their website ?
The one useful in your case is only the one that your TV display.

Let's see what we can do for it, but as Toshiba forums are full of users having DLNA/Cloud issues after having updated their firmware, i'm very suspicious about that.

Did you already asked to Toshiba support to send you a link to their precedent firmware version ?
Pan Borowik
Posts: 8
Joined: Sun May 21, 2017 2:44 am

Re: Toshiba TV not able to detect UMS after firmware upgrade

Post by Pan Borowik »

Sami32 wrote:I'm not sure what do you mean by "from Toshiba page" ? from their website ?
The one useful in your case is only the one that your TV display.
The one one my TV display is the one I got from Toshiba page :)

Attached a trace log of turning TV on (shows up in UMS ok), then going to home screen (TV is disabled in UMS):

Code: Select all

TRACE 2017-06-01 09:10:19.571 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.3:1900]
TRACE 2017-06-01 09:10:19.575 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.1:4373]
TRACE 2017-06-01 09:10:19.580 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.3:1900]
TRACE 2017-06-01 09:10:19.678 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.1:4373]
TRACE 2017-06-01 09:10:19.682 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.3:1900]
DEBUG 2017-06-01 09:10:19.749 [cling-3] net.pms.configuration.ConfigurationReader Reading MediaInfo: true (default: false)
DEBUG 2017-06-01 09:10:19.749 [cling-3] net.pms.network.UPNPHelper Marking upnp renderer "TOSHIBA-LCDTV" at /192.168.1.3 as unrecognized
DEBUG 2017-06-01 09:10:19.750 [cling-3] net.pms.PMS Adding status button for TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.752 [cling-3] net.pms.network.UPNPControl Device icon: http://192.168.1.3:50196/web/file/largeIco.jpg
TRACE 2017-06-01 09:10:19.775 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.1:4373]
TRACE 2017-06-01 09:10:19.780 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.3:1900]
DEBUG 2017-06-01 09:10:19.781 [cling-5] net.pms.network.UPNPControl Renewing subscriptions to 
DEBUG 2017-06-01 09:10:19.781 [cling-5] net.pms.network.UPNPControl Subscribing to AVTransport service on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.782 [cling-5] net.pms.network.UPNPControl Subscribing to ConnectionManager service on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.783 [cling-5] net.pms.network.UPNPControl Subscribing to RenderingControl service on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.783 [cling-5] net.pms.network.UPNPControl Subscribing to X_ServiceManager service on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.819 [cling-3] net.pms.network.UPNPHelper New renderer found: "TOSHIBA-LCDTV" with dlna details: {friendlyName=TOSHIBA-LCDTV, address=192.168.1.3, udn=uuid:34d52464-3d47-11e7-9d89-e0cec3e8d92b, manufacturer=TOSHIBA, modelName=TOSHIBA-LCDTV, modelNumber=, modelDescription=, manufacturerURL=, modelURL=}
DEBUG 2017-06-01 09:10:19.820 [cling-3] net.pms.network.UPNPControl Adding device: urn:schemas-upnp-org:device:MediaRenderer:1 (RemoteDevice) Identity: (RemoteDeviceIdentity) UDN: uuid:34d52464-3d47-11e7-9d89-e0cec3e8d92b, Descriptor: http://192.168.1.3:50196, Root: true
DEBUG 2017-06-01 09:10:19.820 [cling-3] net.pms.network.UPNPControl Subscribing to AVTransport service on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.820 [cling-3] net.pms.network.UPNPControl Subscribing to ConnectionManager service on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.820 [cling-3] net.pms.network.UPNPControl Subscribing to RenderingControl service on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.821 [cling-3] net.pms.network.UPNPControl Subscribing to X_ServiceManager service on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.826 [cling-3] net.pms.network.UPNPHelper Created upnp player for TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.871 [cling-3] net.pms.network.UPNPControl Subscription established: X_ServiceManager on TOSHIBA-LCDTV
TRACE 2017-06-01 09:10:19.880 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.1:4373]
TRACE 2017-06-01 09:10:19.884 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.3:1900]
DEBUG 2017-06-01 09:10:19.885 [cling-3] net.pms.network.UPNPControl Subscription established: ConnectionManager on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.887 [cling-3] net.pms.network.UPNPControl Subscription established: RenderingControl on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.907 [cling-3] net.pms.network.UPNPControl Subscription established: AVTransport on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.926 [cling-3] net.pms.network.UPNPControl Subscription established: X_ServiceManager on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.929 [cling-3] net.pms.network.UPNPControl Subscription established: RenderingControl on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.929 [cling-3] net.pms.network.UPNPControl Subscription established: ConnectionManager on TOSHIBA-LCDTV
DEBUG 2017-06-01 09:10:19.933 [cling-3] net.pms.network.UPNPControl Subscription established: AVTransport on TOSHIBA-LCDTV
TRACE 2017-06-01 09:10:19.980 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.1:4373]
DEBUG 2017-06-01 09:10:21.252 [UPNP-AliveMessageSender] net.pms.network.UPNPHelper Sending ALIVE...
TRACE 2017-06-01 09:10:21.292 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.4:57961]
TRACE 2017-06-01 09:10:21.294 [New I/O worker #5] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50333
TRACE 2017-06-01 09:10:21.295 [New I/O worker #6] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50334
TRACE 2017-06-01 09:10:21.394 [New I/O worker #7] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50335
TRACE 2017-06-01 09:10:21.395 [New I/O worker #8] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50336
TRACE 2017-06-01 09:10:21.494 [New I/O worker #1] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50337
TRACE 2017-06-01 09:10:21.495 [New I/O worker #2] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50338
TRACE 2017-06-01 09:10:21.587 [New I/O worker #3] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50339
TRACE 2017-06-01 09:10:21.589 [New I/O worker #4] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50340
TRACE 2017-06-01 09:10:21.688 [New I/O worker #5] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50341
TRACE 2017-06-01 09:10:21.689 [New I/O worker #6] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50342
TRACE 2017-06-01 09:10:21.788 [New I/O worker #7] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50343
TRACE 2017-06-01 09:10:21.789 [New I/O worker #8] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50344
TRACE 2017-06-01 09:10:21.871 [New I/O worker #1] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50345
TRACE 2017-06-01 09:10:21.872 [New I/O worker #2] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50346
TRACE 2017-06-01 09:10:21.972 [New I/O worker #3] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50347
TRACE 2017-06-01 09:10:21.973 [New I/O worker #4] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50348
TRACE 2017-06-01 09:10:22.072 [New I/O worker #5] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50351
TRACE 2017-06-01 09:10:22.074 [New I/O worker #6] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50352
TRACE 2017-06-01 09:10:22.131 [New I/O worker #7] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50354
TRACE 2017-06-01 09:10:22.132 [New I/O worker #8] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50355
TRACE 2017-06-01 09:10:22.231 [New I/O worker #1] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50361
TRACE 2017-06-01 09:10:22.232 [New I/O worker #2] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50362
TRACE 2017-06-01 09:10:22.331 [New I/O worker #3] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50365
TRACE 2017-06-01 09:10:22.332 [New I/O worker #4] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50366
TRACE 2017-06-01 09:10:22.412 [New I/O worker #5] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50367
TRACE 2017-06-01 09:10:22.413 [New I/O worker #6] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50368
TRACE 2017-06-01 09:10:22.512 [New I/O worker #7] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50369
TRACE 2017-06-01 09:10:22.513 [New I/O worker #8] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50370
TRACE 2017-06-01 09:10:22.612 [New I/O worker #1] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50371
TRACE 2017-06-01 09:10:22.613 [New I/O worker #2] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50372
TRACE 2017-06-01 09:10:22.675 [New I/O worker #3] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50373
TRACE 2017-06-01 09:10:22.677 [New I/O worker #4] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50374
TRACE 2017-06-01 09:10:22.775 [New I/O worker #5] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50375
TRACE 2017-06-01 09:10:22.777 [New I/O worker #6] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50376
TRACE 2017-06-01 09:10:22.876 [New I/O worker #7] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50377
TRACE 2017-06-01 09:10:22.877 [New I/O worker #8] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50378
TRACE 2017-06-01 09:10:27.660 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.3:1900]
TRACE 2017-06-01 09:10:27.665 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.1:4951]
TRACE 2017-06-01 09:10:28.377 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.3:1900]
TRACE 2017-06-01 09:10:29.912 [UPNPHelper] net.pms.network.UPNPHelper Receiving a M-SEARCH from [192.168.1.13:53891]: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 2
ST: urn:dial-multiscreen-org:service:dial:1


TRACE 2017-06-01 09:10:30.324 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.3:1900]
TRACE 2017-06-01 09:10:39.539 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.1:2621]
TRACE 2017-06-01 09:10:45.296 [UPNPHelper] net.pms.network.UPNPHelper Receiving a M-SEARCH from [192.168.1.13:53891]: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 2
ST: urn:dial-multiscreen-org:service:dial:1


DEBUG 2017-06-01 09:10:52.873 [UPNP-AliveMessageSender] net.pms.network.UPNPHelper Sending ALIVE...
TRACE 2017-06-01 09:10:52.965 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.4:55617]
TRACE 2017-06-01 09:10:52.968 [New I/O worker #1] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50403
TRACE 2017-06-01 09:10:52.969 [New I/O worker #2] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50404
TRACE 2017-06-01 09:10:53.069 [New I/O worker #3] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50408
TRACE 2017-06-01 09:10:53.070 [New I/O worker #4] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50409
TRACE 2017-06-01 09:10:53.173 [New I/O worker #5] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50414
TRACE 2017-06-01 09:10:53.175 [New I/O worker #6] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50415
TRACE 2017-06-01 09:10:53.263 [New I/O worker #7] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50416
TRACE 2017-06-01 09:10:53.264 [New I/O worker #8] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50417
TRACE 2017-06-01 09:10:53.362 [New I/O worker #1] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50419
TRACE 2017-06-01 09:10:53.364 [New I/O worker #2] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50420
TRACE 2017-06-01 09:10:53.463 [New I/O worker #3] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50421
TRACE 2017-06-01 09:10:53.464 [New I/O worker #4] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50422
TRACE 2017-06-01 09:10:53.467 [New I/O worker #5] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50423
TRACE 2017-06-01 09:10:53.468 [New I/O worker #6] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50424
TRACE 2017-06-01 09:10:53.567 [New I/O worker #7] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50425
TRACE 2017-06-01 09:10:53.569 [New I/O worker #8] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50426
TRACE 2017-06-01 09:10:53.669 [New I/O worker #1] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50427
TRACE 2017-06-01 09:10:53.670 [New I/O worker #2] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50428
TRACE 2017-06-01 09:10:53.673 [New I/O worker #3] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50429
TRACE 2017-06-01 09:10:53.675 [New I/O worker #4] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50430
TRACE 2017-06-01 09:10:53.774 [New I/O worker #5] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50431
TRACE 2017-06-01 09:10:53.775 [New I/O worker #6] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50432
TRACE 2017-06-01 09:10:53.874 [New I/O worker #7] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50433
TRACE 2017-06-01 09:10:53.876 [New I/O worker #8] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50434
TRACE 2017-06-01 09:10:53.933 [New I/O worker #1] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50435
TRACE 2017-06-01 09:10:53.935 [New I/O worker #2] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50436
TRACE 2017-06-01 09:10:54.033 [New I/O worker #3] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50438
TRACE 2017-06-01 09:10:54.034 [New I/O worker #4] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50439
TRACE 2017-06-01 09:10:54.133 [New I/O worker #5] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50440
TRACE 2017-06-01 09:10:54.135 [New I/O worker #6] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50441
TRACE 2017-06-01 09:10:54.197 [New I/O worker #7] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50442
TRACE 2017-06-01 09:10:54.199 [New I/O worker #8] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50443
TRACE 2017-06-01 09:10:54.295 [New I/O worker #1] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50444
TRACE 2017-06-01 09:10:54.297 [New I/O worker #2] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50445
TRACE 2017-06-01 09:10:54.396 [New I/O worker #3] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50446
TRACE 2017-06-01 09:10:54.398 [New I/O worker #4] net.pms.network.RequestHandlerV2 Ignoring self-originating request from /192.168.1.4:50447
TRACE 2017-06-01 09:10:57.664 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.1:4951]
TRACE 2017-06-01 09:11:00.734 [UPNPHelper] net.pms.network.UPNPHelper Receiving a M-SEARCH from [192.168.1.13:53891]: M-SEARCH * HTTP/1.1
HOST: 239.255.255.250:1900
MAN: "ssdp:discover"
MX: 2
ST: urn:dial-multiscreen-org:service:dial:1


TRACE 2017-06-01 09:11:02.066 [UPNPHelper] net.pms.network.UPNPHelper Receiving a NOTIFY from [192.168.1.3:1900]
DEBUG 2017-06-01 09:11:02.068 [cling-10] net.pms.network.UPNPControl Subscription cancelled: RenderingControl on uuid:34d52464-3d47-11e7-9d89-e0cec3e8d92b: DEVICE_WAS_REMOVED
DEBUG 2017-06-01 09:11:02.068 [cling-13] net.pms.network.UPNPControl Subscription cancelled: AVTransport on uuid:34d52464-3d47-11e7-9d89-e0cec3e8d92b: DEVICE_WAS_REMOVED
DEBUG 2017-06-01 09:11:02.068 [cling-14] net.pms.network.UPNPControl Subscription cancelled: X_ServiceManager on uuid:34d52464-3d47-11e7-9d89-e0cec3e8d92b: DEVICE_WAS_REMOVED
DEBUG 2017-06-01 09:11:02.068 [cling-15] net.pms.network.UPNPControl Subscription cancelled: X_ServiceManager on uuid:34d52464-3d47-11e7-9d89-e0cec3e8d92b: DEVICE_WAS_REMOVED
DEBUG 2017-06-01 09:11:02.068 [cling-12] net.pms.network.UPNPControl Subscription cancelled: RenderingControl on uuid:34d52464-3d47-11e7-9d89-e0cec3e8d92b: DEVICE_WAS_REMOVED
DEBUG 2017-06-01 09:11:02.068 [cling-8] net.pms.network.UPNPControl Subscription cancelled: ConnectionManager on uuid:34d52464-3d47-11e7-9d89-e0cec3e8d92b: DEVICE_WAS_REMOVED
DEBUG 2017-06-01 09:11:02.068 [cling-3] net.pms.network.UPNPControl Subscription cancelled: ConnectionManager on uuid:34d52464-3d47-11e7-9d89-e0cec3e8d92b: DEVICE_WAS_REMOVED
DEBUG 2017-06-01 09:11:02.068 [cling-11] net.pms.network.UPNPControl Subscription cancelled: AVTransport on uuid:34d52464-3d47-11e7-9d89-e0cec3e8d92b: DEVICE_WAS_REMOVED
DEBUG 2017-06-01 09:11:02.069 [cling-16] net.pms.network.UPNPControl TOSHIBA-LCDTV is now offline.
From what I see the TV just registers as it would be turned off when entering the HOME screen, so I guess I'll have to get more info on the matter from Toshiba.
Will post if I get a response from them.
User avatar
Sami32
Posts: 851
Joined: Mon Apr 11, 2016 5:09 am

Re: Toshiba TV not able to detect UMS after firmware upgrade

Post by Sami32 »

Please, post the full trace log as explained in the forum rules, and attach the archive here. Thanks.
Something look strange with your network, but without log i'll not even try to guess.

I would prefer the real firmware from your TV, as your update could have not worked as expected.
Do you know how to read it directly from your TV ?
Pan Borowik
Posts: 8
Joined: Sun May 21, 2017 2:44 am

Re: Toshiba TV not able to detect UMS after firmware upgrade

Post by Pan Borowik »

Attached is the complete tracelog.
I do know how to check the firmware on the TV, but the TV is 250 kilometers away, at my folks home.
Attachments
ums_dbg.zip
(37.78 KiB) Downloaded 543 times
Last edited by Pan Borowik on Fri Jun 02, 2017 1:34 am, edited 1 time in total.
Pan Borowik
Posts: 8
Joined: Sun May 21, 2017 2:44 am

Re: Toshiba TV not able to detect UMS after firmware upgrade

Post by Pan Borowik »

Those are attached in my previous post, which i TOTALLY didn't edit ;)
Post Reply