I’ve been working on getting my source trees on Github in shape so that anyone can build a basic CyanogenMod system. Some small parts still need added but things are looking good there.
I’m also continuing to examine the backup/restore option for the proprietary bits necessary to operate your device, so I can simply ship open-source code only. I believe this is well within the license and the spirit of the ADP1 and ION devices.
A lot of people are helping to work many of these issues out, notably the guys from Google (Dan and JBQ) who manage the open-source project. Some great discussion and initiatives are happening like the Open Android Alliance and the Replicant projects. As much as it sucks to be sort of the “fall guy” for this, I can take it. Let’s fix the problems and move on.
Expect more from me by the weekend!
http://www.cyanogenmod.com/home/just-a-quick-update
keep it running! =)
That's Greeeeat!
I take my hat off to you sir!.
Excellent News...
it's nice to get updates, but i'm sure most of us are smart enough to visit the site directly for his updates or check his twitter.
no need to open new threads for this. -.-
thats the way more donating to you
As long as a Rom doesn't include googlebits it should be fine on google code right? It would be nice to use for bug tracking and a quick downloading service.
Doubt it, since I imagine that a lot of bits are closed-source and harvested from existing ROM dumps and so forth.
I believe quietblongs was the only dev here that actually built his roms from source. With that said. I mean the entire thing except some libs. But I'm not sure if anyone else is doing this. I think most of the aosp roms we have are ports with maybe compiled frameworks from source. Again that's just a guess.
But speaking of quietblongs... I wish he'd come back and make us a bad ass 2.1 aosp build.(a hint to quiet to build us another bare bones build)
I have a "generic" 2.1 AOSP build. The problem is getting the HTC vendor/oem stuff incorporated. I have tried following Cyanogen's lead with his "vendor overlay" in git, also borrowing from Lox's GSM hero stuff, but when I build it that way ((via "lunch htc_heroc-eng") I still end up needing to manually copy the proprietary files one-by one into build to get a resulting system.img. In other words, I'm missing a script that should do this during the build. Since nobody seems to be building for CDMA hero (I find directions for dream, magic, and nexus only), I basically don't trust my result enough to upload for others.
Building 2.1 as "generic-eng" is trivially easy, we could have a "nightly build" setup if we wanted. But getting the vendor stuff properly incorporated into the build (and having the build use these files to generate its source) is not a clear process to me yet. I'm learning but it takes time I don't always have.
On a side note, maybe someone could comment on whether a fresh build with the vendor stuff could/would solve ongoing issues like the camera or whether that is a 2.7/2.9 kernel issue that needs a backport.
5tr4t4 said:
I have a "generic" 2.1 AOSP build. The problem is getting the HTC vendor/oem stuff incorporated. I have tried following Cyanogen's lead with his "vendor overlay" in git, also borrowing from Lox's GSM hero stuff, but when I build it that way ((via "lunch htc_heroc-eng") I still end up needing to manually copy the proprietary files one-by one into build to get a resulting system.img. In other words, I'm missing a script that should do this during the build. Since nobody seems to be building for CDMA hero (I find directions for dream and magic only), I basically don't trust my result enough to upload for others.
Building 2.1 as "generic-eng" is trivially easy, we could have a "nightly build" setup if we wanted. But getting the vendor stuff properly incorporated into the build (and having the build use these files to generate its source) is not a clear process to me yet. I'm learning but it takes time I don't always have.
On a side note, maybe someone could comment on whether a fresh build with the vendor stuff could/would solve ongoing issues like the camera or whether that is a 2.7/2.9 kernel issue that needs a backport.
Click to expand...
Click to collapse
Yeah u will always need proprietary files to build aosp. That's what vendor is for. I've started gathering and trying to setup a community vendor for cdma heros. But just been to busy to finish. Will try soon though an put it on github for all to use.
But as for camera drivers and stuff like that. Ur gonna find that making libcamera build isn't gonna happen as of yet in 2.x aosp. Because it is broken as of the moment and doesn't make. The only solution to gettin camera into an aosp build is to use the libcamera and other camera libs from mine and Flipz HTC Rom. But even then ur gonna need a compatible kernel camera driver to work with it. As of now we haven't got that working fully. But also even once we get the driver working ur gonna have issues in aosp builds with camera as the gsm hero devs have found. As it stands now the aosp camera doesn't fully support our camera. Leaving them left with a 3m camera and I believe no video. It seems that HTC did some extra work in their camera.apk to finish up and give full support for our camera. The problem with that and aosp is like most HTC apks work in and with a HTC modified frameworks. So it goes deep into the framework.jar and many other frameworks files. I won't say it can't be hacked in some how but I will say it won't be easy. But if u manage to pull it of please share because a lot of devs have tried and haven't managed to pull it off as of yet.
Maybe you can point me in the right direction. Attached is my "vendor overlay" attempt. In the first case it's just Lox's stuff for hero with "heroc" in all the right places. The "extract" script is mine, modified by me given Cyanogen's nexus overlay example.
If you can create a git of a proper overlay, that would be great. Even if, as you say, it doesn't get us all the way to a working AOSP ROM.
Lox's language in his extract script is like Cyanogen's in his git repo, ie "who the hell knows if this is right, just guessing". So in that spirit, here is my attempt: a little experience mixed with vendor hatred mixed with voodoo
Feel free to correct me as you can, I would be grateful for a leg up from someone who has been at this longer.
P.S. I can't believe I had to "zip" up a tar.gz tarball to get it to attach to a dev forum (Invalid file). Man, I'm getting old.
P.S.S The included "kernel" file is a zImage I built from your toastcgh 2.7 sources in git. The wlan.ko was built against that...I should double-check that fact...
Ah well, maybe when they redo the forums here they'll think about bug tracking etc but I doubt it.
I did build my aosp rom from source, just built it using the gsm hero's vendor tree, made small adjustments to it for the heroc files. so yea, my rom is from google code to answer the OP's question.
darchstar said:
I did build my aosp rom from source, just built it using the gsm hero's vendor tree, made small adjustments to it for the heroc files. so yea, my rom is from google code to answer the OP's question.
Click to expand...
Click to collapse
EDIT: OHH, I completely misread your thread title, I probably could use google code for my aosp rom to track bugs
darchstar said:
EDIT: OHH, I completely misread your thread title, I probably could use google code for my aosp rom to track bugs
Click to expand...
Click to collapse
Right, I think we all misread it, I believe he was asking why we don't host our code somewhere, like Google Code, with a real bug tracking system, versioning controls, etc. He's got a great point, actually. It would be very nice to have a shared AOSP space, somewhere to see the files and track the issues and changes. ROM development based on AOSP could go on as usual on XDA with that base.
5tr4t4 said:
Right, I think we all misread it, I believe he was asking why we don't host our code somewhere, like Google Code, with a real bug tracking system, versioning controls, etc. He's got a great point, actually. It would be very nice to have a shared AOSP space, somewhere to see the files and track the issues and changes. ROM development based on AOSP could go on as usual on XDA with that base.
Click to expand...
Click to collapse
I got it
The issue is that Google Code won't allow you to host anything you don't have the right to distribute.
5tr4t4 said:
Right, I think we all misread it, I believe he was asking why we don't host our code somewhere, like Google Code, with a real bug tracking system, versioning controls, etc. He's got a great point, actually. It would be very nice to have a shared AOSP space, somewhere to see the files and track the issues and changes. ROM development based on AOSP could go on as usual on XDA with that base.
Click to expand...
Click to collapse
It would minimize on duplicate bug reports at least.
jonnythan said:
I got it
The issue is that Google Code won't allow you to host anything you don't have the right to distribute.
Click to expand...
Click to collapse
Understood, but the proprietary stuff can be pulled from the phone and/or from official releases for other HTC devices given the right script. That's why we need the vendor overlay.
I suppose the follow up question is, "why not just contribute to Android's AOSP core code in git, why create a forked AOSP repo?". That might be right, but we still need the overlay to pull the right files from the device. Perhaps taostcfh or quietblongs or darchstar already have this stuff ready and I'm just late to the game (probably ). Fine, I'd love to see that work so I can help out where possible.
<mini-rant>
This OEM/vendor crap really sucks...should I just repeat what has been said everywhere (and knocked down for very sound business reasons): Google should have released Android under GPL.
</mini-rant>
5tr4t4 said:
Right, I think we all misread it, I believe he was asking why we don't host our code somewhere, like Google Code, with a real bug tracking system, versioning controls, etc. He's got a great point, actually. It would be very nice to have a shared AOSP space, somewhere to see the files and track the issues and changes. ROM development based on AOSP could go on as usual on XDA with that base.
Click to expand...
Click to collapse
Exactly, thanks.
What keeps one of us from leasing a server to share for our (XDA) own CVS, bug-tracking and compiling?
ffolkes said:
What keeps one of us from leasing a server to share for our (XDA) own CVS, bug-tracking and compiling?
Click to expand...
Click to collapse
The fact that someone has to pay for it.
jonnythan said:
The fact that someone has to pay for it.
Click to expand...
Click to collapse
I've got a server but I'm not too familar with CVS, if anyone wants to lend a hand...
ffolkes said:
I've got a server but I'm not too familar with CVS, if anyone wants to lend a hand...
Click to expand...
Click to collapse
I have one too, but I would advocate for something more public, like git or sourceforge or Google Code, XDA, etc. You would want to make sure that you were gaining sharing capabilities and not just isolating yourself...either from upstream improvements or from other community stuff here and on other forums. A thousand people sharing is better than 10-20 people with a server, IMHO XDA has already proven that.
Plus, getting a development server going with all of the niceties of CVS et al is not easy...and there are ready-made solutions already available. None of this addresses jonnythan's point that some of this development is in legal limbo...what happens when someone , even by accident, pushes the google bits onto your public server?
...maybe you would get a cease and desist letter and become famous, LOL.
5tr4t4 said:
...maybe you would get a cease and desist letter and become famous, LOL.
Click to expand...
Click to collapse
Someone needs to combine the power of a forum with the legal protection of a public download site and the bug tracking of google code.
Apparently, I'm too lazy to code that all myself
I've been trying to either find or if I have to develop a tf101 kernel that has a standardized /sys/.. vdd_levels interface for changing under/overvolting and also for seeing what it is set to easily.
Of the ~4 tf101 kernel developers I can find, it appears that only Blades has touched on it, but maybe not uploaded those changes to his github. I would be pretty happy to just use anyone's git as a starting point but also glad to use standard source as a starting point and add the vdd_levels to it.
To do that I'd either need a little help, or a glance at where the missing pieces that I still haven't coded go. I figure that if there are 4 known developers that there must be 10 more that are more like me and don't want to maintain or publish any binaries.
I'd be happy to keep up a github that is in working order with all the voltage + kernel code but have no interest in maintaining the kernel itself. (hey, I've seen those threads.. )
The reason I don't just go over to say, the htc incredible section and use one of the many kernels that do this and are in github already, is because this is specific to board types and that's a piece I don't know enough about yet to transfer even if I'm staring at it. I'd need to see or hear about how to do that piece.
Anyone that can help, thanks much in advance,
Mick
I am new to programming and understanding the concepts behind it and I was wondering if anyone could point me in the direction to some source code for the excellent ROM's I have seen on here or any applications which have been developed for the Android OS? The reason for this request, I need to see the code to understand what's going on behind the scenes to make a ROM/application function. I figure if I am able to study the code, I may actually be able to understand finally how to develop either an application or ROM. Thanks in advance. :good::good::good:
LivioDoubleFang said:
I am new to programming and understanding the concepts behind it and I was wondering if anyone could point me in the direction to some source code for the excellent ROM's I have seen on here or any applications which have been developed for the Android OS? The reason for this request, I need to see the code to understand what's going on behind the scenes to make a ROM/application function. I figure if I am able to study the code, I may actually be able to understand finally how to develop either an application or ROM. Thanks in advance. :good::good::good:
Click to expand...
Click to collapse
Most of the ROM's that are built from source either use AOSP source code which the source code can be found here, Cyanogenmod source code which can be found here, AOKP source code which can be found here, or Paranoid Android source code which can be found here, or the ROM's use a combination of all these listed and cherrypick there favorite features from each while adding there own. When it comes it seeing what other changes have been made by the developer the easiest way to look at the source code is looking at each developers github profile if available which can be accessed by usually searching for there username on github or clicking on there username here on XDA and selecting the "View Github profile" option. Let me know if you still have questions .
Thank you shimp208 for your expedient response on this issue. I will definitely be checking out the links you have provided and with hopes, gain a deeper understanding of the Android OS to become a developer myself.
LivioDoubleFang said:
Thank you shimp208 for your expedient response on this issue. I will definitely be checking out the links you have provided and with hopes, gain a deeper understanding of the Android OS to become a developer myself.
Click to expand...
Click to collapse
I wish you the best of luck man, these guides are also definitely worth taking a look for getting started with a variety of ROM development aspects http://xda-university.com/as-a-developer.
Sent from my SCH-I535 using xda premium
Thanks a lot
shimp208 said:
Most of the ROM's that are built from source either use AOSP source code which the source code can be found here, Cyanogenmod source code which can be found here, AOKP source code which can be found here, or Paranoid Android source code which can be found here, or the ROM's use a combination of all these listed and cherrypick there favorite features from each while adding there own. When it comes it seeing what other changes have been made by the developer the easiest way to look at the source code is looking at each developers github profile if available which can be accessed by usually searching for there username on github or clicking on there username here on XDA and selecting the "View Github profile" option. Let me know if you still have questions .
Click to expand...
Click to collapse
Thanks For Help i too had same Que.
Thank you very much :good: