android-source

As you know, there is a list of several hundred projects in https://android.googlesource.com/ . I'd like to download them all in windows machine. According to Google's document, To install, initialize, and configure Repo: $ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo $ chmod a+x ~/bin/repo To clone the entire platform, install repo, and run: mkdir mydroid cd mydroid repo init -u https://android.googlesource.com/platform/manifest repo sync In my machine, however, I cannot "repo init" in Git Bash because it says it does not have python. I have python installed but

I just checked out master with repo. Now I want to switch to froyo. How can I do this without downloading a bunch of stuff again? I don't want to download a bunch of stuff again, I just want to be able to move freely between branches as in a normal git clone. Since you downloaded everything with repo, you can easily use repo to switch between branches without downloading everything again: repo init -b froyo; repo sync This will download only the files you need to switch branches, just like moving between branches with git. keyboardsurfer provides the commands to checkout the the froyo branch

Closed . This question needs to be more focused. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it focuses on one problem only by editing this post . I have built the Android source for the emulator. I read in the Android Source documentation that the path to 'emulator' is added autmatically during a successful build. However I have two questions about this: If I open a new shell or close my existing shell, 'emulator' is no longer found. Surely I don't have to build each time I want to run the emulator? If the emulator requires an AVD

Upon downloading the master branch from AOSP I get the following error: curl: (22) The requested URL returned error: 404 Not Found Server does not provide clone.bundle; ignoring. Why is this error coming? Log: * [new tag] android-cts-4.4_r1 -> android-cts-4.4_r1 * [new tag] android-sdk-4.4.2_r1 -> android-sdk-4.4.2_r1 Fetching projects: 7% (32/448) Fetching project platform/packages/apps/Launcher3 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 Not

For my thesis, I'm modifying the android framework and building the source (4.1.1 Jelly Bean). I can do a full build, but because this is very time consuming (I'm developing on a ubuntu 12.04 64bit virtual machine) I'd like to build separate modules. For example: When doing changes to the location modules, it should be possible to just build the changed module, and make a new system image: mmm frameworks/base make snod But this doesn't work. Every time I try to boot, the new system image won't boot because of: I/dalvikvm( 1696): DexOpt: mismatch dep signature for '/system/framework/framework

I'm building AOSP from source. What I would like to do is to include a few prebuilt files in the generated system.img as part of the make process. I'm trying to find the actual file that creates the system.img and add a few lines there. Any idea? Thank you in advance. GiantDwarf A good way of adding custom files to the system.img is to add them under vendor/your_name/product_you_want_to_add_them/proprietary/your_files_go_here and add a custom make file called device-product_name.mk . After that's done, just define which files are to be copied from the proprietary folder and inside (e.g. vendor

I am working on an automatic app updating solution for devices (LG p509 - Optimus 1) which we deploy to our customers. We have control of these devices and currently install a custom kernel on them (but not a full custom ROM). Since we are trying to do auto-updating of our app on the device, we need the system to be signed by a key which we control so we can sign our apps with the same key (to get the INSTALL_PACKAGES permission). I have been having a few issues running AOSP builds on the device (using the LG released source for the device), and am trying to take a step back and evaluate our