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

Search This thread
By:
Advanced…
BreckZeBoulay

BreckZeBoulay

Senior Member
Oct 23, 2012
1,379
640
Boulay in Frankreich :D
Questions for GROGG88 and/or scrosler concerning compiling AOSP.

5.1.0_r1 is synchronised on my computer, and I have made a rom AOSP 5.1.0_r1 for my device (hammerhead).
Now 5.1.0_r3 is out.
Do I have to delete all files of _r1 version and make an entire synchronised of _r3 ?
If not, what files/directories can I keep and what files/directories do I have to delete ?
 
Last edited:
sykopompos

sykopompos

Recognized Developer
Jun 26, 2008
15,322
29,134
flithydelphia
BreckZeBoulay said:
Questions for GROGG88 and/or scrosler concerning compiling AOSP.

5.1.0_r1 is synchronised on my computer, and I have made a rom AOSP 5.1.0_r1 for my device (hammerhead).
Now 5.1.0_r3 is out.
Do I have to delete all files of _r1 version and make an entire synchronised of _r3 ?
If not, what files/directories can I keep and what files/directories do I have to delete ?
Click to expand...
Click to collapse

Depends on any changes you made. The only changes were build id numbers in platform build. About 3 minor changes that merge in with no conflicts in frameworks base, one in settings.
If you don't have any files modified then just sync r3 instead of r1
 
BreckZeBoulay

BreckZeBoulay

Senior Member
Oct 23, 2012
1,379
640
Boulay in Frankreich :D
I forgot sykopompos :D

Your answer is specifically for the example I give. And I modify nothing, just AOSP out of the box. I don't have the skill to play with that kind of stuff ^^
But generally, what's the good and sure method, total "wipe" ?
 
sykopompos

sykopompos

Recognized Developer
Jun 26, 2008
15,322
29,134
flithydelphia
BreckZeBoulay said:
I forgot sykopompos :D

Your answer is specifically for the example I give. And I modify nothing, just AOSP out of the box. I don't have the skill to play with that kind of stuff ^^
But generally, what's the good and sure method, total "wipe" ?
Click to expand...
Click to collapse

With as minimal as the changes were between r1 and r3, you can get away with just reinit your manifest to r3 tag instead of r1 and then repo sync. You can then just make otapackage after that without a make clean/clobber and should be able to dirty flash with no problem

Just a heads up though, hammerhead has updated 5.1 props from 47I, it is mostly camera related stuff though
 
BreckZeBoulay

BreckZeBoulay

Senior Member
Oct 23, 2012
1,379
640
Boulay in Frankreich :D
sykopompos said:
With as minimal as the changes were between r1 and r3, you can get away with just reinit your manifest to r3 tag instead of r1 and then repo sync.

Just a heads up though, hammerhead has updated 5.1 props from 47I, it is mostly camera related stuff though
Click to expand...
Click to collapse
but if there are more differences (and generally speaking), the best method is to erase all datas on the computer (?)

Thanks to pointing this. This morning the 47I binaries were not available.
Let's go for a fresh compiling of 5.1.0_r3
 
sykopompos

sykopompos

Recognized Developer
Jun 26, 2008
15,322
29,134
flithydelphia
JamFan05 said:
Would it be possible to clone this into my source directory. Would I have to do anything extra to make it work. Sorry I'm new to all of this
Click to expand...
Click to collapse

I make my binaries so they are compatible anywhere and have redundancy in case things are missing. You can download it, clone it, add it to your vendor to fetch, just make sure that those _ end up being / folders
 
sykopompos

sykopompos

Recognized Developer
Jun 26, 2008
15,322
29,134
flithydelphia
JamFan05 said:
Would I clone it into the root of my source folder or into my vendor folder?
Click to expand...
Click to collapse

Easiest way would be to go into your vendor folder, make a folder called lge, then CD into that and then clone it. When that is done you will have a folder called vendor_lge_hammerhead there, just rename it to hammerhead and you are good to go.

I'll cover how to modify the manifest at some point to show how to have it fetch when you repo sync.

If you have any existing vendor files extracted though for hammerhead, especially the ones from the nexus binaries page, you will want to remove them since it will try to pull from both sets for hammerhead and they will conflict and u will get build errors
 
JamFan05

JamFan05

Senior Member
Jan 25, 2012
293
131
Burlington
sykopompos said:
Easiest way would be to go into your vendor folder, make a folder called lge, then CD into that and then clone it. When that is done you will have a folder called vendor_lge_hammerhead there, just rename it to hammerhead and you are good to go.

I'll cover how to modify the manifest at some point to show how to have it fetch when you repo sync.

If you have any existing vendor files extracted though for hammerhead, especially the ones from the nexus binaries page, you will want to remove them since it will try to pull from both sets for hammerhead and they will conflict and u will get build errors
Click to expand...
Click to collapse

Thanks for the help. I did exactly what you said and it built. But when I flashed it I got com.Qualcomm.timeservice fc and camera fc.
 
7

7786

Senior Member
Aug 7, 2011
258
112
Hey everyone,

I followed this guide and was able to successfully compile an AOSP 5.1 ROM for my nexus 7, was even able to include some cherry picked features in there. My problem is, the tablet keeps rebooting every 15 minutes throwing this error:

