I have already the complete source code of android 4.0. How can I bring it to git so that I can compile and build it through ubuntu 14.04 LTS? Actually I want to build custom ROM.
Is there any other way of compiling and building it?
You do not need to put android source code to git, in order to build it. AOSP is a set of projects (hundreds) which already are in their own repos, at github or other hosts.
You should follow build instructions for your AOSP ROM. For example here it is for CyanogenMod built for Samsung Galaxy S4 mini LTE (serranoltexx)
https://wiki.cyanogenmod.org/w/Build_for_serranoltexx
If you'll be customizing a ROM and you want to put your changes to git, I think it would be right to fork changed repos and modify your repo manifest to use the forked repos.
Related
My team is looking to create our own custom ROM. I would like to base it on AOSP pie. Is there a way to fork or copy the code to GitHub?
I tried just using the Google repo, but it's bigger than my hard drive, so I can't clone it locally to push to GitHub.
We would prefer to base it on a pure Android, not another custom ROM
You can try directly form github:
https://github.com/aosp-mirror
Is mirrored from https://android.googlesource.com/platform/development.git
Hardware requirements:
Your development workstation should meet or exceed these hardware requirements:
A 64-bit environment is required for Android 2.3.x (Gingerbread) and higher versions, including the master branch. You can compile older versions on 32-bit systems.
At least 250GB of free disk space to checkout the code and an extra 150GB to build it. If you conduct multiple builds, you will need even more space.
Note: If you are checking out a mirror you will need more space as full Android Open Source Project (AOSP) mirrors contain all Git repositories that have ever been used.
If you are running Linux in a virtual machine, you need at least 16GB of RAM/swap.
Download the source following the guide here:
https://source.android.com/setup/build/downloading
The source is that big, so if your harddrive is too small you won't even be able to use a custom rom for reference.
For reference, the requirements tell you that you need 250GB for the source and 150GB for building. https://source.android.com/setup/build/requirements
I have a questions about TensorFlow Android Camera Demo, first of all, to start work with this demo I should download (clone) in my laptop all Tenserflow depositary? Or it's possible to download just Android camera example (if yes, then how to do it)?
If you're looking for just the camera demo, it looks like somebody did make a standalone version:
https://github.com/miyosuda/TensorFlowAndroidDemo
The main difference is that the official demo uses Bazel (Google's build tool) to build and has shared dependencies with other tensorflow targets in the full repo, whereas this is uses the standard Android toolchain (including the native code).
If you want to use the official repo, it should be possible to use Android Studio from the demo app directory, as gradle calls out to Bazel in it's build targets.
The TensorFlow Android Camera Demo is now build every night in Jenkins:
http://ci.tensorflow.org/view/Nightly/job/nightly-android/
The "Last Successful Artifacts" section has a "+" sign that you can expand a couple of times to find the tensorflow_demo.apk, which you can then install.
Follow the installation instructions in the README file to install the APK.
You have to first download the source from our repo. Then follow the additional instructions for the Android image demo to make it work.
I would like to add some features to the AOSP Email application which is not supported anymore. So I cloned the repository here (which is a Eclipse project) and migrated it to a Gradle project in Android Studio. But after that it comes to thousend Java errors, missing resources and so on...
So has Google really a not working repo there? Do I maybe need some other repos from AOSP? As it is for now I can't work with it anymore...
So I cloned the repository here (which is a Eclipse project) and migrated it to a Gradle project in Android Studio.
None of the AOSP projects are designed to be used this way. They are designed to be built as part of a firmware build.
If your objective is to contribute changes back to the AOSP, you will need to follow their instructions for using their source code.
If your objective was to create your own email app, you may be better served starting with some base that is buildable as a regular Android app (e.g., K-9 Mail). Otherwise, you are going to need to fix all of those problems, as they reference things that are not going to be available to your app project via the Android SDK.
I'm trying to explore libVLC for Android that's why setting up VLC android project on windows 7 but i'm facing problems. When i import the project and setup all helping libraries and try to compile using NDK it gives following error
make.exe: *** No rule to make target `jni/..//modules/codec/omxil/iomx.cpp',
needed by `obj/local/armeabi/objs-debug/iomx gingerbread/__//modules/codec/omxil/iomx.o'. Stop.
While when i try to search the file in my folder i only able to find iomx.h and iomx.cpp is actually missing but i downloaded the project from official repository.
git clone git://git.videolan.org/vlc-ports/android.git
I'm willing to follow a tutorial with proper configurations to setup and compile android application of VLC but i'm not able to find any tutorial and the official one says that it is for Linux and you will require a Linux or Mac OSX to follow this tutorial Tutorial Link. So my first question is
Can we Compile VLC android project Using all mentioned tools like (Android SDK, NDK, ant etc) on a windows platform.
Secondly i'm not able to find a detailed or much easy Documentation except this one VLC Documentation link, Are there any other easy to understand libVLC documentation more specific to android usage
Please help me or guide me in right direction. I want to develop an application for Docked DVD device for android.
I found my answer about this by myself and today watched this question unanswered so thought to answer it so that it can be helpful for others.
For the first part the answer is 'NO' we cannot compile the libVLC code on Windows OS using NDK as due to complex compilation process of libVLC. it Cannot be compiled using NDK tools that's why VLC released a script to compile libVLC which is in main directory when you download code from Git repository named Compile.sh and it can be run only on linux or mac as both based on Unix. i.e for libVLC compilation you need to run compile.sh which requires alot of linux based tools as mentioned in their official tutorial for compilation. you can try all those packages through cygwin on windows but i have not tried that rather i switched to Ubuntu 13.04 so that i can also explore linux environment...:). One thing i like to mention here if your target is just to use the compiled C++ code of libVLC in your project through java then you can do this on windows OS using libVLC.so file but if you need to change the libVLC code and recompile it then you will need to run compile.sh which requires linux or mac.
For the Second one the answer is same that as far as i know the only documentation i found was that i mentioned in my question.
If I download a project from https://android.googlesource.com to what Android API version will it be compatable ?
I have cloned a project.
Then created a project in Eclipse in that name with its res, src and manifest.xml, but still its shows error with some variables declaration missing , some functions arguments changed/not correct etc.
Any idea?
I'm using sdk_r08, and android 2.3 project working well.
Does the project from https://android.googlesource.com need any dependent files? If so what do I need to get those files?
Is there any extra arguments that I can set in git clone to get the project in a specific version?
You need to use the repo tool , then you can use the -b parameter to checkout a specific branch, see repo documentation for examples.
Actually you cannot load only a single project into eclipse since the whole OS tree is mutually dependent,
you have to checkout the whole source code, make a compile and then copy the .classpath in the root folder of the build and create a java project using this classpath. and ONLY then will you be able to load a project.
however note that the AOSP compiles only on 64bit Ubuntu 10.04 (version and distro is mostly because of library versions and dependencies, I've seen people do it on fedora and suse)
the compile is horrific however you ARE compiling an OS from scratch so ...
it takes about 5 hours on a dualcore pentium u 3gigs of ram..
and about 20 mins on i7 with running
make -j16
after importing everything in eclipse you can work with individual applications like, Launcher, Contacts, Calendar, Phone.. etc..
however to actually install anything on a real device (without flashing the whole rom) you have to refactor/rename the project package declaration since most of them are com.android.* which means the device will not override the default app installed
in short, after setting up the workstation:
(don use -b gingerbread since it is the bleeding edge branch, numbered versions are production branches so bugs are minimal)
repo init -u https://android.googlesource.com/platform/manifest -b android-2.3.4_r1
repo sync
. build/envsetup.sh
lunch 1
make -j8
most of the flags I am using are explained in the tutors below...
More info on the subject:
Workstation setup : http://source.android.com/source/initializing.html
Downloading source ; http://source.android.com/source/downloading.html
Building : http://source.android.com/source/building.html
and most important.. howtos...
http://www.youtube.com/watch?v=1_H4AlQaNa0
http://www.youtube.com/watch?v=rFqELLB1Kk8