Humax FOX T2 reboots on file scan

[Raptor399]

Hi

I've connected a Humax Fox T2 to the latest version of PMS. It connects ok on the Humax, and you can navigate through the folder structures, but as soon as it needs to read files in the folder (to list them) then the Humax reboots itself. This is the debug.log that gets created in PMS :

Code: Select all

DEBUG 2012-12-18 17:58:39.778 [New I/O server worker #1-4] Setting margin to 2Mb
DEBUG 2012-12-18 17:59:43.560 [UPNP-AliveMessageSender] Sending ALIVE...
INFO  2012-12-18 18:00:46.966 [UPNPHelper] No IP filter specified, access granted to /192.168.1.134
DEBUG 2012-12-18 18:02:46.105 [UPNP-AliveMessageSender] Sending ALIVE...
INFO  2012-12-18 18:02:53.308 [UPNPHelper] No IP filter specified, access granted to /192.168.1.133
INFO  2012-12-18 18:05:41.989 [UPNPHelper] No IP filter specified, access granted to /192.168.1.109
INFO  2012-12-18 18:05:42.022 [pool-7-thread-3] Checking IP: 192.168.1.109 for Popcorn Hour
INFO  2012-12-18 18:05:42.777 [pool-7-thread-3] Renderer Popcorn Hour found on this address: HUMAX (192.168.1.109)
DEBUG 2012-12-18 18:05:42.778 [pool-7-thread-3] Starting ping -n 3 -l 64000 192.168.1.109
DEBUG 2012-12-18 18:05:44.779 [SpeedStats Failsafe] Stopping process: ping-30
INFO  2012-12-18 18:05:44.784 [pool-7-thread-3] Address /192.168.1.109 has an estimated network speed of: 85 Mb/s
DEBUG 2012-12-18 18:05:48.976 [UPNP-AliveMessageSender] Sending ALIVE...
INFO  2012-12-18 18:06:28.319 [New I/O server worker #1-3] Checking shared folder: M:\ServerFolders\Music
INFO  2012-12-18 18:06:28.320 [New I/O server worker #1-3] Checking shared folder: V:\ServerFolders\Video
INFO  2012-12-18 18:06:28.320 [New I/O server worker #1-3] Checking shared folder: V:\ServerFolders\Pictures
DEBUG 2012-12-18 18:06:32.893 [New I/O server worker #1-1] Forcing short path name on M:\ServerFolders\Music\FLAC - TO SORT\björk - 1993 - big time sensuality [cd single uk] (flac, 44khz)
DEBUG 2012-12-18 18:08:54.629 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2012-12-18 18:11:59.356 [UPNP-AliveMessageSender] Sending ALIVE...
DEBUG 2012-12-18 18:13:52.916 [Thread-142]
DEBUG 2012-12-18 18:13:52.916 [Thread-143] Maybe you are playing a non-interleaved stream/file or the codec failed?
DEBUG 2012-12-18 18:13:52.916 [Thread-142] Too many video packets in the buffer: (1044 in 33587196 bytes).
DEBUG 2012-12-18 18:13:52.917 [Thread-143] For AVI files, try to force non-interleaved mode with the -ni option.
DEBUG 2012-12-18 18:14:28.354 [New I/O server worker #1-1] Forcing short path name on M:\ServerFolders\Music\EAC\Electronic\#ambient\José Padilla
INFO  2012-12-18 18:14:34.832 [pool-30-thread-1] Exception in thread "pool-30-thread-1" java.lang.NullPointerException
INFO  2012-12-18 18:14:34.833 [pool-30-thread-1]    at net.pms.dlna.CueFolder.resolve(CueFolder.java:170)
INFO  2012-12-18 18:14:34.833 [pool-30-thread-1]    at net.pms.dlna.DLNAResource.run(DLNAResource.java:763)
INFO  2012-12-18 18:14:34.834 [pool-30-thread-1]    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
INFO  2012-12-18 18:14:34.834 [pool-30-thread-1]    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
INFO  2012-12-18 18:14:34.834 [pool-30-thread-1]    at java.lang.Thread.run(Unknown Source)
DEBUG 2012-12-18 18:15:05.276 [UPNP-AliveMessageSender] Sending ALIVE...

You can see that it has set the profile for the device as POPCORN Hour automatically. Any thoughts on how to resolve ?

Thanks

[Raptor399]

You can see that it has set the profile for the device as POPCORN Hour automatically. Any thoughts on how to resolve ?

Thanks

First of all you have to realize that PMS does not know which device connects. It has to guess that from the incoming requests. Luckily devices tend to send fairly distinct request headers, so PMS can tell them apart.

PMS does not know your Humax Fox T2, but appears to be sending similar headers as the Popcorn Hour.
I don't know if that is harmful. To be safe, you could try to create a specific humax.conf as described in the FAQ:

FAQ: My device is not supported by PMS. How can I create a custom renderer.conf to make PMS recognize my device?

However, I'm not sure that a humax.conf will fix the reboot on the Humax side when scanning files.
It sounds more like a bug on the devices side: it should never be possible for any external DLNA request to cause a reboot when requesting files.

Have you tried asking on the Humax support forums?