I'd like your impressions about the MIUI update system, which occurs every week instead of nightly build.
What do you think of it? Is it something that CyanogenMod should put in place ?
Personnaly : I think it is a good method for testing over time. This allows to test more thoroughly builds.
It would be one thing if each nightly was lovingly hand-constructed by a single man working tirelessly to ensure that every day we had a completely new, solid build to flash to our phones, but it's compiled and posted automatically. Commits go in, it's built, and it either works or it doesn't. There isn't any testing being done aside from install a nightly and ***** if it doesn't work.
How exactly would it change if it went to weeklies except there'd be a much larger batch of commits to sort through when something inevitably breaks? Instead of being able to narrow it down to one day's commits causing an issue, now you're looking through seven days' worth of commits to track it.
All that moving to an MIUI-like weekly schedule would do is spawn a jillion KANG threads where someone is compiling and posting the nightly builds but also throwing in future commits which will just muddy the waters when it comes to actually aiding in the development by pointing out bugs. Almost no one will stick to the official weekly builds since they don't care about stability- they just want features now- so the official thread will be graveyard. And now all the issues will be spread out among every KANG thread so you can't see them all in one place.
The only way an MIUI schedule would work is if there was actually dedicated testing on each weekly release detailing what's fixed, what's broken, and what's changed by the developers/device managers in CM since that would be the only incentive to staying on the official weekly rather than the daily KANGs. Obviously this would be a lot more work on already-busy people that currently don't have to worry about it as the process is automated. They wouldn't do it (and I wouldn't blame them).
@yojlik thanks for reply. lot of thing i hadn't think about.
yojlik said:
It would be one thing if each nightly was lovingly hand-constructed by a single man working tirelessly to ensure that every day we had a completely new, solid build to flash to our phones, but it's compiled and posted automatically. Commits go in, it's built, and it either works or it doesn't. There isn't any testing being done aside from install a nightly and ***** if it doesn't work.
How exactly would it change if it went to weeklies except there'd be a much larger batch of commits to sort through when something inevitably breaks? Instead of being able to narrow it down to one day's commits causing an issue, now you're looking through seven days' worth of commits to track it.
All that moving to an MIUI-like weekly schedule would do is spawn a jillion KANG threads where someone is compiling and posting the nightly builds but also throwing in future commits which will just muddy the waters when it comes to actually aiding in the development by pointing out bugs. Almost no one will stick to the official weekly builds since they don't care about stability- they just want features now- so the official thread will be graveyard. And now all the issues will be spread out among every KANG thread so you can't see them all in one place.
The only way an MIUI schedule would work is if there was actually dedicated testing on each weekly release detailing what's fixed, what's broken, and what's changed by the developers/device managers in CM since that would be the only incentive to staying on the official weekly rather than the daily KANGs. Obviously this would be a lot more work on already-busy people that currently don't have to worry about it as the process is automated. They wouldn't do it (and I wouldn't blame them).
Click to expand...
Click to collapse
I fully agree with what you say.
Nightly builds and test build are two different things. Probably it would be usefull to have beta builds with more frequent updates than RC's but that depends only on the amount of spare time the developers have.
I could see keeping nightlies the way they are. Just an automated build for those that want to try it. But it could be a good thing to have weekly builds if you are looking to possibly have more "stable" builds (or rather, not as eratic as the nightlies) available for the long periods of time between stable releases and/or release candidates. I could also see this a good way to minimize the freakouts that happen with some people when the run the nightlies. But, and there always is a but, that also would create more work for someone, so I guess that would depend on whether or not it is worth it and/or whether someone wants to take the time for it.
But I do feel that nightlies should stay in place. They become invaluable in trying to get a solid build and to take care of regressions quickly.
bassmadrigal said:
I could see keeping nightlies the way they are. Just an automated build for those that want to try it. But it could be a good thing to have weekly builds if you are looking to possibly have more "stable" builds (or rather, not as eratic as the nightlies) available for the long periods of time between stable releases and/or release candidates. I could also see this a good way to minimize the freakouts that happen with some people when the run the nightlies. But, and there always is a but, that also would create more work for someone, so I guess that would depend on whether or not it is worth it and/or whether someone wants to take the time for it.
But I do feel that nightlies should stay in place. They become invaluable in trying to get a solid build and to take care of regressions quickly.
Click to expand...
Click to collapse
To address your first point, it would be nice to have a tested build for weekly release but you rightly point out the flaw: someone's going to have to test and document it. That's simply not going to happen.
Also it's kind of mutually exclusive- you either have weeklies and don't have nightlies, or you have it the way it is. Otherwise why not just say that every Wednesday's release is the "weekly" release and all the others are nightly? The alternative to this is to say that "no, the weekly release would be a more stable branch and the nightlies would be automatic" but that's the exact system we have now with RCs and Stable/Final versions the only difference being mandating a weekly schedule and I think we know how Cyanogen feels about release schedules. What would happen in practice is that week after week the "weekly" branch would remain the same until a point release happens. Which is exactly what happens now.
The reason it works for MIUI and won't for CM is because MIUI is closed source and CM is open. With MIUI you have to wait for the weekly release, there's no alternative. That can't be the case for CM since anyone can compile it whenever, and they would do it nightly if the present nightlies were to go away.
Obviously this is all a mental exercise but the fact remains that there's no practical way to implement a weekly schedule nor any benefit over the current system for doing so.
Perhaps both?
"Bleeding Edge" nightly for those who need their fix
Plus a more "Stable" yet regular build, could be weekly, fortnightly or even monthly.
Sent from my Nexus One using XDA App
Nightlies are tiring to keep up with, and where i am at, I suffer alot having to download regularly the whole 83MB to install on my phone. Having regular semi stable releases for new features is a very important.
What i usually do, is read the nightlies thread looking for comments about any problems being faced in the latest nightly, and based on those comments I decide wether or not i download the nightly.
It's kinda the same concept since the people installing the nightlies are acting as the testing team, but not in a dedicated professional kinda way.
I do the same thing--look for changes that impact me.
I don't flash every nightly, and not even every MIUI weekly
As we all know--big changes to CM7 are not coming as fast as they use too and nightly flashing almost seems not necessary--except for the addicts--
I was one, but now reformed--
It's fine the way it is, like rugmankc said you don't have to flash every nightly but it's good to have. I use to flash every nightly to but not anymore. Only if it's worth it.
Plus if there's something wrong with a new build, a fix is usually only a nightly away as opposed to a week away.
baseballfanz said:
It's fine the way it is, like rugmankc said you don't have to flash every nightly but it's good to have. I use to flash every nightly to but not anymore. Only if it's worth it.
Plus if there's something wrong with a new build, a fix is usually only a nightly away as opposed to a week away.
Click to expand...
Click to collapse
I agree totally ....
Although a monthly would be nice at least some sort of stable build for all those who don't flash nightlies with the side effect of having lots of people performing some sort of a "long time" test.
At least certain builds should could be tested a little longer than 24 hours for a some kind of quality feedback if you can say so.
As most of the others here I check the changelogs for each of my devices and decide whether to flash or not.
Kelvino9 said:
Although a monthly would be nice at least some sort of stable build for all those who don't flash nightlies with the side effect of having lots of people performing some sort of a "long time" test.
At least certain builds should could be tested a little longer than 24 hours for a some kind of quality feedback if you can say so.
As most of the others here I check the changelogs for each of my devices and decide whether to flash or not.
Click to expand...
Click to collapse
Nightly builds are NOT tested at all. Individual commits are but not the build. Only RC builds are tested by respective maintainers.
temasek said:
Nightly builds are NOT tested at all. Individual commits are but not the build. Only RC builds are tested by respective maintainers.
Click to expand...
Click to collapse
I'm aware of that, what I was thinking of is that there should be a more frequent RC or beta release as the gap between official releases got bigger.
The last stable release was released in May and the latest RC by the end of June.
For flashaholics like us nightlies are totally fine, but for the more casual user converting to CyanogenMod a regularly updated release would be nice.
Related
Hi guys
After reading around the forum a bit, it seems some people were in similar situations as me, but I still don't have a definite answer.
I have been using a HTC Dream for about a year, and have been an avid fan of cyanogenmod. Although I like the fact that it's rooted and I can install any ROM i liked, I stuck with cyanogen because:
1. It's extremely stable
2. It's well established - they guys got their own site, a central location for all ROM info, all files are found in the same place, they continuously update the ROMs and it pretty much always gets better
The above points for me were reason enough to not even bother with any other ROM. I bought a HTC HD2 a few days back, and I now want to have the phone dual boot Android. What android rom is as good as cyanogen, where "good" is defined by my points above? I know there is a ported cyanogenmod rom, but how well does the port work, will it be updated often as new cyanogenmods get released, etc? Also, I'm no fan of nightly builds, so I don't want a port based on a nightly build - it must either be experimental, release candidate or stable. I also want to stick with the ROM I choose, so it should be continuously updated for the foreseeable future..
First of all, you say you don't want nightly builds, but experimental is okay? Not exactly following, but hey.
There are a couple of CM based roms, if i'm not mistaken 3 are still being maintained:
-JDMS
-HD2ONE
-Mychiprima's (not sure if I'm spelling his name right here) build, it doesn't really have a name (thread contains "htc_linux_wince" at the very beginning)
Mychiprima's builds are based on the autobuild, and are therefor not checked and may contain bugs. JDMS and HD2ONE however are being thoroughly checked & optimized by the respective chefs, so I don't really see a point in not trying them.
Still, if you really want builds based on CM-stable there's always shubcraft and hyperdroid, but both have been discontinued for some weeks already, so you won't get the recent optimizations.
yusufm786 said:
Hi guys
After reading around the forum a bit, it seems some people were in similar situations as me, but I still don't have a definite answer.
I have been using a HTC Dream for about a year, and have been an avid fan of cyanogenmod. Although I like the fact that it's rooted and I can install any ROM i liked, I stuck with cyanogen because:
1. It's extremely stable
2. It's well established - they guys got their own site, a central location for all ROM info, all files are found in the same place, they continuously update the ROMs and it pretty much always gets better
The above points for me were reason enough to not even bother with any other ROM. I bought a HTC HD2 a few days back, and I now want to have the phone dual boot Android. What android rom is as good as cyanogen, where "good" is defined by my points above? I know there is a ported cyanogenmod rom, but how well does the port work, will it be updated often as new cyanogenmods get released, etc? Also, I'm no fan of nightly builds, so I don't want a port based on a nightly build - it must either be experimental, release candidate or stable. I also want to stick with the ROM I choose, so it should be continuously updated for the foreseeable future..
Click to expand...
Click to collapse
check this out http://android.hd2roms.com/
StephanV said:
First of all, you say you don't want nightly builds, but experimental is okay? Not exactly following, but hey.
There are a couple of CM based roms, if i'm not mistaken 3 are still being maintained:
-JDMS
-HD2ONE
-Mychiprima's (not sure if I'm spelling his name right here) build, it doesn't really have a name (thread contains "htc_linux_wince" at the very beginning)
Mychiprima's builds are based on the autobuild, and are therefor not checked and may contain bugs. JDMS and HD2ONE however are being thoroughly checked & optimized by the respective chefs, so I don't really see a point in not trying them.
Still, if you really want builds based on CM-stable there's always shubcraft and hyperdroid, but both have been discontinued for some weeks already, so you won't get the recent optimizations.
Click to expand...
Click to collapse
Thanks for that info. When I said experimental, I meant their beta versions - maybe my terminology is a bit wrong, but I know with the Dream, sometimes they used to release a beta version, then a RC, then a stable. From my understanding nightly builds were often buggy as they weren't tested. I'l have a look at those ROMs you suggest though. Aside from cyanogen, are there any other ROMs you think fit my two point criteria I gave in my first post?
leon98408 said:
check this out - link
Click to expand...
Click to collapse
Thanks a lot. That's very helpful. I'll have a look through that
yusufm786 said:
Thanks for that info. When I said experimental, I meant their beta versions - maybe my terminology is a bit wrong, but I know with the Dream, sometimes they used to release a beta version, then a RC, then a stable. From my understanding nightly builds were often buggy as they weren't tested. I'l have a look at those ROMs you suggest though. Aside from cyanogen, are there any other ROMs you think fit my two point criteria I gave in my first post?
Click to expand...
Click to collapse
I assumed that's what you meant, but RC's and nightlies are both just called experimental.
It's true nightlies as such aren't tested, because they are autobuilt. But the code that goes into it (in modules) does get tested first, so you'll usually have a nice working rom. (I'm talking about officially supported CM devices now, I already said how we do it with HD2).
There are other established builds (on HD2, you don't call them Android ROMs, but builds, because they run from sd card. ROMs are WinMo) yes, MDJ's got a whole series but I'm not a big fan of Sense myself. They're pretty popular though!
StephanV said:
I assumed that's what you meant, but RC's and nightlies are both just called experimental.
It's true nightlies as such aren't tested, because they are autobuilt. But the code that goes into it (in modules) does get tested first, so you'll usually have a nice working rom. (I'm talking about officially supported CM devices now, I already said how we do it with HD2).
There are other established builds (on HD2, you don't call them Android ROMs, but builds, because they run from sd card. ROMs are WinMo) yes, MDJ's got a whole series but I'm not a big fan of Sense myself. They're pretty popular though!
Click to expand...
Click to collapse
Ah i see. Thanks man - I got a lot to learn
Here's what Cyanogen said on the Official CyanogenMod Forums.
http://www.cyanogenmod.com/home/a-note-on-unofficial-ports-and-how-to-get-it-right
With this said, why don't we jump on the bandwagon and just join the CM team? Why don't we make this thing official (if we haven't tried already)? Just a thought, so don't kill me with your opinions. The Devs here are freakin' legit here and I'd like to see 'em do some of the work on the CM Team.
I trust the devs I download from because I follow their work. I don't need it to be "official". Besides, I like the personal touch and one-on-one support I get right here on the xda eris forum. And there's variety.
We could debate the politics of branding and what is CM and what is not CM. But the devs here disclose their sources, changes, known issues and brand their roms as uniquely their own while providing the support and updates. I don't think there's any confusion as to what is 'official' and what is not as the Android Police article referenced in CM's statement implies.
+1. The devs here are excellent, and the devs that base there ROMs on CM list them as "based" on CM not the official CM ROM. I'm not aware of any confusion that this has caused. I'm also not sure what creative constraints would be put on our devs if they went CM. I like the way they individualize the roms for thier personalities and their audiences. I also am not sure what benefit would come with being an "official" CM rom. Just my 2 cents.
Don't get me wrong, I'm not discrediting the Developers that cook these ROM by ANY MEANS whatsoever. They do incredible work with what they push, but here's what I'm saying. The CM ROMS are based off of Official CM Source Code, yes, but I think we'd be making it way easier on ourselves and the developers if we were an actual part of CyanogenMod. If we were a part of CM, then we'd get the CM ROMS as perfect as they can get and THEN the developers can add their own customization to a ROM based off of the Eris Release of CyanogenMod. They all are already doing the work that it would take to actually /BE/ a part of the CyanogenMod team, so why not get on with CyanogenMod so we can be official, and THEN the devs can customize and tweak ROMS they way they see fit?
Once again, absolutely NO discredit to the developers here, and I understand what it takes to keep these ROMS current and I am very appreciative of their work.
The CM ROMs that we have are either built from CM source or ported from the Hero builds already. I'm not really sure what this would give us other than maybe a "go team go" feeling and maybe a little more help than we already get. But the Eris and CDMA Hero are so similar, that doesn't matter much in my opinion as long as any Hero issues get worked out.
The CM buildbots are just building from source and posting the results, much like you would get if you ran EasyDev or did it manually. Now, there's a lot of work going on before that with the code, of course. But... That's what we use too.
I'm not against this at all. It just means that someone will have to 1) want to do it 2) have the time 3) convince Team Douche to let them in. I seem to remember that someone asked early on and the response was that we had to send them an Eris. This might have changed.
This comes up every so often. I guess one of us can find out what we would need to do at least...
Nothing would really change for the end user if we became official cm at this point. Basically one of the devs here that builds from source would submit their vendor tree to the cm source and they would be responsible for maintaining it just like we do now. The only real difference would be that it would get built by the cm build bot and nightly's would be released. I tweeted to cyanogen about getting my 2.2 tree in there along time ago when 2.2 was new but either I did it wrong(not a twitter person lol) or it just got lost in the many many tweets that go through cyanogens account. I never really pushed the issue more because of the extra time it would take me personally and it was just easier to work on my own schedule.
The only added benefit would be that maybe if there was an issue we could not fix then the cm team would take an extra look at our specific phone to help out but really since our phone is so close to the hero and it has official support they sort of fix most of our bugs anyway. I've personally always tried to give the cm team all the credit they deserve(which is alot) and I think the other dev's do the same.
Here's what Cyanogen posted up to www.cyanogenmod.com a week or so again. It looks like we'd need an interested dev here to stop by #cyanogenmod-dev on Freenode to start the process.
I think (and I use xtrSENSE, so I could be wrong) that a lot of people would like and "official" CM port for the Eris, just so they'd have "peace of mind" knowing they've got something "official."
And again, as we've seen mentioned in this post, it couldn't hurt to ask. Provided Team Douche doesn't actually want an Eris, we only stand to gain extra help on our ports.
Cyanogen said:
There’s been some recent talk about unofficial versions of CyanogenMod being created and released on sites like XDA, with large amounts of missing features and broken functionality, and I just wanted to talk about our position on this.
An “official” CyanogenMod version is one that uses our code review system, our source repository, and our mirror network. It should look, act, and feel like CM on any other device, and more importantly, it should follow our release schedules (which is a “when it’s ready” kind of thing, but we do plan our final/RC releases when we feel it’s ready). Most importantly, no major hardware functionality should be broken.
We want to see CM available for every device out there, and our infrastructure (and our developer community) is there for anyone to use. We spend a lot of time making new releases of Android backward-compatible with devices that are not ready for them, and we also spend much time making all of these (sometimes not so pretty) changes co-exist together without breaking other devices. The more eyes on your code, the better it will be.
That said, as much as we’d like it to be, the CMSGS project is not yet an official part of CyanogenMod. There are also a number of other unofficial ports out there which haven’t been submitted to us that we’d love to include. If you’re interested, stop by #cyanogenmod-dev on Freenode. If you didn’t get it from our mirror network or the CM forums, don’t expect it to be up to our standards.
The biggest thing to keep in mind when porting to a new device is to think about how your change is going to affect other devices. This is the biggest reason why we aren’t supporting Samsung devices other than the Nexus S yet. Don’t change hardcoded default values just to suit your device. Use the configuration options available, or add new ones with the original values as defaults. Do a build for another unrelated device after you make your changes (it helps to have another device to test with, of course) and verify it as well. Android was made for this, so do it right.
Like I’ve said so many times before, CyanogenMod is all about the community. And our community can help you too. I’d love to see more of these ports contributed to the project- it’s only going to make things better. We’ve grown from just a mod to what I’d call an “Android distribution” and we need to keep our standards high.
Click to expand...
Click to collapse
Oh no, does this mean we're all running unofficial CM ROMs ?
Wait, everything is working fine though... Official, unofficial, pffft
hallstevenson said:
Oh no, does this mean we're all running unofficial CM ROMs ?
Wait, everything is working fine though... Official, unofficial, pffft
Click to expand...
Click to collapse
+1 10 char......
A dev would have to maintain the device and be committed to building it up, like Darchstar was (is?) for the Hero CDMA. It really all depends on the Dev/Devs for the device, for example I've seen Cyanogen say in his twitter that he would also like to see the Dream/Saphhire continue to be developed for but no one has stepped up to maintain it. I can also only imagine that there are some qualifications for someone to maintain a device. Here is a list of the current maintainers for the devices
https://github.com/cvpcs/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn
Yeah, I can understand that. That's all I was saying, though. If they were doing all of the same work anyway I just thought it would be nice to have. I also didn't know if anyone had pursued this in the past, but seeing as how Conap had already tried I think I'm good with that. I also have no problems running the unofficial ROMs, just so you know. Thanks, guys!
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Hungry Man said:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Click to expand...
Click to collapse
the way i do it is best for me,,and seems to be going fine,,, the cm7 ports have been alot better then the froyo ,, and alot faster ,, look how long it took the froyo camera to work,, gb the camera works outta the box,,
Hungry Man said:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Click to expand...
Click to collapse
There is more than one definition of porting that people are using around here.
1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)
2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)
Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.
The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)
gnarlyc said:
There is more than one definition of porting that people are using around here.
1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)
2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)
Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.
The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)
Click to expand...
Click to collapse
I thought it was a girl
tazzpatriot said:
I thought it was a girl
Click to expand...
Click to collapse
Its a dude.
http://www.youtube.com/watch?v=3zb64y6Nvs0
refthemc said:
Its a dude.
http://www.youtube.com/watch?v=3zb64y6Nvs0
Click to expand...
Click to collapse
nope still a girl
http://www.youtube.com/watch?v=vwIa2S0YQs4
FYI: http://twitter.com/cyanogen/status/45246447385452544
@cyanogen said:
@Algamer we don't officially support the eris, it would be nice if someone doing the porting joined up with us though
about 8 hours ago via web in reply to Algamerhttp://twitter.com/Algamer/status/45235578886815744http://twitter.com/Algamer/status/45235578886815744
Click to expand...
Click to collapse
I think OUR devs are doing just fine. Why change now?
wildstang83
wildstang83 said:
I think OUR devs are doing just fine. Why change now?
wildstang83
Click to expand...
Click to collapse
Our devs are doing more than just fine, especially considering the amount of development we STILL have going on even though the Eris was a short-lived device that was EOL'd after like 8 months, was mid-range compared to the original Droid, and is a pretty niche device being MDPI on Verizon...
Why change now? That's a good question and I don't have a great answer. Like some have said on this post, maybe we'll get more support with bugs, etc. Additionally, a lot of the users here on XDA are looking for consistency. Since many who read and post here lack the skill set to do any meaningful ROM development themselves, they rely on the kindness of willing devs. However, devs will often add their own "personal touches" to their ROMs, which is great and well within their right to do. Having said that, many users are just looking to for something where they know, "Oh OK, so this is the base CM ROM that's officially distributed."
Personally, I don't care whether we have an "official" CM build or not for the Eris. I'm pretty reserved when it comes to ROMs for everyday use and am still using xtrSENSE as my default. The only reason I posted up cyanogen's recent tweet was to show that cyanogen himself is well-aware of the Eris development, is personally following the Eris ports, and is open to a partnership. My hope is that, by bridging communication, I am doing my part in helping to expose any possible mutual benefit (Eris XDA devs, ROM end-users, and Team Douche at CM) that could be gained by considering an "official" build. Ultimately, I understand that this is a decision that can only be made by the devs and also, not fulling understanding ROM development or having the skill set myself, I believe they are in the best position to make that decision. Like I said, I'm merely acting as a messenger, bringing this communication to light on our forum.
Last night, +Steve Kondik took to twitter to vent a little bit:
"CM has been getting a lot of crap lately for taking so long with a release. Guess what? It's not that easy. We don't just call something stable unless we mean it. *Also, RC1 is soon!* The most stable devices will get the RC first. The system we've put in place should allow other devices to catch up quickly. More details later this week "
Now to combat the obvious questions:
# As Steve stated, this will not be for all CM9 supported devices. The Nexus S and Galaxy Nexus can be considered safe bets, but the final list won't be available until release day.
# As always, the proper day of release is difficult/impossible to predict, but we anticipate a code freeze going in place tomorrow at the earliest.
# Yes, this means we will actively be running two separate RC phases (CM7 and CM9). Bug's should be reported to the issue tracker once the release is made, not in the comments on our posts.
# There has been a lot of talk surrounding Linaro in CM. While CM 9.0 won't ship with all the patches on gerrit, quite a few of them are already incorporated and others are sane enough that they will likely be there. There are still some issues surrounding the updated gcc used for the Linaro patches that don't play nice with AOSP.
# Nexus One: For the time being, the N1 will not be supported. We can get it to build/boot/run, but the hacks required break Google's CTS, so until that is rectified, you won't see any build with CM's official stamp of approval.
CM9 News
And from a followup a few hours later:
******
+Ricardo Cerqueira sat down with XDA recently for a developer interview
To piggy back on our comment about the N1 and CTS, Ricardo describes why we don't just shrug off that requirement.
Because it opened a can of worms that can’t be closed again. Getting it to work needed some very ugly workarounds that directly go against Google’s compatibility document for ICS. An app developer targeting ICS as a minimal version for his apps has the right to expect some functionality to be guaranteed on a device that claims to be ICS, that wasn’t (and isn’t) true for ICS builds with these hacks. That’s one the main reasons CM9 does not officially include a bunch of devices that are “working.”
...and some users understand that, but a lot don’t, and they’ll submit error reports on those apps, or they’ll rate it badly at the Play store. This is not a hypothetical scenario, it has happened whether we like it or not, asked for it or not, CM’s userbase is large enough to matter, even if you don’t count derivatives. We have a responsibility not to cause that kind of grief to app developers and we did. With all the mostly bull**** talk about fragmentation, we actively contributed to a break in the platform, no matter how small. That’s not a good thing :X People SHOULD know these builds contain hacks, but you’ve surely realized by now that they don’t
******
dookie23 said:
....so until that is rectified, you won't see any build with CM's official stamp of approval.
Click to expand...
Click to collapse
so.... is that ever gonna get rectified
charlie_su1986 said:
so.... is that ever gonna get rectified
Click to expand...
Click to collapse
I wonder what are the hacks he mentioned in the post. Was it the hboot hack, m2sd hack or swap partition...etc?
what is all the fuss about CM9 not releasing a rom officially when we have quite a few talented devs that have already given us the choice of running a near perfect ICS Rom on our nexus one?
EDIT: BCM offers CM9 features, AOKP offers us users the choice of AOKP features and texasice rom has a twist of its own features to. I do not see a problem with CM not releasing an official rom
Kannibalism said:
what is all the fuss about CM9 not releasing a rom officially when we have quite a few talented devs that have already given us the choice of running a near perfect ICS Rom on our nexus one?
EDIT: BCM offers CM9 features, AOKP offers us users the choice of AOKP features and texasice rom has a twist of its own features to. I do not see a problem with CM not releasing an official rom
Click to expand...
Click to collapse
Don't get me wrong, I love seeing the talented devs make awesome progress on kang'ing CM9 and things are coming together nicely. What I am getting at is not whether Cyanogenmod is releasing a CM9 rom officially for the Nexus One, but it's what Ricardo Cerqueira said about the hacks breaking Google CTS. This could mean that apps might not run or worse yet, FC's for no reason.
Now, the real questions are, what are these hacks Ricardo was talking about and is that gonna get rectified?
the hacks they talk about could be small stuff like ta camera fix etc since vendors do not always release new drivers.I would say that the nexus one is using a few hacks for drivers in order to make everything work better
I suspect it's a combination, both messing with HBOOT partition sizes (which is not a *bad* thing, but involves a lot more risk than just flashing a new ROM) and the nasty driver hacks that the poor dev's have had to do to try to working around the lack of a Broadcom driver, since they saw fit to release neither a driver nor sufficient documentation. It's hard to see how either could be overcome for an "official" CM9 release. I feel like it's a bit of a chicken and egg problem; with sufficient dev attention things could probably be brought into acceptable shape, but unofficial ports will never have sufficient dev attention.
Disclaimer: I really appreciate all the work that's been done by everyone on all the community ROMs. It's a hard, often thankless job, whether you're debugging mystery driver issues on an older phone or trying to coordinate a release for dozens of different devices with angry, impatient fans. While I'd love to have an official, flawless ICS ROM, at least we get more love from the community than we did from Google
decoherent said:
I suspect it's a combination, both messing with HBOOT partition sizes (which is not a *bad* thing, but involves a lot more risk than just flashing a new ROM) and the nasty driver hacks that the poor dev's have had to do to try to working around the lack of a Broadcom driver, since they saw fit to release neither a driver nor sufficient documentation. It's hard to see how either could be overcome for an "official" CM9 release. I feel like it's a bit of a chicken and egg problem; with sufficient dev attention things could probably be brought into acceptable shape, but unofficial ports will never have sufficient dev attention.
Disclaimer: I really appreciate all the work that's been done by everyone on all the community ROMs. It's a hard, often thankless job, whether you're debugging mystery driver issues on an older phone or trying to coordinate a release for dozens of different devices with angry, impatient fans. While I'd love to have an official, flawless ICS ROM, at least we get more love from the community than we did from Google
Click to expand...
Click to collapse
I agree with this post i would put the blame on google for not pushing the vendors for the broadcom drivers since android is open source after all but once again great works by our devs and thanks for letting us experience the latest versions of android on our devices
EDIT: i must admit that i have better devices to use than the nexus one but the community keeps me coming back for more
Sent from my Nexus One using xda premium
I noticed that there is a nightly for 1/21, and also an experimental M1 build for 1/21. What is the difference? Why the different labels. I picked the experimental because the nightly didn't want to download properly.
chilimac02 said:
I noticed that there is a nightly for 1/21, and also an experimental M1 build for 1/21. What is the difference? Why the different labels. I picked the experimental because the nightly didn't want to download properly.
Click to expand...
Click to collapse
Before a mod moves this thread for being in the wrong forum I'll answer. It's pretty self explanatory really. It's an experimental build probably due to some significant change/fix that they want to get tested quickly by putting it out there to the general public. I know one of the issues had to deal with BT audio (At least on the SGS3). You can always look at the changelogs to see the specific changes.
This if from their page: With CM10 we started doing “M-Series” builds every month. These builds are intended to be mostly stable and ready for everyday use. We suspended building these after the initial release in order to focus on 10.1, which is now on track to a stable release. Today we are doing our first M build for 10.1, based on Jelly Bean MR1. More devices are being worked on, and are available as nightly builds for the time being.
Looks like it is a mostly stable build, and they will be releasing 1 each month. The nightly builds will continue to be released alongside the M builds. http://www.cyanogenmod.org/blog/cm-10-1-m-series-builds-have-arrived
I believe nightlies are built automatically on a nightly basis, whereas experimentals are user-initiated and one-time.
Hello guys. First of all I'd like to say I'm a big of of the work of yours. I have PAC on every device I own.
Anyways, I'd like to ask you why don't you make stables weekly, in any amount of time with some release that you know that will not bug or cause harm.
I mean, I know you guys do your best in every single nightly, but me as a every day normal user, I feel skeptical about updating the ROM because sometimes I forgot to backup something or I ended up upgrading while I'm commuting and the nightly of the day comes full of bugs and I end losoing some important file.
I'm sorry, I guess you guys have heard this question before, but I have to suggest you that.
Thing is, there is simply no way that PAC can extensively test the rom on all 100+ devices every week to put out a "stable" build that guarantees to be bug free. One suggestion for people like you who want stable builds could be to just flash the rom once a week or once every other week. The posts on the thread for your device should give you a pretty good indicator as to any new bugs on the builds.
The release builds for the Nexus 4 for example are ony release canditates, milestones, tries and they are pretty old. I know, that it's way too much work to build weekly stables for all devices, but are there any plans to create stable release builds of PACman with Android 4.3 for any devices?
I love this Rom and your work and understand, that it's not easy to merge 3 Roms together. But the bugs appearing are a little annoying and sometimes make the device almost unusable (touchscreen doesn't respond anymore, no inputs possible, need to force shutdown and cold reboot).
I would love to get a more stable build of PACman.