Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to the tutorial for build CyanogenMod 10 for the HTC ChaCha. This tutorial was a community based project from HTC ChaCha’s Google+. We created this tutorial to try and boost the development of the HTC ChaCha board and bring some life back to the board.
Requirements:
Linux System x64 (Ubuntu 12.04 and newer can be used)
Mac OS X can also be used, however this tutorial is designed for Linux users.
Python 2.6 -- 2.7, which you can download from python.org or with sudo apt-get install python on Ubuntu or Debian.
GNU Make 3.81 -- 3.82, which you can download from gnu.org or with sudo apt-get install make on Ubuntu or Debian.
JDK 6 (Can be found at Ubuntu Software Centre or read details in Build Environment for detailed instructions)
Git 1.7 or newer. You can find it at git-scm.com or with sudo apt-get install git-core on Ubuntu or Debian.
Good amount of RAM, less you have longer it will take to build. I recommend a 2GB and higher.
A decent ISP which provides a fast, reliable connection(so you don't timeout during a large pull of source)
Setting up a Build Environment
Follow this guide: http://source.android.com/source/initializing.html
Installing Repo
Repo is a tool that makes it easier to work with Git and Gerrit in the context of Android. To learn more about Repo and Gerrit, see Version Control.
To install, initialize, and configure Repo, follow these steps:
Make sure you have a bin/ directory in your home directory, and that it is included in your path:
Code:
$ mkdir ~/bin
$ export PATH=${PATH}:~/bin
Alternatively, experienced Linux users may wish to add PATH=${PATH}:~/bin to ~/.bashrc to avoid re-typing the export command.
Download the Repo script and ensure it is executable:
Code:
$ curl [url]https://dl-ssl.google.com/dl/googlesource/git-repo/repo[/url] > ~/bin/repo
$ chmod a+x ~/bin/repo
Initializing a Repo client
After installing Repo, set up your client to access the android source repository
Create an empty directory to hold your working files, please note that Linux’s files system is case-sensitive so uppercase letters matter. Give it any name you like, we’ve used WORKING_DIRECTORY for a quick example:
Code:
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
Run repo init to bring down the latest version of Repo with all of its most recent bug fixes. You must specify a URL for the manifest, which specifies where the various repositories included in the Android source will be placed within your working directory and where to download them from. The manifest will update automatically when minor versions of Android are released (4.1.x) but not when major versions are (4.X). A major version can only be changed by selecting the new branch codename with the -b flag bellow.
Code:
$ repo init -u git://github.com/CyanogenMod/android.git -b jellybean
When prompted, please configure Repo with your real name and email address. To download AOSP material, you will need an email address that is connected with a registered Google account. Make sure this is a live address at which you can receive messages as the name that you provide here will show up in attributions for your code submissions. You won’t get any messages if you don’t submit any code.
A successful initialization will end with a message stating that Repo is initialized in your working directory. Your client directory should now contain a .repo directory where files such as the manifest will be kept.
Getting the files
To pull down files to your working directory from the repositories as specified in the default manifest, run
Code:
$ repo sync -j8 WORKING_DIRECTORY
Note: The “-j8” is dependent on your internet connection. If you have a slower and fragile then use a lower number like “j2” for example.
The Android source files will be located in your working directory under their project names. The initial sync operation will take an hour or more to complete. For more about repo sync and other Repo commands, see Version Control.
The repo sync operation will take a lot of time (JB source are about 14 GB!). Make sure no other people will be using your system and then pull the source, recommend pulling during the night. However if your source does get interrupted then you can continue the source pulling by running the command again, however this is not recommended.
Using authentication
By default, access to the Android source code is anonymous. To protect the servers against excessive usage, each IP address is associated with a quota.
When sharing an IP address with other users (e.g. when accessing the source repositories from beyond a NAT firewall), the quotas can trigger even for regular usage patterns (e.g. if many users sync new clients from the same IP address within a short period).
In that case, it is possible to use authenticated access, which then uses a separate quota for each user, regardless of the IP address.
The first step is to create a password from the password generator and to save it in ~/.netrc according to the instructions on that page.
The second step is to force authenticated access, by using the following manifest URI:
Code:
[url]https://android.googlesource.com/a/platform/manifest[/url]
Notice how the /a/ directory prefix triggers mandatory authentication.
You can convert an existing client to use mandatory authentication with the following command:
Code:
$ repo init -u [url]https://android.googlesource.com/a/platform/manifest[/url]
To build for the HTC ChaCha you will need to include the specific repository’s for the device. This includes the device files, vendor files and other important repos which are needed:
Device Tree: https://github.com/adumont/android_device_htc_chacha
Vendor Tree: https://github.com/adumont/android_vendor_htc_chacha
Kernel sources: https://github.com/adumont/htc-kernel-msm7227
Click to expand...
Click to collapse
Note: The maintainer of the source is adlx, feel free to fork the projects (if you need to modify them), but if you fix bugs, please submit a pull request (via Github). To clone the project locally on your hard-drive and modify locally you don’t need to either register at Github nor fork the repos.
Open a terminal (Ctrl+Alt+T) and run the following lines:
Code:
$ cd WORKING_DIRECTORY
$ wget -O .repo/local_manifest.xml
[url]https://github.com/adumont/android_device_htc_chacha/blob/jellybean/extra/local_manifest.xml[/url]
$ repo sync -j8 -c
This will download the needed additional repositories to build Jellybean (CM10) for the HTC ChaCha.
Once you're all set up we can start building. If you're not already in the Terminal, open it up again and navigate to your working directory. Run these following commands to start compiling!
Code:
$ . build/envsetup.sh
$ lunch cm_chacha-eng
$ mka bacon
Note: Where “x” is, number how many jobs you want the compile to complete in a second. Remember that this is dependent on your machine. If you have a low spec computer use “-j1” for example.
This last sentence will initiate the build process, which can take several hours depending of your hardware configuration. Once complete the build system will display where the flashable item is stored. Commonly the file can be found below.
Code:
$ cd out/target/product/chacha/
$ ls *.zip
Troubleshooting network issues
When downloading from behind a proxy (which is common in some corporate environments), it might be necessary to explicitly specify the proxy that is then used by repo:
Code:
$ export HTTP_PROXY=http://<proxy_user_id>:<proxy_password>@<proxy_server>:<proxy_port>
$ export HTTPS_PROXY=http://<proxy_user_id>:<proxy_password>@<proxy_server>:<proxy_port>
NOTE: Rarely, Linux clients experience connectivity issues, getting stuck in the middle of downloads (typically during "Receiving objects"). It has been reported that tweaking the settings of the TCP/IP stack and using non-parallel commands can improve the situation. You need root access to modify the TCP setting:
Code:
$ sudo sysctl -w net.ipv4.tcp_window_scaling=0
$ repo sync -j1
E: Your download during the source pulling stopped or it got interrupted. What’s should I do?
A: Use the same command “repo sync” and your download will be resumed. However the will be a small chance of corruption depending on your situation.
E: make: *** No rule to make target `#######', needed by `out/target/product/chacha/obj/SHARED_LIBRARIES/######'. Stop.
make: *** Waiting for unfinished jobs....
A: Usually this occurs when you have an incorrect file or a corrupted file (which can’t be found) which ChaCha device folder is requesting. Use CyanogenMod’s Github to find the correct file or find it using Google.
Question and Answers
What if I don’t want to build CyanogenMod?
You don’t have to. It is possible to build AOKP, Paranoid Android and so on for the HTC ChaCha. Apart from you need to work through the issues and errors. How to build AOKP will be added to this tutorial soon.
My build has some issues!
Report your issue on this thread and someone may help you. If your not receiving support then use Google or the fancy search bar in XDA.
I’ve got a successful build, what shall I do now?
Congratulations. Post your build on this thread or post to the ChaCha Google+ Community and we can test your ROM out. If you feel like you want some more advance work then continue forward to build AOKP, Paranoid Android and so on. The ChaCha community is needing ROMs you can help!
This project was set-up by the HTC ChaCha community on Google+. This was an open document which members of the community contributed to. All known people who have added to the document is listed below.
Google’s Android Open Source Project (Based of documentation)
Adlx (Created main instructions)
LucasArran (Editor)
Benjamin Gwynn (Proff-read and helped)
And all other members from the ChaCha Community!
Need support?-
If your not receiving a response to your error after a couple of days try posting your issues and errors on the HTC ChaCha Community for quick help.
Donation Note
Please do not donate because of this guide. It's a community made project.
Amazing! Thanks for making this available!
i downloaded the CM10 source but when downloading the device files, the system displays the error in manifest file, wget manifest is successful but repo gives me the below error. can you help
warning: local_manifest.xml is deprecated; put local manifests in `/home/user/WORKING_DIRECTORY/.repo/local_manifests` instead
warning: local_manifest.xml is deprecated; put local manifests in `/home/user/WORKING_DIRECTORY/.repo/local_manifests` instead
fatal: error parsing manifest /home/user/WORKING_DIRECTORY/.repo/local_manifest.xml: not well-formed (invalid token): line 37, column 34
Re: [NEW][GUIDE] How to build for HTC ChaCha!
ajeevlal said:
i downloaded the CM10 source but when downloading the device files, the system displays the error in manifest file, wget manifest is successful but repo gives me the below error. can you help
warning: local_manifest.xml is deprecated; put local manifests in `/home/user/WORKING_DIRECTORY/.repo/local_manifests` instead
warning: local_manifest.xml is deprecated; put local manifests in `/home/user/WORKING_DIRECTORY/.repo/local_manifests` instead
fatal: error parsing manifest /home/user/WORKING_DIRECTORY/.repo/local_manifest.xml: not well-formed (invalid token): line 37, column 34
Click to expand...
Click to collapse
You can ignore the warnings. Regarding the error, can you paste here the line 37?
Sent from my Galaxy Nexus
adlx.xda said:
You can ignore the warnings. Regarding the error, can you paste here the line 37?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
attached is the the local manifest file and here is line 37
<link data-pjax-transient rel='permalink' href='/adumont/android_device_htc_chacha/blob/5844aa97eb21e35b63cf9f13b48cf2a1ba40969b/extra/local_manifest.xml'>
ajeevlal said:
attached is the the local manifest file and here is line 37
<link data-pjax-transient rel='permalink' href='/adumont/android_device_htc_chacha/blob/5844aa97eb21e35b63cf9f13b48cf2a1ba40969b/extra/local_manifest.xml'>
Click to expand...
Click to collapse
ok, my mistake. The correct manifest url is https://raw.github.com/adumont/android_device_htc_chacha/jellybean/extra/local_manifest.xml .
With the new manifest, it made some progress but not sure if this is okay.
warning: local_manifest.xml is deprecated; put local manifests in `/home/ajai/WORKING_DIRECTORY/.repo/local_manifests` instead
Fetching projects: 0% (1/326) fatal: remote error:
CyanogenMod/[email protected]:/android_vendor_htc_chacha is not a valid repository name
Email [email protected]thub.com for help
Fetching projects: 1% (4/326) fatal: remote error:
CyanogenMod/[email protected]:/android_device_htc_chacha is not a valid repository name
Email [email protected] for help
Fetching projects: 39% (128/326) fatal: remote error:
CyanogenMod/[email protected]:/android_vendor_htc_chacha is not a valid repository name
Email [email protected] for help
Fetching projects: 61% (199/326) fatal: remote error:
CyanogenMod/[email protected]:/android_device_htc_chacha is not a valid repository name
Email [email protected] for help
Fetching projects: 94% (307/326) error: Cannot fetch android_vendor_htc_chacha
Fetching projects: 96% (313/326) error: Cannot fetch android_device_htc_chacha
error: Exited sync due to fetch errors
Re: [NEW][GUIDE] How to build for HTC ChaCha!
Local manifest seems to be outdated, you need to change the chacha 's git to point to github instead of assembla.
Sent from my Galaxy Nexus
not sure what i am doing wrong....... still the same
warning: local_manifest.xml is deprecated; put local manifests in `/home/ajai/WORKING_DIRECTORY/.repo/local_manifests` instead
fatal: remote error:
CyanogenMod/[email protected]:/android_device_htc_chacha is not a valid repository name
Email [email protected] for help
Fetching projects: 1% (4/325) fatal: remote error:
CyanogenMod/[email protected]:/android_vendor_htc_chacha is not a valid repository name
Email [email protected] for help
Fetching projects: 55% (179/325) fatal: remote error:
CyanogenMod/[email protected]:/android_device_htc_chacha is not a valid repository name
Email [email protected] for help
Fetching projects: 79% (257/325) fatal: remote error:
CyanogenMod/[email protected]:/android_vendor_htc_chacha is not a valid repository name
Email [email protected] for help
Fetching projects: 99% (322/325) error: Cannot fetch android_device_htc_chacha
error: Cannot fetch android_vendor_htc_chacha
error: Exited sync due to fetch errors
Best & the most organized TUT i've come across so far
I'm going to set-up an event in 3 weeks time (Maybe on the 5th of April) to help users with the HTC ChaCha source development. And hopefully end up with some ROMs in the end.
If anyone is interested in this please post your comments. I will only set this up if people are interested. Also I will host it on Google+ Hangouts with IRC. If the isn't any other easier way of helping.
Join the community on Google+ for more info.
lucasarran said:
I'm going to set-up an event in 3 weeks time (Maybe on the 5th of April) to help users with the HTC ChaCha source development. And hopefully end up with some ROMs in the end.
If anyone is interested in this even please post your comments. I will only set this up if people are interested. Also I will host it on Google+ Hangouts with IRC. If the isn't any other easier way of helping.
Join the community on Google+ for more info.
Click to expand...
Click to collapse
i am in
lucasarran said:
I'm going to set-up an event in 3 weeks time (Maybe on the 5th of April) to help users with the HTC ChaCha source development. And hopefully end up with some ROMs in the end.
If anyone is interested in this please post your comments. I will only set this up if people are interested. Also I will host it on Google+ Hangouts with IRC. If the isn't any other easier way of helping.
Join the community on Google+ for more info.
Click to expand...
Click to collapse
What about existing ROMS?
9v9 said:
What about existing ROMS?
Click to expand...
Click to collapse
Such as? The event is for building from source not current ROMs. But you can still come along with any other questions.
lucasarran said:
Such as? The event is for building from source not current ROMs. But you can still come along with any other questions.
Click to expand...
Click to collapse
I mean like cooking with an already ported ROM. But doing it from scratch from CM7 would be interesting to try. Is it a problem if I have no google+ or other accnts?
9v9 said:
I mean like cooking with an already ported ROM. But doing it from scratch from CM7 would be interesting to try. Is it a problem if I have no google+ or other accnts?
Click to expand...
Click to collapse
I won't be covering it, this is where you should start from and if you have any problems leave me a PM http://forum.xda-developers.com/c.php?t=1598713
lucasarran said:
I won't be covering it, this is where you should start from and if you have any problems leave me a PM http://forum.xda-developers.com/c.php?t=1598713
Click to expand...
Click to collapse
I will be doing this later this month and I will ask for help if it's needed. Thanks!
ERROR
I get this error when i type "repo sync -j8 WORKING_DIRECTORY"
CanYouSmell said:
I get this error when i type "repo sync -j8 WORKING_DIRECTORY"
Click to expand...
Click to collapse
When you see "WORKING_DIRECTORY" it refers to where you have decided to put your CM's sources... It's not the command to run.
In that case anyway, I'm not sure why it's even there.
THe command to sync the repo is:
Code:
repo sync -j8 -c
Hello,
I'm just starting to dive into the world of android development.
Therefor I wanted to have a look at the CM source code for my One S and maybe build it on my own.
What I did:
I followed this wiki http://wiki.cyanogenmod.org/w/Build_for_ville
When did everything start to go wrong:
$ repo sync @ http://wiki.cyanogenmod.org/w/Build_for_ville#Download_the_source_code
$ repo sync ends with errors on checkout:
error: packages/apps/Settings/: CyanogenMod/android_packages_apps_Settings checkout 561d03e5163df4f8b3265d0db3e46fa649b4058d
error: prebuilts/eclipse/: platform/prebuilts/eclipse checkout 127a8c3026fc57fdb7cd0f5183a94043f45e4afe
error: prebuilts/gcc/darwin-x86/arm/arm-eabi-4.6/: platform/prebuilts/gcc/darwin-x86/arm/arm-eabi-4.6 checkout b4a17d2eddd3d40bc665260c40d7bd38fe7b1e7b
and
$ brunch ville fails
I've already searched google but didn't find anything appropriate...
I hope someone can help me resolving this issue.
I'm quite new to Linux and Git, so maybe I'm missing some basics.
Thank you in advance!
eXtatic
I did do a cm11 repo sync to update my source and now i get this:
Fetching projects: 99% (471/475) Fetching project CyanogenMod/android_packages_apps_Email
fatal: remote error:
Repository unavailable due to DMCA takedown.
See the takedown notice for more details:
https://github.com/github/dmca/blob/master/2014-12-22-Cambridge-Mobile.md.
error: Cannot fetch CyanogenMod/android_external_svox
error: Exited sync due to fetch errors
I did a sync on cm10.2 and alsow get:
Fetching project platform/prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.7-4.6
Fetching projects: 99% (394/397) fatal: remote error:
Repository unavailable due to DMCA takedown.
See the takedown notice for more details:
https://github.com/github/dmca/blob/master/2014-12-22-Cambridge-Mobile.md.
error: Cannot fetch CyanogenMod/android_external_svox
error: Exited sync due to fetch errors
[email protected]:~/cm10.2$
Could someone just fix this?????
**** the DMCA!!!!!!!!!!!!!!! Most of us did pay a lot on phones.
I have the same problem today maybe a github problem. repo sync ask me to logon on github. I have tried with my github login but without success.
just ran into the same problem here, my work around was simply to remove that repo from the repo list.
just before repo sync, do this
Code:
nano .repo/manifests/default.xml
press ctrl+w <-- this will open search
type CyanogenMod/android_external_svox
enter
now remove that entire line
ctrl+o to save, followed by enter and ctrl+x to close nano
repo sync
do note, I'm not sure what function this repo serves, just that it shouldnt effect me, since im not building a rom from the source, only using CM to build kernels and recoveries, I hope.
Edit: I'm running into a building error now, so be careful, it could just be CM11 error, or due to my bypass.
Edit2: it's an art compiling problem.
http://review.cyanogenmod.org/#/c/82828/
Thunder07 said:
just ran into the same problem here, my work around was simply to remove that repo from the repo list.
just before repo sync, do this
Code:
nano .repo/manifests/default.xml
press ctrl+w <-- this will open search
type CyanogenMod/android_external_svox
enter
now remove that entire line
ctrl+o to save, followed by enter and ctrl+x to close nano
repo sync
do note, I'm not sure what function this repo serves, just that it shouldnt effect me, since im not building a rom from the source, only using CM to build kernels and recoveries, I hope.
Edit: I'm running into a building error now, so be careful, it could just be CM11 error, or due to my bypass.
Edit2: it's an art compiling problem.
Click to expand...
Click to collapse
what about the old repo like cm10.1, cm10.2 and etc. Are this 'android_external_svox' will take effect on compiling rom?
bangdes said:
what about the old repo like cm10.1, cm10.2 and etc. Are this 'android_external_svox' will take effect on compiling rom?
Click to expand...
Click to collapse
I wasnt building ROMs so it didn't matter to me...
but I just resync'ed after few hours and the repo was automatically re-linked to asop and it was still available there.
so it worked.. and it was cm11.
if you're on another version and it hasn't been fixed, just lock at the local manefest.xml or what ever the name is and change the repo manually.
to do so after you open the xml search for "android_external_svox".
Thunder07 said:
I wasnt building ROMs so it didn't matter to me...
but I just resync'ed after few hours and the repo was automatically re-linked to asop and it was still available there.
so it worked.. and it was cm11.
if you're on another version and it hasn't been fixed, just lock at the local manefest.xml or what ever the name is and change the repo manually.
to do so after you open the xml search for "android_external_svox".
Click to expand...
Click to collapse
Can I copying from different version, for example : jellybean-stable > cm10.1/cm10.2?
Sent from my GT-I9300 using XDA Premium 4 mobile app
Im trying to sync cm12's source code fro git hub
im using virtualbox on host windows 8.1
the virtual machine is ubuntu 14.xx
this porbably the 20th time i did a
Code:
repo sync
it always used to get stuck (it got interupted one way or another :c )
anyways ...later I finally made it till here
HTML:
Fetching projects: 100% (546/546), done.
Traceback (most recent call last):
File "/home/bass_face/.repo/repo/main.py", line 506, in <module>
_Main(sys.argv[1:])
File "/home/bass_face/.repo/repo/main.py", line 482, in _Main
result = repo._Run(argv) or 0
File "/home/bass_face/.repo/repo/main.py", line 161, in _Run
result = cmd.Execute(copts, cargs)
File "/home/bass_face/.repo/repo/subcmds/sync.py", line 681, in Execute
project.Sync_LocalHalf(syncbuf)
File "/home/bass_face/.repo/repo/project.py", line 1230, in Sync_LocalHalf
lost = self._revlist(not_rev(revid), HEAD)
File "/home/bass_face/.repo/repo/project.py", line 2309, in _revlist
return self.work_git.rev_list(*a, **kw)
File "/home/bass_face/.repo/repo/project.py", line 2503, in rev_list
p.stderr))
error.GitError: CyanogenMod/android rev-list ('^ddc4820db2658b6779caf9946e787098d6007967', 'HEAD', '--'): fatal: bad object HEAD
and i got this error can someone please guide me...and i did search for many possible solutions...nothing seems to be related to this porblem or is left unanswered, please help or atleast direct me to a proper solution
many thanks ^_^
Bass_Face said:
Im trying to sync cm12's source code fro git hub
im using virtualbox on host windows 8.1
the virtual machine is ubuntu 14.xx
this porbably the 20th time i did a
Code:
repo sync
it always used to get stuck (it got interupted one way or another :c )
anyways ...later I finally made it till here
HTML:
Fetching projects: 100% (546/546), done.
Traceback (most recent call last):
File "/home/bass_face/.repo/repo/main.py", line 506, in <module>
_Main(sys.argv[1:])
File "/home/bass_face/.repo/repo/main.py", line 482, in _Main
result = repo._Run(argv) or 0
File "/home/bass_face/.repo/repo/main.py", line 161, in _Run
result = cmd.Execute(copts, cargs)
File "/home/bass_face/.repo/repo/subcmds/sync.py", line 681, in Execute
project.Sync_LocalHalf(syncbuf)
File "/home/bass_face/.repo/repo/project.py", line 1230, in Sync_LocalHalf
lost = self._revlist(not_rev(revid), HEAD)
File "/home/bass_face/.repo/repo/project.py", line 2309, in _revlist
return self.work_git.rev_list(*a, **kw)
File "/home/bass_face/.repo/repo/project.py", line 2503, in rev_list
p.stderr))
error.GitError: CyanogenMod/android rev-list ('^ddc4820db2658b6779caf9946e787098d6007967', 'HEAD', '--'): fatal: bad object HEAD
and i got this error can someone please guide me...and i did search for many possible solutions...nothing seems to be related to this porblem or is left unanswered, please help or atleast direct me to a proper solution
many thanks ^_^
Click to expand...
Click to collapse
Did You try This Command
repo sync -f
Then find out whats the issue will causing
repo sync -l
mohamed786 said:
Did You try This Command
repo sync -f
Then find out whats the issue will causing
repo sync -l
Click to expand...
Click to collapse
yes i did try repo synnc -f and i even tried repo sync -f -j with various different values like 1,2,4,16,32
all with the same results...i even tried doing a smart sync i face this error
Code:
error: cannot smart sync: no manifest server defined in manifest
Bass_Face said:
yes i did try repo synnc -f and i even tried repo sync -f -j with various different values like 1,2,4,16,32
all with the same results...i even tried doing a smart sync i face this error
Code:
error: cannot smart sync: no manifest server defined in manifest
Click to expand...
Click to collapse
Just use this command repo sync -l to findout the issue
mohamed786 said:
Just use this command repo sync -l to findout the issue
Click to expand...
Click to collapse
I formatted my virtual HDD and set up everything from scratch following this guide -
https://github.com/PAC-man/android_vendor_pac/blob/pac-5.1/docs/PrepareForBuildLinux.md
As this was the official one run into some problem but I guess I solved it is running fine now.. But please keep an eye on this thread just in case if u could help me get through a problem.
Thanks a ton for replying
Will report the outcomes.
Bass_Face said:
I formatted my virtual HDD and set up everything from scratch following this guide -
https://github.com/PAC-man/android_vendor_pac/blob/pac-5.1/docs/PrepareForBuildLinux.md
As this was the official one run into some problem but I guess I solved it is running fine now.. But please keep an eye on this thread just in case if u could help me get through a problem.
Thanks a ton for replying
Will report the outcomes.
Click to expand...
Click to collapse
Most helpful commands during repo syncing
repo sync -j1 (-j# no of jobs )
repo sync -l (to find issues)
repo sync -c -d -j8
Dont let me post thanks on thread let hit thanks button for all in xda
mohamed786 said:
Most helpful commands during repo syncing
repo sync -j1 (-j# no of jobs )
repo sync -l (to find issues)
repo sync -c -d -j8
Dont let me post thanks on thread let hit thanks button for all in xda
Click to expand...
Click to collapse
this time many things synced properly but
HTML:
Syncing work tree: 61% (310/507) error: in `sync -f`: revision refs/heads/pac-5.1 in android_frameworks_base not found
Bass_Face said:
this time many things synced properly but
HTML:
Syncing work tree: 61% (310/507) error: in `sync -f`: revision refs/heads/pac-5.1 in android_frameworks_base not found
Click to expand...
Click to collapse
Ok.. use this command repo sync -j1 and leave for 6 to 8 hours base frame work base having lots of Gb to download
so be patient.....
Download time will depends on your internet connection.
Oki...and
1. Is there any ways to know when the downloads complete.. I mean a command that will check if everything is in place
2. Will files already downloaded delete itself and redownload.?
mohamed786 said:
Ok.. use this command repo sync -j1 and leave for 6 to 8 hours base frame work base having lots of Gb to download
so be patient.....
Download time will depends on your internet connection.
Click to expand...
Click to collapse
now this happened
Code:
Fetching project android_frameworks_base
error: RPC failed; result=56, HTTP code = 200
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
edit : notice that its just stuck there.? i mean the username doesnt show up (the $ doesnt show up)
edit 2 : i get this at the end then
Checking out files: 100% (3190/3190), done.
Checking out files: 100% (4197/4197), done.
Checking out files: 100% (244/244), done.
Checking out files: 100% (924/924), done.ng out files: 8% (81/924)
Checking out files: 100% (72151/72151), done.
Checking out files: 100% (35/35), done.king out files: 42% (15/35)
Checking out files: 100% (1021/1021), done.
Checking out files: 100% (2459/2459), done.
Syncing work tree: 100% (507/507), done.
[email protected]:~/pac-rom$
am i done.? *_* is this the end.?
Bass_Face said:
now this happened
Code:
Fetching project android_frameworks_base
error: RPC failed; result=56, HTTP code = 200
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
edit : notice that its just stuck there.? i mean the username doesnt show up (the $ doesnt show up)
edit 2 : i get this at the end then
Checking out files: 100% (3190/3190), done.
Checking out files: 100% (4197/4197), done.
Checking out files: 100% (244/244), done.
Checking out files: 100% (924/924), done.ng out files: 8% (81/924)
Checking out files: 100% (72151/72151), done.
Checking out files: 100% (35/35), done.king out files: 42% (15/35)
Checking out files: 100% (1021/1021), done.
Checking out files: 100% (2459/2459), done.
Syncing work tree: 100% (507/507), done.
[email protected]:~/pac-rom$
am i done.? *_* is this the end.?
Click to expand...
Click to collapse
cool
You have complete the source code download
wohoooo
mohamed786 said:
cool
You have complete the source code download
Click to expand...
Click to collapse
Thanks a ton for helping me out will never forget and...
for future reference (cause im not a irresponsible person who leaves a thread after finding the soltuion)
heres what i did:
for anyone whos setting up ubuntu and building lollipop just follow this guide, this is the most basic and mos efficient, you dont have to download a **** load of software if youre running the lates ubuntu version (except for the ones mentioned in the guide) -
HTML:
https://github.com/PAC-man/android_vendor_pac/blob/pac-5.1/docs/PrepareForBuildLinux.md
and most importantely and essential thing to do if youre running ubuntu/mac os x on a virtual box DISABLE ALL THE ANTIVIRUSES,FIREWALLS,ANTIMALWARE SOFTWARES (esspecially the ones dealing with netowrking
and if youve already set up everything and still having errors i suggest updating all and every packages essential [java,python,android sdk,android tools (download all the tools,extras,and the files for the rom your building (version) ]
if youre still having porplems go to the directory where the sources are being downloaded, hit ctrl+h (ubuntu-shows hidden files)
delete everything except .repo except .repo (orelse you will have to redownload all the sources) and initiate repo sync again
if it still doesnt work i suggest formatting everything and starting from scratch or atleast the sources or research till your tired of doing it
and never forget disable firewall or such things they were the culprits in my experience
i almost downloaded 70gb+ data in this process but learnt alot
the thread will most likely be closed now
Bass_Face said:
Thanks a ton for helping me out will never forget and...
for future reference (cause im not a irresponsible person who leaves a thread after finding the soltuion)
heres what i did:
for anyone whos setting up ubuntu and building lollipop just follow this guide, this is the most basic and mos efficient, you dont have to download a **** load of software if youre running the lates ubuntu version (except for the ones mentioned in the guide) -
HTML:
https://github.com/PAC-man/android_vendor_pac/blob/pac-5.1/docs/PrepareForBuildLinux.md
and most importantely and essential thing to do if youre running ubuntu/mac os x on a virtual box DISABLE ALL THE ANTIVIRUSES,FIREWALLS,ANTIMALWARE SOFTWARES (esspecially the ones dealing with netowrking
and if youve already set up everything and still having errors i suggest updating all and every packages essential [java,python,android sdk,android tools (download all the tools,extras,and the files for the rom your building (version) ]
if youre still having porplems go to the directory where the sources are being downloaded, hit ctrl+h (ubuntu-shows hidden files)
delete everything except .repo except .repo (orelse you will have to redownload all the sources) and initiate repo sync again
if it still doesnt work i suggest formatting everything and starting from scratch or atleast the sources or research till your tired of doing it
and never forget disable firewall or such things they were the culprits in my experience
i almost downloaded 70gb+ data in this process but learnt alot
the thread will most likely be closed now
Click to expand...
Click to collapse
MY pleasure
Happy Building In Advance
Thread closed at OP's request.
Hi,
I'm syncing the actual build of Cyanogenmod for lg 990p from Tonyp - At 99% I got the follwing error:
PHP:
Fetching project platform/external/chromium_org/third_party/WebKit
Fetching project CyanogenMod/android_packages_apps_UnifiedEmail
Fetching projects: 99% (469/473) Fetching project platform/external/chromium_org/v8
error: Cannot fetch cyngn/android_vendor_cyngn
error: Exited sync due to fetch errors
Commands I have used:
PHP:
git config --global user.email "[email protected]"
git config --global user.name "myname"
repo init -u git://github.com/p990-dev/android_manifest.git -b cm-11.0-tonyp
repo sync
Normal I would ask directly in the active development thread (http://forum.xda-developers.com/showthread.php?t=2769730), but unfortunately I have not enough posts to ask there.
Any Ideas what I am doing wrong?
Or is there an issue with the Repo?
Thanks in Advance
Patrick
answer to issue
this is an issue with the repo, or specifically with the default manifest. It appears that when the vendor/cyngen repo was removed, the manifest was not updated to not look for it. The simplest solution is simply to run repo sync with -f, which will force it to download all other packages. The more elaborate, and correct solution is to create or edit a file called local_mainfest.xml in working_directory/.repo/local_maifests that includes this:
Code:
<manifest>
<remove-project path="vendor/cyngn" name="cyngn/android_vendor_cyngn" />
</manifest>
This should allow you to repo sync successfully (if it still gives errors, make sure there is not a directory called "cyngn" in vendor/. If there is, just remove it, and sync up again.) I am still test ing make sure the build will complete successfully with these modifications. I will post back tomorrow (well, later today) once my build completes, or errors out.
I can confirm that this works. I had to work through some unrelated qirks before I could get a successful build and confirm, but it did build without the cyngen package, so the solution is to create a local_mainfest that excluded that package.