Working with GIT and GITHUB
for Android Source
I want to start by saying that I am no EXPERT on GIT, but I believe the best way to learn is through trial and error. Through my trials and errors, this is what I have found that works when working with Android Source Code (AOSP).
I started my Android Development basically porting and hacking Android Operating Systems for the HTC Thunderbolt. In my opinion I learned the basics plus some, and was able to create stable builds, which most users found enjoyable to operate. In my quest to further improve my Android development skills, I moved on the next step in Android Operating System development, build a custom AOSP ROM from source. I soon started browsing other developers GITHUB repositories and tried my best to figure out what was going on behind the scenes, in order to share my code with others and visa versa. This lead me to setting up a development platform, downloading the latest (at the time ICS) source and then compiling everything, to obtain, a fresh updated ROM. Obviously, the next step was editing the code to my liking and then trying to figure out how to update my code (push) to Github for version tracking and also hosting purposes. I shopped around on the net for GIT tutorials, and for the life of me, I could not figure out how to make things work the way they should. After doing research on the REPO command (which I came to find was basically the same as GIT but updated to work better with Android) I became more confused. I never found an article or tutorial which explained step-by-step the processes in which I am about to explain, which is why I decided to take the time to compose this tutorial.
Finally, through many hours of research and frustration, I came up with the answers I was so diligently seeking. Here are my findings:
The following Tutorial is for an INITIAL COMMIT of your source to GITHUB. Once you accomplish sending the initial data over, sending only changes thereafter, is very similar, but doesn't require as many steps.
Prerequisites:
(1) Create an account on GITHUB.com
(2) Download the Android Source into a working directory (in my case "android").
(3) Generate your Private SSH Keys for GITHUB (this will allow you to push files without logging in every time) You will find easy to understand directions HERE
For this example I will be working with the following variables:
My default Android directory: ~/android
For this tutorial I will editing the Setting.apk source code in order to add "XYZ" functionality
The source code for the Settings.apk is located in ~/android/packages/apps/Settings
So lets BEGIN!
First Step: You want to go into the directory where you are editing the source.
Code:
cd ~/android/packages/apps/Settings
Second Step: Initialize the Settings source folder and create a git repository
(which will track all changes)
Code:
git init
Third Step: Now you want to log-in to GITHUB and create a repository for your updated Settings source to go. In my case I created a folder on GUTHUB called android_packages_apps_Settings
Forth Step: After you have created your repository on GITHUB, from your Settings source folder, you need to tell git where to push the changes you have made. When you do the initial push, it is actually going to push all of the files in the Settings source folder including the changes you have made. Do this by typing the following command:
Code:
git remote add github [email protected]:yourusername/android_packages_apps_Settings.git
Obviously, you are going to change "yourusername" to whatever username you created on GITHUB.
Fifth Step: Add the entire Settings directory to git so that it starts tracking your additions, deletions, changes, etc for the entire directory.
Code:
git add -A
Sixth Step: Commit the changes that you made to the files in order to push to GITHUB. Now for this example, I want to commit changes to ALL files in the Settings folder.
Code:
git commit -a
If I wanted to just commit changes to one specific file, I would use "git commit whateverfile.java". After you commit, a text editor is going to pop-up. This is where you add the description for the change(s) you have made. If you have detailed change-log of each file you changed, you will not want to use the "git -a" command because the description you enter there is going to be the description for all of the files you edited.
Seventh Step: Now you want to change to the branch you plan on using to push your content. In my case its "jellybean".
Code:
git branch jellybean
Eighth Step: Finally you will now push your initial Settings commit to github. In order to do this, type:
Code:
git push github jellybean
This is going to push github ("github" is the name you gave the REMOTE when you executed the "git remote add" above) to a branch on GITHUB.com called "jellybean". You can name the branch whatever you like, but obviously naming it to the current Android release name is the easiest to remember for you and others.
You should now see that your computer sent files to GUTHUB.com and if you check online, you should see that your changes have been implemented and copied for the world to access.
I hope this helps people out with Android based git commands. I wish I found somthing like this months ago and maybe I would have a few extra hairs on my head. Let me know if you have any additional questions or would like me to add to this tutorial in any fashion. I will be doing a video shortly which I will post to this thread when complete.
Saved for Questions and Answers . . .
Create repository on github called packages_apps_Settings
Clone it
Code:
git clone https://github.com/lithid/packages_apps_Settings.git
cd packages_apps_Settings
Find the aosp settings and pull that repo so all proper history is still entact. Then merge it.
Code:
git pull https://android.googlesource.com/platform/packages/apps/Settings refs/tags/android-4.1.1_r6
Save it
Now add it all and push to your local repo.
Code:
git push
Hello, how do you create a device tree because I want to build from source but my phone does not yet have one. Thanks
itzdarockz said:
Hello, how do you create a device tree because I want to build from source but my phone does not yet have one. Thanks
Click to expand...
Click to collapse
When you say "a device tree" are you referring to the propriety device drivers and such for a particular device?
MyComputerDoctor said:
When you say "a device tree" are you referring to the propriety device drivers and such for a particular device?
Click to expand...
Click to collapse
I mean to build from source and when picking your lunch such as crespo and crespo 4G i want to add my phone into that. Is that necessary to build from source though?
itzdarockz said:
I mean to build from source and when picking your lunch such as crespo and crespo 4G i want to add my phone into that. Is that necessary to build from source though?
Click to expand...
Click to collapse
Let me know if this helps: http://www.netmite.com/android/mydr...build_new_device.html#androidBuildNewFileTree
Thanks for this tut! I've been wanting to push out sources to my github for a while...but couldn't really find a good tut/didn't have the time to do all the research...this seems like it should get me going with my github and I will definatly be using this tut soon
Sent from my SGH-I997 using Tapatalk 2
question, Let's say I want to merge a commit from CyanogenMod's GitHub ..... I use AOKP's Source, is there a command using git that I can use to facilitate this ??
johnhany97 said:
question, Let's say I want to merge a commit from CyanogenMod's GitHub ..... I use AOKP's Source, is there a command using git that I can use to facilitate this ??
Click to expand...
Click to collapse
Use git cherry-pick but first you need to add the repo
So for example you want a commit from settings first you add CM's settings as a repo with git remote add <name> <url> ....Name can be anything
So it will be $ git add remote cm https://github.com/CyanogenMod/android_packages_apps_Settings
then you can either git fetch cm which will sync all the branches out you can just sync a single branch $ git fetch cm cm-10.1
Now you can use git cherry-pick to cherry-pick the commit from CM settings
$ git cherry-pick <sha1>
e.g
$ git cherry-pick 64c377
Now you will probably need to resolve some conflicts which is hard to explain how to resolve as it varies between has been added where cherry-picked.
can some one ell me how i merge the halo from PA ?
thanks
MyComputerDoctor said:
Working with GIT and GITHUB
for Android Source
I want to start by saying that I am no EXPERT on GIT, but I believe the best way to learn is through trial and error. Through my trials and errors, this is what I have found that works when working with Android Source Code (AOSP).
I started my Android Development basically porting and hacking Android Operating Systems for the HTC Thunderbolt. In my opinion I learned the basics plus some, and was able to create stable builds, which most users found enjoyable to operate. In my quest to further improve my Android development skills, I moved on the next step in Android Operating System development, build a custom AOSP ROM from source. I soon started browsing other developers GITHUB repositories and tried my best to figure out what was going on behind the scenes, in order to share my code with others and visa versa. This lead me to setting up a development platform, downloading the latest (at the time ICS) source and then compiling everything, to obtain, a fresh updated ROM. Obviously, the next step was editing the code to my liking and then trying to figure out how to update my code (push) to Github for version tracking and also hosting purposes. I shopped around on the net for GIT tutorials, and for the life of me, I could not figure out how to make things work the way they should. After doing research on the REPO command (which I came to find was basically the same as GIT but updated to work better with Android) I became more confused. I never found an article or tutorial which explained step-by-step the processes in which I am about to explain, which is why I decided to take the time to compose this tutorial.
Finally, through many hours of research and frustration, I came up with the answers I was so diligently seeking. Here are my findings:
The following Tutorial is for an INITIAL COMMIT of your source to GITHUB. Once you accomplish sending the initial data over, sending only changes thereafter, is very similar, but doesn't require as many steps.
Prerequisites:
(1) Create an account on GITHUB.com
(2) Download the Android Source into a working directory (in my case "android").
(3) Generate your Private SSH Keys for GITHUB (this will allow you to push files without logging in every time) You will find easy to understand directions HERE
For this example I will be working with the following variables:
My default Android directory: ~/android
For this tutorial I will editing the Setting.apk source code in order to add "XYZ" functionality
The source code for the Settings.apk is located in ~/android/packages/apps/Settings
So lets BEGIN!
First Step: You want to go into the directory where you are editing the source.
Code:
cd ~/android/packages/apps/Settings
Second Step: Initialize the Settings source folder and create a git repository
(which will track all changes)
Code:
git init
Third Step: Now you want to log-in to GITHUB and create a repository for your updated Settings source to go. In my case I created a folder on GUTHUB called android_packages_apps_Settings
Forth Step: After you have created your repository on GITHUB, from your Settings source folder, you need to tell git where to push the changes you have made. When you do the initial push, it is actually going to push all of the files in the Settings source folder including the changes you have made. Do this by typing the following command:
Code:
git remote add github [email protected]:yourusername/android_packages_apps_Settings.git
Obviously, you are going to change "yourusername" to whatever username you created on GITHUB.
Fifth Step: Add the entire Settings directory to git so that it starts tracking your additions, deletions, changes, etc for the entire directory.
Code:
git add -A
Sixth Step: Commit the changes that you made to the files in order to push to GITHUB. Now for this example, I want to commit changes to ALL files in the Settings folder.
Code:
git commit -a
If I wanted to just commit changes to one specific file, I would use "git commit whateverfile.java". After you commit, a text editor is going to pop-up. This is where you add the description for the change(s) you have made. If you have detailed change-log of each file you changed, you will not want to use the "git -a" command because the description you enter there is going to be the description for all of the files you edited.
Seventh Step: Now you want to change to the branch you plan on using to push your content. In my case its "jellybean".
Code:
git branch jellybean
Eighth Step: Finally you will now push your initial Settings commit to github. In order to do this, type:
Code:
git push github jellybean
This is going to push github ("github" is the name you gave the REMOTE when you executed the "git remote add" above) to a branch on GITHUB.com called "jellybean". You can name the branch whatever you like, but obviously naming it to the current Android release name is the easiest to remember for you and others.
You should now see that your computer sent files to GUTHUB.com and if you check online, you should see that your changes have been implemented and copied for the world to access.
I hope this helps people out with Android based git commands. I wish I found somthing like this months ago and maybe I would have a few extra hairs on my head. Let me know if you have any additional questions or would like me to add to this tutorial in any fashion. I will be doing a video shortly which I will post to this thread when complete.
Click to expand...
Click to collapse
Did you finish the video tutorial?
Sent from my LG-LS970 using Tapatalk 4 Beta
sooo?
Does anyone have further information on how you would sync back to a master? That is, if I sync from AOSP today, make my own changes, and then a few weeks from now I want to resync to an updated AOSP, how do I do this?
Hello peeps,
I can't build CM10.1 (maguro) in Eclipse, I got an error from packages/apps/apollo/src/com.andew.utils/RefreshableFragment.java. It's about Fragment class.
Here is the error :
The type android.view.View$OnCreateContextMenuListener cannot be resolved. It is indirectly referenced from required .class files.
And naturally project can't be built :
The project was not built since its build path is incomplete. Cannot find the class file for android.view.View$OnCreateContextMenuListener. Fix the build path then try building this project
However, I can build in command line via brunch, mm, mmm, etc.
I have to fix these issues, because anytime I add something in a string.xml file, R.java is not updated as the project can't be built.
u will have to add all the missing .jar files... else you have an option to just build an app after you compiled the whole rom with
Code:
mmm "project"
command
frapeti said:
u will have to add all the missing .jar files... else you have an option to just build an app after you compiled the whole rom with
Code:
mmm "project"
command
Click to expand...
Click to collapse
Thanks for your answer. Well yes I currently use mm or mmm commands to rebuild the package I am working on.
I wanted to know if there was a more comfortable option. Adding all the jar files is the way to go as you said.
I'll see if I can deal with that, otherwise I'll stay with mm and mmm command lines.
Hi all,
I'm trying to compile CM10.1 from source, but when trying to do a new repo sync I get this error:
Code:
fatal: duplicate project CyanogenMod/android_device_samsung_maguro in /home/nickamina/android/cm10.1/.repo/manifest.xml
Can anybody suggest what the problem is here? Thanks
Final bump.
Nickamina said:
Hi all,
I'm trying to compile CM10.1 from source, but when trying to do a new repo sync I get this error:
Code:
fatal: duplicate project CyanogenMod/android_device_samsung_maguro in /home/nickamina/android/cm10.1/.repo/manifest.xml
Can anybody suggest what the problem is here? Thanks
Click to expand...
Click to collapse
The Project is duplicated 2 times in default.xml
mithun46 said:
The Project is duplicated 2 times in default.xml
Click to expand...
Click to collapse
Stumbled on this looking for a resolution for this same error with my Nexus 5 Kernel. Only problem is my default.xml does not have a duplicate entry. If I remove the entry altogether from the default.xml and repo sync the Kernel is missing. If I start a build though it will first go and download the missing kernel from github. My guess is somewhere in either device or vendor being the N5 is an officially supported device there is a call to add the package to repo as repo sync in my case will only brake after the source has been compiled.
Hello everybody,
I want to flash a custom kernel to my Galaxy 5 GT-I5500. However, I haven't managed to locate the proper *_defconfig file for my device.
I have also downloaded kernel source from Samsung Open Source Release Centre
Here is the list of configs been found at: /kernel/arch/arm/configs
Code:
acs5k_defconfig
acs5k_tiny_defconfig
afeb9260_defconfig
am200epdkit_defconfig
ams_delta_defconfig
assabet_defconfig
at91cap9adk_defconfig
at91rm9200dk_defconfig
at91rm9200ek_defconfig
at91sam9260ek_defconfig
at91sam9261ek_defconfig
at91sam9263ek_defconfig
at91sam9g20ek_defconfig
at91sam9rlek_defconfig
ateb9200_defconfig
badge4_defconfig
bcmring_defconfig
callisto_rev00_defconfig
callisto_rev03_defconfig
cam60_defconfig
carmeva_defconfig
cerfcube_defconfig
cm_x2xx_defconfig
cm_x300_defconfig
colibri_pxa270_defconfig
colibri_pxa300_defconfig
collie_defconfig
corgi_defconfig
cpu9260_defconfig
cpu9g20_defconfig
cpuat91_defconfig
cronin_rev00_defconfig
csb337_defconfig
csb637_defconfig
da830_omapl137_defconfig
da850_omapl138_defconfig
davinci_all_defconfig
ebsa110_defconfig
ecbat91_defconfig
edb7211_defconfig
em_x270_defconfig
ep93xx_defconfig
eseries_pxa_defconfig
europa_rev02_defconfig
ezx_defconfig
footbridge_defconfig
fortunet_defconfig
h3600_defconfig
h5000_defconfig
h7201_defconfig
h7202_defconfig
hackkit_defconfig
integrator_defconfig
iop13xx_defconfig
iop32x_defconfig
iop33x_defconfig
ixp2000_defconfig
ixp23xx_defconfig
ixp4xx_defconfig
jornada720_defconfig
kafa_defconfig
kb9202_defconfig
kirkwood_defconfig
ks8695_defconfig
lart_defconfig
loki_defconfig
lpd270_defconfig
lpd7a400_defconfig
lpd7a404_defconfig
lubbock_defconfig
lusl7200_defconfig
magician_defconfig
mahimahi_defconfig
mainstone_defconfig
mini2440_defconfig
msm7627_defconfig
msm7627-perf_defconfig
msm7630_defconfig
msm7630-perf_defconfig
msm8655-sr_defconfig
msm8660-chromeos_defconfig
msm8660_defconfig
msm_defconfig
mv78xx0_defconfig
mx1ads_defconfig
mx1_defconfig
mx21_defconfig
mx27_defconfig
mx31pdk_defconfig
mx3_defconfig
n770_defconfig
n8x0_defconfig
neocore926_defconfig
neponset_defconfig
netwinder_defconfig
netx_defconfig
nhk8815_defconfig
ns9xxx_defconfig
omap_2430sdp_defconfig
omap_3430sdp_defconfig
omap3_beagle_defconfig
omap3_evm_defconfig
omap3_pandora_defconfig
omap_4430sdp_defconfig
omap_apollon_2420_defconfig
omap_generic_1510_defconfig
omap_generic_1610_defconfig
omap_generic_1710_defconfig
omap_generic_2420_defconfig
omap_h2_1610_defconfig
omap_h4_2420_defconfig
omap_innovator_1510_defconfig
omap_innovator_1610_defconfig
omap_ldp_defconfig
omap_osk_5912_defconfig
omap_perseus2_730_defconfig
omap_zoom2_defconfig
onearm_defconfig
orion5x_defconfig
overo_defconfig
palmte_defconfig
palmtt_defconfig
palmz71_defconfig
palmz72_defconfig
pcm027_defconfig
picotux200_defconfig
pleb_defconfig
pnx4008_defconfig
pxa168_defconfig
pxa255-idp_defconfig
pxa3xx_defconfig
pxa910_defconfig
qil-a9260_defconfig
qsd8650a_defconfig
qsd8650a-perf_defconfig
qsd8650_defconfig
qsd8650-perf_defconfig
realview_defconfig
realview-smp_defconfig
rpc_defconfig
rx51_defconfig
s3c2410_defconfig
s3c6400_defconfig
s5pc100_defconfig
sam9_l9260_defconfig
shannon_defconfig
shark_defconfig
simpad_defconfig
spitz_defconfig
stmp378x_defconfig
stmp37xx_defconfig
swordfish_defconfig
sx1_defconfig
tct_hammer_defconfig
trizeps4_defconfig
u300_defconfig
usb-a9260_defconfig
usb-a9263_defconfig
versatile_defconfig
viper_defconfig
w90p910_defconfig
xcep_defconfig
yl9200_defconfig
In my view europa_rev02_defconfing might be the correct option but I am not totally sure.
Thanks in advance
hi,i have to rebuild the source code for samsung galaxy core mobile ,i download the jellybean code and i try to rebuild , what is the target product name for samsung galaxy core and how i add the target device name in repo manifeast file , please help me , thank u