[Q] Resources on Git and Cherry Picking? - Nexus S Q&A, Help & Troubleshooting

I've been an Android user for a couple of years now, and I've built my own build environment so I can build my own ROMs, nothing fancy and for the public, just something I can do and learn more about the whole process myself in a hands-on way.
I'm not very familiar with Git, specifically cherry-picking items. I was wondering if anyone had some good resources that explain how one cherry-picks and builds that into their own ROM. I've been looking around but can't really seem to find something that explains HOW to do it and build it into a ROM, most of the posts/pages I've found say "Hey, I cherry-picked this" or "Use Git and cherry-pick it".
I'm still looking around and learning quite a bit about Git, but was wondering if anyone had a site that they preferred or would recommend for someone looking into making their own custom kangs (something other than Google).

Here you are!
http://gitref.org/

Awesome, thanks! I didn't come across that one. I've been checking out the Git Community Book and a couple other wikis, but this one's new to me. I'll check it out.

Yeah, I mean you can find all sorts of things over google, but that site is pretty good as well

I guess my main thing was (is), I used the code from Cyanogen's Gerrit Review for "cherry pick", and it looked like it grabbed what I was trying to grab, but I did a build and those commits weren't in there, so I know I'm missing a step somewhere between running the cherry pick command and building the ROM.

Oh ok, yeah even googling certain git commands such as cherry pick helps
Sent from my HTC Sensation 4G using XDA App

Related

[Q] Compile cyanogenmod for Backflip

Now that the Backflip's been rooted, I'm really hoping to get something fresher than 1.5 on this thing, and I'm not waiting for Moto's 2.1 update any longer. It seems like kernelzilla's made quite a bit of progress on a kernel
bit (dot) ly (slash) brWGPv (sorry, I'm new to XDA and can't post links yet)
Is there a way to download, incorporate this kernel, then compile and sign cyanogenmod to update the device? I'm new to hacking, but I'm comfortable around a command line, and I've written a couple Android apps myself.
I'm looking into that sort of thing right now, I've got lots of development experience but I'm new to kernel hacking too. I'm in the process of educating myself on the whole thing because I'm tired of waiting around when I'm smart enough to be actually making contributions to this. Kernelzilla suggested www.elinux.org and www.kernelnewbies.org as places to get educated on the linux kernel. The main problem is that with android your flashing and it can go horribly wrong, I'm playing with goldfish aka the emulator right now but it's not really the same. I'm actually thinking of switching to gentoo just to get some hands on experience that won't risk bricking anything lol
CM7 for backflip
brian515 said:
Now that the Backflip's been rooted, I'm really hoping to get something fresher than 1.5 on this thing, and I'm not waiting for Moto's 2.1 update any longer. It seems like kernelzilla's made quite a bit of progress on a kernel
bit (dot) ly (slash) brWGPv (sorry, I'm new to XDA and can't post links yet)
Is there a way to download, incorporate this kernel, then compile and sign cyanogenmod to update the device? I'm new to hacking, but I'm comfortable around a command line, and I've written a couple Android apps myself.
Click to expand...
Click to collapse
CyanogenMod is available for Backflip check my thread here.
Hit thanks if it helps ^_^

Cyanogenmod Info.

