{
"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
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
I know that Jake had to step away from the project, and I pretty much intend on running my jfltetmo into the ground, so I'll be on jflte long-term. I'd like to start giving back to the community by seeing if I can pick up where Jake left off. I'm an electrical engineer with plenty of programming experience. I just don't have much in the embedded world. I saw that Jake had some work posted to Github on the 5.1 branch for jflte, but when I follow the directions in omnirom's Github Readme, I get an error of
error: Cannot fetch android_device_samsung_jflte
Can I manually copy the files, and where do they fit within the android structure?
Is Android Studio a good IDE for ROM development?
uagent said:
I know that Jake had to step away from the project, and I pretty much intend on running my jfltetmo into the ground, so I'll be on jflte long-term. I'd like to start giving back to the community by seeing if I can pick up where Jake left off. I'm an electrical engineer with plenty of programming experience. I just don't have much in the embedded world. I saw that Jake had some work posted to Github on the 5.1 branch for jflte, but when I follow the directions in omnirom's Github Readme, I get an error of
error: Cannot fetch android_device_samsung_jflte
Can I manually copy the files, and where do they fit within the android structure?
Is Android Studio a good IDE for ROM development?
Click to expand...
Click to collapse
Hmm, post the full error log? Also, if the branch is only in Jake's personal repos you may need to use a custom local manifest to use that for the device tree instead of Omni's jflte device tree.
I personally just use grep + emacs, I've never been much of an IDE person.
Entropy512 said:
Hmm, post the full error log? Also, if the branch is only in Jake's personal repos you may need to use a custom local manifest to use that for the device tree instead of Omni's jflte device tree.
I personally just use grep + emacs, I've never been much of an IDE person.
Click to expand...
Click to collapse
Hi, thanks for getting back to me! I deleted the directory and reinitialized the omni repo. Here is the error I keep getting, it seems to be choking on arm/linux/androideabi:
repo sync -j8 -f --no-clone-bundle|tee >> reposynclog.txt 2>&1
Fetching projects: 100% (480/480), done.
Syncing work tree: 93% (447/480) error: in `sync -j8 -f --no-clone-bundle`: [Errno 2] No such file or directory: u'/media/rhill/25e87ad3-e539-4009-9c40-0ab4db81d8e0/rhill/WORKING_DIRECTORY/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/.git/HEAD'
error: manifest missing or unreadable -- please run init
I re-ran
Code:
repo init -u git://github.com/omnirom/android.git -b android-5.1 > repoinitlog.txt 2>&1
Which doesn't seem to have thrown any errors at me, but I keep returning to the same broken package, even when I just run repo sync, with no options.
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.
I am trying to build AOSP. I have followed some instructions and the best are the instructions of Sony. But when I come to the point to clone the local_manifests, I need to have another file. I have found the AOSP-bacon repo on github where is a local_manifests to clone. So I have done that but when I try to sync the repo with the command 'repo sync' it gives this back:
[email protected]:~/android$ repo sync
fatal: remove-project element specifies non-existent project: platform/build
I have searched but could not find the answer what to do now. Can someone help me or say what I need to do to build AOSP?
Lennert_F said:
I am trying to build AOSP. I have followed some instructions and the best are the instructions of Sony. But when I come to the point to clone the local_manifests, I need to have another file. I have found the AOSP-bacon repo on github where is a local_manifests to clone. So I have done that but when I try to sync the repo with the command 'repo sync' it gives this back:
[email protected]:~/android$ repo sync
fatal: remove-project element specifies non-existent project: platform/build
I have searched but could not find the answer what to do now. Can someone help me or say what I need to do to build AOSP?
Click to expand...
Click to collapse
try deleting platform/build manually from the source and delete the same from the local_manifest.xml file then do a repo sync.