I'm looking for the android sources that are hosted on kernel.org (according to this site: http://source.android.com/source/downloading.html). However since kernel.org was hacked a few weeks ago, it is down. Is there a friendly fork of the sources somewhere (e.g. github) for me to clone?
There are indeed some parts available on github: https://github.com/android
But not everything I believe.
My starting point for getting it from github is here:
https://github.com/cellcortex/github_android
--- edit
pretty much gave up on using the half-complete github forks. Instead I chose to use http://www.cyanogenmod.com/ which has complete android OS sources on github.
Related
This may look like a duplicate question, but all the previous answers were too much confusing for a ameature developer like me. I have never used NDK before and I am working with android studio and windows PC. Previous answers(1,2) and other sources are suggesting to use linux to compile. I couldn't understand what to do. Can anyone guide me through the steps about embeding libvlc in my android app
If you are having trouble with compiling vlc , then you can use the following library , thou it is unofficial , but I worked with it and it worked fine .
Unofficial VLC Android SDK
If you're on Windows 10, you should be able to follow the wiki at https://wiki.videolan.org/AndroidCompile/ using WSL (and google/use the videolan forum for what you don't know).
If you don't want to compile, another way could be to download the apk of the official vlc-android app, unzip it, extract the libs you want (namely libvlcjni.so and probably libjniloader.so) and add it to your project (which means making gradle happy).
vlc-android is a fully opensource app that does exactly what you want to do. Feel free to have a look.
Good luck
I honestly think Google really did not do a great job at keeping their Android documentation and training guides up to date. Numerous times I encountered situations where the documentation refers to samples that no longer exist.
Most recently I've been trying to learn about animation for Android.
Google seems to have a good API guide about animation:
https://developer.android.com/guide/topics/graphics/prop-animation.html
The guide refers to sample "com.example.android.apis.animation" in the API Demos sample. If you click on the "API Demos" link on that page, it brings you to another page with other samples.
After a bit of searching, I found the older samples have been moved and they can now be downloaded from git using this command:
git clone https://android.googlesource.com/platform/development
Once downloaded, the sample I am looking for can be found at "samples/ApiDemos". The only problem now is those samples don't have a build.gradle file. They must have been created at a time when gradle was not being used yet.
I am obviously new to Android and I am trying to learn the ropes. I am using android studio to build my projects. All the tutorials I've been reading use gradle to build the android application.
My question is in this post is (1) how to get to the older samples that are referred throughout the current Android API guides like the example above, I hope I have identified the correct git repo. (2) How the heck can I compile those older samples.
(1) how to get to the older samples that are referred throughout the current Android API guides like the example above, I hope I have identified the correct git repo.
The only way is to google and try to find them. There is no central repo for old versions of those (at least none that I'm aware of)
(2) How the heck can I compile those older samples.
Instead of opening those projects normally, close your current project (File > Close Project) and then choose "Import from Eclipse". This will look into all configs and generate a build.gradle for you.
I use 2 machines for development, Windows 8 desktop and a Macbook for when I'm away from my desk. I use dropbox to sync my development files between 2 machines. This works pretty well, except for one thing: the SDK path must be updated every time (http://screencast.com/t/XKnqUjiBn)
Is there a work around of some sort for this?
Don't share the local.properties file between machines; that's the file that contains the SDK path, and as its filename indicates, it's supposed to be local to an individual machine.
I suggest that you take a look at a GIT source control (if you haven't done that previously). It is the way better way to manage projects than dropbox sync.
There are 2 very good options for you:
GitHub - free for open source projects, paid for private repositories (paid per repository)
BitBucket - free for private repos too (paid per user)
AndroidStudio (which I suggest for Android projects unless you are working with NDK) has a really good support for importing projects to GIT via GUI. So it helps you a bit if you are not familiar with console stuff. But it is easy with console too. Check out this github tutorial for beginners https://try.github.io/levels/1/challenges/1
With GIT the problem that you are trying to solve is simple just put a file name that you dont want to share into you gitignore file. You can find android preset gitignore files online on sites like gitignore.io.
Good luck.
I'd like to merge pull from here https://github.com/Itseez/opencv/pull/1820 with opencv 2.4.7 for Android. I understand that the Library is included in project but pull from github has to be build somehow and put into my phone as new opencv manager, am i right? Could someone help with this task?
You need to download the sources of OpenCV, and then pull or cherry-pick those two changes on top of used branch. That is more a git related problem than OpenCV :)
On top of that, it looks like the change You are writing about is already merged into the main branch. If You download the sources and NOT checkout on 2.4.7 tag, You will have the slightly buggy, slightly unstable bleeding-edge version of OpenCV, with these changes.
Of course, after that You will need to build the library, but there is a good manual for that at library's web page.
As for building the Android version of OpenCV, here is a tutorial at the official wiki
I've been looking for a finished/working ImageView on Android that has pinch/zoom behavior. Although there are code-snippets all over S.O. for this I want something a little more finished that I can just build and use.
GitHub, which I've never used before, seems to have candidates. As far as I can tell GitHub is a free, public project-hosting, source-control system, but I'm only interested in downloading and trying out projects on it, which can be done by the "Download Zip" button on it.
I recently tried a project called PhotoView but after getting it all imported into my Eclipse development environment I found it had dependencies on a higher API level than I was using or targeting.
Is there any way to avoid that in the future? I.e., is there any place on GitHub where the developers typically lists technical requirements like programming language, target development environment, compiler or SDK versions, etc, so before bothering to download a GitHub project I can guess whether it's even buildable in my environment?
Edit: In my browser I can see a brief revision history but it looks like it only goes back a few changes so the manifest or other key files aren't always visible. Is the only way to see the project files to download the ZIP file, unpack it and look at it in my development environment on my local PC?
Thanks in advance.
Is there any way to avoid that in the future?
Browse the source code. For example, the manifest file (for the component or a demo app) should indicate the android:minSdkVersion.
is there any place on GitHub where the developers typically lists technical requirements like programming language, target development environment, compiler or SDK versions, etc, so before bothering to download a GitHub project I can guess whether it's even buildable in my environment?
Yes. It's called the project README, and you were already there, most likely, as it is the "home page" of the repository. The amount of documentation any given developer will write for any given component will vary.
You are also welcome to file issues against the project, asking for more documentation on this sort of thing, but if and when that issue will be acted upon will also vary.
readme file in root of the project, and Wikipages of that repositories could help you find out additional information about that repository. But at the end, contributors are responsible to prepare this kind of information and some of them don't care. So, you can look for Android manifest file of the project and check the content in GitHub website before download and unzip it.