Code: 
E/Sensors ( 1573): sns_fsa_la.c(386):fsa: fflush failed, 9
E/Sensors ( 1573): sns_fsa_la.c(386):fsa: fflush failed, 9
W/Sensors ( 1573): sns_smr_la.c(446):smr_la: smr_apps_la_thread_main is starting, fd=12, sns_smr.en_rx_msg_ptr=b6f959d0
W/Sensors ( 1573): sns_sam_app.c(6827):sns_sam_reg_algo: Registering algo service 16, err 0
E/Sensors ( 1573): sns_debug_main.c(565):Debug Config File missing in EFS!
E/        (  184): invalid crash request of size 4 (from pid=1573 uid=0)
E/Sensors ( 1602): sns_fsa_la.c(386):fsa: fflush failed, 9
E/Sensors ( 1602): sns_fsa_la.c(386):fsa: fflush failed, 9
W/Sensors ( 1602): sns_smr_la.c(446):smr_la: smr_apps_la_thread_main is starting, fd=12, sns_smr.en_rx_msg_ptr=b6f1b9d0
W/Sensors ( 1602): sns_sam_app.c(6827):sns_sam_reg_algo: Registering algo service 16, err 0
E/Sensors ( 1602): sns_debug_main.c(565):Debug Config File missing in EFS!
E/        (  184): invalid crash request of size 4 (from pid=1602 uid=0)
E/Sensors ( 1612): sns_fsa_la.c(386):fsa: fflush failed, 9
E/Sensors ( 1612): sns_fsa_la.c(386):fsa: fflush failed, 9
W/Sensors ( 1612): sns_smr_la.c(446):smr_la: smr_apps_la_thread_main is starting, fd=12, sns_smr.en_rx_msg_ptr=b6fe59d0
W/Sensors ( 1612): sns_sam_app.c(6827):sns_sam_reg_algo: Registering algo service 16, err 0
E/Sensors ( 1612): sns_debug_main.c(565):Debug Config File missing in EFS!
E/        (  184): invalid crash request of size 4 (from pid=1612 uid=0)
E/Sensors ( 1621): sns_fsa_la.c(386):fsa: fflush failed, 9
E/Sensors ( 1621): sns_fsa_la.c(386):fsa: fflush failed, 9
W/Sensors ( 1621): sns_smr_la.c(446):smr_la: smr_apps_la_thread_main is starting, fd=12, sns_smr.en_rx_msg_ptr=b6fb89d0
W/Sensors ( 1621): sns_sam_app.c(6827):sns_sam_reg_algo: Registering algo service 16, err 0
E/Sensors ( 1621): sns_debug_main.c(565):Debug Config File missing in EFS!

This problem seems to go away if I flash a different kernel, however I didn't even touch the stock kernel. All I did was add a few settings features, included the 5.0.2 blobs from googles website, and that was it. Tried searching but only found few people with this issue and no one seemed to have a solid solution. Anyone run into this one before?
 
BreckZeBoulay

BreckZeBoulay

Senior Member
Oct 23, 2012
1,379
640
Boulay in Frankreich :D
This topic is sleeping :p

Can someone explain me this error when I try to sync the new AOSP 6.0.0_r1 :
Code: 
[email protected]:~/Android/AOSP$ repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.0_r1
curl: (22) The requested URL returned error: 404 Not Found
Server does not provide clone.bundle; ignoring.
fatal: Couldn't find remote ref refs/heads/android-6.0.0_r1
Unexpected end of command stream
fatal: cannot obtain manifest https://android.googlesource.com/platform/manifest

All is fine when I sync 5.1.1_r24
 
Last edited:
M

Methanoid

Senior Member
Aug 10, 2005
237
16
Cool. Pity you closed your Rom thread as it was a useful way to follow new rom news. Now we have to keep checking all threads to see your name next to a 6.0 Rom....
 
You must log in or register to reply here.

Similar threads

followmsi
[ROM][flo|deb][UNOFFICIAL][LineageOS 20.0]
Replies
4K
Views
917K
S
Spielmops
BeansTown106
  • Locked
[ROM][6.0.1][FLO]★ The Pure Nexus Project ★ Substratum ★ [08/21/16]
Replies
1K
Views
325K
BeansTown106
BeansTown106
DJLamontagneIII
[ROM][AOSP 5.0.1][LRX22C][AOSP Kangs][DJL5.0][Build 12][2014/12/04]
Replies
2K
Views
351K
MatVekk
MatVekk
ripee
[ROM][DISCONTINUED][9] LineageOS 16.0 [deb][flo]
Replies
666
Views
216K
lyushiK
lyushiK
ripee
[ROM][DISCONTINUED][10] LineageOS 17.1 [deb][flo]
Replies
716
Views
188K
B
blaze2051

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 411
    Scott
    Scott
    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!     ​
    Click to expand...
    Click to collapse
    Click to expand...
    Click to collapse
    View
    82
    Scott
    Scott
    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 "[email protected]"
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!
    View
    60
    GROGG88
    GROGG88
    I have decided to bring this project out of the shadows. The builds are now accessible through dedicated device threads:

    hammerhead

    flo

    deb
    View
    52
    Scott
    Scott
    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
    Check out @GROGG88 patches HERE!
    Click to expand...
    Click to collapse
    Click to expand...
    Click to collapse
    View
    27
    Scott
    Scott
    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!
    View

New posts