Database Develop

ROM Building Starter Guide?

Considering the state of flux we are in with the roms, I think it would be really kewl for one of the guys to cook up a quick rom building guide. The main objective would be to allow user to replicate the rom build of their own accord. Many projects have taken the "you build it" approach to avoid the pitfalls of distributing closed source.
Look at something like Microsoft Core Fonts in linux. No distribution will ship with the fonts, but they all provide a package, even gnu pure Debian, that will pull the exe files from the web and unpack/install them for you. Same thing goes for flashplayers.
If someone would make a script/guide for making saayyy Cyanogen 4.0.4, by pulling the source from google, adding a modpack, and compiling on their own machine, then Cynan and the other would be clear from any wrong doing. Leave it to the community to distribute and get the roms out. Bittorrent/newsgroups/whatever, they can't stop us all, and they dare not pull a RIAA to hunt people down.
I think its something that maybe worth considering. The stuffer methods are great, but I would personally like to be able to build the rom as it should be, with all the fixings.

One
http://www.johandekoning.nl/index.php/2009/06/07/building-android-15-build-environment/
Two
http://github.com/cyanogen/android
three
http://source.android.com/download
you can add the other junk by following guides on the forums here, or pushing your own apps etc...

Thanks for the clear and concise answers. The first site has some very detailed info. I will give it a go, the Kitchen Rom Builder cooker back from my wizard days has me spoiled, but this looks pretty straight forward I just needed some direction.

helfrez said:
Thanks for the clear and concise answers. The first site has some very detailed info. I will give it a go, the Kitchen Rom Builder cooker back from my wizard days has me spoiled, but this looks pretty straight forward I just needed some direction.
Click to expand...
Click to collapse
http://www.jukie.net/~bart/blog/20090830174551 this one helps out too, but the manifest from cyanogen's github is out of date, it's 4.1 at time of writing this.

This is posted in the wrong area
as post like this are every week

jdk5 is no longer available for download on 9.10 x64 systems. Anyone know of a way around this?

Couldnt you add one of the older repositorys and add it that way?
Its one of the reasons i dont use the x64 build, too many incombatabilitys.
You could always vmware an x86 machine

Yea, I'm just now building a virtualbox x86 machine. I'm going to strip it down to essentials and then install everything needed for android building.

[Q] Explanation of Android Source Tree?

I have started looking at the sources of Android (the main source tree of the operating system not the Android project that opens up in Eclipse) and was able to successfully compile it for my N1. However, I was wondering if there is tutorial out there that tells provides an overview of the source tree. If someone was not involved in embedded development, how does one go about understanding the source tree?

Where it concerns the apps, the tree is pretty much straightforward. The rest is mostly understandable by names, but I don't know if there's any guide out there. I'd like to know too.

Oops.. sorry. I was not talking about application development. I have some experience with that. I am talking about the sources we checkout using git. I hardly have any experience with compiling code for embedded devices so I was looking into what each folder does. For instance, frameworks, libcore, vendors etc.

Big part of the sources in git repo are system apps - that's what I've meant.
Unfortunately, I don't have experience with system side of things.
vendors - collection of scripts with settings for each phone of each vendor (compilation settings, switches, etc).

i looked for the same thing when i first looked at the github tree, it was a bit overwhelming. no walk thru exists that i know of. i just learned to search each branch from the main page, i.e. the msm family for qualcom cpu phones, the samsung kernel, etc. wish it was a bit clearer.

Thanks! I am sure the community would be interested in such a documentation except that it will be terrible if I start writing it though I can make an initial attempt in doing so. I will see if xda has a wiki where I can put this stuff. But please do let me know if XDA provides us with such a wiki already.
EDIT: Never mind. I found the wiki here. I will try to fit it somewhere.

Parts of honeycomb now in AOSP

I haven't checked out this code yet but it seems that the "GPL and LGPL bits" of honeycomb have been added to AOSP. I'm sure some of you will be excited to look through it.
Check out these posts.
http://groups.google.com/group/android-building/browse_thread/thread/b732d8cd82695ce1?pli=1
http://blog.alsutton.com/2011/04/12/android-honeycomb-source-drop/

Can any devs put into relatively plain english what this release means in terms of proper Honeycomb ROM development?

