[Build Guide][Flo/Deb] - Pure AOSP 6.0.0_r1

Search This thread

vibranze

Inactive Recognized Developer
Feb 22, 2007
1,377
84
Singapore
vibranze.blogspot.com
I just flashed my virgin ROM and found out that there's no Play store and Google account to add, it seems like is very very basic ROM.
Any ideas how do I add Google account? Thanks.
 

vibranze

Inactive Recognized Developer
Feb 22, 2007
1,377
84
Singapore
vibranze.blogspot.com
Did you flash gapps?
There is a link at the bottom of the OP.


Or you can get them from here
http://goo.im/gapps

You need the 20130813 ones.

Thanks. So Google's account and Play Store are not part of the AOSP pristine ROM and we have to flash Gapps.
Is it possible to include the Gapps in the build process?
Cheers.

Update: Flashed SuperSU and Gapps, everything's working fine. Question: the Gapps is from CM10.2, is it possible to pick the source from Google and build it together with ROM?
Security setting also F/C-ing here. Attempt to rebuild now.

I found out that yesterday I was using binaries of JSS15Q, now I redownload the binaries but for JSS15R and rebuild. Will update at the end of the day.

:)
 
Last edited:

Scott

Retired Recognized Developer
Thanks. So Google's account and Play Store are not part of the AOSP pristine ROM and we have to flash Gapps.
Is it possible to include the Gapps in the build process?
Cheers.

Update: Flashed SuperSU and Gapps, everything's working fine. Question: the Gapps is from CM10.2, is it possible to pick the source from Google and build it together with ROM?
Security setting also F/C-ing here. Attempt to rebuild now.

I found out that yesterday I was using binaries of JSS15Q, now I redownload the binaries but for JSS15R and rebuild. Will update at the end of the day.

:)

You are correct Android does not have any Gapps installed.

I listed the Gapps that I used with my build in Post #1. They worked well.
 

jaredmorgs

Senior Member
Apr 12, 2012
248
68
Brisbane
I changed the name of the thread to "[ROM][FLO][10/8][JLS36G] - Pure AOSP ROM - AOSP build discussion for newbs by newbs!"

So maybe more people will join in and discuss instead of ask for changes.

Maybe we can start a movement.

It's a shame this thread can't get featured in some way by the XDA soc net accounts. Only folks who are hunting for nexus 7 2013 ROMs will stumble across it.
 

mpmilestogo

Senior Member
Aug 9, 2009
348
66
Union City California
I'm interested in joining the fun :). My challenge is I don't have a bunch of desktop or even laptop systems sitting around that can actually work to compile AOSP. I'm typing this on a 6 year old IBM Thinkpad T60 running Debian Linux testing. Won't work for compiling stuff. In the past though I did compile AOSP ROMs for the HTC Sensation and we had quite the little collaboration group back then as well. Very enriching to have that kind of community working on developing AOSP. That's kinda what I see this is becoming and it really helped me learn the basics since I followed along and compiled the ROM as well.

My main point though is that I am considering using a Debian or Ubuntu VPS for the heavy lifting and am particularly looking at linode for the service since I've done stuff with them before. Can anyone comment on using a VPS solution for this work? The 2g of memory offering is the one I'm considering.

Thanks.
 

meekrawb

Senior Member
Mar 25, 2012
1,472
1,031
TX
Last edited:

Scott

Retired Recognized Developer
Who votes for scrosler to make a youtube video guide :) for us newbs put your hands up in the air :)
I vote that scrosler is very busy person and would never have time for that :p


I'm interested in joining the fun :). My challenge is I don't have a bunch of desktop or even laptop systems sitting around that can actually work to compile AOSP. I'm typing this on a 6 year old IBM Thinkpad T60 running Debian Linux testing. Won't work for compiling stuff. In the past though I did compile AOSP ROMs for the HTC Sensation and we had quite the little collaboration group back then as well. Very enriching to have that kind of community working on developing AOSP. That's kinda what I see this is becoming and it really helped me learn the basics since I followed along and compiled the ROM as well.

