#208 How to Install Fedora Linux on Android Mobile Devices
Closed: published by rlengland. Opened by rlengland.

Article Summary:
How to Install Fedora Linux on Android using Termux and Keep Upgrading/Updating it to the Latest Versions

Article Description:
If you’re interested in running Linux on your Android device, you’re in luck! It’s possible to install Fedora Linux on Android using Termux. Termux is a terminal emulator for Android that allows you to run Linux commands and utilities on your phone or tablet. In this article, we’ll walk you through the process of installing Fedora Linux on Android using Termux and show you how to keep it up to date with the latest versions.

https://discussion.fedoraproject.org/t/how-to-install-fedora-linux-on-android-mobile-devices/85867


Metadata Update from @rlengland:
- Issue assigned to adabalap
- Issue tagged with: article, needs-image

Metadata Update from @rlengland:
- Custom field preview-link adjusted to https://fedoramagazine.org/?p=38333&preview=1&_ppp=05f8947a6b

I'm thinking that there will have to be some modification made to the current image or a new one created.
I get the impression that this will not be specific to Fedora Linux 38 in the future. Please correct me if that is wrong.
If I am correct, how/where does the user find out what version will be installed?

Hello Richard,

Thank you for your email.

Yes we should indeed need to modify the current image or create a new image
that's apt for this context.

As for finding out the version that will be installed, it is correct that
it will not be specific to Fedora Linux 38 in the future.

  • The installer script (proot-install) points to the latest root-fs
    version available for the distribution. This indicates that the script w=
    ill
    automatically fetch the most up-to-date root-fs version during installat=
    ion.
  • If users are looking for information about available Fedora versions,
    they can visit the following URL: "
    https://mirror.de.leaseweb.net/fedora/linux/releases/". This website
    should provide details on the different Fedora releases.

Regards,
Phani Adabala

On Sun, Jul 16, 2023 at 10:41=E2=80=AFAM Richard England pagure@pagure.io=
wrote:

rlengland added a new comment to an issue you are following:
I'm thinking that there will have to be some modification made to the current image or a new one created. I get the impression that this will not be specific to Fedora Linux 38 in the future. Please correct me if that is wrong. If I am correct, how/where does the user find out what version will be installed?

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-magazine-newsroom/issue/208

Metadata Update from @adabalap:
- Assignee reset

Metadata Update from @adabalap:
- Issue assigned to adabalap

Metadata Update from @rlengland:
- Custom field preview-link adjusted to https://fedoramagazine.org/?p=38333&preview=1 (was: https://fedoramagazine.org/?p=38333&preview=1&_ppp=05f8947a6b)

Metadata Update from @rlengland:
- Custom field editor adjusted to rlengland
- Custom field image-editor adjusted to rlengland

Hello, @adabalap

I've done an edit pass on your article and it looks pretty good. Some changes were made such as replacing code text with pre-formatted to conform to the Fedora Magazine standard. There were some other text formatting changes made, as well.

I also added a couple of links to proot-distro and termux for informational context.

The only content question that arose for me was in the text block for Step 3. Is "Copy code" intended to be there? I'm just checking since it seemed a bit out of place from my very quick reading of the information on proot-distro.

I hope the feature image meets with your approval. If not, let me know if you have a good suggestion for an alternative and I can "try again". :-)

If you can give the article another review to ensure that I haven't incorrectly modified any information, and let me know, I can schedule this for this Wednesday or Friday.

Thank you.

Hi Richard,

Thanks for taking the time to edit my article. I really appreciate your
attention to detail and the improvements you've made.

I especially like the way you formatted the code blocks. They're much
easier to read now. And the links to proot-distro and termux are a great
addition.

I've checked the Step 3 text block, and you're right, the "Copy code" line
wasn't intended to be there. It must have come from WordPress when I was
formatting the text. I've removed it now.

As for the feature image, I don't have a strong opinion either way. A
colorful image would probably look good with the foreground text, but I'm
happy with whatever you choose.

Thanks again for your help!

Regards,
Phani Adabala

On Tue, Jul 18, 2023 at 3:54=E2=80=AFAM Richard England pagure@pagure.io =
wrote:

rlengland added a new comment to an issue you are following:
``
Hello, @adabalap

I've done an edit pass on your article and it looks pretty good. Some
changes were made such as replacing code text with pre-formatted to confo=
rm
to the Fedora Magazine standard. There were some other text formatting
changes made, as well.

I also added a couple of links to proot-distro and termux for
informational context.

The only content question that arose for me was in the text block for Ste=
p
3. Is "Copy code" intended to be there? I'm just checking since it seem=
ed
a bit out of place from my very quick reading of the information on
proot-distro.

I hope the feature image meets with your approval. If not, let me know if
you have a good suggestion for an alternative and I can "try again". :-)

If you can give the article another review to ensure that I haven't
incorrectly modified any information, and let me know, I can schedule thi=
s
for this Wednesday or Friday.

Thank you.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-magazine-newsroom/issue/208

Thanks @adabalap the article is scheduled for 19 July 08:00UTC

Metadata Update from @rlengland:
- Custom field publish adjusted to 2023-07-19
- Issue untagged with: needs-image

Issue status updated to: Closed (was: Open)
Issue close_status updated to: published

Metadata