arrjaytea said:
Can any devs put into relatively plain english what this release means in terms of proper Honeycomb ROM development?
Click to expand...
Click to collapse
I can't say for sure, but I got so excited I nearly spilled my drink.

I'm on my phone now so can't really look at the code, but in general any GPLed parts of hc that was distributed as a binary (kernel, ALSA, etc) are required to be accompanied by source upon request. This is a tiny portion of android as a whole however.
Again,can't look at this in detail but sounds like google is just complying with their GPL obligations... as for what they released in particular, git should tell ya..
Update: realized that I should have been clear what the GPL is. Its an open source license... wikipedia should have more info, but wanted to add that just in case anyone may not have heard of it.

I finally finished downloading it
doesn't really seem to be anything interesting..

How about this? Has this been discussed already? Asus releases Google Android Honeycomb source code

xgunther said:
How about this? Has this been discussed already? Asus releases Google Android Honeycomb source code
Click to expand...
Click to collapse
I believe this is referring to the Asus kernel source, which is 100% useless to our tablet.

ScottyNuttz said:
I believe this is referring to the Asus kernel source, which is 100% useless to our tablet.
Click to expand...
Click to collapse
yeah that is, but the OP is talking about the ASOP. I have no idea what is included.

So what's the word? Is the GPL code that was released of any use to the Nook Color and optimizing it for Honeycomb? Or is it just stupid stuff that we already knew or had worked around?

Neither..
Sent from my Desire HD using XDA App

It has been in the repository since January. It's really just a snapshot of where they were in case they mess up the main branch they're working on, and only specific parts of it. Nothing important of use to us.

So basically this is "non-news"?

Exactly, old news.
https://twitter.com/#!/jbqueru/status/57875038942138368

[SOURCE] KERNEL Source Released!

Well, this is sure an interesting email that I just received back from LG's support team, when asked about the kernel sources.
The rep seems to know what I'm asking for-- but for whatever reason denies my request (which is reasonable by the GPL).
Anyway, full email here:
Dear Tyler,
Thank you for inquiring of LG Electronics.
We do apologize for any inconvenience this may have caused.
We would be more than happy to provide the Kernel source which is: 2.6.32.9-PERF
[email protected] #1
Unfortunately, the source will not be released.
Please feel free to contact us if you have any additional questions or concerns. Thank you again for contacting LG Electronics.
Maya C
E-Mail Administrator
Customer Interactive Center
LGEAI
-----------Original Customer Inquiry------------
Received Date : 06/22/2011 02:03 10
The type of inquiry : Others
Product/Model No. : CDMA/LGVS910
As per the GPL, is there somewhere that I can find kernel sources for the LGVS910?
It is not on your LG Open Source page, is there an alternate location I should look?
If there is no public place to download the source, what is your timeline for releasing it?
Thank you!
Click to expand...
Click to collapse
Hmm, should I quote the GPL back to them, or try asking nicely again?

thecubed said:
Well, this is sure an interesting email that I just received back from LG's support team, when asked about the kernel sources.
The rep seems to know what I'm asking for-- but for whatever reason denies my request (which is reasonable by the GPL).
Anyway, full email here:
Hmm, should I quote the GPL back to them, or try asking nicely again?
Click to expand...
Click to collapse
Yeah, that's an invalid response if the code is GPLed.

I'm not quite sure why or how they think they can get away with that, considering the source for all their other phones is available here: http://www.lg.com/global/support/opensource/opensource.jsp
Even the tmobile g2x has it's sources posted...
What I wonder is if they're just saying that _this_ kernel's sources won't be posted.
Maybe they're embarassed? Hope not, because I demand this kernel's source!

thecubed said:
I'm not quite sure why or how they think they can get away with that, considering the source for all their other phones is available here: http://www.lg.com/global/support/opensource/opensource.jsp
Even the tmobile g2x has it's sources posted...
What I wonder is if they're just saying that _this_ kernel's sources won't be posted.
Maybe they're embarassed? Hope not, because I demand this kernel's source!
Click to expand...
Click to collapse
They may be protecting Microsoft's interests (they think) or they had a side agreement with Netflix. Either way, they can't deny a derivative work. It doesn't work that way. (at least I think? I haven't read the most recent GPL in a while...lol)

