Database Users

[DEV TOOL] EasyDev-v9 - "Roll Your Own" [8-28-11]

This is a continuation of the "Compiling CM6 for Eris" thread - http://forum.xda-developers.com/showthread.php?t=856215. But since Team ADX has really come together on this, we are releasing it in it's new form.
Thanks to workshed for working to get the Eris on the Official CM list and merged into the main repo. And also, thanks to workshed for most of the v6 --> v7 changes to EasyDev!
This script will grab CM7 source and compile a CM7 ROM for you using the official vendor tree that is built-in to the CM source. You have the option of including Google Apps or not.
Uses:
CM source - https://github.com/CyanogenMod/android.git
Conap's CFS kernel that's built-in to CM source - https://github.com/Conap30/htc_kernel_desirec_cfs
Requirements
-------------
1) 64- bit Linux -tested on Debian, Ubuntu 10.04, Linux Mint (if you have a different flavor of linux and easydev worked for you, please let us know so we can update this list)
2) An existing Eris ROM that the script will pull the proprietary files from.
INSTRUCTIONS
1) Download the script
2) 'chmod a+x easydev-v9.sh'
3) copy it to the directory of your choice or leave it where it is
4) copy an existing ROM to the same directory (tested with GSB, but most should work)
5) run it ('sudo ./easydev-v9.sh')
Possilbe future features:
Done.
Changelog
v1 - initial release
v2 - added squisher, made 'make clean' optional, added installation of dependencies, cleaned up output
v3 - uses existing ROM to pull proprietary files, renamed to 'easydev' for case sensitive linux admins
v4 - fixed file missing from list in unzip-files.sh in vendor tree, fixed move/rename of existing ROM, change 'make clean' option to default to no instead of yes
v5 - added 'apt-get update' to refresh repo list (should install dependencies now), swapped order of extract-files and unzip-files to fix 'chmod akmd' issue, tried not to break anything else
v6 - moved questions to beginning of script, added check to only init repo the first time, added check for existing ROM, modded vendor tree to fix compile issues
v7 - removed CM6 stuff, removed kernel compilation code, removed vendor tree code, changed from CM6 to CM7, fixed path bug, added 32-bit libs to dep list
v8 - added ALL official CM devices (mostly untested), minor update to dependency installer code (4-21-11)
v9 - added an extra check for correct Java version, fixed .zip rename issue
Download links:
v7+ --> https://github.com/gnarlyc/EasyDev-Eris
NOTE: If you have issues with google setup or not being able to pass andy the android at the beginning of setup, please delete Provisions.apk for system/app you shouldn't have a problem, but just incase, this will remedy it. -workshed

I'm all over this sh*t

Oh damn, I'm excited for this. good thing I use ubuntu!
Sent from my ERIS using XDA App

this should be fun once i get my new laptop.

Nice! I will be trying this later.

This is awesome! Thanks alot. What does the 'make clean' option do?

Skrip037 said:
This is awesome! Thanks alot. What does the 'make clean' option do?
Click to expand...
Click to collapse
The make clean removes everything that has been compile so far leaving only the original source.

Skrip037 said:
This is awesome! Thanks alot. What does the 'make clean' option do?
Click to expand...
Click to collapse
It removes any previously built ROMs, etc. It's not needed every time, so I've made it optional in the next version. The problem was that sometimes the script would be broken in some way and wouldn't build a ROM. But, there's so much text displayed to the screen, it's not always easy to notice. So, I was actually flashing the same test ROM over and over instead of getting a new build...