My main point though is that I am considering using a Debian or Ubuntu VPS for the heavy lifting and am particularly looking at linode for the service since I've done stuff with them before. Can anyone comment on using a VPS solution for this work? The 2g of memory offering is the one I'm considering.

Thanks.
I know people that build on VPS. 2G's memory? Maybe. How many cores and threads? I am runnign on 8 threads 4 cores Xeon x5550 with 120 gig SSD and 16 Gigs DDR3. I rarely see RAQM usage above 2 gigs with building at 24 threads (Make -j24).


If you ever need help with source builds, setting up github, etc just let me know. I have a tutorial here on xda already and can expand upon anything that needs clarification.

http://xdaforums.com/showthread.php?t=1762641

私のONEから送信される。
Learning to git hub would be great. Also if you can comment on the error that we are getting in regards to the Repo command. Its not finding public keyes. Any thoughts?
 

Scott

Retired Recognized Developer
Which repo command is giving trouble? Just did a sync with no errors.

"Failed with could not verify the tag 'v1.12.4'"

Same one the prior guy got and he had to use a different repo binary. I tried the binary he linked to and STILL got that error :confused:

Any thoughts?

Keep in mind this was a complete fresh install of ubuntu last night with all updates applied.
 

meekrawb

Senior Member
Mar 25, 2012
1,472
1,031
TX

Scott

Retired Recognized Developer
The only thing I can find about verifying tags is at the bottom of this page

http://source.android.com/source/downloading.html

Thats for the git, I believe. I think my issue is that "repo" command was updated since now and when I released my first ROM and there is no signed repo out now. But that cant be. That would mean any new Android developer would not be able to download the repo until google fixes this. Which I refuse to believe.

Im going to google it tonight. If not I will try to import that key as you noted.
 

Silvest

Member
Sep 23, 2013
13
3
Delft
Thats for the git, I believe. I think my issue is that "repo" command was updated since now and when I released my first ROM and there is no signed repo out now. But that cant be. That would mean any new Android developer would not be able to download the repo until google fixes this. Which I refuse to believe.

Im going to google it tonight. If not I will try to import that key as you noted.

http://www.marshut.com/wrrts/repo-release-1-12-4.html

I used and it worked=]:
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo >
~/bin/repo
chmod a+x ~/bin/repo
 
  • Like
Reactions: Scott

Scott

Retired Recognized Developer

rocksyjj

Senior Member
Sep 30, 2013
176
42
keep up the grerat work scott,just a small question is linaro part of aosp or is that a different source all together
i see some roms with this added what does it do
 