majorpay said:
They may be protecting Microsoft's interests (they think) or they had a side agreement with Netflix. Either way, they can't deny a derivative work. It doesn't work that way. (at least I think? I haven't read the most recent GPL in a while...lol)
Click to expand...
Click to collapse
As far as my understanding of the GPL, any code they modify that is released as GPL must be released as GPL also.
So, they (CodeAurora) modified Linux-2.6.32.9, which is GPL, hence they must release any modifications.
Where it gets grey is in terms of proprietary modules. However, if it's compiled into the kernel, I understand that it must also be released as source also. The only way to avoid that is to use module loading and taint the kernel, which then does some other license-protecting stuff.
Damn, the GPL is complicated.
EDIT: I'm in LG Live Chat right now asking...

thecubed said:
As far as my understanding of the GPL, any code they modify that is released as GPL must be released as GPL also.
So, they (CodeAurora) modified Linux-2.6.32.9, which is GPL, hence they must release any modifications.
Where it gets grey is in terms of proprietary modules. However, if it's compiled into the kernel, I understand that it must also be released as source also. The only way to avoid that is to use module loading and taint the kernel, which then does some other license-protecting stuff.
Damn, the GPL is complicated.
Click to expand...
Click to collapse
Yeah, it gets more so every year, and depending on what version of GPL is in use depends on what the specifics are. I'd have to say even if their module loading taints the kernel, they should be able to (read: must) release the modified source prior to the dirty side mods.

if they are anything like samsung, they will sit on it for as long as possible.

LG Chat:
Jorge: Hello Guest. Welcome to LG Electronics! How may I provide you with excellent service today?
Guest: Hello, I was wondering when the kernel sources for the LGVS910 would be posted? Specifically kernel 2.6.32.9-PERF [email protected]
Jorge: unfortunately we do not have a date
Guest: Any reasonable estimate?
Jorge: I will love to say a date but we do not have information.
Guest: Okay, thank you.
Click to expand...
Click to collapse
Well, maybe the person in the email was misinformed, or just plain ol confused...

thecubed said:
LG Chat:
Well, maybe the person in the email was misinformed, or just plain ol confused...
Click to expand...
Click to collapse
Or... the current rep is stalling? Why would there be a delay? Shouldn't the GPLed kernel be available immediately at request?
I'm going to assume it won't be too long before they release 2.3 for this phone.

majorpay said:
Or... the current rep is stalling? Why would there be a delay? Shouldn't the GPLed kernel be available immediately at request?
I'm going to assume it won't be too long before they release 2.3 for this phone.
Click to expand...
Click to collapse
Me too.
To give LG some benefit of the doubt, it is possible they just don't want to put the work into it, considering they may have something brand new around the corner.
But-- what I worry about is OTA locking down the phone.... hence my want/need for sources, just in case.

thecubed said:
Me too.
To give LG some benefit of the doubt, it is possible they just don't want to put the work into it, considering they may have something brand new around the corner.
But-- what I worry about is OTA locking down the phone.... hence my want/need for sources, just in case.
Click to expand...
Click to collapse
Yes, and I've seen 2.3 turn otherwise perfectly good phones into piles of poo, so I definitely want a way back if that happens here. Resource requirements and overall overhead seems to increase 10 fold on 2.3

Come to think of it... I just realized I should be really worried for the next OTA update...
Now, those of us with clockwork need not worry, since it just will say "invalid signature" when LG's updates try to install (since clockwork is signed with the testkeys from cyanogenmod). Once it says "invalid signature" you'd just click "reboot now" and grab the update file from /cache .
But still... the unknown is killing me!

Isn't that exactly what happend with the thunderbolt?

thecubed said:
Come to think of it... I just realized I should be really worried for the next OTA update...
Now, those of us with clockwork need not worry, since it just will say "invalid signature" when LG's updates try to install (since clockwork is signed with the testkeys from cyanogenmod). Once it says "invalid signature" you'd just click "reboot now" and grab the update file from /cache .
But still... the unknown is killing me!
Click to expand...
Click to collapse
Well, we can work on the assumption that it's never coming... because you know how Verizon is about releasing updates.
However, in the meantime LG needs to cough up the goods per legal requirement. It could all be part of a greater conspiracy, ha! Release the next batch of goods and destroy what had been previously done, THEN release the source code to the first kernel.

