Terminal Installation Error

[Harsh-Malakar]

Summary

I am installed klyx and when i try to install terminal then i get this error

Klyx Version and System Specs

klyx-release-v2.0.1+preview

[SPORIMEstudio]

Hey Harsh!
First check what is your CPU-ABI. Use CPU-Z app download it from playstore and look for abi section or use termux if you have. Write this command "getprop ro.product.cpu.abi"
If your armeabi-v7a so klyx not support ARMv7 yet if it's arm64-v8a so it something else

[Harsh-Malakar]

Hey Harsh!
First check what is your CPU-ABI. Use CPU-Z app download it from playstore and look for abi section or use termux if you have. Write this command "getprop ro.product.cpu.abi"
If your armeabi-v7a so klyx not support ARMv7 yet if it's arm64-v8a so it something else

i have arm64-v8ab

System Info:
System : Android 14
Host : iQOO I2208
Kernel : 5.4.281
CPU : QTI SM4375 (8 vCPU)
Architectures : arm64

[SPORIMEstudio]

Harsh,
I don't know why it's not working I check bit code arm64 supported by Klyx but I don't why it's happening may be the reason is file is not correctly downloaded or not renamed because as shown in the code Ubuntu downloading with this "https://cdimage.ubuntu.com/ubuntu-base/releases/24.04/release/ubuntu-base-24.04.3-base-arm64.tar.gz" and then the file name change to the sandbox I don't find out the method where this renaming happening.

[itsvks19]

@Harsh-Malakar @SPORIMEstudio this issue has been fixed in last few commits. it will be available in next release.

[itsvks19]

@SPORIMEstudio

I don't find out the method where this renaming happening

renaming happens here

klyx/klyx/src/commonMain/kotlin/com/klyx/terminal/TerminalManager.kt

Line 126 in 796dd28

outputPath = "${Paths.tempDir.join("sandbox.tar.gz")}"

[SPORIMEstudio]

@itsvks19
Why you don't add support for ARMv7?

[SPORIMEstudio]

@itsvks19
Why you don't add support for ARMv7?

[itsvks19]

ARMv7 (32-bit) support was intentionally not included.

The app targets API 26+ and focuses on performance-intensive features (native libraries, large file handling, etc.). In 2026, the vast majority of active devices running API 26+ are ARM64 (arm64-v8a). Supporting ARMv7 would:

Increase APK/AAB size due to duplicated native libraries
Add additional build and testing complexity
Require maintaining compatibility for very old 32-bit hardware
Provide limited real-world benefit, since most developer devices are 64-bit

Since this is a development tool aimed at modern devices, prioritizing ARM64 allows better performance, stability, and maintainability.

If there is significant demand or concrete use cases for ARMv7, I can reconsider in the future.