Great work guys. Going to try it out on Arch Linux and if anyone's interested I'll give details about how to get it working there (or just modify the script to detect Arch as opposed to Ubuntu and work accordingly.
<gripe>One complaint: commands (including scripts) should *always* start with a lowercase letter </gripe>

good work gnarlyc & conap.

this sounds great and i will be trying this when i get home. I have just one question. Why would i want to run this instead of conap's rom? Both being pure CM. I see alot of the other cm6 roms have stuff themed, but conap's rom doesn't. I'm assuming this is complete pure cm without little tweaks done by devs of the respective roms. Thanks in advance.

ngc604 said:
this sounds great and i will be trying this when i get home. I have just one question. Why would i want to run this instead of conap's rom? Both being pure CM. I see alot of the other cm6 roms have stuff themed, but conap's rom doesn't. I'm assuming this is complete pure cm without little tweaks done by devs of the respective roms. Thanks in advance.
Click to expand...
Click to collapse
Some people just like to "roll their own", more or less. If you like having someone else make improvements and fix issues for you, then you'll probably want to stick with another ROM.

I would love to make my own fixes and tweaks but i dont have the knowledge nor the time to gain said knowledge. guess i will just stick with the devs roms. thanks

Very very exciting. I am installing Ubunto 10.4 now. So does EasyDev-v2 pull from the CM6 nightlies or the stable version and can we change where it pulls from for the CM6 source. This is great.

Will have to check this out later. Always wanted to understand the compile process, always to busy with other software projects. Thanks for building this resource for the rest of us.

morrisdan said:
Very very exciting. I am installing Ubunto 10.4 now. So does EasyDev-v2 pull from the CM6 nightlies or the stable version and can we change where it pulls from for the CM6 source. This is great.
Click to expand...
Click to collapse
Hmmm. Someone correct me if I'm wrong, but I'm pretty sure that this is currently grabbing 'stable'.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b froyo
I'm thinking that to get the nightly, we'll have to change that to:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b master
I'll try it as soon as I can. You got me to thinking that we could add that as an option, if I understand this correctly.

Nightly vs Stable
Yes, you answered my question regarding nightly and stable. I am having fun so far. I got all the necessary packages installed. That was pretty easy using the Ubunto package manager deal. So where do I find the proprietary.zip now? I am almost there to cook this sucker up.

morrisdan said:
Yes, you answered my question regarding nightly and stable. I am having fun so far. I got all the necessary packages installed. That was pretty easy using the Ubunto package manager deal. So where do I find the proprietary.zip now? I am almost there to cook this sucker up.
Click to expand...
Click to collapse
I was apparently wrong about the "-b master" switch, but I think I mostly got it right...
Right now, you'll have to grab the files listed in the OP and zip them up into a file called 'proprietary.zip'. Then place it in the same directory that you run the script from.
I'm working on a way that you can just place an existing ROM there, and it will extract the proprietary files for you. That should be in v3.

Proprietary.zip Files
Can I download CELB Froyo 3.8 and uncompress it and do searches for those files and pull them out and zip them up?

morrisdan said:
Can I download CELB Froyo 3.8 and uncompress it and do searches for those files and pull them out and zip them up?
Click to expand...
Click to collapse
Yes, that should work fine. Here's a list with the paths -
https://github.com/Conap30/android_device_htc_desirec/blob/master/extract-files.sh

Building CM10

I had been building CM for my Nook Color using the most excellent instructions from Fattire and group. I got a new p5113 and attempted to build using the instructions from http://wiki.cyanogenmod.org/index.php?title=Build_for_p5113
However, when I got to
Code:
breakfast p5113
there was no device p5113. p5110 was there, but not p5113. How I got it to work was to re-repo init using
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
rather than
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Once I did that I could successfully
Code:
breakfast p5113
and finish the process. It looks to be building as expected now, though I am sure it will be several hours before I know for sure. I will post back if the build stops.
Please forgive me if this is covered elsewhere, but a quick search didn't help me and I could not make a comment directly on the page linked above with the instructions. Hopefully this will help someone who is stuck at this same point.
Cheers

So I need to read more closely. The directions linked to in the OP for installing p5113 ("http://wiki.cyanogenmod.org/index.ph...uild_for_p5113") are really for p5110. But I was trying to breakfast/brunch p5113. However- all of the necessary code downloads when I repo sync '-b jellybean' and breakfast p5113.
Problem is that I had already installed one of the prebuilt CM10 nightlies, so the vendor files that I pulled are incorrect. At least I think that is correct. When I get home I will re-flash back to stock and try to pull the vendor files for p5113 and try to build again. Since the only difference AFAIK is the IR Blaster, maybe that is close to working.

Actually, CM10.1 still in developing. I think the cyanogenmod team will be bring their ROM in stable soon.

jamesh0317 said:
So I need to read more closely. The directions linked to in the OP for installing p5113 ("http://wiki.cyanogenmod.org/index.ph...uild_for_p5113") are really for p5110. But I was trying to breakfast/brunch p5113. However- all of the necessary code downloads when I repo sync '-b jellybean' and breakfast p5113.
Problem is that I had already installed one of the prebuilt CM10 nightlies, so the vendor files that I pulled are incorrect. At least I think that is correct. When I get home I will re-flash back to stock and try to pull the vendor files for p5113 and try to build again. Since the only difference AFAIK is the IR Blaster, maybe that is close to working.
Click to expand...
Click to collapse
You actually are almost correct... Recently they completely removed the 3113 and 5113 versions as the only difference was in the IR blaster, which doesn't work on CM anyways...
Sent from my XT907 using Tapatalk 2

[Script] Build ICS/JB Kernel

Thanks to the amazing work of mapkel you can now use this script to compile and pack the kernel!
UPDATE: read mapkel's post here: http://forum.xda-developers.com/showpost.php?p=43419784&postcount=45
Thank him here.
This is an informative guide and I decline responsibility for any damage to your device.
Do not attempt to build this kernel if you are going to complain to devs about issues.
That being said, mapkel has made this so that even those with little knowledge can build the kernel without any issues. If you do have any issues, post here and I will try to assist you.
The following is a complete tutorial to building the kernel.
Credits:
Kernel Devs: krystianp, lehjr, Epinter, and mmontuori for making this kernel; without them there is no kernel.
Big thanks to mapkel for this amazing script.
Another big thanks to benouch for the original idea.
A final big thanks to zen25205 for help with building the kernel and getting the Linaro Toolchain.
Kernel Kitchen
I suggest building this with the latest CM9 MROM until the public beta is released.
You need to install Ubuntu 12.04 64bit (Google for instructions)
Prerequisites:
Open a terminal and run the following commands the first time:
Code:
sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2
Code:
sudo apt-get install git
If there are any issues with this guide, or if you have any issues building the kernel, post here and I will assist you as best I can.

Stage 1 (start at stage 2 if you have already built the kernel using this script:
Code:
cd ~
Code:
wget https://www.cubby.com/pl/kernel_script.zip/_25f010125b924ec7a42fe1d66245f36a
Code:
unzip ${HOME}/kernel_script.zip -d ${HOME}
Stage 2:
Code:
cd kernel
Code:
./script
There will be 4 choices to make throughout the script:
Clean install y/n (choose "n" on first run of script)
What defconfig? (Usually it is MROM but in the last update it is temporarily MROM2)
Compile CM9 or CM10 kernel? (self explanatory)
Name of config (Any name works. I chose "olympus".)

enjoy)

Built but cam not working

paladin881 said:
Built but cam not working
Click to expand...
Click to collapse
cameras disabled due to battery drain
Click to expand...
Click to collapse
https://github.com/CyanogenMod-Atrix/android_kernel_motorola_olympus/commits/master

Post here if it worked well for you. Give some feedback for mapkel.

No Wifi
Cheers, the script works great on Ubuntu 11.10, without a hic.
However, upon flashing the kernel, I get no wifi. I'm going to try your step by step tutorial...
Edit: I built the kernel using MROM2 defconfig and for CM10, and flashed "someone's" CM10

Newbleeto said:
Cheers, the script works great on Ubuntu 11.10, without a hic.
However, upon flashing the kernel, I get no wifi. I'm going to try your step by step tutorial...
Edit: I built the kernel using MROM2 defconfig and for CM10, and flashed "someone's" CM10
Click to expand...
Click to collapse
Strange..
The modules should copy with this.
Try CM9

atrix4g18 said:
Strange..
The modules should copy with this.
Try CM9
Click to expand...
Click to collapse
I'm updating Ubuntu, maybe the problem is on my end. Will try CM9 in the meanwhile and let you know!

Newbleeto said:
I'm updating Ubuntu, maybe the problem is on my end. Will try CM9 in the meanwhile and let you know!
Click to expand...
Click to collapse
You won't be able to do both.
If you compiled the kernel for CM10 you will only be able to use it on CM10.
Unless you are able to update Ubuntu as you compile the kernel for CM9.

atrix4g18 said:
You won't be able to do both.
If you compiled the kernel for CM10 you will only be able to use it on CM10.
Unless you are able to update Ubuntu as you compile the kernel for CM9.
Click to expand...
Click to collapse
It's impossible to compile while updating, didn't remember that, silly me :silly:
Anyhoot, wifi still doesn't work in Ubuntu 12.04. Fresh install on a different PC, way faster than updating
I'll try CM9 tomorrow, should've been asleep for a while

Can anyone or everyone list sites that work with a direct link.
That means I go to www.sitename/filename.zip and it starts downloading.

All I can think of right now is a cloud storage like Dropbox or Google Drive. I know Dropbox has a traffic limit for public files. Don't know about Google drive
Sent from my MB860 using xda app-developers app

upndwn4par has unlimited bandwidth, iirc. Maybe you can contact him and ask if you can host that one tiny script file there?
Or you could sign up with a free webhost and upload it there. There are several free webhosts with unlimited bandwidth (with a very limited space as trade-off, but I think it's more than enough for the script file).

If it's just a single script, maybe something like pastebin.com or similar might be an option? A little inconvenient since you have to copy and paste content instead of just download, but AFAIK it does have unlimited bandwidth.

atrix4g18 said:
Can anyone or everyone list sites that work with a direct link.
Click to expand...
Click to collapse
Maybe copy.com? Here is my ref for extra 5 GB: https://copy.com?r=qfhUoV
If this does not solve the problem, I can provide space for the script on my own server with a separate FTP account.

priard said:
Maybe copy.com? Here is my ref for extra 5 GB: https://copy.com?r=qfhUoV
If this does not solve the problem, I can provide space for the script on my own server with a separate FTP account.
Click to expand...
Click to collapse
Doesn't have a direct download link.

quetzalcoatl2435 said:
Doesn't have a direct download link.
Click to expand...
Click to collapse
Not quite. You can still download a file, for example using wget.
If You have a short public link, for instance: copy.com/PJzYgAUKECQm, You need to open it and copy the full link. In this case: copy.com/s/PJzYgAUKECQm/BetterBatteryStats_xdaedition_1.13.4.0.apk
then:
wget copy.com/s/PJzYgAUKECQm/BetterBatteryStats_xdaedition_1.13.4.0.apk
and done.

I will look at all the suggestions later today.
Thank you.

Delete

[DEV] CM10.1 builds | help needed adding features | "4.2.2 Revival Team"

Hi,
I synced the CM10.1 source last weekend. I mucked about with the kernel. I pointed it to Christopher83's custom toolchain. I built it. It works. I'm content.
However my plan was to revive 4.2.2 and actually ADD to it, otherwise you could just go and download the zip which the Andromadus team uploaded. Unfortunately I've discovered that I'm completely incompetent when it comes to firstly finding things to add, secondly finding the commit, and then thirdly trying to cherry pick and apply the commit so it works. I haven't really got to stage 3 yet.
So here's my suggestion: could someone please work with me or if syncing sources etc. is not possible, at least help me by being knowledgeable enough to know some good features, point me to the commits, and help me fix conflicts so that I can apply them successfully. Therefore I either want a team, the 4.2.2 revival team as it were, or someone or some people to help me if they can't directly interact with the sources. Don't worry if you can't build for whatever reason: if you can sync specific repos, e.g. settings, frameworks base, and modify them, and push them, so that I can build the ROM, that's fine. Anyone who helps at all will be deemed equally if not more important than myself, as I expect I'll ultimately just end up being the builder.
Thanks very much for your support.

I can help you with that. Tell me when you start your project and what errors did you get
Best Regards,
MarcoMarinho

RE: [DEV] CM10.1 builds | help needed adding features | "4.2.2 Revival Team"
_MarcoMarinho_ said:
I can help you with that. Tell me when you start your project and what errors did you get
Best Regards,
MarcoMarinho
Click to expand...
Click to collapse
Thanks firstly I thought a simple thing to do would be to add the recent app screen ram bar from SlimBean, but I can't find the commit anywhere in the SlimRoms github. Perhaps you know where it is or can find it for me, then I could cherrypick it and we could fix the conflicts together and we'd have our first unofficial CM10.1 ROM with additional features!

HTCDreamOn said:
Thanks firstly I thought a simple thing to do would be to add the recent app screen ram bar from SlimBean, but I can't find the commit anywhere in the SlimRoms github. Perhaps you know where it is or can find it for me, then I could cherrypick it and we could fix the conflicts together and we'd have our first unofficial CM10.1 ROM with additional features!
Click to expand...
Click to collapse
Sure
Here is the commit: https://github.com/SlimRoms/frameworks_base/commit/9c1c3c0955d51adc589ec6fbb667a0ae482de24e
You need this to: https://github.com/AOSB/android/commit/a512f16890af8c277c3d1a88c8bca36711b82328

RE: [DEV] CM10.1 builds | help needed adding features | "4.2.2 Revival Team"
_MarcoMarinho_ said:
Sure
Here is the commit: https://github.com/SlimRoms/frameworks_base/commit/9c1c3c0955d51adc589ec6fbb667a0ae482de24e
You need this to: https://github.com/AOSB/android/commit/a512f16890af8c277c3d1a88c8bca36711b82328
Click to expand...
Click to collapse
That looks interesting, but it's for KitKat... I'll try later once I'm confident. In the meantime, how can I get this to work: https://github.com/SlimRoms/packages_apps_Settings/commit/fb2ea42468bea20f09b99048c9e7535b6cde643f I'm OK apart from the very last bit in UserInterface.java, although I'm applying that code to SystemSettings.java anyway. Thanks

@demkantor @_MarcoMarinho_ I've synced the PA source, can you help me at all setting up the vision.adds file? Thanks

Sure thing, assume this is for 4.2 android right?
Sent from my Nexus 4 using XDA Premium 4 mobile app

demkantor said:
Sure thing, assume this is for 4.2 android right?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, as you know I synced the CM10.1 source a while ago so I used repo init --reference to sync the PA jellybean-legacy sources. Thanks for helping

paste this in a folder and title it
local_manifests
then add it to your .repo folder in ROM directory
I commented out a few things you may need to add, and there is possibly more but i dont have time to look into it all right now. just start with this, repo sync, and then build and check for errors
best of luck!
damn.... giving me uknown file, had to zip it first, so unzip the contents!

demkantor said:
paste this in a folder and title it
local_manifests
then add it to your .repo folder in ROM directory
I commented out a few things you may need to add, and there is possibly more but i dont have time to look into it all right now. just start with this, repo sync, and then build and check for errors
best of luck!
damn.... giving me uknown file, had to zip it first, so unzip the contents!
Click to expand...
Click to collapse
Thanks, do I only need to add these to the vision.adds file then, or do I not need a vision.adds file at all now?

HTCDreamOn said:
Thanks, do I only need to add these to the vision.adds file then, or do I not need a vision.adds file at all now?
Click to expand...
Click to collapse
cant say I've ever used a vision.adds file in a source build, I just find the files i need in github, download source, create a local_manifest, sync, check errors for somethings to add to manifest, build, check for errors, google how to fix, fix, fix, fix ,fix, then bam, got a rom that works.
but I can look into this vision.adds business, I don't think it will be necessary as this will place need files in the proper directories in your source code for you, I assume that's what the vision.adds would do?

demkantor said:
cant say I've ever used a vision.adds file in a source build, I just find the files i need in github, download source, create a local_manifest, sync, check errors for somethings to add to manifest, build, check for errors, google how to fix, fix, fix, fix ,fix, then bam, got a rom that works.
but I can look into this vision.adds business, I don't think it will be necessary as this will place need files in the proper directories in your source code for you, I assume that's what the vision.adds would do?
Click to expand...
Click to collapse
Here's the bit from their guide: http://forum.xda-developers.com/showpost.php?p=30958881&postcount=2 I'm not sure what it does though. I'm completely clueless about that whole post actually. I think it just syncs stuff after a sync.. or something. I don't know why though, isn't that what a local manifests file is for?

hmm... it looks like there will be a bit more to make than just the local_manifests
but i would attempt this first and if it doesnt work than follow the direction in that post as there me be a special way needed to build for pa, which i never have tried to build
most of what they are after will get pulled from local_manifests folder and placed appropriately. but at the same time... never used ./rom-build.sh before so this may be specific to pa, as in you need to follow their steps....
eh, just give it a try, if it doesnt work ill help you create those json files and build it the way laid out in their guide!

HTCDreamOn said:
Here's the bit from their guide: http://forum.xda-developers.com/showpost.php?p=30958881&postcount=2 I'm not sure what it does though. I'm completely clueless about that whole post actually. I think it just syncs stuff after a sync.. or something. I don't know why though, isn't that what a local manifests file is for?
Click to expand...
Click to collapse
Isn't easy, you need to add more repos to configure it for our phone.
This is very diferent:
http://forum.xda-developers.com/showpost.php?p=45827346&postcount=3467
As I said before, you need extra repos than CM needs. You can talk to the dev that made the SlimBean for our phone, as it's based on AOSP he needed to configure it as well.

[Guide] [09/14/2015] Building AOSP 5.1.1_r14 for the Nexus 6-Continued!

Building AOSP for the Nexus 6 - Continued!​
Scott is no longer working with the N6 and he has graciously allowed me to continue his thread . We all owe @scrosler a special THANKS for his work on the original thread. Better yet please go buy him a beer!! I also want to personally thank all who contributed to the original thread. You all make it work!!
​
Preface
1. I want to start by saying that I am still a relative newb. I built my first aosp rom for my N9 using the the guide from the original thread and followed up with one for my N6. I hope that by moving this thread forward we can continue to help others get started while we continue our own learning.
2. All questions concerning the build process and setup are welcome. They may not all get answered but please ask.
This guide continuation assumes the following:
1. You have read the original thread's OP and scanned the remainder of that thread before posting here.
2. To get things started you can test a rom built from android-5.1.1_r14. Get rom below. Vendor blobs updated from here and include the updated LYZ28E blobs. I also added some missing build props.
3. I am also linking the github source for the rom. You can build your own. Get github source below.
4. I hope to add a short get started github tut in OP#2 and add a vendor folder setup discussion in OP#3. I'm still trying to figure out how @sykopompos did his. All help on this subject is welcome.
FYI TO ALL!!! All my testing is on USA Verizon netwok.
LINK TO ORIGINAL THREAD OP
Get ROM HERE
Get GIT SOURCE HERE
==========================================================================================================
The following copied from original OP with some minor editing.
This guide assumes the following
Have Ubuntu 14.04 or equivalent setup, fully operation, and up to date. Hard Machine or Virtual, makes no difference. Must meet the minimum specs for compiling. Info from Google HERE
Understand terminal command line entry as this is all command line processes.
Lets Begin!
Add Java
Code:
sudo apt-get install openjdk-7-jdk
Add Build tools (Adds the required packages at the time of this posting)
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Add Repo command (Syncs Google Repository with your local machine)
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Add bin folder to path for repo command (After you do this close Terminal and re-open to institute changes (easy way))
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify Yourself to the Repo (One day you may make commits so think about that when choosing your info!)
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Sync Repo (Download source... Sit back and grab a pop and a sandwich...)
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-5.1.1_r14
repo sync
Note: I use AOSP as my directory name. You can use what you want. You could use "aosp" or "Source" or "android" or "whateveryoulike"
Set up ccache (this makes subsequent compiling much faster!)
First: Close then re-open the terminal so you are in the home root
Code:
sudo gedit .bashrc
export USE_CCACHE=1 <-Append that line to .bashrc then save and close
cd AOSP
prebuilts/misc/linux-x86/ccache/ccache -M 25G <-I use 25 gigs but you can change that value to any size you feel appropriate)
fhem Alternate ccache setup.
Install ccache using package manager (I use synaptic)
set ccache size - One ccache for all directories.
Code:
ccache -M 35G (I use 35 gigs but you can change that value to any size you feel appropriate)
I do not edit my .bashrc I use the following before my final make command. See Readme Build It
You can choose to use or not use ccache for any build/operation from any directory.
Code:
export USE_CCACHE=1
ccache manual
Install proprietary binaries (Needed for things like GPS and Bluetooth, they are not Open Source like Android) (Install proprietary binaries from here in the root of AOSP folder (or whatever you called yours))
Code:
https://developers.google.com/android/nexus/drivers
Run envsetup.sh
Code:
source build/envsetup.sh
Choose Device
Code:
lunch aosp_shamu-userdebug
Build it!
Code:
make -j16 otapackage
Note: using -j16 means 16 worker threads. This is fine if you have 8 logical CPU's so you may need to adjust that to a smaller or larger number if you have more or less Logical CPU's. Example: I have an i7 K edition Haswell so I have 8 logical cores; so I build with -j16. If you have an i5 quad core CPU which is 4 logical cores then you may want to consider -j8 as the set number of worker threads. Oddly enough Google actually recommends 3 to 4 times the number of logical CPU's. When I do that I have nothing but build crashes. You may need to experiment to get the right blend of performance and stability during build!
If you use
Code:
make -j `getconf _NPROCESSORS_ONLN` otapackage
it may take a little longer but it won't crash.
Find it
Should be located here: /home/yourusername/AOSP/out/target/product/shamu
Congrats!
Your know among the elite enthusiast that can build from source! Pat yourself on the back!

Git Hub Tips
There is already much written on git use so I am not going to try and reinvent that wheel!!!! I will provide some usefull links for your reading pleasure. I will also provide some tips based on my personal experiences using git. I have found there are many ways to get the same result using git and there are also many ways to break your your work. I did a lot of trial and error and deleting to learn what works best for me. Start small, don't be intimidated, and stay patient -- it will come. The following assumes we are using a linux distro.
1. Open a GitHub account ----- its easy. Keep it simple. Follow the setup instructions and use recommended HTTPS connection.. I also suggest caching your login info - I use 60 mins for my default cache time.
2. Install git. It is easiest to install Git on Linux using the preferred package manager of your Linux distribution. I use Synaptic Package Manager. Keep it simple. Follow the setup instructions and use recommended HTTPS connection.
3. Git Tools: I prefer using Geany with terminal and File and Tree Browser and VC control plug-ins. There are many tools available and you may need to find one that works for you. You can install Geany and its plug-ins using your distro package manager.
4. ROM Tree Structure Very Important. I recommend keeping your rom GitHub tree structure in line with the Android Git Repositories.
Useful links:
1. http://git-scm.com/docs
2. http://gitref.org/creating/
3. http://forum.xda-developers.com/showthread.php?t=1877040 Thanks @eagleeyetom
4. http://forum.xda-developers.com/showthread.php?t=2763236 Thanks @jabza
5. http://forum.xda-developers.com/showthread.php?t=2329228 Thanks @Red Devil
I hope the above is helpful to getting you started on GitHub. Good Luck!!

reserved vendor folder discussion.

fhem said:
Building AOSP for the Nexus 6 - Continued!​
Scott is no longer working with the N6 and he has graciously allowed me to continue his thread . We all owe @scrosler a special THANKS for his work on the original thread. Better yet please go buy him a beer!! I also want to personally thank all who contributed to the original thread. You all make it work!!
​
Preface
1. I want to start by saying that I am still a relative noob. I built my first aosp rom for my N9 using the the guide from the original thread and followed up with one for my N6. I hope that by moving this thread forward we can continue to help others get started while we continue our own learning.
2. All questions concerning the build process and setup are welcome. They may not all get answered but please ask.
This guide continuation assumes the following:
1. You have read the original thread's OP and scanned the remainder of that thread before posting here.
2. To get things started you can test a rom built from android-5.1.1_r4 using Sykopompos vendor blobs for 5.1. Get rom below.
3. I am also linking the github source for the rom. You can build your own. Get github source below.
4. I hope to add a short get started github tut in OP#2 and add a vendor folder setup discussion in OP#3. I'm still trying to figure out how Sykopompos did his. All help on this subject is welcome.
FYI TO ALL!!! All my testing is on USA Verizon netwok.
LINK TO ORIGINAL THREAD OP
Get ROM HERE
Get GIT SOURCE HERE
Click to expand...
Click to collapse
Lots and lots of dark magic ?

Hey great to see you. I thought you were kyaking LOL. You coming back for M????

fhem said:
Hey great to see you. I thought you were kyaking LOL. You coming back for M????
Click to expand...
Click to collapse
I actually just ordered my kayaking last night so hopefully I'll have it in time for next weekend.
Just popping in really and checking M out and seeing how it develops

sykopompos said:
I actually just ordered my kayaking last night so hopefully I'll have it in time for next weekend.
Just popping in really and checking M out and seeing how it develops
Click to expand...
Click to collapse
Still waiting for the full platform on aosp. Hey did you diff the stock rom and aosp rom to get your vendor blobs. I was setting up with BeyondCompare to give it a look. LOL Enjoy your time off and your family. Life is too short.

fhem said:
Still waiting for the full platform on aosp. Hey did you diff the stock rom and aosp rom to get your vendor blobs. I was setting up with BeyondCompare to give it a look. LOL Enjoy your time off and your family. Life is too short.
Click to expand...
Click to collapse
For the most part, you can diff and find file differences but aosp has it's own files and stuff like that so you gotta be able to figure out what they do

sykopompos said:
For the most part, you can diff and find file differences but aosp has it's own files and stuff like that so you gotta be able to figure out what they do
Click to expand...
Click to collapse
I was afraid you were going to tell me that. :laugh: Oh well It will give my old brain and google a workout. hahahaha Thanks and enjoy yourself.

Hey @fhem! Glad to see you take over, you're always very helpful!
In your Repo Int code above, did you mean "android-5.1.1_r4"? I wanted to double check that part for the guide.

purian23 said:
Hey @fhem! Glad to see you take over, you're always very helpful!
In your Repo Int code above, did you mean "android-5.1.1_r4"? I wanted to double check that part for the guide.
Click to expand...
Click to collapse
Yep. That's the latest. That's what I built above if you look at the fhemaosp default manifest.

fhem said:
Yep. That's the latest. That's what I built above if you look at the fhemaosp default manifest.
Click to expand...
Click to collapse
Okay cool! Just trying to save some headache if someone grabs the guide one listed lol.

purian23 said:
Okay cool! Just trying to save some headache if someone grabs the guide one listed lol.
Click to expand...
Click to collapse
Fixed thanks for catching that typo.

sykopompos said:
I actually just ordered my kayaking last night so hopefully I'll have it in time for next weekend.
Just popping in really and checking M out and seeing how it develops
Click to expand...
Click to collapse
Hello @sykopompos, I am just glad to see you here! Thanks for all your contributions!
I let @fhem take over the thread since he is more active than I. But I appreciate all the help you have given and will continue to give!
Knowledge is TRULY priceless!
-Scott
EDIT: Can someone put that on my tombstone, lol

Can we have guide about building ROM from open source? e.g LG open source. Actually I was trying to build a M1 review ROM with the LG open source but it fails. I tried several times and finally give op due to errors. I downloaded the android source and then follow this guide and then download LG G4 ROM from following.
http://opensource.lge.com/osSch/list?types=ALL&search=H815
I set up the environment and then started building but it fails again and again. I think it will be very helpful for every one who interested in building ROM from open source. Thanks
Sent from my LG-H815 using Tapatalk 2

janjan said:
Can we have guide about building ROM from open source? e.g LG open source. Actually I was trying to build a M1 review ROM with the LG open source but it fails. I tried several times and finally give op due to errors. I downloaded the android source and then follow this guide and then download LG G4 ROM from following.
http://opensource.lge.com/osSch/list?types=ALL&search=H815
I set up the environment and then started building but it fails again and again. I think it will be very helpful for every one who interested in building ROM from open source. Thanks
Sent from my LG-H815 using Tapatalk 2
Click to expand...
Click to collapse
I have never worked with any LG source codes. I would suggest you start your own thread on the LG G4 Forum. It definately sounds like you got enough to get one rolling. Good luck with the G4.

Hello,
I am trying to build android 5.1.1_r6 for the Nexus 6 and was able to get it to build and install. Had a weird issue where gapps would not install, but I think I fixed that by flashing a different set of gapps. My issue is that I am unable to hear people through the handset speaker when I make phone calls. I have no idea what it is. Apparently they can hear me, but I cant hear them. I can use speaker phone, but even that seems lower volume than normal.
Also, side question, since I am building AOSP 5.1.1_r6 am I supposed to use the preview binaries found here: https://developers.google.com/android/nexus/blobs-preview
or just use the factory image binaries?
Thank you

KerryWood34 said:
Hello,
I am trying to build android 5.1.1_r6 for the Nexus 6 and was able to get it to build and install. Had a weird issue where gapps would not install, but I think I fixed that by flashing a different set of gapps. My issue is that I am unable to hear people through the handset speaker when I make phone calls. I have no idea what it is. Apparently they can hear me, but I cant hear them. I can use speaker phone, but even that seems lower volume than normal.
Also, side question, since I am building AOSP 5.1.1_r6 am I supposed to use the preview binaries found here: https://developers.google.com/android/nexus/blobs-preview
or just use the factory image binaries?
Thank you
Click to expand...
Click to collapse
I haven't been able to get _r6 to build due to errors in frameworks/opt ever since merging so good for you on that. As for the binaries It was found a while back that the Google one were incomplete. People were using The vendor files from chroma in their stead. I haven't spoken to fhem in a couple of days but it looks like his github is under construction atm. I forked the vendor repo from him since he had changes that fixed some no sound issues as well. Again I've yet to build _r6 successfully so no idea if these will solve your issue but you're welcome to try them out? You can get them from my github here: https://github.com/rockinroyle/platform_vendor_moto_shamu
Let us know how it goes? I'm trying again after I clone frameworks from scratch.

rockinroyle said:
I haven't been able to get _r6 to build due to errors in frameworks/opt ever since merging so good for you on that. As for the binaries It was found a while back that the Google one were incomplete. People were using The vendor files from chroma in their stead. I haven't spoken to fhem in a couple of days but it looks like his github is under construction atm. I forked the vendor repo from him since he had changes that fixed some no sound issues as well. Again I've yet to build _r6 successfully so no idea if these will solve your issue but you're welcome to try them out? You can get them from my github here: https://github.com/rockinroyle/platform_vendor_moto_shamu
Let us know how it goes? I'm trying again after I clone frameworks from scratch.
Click to expand...
Click to collapse
I had no luck with r6 either. I reverted back to r5. I looked at chroma/zephk on git and I don't think he took the whole r6 merge to his git repos - not sure what he did.
I'm sticking to to r5 for now.

I've been building r6 fine with zero issues. Did notice the speaker issue on call but fixed it with two commits from chroma in device/moto/shamu for audio. I've also been using the latest binaries posted by google on the aosp page, no issues that I can tell. WiFi calling/normal calling, sound all around, SMS/MMS, all works.
Sent from my Nexus 6 using Tapatalk