I've heard many things, all great, about CM since the beginning of time (...well, close to it.). Frequently, before a real android phone was obtainable via the average pathways here in the U.S. of A, and the iPhone was the only real option for a smartphone, I found myself pulled towards CM-even though I had no way of actually using it at the time. The open-source, power-to-the people feel has always appealed to me...and my journey, starting from the age of 12, when I started crashing my parents computer so I could spend more time with the boutique builder that would fix it, later fixing it myself, then exploring the down-and-dirty innards of my gadgets-- this journey, has always felt like home to me.
My personal tinkering with phones and the like started with my sisters HTC Tilt, which I skinned to look like an iPhone for her. This was one of the first phones with Wi-Fi (Ha!), and trying to get it work was just as fun as using it.
Moving on, I received, for my birthday, a palm PDA (one of the first with a camera and a color screen...the device itself was blue), but I had to return it due to an exploding display.
Finally, a couple years ago, I got my first smart-phone. An iPhone. And within an hour after getting it, I had it jailbroken and themed. But the innards were still off limits. While searching under terms lie? "Hack phone" and "tethering, I always came across posts speaking of Cyanogenmod...In fact, I'd say that an astounding 50% of my searches relating to customizing or modifying--in some way or another, led to a post or thread--sometimes a whole article, on how to do something with android, and specifically CM. This proved fruitful for my later endeavors.
When I was doing better financially, I bought my first android device, and have never felt so empowered, and have never had such a strong ownership of my devices. That device was the Transformer.
Again, after just an hour of owning the device, I was looking up terms...and searching XDA for every bit of relevant information I could find. Some of the questions I had: What is Clockwork Mod? What is Clockwork Mod Recovery? What's the difference? NVflash? What's a B70 serial number mean for my prognosis? What's a Nandroid? How do I choose a ROM?
Although there was a metric ten of terminology I needed to learn to know what I was doing--and even though there was almost a complete vacuum of centralized information--- at least authoritative information (any questioned asked in forums led to me being booted and marked as a noob), things eventually worked out.
I learned about the Boot loader situation for the transformer, the status of honeycomb as a sort of non-open-source open source operating system, and about the battery issues....about kernels, and speaker mods, about modules and root apps-and along the way I learned almost the full metric ton of terminology, and had a metric ton of fun...with you guys.
Which brings me to today...I own a brand new galaxy note, but am once again in the dark. Only this time, its far worse...because my questions pertain to CM, the gold reference when it comes to running a custom rom, and its structure...that is to say, the structure of the ROM, the team that builds it, and the community that helps support it...all relevant to understanding the dearth of work and choice that we find in this very forum. And because its been around for so long, the staple that CM has become, assumes that all things and all people know what's happening.
Which brings me to my real questions....which I've searched, and searched, and searched again for answers to, but have found no conclusive, or concise and relevant answers. I've searched the cyanogenmod site, the forum, this forum, and Google. And while I found half-answers, and although I'm confident I can root any device I, or my friends can buy, and I can install custom roms, edit props, change permissions, dump radios, flash pre rooted kernels and other kernels, and backup and edit every settings app and image I can find, I still find myself lacking a fundamental understanding of Cyanogenmod and Cyanogenmod work, official, and unofficial--information that would make my life complete, and help me bear the fruit of this journey I'm on.
That journey ends with a device that I own...one with cyanogenmod on it...specifically...a device in the near future that runs a version of CM that I helped contribute to-either officially or unofficially to.
And the beginning of the end to that journey, and the desired end game--developing, begins here. With my ASUS Transformer. And my questions.
Note: I illustrated this story in-depth, for a reason. To let you know that I've searched long and hard for clear answers, and that I plan to contribute significantly in the future to Android, and to XDA. I just need a teeny bit of help...a little direction. And so do a lot of us. I haven't found anywhere, a discussion of this subject--a significant one when it comes to understanding our community, our choices, and how to contribute...that subject is the structure of Cyanogenmod: the ROM, the team, and the community that constitutes them. The following questions are relevant to, and seek to address this fundamental lack of understanding.
Since the release of IcS, we've seen an explosion of CM in the Transformer forum. And while I understand how to read a change log, and a list of "what's working" and "what's not working", and can rely on a search find out what "Cornerstone" is, its still damn near impossible to define the relationship that constitutes all of the CM builds that are available. It might be clear, after a search, what the term "Kang" is, but what isn't clear, is what this means for the end-user. Its not clear what's official, what's parallel work, and what makes up the night lies that we can find on the CM repository. Is it one man aggregating work from forums like this, and throwing all of the features and fixes into a centralized build? Are the ROMs that we find in the Development section of the Transformer section off-shoots of CM to be worked on and differentiated in the future? Because where it stands now, I don't see a ton of differentiation. Maybe its because there's just been a new release, and I'm seeing the beginning of a process here. But I'm still unaware of what makes up a CM team. Its not clear how these things work-- if there is one man from the team working on the transformer, another working on the Epic 4g...and so on, or if everyone works on the same thing, and the feature or fix is distributed by a magic machine, or if each person on the team works on the same thing, and then a designated person ports it to his device. It's context like this that makes an informed overview of the current situation possible. And without that context, I'm stuck.
Most know that nightlies come before the release candidate(s), and that a stable release follows. But what I don't know, is why I never hear about an actual release, and almost always hear people speak of night lies, and in general, they're almost categorically excited.
So, if we were to examine my complete and utter lack of knowledge together, wed conclude that it's impossible for me to understand where XDA, and the ROMs that are available in the development section fit in to the grander-scheme of things. Is it better to get a nightly from CM? Is the nightly made up of the very fixes and developments we find in the various ROMs here in the development section?
How does someone go about deciding which of the dozen ROMs to install? Because the threads for ROMs don't explain anything when it comes to explaining an end goal, and a developers intent for the ROM, and the reasons why he/she is making one, I find myself stuck in the quick-sand of change-log after change-log, feature list after feature list.
Give me the 411. Explain to me what I'm missing in my Rosetta stone of the big picture..the grand scheme of things. Maybe I'm looking at this all wrong...maybe I'm just an idiot. Maybe you'll rage at me. But maybe, just maybe, I'm missing only, one small, key, piece of information here, and I spent a couple pages typing on the touchscreen of my transformer for thirty five minutes to find the answers that I badly need.
I'm sorry if I wasted your time. Thank you very much for reading this.
If you have a problem with my post, or a suggestion, attack, or complaint, please Private Message it to me...unless it pertains to the questions I posed...in which case I would very, very much appreciate your comment, your input, you sharing your knowledge, or even a question of your own.
Thanks.
Seriously? All that wall of text to ask the same question that everyone else asks?
This is how you divide up the custom ROMs to make your choice easier:
Do you want cornerstone or no?
If you want cornerstone, you pick between Team EOS or CM9
If you don't want cornerstone, you have these to pick from(in no particular order):
Revolver
Android Revolution HD
Codename Android
AOKP
CM9 no cornerstone version
Just try them and see what you like. I don't understand why people are so cautious before picking a ROM as if it's a permanent choice that can't be reverted.
If you don't like it, you can quickly flash a different ROM.
It's better for you to make your own decision based on your own experience with the ROMs rather than rely on someone else's recommendation whose needs and personal preference might not match yours.
Thank you, actually a nice read, there is also official cm support for our tf, on the cm website, last i seen there were 3 nightlies, since ics iv flashed the official cwm modded rom, then revolutiin, then team eos, then cm9, back to revolution, then codename android, now back on krakd hc rom until jcarrz releases his ics rom.
Sent from my R800i using xda premium
You gotta keep in mind that all ICS development now is in an early stage. Every rom is new, we don't have a solid stable one. Even stock asus have problems with rebooting, dock integration and so on.
CM is fragmented in 2 or 3 builds, and what diferentiates then is only the commits from CM repository and some dev preferences, like cornerstone or full support for the dock.
All roms that aren't Asus based (AOSP) suffers from some aditional issues, like:
- Dock won't be fully working, except on CM9 by ricardopvz and Codename Android. The touchpad still works different from stock asus.
- Some Wi-fi and GPS issues, probably driver related
- Screen rotation have a lag issue (all AOSP roms)
- Dock battery info missing, even with widget.
- Battery drain issues.
I have tested almost all roms and can say most of then is pretty usable. But if combined with overclock kernel, you can certainly expect problems.
[noobquestion]What is this cornerstone everyones talking about? lol [/noobquestion]
Im personally running team EOS nightly build (no cornerstone) with blade's OC kernel running at 1.4Ghz.
I think the ROM works very well. It hasnt really given me any issues except 2 random reboots and 1 semi-freeze (all on the same day lol). Its been running perfect for 3 days now though.
Don't worry about hondroid he is kind of a troll no hard feelings
I have not used CM for quite some time but here is my understanding from having worked with the captivate and transformer for over a year now.
Cyanogen mod is based off of the true source code of andorid taken directly from google and with no OEM's getting their greasy little fingers over them and polluting them with bloatware and skins. From there cyanogen set up a git repository where they have the main android tree as pure as it is and then branches for each device. Then there are plenty of devs working directly on the tree optimizing the core android and adding features which can then be accepted or regected by the otehr devs. Then there is a smaller team of devs on each "Branch" which normally consists of a certain type of processor or chipset. Ex Hummingbird or Tegra 2
The job of the devs there is to integrate that to make it work smoothly and they have the same peer approval system. There are also smaller branches which contain the drivers for most pieces of hardware (Speakers, Screens ect). Then finally there is the device dev there are normally about 5 from my experience but once all the work is done the team can be cut to 1 or 2. They are the people that get it up and running on the device writing missing drivers fixing device specific bugs ect. And once they are done there work they can compile it all together and there we have our nightly.
Then if there is a change in the core all the device devs have to do is recompile and build the rom and there is your next nightly.
The RC happens when they hit a stable nightly or when development has slowed enough that all of the bugs have been fixed
Hope this is helpfull
Thanks to all of your for your responses. I think this is a beautiful conversation that isn't happening enough. All of you have provided great information, that when combined helps to depict the structure of the community we have all grown to love.

