Android Police has a good article about the differences between SDK and Source and CyanogenMod's involvement in the two. I hope you enjoy.
http://www.androidpolice.com/2011/1...eam-cm9-will-arrive-when-the-ics-source-does/
Related
kernel, platform, dev-tools, and "extra" source code!
here
to answer the most obvious question:
Jean-Baptiste Queru said:
Here are the GPL source files that match the 4.0 / r14 SDK.
Like we did for all Honeycomb release, this is NOT the full source tree for IceCreamSandwich, these are only the GPL parts that are in the SDK (along with a few associated files), and they're not enough to build the whole IceCreamSandwich for a device.
Click to expand...
Click to collapse
thanks for the link, but the code is useless - no UI libraries, no dalvik to boot JAR's,
no applications... still waiting until google releases the full sources in november
I agree it's mostly useless, but the kernel source at least provides the basic patches needed for the newer version.
the basic patches are for the emulator only.
we need drivers from LG for our hardware, at least a kernel dev like franco can port the drivers to the 3.0
tree, but its a lot of work ... and currently he didnt have a lot of time.
I was just stumbling around lauchpad and found this:
https://code.launchpad.net/~ubuntu-branches/ubuntu/raring/ubuntu-defaults-nexus7/raring
Is this part of the source code for Ubuntu for Phones?? Not much is said about it on the page. The source tree looks different than the ubuntu source tree, but it might just be patches and a tool-chain to apply to ubuntu-arm.
Edit: This is not the source code, sorry. It's for Ubuntu on the Nexus 7: https://wiki.ubuntu.com/Nexus7/Installation.
I'm completely new to developing and this is my first Android project and also my first time using Github (or any other vcs). I've found guides for how to import projects from Github into Android Studio, but I can't figure out how to upload a new project to Github. I've created a basic project with Android Studio and I've installed git for Windows and openssh in cygwin, but not sure where to go from here. Any help would be great.
Hello,
I have a question about the best way to manage an Android software project that will involve modifying core Android code.
My question is not a normal "how to do this in Android", but rather, concerns the code management process and the build procedure. Has anyone any experience with this, or can point me somewhere?
We are starting a project to implement an audio application on Android phones, the various ARM architectural flavours. This will involve modifying and extending the C/C++ code in the Media Framework library, plus some supporting Java code. In other words, relative to the complete Android codebase, the amount of code that will be affected is quite small. We will need to support various Android versions and various phone manufacturers and models per manufacturer. Our development process concerns using the pure AOSP as a basis, and initially targeting the Google Nexus as a reference platform. After that, customisations needed for real-world phones will be done in cooperation with the phone manufacturers.
From a code management viewpoint, my idea was to maintain a git repository for our Media Framework files, that will be branched for each maintained version of Android. Separately, we will check out from the Google AOSP repository the code for each supported version of Android, and overlay/merge our Media Framework code onto this codebase. The resulting codebase for each version of Android will be built targeted to the range of Android phones that we support, initially the reference Google Nexus.
Some development approaches that come to mind:
- For each Android version, we could patch Android's Media Framework with our code, and then maintain the entire merged AOSP in a local git repository. This would be a huge undertaking, when branches are included, but would at least guarantee that the codebase is always up to date. Howoever, merging our code changes across difference Android versions would be difficult.
- Another option is to only maintain our Media Framework files in a local git repository, branched for each Android version. Before building a specific Android version,we could checkout the Android version from the Google repository (or keep it cached locally on our build system or on developers' machines) and then patch Android's Media Framework files with our files.
Many thanks,
polomora
WiFi direct has a shell tool for doing configuration changes called "p2p_cli". I can't find a newer version compiled to run on Android 5.0 with the new PIE security requirement.
It seems to be part of the Android platform source code, here: https://android.googlesource.com/platform/external/wpa_supplicant_8/+/master/src/p2p
Reference on PIE compile:
http://stackoverflow.com/questions/...id-l-error-only-position-independent-executab
Some ROM developer can maybe compile it for me and provide a download of the binary? Thank you.