Z9X 8K keeps rebooting directly when connected to 5Ghz Wifi

New device. connected wireless (through 5Ghz) to Synology NAS with media through SMb. Scanning media files goes well. So at first no problems. But after about 10 hours: When library is complete.... the device keeps rebooting directly after startup (even when NAS is disconnected to rule out media errors). But it only reboots when connected to my 5ghz network. Not when connecting to the 2.4ghz wifi network (but that one is to slow). I tried a factory reset.... no dice. Same result. At first no problems..... but a few hours later..... continuing bootloops. Any thoughts?

 

I included a video showing the problem:

 

Hi there. Our support team has contacted the agent for solving this issue. Thanks for your feedback : )

 

Hello Zidoo, please provide me with an update. After sending the requested info I did not receive any reply from your support team. Problem still exist.

 

Hi, thank you for your patience. I confirmed it to our developers. They didn't reproduce the issue yet, could you please copy one of the episodes to the internal storage as a test?

 

I do not understand what you want me to test? You want me to play a movie located on the internal storage? I will.... but I cannot get that far when my device is connected to my 5ghz wifi network.... the player wil reboot before even starting the movie.

 

I'm sorry that we've mistaken the conversation pages, that's another conversation.
There's nothing new about the issue you encountered
I will ask the R&D team again recently.

 

It started to happen to my zidoo z30 pro.
When in 5g zidoo reboots.
I disconnected all drives and took out the internal hdd.
Zidoo will reboot itself, sometimes in a minute and sometimes in a couple of minutes and sometimes it will work for an hour before rebooting.
I did a factory reset and no help.
Any luck finding a solution?

 

Hello Zidoo, I shared all the information requested but I get no fix or information on a time line for a fix or feedback off progress. Please inform me with what steps Zidoo is taking to analyse and resolve the issue. The brand new device is still useless this way. Could it be a faulty device (instead of a software error..... for example a bad wifi chip of antenna?). Please communicate better!

 

If i use 4g everything is ok, as soon as i start using 5g zidoo starts rebooting.
My z30 pro is 15 months old and i never had similar problems.

 

Sorry, there's nothing new yet.

 

I tried the new firmware. Lots of fixes (nice!) but regrettably.... no wifi fix:

 

Да, это проблема у меня на Zidoo z9x 8k может по несколько раз перезагрузится пока не поймает wifi сигнал даже 2.4ГГц.

 

Thank you : )

Yes.. Sorry. I mentioned it again anyway. Thanks for your patience.

 

I'm having this issue as well. I'm turning off wifi for now to see if it helps.

 

l alo have this reboot issues. Waiting for fix..

 

Is this the "official" place to report on this or is there a support ticket system?

 

No support ticket system. This is a customer forum that Zidoo do look at - so best place to report issues.

 

I can confirm I don't see the issue when I turn the wifi off. I loaded a CPU monitor app and it doesn't seem like CPU is spiking when this happens, although I do see CPU usage as higher than I would have expected when nothing is happening on the device.

As soon as I change the network to 5G, the reboot cycle starts. The OS loads and then you have about 5-7 seconds before it freezes and reboots. You have to find a moment in time just after the system boots to turn the wifi off to interrupt the continuous reboots.

Is there another app I can load to test anything?

The only risk is that if I end up in a continuous reboot cycle, it's very hard to get the system back stable by turning off wifi quickly.

I'm receiving some network cables later today that I can use to connect to the Internet without wifi so I could possibly do some diagnostics if needed. Happy to help.

 

I would suggest Ethernet is the only way to go, you'll get zero issues. I appreciate in some homes this may be a logistical issue