KERNEL source released

So exciting
http://www.androidpolice.com/2012/0...rnel-source-code-including-that-of-the-one-v/
EDIT: http://dl4.htc.com/RomCode/Source_and_Binaries/doubleshot-gb-crc-2.6.35-f3a1982.tar.gz
Sent from my DoubleShot Lite using Tapatalk 2
ac3theone said:
so exciting
http://www.androidpolice.com/2012/0...rnel-source-code-including-that-of-the-one-v/
sent from my doubleshot lite using tapatalk 2
Click to expand...
Click to collapse
yyyyyyyyyyeeeeeeeeeeeeeeeeeeeeeessssssssssssssssssssssssss
Soo.... Does anyone think we could see some pure AOSP action now? Or someone could update the kernel for CM7? As you will see in general someone -whom I suspect is not alone - would love an AOSP ROM on our HTC Doubleshot.
Maybe this kernel isn't that good as we suppose...
Nusferatu said:
Maybe this kernel isn't that good as we suppose...
Click to expand...
Click to collapse
Well.... What did u expect? we don't have an ICS ROM in our future that we have been made aware of, and it is truly great news as this is something that has made many a dev stray away from this device - now we might be able to get CM7 stable - and others to work off of CM7 such as blahblah
Good news nevertheless
We need to get CM7 STABLE ASAP
We may be late in the running, but that doesn't mean we still can't get merged into the main tree
Nusferatu said:
Maybe this kernel isn't that good as we suppose...
Click to expand...
Click to collapse
Its worse than you thought... The source code was released a really long time ago. This is just an updated kernel, so the real reason for lack of development isn't because the source code wasn't available. :/
michaelmab88 said:
Its worse than you thought... The source code was released a really long time ago. This is just an updated kernel, so the real reason for lack of development isn't because the source code wasn't available. :/
Click to expand...
Click to collapse
Updated source is awesome though. Tried to get it earlier and couldn't - can't on shift and will be working straight until Friday afternoon so won't have a chance to try again for a few days.
Any percieved lack of development is due to people not putting any effort into it - everyone who cries about a lack of development should do something about it instead of waiting for someone else to do so.
Why come here if you don't want to get into dev, worse, come here and complain about yourself not doing anything? Kinda silly.
Whenever I see people complain about a lack of development I wonder why they would basically make fun of themselves? It gives me a laugh at their expense...
Sent from a digital distance.
Yeah i just got the source downloaded because it matches the new ota I'm running now, I've never seen what a dual core source looks like, or if I'll even be able to compile a kernel for this device, I've only compiled a few for the EVO shift, which was straight forward with a little help from my boy drob...who knows o may get it to boot ha-ha.......nope I fudged something in my toolchain It's broke....again.....LOL
Sent from my myTouch_4G_Slide using Tapatalk 2
strapped365 said:
Yeah i just got the source downloaded because it matches the new ota I'm running now, I've never seen what a dual core source looks like, or if I'll even be able to compile a kernel for this device, I've only compiled a few for the EVO shift, which was straight forward with a little help from my boy drob...who knows o may get it to boot ha-ha
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
http://dl.dropbox.com/u/62701184/arm-eabi-4.4.3.zip
That link is for the toolchain you need, i've been hosting it on dropbox for a while until I get it over to a more permanent host.
I can walk you through it later if you want.
I have it written up on how to set up your linux environment and make changes, including versioning instructions, just haven't found the time to polish off a part of it and add it to the dev reference yet.
Got a whole space reserved for the how to from start to finish on making kernels for the doubleshot, and i've already walked people through it with no kernel dev experience so if you've done it for another device it'll be a cakewalk.
I'm eating breakfast now and gotta run out to another job, and going straight from there to dodgeball practice, then work again tonight and from there right to the job i'm about to do again tomorrow this time, so tomorrow night i'm doubtless going to sleep - maybe as early as saturday evening I could go through it with you on IRC if you are interested.
Otherwise I hope to have that in the dev ref next week, work permitting.
Blue6IX said:
http://dl.dropbox.com/u/62701184/arm-eabi-4.4.3.zip
That link is for the toolchain you need, i've been hosting it on dropbox for a while until I get it over to a more permanent host.
I can walk you through it later if you want.
I have it written up on how to set up your linux environment and make changes, including versioning instructions, just haven't found the time to polish off a part of it and add it to the dev reference yet.
Got a whole space reserved for the how to from start to finish on making kernels for the doubleshot, and i've already walked people through it with no kernel dev experience so if you've done it for another device it'll be a cakewalk.
I'm eating breakfast now and gotta run out to another job, and going straight from there to dodgeball practice, then work again tonight and from there right to the job i'm about to do again tomorrow this time, so tomorrow night i'm doubtless going to sleep - maybe as early as saturday evening I could go through it with you on IRC if you are interested.
Otherwise I hope to have that in the dev ref next week, work permitting.
Click to expand...
Click to collapse
I might have my little one on Saturday night so that maybe a no go for then, the tool chain I currently have is 4.4.1, because anything newer for the speedy breaks a ton during the compile.....I changed some commands around for ****s and giggles and got a zimage in arch/arm/boot so I split it with the ota ramdisk and I'm just gonna try....if that goes south I'll setup your tool chain....thanks blue your like the DoubleShot dictionary....
Also I'm gonna grab one of your kernel zips for test flashes if that's ok
Sent from my myTouch_4G_Slide using Tapatalk 2
Blue6IX said:
Updated source is awesome though. Tried to get it earlier and couldn't - can't on shift and will be working straight until Friday afternoon so won't have a chance to try again for a few days.
Any percieved lack of development is due to people not putting any effort into it - everyone who cries about a lack of development should do something about it instead of waiting for someone else to do so.
Why come here if you don't want to get into dev, worse, come here and complain about yourself not doing anything? Kinda silly.
Whenever I see people complain about a lack of development I wonder why they would basically make fun of themselves? It gives me a laugh at their expense...
Sent from a digital distance.
Click to expand...
Click to collapse
Hey I'm not complaining, and I am working on it! I just have to balance between school and work and learning how to build cm7/cm9 from source.
You can check out a little bit of what I've been working on github.com/mafischer
michaelmab88 said:
Hey I'm not complaining, and I am working on it! I just have to balance between school and work and learning how to build cm7/cm9 from source.
You can check out a little bit of what I've been working on github.com/mafischer
Click to expand...
Click to collapse
Lol no worries my friend, was a general comment and not aimed at you in particular, just a perspective I wanted to put out there and you were the first opportunity to do so.
I still haven't found the time to get git set up and learn how to use it - that whole life getting in the way of living thing. Given you have git going that makes you a more responsible dev then I in my book -
@ strapped: all my work available is a contribution to the open source community at large, and the members of XDA in particular. If any of it can be useful, especially as a teaching tool, I wholeheartedly encourage it!
Sent from a digital distance.
Where did all of you come from?
Never knew there was this many people working on the Doubleshot in the background...
gtmaster303 said:
Where did all of you come from?
Never knew there was this many people working on the Doubleshot in the background...
Click to expand...
Click to collapse
I've been here since i preordered my doubleshot... I just haven't had time to work on much of anything, so there's no point in advertising to the community that I'm gonna work on things that may or may not ever get finished. I don't want to spread false hope or anything.
I am however, graduating in may; I'm going to be working over at walmart isd for a summer internship, and I should have more time on my hands once school is over!
How integrated is the Sense stuff into the kernel? As I understand it, we've had trouble removing the Sense underpinnings from the operating system to get it working with things such as Sixaxis. I'm aware that this is entirely a lack of understanding on my part.
I would quite love to get involved in building a ROM myself, perhaps even setting up CM9 from scratch. I just have no idea how to get started. I've mucked around with custom kernels and embedded linux (not android) devices in the past, but I'm not sure how that knowledge would apply to this system. I also have no history of proper programming languages or anything like that. I'm vaguely familiar with how to compile things with the ARM toolchains.
I'm also a tad nervous about bricking the device by writing to a memory location that I really shouldn't be touching.
Kanerix said:
How integrated is the Sense stuff into the kernel? As I understand it, we've had trouble removing the Sense underpinnings from the operating system to get it working with things such as Sixaxis. I'm aware that this is entirely a lack of understanding on my part.
I would quite love to get involved in building a ROM myself, perhaps even setting up CM9 from scratch. I just have no idea how to get started. I've mucked around with custom kernels and embedded linux (not android) devices in the past, but I'm not sure how that knowledge would apply to this system. I also have no history of proper programming languages or anything like that. I'm vaguely familiar with how to compile things with the ARM toolchains.
I'm also a tad nervous about bricking the device by writing to a memory location that I really shouldn't be touching.
Click to expand...
Click to collapse
Sorry for quoting the whole post just to address one thing, but in regards to sixaxis I'm sure it's a safe bet that if one were to simply replace the stock bluetooth stack with the one kornyone used for cm7 in my bulletproof rom it would work fine, and I doubt much other, if any modification would be necessary.
I haven't had time to try, and truthfully i'd rather build my own so am kinda intentionally not trying - I am more interested in the project then just jumping into a solution.
It really depends on what you are trying to do - some sense things can be replaced with relatively little effort, other things are so interwoven it would take considerable effort and time to unravel, reverse engineer and implement a new solution.
A lot of people have been working on different parts of unravelling sense since back in august, and around the middle of that month we got s-off and really started digging in.
There is a considerable knowledge base lurking here to address this kind of stuff if people make it known they are working on things - dig back through the history of the device here at XDA and you can catch a glimpse of it and get some direction on who you can approach when you hit a roadblock, depending on what kind of roadblock it is.
It's better for us as a community to have that kind of knowledge out on the public forum, but there's much more here then what face value suggests.
I've been trying to get that kind of stuff and a general 'start here' knowledge base built in the developers reference stickied here in dev, reading through that would be a good place to start getting oriented on devving for the dubleshot.
I just go through some crazy work cycles and sometimes can't be around much for a time here and ther, so my contributions come in groups and gaps.
Sent from a digital distance.
michaelmab88 said:
I've been here since i preordered my doubleshot... I just haven't had time to work on much of anything, so there's no point in advertising to the community that I'm gonna work on things that may or may not ever get finished. I don't want to spread false hope or anything.
I am however, graduating in may; I'm going to be working over at walmart isd for a summer internship, and I should have more time on my hands once school is over!
Click to expand...
Click to collapse
It doesn't matter whether or not you finish. Status updates would be nice though. At least that way people can know what you're up to, and they may even be able to help you and vice versa.
No one here is demanding an ETA or even a completion at all. We're all in for the fun of it.
Either way I think I can safely speak for everyone when I say, we're excited to see what you got cooking
Blue6IX said:
Sorry for quoting the whole post just to address one thing, but in regards to sixaxis I'm sure it's a safe bet that if one were to simply replace the stock bluetooth stack with the one kornyone used for cm7 in my bulletproof rom it would work fine, and I doubt much other, if any modification would be necessary.
I haven't had time to try, and truthfully i'd rather build my own so am kinda intentionally not trying - I am more interested in the project then just jumping into a solution.
It really depends on what you are trying to do - some sense things can be replaced with relatively little effort, other things are so interwoven it would take considerable effort and time to unravel, reverse engineer and implement a new solution.
A lot of people have been working on different parts of unravelling sense since back in august, and around the middle of that month we got s-off and really started digging in.
There is a considerable knowledge base lurking here to address this kind of stuff if people make it known they are working on things - dig back through the history of the device here at XDA and you can catch a glimpse of it and get some direction on who you can approach when you hit a roadblock, depending on what kind of roadblock it is.
It's better for us as a community to have that kind of knowledge out on the public forum, but there's much more here then what face value suggests.
I've been trying to get that kind of stuff and a general 'start here' knowledge base built in the developers reference stickied here in dev, reading through that would be a good place to start getting oriented on devving for the dubleshot.
I just go through some crazy work cycles and sometimes can't be around much for a time here and ther, so my contributions come in groups and gaps.
Sent from a digital distance.
Click to expand...
Click to collapse
I've been trying to go through the dev reference that you posted and track down as much scattered information as I can, but I'm still not quite sure what I'm doing. Alas.
Regarding bluetooth: would the gingerbread stack be compatible with ICS?
gtmaster303 said:
It doesn't matter whether or not you finish. Status updates would be nice though. At least that way people can know what you're up to, and they may even be able to help you and vice versa.
No one here is demanding an ETA or even a completion at all. We're all in for the fun of it.
Either way I think I can safely speak for everyone when I say, we're excited to see what you got cooking
Click to expand...
Click to collapse
Well what I'm currently up to is making a stable version of cm7 for the doubleshot. I have made lots of progress as far as learning all the tools necessary to compile android from source, which is a relatively simple task. The not so simple part is trying to put together like a puzzle, the source code from other devices. I've hit some roadblocks and I'm currently asking some devs for help, but while I'm at it I guess I can ask for help here on xda.
michaelmab88 said:
Well what I'm currently up to is making a stable version of cm7 for the doubleshot.
Click to expand...
Click to collapse
Yeehaaa!

