@gn-lin s21 is a different phone, has a different SoC and not really related to this s20 fe effort

@AppLee said in Can it do External Monitor + Screen Off?:

And how would you lock the device if not with the power button?

With a shortcut on my keyboard connected via USB-C or Bluetooth. Again, this is not a broken-device use case.

@AppLee said in Can it do External Monitor + Screen Off?:

The behavior of Ubuntu Touch is as expected.

Not really. It should be possible to turn off the device's screen with a power off button and use the device with External Monitor. I don't want my device's screen to waste energy and show anything while I'm using the device as a portable PC.

What are my possible actions if UBports boot.img is couple of MBs larger than target boot partition?

@kugiigi it's software - stock rom does this fine

Can Ubuntu Touch use External Monitor with Screen Off?

I have a device (Galaxy S10) with broken display and I tried some old UT build (16.04 I think) for it. It could only do HDMI output to External Monitor while the Screen was On. When I turned the screen off, the External Monitor locked. This is undesirable in my situation - the device's display does unwanted clicks.

Does it still work the same way or has there been some settings/improvements added?

@retrocountry
This should work for you:
https://docs.ubports.com/en/latest/porting/build_and_boot/standalone_kernel_build.html
Use halium 10 as base.
Deviceinfo values can probably be reused from the Droidian port:
https://github.com/droidian-starqlte/android_kernel_samsung_sdm845/blob/droidian/debian/kernel-info.mk

Check if your device is treble-compatible using this app:
https://f-droid.org/packages/tk.hack5.treblecheck
Run from stock ROM. Also report the VNDK version. This would decide further actions

The porting guide requires img2simg and simg2img which are provided up to Ubuntu 22.04 and not later.
You can install these utilities using this snap:

sudo snap install android-platform-tools

sudo snap connect android-platform-tools:adb-support
sudo snap connect android-platform-tools:block-devices
sudo snap connect android-platform-tools:raw-usb
sudo snap connect android-platform-tools:removable-media
sudo snap connect android-platform-tools:network
sudo snap connect android-platform-tools:network-bind

sudo snap alias android-platform-tools.img2simg img2simg
sudo snap alias android-platform-tools.simg2img simg2img

@faveoled that's where kernel config is stored. deviceinfo is outside of sources directory

@shadan write it line-by-line, fill some data from unpackbootimg

@shadan looks like there are two ways - one involves compiling full halium source, and the one I suggested involves just compiling your own kernel. I'd prefer the latter as I'm a newbie to this

@shadan are you using an old guide? I think you should use this instead:
https://docs.ubports.com/en/latest/porting/build_and_boot/standalone_kernel_build.html

Hello,
Could I use mkbootimg with externally compiled kernel (with the kernel config changes needed by halium) to create halium-boot.img?
The kernel requires some specific tooling. That's why I'm not following the official standalone kernel guide.
If it's possible, I need a way to create boot initramfs.