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

Status
Not open for further replies.
Search This thread
By:
Advanced…
Matt07211

Matt07211

Senior Member
Jan 10, 2015
642
291
Sudarshankakoty said:
Hey.. When I compile a recovery.img (CWM) using source CM codes, I also get a boot.img and ramdisk.img file in my output folder. Why ? Any use of them ? Are they modified to run new CWM ?
Is that the only reason when flashing the CWM recovery alone is not booting the CWM in my device? Do I need to flash that new boot.img too ?
Click to expand...
Click to collapse
First off I'd recommend using TWRP. CWM has been abandoned for a while now, tool have better support overall (both in device and building as you can as questions).

Recovery is well recovery. Boot.img is the defult used when booting normally. The ramdisk can be found inside both the recovery and boot.img and I'm guessing that the process you are doing creates the ramdisk seprate for your convenience (So don't flash it or anything its for the use inside a boot.img or recovery.img)
 
Sudarshankakoty

Sudarshankakoty

Senior Member
May 3, 2016
236
28
Matt07211 said:
First off I'd recommend using TWRP. CWM has been abandoned for a while now, tool have better support overall (both in device and building as you can as questions).

Recovery is well recovery. Boot.img is the defult used when booting normally. The ramdisk can be found inside both the recovery and boot.img and I'm guessing that the process you are doing creates the ramdisk seprate for your convenience (So don't flash it or anything its for the use inside a boot.img or recovery.img)
Click to expand...
Click to collapse

Well. Got it. But any idea what it means ? Jack Server Error ?
No Problems with compiling CWM recovery
 
Sudarshankakoty

Sudarshankakoty

Senior Member
May 3, 2016
236
28
Matt07211 said:
Not sure never compiled a ROM before, but it looks like it gets to use Jack.jar but is unable to find it. I suggest Google it and see if you can locate the file.
Click to expand...
Click to collapse

I killed and disabled the whole jack server ...
Btw are you a CM user ?
lol. I talked to Micromax Support Team today and they said they will inform their developers about releasing kernel sources... lol. Don't know what they gonna do ... :cowboy:
 
Matt07211

Matt07211

Senior Member
Jan 10, 2015
642
291
Sudarshankakoty said:
I killed and disabled the whole jack server ...
Btw are you a CM user ?
lol. I talked to Micromax Support Team today and they said they will inform their developers about releasing kernel sources... lol. Don't know what they gonna do ... :cowboy:
Click to expand...
Click to collapse
I used CM for a little while on my old phone. My current phone doesn't have any custom ROMS.

Doubt they will release sources though.
 
  • Like
Reactions: Sudarshankakoty
A

aadityarulez

Senior Member
Jun 5, 2013
305
72
Consider this. If I have sources for a rom, say RR, and I have 2 different devices and 2 local_manifest files for proprietary files for the devices. So, how do I build for a specific device? Thanks.
 
M

mihran_thalhath

Senior Member
Feb 16, 2015
776
1,591
Ih24n said:
@regalstreak I have some source Here maybe usefull... :) ..

https://www.androidfilehost.com/?w=files&flid=123192
Click to expand...
Click to collapse

While extracting the RR Nougat source you uploaded, an error is encountered. It starts to extract, but after some time it's showing

xz: (stdin): Compressed data is corrupt
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Click to expand...
Click to collapse

It took me more than 2 days to download the file with the crappy internet connection in my place. Should I download the file again?
 
Infinity

Infinity

Account currently disabled
Dec 23, 2015
385
158
GB
meettomy.site
out386 said:
Torrents won't help. You can't download at all once all the seeds goes off. And not many will seed ROMs.
Click to expand...
Click to collapse
Yes this is a drawback

---------- Post added at 06:35 AM ---------- Previous post was at 06:35 AM ----------
kvsjxd said:
Nobody will seed because the post is for people looking for smaller sized sources and most people who download these compressed sources have less bandwidth to spare
Click to expand...
Click to collapse
Yes
 
Status
Not open for further replies.

Similar threads

M
[GAPPS][DAILY] Open GApps for Android; All Android Versions & Devices
Replies
7K
Views
2M
landry314
landry314
A.R.I.S.E. Sound Systems
ARISE Sound Systems™ - Auditory Research in Sound Enhancement
Replies
34K
Views
4M
nericollin
nericollin
Chainfire
[Android 2.1+][03.10.2011][v3.2] Chainfire3D [ROOT][OpenGL ES 2.0+]
Replies
3K
Views
3M
rignfool
rignfool
N
[APP][ROOT] LMT Launcher v3.2
Replies
15K
Views
5M
H
hugozo
capslock66
[Tool][Windows Only][Root] Android Reverse Tethering 3.19
Replies
2K
Views
2M
lenigma1too
lenigma1too

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 125
    regalstreak
    regalstreak
    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.
    Click to expand...
    Click to collapse
    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:

    View
    65
    regalstreak
    regalstreak
    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.
    View
    59
    regalstreak
    regalstreak
    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!
    View
    52
    regalstreak
    regalstreak
    Reserved

    Reserved for stuff.
    View
    36
    MSF Jarvis
    MSF Jarvis
    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.
    View

New posts