Database Develop

[Q] Guide me please! Installing from source.

Hi everyone, i just installed Ubuntu 11.10 on my netbook . Really interested in
building android from source. Like what people are doing in the ICS CM9
development thread. Please guide me on what to do next, i have no experiences on
using Ubuntu. I apologize in advanced for causing any troubles for you
guys.

PlasticPhone said:
Hi everyone, i just installed Ubuntu 11.10 on my netbook . Really interested in
building android from source. Like what people are doing in the ICS CM9
development thread. Please guide me on what to do next, i have no experiences on
using Ubuntu. I apologize in advanced for causing any troubles for you
guys.
Click to expand...
Click to collapse
Here are two great links to get you started
Link 1
Link 2
start by build yourself a kernel, and then work your way to a full build

PlasticPhone said:
Hi everyone, i just installed Ubuntu 11.10 on my netbook . Really interested in
building android from source. Like what people are doing in the ICS CM9
development thread. Please guide me on what to do next, i have no experiences on
using Ubuntu. I apologize in advanced for causing any troubles for you
guys.
Click to expand...
Click to collapse
Brave of you to try. I've been meaning to do that myself, but I believe you can only build in Linux. Alas, I don't have any knowledge of that OS. I only use win7. I know this might be a stupid question, but can one build in win7? hope? he devs releases a flashable zip soon... :'(
Tapatalkin' it from my rooted NookColor running CM7 MiRaGe [KANG] [7.2 RC] overclocked @ 1.2 GHz

les02jen17 said:
I believe you can only build in Linux.
Click to expand...
Click to collapse
Ubuntu is Linux. You can burn it to a CD and take it for a spin without changing your Win7 machine. Or, you can dual boot like I do. Give it a whirl!
To the OP: good for you!

les02jen17 said:
Brave of you to try. I've been meaning to do that myself, but I believe you can only build in Linux. Alas, I don't have any knowledge of that OS. I only use win7. I know this might be a stupid question, but can one build in win7? hope? he devs releases a flashable zip soon... :'(
Tapatalkin' it from my rooted NookColor running CM7 MiRaGe [KANG] [7.2 RC] overclocked @ 1.2 GHz
Click to expand...
Click to collapse
No Windows build support. You can just run Ubuntu in a virtual box without having to deal with a dual boot.
Sent from space

3.0 Kernel for AOSP JB?

I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here -
http://forum.xda-developers.com/showthread.php?p=33291894
He'll probably help us out if we make some progress in booting up Codename with it at least

TheDareDevil said:
I've been using Codename ever since it came out but I got tired of the problems related to the Kernel and switched to ProjectX. I and I'm sure others really want to use a smooth and working JB ROM.
Is there anyone working on the 3.0 Kernel for our device? I know Nik said he contacted someone to help us out but there's been no news on that front yet.
If anyone knows how to modify Kernels, Adi_pat gave some tips here - http://forum.xda-developers.com/showthread.php?t=1899335&page=38
He'll probably help us out if we make some progress in booting up Codename with it at least
Click to expand...
Click to collapse
Upon the exit of JB roms ago, were used GB modified kernel, now with source code maybe will be possible to compile a fully working kernel, but afaik there are no 3.x kernel for JB, maybe someone is working out of xda on irc channel but don't known..
Sadly I do not have much competence, plus I don't have the phone it's to repair....

There is kernel 3 for incredible 2 and desire s..may be someone can port it..
Sent from my HTC Incredible S using xda app-developers app

I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app

TheMegosh said:
I might be crazy, but I remember reading a post not too long ago about a dev that was writing the 3.0 kernel from source for our phones. I haven't heard an update since then, but I remember hearing it was someone with relation to the cm9 team. It sounded promising, but that development was very slow.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?

Well tbh honest a working GB kernel would do too.
Like the front camera and chrome and screen flickering etc.
Damn I wish kaijura was here
Sent from my HTC Incredible S using xda app-developers app

CyanideJack said:
Off the top of my head I seem to recall Noverbose saying he was trying to write a 3.0 Kernel. I also remember at least one other person mentioning something similar to, so there are people working on this. From what I understand it's not easy - I doubt we'll see anything this side of Christmas tbh. I hadn't realised that the Inc 2 and DS had a 3.0 Kernel though. Anyone know if they are actually a made from source version, rather than the same hacked version that we have in Codename, for example?
Click to expand...
Click to collapse
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.

