Miyoo Flip device support (my355)

[apommel]

Make the my355-latest branch up-to-date with the main branch.

As such, the new kernel CPU governor and hook feature were added, similarly to what was done for the other platforms.

In addition, the following improvements were made:

• Small refactoring of the sound settings code to use tinyalsa instead of system calls.
• Fix of an issue where a jack plugged in before boot was not detected.

I have made other small changes (to allow to reach lower volume and brightness), but we can cover those in another PR as they are more dabatable.

[Lawstorant]

Okay, I think you might be right, it's likela a specific app issue because it behaves normally in the main mode, in emulators etc. I'll search for the app again and probably create a general NextUI issue.

And thanks for enabling all emulators. I missed the Neo Geo very much from the April builds like 6.9.0 beta :D

[apommel]

I have merged the main branch, including the h700 changes, into the branch and it is up to date with the latest status. I made some small adjustments for HDMI so that it was more consistent with how it was implemented in h700.

I also had recently added a feature to control the Flip status LEDs in the settings, but this was touching too much shared code for a single device feature, so I reverted it, and I'd implement it as a Pak instead.

It is ready for review from my point of view @frysee. Regarding the Bootlogo Pak, I was under the impression that it would be moved to a stand-alone Pak as it was starting to ship quite some amount of images. What's the plan on that? I was planning to update this Pak with Flip support while benefitting from the logo selector screen.

I'll also produce a new pre-release so that users can test this updated status.

[frysee]

Yeah, theres a couple of topics that we moved out of the initial PR scope. Bootlogo should just move out and become a standalone pak, I think.

I guess the plan would be to move it to its own repo to get the NextUI release size down, while initially maintaining the naive implementation it currently has. I could see it being beneficial to be a bit smarter about it, and maybe just pull down the images lazily instead of shipping all of them upfront.

[frysee]

As far as my355 is concerned, I'm a bit undecided on what do do. I appreciate all the effort from you and @adthing that went into this, but I am conflicted on supporting the platform for the forseeable future. Compared with the other devices there seems to be rather low interest, and I'm also not super fond of the device myself. I'm not ready to just banish it to the graveyard yet, but the thought crossed my mind.

[apommel]

I thought that was indeed the case. From my side, I am not keen on maintaining a separate fork forever, and the time I've spent on the device was clearly with the objective of merging the work into NextUI.

I'd say that the fact that the device is relatively 'low interest' can be seen as a positive too. Once merged, I don't expect a lot of issues specific to the device to come up. The device-specific code is also relatively self-contained, so I don't expect too much maintenance burden once the code would be merged. But you obviously have the final call on that. The problem that all contributors would not be able to test their features on all supported devices is also already existing, whether Miyoo Flip is added or not. On my side, even after the branch would be merged, I'd be happy to test new features to ensure they work properly on the device when relevant.

I'll let you think a bit more about what you want to do. I think it's fine to have 6.15 released with H700 support and decide a bit later for the Miyoo Flip.