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
Related
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, I have a samsung Galaxy Tab 4 10.1 tablet but it has very small developer community so I couldn't find any AOSP roms suitable with my device. Is it possible to make an AOSP rom work on my tab or is it possible to build rom for my tab? Please help, thanks in advance.
Sent from my SM-T530 using XDA Premium 4 mobile app
mhmtemnacr said:
Hi, I have a samsung Galaxy Tab 4 10.1 tablet but it has very small developer community so I couldn't find any AOSP roms suitable with my device. Is it possible to make an AOSP rom work on my tab or is it possible to build rom for my tab? Please help, thanks in advance.
Sent from my SM-T530 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you have knowledge in making a whole new device tree from scratch, then it'll be possible. But you also need to find the right kernel source. For building AOSP from source you need 3 components:
device tree
kernel source
vendor tree
If you have these 3, you can start building.
GeekyDroid said:
If you have knowledge in making a whole new device tree from scratch, then it'll be possible. But you also need to find the right kernel source. For building AOSP from source you need 3 components:
device tree
kernel source
vendor tree
If you have these 3, you can start building.
Click to expand...
Click to collapse
Hi, thanks for reply. I don't know how to obtain those. Is there a noobish-written tutorial or something to help me get started? And, can I find these kernel sources, etc in the http://opensource.samsung.com/ because my device is samsung.
mhmtemnacr said:
Hi, thanks for reply. I don't know how to obtain those. Is there a noobish-written tutorial or something to help me get started? And, can I find these kernel sources, etc in the http://opensource.samsung.com/ because my device is samsung.
Click to expand...
Click to collapse
There is no tutorial for this. But you can take an example: https://github.com/CyanogenMod/android_device_samsung_i9300
This is a device tree for Samsung Galaxy S3 International version. You can get all these from your device itself. For vendor look here: https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-11.0/i9300
But vendor is very easy. But I don't think you can make it as for now. I think you should first start building a ROM for a device which has all his dependencies on CM's repo. Start with this tutorial: http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
Read through this http://forum.xda-developers.com/showthread.php?t=2195858
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.
Does someone wants to help me making an AOSP device tree?
Would bring some more roms to our device
I already started with a branch and commented out some compiling errors:
https://github.com/benschhold/android_device_oneplus_oneplus2/tree/aosp
Any help is appreciated.
@regalstreak
maybe something for you if you are interested
benschhold said:
@regalstreak
maybe something for you if you are interested
Click to expand...
Click to collapse
The problem is the kernel source. Ain't it? We need to rebegin from the plain linux kernel src imo idk
regalstreak
regalstreak said:
The problem is the kernel source. Ain't it? We need to rebegin from the plain linux kernel src imo idk
regalstreak
Click to expand...
Click to collapse
angler custom kernel work on both cm/aosp so i didnt thought about that
and isnt oxygen stock kernel aosp + oneplus patches? maybe we could start from there
benschhold said:
angler custom kernel work on both cm/aosp so i didnt thought about that
and isnt oxygen stock kernel aosp + oneplus patches? maybe we could start from there
Click to expand...
Click to collapse
Oxygen is based on caf so it is difficult. But not impossible. Did you build tho? We can get it booting easily. But ril and some stuff womt work.
regalstreak
regalstreak said:
Oxygen is based on caf so it is difficult. But not impossible. Did you build tho? We can get it booting easily. But ril and some stuff womt work.
regalstreak
Click to expand...
Click to collapse
im currently stuck at busybox error which i couldnt solve but not sure if its device related, tried on screwd rom and that have a lot of optimizations which cought caused that
i have to try again on another aosp source
benschhold said:
im currently stuck at busybox error which i couldnt solve but not sure if its device related, tried on screwd rom and that have a lot of optimizations which cought caused that
i have to try again on another aosp source
Click to expand...
Click to collapse
Make pure aosp source. And clone busybox from cm if its still not fixed. Its not a device error.
regalstreak said:
Make pure aosp source. And clone busybox from cm if its still not fixed. Its not a device error.
Click to expand...
Click to collapse
yep, im syncing
will try cm busybox if errer persists
benschhold said:
yep, im syncing
will try cm busybox if errer persists
Click to expand...
Click to collapse
screwd rom woo my fav rom !!
Sent from my ONE A2003 using XDA-Developers mobile app
does someone know where to define where kernel source is stored?
the typical TARGET_KERNEL_SOURCE is not working
when to try to build inline its always looking in out/ folder
Man, wish I could help but lack the skills.. Plenty of Linux machines on hand though.. Where do I start?
@benschhold, @King_lilrowrow wrote on his Twitter acc about 20 days ago he built NX Rom using only AOSP code. Doesn't that mean he had to make an AOSP tree? I would ask him for help
MaxtremePL said:
@benschhold, @King_lilrowrow wrote on his Twitter acc about 20 days ago he built NX Rom using only AOSP code. Doesn't that mean he had to make an AOSP tree? I would ask him for help
Click to expand...
Click to collapse
Trees or it didn't happen!
builds are going through compiling now
but are not booting
lets see
benschhold said:
builds are going through compiling now
but are not booting
lets see
Click to expand...
Click to collapse
Take your time [emoji1] [emoji7]. Can't wait. I have always loved pure AOSP
Sent from my ONE A2003 using Tapatalk
benschhold said:
builds are going through compiling now
but are not booting
lets see
Click to expand...
Click to collapse
Post some logcat, maybe we can help
WaxLarry said:
Post some logcat, maybe we can help
Click to expand...
Click to collapse
as far as i now its not possible to take one when not passing oneplus logo
i just compile another one and lets hope for the best :fingers-crossed:
i've already built aosp for lg g3.. i'm downloading right now n-preview2 sources i will help, i'll let you know once i will have everything ready
benschhold said:
as far as i now its not possible to take one when not passing oneplus logo
i just compile another one and lets hope for the best :fingers-crossed:
Click to expand...
Click to collapse
The problem is the kernel, i've already had this kind of problem.
Are you compiling your own kernel? If yes, which sources?
Basically in lollipop the kernel is compiled uncompressed with appended dtb, since MM, kernel is compressed and dtb is included in kernel.
WaxLarry said:
The problem is the kernel, i've already had this kind of problem.
Are you compiling your own kernel? If yes, which sources?
Basically in lollipop the kernel is compiled uncompressed with appended dtb, since MM, kernel is compressed and dtb is included in kernel.
Click to expand...
Click to collapse
no i went back to screwd cause aosp just wont find my kernel source
i fckd it up elsewhere
there is a solution for this. set in your baord config like this
Code:
BOARD_CUSTOM_BOOTIMG_MK := device/oneplus/oneplus2/mkbootimg.mk
and take the file from cm for example
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/