I have been compiling aokp,cm9,cm10 and even building my own kernels!
But i have not configured a way to compile a specific branch of cm9 yet! Havent had the need til now!
I suppose after repo i need to edit a local manifest and revisions!
Looking to compile cm9.1
guidance please Thanks!:laugh:
R-M-S said:
I have been compiling aokp,cm9,cm10 and even building my own kernels!
But i have not configured a way to compile a specific branch of cm9 yet! Havent had the need til now!
I suppose after repo i need to edit a local manifest and revisions!
Looking to compile cm9.1
guidance please Thanks!:laugh:
Click to expand...
Click to collapse
Repo init -u linkhere -b branchhere
Idk if that's what you meant though...
Sent from my HTC PH39100 using Tapatalk 2
R-M-S said:
I have been compiling aokp,cm9,cm10 and even building my own kernels!
But i have not configured a way to compile a specific branch of cm9 yet! Havent had the need til now!
I suppose after repo i need to edit a local manifest and revisions!
Looking to compile cm9.1
guidance please Thanks!:laugh:
Click to expand...
Click to collapse
When you do a repo init you need to swap in the branch you want to build for whatever is currently in the -b tag.
so... btag
-b ics 9.1.0
Click to expand...
Click to collapse
????
Related
I am downloading the CM source for ICS (repo init -u git://github.com/CyanogenMod/android.git -b ics)
I also see the lgics and lupohirp's branch on github. What is the difference between the the one I am downloading and the one on the other branch?
If I am not wrong its just their fixes made during porting? Just need to confirm this.
Suppose I want to build and make a rom with all lupohirp's fixes should i takes the files from https://github.com/lupohirp/cm_device_lge_p500 also and merge?
And https://github.com/lupohirp/cm_vendor_lge_p500 seems to have the vendor specific files which is needed for building the sources?
Cm9 does not have the device source for p500, therefore you need adams or lupohirps device sources
Sent from my GT-I9300 using xda app-developers app
_Arjen_ said:
Cm9 does not have the device source for p500, therefore you need adams or lupohirps device sources
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I assume if i download that code and try to build it, it will go on fine. Rather if i take the cm9 source for some other device and try to port it, I will get some errors and issues right? isnt that the correct way to start?
rohitsk said:
Thanks. I assume if i download that code and try to build it, it will go on fine. Rather if i take the cm9 source for some other device and try to port it, I will get some errors and issues right? isnt that the correct way to start?
Click to expand...
Click to collapse
After banging my head for sometime, i finally realized that we do have to download the CM source and then use adam/lupohirp's sources on top of it. Thanks.
I have started downloading the cm source for ICS. Any idea regarding how big it is?
rohitsk said:
I have started downloading the cm source for ICS. Any idea regarding how big it is?
Click to expand...
Click to collapse
Approx 6gb..
Sent from my LG-P500 using xda premium
I have had experiences with gentoo and wish to try my hands at developing my own AOKP rom for a chinese tablet that is unsupported.
I am currently syncing my repo and wish to understand more before I proceed.
What will be the easiest way to get Android running if I compile AOKP? Given that the tablet runs ICS at the moment, will it work if I compile AOKP and port the existing kernel over?
I have also gotten my hands on the source codes for the tablet.
Do you have a device tree?
If not, first you should create one.
Then only you can compile android.
adil_ said:
Do you have a device tree?
If not, first you should create one.
Then only you can compile android.
Click to expand...
Click to collapse
I highly doubt that there is an existing device tree. Now comes the noob question: How can I check if there is an existing device tree???
Anyway, I have been extensively reading up on building android and gotten the AOKP sources and original manufacturer source. Am I right to say that as long as I can compile AOKP, I should be able to boot using an existing kernel??
As for the the two sources, should I copy over the original devices and hardware folder to the AOKP source before I build so as to ensure a compatible build???
tobyhund said:
I highly doubt that there is an existing device tree. Now comes the noob question: How can I check if there is an existing device tree???
Click to expand...
Click to collapse
Google.
Anyway, I have been extensively reading up on building android and gotten the AOKP sources and original manufacturer source. Am I right to say that as long as I can compile AOKP, I should be able to boot using an existing kernel??
Click to expand...
Click to collapse
No it is not right to say. While it is possible you will probably need to do extensive debugging along the way.
As for the the two sources, should I copy over the original devices and hardware folder to the AOKP source before I build so as to ensure a compatible build???
Click to expand...
Click to collapse
Depends on what source you are talking about. What source do you have exactly?
You could try my thread here: http://forum.xda-developers.com/showthread.php?t=1935162
It does have some nice links to.
Hi Everyone,
I'm trying to download the SaberMod source and I'm using an older thread that has a source address of
https://github.com/SaberMod/android.git -b sm-jb-mr1
Click to expand...
Click to collapse
I believe the address is still correct but the branch I want to use is kitkat (at least not use jelly bean). Looking around on SaberMod's github I see SaberMod/GCC_SaberMod with various 4.X branches and I think those are the ones I need to select, but not sure. Should the repo address I use be
https://github.com/SaberMod/android.git -b kitkat
Click to expand...
Click to collapse
or choose one of the various 4.X version like this
https://github.com/SaberMod/android.git -b 4.10.0
Click to expand...
Click to collapse
or am I completely off?
hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/know.../open-devices/
feel free to fork, build, fix and push back
Br
J
reserved
@jerpelea
What about software binaries for Z Ultra? will Z1 do the job?
@jerpelea
Can you please share a bit more details about the precompiled kernel for other devices there at SonyXperiaDev's git is made from which sources?
So that by then we can compile a kernel.
I'll have a look tonight and see if there is anything I can try
I'm trying to build aosp 5 using z1 binaries from the sony dev site at the moment
blueether said:
I'll have a look tonight and see if there is anything I can try
I'm trying to build aosp 5 using z1 binaries from the sony dev site at the moment
Click to expand...
Click to collapse
you and me both but at the same time i'm following @jerpelea guide to build lollipop with new binaries
My VM takes ages to compile
blueether said:
I'll have a look tonight and see if there is anything I can try
I'm trying to build aosp 5 using z1 binaries from the sony dev site at the moment
Click to expand...
Click to collapse
I have been trying since almost one week.
Have been stuck at points i couldnt get past.
Lets hope this time something sweet comes :angel:
Many thanks jerpelea.
A device-sony-togari repository is referenced in the readme for the rhine common device tree, but It's not yet public. Can we expect this, along with togari specific binaries any time soon?
Compiling Sucessfull
Not made with lollipop binaries.
#### make completed successfully (02:10:52 (hh:mm:ss)) ####
Anyone care to try? I'm not responsable for any bricking or the cat in the house catching fire.
Saatvik Shukla said:
@jerpelea
Can you please share a bit more details about the precompiled kernel for other devices there at SonyXperiaDev's git is made from which sources?
So that by then we can compile a kernel.
Click to expand...
Click to collapse
the kernel is precompiled from the kernel repo of the sonyxperiadev git. (latest 3.5 branch should be used for compiling).
May i suggest adding "5.0" or "lollipop" to the thread title?
tsiros said:
May i suggest adding "5.0" or "lollipop" to the thread title?
Click to expand...
Click to collapse
Yeah, that would draw some extra attention. Maybe a mod can add it?
you can use honami blobs but kernel and dts have to be recompiled from unified kernel source
kernel is same unified kernel and has all configs for togari
please be patient and we will add new devices soon
br
J
Ok... building kernel right now... let's see
Sm0L said:
Compiling Sucessfull
Not made with lollipop binaries.
#### make completed successfully (02:10:52 (hh:mm:ss)) ####
Anyone care to try? I'm not responsable for any bricking or the cat in the house catching fire.
Click to expand...
Click to collapse
Sure bring it on. Still animal crulety is not fun
KalleEatingBrain said:
Sure bring it on. Still animal crulety is not fun
Click to expand...
Click to collapse
You probably should check out this thread.
updated guide and blobs for android Lollypop version 5.0.1
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
jerpelea said:
updated guide and blobs for android Lollypop version 5.0.1
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Click to expand...
Click to collapse
Thanks for the hard work. AOSP id my daily at the moment, only real bug seems to be that cores 1-3 don't go off line (it is using CM's kernel at the moment as the AOSP one had more bugs I think)
blueether said:
Thanks for the hard work. AOSP id my daily at the moment, only real bug seems to be that cores 1-3 don't go off line (it is using CM's kernel at the moment as the AOSP one had more bugs I think)
Click to expand...
Click to collapse
cm and aosp in this moment are same kernel
br
J
jerpelea said:
cm and aosp in this moment are same kernel
br
J
Click to expand...
Click to collapse
blueether said:
Thanks for the hard work. AOSP id my daily at the moment, only real bug seems to be that cores 1-3 don't go off line (it is using CM's kernel at the moment as the AOSP one had more bugs I think)
Click to expand...
Click to collapse
Cm11 kernel to be precise.
If I remember right cm12 kernel didn't boot at all.
hi everyone
i was going to try building a kernel for .131 rom but i couldnt find anything over on github
if any have it can you please share?
Here
hxxp://developer.sonymobile.com/downloads/xperia-open-source-archives/
You have success?
Does it work on e2312 (Aqua dual)?
Dell Schulz said:
You have success?
Click to expand...
Click to collapse
im working on it as a hobby on my free time
soo it wont be opertional anytime soon
https://github.com/sonyxperiadev/kernel-copyleft/commits/26.3.A.1.xxx
there's kernel repo for AOSP and opensource ROMs (https://github.com/sonyxperiadev/kernel)
and kernel-copyleft for Sony's "Stock" ROMs (https://github.com/sonyxperiadev/kernel-copyleft) ,
for additional drivers (e.g. FM/Bluetooth, etc.) you'll need the opensource driver tarball from https://developer.sonymobile.com/do...n-source-archive-for-26-3-a-1-33-26-3-b-1-33/