I recently purchased a Zidoo Z9x 8k and hit the issue that's been reported here in the past where the Zidoo boots to the dashboard, hangs after a couple of seconds, then reboots endlessly when connected to wireless. I believe I've figured out what is happening. It appears to me that when the Zidoo boots, with the default settings, it is trying to load/refresh the posterwall before the Zidoo has established the wireless network connection and hits a fatal exception because it has no network connection fully established yet. I've noticed that under normal circumstances, the Zidoo will display a message stating it is refreshing the posterwall in 4-5 seconds, which lines up with how long it takes until the Zidoo reboots itself. I delved into the settings and hit upon what I believe is the solution. Solution: Turn on "Use Local Posters". The Zidoo then boots and doesn't crash/reboot, which indicates to me that it is loading from disk instead of network and no longer trying to access the network before the connection is established. This also explains why the workaround of using Ethernet doesn't encounter the problem, Ethernet connection is established faster than the delay in refreshing the posterwall so it doesn't enter the state where it's attempting to get an image without a network connection. It's possible to trigger this issue in another fashion as well. I have a DAS with three disks. It finds the three disks in succession, notifying me after each is found. If I go to the posterwall and try to scroll after the first disk is found but before the second or third, I'll get the same reboot. Summary: I believe the Zidoo has an unhandled exception with loading posterwall images and being unable to access the image source causing it to crash/reboot. Switching to Local Posters and letting it find all connected disks before attempting to navigate is resulting in a stable system.
@Markswift2003 the above looks like a good analysis and should be reproducible, thus fixable. Can you check and add to your list please?
As @Gatt9 says, Wifi takes a little longer to connect, probably more to do with authentication than anything else - you can see this by sharking the network but equally it's easy to see if you just boot the box and immediately open HT - as long as you're using network sources and have "Display poster for unconnected devices" turned off, you get this: But then, within a couple of seconds the network is up and all works fine with no reboots. If I enable "Display poster for unconnected devices" then I get posters up immediately on boot although obviously have to wait for Wifi to connect to actually access a file - but by the time you've clicked through to a poster, odds on the network is up. But again no rebooting. Use Local Images First or not makes no difference to the behaviour (other than having to recache when switching, which is normal). So I can't replicate this behaviour I'm afraid - it must be something specific to the environment, but what, I don't know.
Maybe I can help... I've been struggling with these restarts for a few days—when listening to music from local files and Spotify—and finally, after trying various options, I managed to pinpoint the cause. In my case, simply setting HDCP to "Off" was enough to stop the restarts. Sorry for my English, I'm using a translator.
Can someone give a simple set of instructions on how to find this setting? I cannot find it and I've been looking for an hour. Something like this would be great to show where this setting is buried in the menus: Step 1 > Step 2 > Step 3
