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
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.
hi everyone,
As you see the topic its about AOKP team which they have a new version of ICS porting method. First they started moding the devices like Nexus-S and Galaxy nexus. After succeding they came up with other new devices and ported ICS base rom to other devices such as HTC, Xoom,Galaxy Tab.Today i talked to Roman the Dev guy from this team about our beloved TF.Unfortunately he said they wont port this rom to TF. I just started this thread to ask this team for porting this rom. I think if they see our requests they might put their efforts to make it work on our devices. Im currently using build 23 of this rom on my Nexus-s.it comes with lots og built in features.
here is the link for the website.Head over it might be interesting for you.
http://aokp.co
Sent from my Nexus S using xda premium
You said yourself they already said no. Respect their decision and leave them alone; if you don't like the decision you can port it yourself.
From their point of view, I can see why they said no. We will--eventually, one day--get an update from Asus themselves, which will satisfy 99% of users. The remaining 1% will get mods based on the Asus stock roms, just like they do now. There's also already a partially completed port underway by somebody else.
Why would they waste their resources on the TF101 when there are plenty of other devices that have no ICS port, and no chance of getting one from their manufacturer, which they could work on?
Actually, the correct guy to ask for a port is this guy @ProTekkFZS . He recently went on a spree porting aokp to many devices. Roman only port to devices that he is currently using which are gal nexus, nexus s and gal tab.
Sent from my Galaxy Nexus using XDA App
if they dont want to port it got to respect that decision but if they would i would be sooooo happy a really great rom would use it
roman recieved a htc sensation from rootzwiki and he hasnt even ported it there yet so i wouldnt hold my breath dude... although it would be epic...
Sent from my Revolver Powered Asus Transformer
there is a plan for cm this is nothing compared to that and then there will be miui
pashinator said:
there is a plan for cm this is nothing compared to that and then there will be miui
Click to expand...
Click to collapse
1, MIUI won't come to tablets until Xiaomi makes a tablet UI version
2, CM is nowhere yet for the TF
3, Currently AOKP provides more control and access to things than CM. It was stated Cyanogen by himself that CM9 will NOT contain the old CMParts style settings, but rather have them in their respective submenus. AOKP goes on the CM7 way, having a separate app what can switch controls on-off. I'm already using it on my phone (ZTE Blade), and it's currently more stable than CM or even an AOSP build.
fonix232 said:
1, MIUI won't come to tablets until Xiaomi makes a tablet UI version
2, CM is nowhere yet for the TF
3, Currently AOKP provides more control and access to things than CM. It was stated Cyanogen by himself that CM9 will NOT contain the old CMParts style settings, but rather have them in their respective submenus. AOKP goes on the CM7 way, having a separate app what can switch controls on-off. I'm already using it on my phone (ZTE Blade), and it's currently more stable than CM or even an AOSP build.
Click to expand...
Click to collapse
1, Miui for tablets could become a reality without Xiaomi since they decided recently to change their code in Open source...so maybe one day
2, not yet, sure, even if CM has already talked about TF cm9 to come
3, here i think it really depends on the phone : with my Nexus S, aokp is pretty stable and smooth, but not as some other aosp (Pete Alfonso's) or CM (fitsnugly's kangs) for example.
Let's first get next Paul's builds, Asus's release then, and CM9 eventually.....at this point we all should be Fulfilled.
kptnk said:
1, Miui for tablets could become a reality without Xiaomi since they decided recently to change their code in Open source...so maybe one day
2, not yet, sure, even if CM has already talked about TF cm9 to come
3, here i think it really depends on the phone : with my Nexus S, aokp is pretty stable and smooth, but not as some other aosp (Pete Alfonso's) or CM (fitsnugly's kangs) for example.
Let's first get next Paul's builds, Asus's release then, and CM9 eventually.....at this point we all should be Fulfilled.
Click to expand...
Click to collapse
1. First of all, they haven't gone totally open source yet. And to include a tablet overlay, that would be a huge work. Not just graphics, but compatibility, screen issues, alignments, and such.
2. There will be a CM9 build, but only after CM9 is stable enough, and Asus released theirs so Bumble-Bee, RaYmAn, Roach, and the others can make a working one. So no CM9 for now
3. Yes it depends on that too, but show me any point of CM9 having more feature than AOKP. AOKP derives directly from CM9 sources, with the additional apps and features, plus fixes. So I consider it more mature.
Paul already published his sources for the TF, so we could easily grab his tree, change some stuff for AOKP, and make a build. I don't have quite the PC for such building processes, it would take days, and my electricity bill is already over the limit - so I can't do it definitely. But if there's someone else willing, everything can be made
fonix232 said:
1. First of all, they haven't gone totally open source yet. And to include a tablet overlay, that would be a huge work. Not just graphics, but compatibility, screen issues, alignments, and such.
2. There will be a CM9 build, but only after CM9 is stable enough, and Asus released theirs so Bumble-Bee, RaYmAn, Roach, and the others can make a working one. So no CM9 for now
3. Yes it depends on that too, but show me any point of CM9 having more feature than AOKP. AOKP derives directly from CM9 sources, with the additional apps and features, plus fixes. So I consider it more mature.
Paul already published his sources for the TF, so we could easily grab his tree, change some stuff for AOKP, and make a build. I don't have quite the PC for such building processes, it would take days, and my electricity bill is already over the limit - so I can't do it definitely. But if there's someone else willing, everything can be made
Click to expand...
Click to collapse
1 & 2, i agree, that's sure.
3, aokp has indeed for now more features than cm9 and kept cm7 idea with nominated menu, which is more than rich of full customization possibilities. My point was in fact on the stability, efficiency and smoothness : there are, for nexus s at least, aosp roms and some cm9 builds which are better than aokp. So not in terms of "quantity" but of a certain idea of quality. Certain idea, because it is of course a question of point of view. That said, i love Roman's work.
I wish i could build on Paul's and Roman's sources for our beloved TF, but even if my electricity bill could eventuelly bear it (for a time), i have neither the pc, nor the knowledge to do so, which is worse .....here's just a very greatful and curious user....
How many times has there been multiple official builds for the same Android version? The JWR build pushed ota to our phones is much more stable than the JSS Roms. However for some reason AOSP supports the JSS build which also means everyone building Roms is also using JSS as a base. Sorry but "occasional" deadlocks and freezes is something isn't stable. Cataclysm is a JWR based ROM that works really well. Just wanted to see what else is out there.
Anyone else mystified why AOSP would support some broken build of 4.3 when a stable build of the same version is available?
Anyway, sorry to rant. I'll be happy when stock and AOSP are on the same page again. Come on 4.3.1!
If you read the thread regarding information about it, this wouldn't be needed..
Sent from my Nexus 4 using Tapatalk 4
Misledz said:
If you read the thread regarding information about it, this wouldn't be needed..
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
I have read the thread. I felt the need to rant despite that somewhat informational thread. Aside from that I ask legitimate and pertinent questions. Apparently you cant answer them. Nice bloated sig:good:
there are constantly different builds for aosp, while stock stays the same until an official ota update. aosp is constantly getting stuff added/fixed, since the very beginning, with differing build numbers. the difference being this time there is a big difference(change) in the kernel and graphics.
simms22 said:
there are constantly different builds for aosp, while stock stays the same until an official ota update. aosp is constantly getting stuff added/fixed, since the very beginning, with differing build numbers. the difference being thus time there is a big difference in the kernel and graphics.
Click to expand...
Click to collapse
Hey thanks for the info. But usually stock and AOSP share the same build if I'm not mistaken. I personally can't recall a time when they didn't. Aside from that I can't grasp why AOSP would officially support a build known to be broken. The best developer in the world can't somehow fix a broken source. Also not sure what you mean by aosp being constantly updated and fixed? As a n4 user how could I reap the benefits of all these changes aside from waiting for an OTA update?
RealiZms said:
Hey thanks for the info. But usually stock and AOSP share the same build if I'm not mistaken. I personally can't recall a time when they didn't. Aside from that I can't grasp why AOSP would officially support a build known to be broken. The best developer in the world can't somehow fix a broken source. Also not sure what you mean by aosp being constantly updated and fixed? As a n4 user how could I reap the benefits of all these changes aside from waiting for an OTA update?
Click to expand...
Click to collapse
as soon as there is new code available, it gets dropped into aosp immediately(usually). lets say the build number is rtt234(made up), aosp can add a rtt234a, rtt234b, rtt234c.. just like it happened for 4.2.2. aosp supports the latest build, they dont go backward. just because something might not work right, i can and will get fixed. but, just so you know, aosp can get updated 10+ times before stock sees 1 update. anyways, the issue that you are talking about, the freeze in the keyboard, affects everyone a bit differently. some people havent had one freeze yet, others get it constantly and are very annoyed. it happens to me one or twice every 2-3 days, so it doesnt bother me at all.
simms22 said:
as soon as there is new code available, it gets dropped into aosp immediately(usually). lets say the build number is rtt234(made up), aosp can add a rtt234a, rtt234b, rtt234c.. just like it happened for 4.2.2. aosp supports the latest build, they dont go backward. just because something might not work right, i can and will get fixed. but, just so you know, aosp can get updated 10+ times before stock sees 1 update. anyways, the issue that you are talking about, the freeze in the keyboard, affects everyone a bit differently. some people havent had one freeze yet, others get it constantly and are very annoyed. it happens to me one or twice every 2-3 days, so it doesnt bother me at all.
Click to expand...
Click to collapse
My point is even though AOSP is updated constantly how does the user reap the benefits or update to the latest build if its not official? I'm pretty sure they can't. Pretty sure developers can only build from an official source. So AOSP updating constantly really is a nice idea however if updated builds aren't published why should I care?
RealiZms said:
How many times has there been multiple official builds for the same Android version? The JWR build pushed ota to our phones is much more stable than the JSS Roms. However for some reason AOSP supports the JSS build which also means everyone building Roms is also using JSS as a base. Sorry but "occasional" deadlocks and freezes is something isn't stable. Cataclysm is a JWR based ROM that works really well. Just wanted to see what else is out there.
Anyone else mystified why AOSP would support some broken build of 4.3 when a stable build of the same version is available?
Anyway, sorry to rant. I'll be happy when stock and AOSP are on the same page again. Come on 4.3.1!
Click to expand...
Click to collapse
JSS is a development branch. The reason why AOSP has multiple branches is because JSS has last minute fixes for The new Nexus 7. Google knew these changes broke other devices but didn't have time to fix them so they just gave other Nexus JWR. Most custom ROMs just supports JSS because it's the latest.
Sent from my Nexus 7 using Tapatalk 4
RealiZms said:
My point is even though AOSP is updated constantly how does the user reap the benefits or update to the latest build if its not official? I'm pretty sure they can't. Pretty sure developers can only build from an official source. So AOSP updating constantly really is a nice idea however if updated builds aren't published why should I care?
Click to expand...
Click to collapse
builds are published constantly. look at the development threads. for example, Rasbean jelly, an aosp ROM, gets built that day or the next, after a code drop. that's the beauty of running aosp builds. stock ROM users get updates only after an ota, while anyone can build from aosp whenever they feel like it.
simms22 said:
builds are published constantly. look at the development threads. for example, Rasbean jelly, an aosp ROM, gets built that day or the next, after a code drop. that's the beauty of running aosp builds. stock ROM users get updates only after an ota, while anyone can build from aosp whenever they feel like it.
Click to expand...
Click to collapse
Hey thanks for clarifying. I have been following both development threads. And the smoothest ROM I've tried is Cataclysm which is a JWR based ROM.
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.