• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[SOURCES] [DevXchange] Android Sources Highly Compressed & Developer Exchange

Status
Not open for further replies.
Search This thread

Parthib

Senior Member
Aug 27, 2016
164
63
Then you really shouldn't be building ROMs
Why bro ?
I already compiled some roms(cm11,12) using highly compressed sources of this thread.
But I don't know how to request a new source.
And I am not doing this pull request because if something goes wrong while doing that or I missed up someting then everyone will get angry on me.


Sent from my Primo NF2 using Tapatalk
 

ABSathe

Senior Member
Aug 4, 2016
437
458
Pune
Why bro ?
I already compiled some roms(cm11,12) using highly compressed sources of this thread.
But I don't know how to request a new source.
And I am not doing this pull request because if something goes wrong while doing that or I missed up someting then everyone will get angry on me.
If pull request is wrong .. owner of repo will simply close it without merging ... There's no harm in trying .
 

Druboo666

Senior Member
Sep 15, 2013
337
435
Dhaka
PR has been sent 4 days ago be me for DU (Caf & AOSP) Ground Zero ROMs (validus,tesla,&tipsy) also for OCTOS but none of them are merged.
may i know why ...or did i do something wrong should i need fix anything to get them merged or i simply wait it out
 

regalstreak

Senior Member
Jun 26, 2013
1,262
4,498
Mumbai
PR has been sent 4 days ago be me for DU (Caf & AOSP) Ground Zero ROMs (validus,tesla,&tipsy) also for OCTOS but none of them are merged.
may i know why ...or did i do something wrong should i need fix anything to get them merged or i simply wait it out

Man you sent pull request for 6 roms. Are you going to build all in one click? Do you really need 6 roms? You commit messages say "Added <rom>".
Why would I waste bandwidth on my server and do 6 roms just for the sake of "adding"?
Just submit pr s for the ones you are actually going to compile.
 

Druboo666

Senior Member
Sep 15, 2013
337
435
Dhaka
Man you sent pull request for 6 roms. Are you going to build all in one click? Do you really need 6 roms? You commit messages say "Added <rom>".
Why would I waste bandwidth on my server and do 6 roms just for the sake of "adding"?
Just submit pr s for the ones you are actually going to compile.

I actually compile GZR and OctOS ? ? ?
And for DU you already had previous PR which you closed with a resend request so i just send the PR....
 
Last edited:

ABSathe

Senior Member
Aug 4, 2016
437
458
Pune
FAQ
Q6> How do I use these sources?
Ans: First, you will have to extract them as mentioned above. You should get a .repo folder. In the same folder itself (not inside .repo but the folder that contains .repo), you will have to update the local work tree. You can update it by using This command will help you to use minimum data/internet as it does not download extra tags or clone bundles.
If you do not want to use data at all, you can use this: This will not fetch anything from the internet. Happy compiling!

Please press the "Thanks Button" if we helped you and quote us if you have a problem!
Any idea how much internet will be used ? Or any way to monitor it ?
 

regalstreak

Senior Member
Jun 26, 2013
1,262
4,498
Mumbai
I have one doubt.
If i am using shallow source and if i do "repo sync" to update recent changes, will it download complete data(means previous commits also) or just recent changes?

As it had been initialised as shallow, it won't sync full. It will remain shallow. If you want to unshallow a specific repo, you can cd to that, for example,
Code:
$(croot) && cd external/wpa_supplicant_8
and do this:
Code:
git pull --unshallow
This will unshallow the specific project.

after syncing local only as mentioned in faq can i sync the same with internet, which command should i use to sync it with minimum internet?
Of course you can sync the same with internet. The command is the same, just remove the 'l' flag.
 

himavanth.reddy925

Senior Member
Oct 7, 2014
68
17
getting error while decompressing

im getting error while decompressing the source of XenonHD sources.. combined the XenonHD-n-shallow-20170629.tar.xz.aa XenonHD-n-shallow-20170629.tar.xz.ab XenonHD-n-shallow-20170629.tar.xz.ac
 

messi2050

Senior Member
Nov 1, 2012
2,299
3,278
As it had been initialised as shallow, it won't sync full. It will remain shallow. If you want to unshallow a specific repo, you can cd to that, for example,
Code:
$(croot) && cd external/wpa_supplicant_8
and do this:
Code:
git pull --unshallow
This will unshallow the specific project.


