can anyone help me to learn a bit more than android!
I heared about compile form source and biuld form source...And I can't understand what diferences between compile from source and port! can U explain easily?
for example should I want to bring superOxygen Rom in my x10 , should I port it with cm as base or compile form source?!
thx
for short:
porting means you are making rom to your device from another device, you will be just moving libs, editing ramdisk, etc.
compiling from source means you make a complete rom from scratch including programming own drivers, libs in some situations.
If source is avaiable fot superOxygen then you can try compiling it yourself, but editing, or adding your drivers is necessary, and anyway its harder than porting, but gives better result in fact because you can program everything to make it work and you aren't dependant on binary files like in porting.
When porting, hardware should be close to one you have in your X10, because most things will not work when processor differs, wifi modules, gsm etc. You take files from any X10 rom and replace ones that are with same name in another rom (oxygen here).
Thanks very much man!
I took your advices...it was good advices but what is your idea about this:
If I port Superoxygen from Nexus1 for my x10 and (use stable AOSP as base) , then can I say I make a superOxygen Rom?
compiling from source is how much difficult?! I'm 17...! , I have a link that teach compile from source... Is it need some Knowledges that is impossible for me?!
heh, im 17 too and I don't have much knowledge, but looking on pcfighter(a gt540 developer) im impressed, hes 17 too and does a great job, so it depends on time spent and interests
when you port oxygen, you can just say that you ported and not made it. credits go to the maker and you for just making it work on x10
I'm looking now how to compile for gt540 but can't find any idea how to make it strict for gt540 compiling from source tutorials are mostly for nexus s and nexus 4g because most of are just remade of what you can find on official android developer page and its easier. For unsupported device its even harder, you have to work with what you already have and add it first to sources then ... more things to do. I'm beginner with that too, just pulled sources yesterday and looking how to make it work :] so don't expect so much help in this way :]. Just telling you overall how this looks
For compiling you need to know Java and C programing language.
Sent from my Xoom using Tapatalk
@mesaj! do you know c and gava programing languge?! ofcourse I worked c++ a little...
Thanks now I also know what the difference is.
In easy terminology. Compiling a ROM is building a ROM from the source code so it means you are building a ROM from the ground up. Porting a ROM to your phones means to take a ROM built for another phone and to get it working on yours. That's the simplest way to think of it. I have in my signature a guide for compiling a ROM. Oh and I'm newly 18
私のEVO 3Dから送信される。
Thanks for this thread
Thanks now I also know what the difference is.
Click to expand...
Click to collapse
Thanks for this thread
Click to expand...
Click to collapse
just press the thanks button if you like this thread
OK, this is beginning to give me the s**ts. Where are all the sources to the stuff that is being posted up here? I have been trying to build (rebuild) some of the ROMS on here, if for no other reason than to check there is no dodgy code in them, but also to learn from what everyone has done.
This is supposed to be a DEVELOPMENT forum, where source code is shared and discussed. Not a bazaar where the posters do a bit of hocus-pocus putting together roms from binaries of unknown source code. They fall like crumbs from the majestic sages, that do even more unknown hocus-pocus and cast them down to the unwashed masses to oooh and aahh at, as they give homage to the great compilers in the sky. What is this? Job security?
I have no idea what the legals are around this and I don't really care. The point is that the spirit of the GPL is you post sources (or patches against standard sources) along with any binaries. The binaries are only there to save us the bother of recompiling. The source is what is important in this forum. How else are others going to improve on the code if they can't see it?
I have posted on a couple of threads and/or contacted various people on here, most of whose response is "oh I didn't compile the actual source code, I just stuck it together from the binaries". One of them (thanks kevinlekiller) was kind enough to at least give me rundown on what he did (as best as he could remember - bit of a worry!), but even he didn't have access to the source code. Maybe I haven't looked in the right place, but it shouldn't be this frigging hard - it should be front and centre.
If I had my way, I would ban every ROM post that didn't have a clear link back to all the sources. That's what github etc is for!
Please, please, people, post the source first, binaries can be an afterthought. If you don't have access to the source code, then I reckon it shouldn't be here - who knows what in there? One of these days someone is going to innocently distribute some nefarious program with a ROM. It really isn't that hard to compile a ROM - takes about half an hour on my Linux laptop.
This is actually standard xda-developers policy: see http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45 but seems to be widely ignored.
OK, I'll get off my soapbox now.
Edit: I realise this doesn't apply to everyone, some people are great about posting sources.
Wrong section buddy
Sent from my GT-S5830 using xda premium
djsky2011 said:
Wrong section buddy
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Huh? You're joking right? I'm discussing the sources not being available in this section, the source is a development topic. Hmm maybe this is such a common complaint that there is a separate section created for it. Sorry I'm getting crabby.
What section should it go in?
You take 30mins , mine takes 2h - it's different for everyone......
Furthermore , if they're basing a ROM off a ROM , what sources are there to be published ?
Furthermore , the sources can already be found online if you want CM7/AOSP:
http://github.com/teamhacksung/android_device_samsung_cooper
Herpderp Defy.
ok man make a rom then talk to us. most of roms here are like this u got new app,launcher and theme voila new rom is posted(no offense).so they cant give you source code.they make roms from the prebuilt ones like using stock or cm7 as base .most of the developers which made roms from source code had there github accounts link in there username ok i agree there are one or two developer who dont share but that dose not mean everyone here is just like them.ok
1.i can make a rom.
2.but i will not make a one unless i compiled it from source code.
3.sure i will share its source code.
i agree a little bit with you
EmoBoiix3 said:
You take 30mins , mine takes 2h - it's different for everyone......
Furthermore , if they're basing a ROM off a ROM , what sources are there to be published ?
Furthermore , the sources can already be found online if you want CM7/AOSP:
http://github.com/teamhacksung/android_device_samsung_cooper
Herpderp Defy.
Click to expand...
Click to collapse
Finally. Thank you! A link to the source code (actually the config files is just what I looking for).
So, since I have your attention, I see a couple of roms from people like vo-1, what is he doing just compiling the source (I have asked him, no reply)?
On the ROMS based on ROMS thing, while there is technically no source code you put through a compiler - there is still source - it is a list of all the changes made to that ROM.
I also can't believe people don't seem to use any sort of build environment - as in a build script - how else are we going to document what's been done and/or recreate it?
xdaboy122 said:
ok man make a rom then talk to us. most of roms here are like this u got new app,launcher and theme voila new rom is posted(no offense).so they cant give you source code.they make roms from the prebuilt ones like using stock or cm7 as base .most of the developers which made roms from source code had there github accounts link in there username ok i agree there are one or two developer who dont share but that dose not mean everyone here is just like them.ok
1.i can make a rom.
2.but i will not make a one unless i compiled it from source code.
3.sure i will share its source code.
i agree a little bit with you
Click to expand...
Click to collapse
Yes I agree this does not apply to everyone. Some people do post source. I suppose my frustration was the source seemed to be forgotten and it shouldn't be so hard to track it down. Maybe I have spent too much time in the Linux world, where source code is king.
I will kick off a make on the source that EmoBoiix3 linked to (thanks mate) and see where we go from there!
A lot of roms here are based off other roms. So much they don't build it themselves, just some editing of the zip.
Other developers merely want to save the technobabble since most xda users are blind to programming.
divereigh said:
Huh? You're joking right? I'm discussing the sources not being available in this section, the source is a development topic. Hmm maybe this is such a common complaint that there is a separate section created for it. Sorry I'm getting crabby.
What section should it go in?
Click to expand...
Click to collapse
still wrong section
this aint a source
this is a discusion so its supposed to be in general section
Should be in general section IMO.
But I fully agree with the OP. It is true lots of ROMs here are "cooked" from other ROMs and are not "developed" denovo. They are "theme" packs.
But for example we have two groups actively working on builds of CM 7.2, they each seem to be building from source and tweaking fixes in. It would really help if everyone used github. Pull a source, build, fix and commit to your fork. Anyone else can see what you changed, what revision of the tree you used, and can learn from your work and it could perhaps inspire them to fix something else, to contribute back to make *your* build better.
Sharing your code, even if it is just 5 line hack on teamhacksung / cyanogenmod /AOSP source, honours the GPL and helps our community grow stronger.
The GalaxyICS team is a great example, I can see where they've pulled their sources, what (hard) work they've done in what components. They are contributing all their work and knowledge back. And their fixes can be pulled into other projects easily, speeding up development and sharing that knowledge for everyone.
A phone like the Ace continually loses developers as they migrate to "better" phones, and we really need to share as much knowledge as possible to keep our software
Sometimes , changes just cannot be shown.....like framework-res tweaks!
Herpderp Defy.
EmoBoiix3 said:
Sometimes , changes just cannot be shown.....like framework-res tweaks!
Click to expand...
Click to collapse
What sort of tweaks are you thinking of? If it's a replaced image file, then that can be a separate file copied in with a script. If it's a changed text file, that can be done with patch or sed.
Let me give you an example of what I did with kevinlekiller's The End 2.5o rom. He based it on a vo-1 rom and did a fair number of replacing files, odexing etc. I produced this bash script (attached) along with his extra (binary) sources which I think replicated what he did. Self documenting! Everyone can see what is in there, maybe even change it again.
More details towards the bottom of this page: http://forum.xda-developers.com/showthread.php?t=1440396&page=31
I see where you are coming from and I sympathize. I'm not a developer, because I don't have the time and patience to work on source code , compile , debug etc.
The Rom's we have for the Galaxy Ace are already very good, the developers that have worked on them have/had the time and patience to iron out most the issues. So for me to try to come out with something better would seem futile.
I still like customizing these Rom's to a way that work better for me, and it doesn't involve having to spend lots of time, because like I said they are already very good. So it just ends up that a few files are added or changed.
Is that a bad thing? I think those that think it is should just not use those types of Rom's, everyone has a right to their opinion.
At first when you asked me for sources, I thought you meant the source code, since I already listed everything that was used in the first post. But then I realized you wanted direct sources (links) to those files. This is something I will do in the future, post the links of every file, I agree with you , things should be more documented, it would save everyone time instead of trial and error and possibly even giving up.
Anyways, I should conclude here, it is getting a long read.
divereigh said:
What sort of tweaks are you thinking of? If it's a replaced image file, then that can be a separate file copied in with a script. If it's a changed text file, that can be done with patch or sed.
Let me give you an example of what I did with kevinlekiller's The End 2.5o rom. He based it on a vo-1 rom and did a fair number of replacing files, odexing etc. I produced this bash script (attached) along with his extra (binary) sources which I think replicated what he did. Self documenting! Everyone can see what is in there, maybe even change it again.
More details towards the bottom of this page: http://forum.xda-developers.com/showthread.php?t=1440396&page=31
Click to expand...
Click to collapse
nice script, thats for sure
but u shouldnt expect everyone to be as geeky and provide such build script.
theres a big different between "providing source" that is mandatory by forum rules and "providing howto step by step" like in your script.
hell most of the roms (the one that is based on previous precompiled rom) were created 100% on windows machine without even touching linux, and maybe the rom creator (modder) doesnt have any clue what in the world is linux. maybe they even dont know that their windows machine do have terminal (cmd). so arent u asking for too much?
an0nym0us_ said:
nice script, thats for sure
but u shouldnt expect everyone to be as geeky and provide such build script.
theres a big different between "providing source" that is mandatory by forum rules and "providing howto step by step" like in your script.
hell most of the roms (the one that is based on previous precompiled rom) were created 100% on windows machine without even touching linux, and maybe the rom creator (modder) doesnt have any clue what in the world is linux. maybe they even dont know that their windows machine do have terminal (cmd). so arent u asking for too much?
Click to expand...
Click to collapse
Actually I only have 1 windows pc, all my other PC's are ubuntu / linux mint installed on them. I use windows on the main PC because most of my games work on it.
Edit: And, I didn't take offense to your post , it is valid, most people have no clue about linux.
kevinlekiller said:
Actually I only have 1 windows pc, all my other PC's are ubuntu / linux mint installed on them. I use windows on the main PC because most of my games work on it.
Edit: And, I didn't take offense to your post , it is valid, most people have no clue about linux.
Click to expand...
Click to collapse
and no offence intended and sorry if anyone feels my post abit too offending
my point is a rom created from previous precompiled rom can be created 100% on windows machine.
in that case the rom also doesnt have sourcecode because it were created from already precompiled rom.
so if the modder just give a valid link to what he put/change it still suites the forum rules to provide source.
let say i've modded a cm rom, i've include ketuts oc kernel, i've include a launcher, and a filemanger, and a theme.
so if i just provide a valid link to the original cm rom, a link to ketuts oc kernel thread, a market link to the launcher, the filemanager and the theme, thats a valid source because the rom were modded from binary precompiled rom/kernel/launcher/filemanager/theme.
so the link to those binary precompiled rom/kernel/launcher/filemanager/theme is a valid "source".
divereigh said:
This is supposed to be a DEVELOPMENT forum, where source code is shared and discussed. Not a bazaar where the posters do a bit of hocus-pocus putting together roms from binaries of unknown source code.
Click to expand...
Click to collapse
I agree. There are two groups of devs:
"Real" developers. They provide repo links and detailed changelogs.
Modders. They should provide repo links and detailed changelogs.
A repo has the benefit of allowing peer review. Peer review improves code quality just like user tests and their reports do. Afterall, this is what XDA is about.
What I like about XDA is how people eagerly send in "works" notes. Not much information, but better than just trying out and telling nobody.
Exactly guys......it seems cyanogenmod has become the only alternative and devs here are only editing it and bringing out new firmware versions. Some also edit stock roms..........but no one here gave a thought of creating a new genre of custom rom right from source.
biswatmak said:
Exactly guys......it seems cyanogenmod has become the only alternative and devs here are only editing it and bringing out new firmware versions. Some also edit stock roms..........but no one here gave a thought of creating a new genre of custom rom right from source.
Click to expand...
Click to collapse
its not as easy as it sounds, thats why the two main dogs are miui and cyanogenmod.
an0nym0us_ said:
nice script, thats for sure
but u shouldnt expect everyone to be as geeky and provide such build script.
Click to expand...
Click to collapse
I get that. I essentially built an interpreter and a source file (the build instructions). Way too much for most. However I think it would be great as developers if we provided be packaging tools so that others can use them and provide repeatable builds and automatically documented builds ("read the source luke").
an0nym0us_ said:
theres a big different between "providing source" that is mandatory by forum rules and "providing howto step by step" like in your script.
Click to expand...
Click to collapse
Agreed, it isn't mandatory, however for the purposes of educating and peer-review it would be great. So my challenge is to make this easy for people.
an0nym0us_ said:
hell most of the roms (the one that is based on previous precompiled rom) were created 100% on windows machine without even touching linux, and maybe the rom creator (modder) doesnt have any clue what in the world is linux. maybe they even dont know that their windows machine do have terminal (cmd). so arent u asking for too much?
Click to expand...
Click to collapse
So we need a graphical version for Windows..
Hi. I would like to learn how to develope and port kernels..
Before anybody starts posting guides, I know how to download a kernel source add a few tweaks and compile. But I do not know how to port kernels. Or make cyanogen or AOSP kernels..
So my question is, are there any guides I can read, That will help me get started.
I also understand that I won't get a specific guide I just want a general guide to help me get started.
gmillz said:
Hi. I would like to learn how to develope and port kernels..
Before anybody starts posting guides, I know how to download a kernel source add a few tweaks and compile. But I do not know how to port kernels. Or make cyanogen or AOSP kernels..
So my question is, are there any guides I can read, That will help me get started.
I also understand that I won't get a specific guide I just want a general guide to help me get started.
Click to expand...
Click to collapse
There is no general guide, or any specific how to for merging code to build a aosp kernel. You get the kernel source for HTC for example, then compare that kernel with either an aosp kernel with a comparable type, or look at the aosp devices and merge things are remove them until you have a kernel that can boot in aosp. Then you start tweaking and tweaking until the kernel is stable.
lithid-cm said:
There is no general guide, or any specific how to for merging code to build a aosp kernel. You get the kernel source for HTC for example, then compare that kernel with either an aosp kernel with a comparable type, or look at the aosp devices and merge things are remove them until you have a kernel that can boot in aosp. Then you start tweaking and tweaking until the kernel is stable.
Click to expand...
Click to collapse
Thank you. That gives me a better understanding.
Sent from my captivated jelly beans. waiting on my skyrocket to get back from its space journey.
Hello everyone, I'm trying to compile a version of CM10.1 with Linaro Toolchain, but so far only managed to set the Linaro for part of the ROM (JAVA), while for the Kernel (C/C++) has not been successful.
In the link below, infected_ posted a brief tutorial on how to configure the environment to use Linaro, but only for part of the ROM (and works well :good. As for the kernel, it was unclear how to perform the configuration.
http://forum.xda-developers.com/showpost.php?p=42976693&postcount=12
Could anyone give me some help on how to configure Linaro to compile the Kernel CM10.1 along with the rest of the ROM?
Before someone politely send me to Google... I searched and got many errors... (I even "kill" my phone, but already revived her.).
Note: I have no interest in publishing my work, I'm just looking for knowledge because I am very curious!
New informations about Linaro configurations to compile the CM10.1 Kernel released by infected_:
http://forum.xda-developers.com/showpost.php?p=43649447&postcount=449
All information gathered here are authored by infected_, then give thanks to him!:good:
Sorry for my English and thank you!:highfive:
Someone, somewhere?
Ask the devs on here to help you mate. A few on here using that way of building . Im sure they will help out. Just ask really nice :thumbup:
andrewwright said:
Ask the devs on here to help you mate. A few on here using that way of building . Im sure they will help out. Just ask really nice :thumbup:
Click to expand...
Click to collapse
Thank you my friend, I tried to ask a few things for some devs via PM, but usually they do not respond, because there are many requests all the days.
I found it interesting to create this topic because I've seen some people with the same question that I, and perhaps could be kept here a discussion.
But anyway I appreciate your interest!:good:
To be honest mate that sounds like a great idea. Keep trying pms and when you have compiled a working rom come bk and tells us (me) how. Soon im going to build a rom and am looking for all the info I can get on it. If I find what you need il come bk here. I read its smoother ui and better battery this way. It that why you choose this way of building?
Precisely, I read about it, and as I understand, when using Linaro Toochain, we get a gain of over 30% in performance, but I believe that the secret of all this performace is in the compilation of Kernel. And it is this part that I "got stuck" hehehe...
Currently my environment works well with Linaro Toochain 4.8-13.06 (compiling part of the ROM), and with Official Google GCC 4.7 (compiling the kernel).
At that moment I did not notice a significant gain in performance compared to the CM10.1 Official Nightly Builds.
Hello there guys,
As we all know we only have 3? 4? developers for the HOX+ . And they are really doing all they can to help keep the phone upto date.
But as we all know they are all busy and can't update their roms that much any longer.
EDIT: Lloir already has a guide : http://forum.xda-developers.com/showthread.php?t=2187266 but I don't think he covers how to fix camera and gps and stuff
So! Is it possible to make guide on how to compile the rom from the source? I know tombridden and lloir already made a one post guide on how to build some roms but it was too specific.
I now have an extra machine (a laptop) with 500gb free storage and ubuntu as the main OS. It's quite powerful too with 6gb RAM and i7. So Why not use it to help the community while others are busy? In the meantime I will look around for some guides for other phones but I don't think they will help that much.
And please include the answers to those questions if you make a guide:
1- What to do to fix camera/GPS/wifi/Data/sensors ?
2- What approach should I take when compiling a new ROM. For example: there are no developers for PACMAN , how will it differ during compiling between it and AOKP/CM/AOSP .
I am talking about a rom that wasn't approached by Lloir so he won't have the repos for them. What to do then?
Thanks a lot and I can't wait to help
@Lloir @tombriden @PippoX3 @mike1986. and any other developer out there.
you can start by looking at XDA-University
The reply is correct. All of us moved first steps studying at XDA University.
Anyway the case is more complex than others.
For this device there are really few developers. Other device have a lot of support from constructors, many dev and the team-work result in a lot of kernels/roms to flash for the final user.
If you wanna taste the happyness for build a rom, I'll send you a guide to setup your ubuntu, download the sources and build.
But in this case, where enrc2b is not officially support, the things are more difficult.
You must have a minimal practical with java, cpp, android and kernel code (if so).
For the moment I'm in trouble to build an AOKP 4.2.2 with new kernel. I haven't device to try, 'cause the hard is build&&try continuosly.
Not the fact to have a pc turned on for hours and hours.... and the eyes&&mind open for hours and hours... but the patience to continuously try time after time.
Now I am in a dead point... many users like have S2W enable on new CM kernel... but.... the kernel won't!
Thanks a lot anyway. Thanks to @Lloir, @tombriden, @maxwen and alls who's workin' for this device.
Stay tuned....
PippoX3 said:
The reply is correct. All of us moved first steps studying at XDA University.
Anyway the case is more complex than others.
For this device there are really few developers. Other device have a lot of support from constructors, many dev and the team-work result in a lot of kernels/roms to flash for the final user.
If you wanna taste the happyness for build a rom, I'll send you a guide to setup your ubuntu, download the sources and build.
But in this case, where enrc2b is not officially support, the things are more difficult.
You must have a minimal practical with java, cpp, android and kernel code (if so).
For the moment I'm in trouble to build an AOKP 4.2.2 with new kernel. I haven't device to try, 'cause the hard is build&&try continuosly.
Not the fact to have a pc turned on for hours and hours.... and the eyes&&mind open for hours and hours... but the patience to continuously try time after time.
Now I am in a dead point... many users like have S2W enable on new CM kernel... but.... the kernel won't!
Thanks a lot anyway. Thanks to @Lloir, @tombriden, @maxwen and alls who's workin' for this device.
Stay tuned....
Click to expand...
Click to collapse
That's what i did already. I set up the periphals/kernel/device info GITs and now i am looking for the roms, I found CM and stuff but I can't find PURE AOSP , does that mean i must download it and upload it?
I also have Oracle java installed. Do I have to have open JDK?
Ghand0ur said:
That's what i did already. I set up the periphals/kernel/device info GITs and now i am looking for the roms, I found CM and stuff but I can't find PURE AOSP , does that mean i must download it and upload it?
I also have Oracle java installed. Do I have to have open JDK?
Click to expand...
Click to collapse
https://github.com/pure-aosp/android
Lloir said:
https://github.com/pure-aosp/android
Click to expand...
Click to collapse
Now that we begin to have a solid CM base, will possible to build at least CM for enrc2b for noobs too.
And eventually "port" device/kernel" parts to others platforms. So who like e.g. PA can do...
If you agree, I can paste my personal appoints to a guide, from client setup (Sun java don't works) to the build zip rom.
Updated and corrected to last KK.
PippoX3 said:
Now that we begin to have a solid CM base, will possible to build at least CM for enrc2b for noobs too.
And eventually "port" device/kernel" parts to others platforms. So who like e.g. PA can do...
If you agree, I can paste my personal appoints to a guide, from client setup (Sun java don't works) updated and corrected to last KK.
Click to expand...
Click to collapse
Go for it. Saves me doing it which I was about to do
Sent from my One X+ using Tapatalk