Database Users

IDEA : git repository

I find that many developers are working on porting android 2.1 or 1.6 vanila and it result in much duplicated work.
I was thinking of maybe setting up 2 git repositories one for 1.6 AOSP and 2.1 AOSP on which everyone can work on, improve and fix bugs.

lgstoian said:
I find that many developers are working on porting android 2.1 or 1.6 vanila and it result in much duplicated work.
I was thinking of maybe setting up 2 git repositories one for 1.6 AOSP and 2.1 AOSP on which everyone can work on, improve and fix bugs.
Click to expand...
Click to collapse
That's a nice idea, im begging to look after a site to host the repositories...

We can use github for hosting or any other site. I'm interested in looking after the repositories too.
A centralized effort will always be better then a fragmented one.

lgstoian said:
We can use github for hosting or any other site. I'm interested in looking after the repositories too.
A centralized effort will always be better then a fragmented one.
Click to expand...
Click to collapse
If you have alot of money, then Github would be ok... But it costs $50/month for the package that is minimum for two sets of android source code...

Know any places where we can host the code?

Mod. edit: not dev related, moved to general

Gitorious and Github are both free and unlimited for open source projects.

We can use sourcefordge too. The offer svn and git repositories. So what about it folks, who would be interested?

I would be interested in this...

I think we should open a project on sourcefordge for android 2.2 with the first task being to get the new kernel (2.6.32) working on the tattoo.

It could host the long awaited universal froyo upgrade
-------------------------------------
Sent via the XDA Tapatalk App

lgstoian said:
I think we should open a project on sourcefordge for android 2.2 with the first task being to get the new kernel (2.6.32) working on the tattoo.
Click to expand...
Click to collapse
That will be hard becuase the new kernel (2.6.32) is very big so we would need something like GRUB to boot it, from another partition than the boot partition...

If we disable enough modules the size should go down but that would mean it won't be universal any more.
There could be a regular version and a 'lite' version for Tattoo and older phones.

Wait wait wait.
I can play full divx movies smoothly so some seldom used modules could be stored on sd with no prob.
-------------------------------------
Sent via the XDA Tapatalk App

Release of 2.3 mean cyMOD?

just wondering because isnt that why they stop progress?

markawashington said:
just wondering because isnt that why they stop progress?
Click to expand...
Click to collapse
1. 2.3 has not been officially released for the Epic. We only have binary leaks, no source code.
2. The CM 7 team is waiting for the official release of 2.3 because the GPL requires Samsung to release the source code then.
The CM7 team needs the source code for the customized Epic kernel & drivers. They may need other source code poeces too.
tl:dr No, since they still do not have the needed source code.
Find more details here. http://forum.xda-developers.com/showpost.php?p=16147166&postcount=24

sources released on htcdev.com

htc have released source code at htcdev.com, including i have noted, a gingerbread update for desire. would these releases make it easier for hd2 android development?
it will be an interesting next few weeks

