Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Android Linux
0 views
Skip to first unread message
Wei Spinks
Jan 16, 2024, 5:04:59 AM1/16/24
to
Android's kernel is based on the Linux kernel's long-term support (LTS) branches. As of 2023[update], Android uses versions 4.14, 4.19, 5.4, 5.10 or 5.15 of the Linux kernel (and since modified Linux kernels are used, kernels are often named like android13-5.15 or android-4.19-stable).[189] The actual kernel depends on the individual device.[190]
android linux
DOWNLOAD https://t.co/AA7J45Xvby
The device codename is usually not visible to the end user, but is important for determining compatibility with modified Android versions. It is sometimes also mentioned in articles discussing a device, because it allows to distinguish different hardware variants of a device, even if the manufacturer offers them under the same name. The device codename is available to running applications under android.os.Build.DEVICE.[239]
I would be most interested in a version which is compatible with Debian and/or Fedora. Those two distros are the primary linux flavors in QubesOS, and Debian is the foundation for the default OS on the Librem5 (PureOS).
Either way, if packaged for Debian, being adaptive to mobile size screens would be a nice touch, to support usage on a Librem5 and/or Pine Phone.
As a side note, it would be an honor to test any beta version (even alpha) for any linux distro if the opportunity arises.
By the way, thank you for developing this browser and the Kagi search engine. I tip my hat to you for making ethical business decisions.
Vlad
I actually haven't seen the browser (although I am supporting it) because I only use *BSD and linux distros; however, I can still say that the amount of work 5 people have accomplished is astonishing. Developing and maintaining a modern browser is a monumental task. You have an amazing team!
I, for one, am glad you are not Google, Apple, or Mozilla. Being receptive to eventually support other platforms when you have the time and resources is good enough for me.
Thank you.
Thank you for your answer
I don't think this possibility exists because when I execute cargo build --target=aarch64-linux-android and cargo build in the same terminal, the result is that cargo build will build an error while cargo build --target=aarch64-linux-android will not.
Android is a tier 2 target without host tools. This means that while we ship a precompiled standard library, we don't ship a precompiled rustc version for android. Using rustup requires a precompiled rustc version for the host shipped by the rust project.
The last API change seems to have happened in 2018 (see -android/pull/1067) which broke Android 4.0.x support. I have also found -android/issues/564 from 2016, which suggests that Android 2.2 support was dropped at that time. Also, it definitely used to work there in 2014 (see -android/issues/44). I am not sure whether this means that Syncthing should be compiled with an older NDK or whether some other hacks would be required to make it work.
Extending from this the elixir-desktop library now also supports abstracting Android apps using the very same interface. Meaning that a desktop app written using elixir-desktop can run unmodified natively on an android phone. The example project (ready to clone) ships the full Elixir+Erlang runtime ported to all common Android targets.
2) Do these apps install Linux with gui etc on tablet or does this only install terminal kind of environment and uses remote login (like splashtop) to access a pc with linux and then display screen on our tablet ( I dont want this) ?
You could certainly make the case that this is not a "full" installation, as it makes use of the kernel elements of the android OS it runs on top of: that distinction, however, is a very fine one and would not be particularly salient to even most IT professionals.
For both tools, you would end up accessing the Desktop GUI through a VNC: this VNC, however, would be pointed at the Android device itself. Because the desktop distro will be running in the chrooted environment "on top" of the android OS (which controls the screen), it doesn't have a way a way to access the screen directly.
You're using VNC not because you need to access a screen remotely, but because you need to create a virtual screen.
yes this seems very strange to as well, linux are an important part of many back bone and end users OS systems (i have been told that PA is built on centos linux distr for example) and there are estimates ranging between 25 and 50 mil linux users worldwide. For android I have seens estimates ranging from 40 - 60% of the global smartphone market, wich is double the number of iphone users, yet there is a iphone client from PA.
yes I have also found anothwer app vpncilla that connects fine, and I think it is sad that their android client is restricted to portal license users, a lot of users, like my company uses global protect, witout having or need ing the rather expensive portal license.
You can use the sys-fs/android-file-transfer-linux-9999 ebuild if you want the latest Git version by adding the following entry to `/etc/portage/package.accept_keywords (which can either be a directory or a file):
I have been using Pihole on my home network for quite some time. Our android phones use the Private DNS option which makes sense when out of the house, but at home Private DNS means that the android phones bypass the Pi-hole with a DoT connection to Google DNS. I also use Fedora for my workstation and for a small raspberry cluster. The next version (F35) will default to 'opportunistic' DoT.
Again the goal is to extend Pi-hole to offer opportunistic DoT for clients like android so that my pihole is providing DNS and add blocking etc while connected to the home network but also maintain classic DNS service for all other clients. I am constantly amazed at how many network devices we have in our farm house.
Make sure you have the EasyTether android app installed on your phone for it to connect to. Note: The Lite app disables some connections and you must have the paid app for full functionality. For this reason, using the AziLink setup is recommended instead.
f448fe82f3
android linux
DOWNLOAD https://t.co/AA7J45Xvby
The device codename is usually not visible to the end user, but is important for determining compatibility with modified Android versions. It is sometimes also mentioned in articles discussing a device, because it allows to distinguish different hardware variants of a device, even if the manufacturer offers them under the same name. The device codename is available to running applications under android.os.Build.DEVICE.[239]
I would be most interested in a version which is compatible with Debian and/or Fedora. Those two distros are the primary linux flavors in QubesOS, and Debian is the foundation for the default OS on the Librem5 (PureOS).
Either way, if packaged for Debian, being adaptive to mobile size screens would be a nice touch, to support usage on a Librem5 and/or Pine Phone.
As a side note, it would be an honor to test any beta version (even alpha) for any linux distro if the opportunity arises.
By the way, thank you for developing this browser and the Kagi search engine. I tip my hat to you for making ethical business decisions.
Vlad
I actually haven't seen the browser (although I am supporting it) because I only use *BSD and linux distros; however, I can still say that the amount of work 5 people have accomplished is astonishing. Developing and maintaining a modern browser is a monumental task. You have an amazing team!
I, for one, am glad you are not Google, Apple, or Mozilla. Being receptive to eventually support other platforms when you have the time and resources is good enough for me.
Thank you.
Thank you for your answer
I don't think this possibility exists because when I execute cargo build --target=aarch64-linux-android and cargo build in the same terminal, the result is that cargo build will build an error while cargo build --target=aarch64-linux-android will not.
Android is a tier 2 target without host tools. This means that while we ship a precompiled standard library, we don't ship a precompiled rustc version for android. Using rustup requires a precompiled rustc version for the host shipped by the rust project.
The last API change seems to have happened in 2018 (see -android/pull/1067) which broke Android 4.0.x support. I have also found -android/issues/564 from 2016, which suggests that Android 2.2 support was dropped at that time. Also, it definitely used to work there in 2014 (see -android/issues/44). I am not sure whether this means that Syncthing should be compiled with an older NDK or whether some other hacks would be required to make it work.
Extending from this the elixir-desktop library now also supports abstracting Android apps using the very same interface. Meaning that a desktop app written using elixir-desktop can run unmodified natively on an android phone. The example project (ready to clone) ships the full Elixir+Erlang runtime ported to all common Android targets.
2) Do these apps install Linux with gui etc on tablet or does this only install terminal kind of environment and uses remote login (like splashtop) to access a pc with linux and then display screen on our tablet ( I dont want this) ?
You could certainly make the case that this is not a "full" installation, as it makes use of the kernel elements of the android OS it runs on top of: that distinction, however, is a very fine one and would not be particularly salient to even most IT professionals.
For both tools, you would end up accessing the Desktop GUI through a VNC: this VNC, however, would be pointed at the Android device itself. Because the desktop distro will be running in the chrooted environment "on top" of the android OS (which controls the screen), it doesn't have a way a way to access the screen directly.
You're using VNC not because you need to access a screen remotely, but because you need to create a virtual screen.
yes this seems very strange to as well, linux are an important part of many back bone and end users OS systems (i have been told that PA is built on centos linux distr for example) and there are estimates ranging between 25 and 50 mil linux users worldwide. For android I have seens estimates ranging from 40 - 60% of the global smartphone market, wich is double the number of iphone users, yet there is a iphone client from PA.
yes I have also found anothwer app vpncilla that connects fine, and I think it is sad that their android client is restricted to portal license users, a lot of users, like my company uses global protect, witout having or need ing the rather expensive portal license.
You can use the sys-fs/android-file-transfer-linux-9999 ebuild if you want the latest Git version by adding the following entry to `/etc/portage/package.accept_keywords (which can either be a directory or a file):
I have been using Pihole on my home network for quite some time. Our android phones use the Private DNS option which makes sense when out of the house, but at home Private DNS means that the android phones bypass the Pi-hole with a DoT connection to Google DNS. I also use Fedora for my workstation and for a small raspberry cluster. The next version (F35) will default to 'opportunistic' DoT.
Again the goal is to extend Pi-hole to offer opportunistic DoT for clients like android so that my pihole is providing DNS and add blocking etc while connected to the home network but also maintain classic DNS service for all other clients. I am constantly amazed at how many network devices we have in our farm house.
Make sure you have the EasyTether android app installed on your phone for it to connect to. Note: The Lite app disables some connections and you must have the paid app for full functionality. For this reason, using the AziLink setup is recommended instead.
f448fe82f3
0 new messages