Hello,
I have been following this thread: http://forum.xda-developers.com/showthread.php?t=1991320&page=1 where icoolguy1995 has managed to create a ROM for the Allwinner A13 tablet.
Unfortunately, like many ROMs, the source code is not immediately available for further development. Basically I signed up to this forum because I planned to ask him for the source code, but as I cannot post in the developer's forum, I cannot.
I also notice that this is a reoccurring theme with new ROMs posted on XDA - the source code is often missing, and I was wondering what people's thoughts on this issue were?
_______
user135
You could just PM the creator, you don't need to post in a certain thread to do that. This is the course of action that would make the most sense, anyway.
Sent from my Transformer TF101 using xda app-developers app
Depending on the base ROM there may not be source available. Only the kernel source is available as most stock ROMs are closed sourced.
Wayne Tech S-III
Related
Hi guys, I've been hiding out over on slate droid for a bit - I picked up a pandigital novel for free and I've been working on getting it to run things other than eclair. I have a working honeycomb port for it - woot - butttt pandigital refuses to release kernel source code for the device. velocity micro released a cookie cutter version of the same device and won't give up the kernel source either so heres the trouble - without a new kernel module honeycomb and gingerbread have no wifi.
Is it possible to compile a generic kernel module or a signed one for this kernel with no kernel source? Help please.
Maybe the full might of xda could get pandigital to fork over the source code but seeing as how we don't have a pandigital section demand for this is low here. I'm disgusted by the way these companies have been stealing open source software.
http://www.slatedroid.com/topic/23492-honeycomb-it-doesnt-run-very-well-on-my-novel-yet/
There's a link to the issue - I'm not sure if it's polite to link to another forum here - mods remove it if you like. That entire thread would be here on xda if we had a novel device forum
See u back at SLatedroid.
Sent from my X10i using XDA App
Hi,
Im new with android develoopment so please bear with a n00b. can someone guide me how to build ics rom using the source provided by samsung..
I have downloaded the original android ics source and samsung's source.. I can build the android source but I dont know how to plug in the samsung code. Unfrotunately, sammy's documentation is insufficient probably about 10 lines, just says to overwrite the android source and do a make. But when I run make I get errors...
I've been looking at the forums most of them build from the cm10 source, but I want to build using the original. Figured I would learn more if I tried to build it from the actual sources..
Appreciate any help. If I learn, I would definitely pay it forward by contributing whatever I can to the community..
Thanks
You need to post this in the Galaxy Note phone section.
Wrong section. 1) Dev sections are for builds and modifications. 2) wrong device thread. This is for the galaxy note 10.1 tablet.
Sent from my GT-N8013 using xda premium
n00b13 said:
Hi,
Im new with android develoopment so please bear with a n00b. can someone guide me how to build ics rom using the source provided by samsung..
I have downloaded the original android ics source and samsung's source.. I can build the android source but I dont know how to plug in the samsung code. Unfrotunately, sammy's documentation is insufficient probably about 10 lines, just says to overwrite the android source and do a make. But when I run make I get errors...
I've been looking at the forums most of them build from the cm10 source, but I want to build using the original. Figured I would learn more if I tried to build it from the actual sources..
Appreciate any help. If I learn, I would definitely pay it forward by contributing whatever I can to the community..
Thanks
Click to expand...
Click to collapse
Wrong forum and building pure AOSP for Samsung non-Nexus devices is impossible, too many framework changes needed. Android userspace is Apache licensed so this is unfortunately legal.
Sent from my GT-N8013 using Tapatalk 2
Thread Moved
Please post in the correct section.
Hi,
Nowadays I'm going to do some work in firmwares and I've looked for the full P6200L source tree in a lot of places, but I had no success.
In this post (http://forum.xda-developers.com/showthread.php?t=1576553&page=1) I saw a huge and great discussion regarding port cyanogen 6 to the devices P6200 like. Unfortunately I'm not allowed to post comments directly there.
Can some one point to me where can I find the latest source code that @aorth is using to generate those builds?
ss.plinio said:
Hi,
Nowadays I'm going to do some work in firmwares and I've looked for the full P6200L source tree in a lot of places, but I had no success.
In this post (http://forum.xda-developers.com/showthread.php?t=1576553&page=1) I saw a huge and great discussion regarding port cyanogen 6 to the devices P6200 like. Unfortunately I'm not allowed to post comments directly there.
Can some one point to me where can I find the latest source code that @aorth is using to generate those builds?
Click to expand...
Click to collapse
Guys, @aorth send a message to me. I think this thread may be closed now.
Thanks.
So to preface, every Development thread on XDA has the following sticky:
1. If you are using a stock kernel you MUST mention where you obtained your source. Also, having a link leading to where the manufacturer has uploaded their source is always helpful.
2. If you are using a community driven source build (e.g. CyanogenMod, AOSP, or Parandroid) or a singular developer's source you MUST link directly to the repository that contains the kernel for that specific device. If you are only linking to another thread or to a general repository, this will not be considered as being GPL compliant unless the code has not been modified.
3. If you are forking a repository that is similar to the examples listed above in #2, you MUST publish and link your entire kernel source. This includes any and all changes that you have made. Two of the most common ways developers publish their source on XDA is either with Gerrit, or GitHub. While these two methods are recommended, they are not the only routes you can choose to accomplish this. All that is required is that the source can be viewed and downloaded by anyone who wishes to do so. When releasing an update, your repository must be updated the moment you release your kernel on XDA. If you can post your update to XDA, there should be no reason as to why you cannot release your source.
Click to expand...
Click to collapse
Yet, what are we to do with the tons of ROM development threads that has no reference to sources or general threads that are not possible to build? For me that's mainly a security concern, when a dev releases a ROM for general use, it's hard to check for the authenticity of the product.
My Question Is How Will the Custom Rom Made From The Aosp Base??
I Really want to learn the Android Custom Rom Development.(Again I'm Telling That I'm Not asking about complier or bulid the rom). I'm asking about the source and how it is made.
I Want To Be a core member.
Giving a Guide To This Question Is Highly Appreciated!!
Thank You Guys
(t.me) is a good place, they use SDK and Android Kitchen etc.
JaswanthTeja said:
My Question Is How Will the Custom Rom Made From The Aosp Base??
I Really want to learn the Android Custom Rom Development.(Again I'm Telling That I'm Not asking about complier or bulid the rom). I'm asking about the source and how it is made.
I Want To Be a core member.
Giving a Guide To This Question Is Highly Appreciated!!
Thank You Guys
Click to expand...
Click to collapse
Custom ROM sources require that the stock source code be made available to the public by the manufacturer/carrier of the device. If the stock source code for a specific device has not been made available to the public, developers can not create custom ROM source code for that specific device. Developers use the stock source code to create the custom ROM source code and then ROMs are built using the custom source they created. I think that is the answer you were really looking for. You want to know how the source code itself that the ROMs are built from is created. You aren't asking about the fruit that comes from the tree, you are asking where the tree that bears the fruit comes from. Am I right?
The only way to get custom ROMs on devices that do not have stock source code made available is to port custom ROMs from a similar device with the same architecture that does have available source code and custom ROMs made for it.
OldNoobOne said:
(t.me) is a good place, they use SDK and Android Kitchen etc.
Click to expand...
Click to collapse
I don't think that is what they are asking.
Droidriven said:
I don't think that is what they are asking.
Click to expand...
Click to collapse
Yeah, I Want To Know About Android Arc
JaswanthTeja said:
Yeah, I Want To Know About Android Arc
Click to expand...
Click to collapse
I answered the question. If you specifically want to know how developers convert stock source code into custom ROM source code, you probably will not find that answer here. Most of the people here work with the stuff that the LineageOS team creates from stock source code after the custom ROM source code has been created, they are not part of the process involved in creating the custom source code. It is like being a construction worker, the construction worker does not create the material that he uses to build a house, someone else creates the materials and then he uses what they created to build a house. Google and the LineageOS team create the material, the developers here use what they created to build the ROMs here.
You should try going to github or the LineageOS website to ask your question.
Droidriven said:
I answered the question. If you specifically want to know how developers convert stock source code into custom ROM source code, you probably will not find that answer here. Most of the people here work with the stuff that the LineageOS team creates from stock source code after the custom ROM source code has been created, they are not part of the process involved in creating the custom source code. It is like being a construction worker, the construction worker does not create the material that he uses to build a house, someone else creates the materials and then he uses what they created to build a house. Google and the LineageOS team create the material, the developers here use what they created to build the ROMs here.
You should try going to github or the LineageOS website to ask your question.
Click to expand...
Click to collapse
cool