The articles language is pretty confusing in the way that the author continues to say "the phone can run linux", even after saying that "of course, android is l

The articles language is pretty confusing in the way that the author continues to say "the phone can run linux", even after saying that "of course, android is linux". If the only shortcoming of android, compared to a more typical linux distribution, was that it didn't have a shell interface, that can be solved with the variety of shell programs available for the android environment. However bigger issues remain unsolved by adding a shell. The configuration of the _actual_ linux kernel used in android being one of the most significant. For instance, typical linux has excellent support for all USB class devices, whereas android disables this functionality. USB-on-the-go only supports specific devices in most android distributions. Rather than running a linux user space in an android chroot environment, as has been possible to do for years with many embedded linux flavors: archlinuxarm, debian, gentoo, ubuntu, all have documented means of installing a more full featured user space in a chroot over android. The better/more desirable configuration is to run the more full featured linux kernel and user space directly on the phone h/w, and then run android in a chroot or virtual machine when access to an android only app is needed. Such as this phone: https://furilabs.com/ https://furilabs.com/ This allows the android subsystem to be completely shut down when not in use, thus disabling the goggle surveillance and other undesirable features of android. For any semi-technical phone user, this article is old news. The only thing new about it, is that the chroot is configured by goggle itself, which pretty much insures that the config will be primarily for the benefit of goggle, not the user.