[Android Stick & Console RockChip based Computers] Barkuti:
Major update (and further updates on the way):

For whatever reason I finally ended up dealing with an X96 X6 TV box from Shenzhen Amedia Technology.

The box runs Android 11, its remote features bluetooth connectivity and works as an air mouse with a pestering brief standby time (so better press the air mouse button each time it is picked up).

The box comes rooted, lacking superuser rights management application and using an su binary located in a typical location (/system/xbin folder if I recall correctly). I discovered this after installing the Magisk application, patching the boot partition and rebooting, as (much alike what I reported before on post #8 here) Magisk then starts complaining about a “competing su binary” as the app is open. I solved this problem by renaming the preinstalled su binary (deleting it would also solve the problem I guess).

The X96 X6 is in the same league as the H96 Max V56 I dealt with before, with the same basic problems, but with the X96 X6 I had time to investigate much deeper and solve most of them.

The issues with the Enter key and external keyboards can be fixed, but it has its trickery. In the first place, the reason why I couldn't fix the “Generic.kl” file in my previous attempts is due to a weird thing which the @#$% developers did with the /system partition: there is an “Aging_test_video.mp4” file located in the /system partition with around 15 MB of size which, apparently, fills the partition entirely or even surpasses its size (?); I can't say for sure if it's the latter, but to my reasoning it must be the latter because that explains why I couldn't save the fixed “Generic.kl” file (whose size was smaller!), and I was ending with a fully empty file instead, why I couldn't copy/paste the fixed file from another location or essentially why I couldn't do anything to the files in the /system partition besides renaming them.

One of the botches the X96 X6, H96 Max V56 and probably all these boxes share in common is that their Android system has two settings applications: the stock one, and another one whose package name features the “TVsettings” string as far as I recall. I won't comment much further for now except that I had done many installs and modifications to the X96 X6, and my last move involved freezing the TV Settings app to see if that would fix the inability to pair bluetooth peripherals using the stock settings app. Unfortunately, the freezing of such app resulted in a non-booting system; others call this a bootloop because you end up seeing a never ending system loading animation on the screen, although what actually happens is that something critical crashes upon booting and so the system fails to boot. I'd love to see text messages of the system parts being loaded and etcetera, very much like in the days of MS-DOS or in Linux with verbose booting enabled, but stupid retarded splash screen booting is all we have in Android unless we install some modification (interesting: [MODULE] LiveBoot - Verbose boot animation). The TV Settings app allows pairing of bluetooth devices, whereas the stock Android one fails; when pairing of bluetooth devices is done with the stock settings application a confirmation dialog seems to appear, although dissappears almost instantly, giving no chance of confirmation.

Oh! To add more fuel to the fire, the TV Settings app is recognized by the system… as a launcher application! For the love of God, how retarded this is! Only certain launchers will list other launchers in the app drawer, so as it is executing or launching the TV settings app from an alternative launcher most likely forces you to either change the launcher (using Settings) to the default MBoxLauncherNew one, as it has a link to open it, or to make a custom desktop shortcut with something like App Manager.

Do you understand why I say that these Android boxes or Android boxes' firmwares are really botchy?

I now have to endure the reinstall of my previous software and fixes, plus I'll have to address certain problems with external joysticks or gamepads in MAME4Droid.

I miss TWRP, by the way.