1. Wrong forum
2. Already posted on the main news page
3. Gingerbread for desire is released last week already but not the kernel source
4. Source codes were always there on the htcdev site, nothing new
Dont post things too fast m8, i know everyone is excited about the desire gingerbread rom and how it potentially can fix the graphic glitches on the sense roms (is'nt even sure it will be fixed).
Please correct me if i'm wrong i dont think there is much to develop anymore for our HD2's as there are android builds that run as fast as stable as any generic android device.
The only big thing i can imagine that still can be developed is true 720p recording and i dont know if the source code will help getting this to work. i'm not a dev

a dead man said:
would these releases make it easier for hd2 android development?
Click to expand...
Click to collapse
No, it's not a source code of Desire kernel but "only" upgrade Desire to Ginger.

a dead man said:
htc have released source code at htcdev.com, including i have noted, a gingerbread update for desire. would these releases make it easier for hd2 android development?
it will be an interesting next few weeks
Click to expand...
Click to collapse
thisa was posted yesterday and was in the wrong forum and you have done it again today, there is already 2 other threads about this going in Q&A
needs KERNEL source not the release of GB

I know this is a dead thread, but one question that has been on my mind. If a kernel can be compiled can't the kernel be decompiled to study the source code? Just a thought.

[email protected] said:
I know this is a dead thread, but one question that has been on my mind. If a kernel can be compiled can't the kernel be decompiled to study the source code? Just a thought.
Click to expand...
Click to collapse
Decompiled software is very hard to read, follow and understand. The "decompilation" process does not result in the original source code but in assembler code, which is big, ugly and meant for machines not people.

deviant007 said:
Decompiled software is very hard to read, follow and understand. The "decompilation" process does not result in the original source code but in assembler code, which is big, ugly and meant for machines not people.
Click to expand...
Click to collapse
Okay. Thank you for the answer.

One question guys, may be in the wrong thread but excuse me. I just wondering...HTC realesed upgrade for Desire some time ago, Is it that they are not yet published the source code does not break the rules of the General Public License (GPL)?

Ica Cream Sandwith?

Hi all, is possible upgrade to Android 4.0 version for Magic

cyanogen said:
We’ll be following up with a few minor releases [of CyanogenMod 7] and soon it will be time to start work on CM9!
Click to expand...
Click to collapse
Here's an answer - we can't probably get it until it's in CyanogenMod, and there's no promises that ICS will work on Magic/G1. So lets just wait until Google releases the source code and CM team can grab it - in the meantime, lets donate them some cash: http://forum.cyanogenmod.com/donate

kanttii said:
Here's an answer - we can't probably get it until it's in CyanogenMod, and there's no promises that ICS will work on Magic/G1. So lets just wait until Google releases the source code and CM team can grab it - in the meantime, lets donate them some cash: http://forum.cyanogenmod.com/donate
Click to expand...
Click to collapse
Thank you kanttii

Moved to General until the OP makes it happen.

Ice Cream Source Build?

Hi,
i know that the build would be slow as hell but has anyone compiled ICS for the G1? just for trying it ?
i would like to try it myself but i have no clue on how and from hat i`ve heard my computer would take ages to build it

It's done for droid eris, it can be ported to G1.
http://forum.xda-developers.com/showthread.php?t=1352170

Porting would be inefficient when it can be built from source.
Unfortunately I can't do neither
Sent from my GT-I9100 using XDA App

Ice Cream Sandwich Build Help
As soon as the source was released I was thinking about trying to build it for "old reliable" (my nickname for my old G1). I know it would be slow as mud but I still want to give it a try. Problem is I've never compiled the source of Android before so I would be going in blind. I've read the info at source.android.com so I have somewhere to start. If anyone has any other guides/tutorials on how to build Android for a device then I would be really appreciative. I'm a Computer Science major so don't be afraid to throw a little code at me either. I'll include the details of my phone below in case anyone needs it.
HTC Dream
SPL: HBOOT-1.33.2005 (DangerSPL)
Radio: 2.22.19.261
OS: CyanogenMod 6.1 (Android 2.2.1)

You can have a look at Terry' ezGingerbread thread. Here he explains what to do to compile his ezGingerbread from the sources. Principally compiling ICS is the same, but you need to exchange / modify the manifest to your needs.
Sent from my Gingerbread on Dream using XDA App

Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App

hyperspace290 said:
Thanks, I looked it up and it was really helpful. Just a couple of quick questions. Do you know how far from stock ezGingerbread is? What do you mean when you say manifest? When people port a new version to a new device how is it normally done?
Thanks for your help. If I manage to get anything useful I'll be sure to share it here first.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
It's almost stock, but there are some projects from CM included and some he cloned from CM or from other sites and manages them by himself. Details you can see it in his manifest.xml located in the .repo directory. The manifest defines, what projects are to be included and what branch you want to use for these projects.

You will not want my manifest for ICS (at least unless I make an ICS branch myself)
The reason is you will want to use the ICS git repos and not the GB git repos (original or cloned by me)
That said if you are new to building an android rom look at the structure using ezgb some, and build ezgb, then when you understand the structure clone ICS from aosp (see info on source.android.com) and create your own manifest from that including cloned git repos you need from ezgb with any addtl modifications required.
The first thing is:
* Git is the source control for all parts of android, however many (well over 200) git repos are used in ICS
* Repo is a tool (python script with plugins pulled from its own git repo) for maintaining all of the git repos used in an android build, and creating the true tree of repos needed for the work directoy.
* Manifest is a special git repository with default.xml (and sometimes other manifest xmls) used by the repo script to find all the projects other git repositories, as well as what branch/commit to checkout to the work directory.

Thanks for the advice guys. Glad to see the little G1 is still getting some love. I think I'll start by building ezGingerbread to get the handle on the build process for Android and at least get up to 2.3.
If anyone knows what kinds of modifications are normally needed for a port like this then I would appreciate the help. Is it normally just editing some config files or would I have to dive into the code? Thanks again.
Sent from my DROID3 using XDA App

Looks like someone has beaten me to the punch. Anyone interested shout go have a look at this thread: http://forum.xda-developers.com/showthread.php?p=19648827

not exactly.
that is a port from a source-build for the hero
but very close
looks like the dev is trying to make a source build for the dream.
you could contact him so you can work together

Really get the cm9 source, pull forward the dream/sapphire device trees from cm7 (or firerats port of that) and it ought to be alright.
There seems little in the way of true cm bits at current (sure to change soon) but most of the hardware backwards compatibility patches are alredy in cm9 from the looks of it.. for all I know this is a cm9 build since aosp has no hero device tree out of box.

I was going to reply to that thread but since I'm still considered new I can't post to development threads. I guess I will PM the dev later to let him know I'm interested in helping him out.
Why would you build for another device if the dream has built into AOSP? Doesn't make a whole lot of sense to me unless they flat out took out the board file in ICS but you could easily put it back by pulling it from an earlier revision.
Sent from my DROID3 using XDA App