TriForceX/MiyooCFW

When AutoStart is enabled, gmenu2x loses information about the setted skin after exiting the application (and shutdown is initiated by the system)

MayanKoyote opened this issue · 1 comments

When AutoStart is enabled, gmenu2x loses information about the setted skin after exiting the application (and shutdown is initiated by the system).

Steps:

  1. The skin changed from the 'default' skin to (in my case) 'Legacy' skin.
  2. Autostart is switched to ON in settings. Settings saved.
  3. The application is started then exited. The screen turns black and then switching off.
  4. The console turns on (manually). The 'default' skin design is visible on screen.

Builds on which I noticed this: 752d0a6, f4f5811. I have not tested earlier builds for this.

I am attaching several gmenu2x configs that I copied at different stages.

  1. Right after the fresh firmware flashing. Nothing was done.
  2. Skin was changed to "Legacy".
  3. Autostart shut down the system after exiting the application. The console is turned on after this.

The latter clearly lacks the setted skin.
gmenu2x-1-firstboot.conf.txt
gmenu2x-2-theme_set_to_legacy.conf.txt
gmenu2x-3-autostart_cycled.conf.txt

Fine-tuned sed cmd after app shutdown for gmenu2x.conf with: MiyooCFW/gmenu2x@28a7f05 . Should be ok 🙏