Hi there! I am new here! So decided to start off with this!
Here's a list of the OpenSource ROMs, with the links to their github repos and the commands used for initializing their respective repos, to the working directories
For syncing the full repo,
After you initialize certain repo in the working folder, you have to give the following command :
Code:
repo sync -jX -c -f
Note : X = no. of threads. If you are not working on certain things in the background, you can add as many threads as the CPU supports.
ROMs with Github links. This will be useful for source builders, as they would find all the Github links are one place!
1. CyanogenMod
Link to Github sources :
Code:
[URL="https://github.com/CyanogenMod"]https://github.com/CyanogenMod[/URL]
Command for initializing the repo in the working folder :
Code:
repo init -u git://github.com/CyanogenMod/android.git -b <branch>
2. OmniROM
Link to github sources :
Code:
[URL="https://github.com/omnirom"]https://github.com/omnirom[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/omnirom/android.git -b android-4.4
3. Carbon ROM
Link to github sources :
Code:
[URL="https://github.com/CarbonDev"]https://github.com/CarbonDev[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/CarbonDev/android.git -b <branch>
4. PAC-man
Link to github sources :
Code:
[URL="https://github.com/PAC-man"]https://github.com/PAC-man[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/PAC-man/pacman.git -b <branch>
5. Paranoid Android
Link to github sources :
Code:
[URL="https://github.com/ParanoidAndroid"]https://github.com/ParanoidAndroid[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u [email protected]:ParanoidAndroid/manifest.git -b <branch>
6. Root Box
Link to github sources :
Code:
[URL="https://github.com/Root-Box"]https://github.com/Root-Box[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/Root-Box/platform_manifest.git -b <branch>
7. AOKP
Link to github sources :
Code:
[URL="https://github.com/AOKP"]https://github.com/AOKP[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b <branch>
8. AOSP
Link to github sources :
Code:
[URL="https://github.com/android"]https://github.com/android[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://android.googlesource.com/platform/manifest.git -b <branch>
9. CyanMobile
Link to github sources :
Code:
[URL="https://github.com/CyanMobile"]https://github.com/CyanMobile[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/CyanMobile/android_cyanmobile.git -b <branch>
10. MiCode
Link to github sources :
Code:
[URL="https://github.com/MiCode"]https://github.com/MiCode[/URL]
Command for initializing the repo in the working folder:
Code:
I couldn't find the manifest git! Some one help me out! :P
11. AOSB
Link to github sources :
Code:
[URL="https://github.com/AOSB"]https://github.com/AOSB[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/AOSB/android.git <branch>
12. Liquid Smooth
Link to github sources :
Code:
[URL="https://github.com/LiquidSmooth"]https://github.com/LiquidSmooth[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/LiquidSmooth/android.git -b <branch>
13. Slim ROMs
Link to github sources :
Code:
[URL="https://github.com/SlimRoms"]https://github.com/SlimRoms[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/SlimRoms/platform_manifest.git -b <branch>
14. CyanFox
Link to github sources :
Code:
[URL="https://github.com/CyanFox"]https://github.com/CyanFox[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/CyanFox/android.git -b <branch>
15. Lewa OS
Link to github sources :
Code:
[URL="https://github.com/LeWaCode"]https://github.com/LeWaCode[/URL]
Command for initializing the repo in the working folder:
Code:
I couldn't find the manifest git! Some one help me out! :P
16. Mokee
Link to github sources :
Code:
[URL="https://github.com/MoKee"]https://github.com/MoKee[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/MoKee/android.git -b <branch>
17. ResurrectionRemix
Link to github sources :
Code:
[URL="https://github.com/resurrectionremix"]https://github.com/resurrectionremix[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b <branch>
I am new here, so I am sure, I might have missed out some ROM. Please care to inform that through posting the Github link in the thread! Thanks
I'm really sorry if I'm posting in the wrong thread, but I'm new to the dev forums so I didn't want to make a whole new thread for this simple question. I'm currrently syncing the CM-11.0 branch from the cyanogenmod github. And most packages are donwloaded correctly, but 4 are making problems. Here's the log of my terminal:
Code:
Fetching projects: 99% (433/437) fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/packages/apps/QuickSearchBox.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/external/safe-iop.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/system/security.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/external/chromium_org/third_party/leveldatabase/src.git'
error: Cannot fetch CyanogenMod/android_packages_apps_QuickSearchBox
warn: --force-broken, continuing to sync
error: Cannot fetch CyanogenMod/android_system_security
warn: --force-broken, continuing to sync
error: Cannot fetch platform/external/chromium_org/third_party/leveldatabase/src
warn: --force-broken, continuing to sync
error: Cannot fetch CyanogenMod/android_external_safe-iop
warn: --force-broken, continuing to sync
I ran the repo sync command with the -f flag as you can see, so it would download everything else execpt the ones it can't. I'm running ubuntu 13.10 x64. Also I should mention that I haven't added any device specific trees yet, only pure CM without kernel, device or vendor repos
Why the -c and -f arguments with repo sync? Doesn't it run fine without them?
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
paxy97 said:
I'm really sorry if I'm posting in the wrong thread, but I'm new to the dev forums so I didn't want to make a whole new thread for this simple question. I'm currrently syncing the CM-11.0 branch from the cyanogenmod github. And most packages are donwloaded correctly, but 4 are making problems. Here's the log of my terminal:
Code:
Fetching projects: 99% (433/437) fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/packages/apps/QuickSearchBox.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/external/safe-iop.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/system/security.git'
fatal: Not a git repository: '/home/pavle/android/system/.repo/projects/external/chromium_org/third_party/leveldatabase/src.git'
error: Cannot fetch CyanogenMod/android_packages_apps_QuickSearchBox
warn: --force-broken, continuing to sync
error: Cannot fetch CyanogenMod/android_system_security
warn: --force-broken, continuing to sync
error: Cannot fetch platform/external/chromium_org/third_party/leveldatabase/src
warn: --force-broken, continuing to sync
error: Cannot fetch CyanogenMod/android_external_safe-iop
warn: --force-broken, continuing to sync
I ran the repo sync command with the -f flag as you can see, so it would download everything else execpt the ones it can't. I'm running ubuntu 13.10 x64. Also I should mention that I haven't added any device specific trees yet, only pure CM without kernel, device or vendor repos
Click to expand...
Click to collapse
Try to sync again.. this time, don't use the -f arguments.
SMillerNL said:
Why the -c and -f arguments with repo sync? Doesn't it run fine without them?
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
Click to expand...
Click to collapse
Ya, It will run without -c and -f arguments. But -f will force the sync. It is good for people who have a slow internet, as the download won't break in between(that doesn't matter much though, but it saves time, if suppose the dev is syncing overnight).
PixCM said:
Try to sync again.. this time, don't use the -f arguments.
Ya, It will run without -c and -f arguments. But -f will force the sync. It is good for people who have a slow internet, as the download won't break in between(that doesn't matter much though, but it saves time, if suppose the dev is syncing overnight).
Click to expand...
Click to collapse
So what will -c do then?
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
SMillerNL said:
So what will -c do then?
Sent from my Nexus 4, want to know my current project? Check http://team-fun.eu
Click to expand...
Click to collapse
-c: command and arguments to execute. The command is evaluated through /bin/sh and any arguments after it are passed through as shell positional parameters.
PixCM said:
Hi there! I am new here! So decided to start off with this!
Here's a list of the OpenSource ROMs, with the links to their github repos and the commands used for initializing their respective repos, to the working directories
For syncing the full repo,
After you initialize certain repo in the working folder, you have to give the following command :
Code:
repo sync -jX -c -f
Note : X = no. of threads. If you are not working on certain things in the background, you can add as many threads as the CPU supports.
ROMs with Github links. This will be useful for source builders, as they would find all the Github links are one place!
1. CyanogenMod
Link to Github sources :
Code:
[URL="https://github.com/CyanogenMod"]https://github.com/CyanogenMod[/URL]
Command for initializing the repo in the working folder :
Code:
repo init -u git://github.com/CyanogenMod/android.git -b <branch>
2. OmniROM
Link to github sources :
Code:
[URL="https://github.com/omnirom"]https://github.com/omnirom[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/omnirom/android.git -b android-4.4
3. Carbon ROM
Link to github sources :
Code:
[URL="https://github.com/CarbonDev"]https://github.com/CarbonDev[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/CarbonDev/android.git -b <branch>
4. PAC-man
Link to github sources :
Code:
[URL="https://github.com/PAC-man"]https://github.com/PAC-man[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/PAC-man/pacman.git -b <branch>
5. Paranoid Android
Link to github sources :
Code:
[URL="https://github.com/ParanoidAndroid"]https://github.com/ParanoidAndroid[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u [email protected]:ParanoidAndroid/manifest.git -b <branch>
6. Root Box
Link to github sources :
Code:
[URL="https://github.com/Root-Box"]https://github.com/Root-Box[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/Root-Box/platform_manifest.git -b <branch>
7. AOKP
Link to github sources :
Code:
[URL="https://github.com/AOKP"]https://github.com/AOKP[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b <branch>
8. AOSP
Link to github sources :
Code:
[URL="https://github.com/android"]https://github.com/android[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://android.googlesource.com/platform/manifest.git -b <branch>
9. CyanMobile
Link to github sources :
Code:
[URL="https://github.com/CyanMobile"]https://github.com/CyanMobile[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/CyanMobile/android_cyanmobile.git -b <branch>
10. MiCode
Link to github sources :
Code:
[URL="https://github.com/MiCode"]https://github.com/MiCode[/URL]
Command for initializing the repo in the working folder:
Code:
I couldn't find the manifest git! Some one help me out! :P
11. AOSB
Link to github sources :
Code:
[URL="https://github.com/AOSB"]https://github.com/AOSB[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/AOSB/android.git <branch>
12. Liquid Smooth
Link to github sources :
Code:
[URL="https://github.com/LiquidSmooth"]https://github.com/LiquidSmooth[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/LiquidSmooth/android.git -b <branch>
13. Slim ROMs
Link to github sources :
Code:
[URL="https://github.com/SlimRoms"]https://github.com/SlimRoms[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/SlimRoms/platform_manifest.git -b <branch>
14. CyanFox
Link to github sources :
Code:
[URL="https://github.com/CyanFox"]https://github.com/CyanFox[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u git://github.com/CyanFox/android.git -b <branch>
15. Lewa OS
Link to github sources :
Code:
[URL="https://github.com/LeWaCode"]https://github.com/LeWaCode[/URL]
Command for initializing the repo in the working folder:
Code:
I couldn't find the manifest git! Some one help me out! :P
16. Mokee
Link to github sources :
Code:
[URL="https://github.com/MoKee"]https://github.com/MoKee[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/MoKee/android.git -b <branch>
17. ResurrectionRemix
Link to github sources :
Code:
[URL="https://github.com/resurrectionremix"]https://github.com/resurrectionremix[/URL]
Command for initializing the repo in the working folder:
Code:
repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b <branch>
I am new here, so I am sure, I might have missed out some ROM. Please care to inform that through posting the Github link in the thread! Thanks
Click to expand...
Click to collapse
The ParanoidAndroid repo is actually
https://github.com/AOSPA for Nexus devices
or
https://github.com/AOSPA-legacy for non-Nexus
I'm getting excited repo sync error... When I do "repo sync" command ...
And when I do a "./build-pac.sh p3100" command..
It gets stuck at lunching device thing... It's unable to download dependencies from cyanogenmod...
I had edited the room_service.xml a while back.. The error started after that... But now I deleted the room service file but the error still fails... Any solutions...?
Thanks for including CyanFox....... ....
Sent from my GT-I9100 using Tapatalk
zeetherocker said:
I'm getting excited repo sync error... When I do "repo sync" command ...
And when I do a "./build-pac.sh p3100" command..
It gets stuck at lunching device thing... It's unable to download dependencies from cyanogenmod...
I had edited the room_service.xml a while back.. The error started after that... But now I deleted the room service file but the error still fails... Any solutions...?
Click to expand...
Click to collapse
Hmm, The lunch process doesn't use the room service. It uses the dependencies of the ROM and syncs, whats there in the dependencies file!
Check dependencies for errors, or manually put the files in place. The vendor in /vendor/manufacturer/device, the device tree in /device/manufacturer/device and kernel in /kernel/manufacturer/device (check in the boardconfig.mk, for exact location of kernel source).
I suppose that its a exiting repo error and not a exciting repo sync error . for that, use the flag "-f" , for example. repo sync -f
Check if this works :highfive:
PixCM said:
Hmm, The lunch process doesn't use the room service. It uses the dependencies of the ROM and syncs, whats there in the dependencies file!
Check dependencies for errors, or manually put the files in place. The vendor in /vendor/manufacturer/device, the device tree in /device/manufacturer/device and kernel in /kernel/manufacturer/device (check in the boardconfig.mk, for exact location of kernel source).
I suppose that its a exiting repo error and not a exciting repo sync error . for that, use the flag "-f" , for example. repo sync -f
Check if this works :highfive:
Click to expand...
Click to collapse
I'm sure it's excited repo sync error... I'll post a Screenshot later... For now I've deleted a few folders... I'll try syncing repos again in the morning... And I'll do whatever u said and report back if I get errors..
Replicant OS
Nice list, I did not know there where so many, here is another one at http://www.replicant.us/
@PixCM Nice thread
maybe add VanirAOSP
https://github.com/VanirAOSP/platform_manifest
add Hellkat
https://github.com/Hellybean/android
add BeanStalk
https://github.com/scotthartbti/android
Cheers
MiCode builds funny.
sync command:
repo init -u git://github.com/MiCode/patchrom.git -b jellybean42
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
and Dirty Unicorn
https://github.com/DirtyUnicorns-KitKat
sync:
repo init -u https://github.com/DirtyUnicorns-KitKat/manifest.git -b du44
Here you go, this should about cover it
https://github.com/LowEndGeek/General_Android_Documents/blob/master/CustomRoms.md
more...
broodROM
https://github.com/broodROM/platform_manifest
AOSP-S4 4.4.2 KitKat
https://github.com/AOSP-S4-KK/platform_manifest
ValidusAOSP
https://github.com/ValidusAOSP/platform_manifest
MWisBest
https://github.com/MWisBest/android_manifest
AnimeROM
https://github.com/AnimeROM/android
TheSchismROM
https://github.com/TheSchismROM/platform_manifest
Mahdi-Rom
https://github.com/Mahdi-Rom/platform_manifest
and one more guys
https://github.com/PureKat/android
Www.github.com/SOKP/platform_manifest
Sent from my GT-I9500 using XDA Premium 4 mobile app
another one=AICP rom
Android Ice Cold Project
https://github.com/AICP/platform_manifest
repo init -u https://github.com/AICP/platform_manifest.git -b kitkat
if someone got some new rom link to add... please do!
one more
will test it soon... today if iam lucky...
https://github.com/CyanHacker/android
repo init -u git://github.com/CyanHacker/android.git -b kitkat
Related
Hi guys, I'm following a guide in the RC Forums regarding compiling cm7. I am on the setting up repo part and have made a directory for compiling, however, when I try to
Code:
$ repo init -u git://github.com/CyanogenMod/android.git
I get
IOError: [Errno 2] No such file or directory: '/home/aquethys/CyanogenCompiling/.repo/manifests/.git/HEAD'
Terminal also skipped over some files earlier in the guide when setting up, could that also be the problem?
Thanks in advance!
Aquethys said:
Hi guys, I'm following a guide in the RC Forums regarding compiling cm7. I am on the setting up repo part and have made a directory for compiling, however, when I try to
Code:
$ repo init -u git://github.com/CyanogenMod/android.git
I get
IOError: [Errno 2] No such file or directory: '/home/aquethys/CyanogenCompiling/.repo/manifests/.git/HEAD'
Terminal also skipped over some files earlier in the guide when setting up, could that also be the problem?
Thanks in advance!
Click to expand...
Click to collapse
That will download the entire tree including all versions of Android. If you are looking to compile I suggest you add '-b gingerbread' so your line would look like:
Code:
$ repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
AOSPA+ Building from sources
Pre reuirments :
A 64 bit PC
Some knowlegde About Git
A brain
This is unofficial. This thread is intended for devs & advanced users only.
For the first time you try to build AOSPA
Follow this guide up to "Initialize the CyanogenMod source repository" step (don't execute this step).
http://wiki.cyanogenmod.org/w/Build_for_smultron
Download & compile lz4 compression tool
Code:
sudo apt-get install subversion
cd ~/Downloads
svn checkout -r 91 http://lz4.googlecode.com/svn/trunk/ lz4
cd lz4 && make && cp lz4demo ~/bin/lz4demo
Initialize the AOSPA source repository
Enter the following to initialize the repository:
Code:
cd ~/android/system/
repo init -u git://github.com/ParanoidAndroid/manifest.git -b jb43-legacy
Get the required local manifest
Code:
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.2/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
Download the source code
Code:
repo sync
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.2/updates.sh > ~/android/system/updates.sh
chmod a+x updates.sh
./updates.sh
Get the prebuilts
Code:
cd ~/android/system/vendor/cm
./get-prebuilts
Setup the environment & prepare the device-specific code.
Code:
cd ~/android/system
. build/envsetup.sh
breakfast smultron
Build the ROM (takes long time)
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-10.2-DATE-UNOFFICIAL-smultron.zip
The next times you want to build, you only need to do the following:
Sync the repositories & make sure you are using the latest local_manifest.
Code:
cd ~/android/system/
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.2/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
repo sync
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
curl https://raw.github.com/LegacyXperia/local_manifests/cm-10.2/updates.sh > ~/android/system/updates.sh
chmod a+x updates.sh
./updates.sh
Setup the environment
Code:
. build/envsetup.sh
Build the ROM
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/PA-3.9-DATE-UNOFFICIAL-smultron.zip
Steps to build only the kernel:
Sync the repositories.
Code:
cd ~/android/system/
repo sync
Setup the environment
Code:
. build/envsetup.sh
Build the kernel
Code:
breakfast smultron
make -j4 bootimage
If the build finishes successfully, you will find the boot image here:
~/android/system/out/target/product/smultron/boot.img
Credits: Thanks to hnl_dk , mikeioannia for the initial CM9 & CM10 , 10.1 , 10.2 guides.
And you built successfully with that method? Because as far as I know it's impossible... You didn't define anything about the device in the vendor/pa folders so it can't even find your device while trying to ./rom-build.sh
Sent from my Nexus 4 running Android 4.2.2
As reported by mihahn this thread seems a blatant copy of another guide without any actual research. I've maintained AOSPA for several devices for some time and see at least 2 mistakes when quickly scanning through it.
Thread closed for now, if it's solved I'll reopen, otherwise it will be deleted.
Lets assume we've fetched an android source tree
Code:
repo init -u $url && repo sync
.. committed some local changes and saved a snapshot
Code:
repo manifest -o ~/snapshot.xml -r
Will another 'repo sync' wipe the snapshot references from our tree or can we still revert to that snapshot later on?
Where to find reference to the snapshot in the local tree?
While Bryan Hundven shows us how to mirror all of CM source code locally to your machine, I want to do the same for a specific branch, e.g. cm-12.0. Disconnecting myself from Internet, I tried the following without any success,
Code:
cd /mnt/Mirror
mkdir CM12.0_Mirror
cd CM12.0_Mirror
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.0 --mirror
repo sync -j 4
cd ..
mkdir CM12.0_Work
cd CM12.0_Work
repo init file:///mnt/Mirror/CM12.0_Mirror -b cm-12.0
The error message I received is the following:
fatal: '/mnt/Mirror/CM12.0_Mirror/manifest.xml' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Click to expand...
Click to collapse
Instead of the last command, if I issue the following
Code:
repo init -u git://github.com/CyanogenMod/android.git --reference -b cm-12.0
The error message I received is the following:
fatal: unable to connect to github.com:
github.com: Name or service not known
Click to expand...
Click to collapse
If you want to help, please check out the newest posts.
Original post:
I have been trying to download the AOSP sources for the last few days but I can not seem to make it work at all, it downloads a little bit of stuff then fails after waiting for a long period of time.
Things I have tried:
Code:
repo init -u https://android.googlesource.com/platform/manifest
Code:
repo init -u https://android.googlesource.com/platform/manifest --no-clone-bundle
Code:
repo init -u https://android.googlesource.com/a/platform/manifest
Code:
repo init -u https://android.googlesource.com/a/platform/manifest --no-clone-bundle
Code:
sudo sysctl -w net.ipv4.tcp_window_scaling=0
repo init -u https://android.googlesource.com/platform/manifest
Code:
sudo sysctl -w net.ipv4.tcp_window_scaling=0
repo init -u https://android.googlesource.com/platform/manifest --no-clone-bundle
I have no idea what I am doing wrong. I am using the latest repo with the shebang changed from python to python2.7.
gudenau said:
I have been trying to download the AOSP sources for the last few days but I can not seem to make it work at all, it downloads a little bit of stuff then fails after waiting for a long period of time.
Things I have tried:
Code:
repo init -u https://android.googlesource.com/platform/manifest
Code:
repo init -u https://android.googlesource.com/platform/manifest --no-clone-bundle
Code:
repo init -u https://android.googlesource.com/a/platform/manifest
Code:
repo init -u https://android.googlesource.com/a/platform/manifest --no-clone-bundle
Code:
sudo sysctl -w net.ipv4.tcp_window_scaling=0
repo init -u https://android.googlesource.com/platform/manifest
Code:
sudo sysctl -w net.ipv4.tcp_window_scaling=0
repo init -u https://android.googlesource.com/platform/manifest --no-clone-bundle
I have no idea what I am doing wrong. I am using the latest repo with the shebang changed from python to python2.7.
Click to expand...
Click to collapse
Just attempted to pull AOSP again, same issues.
Edit:
I just tired it again in a Debian virtual machine and it worked.
What about arch is killing repo?
Edit 2:
I figured it out thanks to progandy, Google servers seem to have a bugged HTTP 2 implementation.
I'm now having an issue when trying to build AOSP, aparently clang can't find ncurses.
Code:
prebuilts/clang/host/linux-x86/clang-3289846/bin/clang.real: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory
When it exists in multiple locations:
Code:
$ find | grep -F libncurses.so.5
./prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.17-4.8/sysroot/usr/lib32/libncurses.so.5.9
./prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.17-4.8/sysroot/usr/lib32/libncurses.so.5
./prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.17-4.8/sysroot/usr/lib/libncurses.so.5.9
./prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.17-4.8/sysroot/usr/lib/libncurses.so.5