Database Users

[Q] git 2.3 source code , which directory

i went to GIT looking for source code for android 2.3 and looked in the 'platform ' project at : git url root p=platform/frameworks/base.git;a=summary
i found the list of GIT tags below but not 2.3 .. where do i get just 2.3 source?
Tag list from GIT:
android-adt-0.9.9
android-adt-0.9.8
android-2.2_r1.2
android-2.2_r1.3
android-2.2.1_r1
android-cts-2.2_r3
android-cts-2.1_r5
android-sdk-2.2_r2
android-sdk-2.2_r1
android-sdk-tools_r6
android-sdk-tools_r7
android-cts-2.1_r4
android-cts-2.2_r2
android-cts-2.2_r1
android-2.2_r1.1
this is all froyo stuff. where do i get gingerbread?

2.3 source has yet to be released. Should come soon after Nexus S launch.

Android 3.2 source code available

Just wondering...
Does this mean we can bake an SGS2 ROM with Android 3.2 now, or are the listed caveats insurmountable?
Android 3.2 source code available
As usual, and just like we had done before for Android 3.0 and 3.1,
the source code for the GPL and LGPL components of Android 3.2 is
available in the Android Open-Source Project, under the tag
android-3.2_r1
The process to build it is the same as what we had for 3.0 and 3.1:
# start from a master client
repo init -m 3.2-base.xml
repo sync
repo forall -c git checkout android-3.2_r1
# build with the regular process
# to come back to a plain master
repo init -m default.xml
repo sync
The caveats are unchanged since 3.1:
-the checkout command will return an error message because the tag
doesn't exist in all projects, ignore it.
-the compiled isn't any more likely to work on actual hardware as 3.1
did, since the same binary incompatibilities are still there.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

Tsais said:
Just wondering...
Does this mean we can bake an SGS2 ROM with Android 3.2 now, or are the listed caveats insurmountable?
Android 3.2 source code available
As usual, and just like we had done before for Android 3.0 and 3.1,
the source code for the GPL and LGPL components of Android 3.2 is
available in the Android Open-Source Project, under the tag
android-3.2_r1
The process to build it is the same as what we had for 3.0 and 3.1:
# start from a master client
repo init -m 3.2-base.xml
repo sync
repo forall -c git checkout android-3.2_r1
# build with the regular process
# to come back to a plain master
repo init -m default.xml
repo sync
The caveats are unchanged since 3.1:
-the checkout command will return an error message because the tag
doesn't exist in all projects, ignore it.
-the compiled isn't any more likely to work on actual hardware as 3.1
did, since the same binary incompatibilities are still there.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Click to expand...
Click to collapse
honeycomb is just meant for tablets not cellphones..

ditto to the guy above me...
and this belongs in general, read the damn stickies!
We have known for about week now as well... thanks for the old news!
<Ninpo> rofl it's only the GPL and LGPL components
<Ninpo> so not the full thing by a long shot since most of Android is Apache licensed

Also, this is only the LGPL and GPL components, which is a hell of a long shot away from being actual Honeycomb sources, since most of Android is under the Apache license.

I remember reading that Google will release full source code for Honeycomb some time after Ice Cream Sandwich release.

[guide][wip] [beginners] how to push a device tree to github

SO AS OF NOW WE HAVE GUIDES ABOUT HOW TO MAKE A KERNEL , ROM FROM SOURCE CODES..THIS GUIDE WILL TALK ABOUT PUSHING THE DEVICE TREE OR KERNEL TREE TO YOUR GITHUB ACCOUNT ...THIS IS A BEGINNER'S GUIDE IN THIS GUIDE I WILL ASSUME THAT UR BUILDING CM 11
STEP1:- CREATE A GITHUB ACCOUNT
STEP 2 :- CREATE A REPOSITORY BY CLICKING THE "+" beside ur user name and name it "android_device_samsung_i9082"
STEP 3 :- in the terminal navigate to the device folder
Code:
cd cm11/device/samsung/i9082
STEP 4 : WE ADD THE REPOSITORY TO WHICH WE HAVE TO PUSH THE FILES TO
Code:
git remote add cm https://github.com/username/android_device_samsung_i9082.git
STEP 5: we create a branch
Code:
git branch cm-11.0
Code:
git checkout cm-11.0
STEP6: WE PUSH THE THE TREE
Code:
git push -u cm cm-11.0
THIS GUIDE IS A WIP ... I WILL UPDATE IT SOON WITH PICTURES ..TO MAKE UL UNDERSTAND BETTER
CREDITS
1) @k2wl
2) help.github.com
3) @jackeagle

