This is a guide to build cyanogenmod 10.1 (Android 4.2.1) for Google Nexus 4. This guide is for linux. I will add a guide to build on mac soon, but the basic principle is the same.
Preparation
You need a fully working build environment. If you don't have one running already, you can follow the official android guide on how to set up build environment. Follow the easy steps in the guide.
Check this guide by sylentprofet about how to get the build environment set up.
Your build environment is now set? Good, let's start!
Get the sources
Start by creating a new working directory for CM10.1. You can create this anywhere on your workstation.
Code:
$ mkdir ~/cm10.1
$ cd ~/cm10.1
£ mkdir -p bin
Initialize Repo for Android CM10.1 (Android 4.2.1):
Code:
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
and enter your credentials if needed.
Download the sources:
Code:
$ repo sync
Wait until it is finished. It will take a long time, depending on your internet connection.
Obtain the device build files and proprietary files:
To do this create a file named 'local_manifest.xml" in the .repo folder. This is a hidden folder, so you have to allow your visualisation of hidden files, alternatively run "open .repo" code from terminal. Or you can just run the code below to create the file directly into the folder.
Code:
$ gedit ~/cm10.1/.repo/local_manifest.xml
For Mac you can use:
Code:
$ touch ~/cm10.1/.repo/local_manifest.xml
Paste the following lines into the file:
Code:
<manifest>
<project name="TheMuppets/proprietary_vendor_lge.git" path="vendor/lge" remote="github" revision="cm-10.1"/>
<project name="CyanogenMod/android_device_lge_mako" path="device/lge/mako" remote="github" revision="cm-10.1"/>
<project name="CyanogenMod/lge-kernel-mako" path="kernel/lge/mako" remote="github" revision="jellybean"/>
</manifest>
Save the file. And rerun the code:
Code:
$ repo sync
Download the necessary pre-builts:
Code:
$ ~/cm10.1/vendor/cm/get-prebuilts
That's all the sources ready now.
Edits for mac only
If you try building now you will get elf errors when the kernel is being compiled. There are different way for fix this, but I'm using this method.
Go to /kernel/lge/mako/scripts/mod/ folder, open the file 'mk_elfconfig.c' and replace
Code:
#include <elf.h>
with
Code:
#include "elf.h"
. Do the same in the file named 'modpost.h'. Next download the attached file named 'elf.h' and copy to the same folder. You are now ready to build.
Building CyanogenMod
Run the following command:
Code:
$ . build/envsetup.sh
and build by running:
Code:
$ brunch mako
Credits:
CyanogenMod team
Raum1807
Weow, your nice.
I was compiling CM10.1 for my mako and I have this following error
what about that ?
[[email protected] system]# . build/envsetup.sh && brunch mako
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/lge/mako/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
including vendor/cm/vendorsetup.sh
File "<string>", line 1
import os,sys; print os.path.realpath(sys.argv[1])
^
SyntaxError: invalid syntax
File "build/tools/roomservice.py", line 37
print "Device %s not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod)." % device
^
SyntaxError: invalid syntax
** Don't have a product spec for: 'cm_mako'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
[[email protected] system]#
Click to expand...
Click to collapse
Happened to me too. Re run ". build/envsetup.sh" and then "brunch mako". Worked for me the second time.
Edit: didn't read the post carefully, looks more like a build environment error
Sent from my Nexus 4 using xda app-developers app
Downgraded make, git and perl on my Arch Linux. Now works
I've just added this guide to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
Good to see another O2X convert here
Good guide, might start building my own stuff again for this phone.
Cannot seem to get past this:
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/mako/cm.mk]]: "frameworks/native/build/phone-xhdpi-2048-dalvik-heap.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_mako'
** Do you have the right repo manifest?
Any ideas?
Is there a guide on how to do cherry picks? Im interested in developing
Sent from my Nexus 4 using xda premium
dosangst said:
Cannot seem to get past this:
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/mako/cm.mk]]: "frameworks/native/build/phone-xhdpi-2048-dalvik-heap.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_mako'
** Do you have the right repo manifest?
Any ideas?
Click to expand...
Click to collapse
Check if you have the file "phone-xhdpi-2048-dalvik-heap.mk" in your repo.
jarjar124 said:
Is there a guide on how to do cherry picks? Im interested in developing
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Go go the gerritt review site, click on 'cherry-pick' and the copy the code displayed underneath. On terminal direct to the required folder and then paste the code on terminal. So if the change is in 'frameworks_base', do 'cd ~/cm10.1/frameworks/base' and then paste the code.
This might help..
https://android.googlesource.com/pl...815362c/build/phone-xhdpi-2048-dalvik-heap.mk
dosangst said:
Cannot seem to get past this:
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/mako/cm.mk]]: "frameworks/native/build/phone-xhdpi-2048-dalvik-heap.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_mako'
** Do you have the right repo manifest?
Any ideas?
Click to expand...
Click to collapse
Imperticus said:
Check if you have the file "phone-xhdpi-2048-dalvik-heap.mk" in your repo.
Go go the gerritt review site, click on 'cherry-pick' and the copy the code displayed underneath. On terminal direct to the required folder and then paste the code on terminal. So if the change is in 'frameworks_base', do 'cd ~/cm10.1/frameworks/base' and then paste the code.
Click to expand...
Click to collapse
I finally got Cm10.1 to build correctly on my own after days and days of troubleshooting. I wish I would have seen this guide earlier! I am having one slight problem though. Every time I sync, it hangs at 99%(353/356). It always hangs up on the last 3 projects. Everything builds fine. I think it has something to do with prop files. I've tried pulling them from the phone and using "The Muppets" github in local_manifest.xml, but it makes no difference. It hangs every time. I've let it sit for hours and nothing. It was syncing all the way through just fine, but a couple days ago it stopped and hasn't synced properly since. If anyone has any ideas I'd greatly appreciate it! Thanks.
how do i move the file when it is done compiling? it says" The file "cm-10.1-20121222-UNOFFICIAL-mako.zip" cannot be handled because you do not have permissions to read it." Also when I do get it out to desktop with this command " sudo cp -r cm-10.1-20121222-UNOFFICIAL-mako.zip '/home/jarman/Desktop' " I dont have permission to read and write it. Any help?
jarjar124 said:
how do i move the file when it is done compiling? it says" The file "cm-10.1-20121222-UNOFFICIAL-mako.zip" cannot be handled because you do not have permissions to read it." Also when I do get it out to desktop with this command " sudo cp -r cm-10.1-20121222-UNOFFICIAL-mako.zip '/home/jarman/Desktop' " I dont have permission to read and write it. Any help?
Click to expand...
Click to collapse
sorry i'm more familiar with mac, not linux.Try 'sudo chmod -R 755 cm-10.1-20121222-UNOFFICIAL-mako.zip'
jarjar124 said:
how do i move the file when it is done compiling? it says" The file "cm-10.1-20121222-UNOFFICIAL-mako.zip" cannot be handled because you do not have permissions to read it." Also when I do get it out to desktop with this command " sudo cp -r cm-10.1-20121222-UNOFFICIAL-mako.zip '/home/jarman/Desktop' " I dont have permission to read and write it. Any help?
Click to expand...
Click to collapse
Why don't you set your build folder in the home directory?
Thanks for the guide was wondering how to make the switch as I was building CM10.
Anyone having luck building in Ubuntu 12.04, Just curious as I am on 10.4 (x64) as advised by Google but that update button is begging me to press it. Also will upgrading from 10.4 to 12.04 destroy my Android/CM build enviroments or will everything remain in tact??
Thanks for the help.
kjacksonmusic said:
Thanks for the guide was wondering how to make the switch as I was building CM10.
Anyone having luck building in Ubuntu 12.04, Just curious as I am on 10.4 (x64) as advised by Google but that update button is begging me to press it. Also will upgrading from 10.4 to 12.04 destroy my Android/CM build enviroments or will everything remain in tact??
Thanks for the help.
Click to expand...
Click to collapse
It should work on 12.04, as the cyanogenmod official guides are written for that version of ubuntu. I can't say whether the build environment will remain the same or not.
kjacksonmusic said:
Thanks for the guide was wondering how to make the switch as I was building CM10.
Anyone having luck building in Ubuntu 12.04, Just curious as I am on 10.4 (x64) as advised by Google but that update button is begging me to press it. Also will upgrading from 10.4 to 12.04 destroy my Android/CM build enviroments or will everything remain in tact??
Thanks for the help.
Click to expand...
Click to collapse
There are different packages to set up the build environment in 12.04 that are listed on googles site. They work. You can upgrade, but you would have to install the new packages. They also work on 12.10 fyi.
I was wondering if anyone has successfully set up the build environment in Mint 14? The packages for 12.04 won't install. If anyone can help, I would be grateful.
Sent from my Nexus 4 using Tapatalk 2
In case anyone is following my upgrade, I upgraded to 12.04 and my Android Working Directory still compiles and builds as well as cm10.1:good:.
Thanks for the help.
kjacksonmusic said:
In case anyone is following my upgrade, I upgraded to 12.04 and my Android Working Directory still compiles and builds as well as cm10.1:good:.
Thanks for the help.
Click to expand...
Click to collapse
Even builds just fine for me on 13.04 mate. Just using the 12.04 required packages.
@OP - could you do a guide on how to build AOSP rom and adding in features from CM?
Many thanks!
Hey guys! This guide is surely gonna help a lot of people who build/compile ROMs, to understand the hidden meaning behind most of the common commands associated with the building stuff.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SO STARTING WITH THE COMMANDS GENERALLY USED FOR BUILDING DEVELOPMENT ENVIRONMENT:
We type the command sudo a lot of times and it asks for our desktop's password.
What is 'sudo'?
sudo is a Linux command used to execute programs as the root, or "super user." sudo is a shortening of "substitute user do."
One uses sudo when they need to run a command or program as root, but do not wish to log out or switch their entire shell to root privileges (like they could do with the su command).
Click to expand...
Click to collapse
What is 'mkdir'?
The 'mkdir' (make directory) command in the Linux or Ubuntu operating systems and in the PHP scripting language is used to make a new directory.
eg: mkdir -p ~/bin
Click to expand...
Click to collapse
What is 'cd'?
Besides listing the command "change directory" command "cd" is used.
The cd command, also known as chdir (change directory), is a command-line OS shell command used to change the current working directory in operating systems such as Ubuntu or Linux.
eg: cd ******(folder name)
Click to expand...
Click to collapse
What does './configure' do?
Typically the configure script when run will check some details about the machine on which the software is going to be installed. This script checks for lots of dependencies on your system. For the particular software to work properly, it may be requiring a lot of things to be existing on your machine already. If any of the major requirements are missing on your system, the configure script would exit and you cannot proceed with the installation, until you get those required things.
Click to expand...
Click to collapse
What is 'make'?
the make command accepts targets as command line arguments. These targets are usually specified in a file named 'Makefile', which also contains the associated action corresponding to the targets.
When the make command is executed for the very first time, it scans the Makefile to find the target (supplied to it) and then reads its dependencies. If these dependencies are targets themselves, it scans the Makefile for these targets and builds their dependencies (if any), and then builds them. Once the main dependencies are build, it then builds the main target (that was passed to the make command).
Click to expand...
Click to collapse
What does 'sudo apt-get' do?
Now there are a lot of things that are done with the command 'sudo apt-get'. Some common ones are:
'apt-get update' downloads the package lists from the repositories and "updates" them to get information on the newest versions of packages and their dependencies. It will do this for all repositories and PPAs.
'apt-get upgrade' will fetch new versions of packages existing on the machine if APT knows about these new versions by way of apt-get update.
'apt-get install': This option is followed by one or more packages desired for installation. Each package is a package name, not a fully qualified filename.
Click to expand...
Click to collapse
MOVING ON TO THE COMMANDS USED FOR COMPILING PROCESS:
What is 'curl'?
'curl' is a client to get documents/files from or send documents to a server, using any of the supported protocols (HTTP, HTTPS, FTP, GOPHER, DICT, TELNET, LDAP or FILE). The command is designed to work without user interaction or any kind of interactivity.
eg curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Click to expand...
Click to collapse
Why do we use 'chmod' command?
In Linux or Ubuntu, 'chmod' changes the permissions for a file; permissions should include a letter designating who gets permissions ('u' for the user, 'g' for the group, 'o' for others, or 'a' for all) followed by a '+' or '-' (to give or take away the permission) followed by the kind of permission ('r' for read access, 'w' for write access, 'x' for execute if the file is a program or script).
eg: chmod a+x ~/bin/repo
Click to expand...
Click to collapse
Why do we use 'export' command?
When you use export, you are adding the variable to the environment variables list of the shell in which the export command was called and all the environment variables of a shell are passed to the child processes.
eg: export PATH=${PATH}:~/bin
Click to expand...
Click to collapse
What is 'gedit'?
'gedit' is a light-weight text editor. Gedit has all the basic features you come to expect from a simple text editor, but Gedit has a native graphic user interface (GUI). Gedit also has command line arguments available to users to quickly and easily view and edit files from a terminal. Overall, Gedit is an easy to use text editor with utilizing the powerful capabilities of the desktop.
Click to expand...
Click to collapse
Why is 'repo init -u url -b branch' used?
This would initialize a new local source repository. This will create a new place to hold your local copy of the source tree. “url” should point to a Manifest repository that describes the whole sources. It is a special project with a file (default.xml) that lists all the projects that Android is made of. In the Manifest file, each projects has attributes about: where to place it in the tree, where to download it from (git server), revision that will be used (usually a branch name, tag or commit sha-id).
eg:repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
Click to expand...
Click to collapse
What is 'repo sync'?
After the repo initialization, this command downloads all the sources to your local directory. The first time you run this command, it will download the sources. Android sources are huge, for example, CM11 (KitKat) sources are approximately 12GiB. So, be prepared: you’ll need space in your hard drive, and time (possibly several hours)-depending on you ISP.
Click to expand...
Click to collapse
What is 'mka'?
This little gem of a command is basically equivalent to a super-charged version of 'make'. Problem is, make is SLOW in its default configuration. It can take hours longer depending on your hardware.So, mka is like a cheetah. What this means is that ALL of your processor is working, not just one small part of it(which is used with 'make' command).
Click to expand...
Click to collapse
What is 'breakfast'?
In order to explain brunch, we have to explain breakfast first. Breakfast is a function used to configure your build. It keeps track of a list of officially-supported devices to build for, and allows you to choose one. You can do this two ways,
1) breakfast [device name]
or
2) breakfast
Now, the first method is a shortcut to your device. If you don't know your device's name, then you can probably choose the second method which would display all the officially supported devices.
Breakfast then goes on to configure your build environment with the correct variables to create your device-specific rom.
Click to expand...
Click to collapse
Why do we use 'brunch'?
brunch followed by your device's codename is used to tell the system to start building/compiling from the sources.
eg: brunch ****(device codename: eg pico for HTC Explorer)
Click to expand...
Click to collapse
What is 'lunch'?
Lunch is used EXACTLY like breakfast, the only difference being the choices you have to build with it. Using lunch, you can choose non-official or non-standard builds for your device. This includes special debug versions and also allows you to build CyanogenMod for use on the Android Emulator. To build after running lunch, simply issue the command mka.
Click to expand...
Click to collapse
THANK YOU GUYS FOR READING IT. HOPE IT COMES HANDY TO YOU!
XDA-Portal: http://www.xda-developers.com/android/basic-linux-commands/
Source: http://www.google.com/
Nice overview for people new to Linux, but I'm afraid I'm going to have to disagree on your explanation of the sudo command. Contrary to your explanation, the name of the sudo command is actually derived from the su command (sudo homepage), which means: ”substitute user”. When taking this into account the meaning of sudo becomes: ”substitute user do”.
The reason I'm saying this, is because sudo, just like su, can be used to execute commands as/switch to any user present on the system.
Do note that apt-get and dpkg are distro-specific, not Linux-specific. If you're using Ubuntu, Debian or elementary, apt-get is there, but on Fedora you'll find yum, on Arch you've got pacman, on Gentoo you end up with emerge and so on.
is this an example of the real guide?
i mean there are so many more thing you need to explain
1.rm
2.ls
3.pwd
4.cp/mv
5.lunch
6.breakfast(i mean you mention brunch ,without breakfast?)
7.mka
more i can't remember
and all of this i have used while building.
Imposible to read on mobile
You know this is very hard to read on a phone? I mean, those boxes are for code, no? Any way, good post.
Erackron said:
Nice overview for people new to Linux, but I'm afraid I'm going to have to disagree on your explanation of the sudo command. Contrary to your explanation, the name of the sudo command is actually derived from the su command, which means: ”substitute user”. When taking this into account the meaning of sudo becomes: ”substitute user do”.
The reason I'm saying this, is because sudo, just like su, can be used to execute commands as/switch to any user present on the system.
Click to expand...
Click to collapse
This was a great overview, it did teach me a few things. Just one minor thing, in my Linux class we were taught that su meant 'switch user' and the other meanings were actually wrong. Then sudo would become: 'switch user do'. Which meaning is it then?
ruledrbrt1 said:
This was a great overview, it did teach me a few things. Just one minor thing, in my Linux class we were taught that su meant 'switch user' and the other meanings were actually wrong. Then sudo would become: 'switch user do'. Which meaning is it then?
Click to expand...
Click to collapse
I'm pretty sure sudo is something else. Ex: You can do sudo su - to switch to root.
You dont have automatikli sudo rights. The configuration file for sudo is*/etc/sudoers wich u can edit with visudoers.
The distinction between sudo and su is that with sudo, you need to have a user configured in a system wide configuration file (/etc/sudoers) to actually have him use the command and if someone attempts to use it without having permission, a log email will be sent to the email address configured for the root user.
When your account has been configured to allow sudo usage, you can then switch to any user/perform any command as the other user, but you only need to enter your own password when executing a command/switching to another user.
The su command is not really configurable, and only allows you to switch to another user if you enter that user's password.
So while
Code:
sudo -s someuser
and
Code:
su someuser
have the same effect, the sudo version asks for the password of the current user (and fails if the current user has no sudo rights) while the latter asks for the password of someuser.
For more on su and sudo.
cybervibin said:
is this an example of the real guide?
i mean there are so many more thing you need to explain
1.rm
2.ls
3.pwd
4.cp/mv
5.lunch
6.breakfast(i mean you mention brunch ,without breakfast?)
7.mka
more i can't remember
and all of this i have used while building.
Click to expand...
Click to collapse
To be honest if people don't understand what 1 through 4 mean in your list, then most likely they shouldn't be trying to develop anything IMHO
mjwhirly said:
To be honest if people don't understand what 1 through 4 mean in your list, then most likely they shouldn't be trying to develop anything IMHO
Click to expand...
Click to collapse
well he included 'cd' and 'mkdir'
so i just mentioned
Erackron said:
Nice overview for people new to Linux, but I'm afraid I'm going to have to disagree on your explanation of the sudo command. Contrary to your explanation, the name of the sudo command is actually derived from the su command (sudo homepage), which means: ”substitute user”. When taking this into account the meaning of sudo becomes: ”substitute user do”.
The reason I'm saying this, is because sudo, just like su, can be used to execute commands as/switch to any user present on the system.
Click to expand...
Click to collapse
Corrected it. Thanks!
cybervibin said:
is this an example of the real guide?
i mean there are so many more thing you need to explain
1.rm
2.ls
3.pwd
4.cp/mv
5.lunch
6.breakfast(i mean you mention brunch ,without breakfast?)
7.mka
more i can't remember
and all of this i have used while building.
Click to expand...
Click to collapse
Well, added the last three. Thanks!
letoloke said:
You know this is very hard to read on a phone? I mean, those boxes are for code, no? Any way, good post.
Click to expand...
Click to collapse
Now, I guess it would be readable on phones as well, since I have changed code to quotes. Hope it works now. Thanks!
Thanks for the knowledge
Easy to digest explanations.
I'd like to link this free course by Linux Foundation - https://www.edx.org/course/linuxfoundationx/linuxfoundationx-lfs101x-2-introduction-5386
I am full time linux user and linux is much much better when it comes to developement/re-engineering stuffs. This free course gives deep introduction to linux and basic info to bash scripting.
Thanks bro, much appreciated work, just started to build ROM from source for i9100 android lollypop named "CodeROM"
this tutorial is really helpful... thanks added... & keep updating the thread whenever new commands arrives.... so people like me can get most out of it
warrior1208 said:
Hey guys! This guide is surely gonna help a lot of people who build/compile ROMs, to understand the hidden meaning behind most of the common commands associated with the building stuff.
SO STARTING WITH THE COMMANDS GENERALLY USED FOR BUILDING DEVELOPMENT ENVIRONMENT:
We type the command sudo a lot of times and it asks for our desktop's password.
What is 'sudo'?
What is 'mkdir'?
What is 'cd'?
What does './configure' do?
What is 'make'?
What does 'sudo apt-get' do?
MOVING ON TO THE COMMANDS USED FOR COMPILING PROCESS:
What is 'curl'?
Why do we use 'chmod' command?
Why do we use 'export' command?
What is 'gedit'?
Why is 'repo init -u url -b branch' used?
What is 'repo sync'?
What is 'mka'?
What is 'breakfast'?
Why do we use 'brunch'?
What is 'lunch'?
THANK YOU GUYS FOR READING IT. HOPE IT COMES HANDY TO YOU!
XDA-Portal: http://www.xda-developers.com/android/basic-linux-commands/
Source: http://www.google.com/
Click to expand...
Click to collapse
How to pause repo sync????
My pc was shut down bcoz electricity gone and i was rezume rwpo sync plz tell me how to reaume repo synce fast
I get this error plz fix
Sent from my Xperia M2 Dual using XDA Free mobile app
manask002 said:
I get this error plz fix
Sent from my Xperia M2 Dual using XDA Free mobile app
Click to expand...
Click to collapse
You need to add yoour sources to the local_maifest.xml or you have to create a room service xml because your device is not supported officially.
Check this helpful guide on how to make a local manifest.
http://forum.xda-developers.com/showthread.php?t=2329228
Hope this helps you.
My device is xperia m2 its officially support aosp xperia
Sent from my Xperia M2 Dual using XDA Free mobile app
Noob on Linux
I want to try to build a rom for my Nexus 5 but want too also better understand Linux eg Ububtu 14.10 and not just copy text given in a buildingmanual so where is the best place to start really understanding Ubuntu?
I am looking for a list of all termux Packages and what there functions are, I am knew to the Linux and termux world and trying to learn anything and everything I can, any directions will be greatly appreciated, I'm trying to focus on learning termux right this moment. Thank you everyone and God Bless.
Package Management - Termux Wiki
wiki.termux.com
pkg list-all
Does list them all. Get to about half the alphabet and then no more why cause it cant keep going. So honestly someone needs to help with it.
well
termux package based on AUR (maybe)
and make sure u installed it from Fdroid
try this
Code:
apt update && apt upgrade
apt install x11-utils
apt install root-utils
#for x11 and root are showed from frist you open termux
apt list
# marked as comment, ignore it
Termux | F-Droid - Free and Open Source Android App Repository
Emulator terminala z pakietami
f-droid.org
Avisadius said:
(...)
apt install x11-utils
apt install root-utils
(...)
Click to expand...
Click to collapse
E: Unable to locate package x11-utils
E: Unable to locate package root-utils
A termux-setup-storage should be performed before use, but even that doesn't help.
ze7zez said:
E: Unable to locate package x11-utils
E: Unable to locate package root-utils
A termux-setup-storage should be performed before use, but even that doesn't help.
Click to expand...
Click to collapse
true
Make the command output to a text file, then it will contain all the lines.
First, make sure termux has storage permission (or maybe it will ask when you run this command, not sure)
pkg list-all >> /storage/emulated/0/Download/all.txt
cybercme2aT said:
(...) I am knew to the Linux and termux world and trying to learn anything and everything I can, any directions will be greatly appreciated, I'm trying to focus on learning termux right this moment. Thank you everyone and God Bless.
Click to expand...
Click to collapse
For you and for everyone who came across this thread, I recommend learning about the tremendous opportunities that come with using termux on your phone.
[GUIDE][NO-ROOT] How to install Ubuntu and other Linux Distros on Your Phone or Android TV Box, using Termux
NOTICE: THIS METHOD IS ONLY FOR NON ROOTED DEVICES PROOT-DISTRO GITHUB PAGE Hello Friends! Today I wanted to start a thread that will house prebuilt Linux environments, as well as instructions for building the Linux environments yourself...
forum.xda-developers.com
jenneh's other threads are also very informative.