I posted this question over on the Cyanogenmod forums, but honestly it doesn't look like there is much action over there, especially in regards to development. Almost everything I've read seems to be installation or request related.
I've already built and have installed CM-10 from the sources for my HTC Amaze 4G. Of course, I'm experiencing the same bugs on it that exist with the most recently available CM-10 nightlies from the main site. My goal is to squash the last few remaining bugs on this version before eventually proceeding with further development on newer branches.
My question is as follows: In the process of looking over different repos, both official and unofficial, I've noticed several incremental branches for which I can find no explanations online. For example, I can figure out that if a repo has both a jellybean and jellybean-stable branch the one marked stable is the one which was used to build the stable CM-10. However there are several branches marked with the "ds" label. For example, a jellybean and jellybean-ds, or CM10.1-ds. What does this "ds" stand for?
My guess is that "ds" means that it is "deemed stable", as in it's as stable as it's going to get, but no further development is taking place on that branch. However I'm by no means sure, which is why I'm posting. Adding confusion to the equation are several references to "double-shot" which seem to reference added performance features. Also, when there are multiple branches marked for example, jellybean, jellybean-ds, and jellybean-stable which would be the most current?
Someone with some insight please elaborate. TIA
My post fell back to page 7, so this is a bump. Someone has to know the answer. Anyone?
Related
There is a similar thread in the Captivate section (posted by sixstringsg) so I thought I would bring one here. The purpose of this thread is to encourage people to make KANG builds of CM7&9 and provide a place for them to post links to their builds. KANGS may include code that is not fully tested or they may simply be clean, up-to-date builds straight from the repo... and thus, are lightly supported if at all. If you build KANGS... post them in this thread.
I have been building these KANGS (they really call them UNOFFICIAL's now ) for my wifes phone for a while now and thought it time to post some for you guys. I recently dropped CM7 in favor of taking the wife up to CM9. Most of the builds are "clean"... meaning that I haven't cherry picked any of the changes awaiting approval in gerrit HERE
If you are coming from a Samsung ROM wipe everything. If you are coming from CM7 or another ICS ROM, at least wipe cache, dalvik, and system. You may get away with not wiping data (I do mostly).
Flashing this KANG is an open admission that you hate your phone and are intent on bricking it. I accept no responsibility for any damage that you inflict upon your phone. Kangs from Androtransfer.com WILL download using the phones browser, but you may have to rename the file .zip from .htm before you flash. If you use Firefox or Opera for downloading it, it works properly. For some reason the stock Android browser and Chrome don't parse the link correctly.
Latest KANG... download from here
Flash the 4/29 gapps with CM9. Download from here
If you want to start building CM9 for epicmtd... GO HERE
...more to come later. I will add info about cherry picking, etc...
Once you have your build environment configured, here are a couple of things that I do.
Open the local_manifest.xml (located in .repo folder) adding the following line...
<project name="koush/proprietary_vendor_samsung" path="vendor/samsung" remote="github"/>
This will sync all the samsung proprietary files and basically allow you to make builds for a phone you don't have.
For the epic, I have added these lines...
<project name="CyanogenMod/android_device_samsung_epicmtd" path="device/samsung/epicmtd" remote="github"
<project name="CyanogenMod/android_kernel_samsung_victory" path="kernel/samsung/victory" remote="github"/>
This syncs the kernel source as the kernel is built in-line and is not prebuilt.
<project name="EpicCM/epictools.git" path="epictools" remote="github" revision="ics"/>
Currently epictools allows you to turn off the backlight of the capacitive buttons unless they are pressed. Could be nice if you are watching a movie in bed on your phone.
More details... HERE (github.com/epicCM)
Cherry picking details... coming soon
FIRST!
What's different in that build?
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Zeinzu said:
What's different in that build?
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Click to expand...
Click to collapse
My guess would be nothing... we have unofficials in the gnex forum... that the guy does just to get it out to people quicker... nothing special just faster than their build bot.
Zeinzu said:
What's different in that build?
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Click to expand...
Click to collapse
That build is clean (no cherry picks) built with latest merges from the cyanogenmod ics branch.
so... unofficial "nightlies"?
Thanks for putting this up op
Sent from my SPH-D700
I updated OP to clarify why I posted this thread. Just as you said... to prevent 30 different threads of people posting KANG builds... this will be the ONE.
Since KANGs are ever changing, there is no reason to update the OP as the Kanger will post a link to his latest KANG near the end. We have the same type of threads going in Captivate and Crespo.
If this thread is deemed "not welcome" than by all means delete it. As I see it, interest in the epic is waning. I am merely trying to encourage.
This is intended as a KANG thread... not a thread for my specific kang. It is not the same as the beta 3 version. There have been merges since that ROM was built. Can I name them all? Nope.
lownox said:
This is intended as a KANG thread... not a thread for my specific kang. It is not the same as the beta 3 version. There have been merges since that ROM was built. Can I name them all? Nope.
Click to expand...
Click to collapse
OK to clarify you are saying this is newer than Beta 3 as it has merges not yet incorporated in the official CM9 thread and if anyone else makes a Kang they should just add it in a post? That part won't work. It will make it hard to find individual Kangs. If you can't maintain the OP with others' Kangs then I can stick in links, if everyone thinks this thread is useful and adds something for the Epic community.
Sent from my SPH-D700 using xda premium
I am happy to update the OP with links if other people start making KANGS. Most of the time they will be posting their builds to some central location and people reading the thread can simply follow the link, see what the latest build date is, and choose to download it or not.
My page, for example, says that if the build is anything other than a "clean" build I will note what has been cherry picked. Cherry picks aren't always stable and sometimes they even cause problems. Since there are no "nightlies" for CM9 epicmtd... Kangs are a way to be able to run the latest merged changes and maybe some cherry picks.
In my next build, I will include some cherry picks. All the forums here seem to run a little bit different. I really wasn't expecting the bit of harshness I got here. I guess I took for granted that everyone knew about Kangs (or Unofficial) builds and what they were.
legit rom!
A lot gets merged everyday. merged changes are here.
review.cyanogenmod.com
I am currently making a build with the following cherry picks... It will be building for a while. So TO BE CLEAR... will be a build with all current merged changes and four cherry picks associated with 2 overall changes...
Electrion beam animation
Option to adjust navbar glow animation duration
Here are links to the picks in gerrit. Take a look.
http://review.cyanogenmod.com/#/c/12959/
http://review.cyanogenmod.com/#/c/15578/
http://review.cyanogenmod.com/#/c/16183/
http://review.cyanogenmod.com/#/c/16184/
lownox said:
A lot gets merged everyday. merged changes are here.
review.cyanogenmod.com
I am currently making a build with the following cherry picks... It will be building for a while. So TO BE CLEAR... will be a build with all current merged changes and four cherry picks associated with 2 overall changes...
Electrion beam animation
Option to adjust navbar glow animation duration
Here are links to the picks in gerrit. Take a look.
http://review.cyanogenmod.com/#/c/12959/
http://review.cyanogenmod.com/#/c/15578/
http://review.cyanogenmod.com/#/c/16183/
http://review.cyanogenmod.com/#/c/16184/
Click to expand...
Click to collapse
I don't see cm7
Sent from my SPH-D700 using Tapatalk 2
lownox said:
[...]I really wasn't expecting the bit of harshness I got here. I guess I took for granted that everyone knew about Kangs (or Unofficial) builds and what they were.
Click to expand...
Click to collapse
Each device forum on XDA operates as it's own community. We have regulars. We have standards. We have issues we've ironed out throughout the device's lifetime.
"Kang" has generally been used to refer to stolen or leaked coding. Up until recently, it had been more of an insult to call someones rom a "kang." Terms like "unofficial" or "variant" likely would have been greeted with less suspicion. But, more specifically, you should always have a well stated OP with a clear purpose. Starting a thread by saying something like "here I will be posting official cm9 roms with no changes and any one can feel free to post theirs" is never a good idea. Especially since things can become gray-area when talking about CyanogenMod source.
Basically, you need a well-stated and well formatted OP defining what it is you're sharing and how it differs from the CM9 and CM7 threads we already have here.
The only thing I noticed is the phantom vm notification
Sent from my SPH-D700
I would like to add my 2 cents, or five, or ten, on this subject, and this being a public forum, there's nothing stopping me.
I don't really see how this thread is any different than a thread in the theme forum that has links to various theme's threads.
When I saw this thread it had been up for a while, so I didn't see how the OP was initially laid out, therefore I cannot speak on that matter, but I can say this: I feel that in its current state, the OP perfectly states the intent and design of this thread. Also, on a personal note, I'm very glad its here.
I won't say that interest in epic development is waning, but there's really no arguement that compared to a few months ago, there isn't near as much going on.
I also hope that this will encourage more devs to try their hand at ICS and CM based ROMs. I would love to see some slim ics or codename android jumpin off in this forum.
I really enjoy the epic forum and community, especially now, our forumm is well monitored and tight knit. But I also enjoy seeing new developers and new dev teams adding to the variety in our forum. This will never happen if we keep jumping on newcomers with a hostile attitude. I'm not saying anyone means to do so, but it does come off that way from time to time. This is my perspective, a member of this community for over a year, so imagine how someone new would take it.
I would like to personally extend my grattitude and a warm welcome to the epic community to the OP.
I'm sure most of us, if not all appreciate your presence.
Sent from my SPH-D700 using xda premium
Welcome to the Epic community OP:thumbup:
Sent from my SPH-D700 using xda premium
For those who followed the CM9 beta3 development cycle, we posted many test builds and received much helpful feedback toward improving beta3. We will soon post beta4-pre builds in the same fashion. Additionally, Team Epic is working on fixing some poor code quality issues in preparation for enabling official CM9 nightly builds in order to make this a more automatic process.
It seems many of the posters here are missing the latest Epic development news. If you follow +Epic CM and +CyanogenMod on Google+ you will know stuff often before it hits XDA.
Sorry if this was answered already. At the moment there is 4 you could choose from. I've read countless posts in each thread but that may be the reason why this goes over my head. I'm just trying to understand the difference between them all. I also thought I read that xoomdev said the devs couldn't make their own builds and could only release the official bricks. I know this was answered over in one if the rootz threads too but there's so many posts it would be like finding a needle in a haystack. So if anyone has the time and would like to elaborate, thank you in advance.
I am confused by this as well - it seems like there are multiple aokp and CM10 builds going around.
Very simply put you have the official builds of each which is how the main developers want the ROM to act/feel/look/etc... They also provide the code for these builds so any other developers that want to can add/subtract little tweaks here and there to make it how THEY want it to act/feel/look/etc... And that is what the unofficial builds are, "aftermarket" developers tweaking it.
EDIT: Also, if you have a bug on the official build of either then there's a 99% chance it's on all the other ones too.
Brian Gove said:
Very simply put you have the official builds of each which is how the main developers want the ROM to act/feel/look/etc... They also provide the code for these builds so any other developers that want to can add/subtract little tweaks here and there to make it how THEY want it to act/feel/look/etc... And that is what the unofficial builds are, "aftermarket" developers tweaking it.
EDIT: Also, if you have a bug on the official build of either then there's a 99% chance it's on all the other ones too.
Click to expand...
Click to collapse
Thank you!
I heard over on Android Authority that Samsung has release its JellyBean source code for the i1900. I know our phones have a different processor, so it's not going to work on our phones, but given that they share at least a name, should I be hopeful that there could be some goodness in there to help move our Skyrocket's along with JellyBean (e.g. CyanogenMod 10.1), or even hopes of an official JellyBean release from Samsung?
http://www.androidauthority.com/samsung-releases-android-jelly-bean-source-code-galaxy-s2-137715/
There is already a Samsung JB leak in Development forum, you should have taken a look there.
Trinition said:
I heard over on Android Authority that Samsung has release its JellyBean source code for the i1900. I know our phones have a different processor, so it's not going to work on our phones, but given that they share at least a name, should I be hopeful that there could be some goodness in there to help move our Skyrocket's along with JellyBean (e.g. CyanogenMod 10.1), or even hopes of an official JellyBean release from Samsung?
http://www.androidauthority.com/samsung-releases-android-jelly-bean-source-code-galaxy-s2-137715/
Click to expand...
Click to collapse
Do you read any of our threads before posting useless new threads?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Should have done a search? I did, thanks. Searched for "jelly bean source". No hits. So I posted.
And a leaked *compiled* ROM does not equal source. Now it does answer my question about the Skyrocket getting Jelly Bean, and further implies there will eventually be a source delivery. That does not mean that the regular S2 Jelly Bean source available now can't offer a more immediate impact.
Also note that the UCLK4 thread in the development forum is slightly over one day old as of now. At the time I posted this thread, it was about 12 hours old. And the one in the General section was started after.
In fact, I saw the S2 news at AA much earlier yesterday but decided to wait to ask so others with more knowledge and experience could preemptively answer my question. But, via my search, I didn't find my answer.
So, yes, I agree my thread is now irrelevant. But at the time, it was hardly as clear as the smug replies in this thread suggest.
Sorry for my rudeness in response to yours. I know you guys have to put up with a lot of newbs. But the robotic and condescending dismissals are just as annoying to see over and over again, especially after I *did* do my due diligence.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I didn't mean anything harsh in my reply, but answered half of your question, a half that seemed to me the most important one (our phone having official Samsung JB).
To answer one more thing: the sources are good for some things, namely if your goal is to patch the new kernel to the old driver binaries (the kind of work that's necessary for old and non-supported phones to run the latest OS found on their latest siblings with the same chipset) - but if your goal is to run the full OS with official latest drivers that it's built to run with, without precompiled binaries the source is good for nothing. And the patching work is futile if the official release is a month-two away.
Looking to hear pro's and con's of running nightlies
I am currently running locked and non rooted but thinking about switching to nightlies just looking to see if theres con's from the people that have switched. i realize that they are not "stable" builds and will have more bugs than the OTA's but how much more?
aford89 said:
Looking to hear pro's and con's of running nightlies
I am currently running locked and non rooted but thinking about switching to nightlies just looking to see if theres con's from the people that have switched. i realize that they are not "stable" builds and will have more bugs than the OTA's but how much more?
Click to expand...
Click to collapse
You can read the discussion in nightly builds, try the builds which are best suited you perhaps less bug or whatever, then stay on that build until have major update / changes. Because sometimes nightly updates will fix current bug but break other things.
So, what are the differences between cm11s and cm11 except the "stock" root permission?
XDA is a development site not a support site. As the term "Best" or "Most Stable" is a very subjective term, such members are expected to do their own research, read through the development threads, and decide what is "Best/Most Stable" for them.
The only results that would be posted here are what each member has found to be "Best" or "Most Stable" for them by experimentation based on their phone/usage/setup/apps/signal strength. And at times, these thread spiral into arguments over which is perceived "Best/Most Stable".
Please take the time to read through the development threads, and interact with the members there, to learn all about the software you are about to drastically alter your very expensive device with.
Which nightlies? There are no nightlies of CM11s.
But in general nightlies of a ROM have the possibility to be more buggy.
To quickly sum things up
You get the newest commits asap which can be hugely beneficial that you get fixes before anybody else. But at what cost? Like what Shoxter said, it could be buggy since it is still a work in progress. In my past experience, bugs do occur but at times they don't. They're not game changers to the point where you can't use the phone, so as long as you're aware of that risk (its pretty low) then feel free to flash nightlies.
I haven't been able to follow the D2 consolidation, then subsequent breakup by device again, but saw that apexqtmo commits on the CM12.0 branch are pretty infrequent. There was a commit on April 3rd, which makes me think it might actually be alive.
So my question is: Does CM12.0 build for apexqtmo currently? (I haven't updated my build environment since 4.4, so can't quickly test...don't really want to spend the effort if the answer is already a known "no")
(Obvious follow-on from somebody would be "if yes, what works/doesn't work?")
scotte9999 said:
I haven't been able to follow the D2 consolidation, then subsequent breakup by device again, but saw that apexqtmo commits on the CM12.0 branch are pretty infrequent. There was a commit on April 3rd, which makes me think it might actually be alive.
So my question is: Does CM12.0 build for apexqtmo currently? (I haven't updated my build environment since 4.4, so can't quickly test...don't really want to spend the effort if the answer is already a known "no")
(Obvious follow-on from somebody would be "if yes, what works/doesn't work?")
Click to expand...
Click to collapse
The short answer is 'yes', but there's some pretty big caveats.
The bare CM12 trees for apexqtmo are rather broken, and even TeamApexQ's repos currently audio is broken, but it does build. CM12.1, the answer is currently 'no'.
Magamo said:
The short answer is 'yes', but there's some pretty big caveats.
The bare CM12 trees for apexqtmo are rather broken, and even TeamApexQ's repos currently audio is broken, but it does build. CM12.1, the answer is currently 'no'.
Click to expand...
Click to collapse
Thanks for the info. Sounds like more than a quick weekend project (I was hoping it was "It works except we need to update the vold configuration" or something easy). I think I'll let the wife live with CM11 for awhile longer then.
Shame because it doesn't look like any of the lollipop builds are being updated at all. I wanted to get my feet wet with building them, but this is probably more than a starting project.
Development Forums are for developers to share their work and post their Roms and Mods.
Questions belong in the Q&A section.
Thread has been moved to correct section, please pay attention to XDA rules.