I'll leave this here until I get enough time to put the changes in the wiki page: http://forum.xda-developers.com/showthread.php?t=2259929 GermainZ (talk) 18:45, 4 May 2013 (UTC)
I found installing the Android SDK within Eclipse is much more pleasant, especially when your developing alone. No need for AUR and chmod orgies.
Open up Eclipse, go to Help - Install new Software - Add...
and choose "Developer Tools"
In my case everything was installed to
~/Development/android-sdks (of course the installer lets you choose any directory that suits you best)
After that, close eclipse,
cd ~/Development/android-sdks/tools and fire up the Android SDK Manager ./android sdk
to get additional libs and the latest updates (don't miss this step)
You can now create a new Android project in Eclipse and everything works fine!
I always build with no problems Android using OpenJDK. I think it was OpenJDK 7, but I'm going to build Android again so I'll see which one works best. Anyway there's no need to use Oracle Java.
As of November 3/4, 2014 with the release of Android 5.0, Android will no longer build with Oracle Java. (I remember reading this somewhere on the internet and this was also my experience when trying to build 5.0 with Oracle Java. After switching to OpenJDK 7 there were no build issues related to java. Orkeren (talk) 21:26, 4 November 2014 (UTC)
Android SDK core components
Find the line where it says:
# chown -R :sdkusers /opt/android-sdk/
And should be like this:
# chown -R <user>:sdkusers /opt/android-sdk/
You must change it from root user to your regular user, otherwise it just won't let you edit anything at
/opt/android-sdk/. Who da heck changed it? I've already tested it in the past.
- I did, because it makes no sense to put a particular user in charge (and, it is the point of groups). I also added that you should use
chmod -R g+wafterwards to have it working. Moviuro (talk) 13:44, 1 March 2015 (UTC)
- Umm ok. I wonder how I didn't notice
chmod -R g+wpart? Well, nevermind, great work. Thanks sir ;) -- Erkexzcx (talk) 11:53, 2 March 2015 (UTC)
- Umm ok. I wonder how I didn't notice
As you all know, this is the alternative to odin (windows app for flashing and restoring Samsung devices). Maybe is here anyone who is familiar with it and can put some description here or in the wiki page (I mean creating new topic)? I will try to figure out as much as possible about it, but not sure if I can do it alone. -- Erkexzcx (talk) 11:53, 2 March 2015 (UTC)
Much of this section seems confusing in regards to the python venv stuff. I simply used OmniROM's instructins which were all of a few lines http://docs.omnirom.org/Setting_Up_A_Compile_Environment#Arch_Linux
Arch Linux--Jawz101 (talk) 01:59, 8 November 2015 (UTC)
If you are using an x64 install, you should enable the multilib repository in
/etc/pacman.conf, to permit 32 bit software to be installed.
Install the following packages on an x64 system:
base-devel gcc-multilib git gnupg flex bison gperf sdl wxgtk squashfs-tools curl ncurses zlib schedtool perl-switch zip unzip libxslt libxml2 lzo lzop python2 lib32-zlib lib32-ncurses lib32-readline
Install the following packages on an x86 systems:
base-devel gcc git gnupg flex bison gperf sdl wxgtk squashfs-tools curl ncurses zlib schedtool perl-switch zip unzip libxslt libxml2 lzo lzop python2
The android source code expects "python" to link to "python2". Create a symlink to /usr/bin/python2 and add that to $PATH. Or you can use virtualenv. Install the python-virtualenvwrapper  and configure it.
$ sudo pacman -S python-virtualenvwrapper
$ source /usr/bin/virtualenvwrapper.h
$ mkvirtualenv -p `which python2` python2
$ workon python2
You will also need jdk7.
To install jdk7, you can use the package "jdk7-openjdk"To install repo, you can use the package "repo" from the AUR: https://aur.archlinux.org/packages/repo/
- also of note, repo sync -c switch is no longer supported
Building the code
Note on RAM usage: Using the official build instructions from the LineageOS Wiki, I did not notice heavy usage of the /tmp directory. Instead I needed around 10 GB of Memory for the build to succeed. I think the behaviour is the same for AOSP.
The use of adb from android-tools interferes with the adb built into android studio causing it to crash when you stop the application after running it on a physical device. Even after unplugging the phone, it is still registered as being connected to the computer preventing it from connecting again once plugged back in requiring a restart.