reserved

It would be pretty nice if you can add in on how to cherry-pick and git log --graph.Anyways,this guide is very detailed and useful overall and have an awesome say ahead [emoji1][emoji1][emoji106]
Sent from Planet Phaser

The-Grape said:
It would be pretty nice if you can add in on how to cherry-pick and git log --graph.Anyways,this guide is very detailed and useful overall and have an awesome say ahead [emoji1][emoji1][emoji106]
Sent from Planet Phaser
Click to expand...
Click to collapse
Yea sure ... As u saw .. This guide is a wip .. I will add pictures and more .. Fr users to get a better idea of how its done

rutvikrvr said:
Yea sure ... As u saw .. This guide is a wip .. I will add pictures and more .. Fr users to get a better idea of how its done
Click to expand...
Click to collapse
Thanks a lot

[GUIDE]Git Advanced Methods
Sometimes,you might be wondering how can i update the device tree without deleting my current device tree but through applying the latest changes
Well today i will teach you a new function call cherry-picking.This function is one of the most known features of git as it provides simple and easy copy-pasting job for you
First of all,add the remote first.Note:The hello is the main remote for this link
Code:
git remote add name url
eg: git remote add hello https://github.com/AOGP/android_packages_apps_Lightbulb.git
Second,fetch the remote
Code:
git fetch name
eg: git fetch hello
Thirdly,once finish fetching.Copy the commit id from github
Code:
git cherry-pick SHA-1/Commit ID
eg: git cherry-pick a7d0c5fc6df49a07855ccb36fb22fdaf321e20ba
If you faced any errors,solve them by typing and then see the red color files name in the terminal and fix them by comparing between <<<<<<<HEAD
Code:
git status
Once done solving all the errors,push the commit to github to keep the authorship of the commit as it is rude to just use their work and put yourself as author
Code:
git push [name of the remote] [your repository branch]
eg: git push origin master

guide updated in compliance with authorship of commits

[Q] Building Android Source

Simple Question,
I've downloaded android source over Git with
Code:
git clone https://android.googlesource.com/device/asus/grouper
Is this enough?

No. Source.android.com has a complete walkthrough on how to build. You need to do much more than a git clone. You need all the repos for source.
#stayparanoid

[Q] How to switch branches with repo

As I get more into android development for the Nexus 6 I have yet to figure out how to update to the latest android build while leaving my local changes. So for example I am working on 5.0.0 and made changes. Now 5.0.2 is out I want to update to that build. The only I have found is going a repo init but to my knowledge this wipes out your changes. Is there a way to switch and merge your local changes?
Thanks in advance

http://gitref.org/

DSA said:
http://gitref.org/
Click to expand...
Click to collapse
So say I have a change in every git repo, would doing those commands through a `repo forall` be the proper way?

sorry, use this one instead:
http://jonas.nitro.dk/git/quick-reference.html
just an example:
Code:
Branches:
git checkout branch Switch working tree to branch
-b branch Create branch before switching to it
git branch List local branches
git branch -f branch rev Overwrite existing branch, start from revision
git merge branch Merge changes from branch
or this:
https://confluence.atlassian.com/display/STASH/Basic+Git+commands
another similar example:
Branches
Create a new branch and switch to it: git checkout -b <branchname>
Switch from one branch to another: git checkout <branchname>
List all the branches in your repo, and also tell you what branch you're currently in: git branch
Delete the feature branch: git branch -d <branchname>
Push the branch to your remote repository, so others can use it: git push origin <branchname>
Push all branches to your remote repository: git push --all origin
Delete a branch on your remote repository: git push origin :<branchname
Click to expand...
Click to collapse