Top Liked Posts

  • There are no posts matching your filters.
  • 411
    This is a PURE AOSP ROM build guide. I have opted not to post an actual AOSP ROM based on 6.0.0 due to the fact I just dont care for it much. The instructions are up to date as of 10/21/2015



    Deprecated-> This thread is about learning to build your own ROM following the instructions in post #2. The ROM posted in this thread is for example output. Feel free to download and use the ROMS @GROGG88 and I build! Feel free to try and build your own. We will try to help!

    Quick Change Log
    • 10/21 - Updated guide to reflect Android version 6.0.0_r1. No ROM for download (at this time).
    • 1/17 - Updated build with official 5.0.2 Binaries. Fixed Browser "Settings" crash.
    • 12/19 - Updated my Flo builds to Android 5.0.2_r1
    • 12/9 - Updated my Flo build. Will not be doing a Deb Build any more.
    • 12/2 @GROGG88 has updated his builds. I have not! I will update tomorrow. I did however get thefactory stock rooted ROM up HERE!
    • 11/18 - @GROGG88 and I have joined forces to create two ROMS! I will be creating PURE AOSP ROMS and he will be creating Modified ROMS with many useful features! Each ROM can als be user built because all commits are shared in post #2!!!
    • 11/15 - B8 - Updated the 5.0.0_r6. Deb is only using preview binaries due to lack of final binary files.
    • 11/14 - B7 - Updated the 5.0.0_r5. Deb is only using preview binaries due to lack of final binary files.
    • 11/10 - B6 - File system install instead of block install, Added Google Location Services to framework, Fixed a root issue that couple DEB users were having
    • 11/9 - B5 - Changed wallpaper again. Fixed stock recovery at source level (Thanks to @Gnome and @GROGG88)
    • 11/8 - B4 - Changed wallpaper to android 5 Wallpaper, fixed reverting to stock recovery (No need for save-recovery.zip), pre-rooted boot.img (No need for extra boot.img!)
    • 11/7 - B3 - Removed it. Bad files. Reverted back to Build 2.
    • 11/5 - B2 -- Fixed MTP bug that google has left in every version of AOSP, made ROM recovery flashable and added 2 zips to the OP
    • 11/4 - B1 - Update to 5.0.0_r2. PC install via fastboot


    Additional Downloads
    • Root by @Chainfire HERE!
    • Gapps for Lollipop HERE! There may be others so shop around!
    • Stericson's Busybox in flashable zip format is attached! Thanks to @Stericson for the binaries!




    @GROGG88's Special Builds are HERE!


    MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed



    Please hit Thanks! It just as easy as hitting Download!
    82
    Ubuntu 14.04 Set up and Build Guide

    Updated 11/05/2014

    Feel free to ask any questions about the build process. Do not ask questions about Ubuntu!

    This guide assumes the following
    1. Have Ubuntu 14.04 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
    2. Understand terminal command line entry as this is all command line processors.
    3. You are not here to ask for help with Linux, only the Android build process!


    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 "you@youremail.com"
    git config --global user.name "yourpreferredusername"

    Synch 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-6.0.0_r1
    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"


    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:
    [url]https://developers.google.com/android/nexus/drivers[/url]



    Run envsetup.sh
    Code:
    source build/envsetup.sh

    Choose Device
    Code:
    lunch

    Build it!
    Code:
    make -j8 otapackage


    See Build Notes and ramblings from me in post #3!
    60
    I have decided to bring this project out of the shadows. The builds are now accessible through dedicated device threads:

    hammerhead

    flo

    deb
    52
    Notes
    • The ROM build will be a PURE AOSP ROM with no Gapps at all. See links in post #1 to PA Gapps for a good set of Google Apps!
    • The ROM will also have terminal level SU. So becareful! In other words its fully rooted and could be open to vulnerabilities. Flash your favorite Superuser Package if you need it. I dont. I recommend SuperSU by @Chainfire HERE. Download the flashable zip and flash after you flash ROM.
    • make -j8 is the number of worker threads that the make command will use to build. To me 8 is a safe number for an i7 processors. For an i5 Processor I would use -j4. I have experimented with a multitude of different values and it seems to me that the number of logical cores is also the best number to use with the make command.
    • Google recommends between -j24 and -j32 (to me that is excessive and causes my machine to error out every once in a while). Keep in mind the higher you push the more load the CPU will undertake. If your O/C'ing real hard you better have some nice cooling! I had to cut back OC on my 4770k from 4.65 to 4.4 with a Corsair H60 cooler just so it wouldn't over heat. When in doubt start low.
    • My i7 machine clocked at 4.4 and 16 gigs of RAM on a Samsung 840 Pro 256 Gig SSD take about 38 minutes to build the entire ROM.
    • With a 50 Meg download link it took maybe 30 to 45 minutes to sync the repo.

    Changes from Source
    27
    Build 6 is up!


    The following changes were made...


    • File system install instead of block install
    • Added Google Location Services to framework
    • Fixed a root issue that couple DEB users were having



    The ROM is now like a standard ROM install as far as the system.dat vs a /system install. What does this mean? It means you edit the ROM now like add your own apps, take things out and repost it with your changes (as long as credit is given).

    Edit: I posted a Diff of all changes made from Source to this ROM. Its in post #2 for anyone wanting to know the changes that were made to get it where its at.

    Enjoy!