Getting Started with ROM Development

I've been around for a while, and flashing ROMs all the time, but I was wondering what it really takes in order to really get going with ROM development. I would really like to put together my own PAC/Rootbox/ReVolt-style ROM, but I don't really know where to get started. I have done a very small amount of Android app development, but I do have experience with Java. Does anyone have any pointers for where to get started, best practices, etc...?
Also included in this question should be this: I have a little experience with Github, but haven't really ever used it do pull requests, forking, and such, and I've only ever really used it for hosting my own projects. Is there a good guide on how to understand that type of stuff, as well as where to do builds, nightlies, and hosting? From what I've gathered from various ROM devs so far is that if you host on Goo.im, that will let you take advantage of GooManager for OTA updates, right?
drinfernoo said:
I've been around for a while, and flashing ROMs all the time, but I was wondering what it really takes in order to really get going with ROM development. I would really like to put together my own PAC/Rootbox/ReVolt-style ROM, but I don't really know where to get started. I have done a very small amount of Android app development, but I do have experience with Java. Does anyone have any pointers for where to get started, best practices, etc...?
Also included in this question should be this: I have a little experience with Github, but haven't really ever used it do pull requests, forking, and such, and I've only ever really used it for hosting my own projects. Is there a good guide on how to understand that type of stuff, as well as where to do builds, nightlies, and hosting? From what I've gathered from various ROM devs so far is that if you host on Goo.im, that will let you take advantage of GooManager for OTA updates, right?
Click to expand...
Click to collapse
As far as the github, you can fork the CM link directly for The GNote 2 as it's supported by them. If it were not you would have to fork a dev that has ported it over. Once you setup your box, ( there are numerous "how to compile custom roms" ) you can compile your rom. Easiest would be to ask somebody that has a "clean" (no customizations) CM build that you can use, and make your own mods. After that. It all counts on how good you are with coding and making your own mods. Hope this gets you started. Youtube and google are good places to start. I always refer Android Dev section for my repos and how-to's.
It takes, above all else, patience. start here
http://forum.xda-developers.com/showthread.php?t=1946481
Chasmodo dev gives me a link where you can see tons of guide and tutorials… good for noobs but also for advanced devs… I would like to compile an aosp for n5100 that is unsupported by cyano team at the moment… so I think that is too hard
http://forum.xda-developers.com/showthread.php?p=41491498
Inviato dal mio GT-N5100 con Tapatalk 2

Development Version Control. Is there something better than git?

Hello I am wondering if there is a version control that you find more productive than git. In the past I used SVN and loved it. It worked great and got the job done. Then at work we moved to git. At first I hated git, it seems so much more complex. But now I would never go back to SVN. Git has made things easier overall and more productive. Git was well worth the learning curve.
I knew there were others but I never knew how many. I know its hard to go wrong with any version control but i am wondering.
Is there any version control you find better than git? Just curious. Would something new be worth moving to?
Thanks for your time.

Categories

Resources