Hi everyone,
I'm still quite new to building ROMs from scratch, so please bare with me. As my HD+ (ovation) has been so happy n stable on cm12.1 (this thread) I've decided to attempt to compile it myself to start with, then I can look into the few simple mods i wish to add to the source, bundle a few apps etc etc maybe a couple of minor fixes in time....
Right anyway my question,
I have syncd the repo, and using the cm wiki and the breakfast command I have downloaded the device code. I have started to explore it, however I have been reading about the local_manifest.xml which i dont yet have, now looking around on github I have:
android_device_bn_ovation
android_kernel_bn_omap
android_vendor_cm
is that right? how to do I inc the forks of airend, hashcode, and verygreen? what about other kernels? Please any help or advice would be greatly appreciated.
Related
Hi,
I'm trying to build cyanogenmod 6 (froyo) from sources on github for G1.
Sidenote. The reason I'm trying to do this is i'd like to modify kernel parameters. I'm trying to make the phone talk to external device using built in serial port. I can do it with my current CM6, but it looks like serial debugger engages and starts responding to the device and also steals some of the data being sent to phone.
To build I used instruction posted at cyanogen wiki "HTC Dream & Magic: Compile CyanogenMod (OS X)" which covers gingerbread but checked out froyo-stable branch at first. I know that gingerbread version stopped supporting G1 at some point last year.
Without much success even after fixing manifest to point to updated repo urls from kernel.org to googles repo etc. The problem is that apache-http seems incompatible with old sources and it is referenced by head.
I also tried froyo branch, but it doesn't build as well because something seem to be broken for dream_sapphire, and it is not present in the devices anymore.
I've tried searching for compilation errors, and general build questions/instructions here and on cyanogen's forum, but looks like CM6 is not very active these days.
Can someone point me into right direction where to search for relevant info on building it? Would getting a proper revision help or should I combine stuff from several branches to make it work?
I've already spent quite a lot of time figuring out how build is being configured and how things stitch together but without much progress on the actual build.
And with times required to sync a whole repo and build it, it is becoming frustrating.
Any help would be muchly appreciated!
Regards,
Oleg
It's dead.
I also wanted to make a cm6 rom, but I couldn't get anything to work.
I got the addresses all updated but it looks like a bunch of the files have completely dissappeared. You may be able to make it skip those, but then it may not work completely.
Go for AOSP?
Now that's a shame. I wanted to build CM because I'm familiar with it and the other thing is that they have reasonable instructions about building it. But at least I don't need to waste my time trying to figure out how to fix it.
In fact I don't need any extras they provide, a bare android would suffice to me if all the sensors and connectivity would be available. But I'm not familiar with internals of building vendor specific stuff. My understanding was that I need proprietary parts together with AOSP to build a working ROM and that's one of the things CM guys did. Correct me if I'm wrong.
aliher1911 said:
Now that's a shame. I wanted to build CM because I'm familiar with it and the other thing is that they have reasonable instructions about building it. But at least I don't need to waste my time trying to figure out how to fix it.
In fact I don't need any extras they provide, a bare android would suffice to me if all the sensors and connectivity would be available. But I'm not familiar with internals of building vendor specific stuff. My understanding was that I need proprietary parts together with AOSP to build a working ROM and that's one of the things CM guys did. Correct me if I'm wrong.
Click to expand...
Click to collapse
Nope AOSP is as easy to build now
Go to the android site and follow directions
Google for "build android"
At the part when doing repo init you need to get the right branch
Go to "build for devices" then scroll down for recommended branches and look for the dream
One thing you'll need to do differently is do "make otapackage" instead of plain "make"
And once that's done you'll need to tweak the zip and get rid of the "recovery" folder and tweak the updater-script
Oh yeah, and I don't know exactly how you would do this part, but you'll need to get the source for a newer kernel in there, like ezterry kernel and use it with 2708+ radio/spl
Unless you wanna use the AOSP kernel & spl & radio which is old
What I did is just flash his kernel after the rom, but you want to do kernel stuff so yeah...
Sent from my HTC Dream using Tapatalk
Hi everyone. I am a new developer learning how to use the github to help improve the code for the nook color linux branch. You can follow along with my posts down in the cyanogenMod forums at this link here. http://forum.cyanogenmod.com/topic/50994-follow-along-with-me-trying-to-learn-how-to-code/
Anyone interested in learning this skill, I have set up a lengthy thread down there for us to learn how. If any beginners wanting to learn or have questions just email me here or down in the nook color cyanogenMod forums and I will get back to you. Or ask in this thread here.
The Github is a repository where you can help the other developers improve the code, merge code back to the master branches that have forked out and to look for merge conflicts and other bugs that will help improve the function of your nook color. I have the basics down so ask me any questions.
You can check out the github for the upcoming Ice Cream Sandwitch that is coming to your nook color along with who is developing on it and what they are doing. Here is the repository for the nook color linux branch. https://github.com/fat-tire/android_device_bn_encore
Interested on who is working on your nook color linux branches? Check this link out here. https://github.com/fat-tire/android_device_bn_encore/network/members
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Already know how to use git? Help us out by taking a look there on our branches. Any help would be appreciated.
~~~~~~~~~~~~~~~~
I have been lurking here since I was 12 years old. Now I am ready to take on linux development for your nook color. Come join me and clone my repos and lets get started ok? I want to see some forks up in our linux branch. I know some of you are holding out ) You can find me on the github here guys. https://github.com/meteorrock/android_device_bn_encore
I'd help but I don't own one waiting for supurb ics for a friend
Sent from my SCH-I500 using XDA
Hello all. I've recently been trying to get into Android development, more specifically Kernel development. I've played around with some kitchens and looked at the GB kernel sources from Samsung and tweaked it around.
Previously I previously learned Java to a point where I can put basic lines down and also more advanced stuff but with a bit of help here and there.
I have one question though, what would be the recommended path for creating an ICS Kernel. My plan is to start of with something "stock" and build up but I'm not quite sure what to consider stock seeing as the S1 never got ICS officially. Would I have to use CM9's Kernel sources and if so where do I acquire them.
I also have a good understanding of Ubuntu and its terminal and have a functional idea of what I'm doing there.
Hello,
I searched through a lot of threads on how to compile CM, also checked CM wiki, but I want to compile AOSP, not CM. I want to compile it and maybe add some little tweaks to it. How do I compile it? I mean the device-specific part - which repositories, where do I put them (device, kernel,...) and so on?
I'm new to this, and also there's a problem with Ubuntu in VirtualBox, I cannot get my Galaxy S recognized via ADB in the virtual machine (Ubuntu). Just VirtualBox fails at connecting. So I want to ask also if there is any way to get proprietary vendor stuff from phone without using the extract-files.sh script? (another repository for this?)
I'm sorry if I'm starting a question that has been discussed before, but I couldn't find a thread about compiling AOSP for the galaxysmtd. I also checked malcho's thread for building unofficial nightlies and I'm lost there. Still don't know how...
Thanks in advance.
Hey fellas,
Currently I have CM13 compiled from source and its up and running for trltetmo (love it). I am just trying to see how other people are compiling toolchains and making them work. I have spent way too much time banging my head against the wall trying to get things running but I'm stuck using outdated sources and very buggy code...
Curious if:
- People have experience using SM and how they are updating it from source (osl from their manifest is non existent). Currently I can only find an outdated precompiled zip for SM found here.
- People have any experience using UBER and where is their source directory to pull updated code.
Currently I have several things where they need to be and if I can get some help applying a custom TC I may start to release optimized, minimalist, true (not jimmy rigged vzw files) CM13 zips.
NOTE: if it weren't for @fattire, @ZION959, @BotsOne none of this would be possible.