ZaySk said:
Yes those 3.0 kernels are compiled from source. I checked out AOSP ROM threads in the Desire S and Inc 2 section that had 3.0 kernel, then looked up the creator of the ROM on github and found the sources. I was going to try tackle the 3.0 kernel to get a hang of the make system before building CM9, but I don't have enough monthly data left to download the kernel toolchain! Nov 1st is close, so I can get to work soon! :highfive:
The best way to build an AOSP 3.0 kernel for our device would probably be to look at the source code for 3.0 kernels on our sister devices, and figure it out from there.
Click to expand...
Click to collapse
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?

The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s

CyanideJack said:
Well holy crap, dude, get on that! Seriously though, getting a working 3.0 kernel for our device would go a long way to making JB a usable ROM for our device. Would it be possible to port JellyTime or a similar JB ROM to our device as well?
Click to expand...
Click to collapse
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
l0st.prophet said:
The source doesn't need changing, it is the ramdisk that is the problem. I have been trying to get help, but so far no luck, adi_pat said he would take a look, but it is hard for me to test as I no longer have an inc s
Click to expand...
Click to collapse
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.

ZaySk said:
I'm gonna worry mainly about compiling CM9 from source once November hits, that's gonna take up the majority of my time. After I get the first release of CM9 out, I'll start work on a 3.0 kernel if it hasn't been done yet. I have no experience whatsoever dealing with kernels though, except for small ramdisk edits, so don't expect any miracles.
It should be possible to port other JB ROM's over using one of nik's ported JB ROM's as a base and reference point, the only problem is I don't know exactly what files I have to substitute to port a ROM. I've PM'd nik about that a few hours ago, so hopefully I'll get some more information on the subject. Nik has been a big help to my dev efforts as a whole.
Interesting, if it's only the ramdisk that needs changing, couldn't you look at the ramdisk from one of niks JB ROM's? Or is it not as simple as that? I'm assuming the latter, seeing as if it were that obvious I'm sure someone would've done it by now. If you ever need help testing, send me a PM I'd be more than willing to test for you.
Click to expand...
Click to collapse
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?

markj338 said:
About using one of Nik's JB roms as a reference
What I understood was that the rom has been built around the old 2.6.x kernel and has to be modified again to work with the 3.0.x kernel, if you guys get one up and running. If that is the case, wouldn't you be going down the wrong path if you model it around nik's existing 2.6.x roms?
We need kaijura here, he was our AOSP kernel master. Hopefully he is doing ok, and has found something else other than xda because he hasn't been online for months. At least other devs, like lordclokan and kali- have moved on and are active with other devices... kaijura hasn't been on at all. Anyone been in contact with him/her?
Click to expand...
Click to collapse
I know, it would be going down a pretty redundant path. If I was able to port over a JB ROM using nik's ROM's as a base, then my ported ROM would inherit all the same bugs nik's ROM's already have.
I wish kaijura was still around, I have so many questions I want to ask about compiling from source! Luckily lordclokan was a massive help to me in that regard. Kaijura's github hasn't seen action in months either, sadly.

Forgive my ignorance, but isn't the Desire HD essentially our device with a bigger screen and less memory? That being the case, could we not just port across one of the 3.0 Kernels from that?

The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.

The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app