Of course you can sync the same with internet. The command is the same, just remove the 'l' flag.
please can you upload lineage 14
Edit: pull request done
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 125
    qr98avA.png

    Ss8GksS.png

    Project abandoned, please do not submit pull requests.

    Disclaimer: The wordings in the thread are meant to be noob-friendly and for newer developers that have just dipped their feet into Android platform development. Hence, they won't be accurate in many places for the 'geek'. Also, we had started distributing shallow cloned sources with a depth of '1' instead of non-repo sources (as they are more or less of the same size). So this should not be a problem for the ROM developers in our opinion as they can be fetched by syncing.

    Hello!
    We, Android Developers, have many problems. One such of them is "SLOW INTERNET" or even "LOW BANDWIDTH".
    Due to these problems, we are unable to sync the BIG chunk of Android source codes from the respective repositories.
    Hence, most of the new and learning developers just fail at the first step: Downloading The Source Code!
    So, here I present you with a thread, which contains links to download "HIGHLY COMPRESSED", untouched (unmodified) and full Android source codes of many different ROMs!
    The links to the highly compressed source codes you will find here are not uploaded by me alone. There are many other people that have contributed.
    Some of them are: @DigiGoon @MSF Jarvis and @regalstreak (me)

    jPIwEta.png

    So, Let's begin!
    First things first.
    You should know what a repo is.
    I quote XDA:

    What is Repo?
    Repo is a repository management tool built on top of Git.

    It’s first purpose is to downloads files from multiple git repositories into your local working directory (aka the source tree). That means that you won’t have to manually download or fetch the latest changes from about 300+ projects (depending on if you are downloading AOSP, CM or AOKP for example), repo will do it for you.

    The second purpose of repo is to made it easy to submit your code contributions for review to a Gerrit server.
    When you download a source code with repo, you get a folder named .repo in your working directory. It contains all the compressed .git format files that need to be in the source code.
    After the source has been downloaded, the repo tool decompresses the files from the ".repo" folder and you get the source code in the working directory itself!
    This project will give you a highly compressed shallow cloned and full tarball of the sources (for those who can't download it via repo or have limited speeds on github/aosp servers). More information is given in the FAQ section. It is must-read. Without it, you won't understand how to use these.

    Note: You cannot go from CM12 source to CM12.1 or going CM12 to CM13 as these are different branches on the CyanogenMod repo. No way doing that. You will have to manually download the new source.

    t86aGPB.png

    So, We are done with the information!
    Now, The interesting part. The sources!

    Note: All links on this thread are tap friendly! They open in new tabs :)

    I have divided this into several sections for ease of reading and getting the sources. They are:

    65
    As you know that we have been using the Skadoosh script recently, which is made by me (@regalstreak), @MSF Jarvis and @DigiGoon, all our sources are being uploaded to one common folder on AndroidFileHost.
    This is an automated process in which you submit a Pull Request on the Skadoosh's git and the required source will be available to you soon after it.
    More information regarding the process is on Post 3 by @MSF Jarvis
    The link to the folder where all the sources are uploaded is Here.
    The old upload afh folder can be found Here
    If you have any other issues regarding the sources, please mention us here. We will be happy to help you. Please read the FAQ before doing stuff.
    59
    FAQ

    Q1> How should I extract the source?
    Ans:

    First you will have to join the archive parts into one big archive. Download all the parts. Then put all parts in one folder. Verify md5sum by
    Code:
    md5sum -c *.md5sum
    Then do
    Code:
    cat *.tar.* > yourbigarchivename.tar.xz
    Just quote me if you don't understand this. I'll help you out.

    If your archive is in .tar.xz format, do this:
    • Open Terminal
    • Now cd to the drive where you have downloaded the sources
    • Extract it
      Code:
      tar -xvJf (file name here).tar.xz

    If your archive is in .tar.gz format, so do this:
    • Open Terminal
    • Now cd to the drive where you have downloaded the sources
    • Extract it
      Code:
      tar -xvzf (file name here).tar.gz

    Now you have extracted the source.

    Q2> I am not able to extract the source. What should I do?
    Ans: You cannot extract source with GUI on the Archive Extractor. So, try the method I mentioned.

    Q3> Is the size of all files 2GB? I saw the size 2GB on AndroidFileHost!
    Ans: The mentioned size on AFH is incorrect. AndroidFileHost has some problems while showing file sizes for files above 2GB. You need to click on Download once to view the correct size!

    Q4> How do you compress them? I mean, I need the command so that I can help you out!
    Ans: Our script is open source. You can view it here: https://github.com/regalstreak/skadoosh

    Q5> What are shallow and full sources?
    Ans: Shallow sources are the ones that just have the latest or the HEAD commits in each subproject. You can read more about it from here. Full are the ones that have all the bits from the starting of the subprojects and hence the archives have a large file size.

    Q6> How do I use these sources?
    Ans: First, you will have to extract them as mentioned above. You should get a .repo folder. In the same folder itself (not inside .repo but the folder that contains .repo), you will have to update the local work tree. You can update it by using
    Code:
    repo sync -c -f --force-sync --no-clone-bundle --no-tags -j8
    This command will help you to use minimum data/internet as it does not download extra tags or clone bundles.
    If you do not want to use data at all, you can use this:
    Code:
    repo sync -c -f --force-sync --no-clone-bundle --no-tags -j8 --local-only
    This will not fetch anything from the internet. Happy compiling!

    Please press the "Thanks Button" if we helped you and quote us if you have a problem!
    52
    Reserved

    Reserved for stuff.
    36
    Originally, we have had a "Ask on the thread, we'll try" approach to how things work. This is changing now.
    While this worked good enough for those asking for the sources, the people who did the actual work were overburdened. Frankly, the process was pretty sketchy. I personally faced the burden part when there were about 6 or 7 ROMs to do! I actually forgot about one guy who made the request earliest, which kinda sucked.
    Going forward, this won't happen now. We have a script up on @regalstreak's Github. Updates to it are synced to my server and executed.

    url]

    The process for requesting sources is now something like this :
    • Go to the Github repo and edit the compress.bash script
    • Start a Pull Request
    • Wait for it to be merged
    • Wait for even more time to let it upload and one of us to send the confirmation here.
    • Do whatever the heck you want with those sources!

    url]

    NOTE: The compress.bash looks like this in a classic example of how to do it WRONG.
    Code:
    name=AOSP
    manifest=[url]https://android.googlesource.com/platform/manifest[/url] -b android-4.0.1_r1
    branch=android-6.0.1_r55
    
    ./skadoo.sh $name $manifest $branch

    This was after This PR was merged and is being shown as the perfect way to mess it up. You are ALREADY passing the branch parameter separately, so adding '-b android-4.0.1_r1' looks like a shining example of blind copy paste. Don't do that. Change the name, manifest and branch with some general application of the faculty of common sense.

    Interested users are also suggested to read this strongly worded post.