Nothing to be afraid of. Undocumented functionality in RockBox. Forget it, reboot, and enjoy untils it shows again.
---
More seriously. RockBox (RB) is a wonderful piece of software written by benevolents, who are comitted to offer better firmwares for Digital Music Players. Their lair is here :
https://www.rockbox.org/
The initial release was in june 2002. A few weeks from now.
They developped RB, and ported it to various devices, adding a functionality here, removing a bug there. Quite a tremendous work and an astonishing result. Do you know you can play Doom on RB ? Do you know what Doom is ?
They are still active. After all those years. Chasing bugs, porting to new devices. At their pace.
They have not ported RB to a new device for a couple of years, although they are working on it. No release for quite time. They are working on a port to XDuoo X3 since december 2015.
http://forums.rockbox.org/index.php/topic,51139.0.html
Here comes XVortex. A cool russian guy. He is not in the RB team, but decided to port RB to XDuoo X3. And did it. Made his firmware public. Made his sources public. RB team reviewed it, someone said the code seems excellent. Although XVortex is using their source code and their logo without explicit autorisation, and doesn't mention the copyrights he uses.
http://xvtx.ru/rockbox/
XVortex maintained his code, and made a few improvments. The bug (undocumented functionality
) you meet has been reported for some monthes, but nothing seems done about it. There is another bug, more frequent, concerning USB accessibility of the device, when RB is active. Another one is the 3 seconds delay when start playing a file. None being investigated neither.
So, if any bugs shows up, there is not much about them you can do. Return to official firmware (OF) ? Make a note to XVortex, asking hom to correct the bug ? Done, with mixed results. Offer to pay him for his work ? Wait for RB's official release ? If the bug doesn't bother you to much, just endure it and go on ? I choosed to endure. I think I may had this bug twice or thrice since july.
Anyhow, it's not because your device is wrong. No hardware failure there. Just reboot.
Thezac.