l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Well you can prolly get ideas from adi ( he posted http://forum.xda-developers.com/showpost.php?p=33302707&postcount=387 not sure if you saw it) he seems to know what's up.

TheDareDevil said:
The only problem with the desire HD kernel would be that our front camera would not work
+ I forgot to link to adi_pat's post - http://forum.xda-developers.com/showthread.php?p=33291894
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
So it looks like the furthest things got regarding a 3.0 Kernel was;
Adi_Pat said:
chan
Ok so 2.6.35 works with Jellybean. Why not pack the ramdisk with zImage compiled from 3.0.y sources(Considering you are using standard boot.img format[?]) Because to get it to boot, you would not require any hacks/changes to source, editing ramdisk(init.rc) is enough to make it boot initally.
EDIT: You may also need to change init binary.
Click to expand...
Click to collapse

l0st.prophet said:
The problem with the ramdisk that come with the official ROM's that have 3.0 kernels, is that they are built for the sense framework and don't work on AOSP ROM's. The ram disk that is included with Nik's JB ROM's is heavily modified to run a GB kernel with ICS / JB sources, so the problem is I don't have a base to work from, I am basically trying to merge the two init's to make the 3.0 kernel boot.
Saying that we need to port 3.0 kernel is probably a bit misleading, and for that I apologise, the kernel itself has very little Sense specific stuff, it's the ramdisk that is responsible for launching the kernel that is the issue here at the moment.
Click to expand...
Click to collapse
Very interesting, thanks for the informative post. :good:

zaysk said:
very interesting, thanks for the informative post. :good:
Click to expand...
Click to collapse
happy november!!!

markj338 said:
happy november!!!
Click to expand...
Click to collapse
A very happy November indeed

[Q]how to compile from source

I apologize for my bad English I am Italian and use google translate
I need a guide on how to compile Android from source
(the ParanoidAndroid for accuracy)
which linux distro to use?
which packages to install?
which commands to use?
I have a lot of time free
and a core i5 cpu
I think that to compile Android from source
but I need a guide
then I ask you developers, you can post a guide
----------------------------------------------------------------------------------------
write from my pc using win8 e programming a websites

bomdia said:
I apologize for my bad English I am Italian and use google translate
I need a guide on how to compile Android from source
(the ParanoidAndroid for accuracy)
which linux distro to use?
which packages to install?
which commands to use?
I have a lot of time free
and a core i5 cpu
I think that to compile Android from source
but I need a guide
then I ask you developers, you can post a guide
----------------------------------------------------------------------------------------
write from my pc using win8 e programming a websites
Click to expand...
Click to collapse
Well, you need a lot of work to get a working build, as i currently compile CM9 for SXL.
Recommended distros: Ubuntu 12.04 Precise / Linux Mint 13 Maya with Cinnamon interface to have the best linux experience << The best linux distro i ever used
Packages: Well, you need to check the Paranoid site to download the repo for ICS or JB variant of source-code.
Commands: Lots of commands, there are tutorials online. Example >> here
After this, you will need the device tree for SXL, i have one that is deprecated (not updated for some time), it does not work the variant uploaded here, but i will upload it.
You will need the vendor files, i also have the files but as the build of CM9 don't work, i haven't upload them anywhere untill i can get an at least experimental build that boots
Link for android device tree for sxl by me here
There is a lot of work and there aren't any specific guides on how to do this, you need to join communities and be a pain on the ass for them untill you learn how to do this.
I hope this helps anyways

Lexmazter said:
Well, you need a lot of work to get a working build, as i currently compile CM9 for SXL.
Recommended distros: Ubuntu 12.04 Precise / Linux Mint 13 Maya with Cinnamon interface to have the best linux experience << The best linux distro i ever used
Packages: Well, you need to check the Paranoid site to download the repo for ICS or JB variant of source-code.
Commands: Lots of commands, there are tutorials online. Example >> here
After this, you will need the device tree for SXL, i have one that is deprecated (not updated for some time), it does not work the variant uploaded here, but i will upload it.
You will need the vendor files, i also have the files but as the build of CM9 don't work, i haven't upload them anywhere untill i can get an at least experimental build that boots
Link for android device tree for sxl by me here
There is a lot of work and there aren't any specific guides on how to do this, you need to join communities and be a pain on the ass for them untill you learn how to do this.
I hope this helps anyways
Click to expand...
Click to collapse
thanks a lot I think I start tomorrow I'm a little tired

Hi just so you know you won't be able to compile Paranoid Android for ICS from source as it was never released.
If you can get JB to work then you will not only be a hero but also be able to use Paranoid Android source

I have a problem I can not download the sources of the paranoid in any way
help (or build the sources normal Android?)

Did you follow a guide how to set up the environment in linux? Or Mac.. the way you can download sources is git clone and then the git link. There are many guides on doing that part. Also when I download source it times out in a 4 mb/s connection and I need to use a better connecyion
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

anders3408 said:
Did you follow a guide how to set up the environment in linux? Or Mac.. the way you can download sources is git clone and then the git link. There are many guides on doing that part. Also when I download source it times out in a 4 mb/s connection and I need to use a better connecyion
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Click to expand...
Click to collapse
aa ok but the guide I was reading did not say that it was necessary to clone each of the sources piece by piece, but he said to use a single link.
I have linux mint 14 with cinnamon (from the 13 consigliatami lextmazter I do not work)
both in Italy and in spite of my connection is approximately 16 mb / s (88% above the national average)

Post link to guide.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium

bomdia said:
aa ok but the guide I was reading did not say that it was necessary to clone each of the sources piece by piece, but he said to use a single link.
I have linux mint 14 with cinnamon (from the 13 consigliatami lextmazter I do not work)
both in Italy and in spite of my connection is approximately 16 mb / s (88% above the national average)
Click to expand...
Click to collapse
I do not recommend Linux Mint 14 as it is new edition, based on new Ubuntu version 12.10 if i remember good, don't know for sure, that's why, on Ubuntu 12.04 building is supported, even though on some guides it is said that on 12.04 it is experimental, well, it was, now it should be stable.
Also, if you want to port things like Paranoid or PAC you should start with AOSP or CM9 or AOKP, to put it short, versions that have guides and source codes on their sites. In my opinion CM is the best thing to start with, that's why i started CM9, after that you can easily port every 4.0.4 AOSP based ROM.
The same thing applies to JB, if you can port or build AOSP or CM10, you can port every JB AOSP based ROM very easily following only a few basic steps, that's how things work in this hood
Off-topic: I was a little distracted from building/testing/devving because of the school affairs, but today i will resume my work on CM9, if things work well, i will have a bootable build this very evening.

same as lexmazter, sound correct. the hard part is build CM9 rom, rest is pretty easy.
Lexmazter, i am about to try take a ramdisk from cm9 primou and make changes in every lines and see if i can get it to work with runnymede. if it does we will have a working aosp bootimg. i have compiled a zimage from source and it works with wifi and bt and so on in sense rom, also zimage works with cm9 with wifi.
lexmazter, can you please take a bencmark test with antutu 3.0.1, the new one, and post screenshot of the score and wich rom you are in ? they have made the test much diffrend so score is diffrend in 3.0.1 than older , so i have nothing to compare it to

anders3408 said:
same as lexmazter, sound correct. the hard part is build CM9 rom, rest is pretty easy.
Lexmazter, i am about to try take a ramdisk from cm9 primou and make changes in every lines and see if i can get it to work with runnymede. if it does we will have a working aosp bootimg. i have compiled a zimage from source and it works with wifi and bt and so on in sense rom, also zimage works with cm9 with wifi.
lexmazter, can you please take a bencmark test with antutu 3.0.1, the new one, and post screenshot of the score and wich rom you are in ? they have made the test much diffrend so score is diffrend in 3.0.1 than older , so i have nothing to compare it to
Click to expand...
Click to collapse
5941 no OC with LTX Kernel v0.7 and Sense 3.0 by fshami, also, i think i found the right ramdisk for now for CM9, it solved the dalvik-permissions, now i still need to boot the build, still trying to figure what is wrong here and why it hangs after Android is upgrading... >> Starting applications.
I can work more on my device now as i have a cheap second phone to use if for calls and sms.

so then I decided, when I start buildare the source of AOSP Android 4.2 jellybean I think it's easier for me to start.
I had to use because the new mint old man crashed always

bomdia said:
so then I decided, when I start buildare the source of AOSP Android 4.2 jellybean I think it's easier for me to start.
I had to use because the new mint old man crashed always
Click to expand...
Click to collapse
As a recommandation, i would recommend building AOSP 4.0.4, it is easier to start and has more chances of working, after that, you have the experience and the headstart to work on 4.1 and only after that on 4.2.
Just start with baby-steps, it is easier and increases the chances of success.

Lexmazter said:
As a recommandation, i would recommend building AOSP 4.0.4, it is easier to start and has more chances of working, after that, you have the experience and the headstart to work on 4.1 and only after that on 4.2.
Just start with baby-steps, it is easier and increases the chances of success.
Click to expand...
Click to collapse
ahh ok then I try to go with 4.1 if I can not then step 4.0.4

bomdia said:
ahh ok then I try to go with 4.1 if I can not then step 4.0.4
Click to expand...
Click to collapse
Well, i recommend this because i'm still building 4.0.4 and i haven't successfully booted a build, so that's why i say this, because if you get the 4.0.4, in short terms, all you need to change for 4.1 is the graphics driver, but for 4.2 i don't know for sure, too new for me and i'm still trying to get 4.0.4 to air

then my kernel is not so bad 5838 with sense 4.1 v. 1.5.1 and still missing some improvments
which ramdisk are you using, zimage from stock rom should get it to boot, but the ramdisk as you know need to be changed to cm9. when you compile from source it should also make a ramdisk that will fits the rom, i think it is best to check what the diffrence in the new ramdisk and the old one with VM errors and then fix them, perhaps it will boot then ? one specific compiled by you ? post a logcat in your cm9, had also some bootloop in my cm9 port but got it booting.

anders3408 said:
then my kernel is not so bad 5838 with sense 4.1 v. 1.5.1 and still missing some improvments
which ramdisk are you using, zimage from stock rom should get it to boot, but the ramdisk as you know need to be changed to cm9. when you compile from source it should also make a ramdisk that will fits the rom, i think it is best to check what the diffrence in the new ramdisk and the old one with VM errors and then fix them, perhaps it will boot then ? one specific compiled by you ? post a logcat in your cm9, had also some bootloop in my cm9 port but got it booting.
Click to expand...
Click to collapse
just enter the irc channel, will talk more there, no need to spam the forum with this.
The boothanging is because of the audio, the ramdisk is good, i use the LTX v0.7 zImage and ramdisk from stock edited to fit the build.
Also, the ramdisk is not made with the build, maybe if you compile the kernel with the rom, and for this you need to put the kernel online and othe things, and because of proxy, i can't and won't do that. For more details, like i said, find me on the irc.
link here

you say that jelly beans to need a new kernel? because sifting through the Internet I found this: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources there are also drivers for jelly bean of adreno 2xx

bomdia said:
you say that jelly beans to need a new kernel? because sifting through the Internet I found this: https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources there are also drivers for jelly bean of adreno 2xx
Click to expand...
Click to collapse
yeah, those are the drivers
But they do not require a new kernel

Lexmazter said:
yeah, those are the drivers
But they do not require a new kernel
Click to expand...
Click to collapse
but I need or I do not need?

[Q] How to port I9300 roms to I9305?

Hello , I'm very disappointed of the interest of the developpers for the LTE variant of the S3 so i wanted to port i9300 roms from myself , according to hardware , the only changes are the modem and the ram right ? So how could i port these roms ? From no specific knowings , i'd like to at least learn how to do it without big risks of brick so help please .
Thank you and sorry for english mistakes if i've done some.

aaz03 said:
Hello , I'm very disappointed of the interest of the developpers for the LTE variant of the S3 so i wanted to port i9300 roms from myself , according to hardware , the only changes are the modem and the ram right ? So how could i port these roms ? From no specific knowings , i'd like to at least learn how to do it without big risks of brick so help please .
Thank you and sorry for english mistakes if i've done some.
Click to expand...
Click to collapse
this is not a easy question for random guys like me with almost zero knowledge about developing, although on the other hand a developer could simply explain how its done by f.e. making a thread about porting roms specifically to our i9305 in noobs language (if possible) but i doubt that this will happen, as it is very much time consuming and a lot of thinking and typing work. personally i think a thread like this would bring some life into our i9305s threads, dont you think so..?
to get you already started with some learning and discovering for yourself, read further..
the best method for porting roms is IMO building from source, but this is not as easy as it sounds..
first you will need to set up a build environment. I assume youre using Windows OS, now if you got a 64 bit system this is exactly what you need.. fortunately for you and others there is a custom branch of the Ubuntu OS thanks to @sylentprofet to use with Oracles VB/VM (Virtual Box/Machine) already preconfigured for building or porting roms (both require building/developing experience though) all you need to do is download the source and commit, fork, cherry-pick etc. if you decide to step into the android development world, you will learn more step by step however having some basic knowledge like terminal commands and git commands would be useful.
Also you need to get familiar with github and how it is used, check out here
I recommend lots of research though before actually taking any actions!! all these things will make you feel :silly: at times, but do not give up! for there were is a will, theres a way
good luck :good:
Download builduntu v1.4 here
Download Oracles VB here
Guide-how to build rom from source (most recent one i guess)

MaHo_66 said:
this is not a easy question for random guys like me with almost zero knowledge about developing, although on the other hand a developer could simply explain how its done by f.e. making a thread about porting roms specifically to our i9305 in noobs language (if possible) but i doubt that this will happen, as it is very much time consuming and a lot of thinking and typing work. personally i think a thread like this would bring some life into our i9305s threads, dont you think so..?
to get you already started with some learning and discovering for yourself, read further..
the best method for porting roms is IMO building from source, but this is not as easy as it sounds..
first you will need to set up a build environment. I assume youre using Windows OS, now if you got a 64 bit system this is exactly what you need.. fortunately for you and others there is a custom branch of the Ubuntu OS thanks to @sylentprofet to use with Oracles VB/VM (Virtual Box/Machine) already preconfigured for building or porting roms (both require building/developing experience though) all you need to do is download the source and commit, fork, cherry-pick etc. if you decide to step into the android development world, you will learn more step by step however having some basic knowledge like terminal commands and git commands would be useful.
Also you need to get familiar with github and how it is used, check out here
I recommend lots of research though before actually taking any actions!! all these things will make you feel :silly: at times, but do not give up! for there were is a will, theres a way
good luck :good:
Download builduntu v1.4 here
Download Oracles VB here
Guide-how to build rom from source (most recent one i guess)
Click to expand...
Click to collapse
Thanks mate, i'm gonna try this and gîve you some news, other advices for maybe add some optimizations like linaro and kernel adding for example? I'd like to just port Roms but maybe it would be interesting to build my own rom later
Edit: sorry didn't read the guide, find my answers, thank you

aaz03 said:
Thanks mate, i'm gonna try this and gîve you some news, other advices for maybe add some optimizations like linaro and kernel adding for example? I'd like to just port Roms but maybe it would be interesting to build my own rom later
Click to expand...
Click to collapse
your welcome bro :good:
i really have no idea about how linaro is used in combination with kernel, you really have to google that one or get in contact with a dev. willing to help you out i think the kernel is automatically installed with your build when youre initializing/syncing repos and with commands in terminal its executed to build it. you can of course compile own kernel with modifications but as i said it needs lots of research, wish i could help you..
try for now some basics with the guide for gaining more experience and who knows what you will be capable of in next 2/3 months or less

aaz03 said:
Thanks mate, i'm gonna try this and gîve you some news, other advices for maybe add some optimizations like linaro and kernel adding for example? I'd like to just port Roms but maybe it would be interesting to build my own rom later
Edit: sorry didn't read the guide, find my answers, thank you
Click to expand...
Click to collapse
Here you got some useful video tutorial regarding kernel development with Linaro

MaHo_66 said:
Here you got some useful video tutorial regarding kernel development with Linaro
Click to expand...
Click to collapse
Ty , it 'd try , any other advice for kernel dev ?

aaz03 said:
Ty , it 'd try , any other advice for kernel dev ?
Click to expand...
Click to collapse
not that i know of, the tutorial should be explaining everything

How do we build Resurrection Remix,CyanogenMod,Crdroid,AOSP,etc?

Hi developers, I'm a newbie for developing Android. Can i ask you all? How do you build and develop Resurrection Remix,CyanogenMod,Crdroid,AOSP,etc? I want to build and develop my own rom,please?:crying: Thanks.

Look on their tutorials...

Having a separate computer for doing builds is a huge difference. The amount of storage and RAM it takes to build these ROMs is large. I have tried to build from source many times on my laptop. Get a dedicated build machine with enough memory and storage to complete the builds.

Rezei said:
Look on their tutorials...
Click to expand...
Click to collapse
I have been working on building from source for over a year now. I have followed many different tutorials for repo and building. I still have had no luck. I have not given up yet. Every video I have watched makes it look easy, but it is not that easy. Just now I have had gnults_handshake TCP errors when repo is going on. It isn't all that easy to debug Linux commands when building a build environment.

So I finally built CM 11, 12.1, and CM 13 from source. It took one successful build to make the difference. Good stuff!

Can you point me at one of those tutorials?
Thanks

They are on this website. Have a look around.

You need a complete linux distro , you must done a dual-boot it's better , linux alone is fah , and go to see guides for terminal commands you should use , in dual-boot you must have at less 200 Gb for the distro and then you're done with fews hours and days of patience

Man, I follow this tutorial.
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763/page1

Abdullah Yusoff said:
Hi developers, I'm a newbie for developing Android. Can i ask you all? How do you build and develop Resurrection Remix,CyanogenMod,Crdroid,AOSP,etc? I want to build and develop my own rom,please?:crying: Thanks.
Click to expand...
Click to collapse
You'll need few requirement to go :
- Hardware
- 8GB RAM (more is better)
- minimum dual core CPU
- minimum 150Go storage
- Some knowledge :
- For that, I recommend you to read pages on Android Developers AOSP, looks other commits to understand how does a device tree (or hw, kernel, etc..) work, and be curious each thing you don't understand on in a device tree, check what is it (e.g.: you see "libIon", check what is "libIon")
Good luck!