[Android Software Development] spocky12:
Seems like it's an international model with Android 9. I haven't found how to root these models yet (bootloader and recovery are both encrypted)

Probably the same as CInema 4k Pro (using FengOs). You should be able to replace the launcher. Neither root, nor any display profiles yet.

Thanks ! If your device has been rooted, you need to unroot it before installing OTAs. No android major version upgrade is possible (or "maybe" with a lot of work and major risks of bricks, so I won't try it).

Can't test on my devices (which have a power button, so no automatic power on when plugged in). I might have found a workaround. I'll contact you when it's ready to test.

Great news !

Unfortunately, I'm stuck to the stock revision (1229). Somehow during my exploration of the device, it seems I managed to get a file written on the readonly system partition (don't know when and where, it was not on purpose, probably one executable that wrote a log somewhere...). Anyway, now, I'm unable to make any update. Worse, it's the 1st firmware, with a bug that forces to power it off twice (first time I power off, it reboots automatically).

Only a full firmware could fix it, but none are available. Guess I'm gonna have to live with it :rolleyes:

I can't explore much of the OTA without installing it (it mostly contains patches to files and rare complete files). But I could see that the memc component just had a firmware update (probably improvements). Don't know if they plan on enabling it on the cinema 4k pro, but other fengOs devices with memc enabled will probably have this update too.

Are you sure you mounted /system ?

Non system app have little control over power manager. I'll see if I can find a workaround.

Make sure the usb device is already plugged in when you reboot your device. Then it should be automatically detected/mounted

Until it can be rooted, support is limited (as is support for anglee) but you should still have a few features available.

Time, patience, luck...

I have this device. Seems that the bootloader won't boot any recovery that is not specifically written for it (in OTA, the recovery seems encrypted, referencing "AMLSECU!"). And even with the magic uart cable, I only have a console acces during bootloader phase. In recovery, it used to provide a root console which is not there anymore...

International devices behave the same, so maybe there's information on this behavior somewhere for some other device (mibox, mi tv, or even amlogic non xiaomi device). I already searched a bit on 4pda, but couldn't find anything relevant. Which doesn't mean it doesn't exist.

Regarding you issue, you can totally fix it by script : with adb, "reboot -p" will power down you device, no root required.

Thanks for sharing your experience (and for the donation) !

Sorry, I have no idea. But if it's an unwanted behavior, they might issue a new OTA to fix it pretty soon.

I've just tested, it works with a physical remote (eg: hitting F3 on a keyboard starts HDMI3). It seems like keyevents sent through ADB totally bypass accessibility services. Unless there's some parameter I'm overlooking, there's not much I can do :(

Anyway, there are other means to launch HDMI input from adb, such as :

am start -n com.spocky.projengmenu/.activities.input.SourceHDMI3Activity

Perhaps a buttons remapper app may be able to make a shortcut to the settings activity ? (just a supposition, I've never used one)