You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is fastfetch package in the Termux repo, which, in my case, prints the correct name of my CPU: "SM8250 (8) @ 3.19 GHz" (which is Snapdragon 870). However, when being executed inside a chroot distro (tested on Ubuntu and Arch), fastfetch claims that the name of my CPU is "kona (8) @ 3.19 GHz":
It's kinda weird because the correct name of my CPU can be found easily in the proc/cpuinfo file (so the fix of this bug should be very simple):
The text was updated successfully, but these errors were encountered:
Nikitf777
changed the title
[BUG] CPU name on Android inside a chroot container is not correct, despite the fact that it can be found in /proc/cpuinfo
[BUG] CPU name on Android inside a chroot container is not correct, despite the fact that it can be found in /proc/cpuinfo
Jan 13, 2025
Nikitf777
changed the title
[BUG] CPU name on Android inside a chroot container is not correct, despite the fact that it can be found in /proc/cpuinfo
[BUG] CPU name on Android inside a chroot container is not correct, but it can be found in /proc/cpuinfo
Jan 13, 2025
There is fastfetch package in the Termux repo, which, in my case, prints the correct name of my CPU: "SM8250 (8) @ 3.19 GHz" (which is Snapdragon 870). However, when being executed inside a chroot distro (tested on Ubuntu and Arch), fastfetch claims that the name of my CPU is "kona (8) @ 3.19 GHz":

It's kinda weird because the correct name of my CPU can be found easily in the

proc/cpuinfo
file (so the fix of this bug should be very simple):The text was updated successfully, but these errors were encountered: