Either SOCKS or MTProto, both will work actually. And you can find the latter spread across select Telegram channels and connect to one of them with only few clicks.

Not indicative of final #grus ~ms3 product, may subject to change depend on how it performs

Another moment where I forgot to automatically upload the build

New #grus test build (4.9) with branch android-10.0 at commit a82323948530 ("ARM64/dts: grus: Make several lower CPU frequencies available").

Some inlining changes, JankBenchX score is significantly worse in some aspects, but tell me if there's any change in smoothness in @sdm710dev

New #grus test build (4.9) with branch android-10.0 at commit 9b53f184e791 ("ARM64/dts: grus: Allow 576 MHz to be selected").

New #grus test build (4.9) with branch android-10.0 at commit 2ae02443a814 ("ARM64/dts: grus: Allow 576 MHz to be selected").

#X00T: TWRP build that uses msm-4.14 kernel and will only handle FBE decryption. It can be used to flash ROMs that ship 4.4/4.14/4.19 kernels. Crypto blobs are updated to latest 10 Beta for this device to accomodate the support.

Whoops I forgot to properly name it, but anyways you know it.

#X00T: This one is just as straight-forward as usual: TWRP 3.5.0_9; except, that several system blobs will be built from source instead.

New #grus test build (4.9) with branch android-10.0 at commit 2ae02443a814 ("ARM64/dts: grus: Allow 576 MHz to be selected").

This is just a relink with Binutils 2.36.1

Test build that recompiles latest staging with latest internal release of SDClang; vDSO32 has to be disabled for this build due to compiler-related issues.

New #grus test build (4.9) with branch android-10.0 at commit a0fb455a64d0 ("BACKPORT: arm64: vdso32: add CONFIG_THUMB2_COMPAT_VDSO").

vDSO32 re-enabled. Release build will still be compiled with SDClang 10 until ready-for-distribution build is made available by Qualcomm, either on their developer website or via BSP.

New #grus test build (4.9) with branch android-10.0 at commit d381c2076ae5 ("Kbuild: Zero-init uninitialized locals for security").

New #grus test build (4.9) with branch android-10.0 at commit 6f84b7c7c17d ("Revert "fdt: Properly handle "no-map" field in the memory region"").

New #grus test build (4.9) with branch android-10.0 at commit 2a84a70cb890 ("Kbuild: Zero-init uninitialized locals for security").

DO NOT FLASH, I accidentally set a wrong ifdef guard which breaks booting for the same reason as what I wrote on latest post of @KudProject. Wait for next semi-automated build instead.