Leaderboard

I cannot reproduce this with my Pro1-X. Not using Termux, though. I'm running Debian 11 in a (rooted) chroot of LOS 20.0 and use ConnectBot as my terminal emulator. Your script works fine (with some trivial changes to match my environment). As, also for you, the keyboard behaves normally in other apps, it seems to me that you are somehow triggering a bug in the terminal emulation of Termux.

@Hook, It was when i tried to save a file in nano with Ctrl+x. IDK why it happens but i have to full exit Termux to recover a working environment. In others Apps, there were not any issue with the Keyboard. So i decided to reinstall Termux from scratch. And, or now, to double char anymore. Wait & See. Edit: This issue is back. I must exit Termux and clear the cache to get back my keyboard working with Termux as before. Very strange.

One clarification. Under what conditions is this happening? When you run the script? When you are using the script editor? When you are using anything in Termux? Or is this something that is happening everywhere, whenever you type on the keyboard? I don't have any good answers, btw, but I would think anyone with answers would need to know that.

It is not a situation I have experimented with, so can not say. You might try some software like like e.g. KeyEvent that shows the make and break codes for pressing and releasing each key.

SHA-256 confirmed, working just fine with only the zip file. (I was already on LOS 20) Camera is working fine on this one. Thank you!

...Solder Directly ? NO! Is needed to use Fx electronic from old battery for correct charging. RK61 batt have only two pins on connector

I've uploaded my latest build of LineageOS 16.0 for OG Pro1 (SD835) to https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 The ROM dated "20240807" gives you backported Android security patches up to the July 2024 ASB. There are no other changes since last time. The full patchlog, documenting all my changes relative to unmodified LOS 16.0 is also available, as usual. Have fun.

lineage-21.0-20240615-nightly-pro1-signed.zip: https://mega.nz/file/05slyRjb#u58reQoMdiZAgDM0Wy7DJJ5T8jO9MEoNIiPs1jIpmP8 boot.img: https://mega.nz/file/xlkjTLZA#XDqVC2BDpTXI4Wo2HoEGyQWMDHZzfdroGOEEdmiCECw I don't have dtbo.img or vbmeta.img, but I don't believe they're usually required. Of course you shouldn't trust me blindly and verify the signature of the image here: https://download.lineageos.org/verify Still hope this gets resolved normally soon. I don't really want to wipe but could use the camera quite a bit in a couple of weeks.