not install the package : qemu-user-aarch64

[Ashes-Snow]

I can't get into the codefa 1.5.0
Let me show you screenshots

And ,when i try to install this package ,there is no apt tools and dpkg tools ,so i download the code of dpkg,but the question comes. Because some tools and components like gcc... are missing , i can't complete the compilation and installation of the dpkg source code.

By the way,
android os : android 13,
device:xiaomi pad 5 pro 5g
I just update the Android webview on google play,i am sure it is absolutely no bussiness with android webview.
and i try to use browser to open ,is failed to link to ubuntu,here is screenshot

and when i try to debug at termux i was find that codefa will be software crashes when my Bluetooth keyboard connected or disconnected ,this issue can be reproduced stably regardlessc of my uninstall and reinstall.

[Ashes-Snow]

If you need a log of the software crash, please let me know and I will send it to you in the qq group

[brian200508]

It seems so that proot-distro will detect 'arm' instead of 'aarch64' - however.

With this workaround (enforcing DEVICE_CPU_ARCH aarch64) I could fix the issue and my build https://github.com/brian200508/code_lfa/releases/tag/v1.5.0%2B20-build-56 starts code server again.

You have to patch two artifacts:
(see commit 00de28a in my fork https://github.com/brian200508/code_lfa)

• assets/proot-distro/proot-distro.sh and
• proot-distro.sh inside of assets/proot-distro.zip (for example using the VSCode extension ZipFS - https://marketplace.visualstudio.com/items?itemName=arcanis.vscode-zipfs)

Best Regards
Brian

[mengyanshou]

It seems so that proot-distro will detect 'arm' instead of 'aarch64' - however.

With this workaround (enforcing DEVICE_CPU_ARCH aarch64) I could fix the issue and my build https://github.com/brian200508/code_lfa/releases/tag/v1.5.0%2B20-build-56 starts code server again.

You have to patch two artifacts: (see commit 00de28a in my fork https://github.com/brian200508/code_lfa)

• assets/proot-distro/proot-distro.sh and
• proot-distro.sh inside of assets/proot-distro.zip (for example using the VSCode extension ZipFS - https://marketplace.visualstudio.com/items?itemName=arcanis.vscode-zipfs)

Best Regards Brian

But strangely enough, his device, uname-m, returns aarch64

[brian200508]

Yes You're right. When I execute the command in plain termux from https://github.com/termux/termux-app/releases/tag/v0.118.1 the uname -m command also returns aarch64 on my device (Samsung Galaxy Z Fold 3, Android 14 One UI 6.1.1, Security-Patch Level Jan., 1st 2025).

With commit e022901 on my repo I have temporarliy add some debug output:

After clean install of the modified App I had these outputs which I still do not understand right now:
DEVICE_CPU_ARCH: 'arm'.
target_arch: 'aarch64'.

Maybe someone has an idea...

[siilm]

I have this problem same