Here anyone can give me clues why i'm getting this errors?I searched on Google but didn't get any proper solutions.I'm building a cynogenmod rom from the source and following cm guide.I need help.
Thanks in advance.
Røbin said:
Here anyone can give me clues why i'm getting this errors?I searched on Google but didn't get any proper solutions.I'm building a cynogenmod rom from the source and following cm guide.I need help.
Thanks in advance.
Click to expand...
Click to collapse
Most of the errors you can ignore. Only concentrate on the error thats actually stopping the build. I don't know the spec of your pc but you need as much free space on your drive as you can get, at least 50 Gb.. 100 Gb is better.. Also an minimum of 4 Gb RAM, 8 Gb is better and so on for a near error free build.. If someone wants to build MM on a old machine, it becomes difficult as the spec of the machine plays a huge part in the build process.. @Daedroza has given you the commands and tips/tricks but i personally think the problems are with the spec of your machine and/or the setup..
hagar006 said:
Most of the errors you can ignore. Only concentrate on the error thats actually stopping the build. I don't know the spec of your pc but you need as much free space on your drive as you can get, at least 50 Gb.. 100 Gb is better.. Also an minimum of 4 Gb RAM, 8 Gb is better and so on for a near error free build.. If someone wants to build MM on a old machine, it becomes difficult as the spec of the machine plays a huge part in the build process.. @Daedroza has given you the commands and tips/tricks but i personally think the problems are with the spec of your machine and/or the setup..
Click to expand...
Click to collapse
In virtual box I set hard disk to 80gb to store all the necessary files and tools and my pc have 4gb ram so virtual box suggested me to only use minimum 2gb of ram.So should I now give the full ram power to the building process?
Worth a try brother.. My machine has 4gb RAM but it also gave errors building MM.. Recommendations are for 8 or more gb RAM.. AOSP for lp is also taking a massive amount of resources on the machine..
hagar006 said:
Worth a try brother.. My machine has 4gb RAM but it also gave errors building MM.. Recommendations are for 8 or more gb RAM.. AOSP for lp is also taking a massive amount of resources on the machine..
Click to expand...
Click to collapse
Didn't work. pc hang and need to restart.So maybe I need to virtually increase the ram somehow.
hagar006 said:
Worth a try brother.. My machine has 4gb RAM but it also gave errors building MM.. Recommendations are for 8 or more gb RAM.. AOSP for lp is also taking a massive amount of resources on the machine..
Click to expand...
Click to collapse
Did you check log that I attached? Dose that really mean my pc don't have enough amount of resources?
Yes I looked at the log and getting a whole ream of errors is usual but only concentrate on the error that stopped the build.. I personally would use the command "make clean", hand over more RAM to the VM and start the build again..
hagar006 said:
Yes I looked at the log and getting a whole ream of errors is usual but only concentrate on the error that stopped the build.. I personally would use the command "make clean", hand over more RAM to the VM and start the build again..
Click to expand...
Click to collapse
i can't set more than 3gb ram for virtual box.so 3gb is enough?and cleaning just waste my time but no good results
No, those are very poor specs for building ROM. I have 8 gigs DDR4, i7-6700 with water-cooling(<-- water cooling was to exaggerate ).
I don't use VMbox, and my builds usually finish in 40 minutes on HDD.
Regarding this thread post #59 everybody gets build errors and they are very verbose. Fix it yourself if you want to learn and google will help you as it help me(You were really asking easy ones bro you didn't even knew basic fixing deps)
Building with VMbox with low-specs is a long shot.
Before creating more threads and queries :
repo sync -j4
source build/envsetup.sh
breakfast dogo
make clean
make bacon -j16 (If you keep getting different errors, reduce 16 --> 8 --> 4 and also use make clean everytime).
Daedroza said:
No, those are very poor specs for building ROM. I have 8 gigs DDR4, i7-6700 with water-cooling(<-- water cooling was to exaggerate ).
I don't use VMbox, and my builds usually finish in 40 minutes on HDD.
Regarding this thread post #59 everybody gets build errors and they are very verbose. Fix it yourself if you want to learn and google will help you as it help me(You were really asking easy ones bro you didn't even knew basic fixing deps)
Building with VMbox with low-specs is a long shot.
Before creating more threads and queries :
repo sync -j4
source build/envsetup.sh
breakfast dogo
make clean
make bacon -j16 (If you keep getting different errors, reduce 16 --> 8 --> 4 and also use make clean everytime).
Click to expand...
Click to collapse
I googled every problem that I faced but no specific result was found.I need to understand those errors meanings but can't get any help from Google. So I needed help from experienced developer like you.Yes now I know and can understand some errors that require tools to solve it but those java error are complicated for me to understand.So I'm now trying again from the beginning following your tips.But as you said my pc spec are old to build a rom so maybe this will be my last try.I need to upgrade my pc first.I have a question if my pc spec not good enough to build cm13 so can I build old custom android version like lollipop or kitkat?because someone (can't remember his name)told me cm13(Android Marshmallow) need higer spec to build.
Daedroza said:
No, those are very poor specs for building ROM. I have 8 gigs DDR4, i7-6700 with water-cooling(<-- water cooling was to exaggerate ).
I don't use VMbox, and my builds usually finish in 40 minutes on HDD.
Regarding this thread post #59 everybody gets build errors and they are very verbose. Fix it yourself if you want to learn and google will help you as it help me(You were really asking easy ones bro you didn't even knew basic fixing deps)
Building with VMbox with low-specs is a long shot.
Before creating more threads and queries :
repo sync -j4
source build/envsetup.sh
breakfast dogo
make clean
make bacon -j16 (If you keep getting different errors, reduce 16 --> 8 --> 4 and also use make clean everytime).
Click to expand...
Click to collapse
Hello sir please for the last time help me with this,I"m now building rom using architekt in VB and its default java jdk version is 6 but i want to change it to 7.I"ve tried your given command but its showing command not found.what should i do?i can use command to sync repo,and other command to download and setup all other thing to prepare build environment.Solution for architekit is very rare in google.So i need some help.This is the link for architekit that i found in google http://nathanpfry.com/architekt/
EDITroblem Solved and founded solution.
Related
Hello everyone,
I want to start theming and because I'm unsure of some stuff, I'm asking for help.
After some Googling, I found out that to start making CM7 Theme Chooser themes I have to download the CyanogenMod 7 source code first. I found this video that shows how to download all the necessary stuff. But here's the thing.
I'm running Ubuntu 10.04 installed with WUBI (inside Windows 32-bit) and I have only 7GB free space on my C drive for Ubuntu. If it is necessary, I can reinstall and give it more space. Also, I haven't installed Java and the Android SDK yet.
The guy on the video says that it will take aprox. 2 hours to download the source code. I'm guessing that the size of the code is huge.
I have also read that you need a very "strong" computer to compile the CM7 source (I don't know if this applies here).
Having said all those, is my computer able to handle these and do I have enough free space?
Can't I just download the T-Mobile part instead of the whole source code?
A pc with 4gb ram and i5 cpu need about 0.5 hour to compile cm7 source...
But I need it just for themes. Can't I download just the T-Mobile source?
Sent from my X8 using XDA
CM7 sources eats up approx 50gb of your drive.
Why not start with a dummy rom to theme? (Im not certain)
i dont think so for theming you need whole cm7 source...just need to learn xml...i know somewhere on xda a TUT....lemme find it...
cm6 source code was 11.6 gb....and i guess cm7 source is somewhere around 22.xx gb
My interenet connection is darn slow (40 kb/s...lmfao)...otherwise i would have my own sources P...lol)....if anybody can upload it....well downloading tons of gb without able resume it is painful....
PS-i have cm6 source....it took nearly 8-10 days to download....net bill was huge !!! and my dad nearly threw me out of the house...anyway who uses froyo now...
EDIT-link: http://forum.xda-developers.com/showthread.php?t=964391
Thanks for the link. Gonna use that one because I really don't see the point in downloading the whole CM7 source.
Thread solved.
--- copied with permission from nathanpfry.com ---
Hi everyone! Have you ever wanted to compile your own nightlies, but are too intimidated or "not a dev"?
For various reasons, I've decided to write a guide about how you too can enter the wonderful world of development.
Before we begin, I'm going to say one thing. I'll probably repeat it a bunch of times too, to be sure everyone reads it at least once while skimming through this. PLEASE GOOGLE YOUR QUESTION FOR AT LEAST 5 MINUTES BEFORE ASKING IT HERE. The main reason I wrote this guide is to try to refocus the point of the "Development" forums on XDA. There are many users out there that seem to think this is a place to make demands for answers without trying to contribute or learn anything themselves. Developing isn't an easy thing. You should know a little bit of Linux going into this, if not, prepare yourself for some reading. This isn't the place for you to ask how to install Ubuntu, or why you need 64 bit. Just have a little faith and trust me.
Major thanks goes out to Hashcode.. Seriously, you have no idea what an inspiration he's been. For all intents and purposes, this guide will show you how to set up your system and compile ROMs based on his work, perhaps even help work on fixes. I suppose I should thank google, cyanogenmod, team aokp, thingonaspring (minimoto rocks!) a few others. You know who you are.
On with the show.
Here's a list of things you will need:
1) A decent computer (at least dual core, 2+ gig of RAM, 50 gig free HD space) capable of running Linux
2) A copy of Builduntu
3) Spare time and the desire to learn.
Double check that your main system is 64 bit. 32 bit OS will not work!
Once you get Builduntu up and running (there are instructions @ the above link), read on.
You need to make a decision. What flavor of Android do you want to compile? In other words, AOKP, Cyanogenmod, AOSP, LiquidSmooth, SimpleAOSP etc etc etc.
For the purposes of teaching everyone, I'm going to base this guide on AOKP.
You've made it this far, you're basically almost there. *cue motivational montage music*
When Builduntu says, "initialize the build repo", that means to sync your source code with a git repository. Run these commands in a terminal:
Code:
mkdir ~/android
Code:
cd ~/android
The following command will do the actual initialization:
Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b jb-mr1
Ok, after this next part you're going to want to take a break. It's time to actually download to your computer (sync) the source code. As of writing this guide, it is over 10 gigabytes of information, depending on which "flavor" of Android. In the terminal:
Code:
repo sync
Don't worry, just execute and walk away. Depending on the speed of your internet connection, this could take a long time. Anywhere from one hour to "maybe-you-should-do-this-before-you-go-to-sleep". Up next is actually doing the compiling.
When that finishes, you have the source code. Let's get to business. This next bit will probably take a while also, but again, it's a set-it-and-forget-it situation.
Code:
cd ~/android
source build/envsetup.sh
lunch yourdevicenamehere
make otapackage
That should do it! Watch for errors, but everything should work at this point. Again, how long this takes is completely dependent on how fast your computer is. If it completes without a hitch, you'll have a flashable zip file located in ~/android/out/target/product/yourdevicename/
Congrats, you just compiled from source! Now, if you really want to get adventurous, you can start delving into the code itself and make some changes. But this post isn't the place to get into all that. Good luck, and please say thanks if this guide was helpful!
PLEASE PLEASE PLEASE If you happen to find an error in my guide (not just a question about it!) PLEASE PM ME. I will give you credit in the post. A potentially useful fix could be buried pages deep in the thread and unfortunately get lost if it's only a reply. Thanks!
Many thanks!
Although I didn't tried this howto yet, I feel obligated to thank you for this. In the past I though about trying to do something directly tweaking the code and, who knows, contribute with something nice to our "D3 society". But could never figure how to start it. I will spend some time trying to make it work using this "manual" and give some feedback about it.
Again, thanks.
Re: [DIY] How To Compile Your Own Nightlies (and Learn Something in the Process)
Great post.
Sent from my XT926 using Tapatalk 2
Thank you for taking the time to show the community how to contribute and give back what has been given.
Thanks for this awesome guide! I followed your directions and did produce a zip that I can flash with safestrap. Unfortunately it will not boot though:crying: Is there anything else to do with the kexec zip to make it safestrap compatible? Or did I just screw something up
Either way I am glad I did this and without your 2 great guides I never would have. So thank you again sylentprofet! :highfive:
Caldair said:
Thanks for this awesome guide! I followed your directions and did produce a zip that I can flash with safestrap. Unfortunately it will not boot though:crying: Is there anything else to do with the kexec zip to make it safestrap compatible? Or did I just screw something up
Either way I am glad I did this and without your 2 great guides I never would have. So thank you again sylentprofet! :highfive:
Click to expand...
Click to collapse
Hmmmmmm. That is a frustrating problem. I've had it happen before..
Just tried a compile myself, and CM10 doesn't work. Silly me for thinking that everything would go smoothly. It could be some changes reflected recently on CM's end. The joys of development!
However, I just tried an AOKP 4.2 build, and it does boot. So I'm going to make some quick changes to the guide to reflect building for AOKP while I examine the code and see what's up.
There's nothing more frustrating when a build completes successfully and then won't flash. I'll keep everyone posted.
this looks amazing
thank you for spending the time to write this up!
May be up for a reinstallation of my Ubuntu (currently 12.04 x86 :/).
Wonderful, might try to adapt for the galaxy note 3.
Lillie via LG Spectrum (waiting for N3 DE) & tapatalk
*EDIT* This thread is now based upon the work by @fattire and @slayher, who got it up on the 910T. For that phone see this thread: http://forum.xda-developers.com/not...nt/unoffcial-cm-12-0-t-mobile-note-4-t2964887
This thread is for dev's interested to help out porting CM12 to our device. I've researched for info regarding CM ports and good information is actually quit scarce. A dev might post something like 'hmm stuck at boot anim' and then the next day 'got it, booting now !' without explaining what he did to solve it. I want to change that, so this thread can serve as a guide for other first time porters too (this is also my first porting project), documenting every step as in much detail as possible.
For ROMS: http://forum.xda-developers.com/not...official-cm-12-0-910f-note-4-trltexx-t2987412
Please use this thread for R&D/development ONLY !!!
Ok, I'm really starting from scratch and never done any phone ROM porting. I've just made a new virtual disk running ubuntu and am currently downloading the CM12 repo. I figured, how to get even started here. I figured that the goals we need to attain in this order:
1) compile the kernel samsung supplied
2) make sure we can boot into kernel
3) get ADB up and running
4) get CM12 starting up, even the bootanim alone would be a nice goal to reach
5) Booting into homescreen
6) Fixing all stuff like modem, wifi etc etc etc
Anyway, I'm currently downloading CM12 sources as we speak ...
This is by the way a link I found very useful: http://www.androidenea.com/2009/08/init-process-and-initrc.html It describes the Android init process, cause I was wondering, how to even start all this ? How to get from kernel to CM booting: that's where init.rc should come into play of course
Good luck this is a long project. I build carbonrom for another phone where everything for cm was allready fixed. I would start with a phone that allready has support to learn how the process goes. You can brick your phone and it's a process of trail and error... But I hope you manage good luck!
KaptKeefmenneke said:
Good luck this is a long project. I build carbonrom for another phone where everything for cm was allready fixed. I would start with a phone that allready has support to learn how the process goes. You can brick your phone and it's a process of trail and error... But I hope you manage good luck!
Click to expand...
Click to collapse
I'm not sure I understand what you mean ? If the phone already has support, then what's there to port ? Or do you mean building CM itself ? That I've done quite a few times already, did quite a bit of work on the i9500, fixing RILD issue's, kernel issue's and other stuff.
soo...maybe m wrong (has been a while snce ive ported) but im goin to drop a few lines anyhow......
porting is very different from source building.....the only reason you would need to dl the cm sources would be to compile the rom using sources...and right now the note 4 has none we would need device,kernel,common,vendor sources for that....so... we cant source build right now only port....sp what we need to do is research which device officially or unofficially that has cm with same specs as the note4 things like screen size, board, things of that nature....and would highly recommend using the same carrier as well.....but once we have that info....dl that phones cm rom zip....dl one of our phones rom zips.....now for the fun....ill lay out a way i did it maybe is the same still ...
place both cm zip and note 4 zip on desktop..
create a new folder call it new
drag all files from the cm zip into the new
open the new and open the note 4 zip have them side by side
now your going to drag pretty much all folders/files from the note 4 system folder into the new sytsem folder one folder at a time excluding:
app,priv-app,etc,fonts,media,framework,xbin (im probably forgetting one or two but has been a long time)
now the fun begins....time to edit some xmls and trial and error on pretty much everything until it is working right
you are also going to want to change out the kernel and have to edit the updater-script in the meta-inf....
im positive im forgetting a few things but this is pretty much what i can remember......from off the top of my head...some of the guides ill link in a bit will go into greater detail and explain things more in depth
a few links ive had bookmarked that will help ya
http://forum.xda-developers.com/showthread.php?t=1908008
http://forum.xda-developers.com/showthread.php?t=732957
http://forum.xda-developers.com/showthread.php?t=1957219
http://forum.xda-developers.com/showthread.php?t=1272270
http://forum.xda-developers.com/showthread.php?t=2113479
http://forum.xda-developers.com/showthread.php?t=1801690
http://forum.xda-developers.com/showthread.php?t=2251719
http://forum.xda-developers.com/showthread.php?t=1941239
http://forum.xda-developers.com/showthread.php?t=1805408
http://forum.xda-developers.com/showthread.php?t=2058850
all of these links in one way or another have helped me during my porting phase hope they do the same for you ...like ive said before im more of a source builder so thats what imgoing to be trying to do is getting a working tree... but if you need help just hit me up ill do what i can
Shouldn't this thread be in general?
jdidtht said:
Shouldn't this thread be in general?
Click to expand...
Click to collapse
yes it really should being as there is no development only discussion...but thats the moderators job not mine
spleef said:
yes it really should being as there is no development only discussion...but thats the moderators job not mine
Click to expand...
Click to collapse
Threads regarding R&D belong in development, so I guess it really belongs here. Even more so cause if it's moved to general, tons of n00bs will join in and destroy the thread. please keep this developers only.
Anyway thanks to see you join in Spleef, much appreciated !! Still setting up my environment myself ...
spleef said:
soo...maybe m wrong (has been a while snce ive ported) but im goin to drop a few lines anyhow......
porting is very different from source building.....the only reason you would need to dl the cm sources would be to compile the rom using sources...and right now the note 4 has none we would need device,kernel,common,vendor sources for that....so... we cant source build right now only port....sp what we need to do is research which device officially or unofficially that has cm with same specs as the note4 things like screen size, board, things of that nature....and would highly recommend using the same carrier as well.....but once we have that info....dl that phones cm rom zip....dl one of our phones rom zips.....now for the fun....ill lay out a way i did it maybe is the same still ...
place both cm zip and note 4 zip on desktop..
create a new folder call it new
drag all files from the cm zip into the new
open the new and open the note 4 zip have them side by side
now your going to drag pretty much all folders/files from the note 4 system folder into the new sytsem folder one folder at a time excluding:
app,priv-app,etc,fonts,media,framework,xbin (im probably forgetting one or two but has been a long time)
now the fun begins....time to edit some xmls and trial and error on pretty much everything until it is working right
you are also going to want to change out the kernel and have to edit the updater-script in the meta-inf....
im positive im forgetting a few things but this is pretty much what i can remember......from off the top of my head...some of the guides ill link in a bit will go into greater detail and explain things more in depth
a few links ive had bookmarked that will help ya
http://forum.xda-developers.com/showthread.php?t=1908008
http://forum.xda-developers.com/showthread.php?t=732957
http://forum.xda-developers.com/showthread.php?t=1957219
http://forum.xda-developers.com/showthread.php?t=1272270
http://forum.xda-developers.com/showthread.php?t=2113479
http://forum.xda-developers.com/showthread.php?t=1801690
http://forum.xda-developers.com/showthread.php?t=2251719
http://forum.xda-developers.com/showthread.php?t=1941239
http://forum.xda-developers.com/showthread.php?t=1805408
http://forum.xda-developers.com/showthread.php?t=2058850
all of these links in one way or another have helped me during my porting phase hope they do the same for you ...like ive said before im more of a source builder so thats what imgoing to be trying to do is getting a working tree... but if you need help just hit me up ill do what i can
Click to expand...
Click to collapse
Great addition to the thread ! Hmm I haven't done any porting myself. I figured once we have a kernel up (compiling it should be easy), then what's stopping us from booting CM ? I mean of course RILD won't work if we don't have a JNI (or what's it called on ART, ANI ? ) interface to the modem. Of course we won't have NFC, internet, telephony, all that. But merely booting a graphical interface that should be doable with Nexus 6 source code, right ? I mean all we need is SoC sources so we have cpu & graphics working, right ? So That was what I had in mind myself but your approach actually is quite the same now I think of it
Thread is moved to general AGAIN. Hehe. Starting a development thread ON XDA and have it in the developer section seems harder than porting CM12 Anyway I guess it doesn't matter in which section it is, as long as n00bs and trolls stay out and we can focus on development only.
Anyway, downloading kernel sources as we speak ...
BTW, here is Nexus 6 source code: http://www.xda-developers.com/android/google-nexus-6-factory-images/
Going to down that right now too ...
Ok, building kernel as we speak. I just installed the arm-eabi-4.7 toolchain, like this:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/
And then edited the makefile and issued the 3 commands all as specified in README_Kernel.txt from the Samsung Kernel. So far so good
And yes, as expected, build breaks:
drivers/scsi/ufs/ufs_test.c:25:19: fatal error: ../sd.h: No such file or directory
compilation terminated.
make[3]: *** [drivers/scsi/ufs/ufs_test.o] Error 1
make[2]: *** [drivers/scsi/ufs] Error 2
make[1]: *** [drivers/scsi] Error 2
make: *** [drivers] Error 2
Hehe, Samsung wouldn't be Samsung if they would supply a kernel that actually builds from the start Going to investigate ...
Actually that seems like an easy fix, just linked the file correctly
And a new break:
In file included from drivers/gud/MobiCoreDriver/logging.c:21:0:
drivers/gud/MobiCoreDriver/main.h:24:22: fatal error: platform.h: No such file or directory
I'd say it's looking for the file in platforms/MSM8960_SURF_STD, going to link it correctly ...
And building again ...
n file included from drivers/video/msm/mdss/mdss_mdp_trace.h:255:0,
from drivers/video/msm/mdss/mdss_mdp.c:61:
include/trace/define_trace.h:79:43: fatal error: ./mdss_mdp_trace.h: No such file or directory
Include should point to kernel includes, fixing it again
And building again ...
Code:
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
LZO arch/arm/boot/compressed/piggy.lzo
AS arch/arm/boot/compressed/piggy.lzo.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
Kernel ready Of course that was the easy part, hehe, but still, progress. Tomorrow going to start with the difficult part, getting CM up
I've ported before but only tw where it was mainly framework edits. Never worked with cm before but like the op I'm keen to learn. If i can help at all just let me know, I use linux mint myself rather than Ubuntu but they're very similar
So, just downloaded Nexus 6 sources. It seems that directory /device/moto/shamu contains the device hardware stuff we need ! Going to research some more today ...
*EDIT* also mind the propietary-blobs.txt in that directory. I'm still waiting for my Note 4 myself (hopefully friday), but this needs to be compared with the files on the device, cause if they exist, they will be blobs of course and we need them.
Hey, as alot of us know many people have left this phone and moved on to the cooler more exciting phones. and are busy with life.....id like to request a guide for the ones that would like to make some creation and learn how to build...for the love of this phone ^-^and that have some knowledge atleast
Xendrix said:
Hey, as alot of us know many people have left this phone and moved on to the cooler more exciting phones. and are busy with life.....id like to request a guide for the ones that would like to make some creation and learn how to build...for the love of this phone ^-^and that have some knowledge atleast
Click to expand...
Click to collapse
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984 I tried with this but I was getting to much rejects and I couldn't fix them all by my self. Most likely because I was trying to patch the stock 64 bit. But you have the CM, RaptorROM that are more vanilla like. If you are lucky you should be getting less rejects then me. :highfive:
denny.hell said:
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984 I tried with this but I was getting to much rejects and I couldn't fix them all by my self. Most likely because I was trying to patch the stock 64 bit. But you have the CM, RaptorROM that are more vanilla like. If you are lucky you should be getting less rejects then me. :highfive:
Click to expand...
Click to collapse
Ok cool i just pulled that same guide up, ill try it out and see where i get!
Sent from my iPhone using Tapatalk
Xendrix said:
Ok cool i just pulled that same guide up, ill try it out and see where i get!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If you need help with the rejects just ask. I'm sure I could spare some time to help out
denny.hell said:
http://forum.xda-developers.com/android/software/guide-build-port-miui-rom-to-device-t3250984 I tried with this but I was getting to much rejects and I couldn't fix them all by my self. Most likely because I was trying to patch the stock 64 bit. But you have the CM, RaptorROM that are more vanilla like. If you are lucky you should be getting less rejects then me. :highfive:
Click to expand...
Click to collapse
That was really not all that great of an instruction on how to get started with rom building because for 1 unless you have a really super fast computer trying to do that in a VMWARE is going to take forever because the first compile and build takes hours upon hours I'm not kidding when I said you needed to download the entire CyanogenMod or AOSP source code and apparently from all the changes people have made its up over 13GB which is huge mind you the first build is going to give quite a few errors which you'll need to fix by going into your github and making changes to the specific file that needs changing and then repo sync or just change it on your local computer first then push it to github.. You did fork the device tree to your own github right? Then you have to download the device tree source to your local pc in order to even begin building anything. They also need to be in the correct spot by the way or the build is gonna throw an error that it can't find / or so and so doesn't exist.. By the way the 3 device tree files you're gonna need are "Device, Vendor and Kernel.."..
https://wiki.cyanogenmod.org/w/Development
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
MrMike2182 said:
That was really not all that great of an instruction on how to get started with rom building because for 1 unless you have a really super fast computer trying to do that in a VMWARE is going to take forever because the first compile and build takes hours upon hours I'm not kidding when I said you needed to download the entire CyanogenMod or AOSP source code and apparently from all the changes people have made its up over 13GB which is huge mind you the first build is going to give quite a few errors which you'll need to fix by going into your github and making changes to the specific file that needs changing and then repo sync or just change it on your local computer first then push it to github.. You did fork the device tree to your own github right? Then you have to download the device tree source to your local pc in order to even begin building anything. They also need to be in the correct spot by the way or the build is gonna throw an error that it can't find / or so and so doesn't exist.. By the way the 3 device tree files you're gonna need are "Device, Vendor and Kernel.."..
https://wiki.cyanogenmod.org/w/Development
https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Click to expand...
Click to collapse
Yes, everything you said is correct. I was only giving him a starting point. I know that porting, in this case patching, is a lot more easier than building, if done properly. If he wants to build and to learn a lot of stuff I personally advice him to follow your advice.
But in the end it's up to him. At least now he has two starting points. :highfive:
denny.hell said:
Yes, everything you said is correct. I was only giving him a starting point. I know that porting, in this case patching, is a lot more easier than building, if done properly. If he wants to build and to learn a lot of stuff I personally advice him to follow your advice.
But in the end it's up to him. At least now he has two starting points. :highfive:
Click to expand...
Click to collapse
That's true, 2 starting points is better than none.. I don't necessarily like "patching" others work because you never really know how they made it or if it has problems which is why I just start from scratch.
Yes starting from scratch was initially what i wanted but i looked around on XDA university for a week and that helped get me to learn about setting up Vm, installing android sdk through terminal ETC and repo init repo sync, downloading repositories and other source codes.....BUT my thing is wanting to learn how patch errors and need more on hands experience for setting up build environment
Sent from my iPhone using Tapatalk
I am planning on building a custom rom, I would want CyanogenMod 14.1, or other custom rom, but I need a small team to develop it, to get the best result possible. I think it would be fun and maybe even do some great work.
But, I have some requirements:
1. Know big part of linux(ubuntu) commands
2. Know english or my home language, I hope you see at my profile from what country I am if you talk my home language just give me a PM. But I'm happy with both of them.
3. Have a computer(lol) and maybe 2,3,4 or more GB of ram and 100GB of storage for developing
4.Have a P8 Lite to test the progress of the rom.
Please do not make hate or fun or fun of me just because this thread sounds funny.
"we" already have a team like this, OpenKirin, made by XePeleato, surdu_petru and 1 more guy, working on P9...
D1stRU3T0R said:
"we" already have a team like this, OpenKirin, made by XePeleato, surdu_petru and 1 more guy, working on P9...
Click to expand...
Click to collapse
I know, but more teams= more progress; more roms
You better join their team
Audriuskins said:
You better join their team
Click to expand...
Click to collapse
, Would be better, but I'm not still at their "skill" level. I know how to build a rom from source, but I do not use my own source code, I often use XePeleato's source, I need to learn how to build device tree, blobs, etc.
XTutorials said:
, Would be better, but I'm not still at their "skill" level. I know how to build a rom from source, but I do not use my own source code, I often use XePeleato's source, I need to learn how to build device tree, blobs, etc.
Click to expand...
Click to collapse
Then create a topic in Development and post your progress as soon as you've done anything. The community tells you if it works or not, but building for this device without experience is not that easy. I wish you the best of luck, but only using XePeleato source and adding nothing won't help at all. If you think you can fix something, just commit to their github. But you won't find a developing team over here. I would try to learn myself, but I don't have a PC that's able to do anything. Try to build things yourself, commit to their github and try to help the OpenKirin team. There nothing else to do here for you, if you're inexperienced.
XTutorials said:
3. Have a computer(lol) and maybe 2,3,4 or more GB of ram and 100GB of storage for developing
Click to expand...
Click to collapse
Just to joke a little : with only 2GB RAM & 100GB storage, you'll be able to build the whole source code of Android MM or N, in a few days
Now really, you need at least 16GB DDR3/4 and minimum 200GB storage ( preferably SSD ) , because you need to set ccache to 50GB or maybe 100GB ! If you have only 100GB and setting ccache to 50GB, with only 50GB storage free - you'll never be able to build the whole source code !
Vinnipinni said:
Then create a topic in Development and post your progress as soon as you've done anything. The community tells you if it works or not, but building for this device without experience is not that easy. I wish you the best of luck, but only using XePeleato source and adding nothing won't help at all. If you think you can fix something, just commit to their github. But you won't find a developing team over here. I would try to learn myself, but I don't have a PC that's able to do anything. Try to build things yourself, commit to their github and try to help the OpenKirin team. There nothing else to do here for you, if you're inexperienced.
Click to expand...
Click to collapse
+1
surdu_petru said:
- you need at least 16GB DDR3/4 and minimum 200GB storage ( preferably SSD ) -
Click to expand...
Click to collapse
+1, i have i7-4770k @ stock, 6gb of ram and 140gb of samsung ssd allowed to virtual machine. And first build takes about 2hr30min
I know little about Linux, but I heard that developers can use Google Cloud.
Sent from my HUAWEI CHM-TL00H using XDA Labs
Vinnipinni said:
Then create a topic in Development and post your progress as soon as you've done anything. The community tells you if it works or not, but building for this device without experience is not that easy. I wish you the best of luck, but only using XePeleato source and adding nothing won't help at all. If you think you can fix something, just commit to their github. But you won't find a developing team over here. I would try to learn myself, but I don't have a PC that's able to do anything. Try to build things yourself, commit to their github and try to help the OpenKirin team. There nothing else to do here for you, if you're inexperienced.
Click to expand...
Click to collapse
That is what I'm going to do in the next days, I need to research a lot for now and if I (god help) succeed I'll let you know.
surdu_petru said:
Just to joke a little : with only 2GB RAM & 100GB storage, you'll be able to build the whole source code of Android MM or N, in a few days
Now really, you need at least 16GB DDR3/4 and minimum 200GB storage ( preferably SSD ) , because you need to set ccache to 50GB or maybe 100GB ! If you have only 100GB and setting ccache to 50GB, with only 50GB storage free - you'll never be able to build the whole source code !
+1
Click to expand...
Click to collapse
:laugh: :laugh: I know I exaggerated, but I just use 8GB of ddr2 and a 250GB HDD, repo sync takes approximately 2 hours and building the rom somewhere like 3:45-4:30 hours
This sounds like april fools! Dude that doesn't know anything wants to spear a dev team? Maybe this is hi620softs other account? :silly::silly: