@Pulsar33 and @AppLee Thanks for your replies and sorry for putting my problem so poorly.

I don't want the screen to be always on because I'm trying to make an alarm clock. Therefore the screen has to go inactive ("dark") eventually - else I can't sleep :).

The "snooze" button of the UT clock app is pretty tiny. When I finally found it I'm wide awake.

Therefore I'm trying to make an app with a huge "snooze" button that's filling the whole screen so I just have to tap on the display to hit it. But the screen has to be active to do so.

I want my script to do what the UT-clock-app does: Activate the screen when the alarm goes off.

I have a Tcl/Tk script started and running in the container. After a while - say 10 min - the script will create a window with a button to press.

Meanwhile the display has gone dark. Therefore I have to press the (hardware) power button in order to activate the display before can press the said (software) button.

Is there any way to activate the display "from within the container" to immediately be able to press the said (software) button and avoid pressing the power button?

Thanks in advance!

I have experienced a huge difference between 1280x800 and 1920x1200. I'm having a X605F which I bought from a shop who sell used devices (am I allowed to put a link here?). I'm happy with it.

@xekuta747 It's supposed to be seen in "Info" and so it is on my phone. But on my tablet it is not. Maybe you can find out by the date

@Luksus
UT just booted! Great job!

The fastboot -w command does not work. I got

xxx@MintXfce:~/Programme/UBPorts/Lenovo X605F$ fastboot -w
wiping userdata...
Invalid erase-block-size 512: must be a power of 2 and at least 4096.
Invalid logical-block-size 512: must be a power of 2 and at least 4096.
mke2fs 1.45.5 (07-Jan-2020)
/tmp/TemporaryFile-kpVmgi: Nicht implementierte Ext2-Bibliotheksfunktion beim Erstellen des Superblocks
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata

Had to use twrp.

@keneda Yes, but this time I tried it on Android 9. The same command failed on Android 8 before. But meanwhile the device was updatet.

@luksus Will I still have to flash Android 9 stock firmware or may I skip that and go straight to flashing UT?

@luksus @MrT10001

Surprise! I found this on https://forum.xda-developers.com/t/guide-unlock-root-lenovo-smart-tab-p10-tb-x705f-by-chaser42.3956198/ :

NOTE THAT THIS GUIDE IS ONLY APPLICABLE IF YOUR DEVICE IS RUNNING ANDROID 9.0 (PIE). If your device shipped with Android 8.0 (Oreo), you must upgrade because the Oreo bootloader does not allow a permanent unlock.

And literally simultaneously a new Android system update popped up on the device (there had been two since thursday when I got the device). And this time it updated to Android 9.

So I tried and I got

xxx@MintXfce:~/Programme/Android platform tools/platform-tools$ ./fastboot flashing unlock
FAILED (remote: 'Need wipe userdata. Do 'fastboot oem unlock-go'')
fastboot: error: Command failed

Then of course I did what I was told and got

xxx@MintXfce:~/Programme/Android platform tools/platform-tools$ ./fastboot oem unlock-go
OKAY [  0.044s]
Finished. Total time: 0.044s

@ luksus You will have to update that part of the install instructions I guess. I will keep going and give a report after success (hopefully).

@MrT10001 Thanks again.

@mrt10001 Thanks for your efforts!

Have you tried another USB cable?

Yes I have.

Have you double checked USB debugging is on

Checking it every time before I try.

and not set to MTP? (if MTP is set it will usually show up on the PC as an external storage device/tablet)

This is new to me. Instructions I found on www say it must be set to MTP. What do you recommend? I just tried "Wird aufgeladen" (~ charging only) - didn't work out.

Have you double checked OEM unlock is on?

Checking it every time before I try.

Has the tablet ever had a custom ROM, or been rooted in the past?

No idea.

Are you running Fastboot from the Android Studio folder?

Yes.
./adb ... and ./fastboot ... (./<command> on Linux)

Have you tried another operating system? (if it won't play with windows, I use Ubuntu and vice-versa).

MX Linux and Mint Linux. I have no windows machine around.

Have you read this?

Yes. I guess I've read every single instruction on how to avoid the (remote: unknown command) error.

@mrt10001 True. Therefore the install instructions include flashing Android 9 stock firmware. But in order to do so I have to unlock the bootloader before.