FK is just available on android unfortunately. Im going to be testing out @miniconfig’s remote assist display integration one of these days but if u feel adventurous, you could try that instead of chromium.
Hey Folks, not usually one to post like this but i need some help or a nudge in the right direction. I’ve followed all the steps in the windows installation guide and can complete the flashing procedure. when i reboot at the end of the guide the device reboots flashing lenovo like you stated, then i see the postmarket screen. finally i get to what appears to be a android lock screen with text saying swipe up to unlock. problem is the touch input doesn’t seem to work. am i missing something silly? Thanks in advance.
Did you flash a mismatched set of (lk2nd, userdata) images?
The same thing happened to me when I compiled a lk2nd from git over a month ago, and flashed it to a device that was using a rootfs phosh image from around June 2024
The boot sequence is device bootloader → lk2nd → linux kernel: in the 1st step, the hardware panel selection is given by the bootloader to lk2nd, in the 2nd step lk2nd boots the kernel using /boot/extlinux/extlinux.conf which mentions “fdt /apq8053-lenovo-cd-18781y.dtb”
In lk2nd git log, commit 055f10ffe5382bb382dfd52f31b9b24729fddc51 changed how the dtb format to refer to the panel in Aug 2024, but a DTB compatibility problem doesn’t make much sense because the dtb /boot/apq8053-lenovo-cd-18781y.dtb is on /boot from userdata1 (/dev/mmcblk0p51 used by the device mapper, check dmsetup ls --tree) while lk2nd is on the EDL boot (/dev/mmcblk0p21 given /dev/disk/by-partlabel/)
However, I solved my problem just by flashing an older lk2nd (less TBW, better for the eMMC that flashing userdata) using a 300kb image from thinksmart so it’s as if the .dtb from /boot was ignored and the one from the boot partition used instead?
On the June 2024 image, the /boot/apq8053-lenovo-cd-18781y.dtb is about 65145 b with the md5sum 42d71c3bf3b7b1ae3cc10007477f581e while a 2025 dtb is slightty bigger (65531) and has the md5sum 60326c220ada4705f05627b1a7dc768a
After decompiling the dtb files to dts using dtc, then doing a diff, I saw many small differences, including the key one mentioned in 055f10ffe5382bb382dfd52f31b9b24729fddc51 for touchscreen@38 and touchscreen@48
I still don’t understand precisely why the touchscreen issue happened, or if the dtb could be ignored, but somehow flashing the old lk2nd fixed the touchscreen problem, so you may want to try this silly fix!