• Status Unconfirmed
  • Percent Complete
  • Task Type Feature Requests
  • Category Bootloader
  • Assigned To No-one
  • Operating System xDuoo X3ii
  • Severity Low
  • Priority Very Low
  • Reported Version Daily build (which?)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by salty-horse - 2022-10-04
Last edited by salty-horse - 2022-10-07

FS#13366 - Bootloader should offer to autorestart when rockbox could not be loaded

I’m using Rockbox (build from 2022-05-03) with xDuoo X3ii.

Sometimes the bootloader fails to load Rockbox with the error “Cannot boot Rockbox”. After a single restart of the device it loads fine.

The current bootloader makes this restart process very cumbersome:

1) When starting the device without user interference, the bootloader tries to load rockbox and gives the error
2) Then the bootloader is back in the main menu, and after several seconds of no user involvement, will attempt to load rockbox instead.

I haven’t tried, but I think this loop will continue indefinitely.

If I wish to restart the device, I need to follow these steps:

3) Choose the configuration option in the bootloader, and choose the restart action.
4) Wait for the device to restart. Then the bootloader will start with the “Settings” option selected by default (since it was the last selection).
Before it auto-selects it, I need to quickly switch back to the Rockbox menu option.

During this entire process, the device requires my full attention, which means I can’t just turn the device on in my pocket and wait for it to autoplay.

To ease this error-recovery, I suggest the following:

1) When Rockbox fails to load, a countdown timer will start, and when it’s over, the device will automatically restart. The user can interrupt this process with any button press.
2) When choosing the settings option in the bootloader, I don’t think the bootloader should remember it for later. It should only remember the Rockbox option, or the “native firmware” option.

This is a bug: the bootloader says "rockbox not found" even though rockbox is there.

If that were fixed then an "auto restart" feature would not be needed. And in any event I doubt putting the player in a boot loop is the wisest thing to do.

1. should I open another bug about the failure to launch? Note that it's not a "not found" error, it's "cannot boot".
2. I can see how a restart loop is more risky than the current loop. Then how about just pausing the auto-confirm timeout when it goes back to the main menu, and making sure the bootloader shuts down after X minutes of inactivity?

1. Yes, it's better if you open another bug because "feature requests" seem to be hidden from the bug list by default.
2. Stopping the automatic timeout after a failed boot and shutting down on inactivity sounds good to me.


Available keyboard shortcuts


Task Details

Task Editing