So in other words when we get 2.3 they'll unsuspectingly give us everything we need for custom roms and kernels once one of us extracts it from the cache...
Little Buddy Sr.

MXFrodo195 said:
So in other words when we get 2.3 they'll unsuspectingly give us everything we need for custom roms and kernels once one of us extracts it from the cache...
Little Buddy Sr.
Click to expand...
Click to collapse
Not likely... They'll release the source for 2.2 to the public when 2.3 gets pushed. We're helping them find all the holes they left in 2.2.

I guess the phones work differently. I have only experienced OTAs on the original droid. In that phone's case; once you got the OTA and the phone rebooted, it would reboot to clockwork. If you wanted to apply the OTA you just selected "Update from SD" (or something like that). If you didn't you just rebooted the phone. Now granted that it will keep on bugging you that you don't have the latest until you trick it by changing the signature (on one of the prop files I believe it was - not sure if it still works that way).

Someone please let me know what I need to say over live chat or by email ill send or talk with them. Nothing to lose and alot to gain. And several cold beverages of my choice will help. I'm just not in the know on open sorce code etc.... I want to help.

From the GPL:
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to “keep intact all notices”.
c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
Click to expand...
Click to collapse
As long as they hold out, they are in violation of the GPL. It should be noted, however, that they aren't the only ones in the Android world doing this. It has been the discussion hot topic for a lot of Android device manufacturers.
It could all be nothing, and they may not have "gotten around to it" yet. They have released all their previous and current works. It does question why this phone is on hold, and I'd venture to guess (but could be completely wrong) that it revolves around Microsoft protecting their digs in this machine.

The full thing is here if you want to review it...
http://www.gnu.org/licenses/gpl.html

[Q] Kernels and related

I don't know if this is the right place to ask but I think I'll post here instead of development. I want to get into making my own slightly tweaked kernels but I really know nothing about whets where in the repository (like what file I would look in for clocks or voltages). I was just wondering if someone could point me toward some documentation so I can at least have a but of an idea. Thanks!

Developing anything is pretty complicated without some codding skills so I would advise against trying to code your own kernel although if you want to I can't stop you but in your position I would have posted in android development section you may get faster results.

I have experience in coding in c++, html, some assembly, wrote a very basic bootloader that doesn't really do much for a pc. I'm just looking to make some minor changes. (clocks or voltages)

# include <iostream>
using namespaces std;
void main()
{
cout <<"Well in that case I guess you could but like I said you'll probably get more responses in the android development section then nexus one Q&A.\n\nBTW I'm no expert in c++ just wanted to do this as a little joke all I know are the basics ";
cin.get();
}
NOTE: I know code is not supported in most forums so if a mod wants to delete this feel free it was just a joke so.

Very nice but unfortunately wouldn't compile in my compiler thanks to microsoft requiring include stdfax or whatever it is that I have to add up there with precompiled headers.... A pain but I never really learned gcc and its rules
Will post in dev section thanks for the suggestion!

Oh well I just noticed something and I'm going to guess that's why it didn't compile for you I made a typo up there it's not "namespaces" it's "namespace".

meltbox360 said:
I have experience in coding in c++, html, some assembly, wrote a very basic bootloader that doesn't really do much for a pc. I'm just looking to make some minor changes. (clocks or voltages)
Click to expand...
Click to collapse
All you have to do is browse some of the repositories here in the dev section. Click the GitHub link to pershoot or intersects repository. Then go to the kernel project/source and click "commits" at the top. Look thru each commit to get an idea of what's going and being changed in the kernel. The good stuff will be from months ago so you'll have to keep going back far thru the commits to find the significant changes.
Then setup your own build environment. Cyanogen wiki has a step by step tutorial guide that's straight forward and rather easy to get going.
When done that, just practice making some tiny code changes to the kernel, something that interests you, and try to compile it. You'll prob get an error so tweak it till it compiles with no error, then flash it to your device and see if it works.
It's fun to do and you can get setup pretty quickly with all the info available to us.