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.
October 31st, 2011
The current and future state of CyanogenMod Nightlies
Happy thing to hear, but i want to give a suggestion to cm team, but dont know where to put it, if any body know it, then pls forward it to them, or help me to post it in right place,
It is;
Insted of putting nightlies on same device, frequently, cm builds should add an app through which newly realised patches and modes should be integrated into the rom from the device itself( just like windows updates or software updates) or some thing like update zip etc..
The advantages are..
1) avoid heavy size downloads of frequently updated nightlies
2) easy updates
3) every user/ device is stays updated
4) avoid errors and bugs more easily.
5) save a large amount of data space in server ( where all these nightlies are uploaded)
The 1ly thing should be cared is to ensure that the device gets updates in a constant manner, ie user should not install update no.2 unless he put update no.1 in the device.
Dont you seem it is nice?
Sent from my HTC Wildfire using XDA App
showlyshah said:
3) every user/ device is stays updated
4) avoid errors and bugs more easily.
Dont you seem it is nice?
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
That is a two sided knife.
Regarding point 3, if an update brings trouble, it will bring trouble for everyone. Meaning a hell of a lot of user getting their phones messed-up. The way it is now, only those who want nightlys might bump their heads into problems. Those who don`t have the time to wait for fixes stay on stable.
4) and encounter bugs and errors more easily. Imagine a problematic update that makes you incapable of answering a call. because the nature of the update, everyone gets the bug. Imagine the amount of **** that will get thrown in the direction of the CM team.
The current way is, IMO the best way.
If I misunderstood you, please tell me.
Alex_GP said:
That is a two sided knife.
Regarding point 3, if an update brings trouble, it will bring trouble for everyone. Meaning a hell of a lot of user getting their phones messed-up. The way it is now, only those who want nightlys might bump their heads into problems. Those who don`t have the time to wait for fixes stay on stable.
4) and encounter bugs and errors more easily. Imagine a problematic update that makes you incapable of answering a call. because the nature of the update, everyone gets the bug. Imagine the amount of **** that will get thrown in the direction of the CM team.
The current way is, IMO the best way.
If I misunderstood you, please tell me.
Click to expand...
Click to collapse
You said it, but its not as right as you think. The reason is the answ you may give for my following question " how frequently do you update your Linux / windows / Mac? ? Do you keep an automatic update or a manual update? And in case you are a frequent updater, can you say every 1 is like you?"
Dude i just mention to add an app, from which you can update your cm, and not necessarly it is an automatic one, it should be a manual one, just like cwm updates are notified by rommanager , you will be provided with a notification, you may or may not install it, and ofcourse every update package should have a changelog, so that you are aware of the changes.
Also the app should have an option to backup the old files in case if you want to revert back.
Sent from my HTC Wildfire using XDA App
Mmmm I'm happy the way it is.
Motto/quote : if it ain't broke don't try and fix it!!
I have yet to see a heavy size nightly or stable for that matter.I'm not having a moan at your idea but people are all different and choice is what makes us stand apart. We have an app which informs us of new builds and its then our choice of what to do with said information. There is an updated changelog page for info on each build and xda forum members have everything else regarding new builds/stable info.
My personal preference is stable but I like to test nightlys too and swap and change like the weather, so for me I say nooooooo I have everything I need where it is now. Regards Slymobi.
sent from my wilderbeast:buzz
ya you are right, stable versions are here, but what about nightlies? every week or two they are releasing a new nightly, and many of them contains major or minor bug fixes, so the user have to download, wipe(if it is needed) and flash again, dont it seems a bit discouraging?, i seem it like formatting your pc, running all the os setups, then installing your softwares etc.., some times you do all this for a small script/library change? so is that worthy enough? i dont think so. more over the developers have to build and build the update zip again and again, thats why i started thinking like this.
if you people dont like my idea, just we can stop it.
showlyshah said:
ya you are right, stable versions are here, but what about nightlies? every week or two they are releasing a new nightly, and many of them contains major or minor bug fixes, so the user have to download, wipe(if it is needed) and flash again, dont it seems a bit discouraging?, i seem it like formatting your pc, running all the os setups, then installing your softwares etc.., some times you do all this for a small script/library change? so is that worthy enough? i dont think so. more over the developers have to build and build the update zip again and again, thats why i started thinking like this.
if you people dont like my idea, just we can stop it.
Click to expand...
Click to collapse
Back-up your apps with Titanium back-up. Many nightlies can be updated with out needing to format all the partitions. (maybe cache, just to be sure).
It`s not a chore. Nobody forces you to do it. If you consider the update to be worth the work, then ok. If not, stay on stable.
EDIT: MODS don't take this as a best thread ROM please, im not willing to ask this due to everyone having his own experience and preferences, im asking for STABLE thank you hope you understand and if you are going to delete pm me on what is wrong so I can change it
Hello, I've just read the Best ROM post it, but I think im not asking the same as the best ROM
I actually want a ROM which is stable for my girlfriend, I have tested loads of roms out there, and in my opinion latest rom are the best because of new features but they can have problems in speed or bugs (which is obvious ^^ now its to your choice if you want to keep updating your rom or stick for a stable one some time)
Everyone has his favourite rom and for X reasons, I'm not asking this...
I want a stable rom for someone who doesn't want problems with his phone (sometimes I think to only reflash and leave it like that so she doesnt wine)
Im actually thinking about few roms..
1. MSGINGER4.0 (I used this rom for about a month and I didn't find any bugs and excellent battery +720p, just the problem about 2g/3g toogle which in gingerbread is impossible to make it work + cm7 settings not working make it very little customizable - for ex. disabling in notifications the bluetooth which some people never use)
2. CM7 ROM: I know there are many out there, I've tried skanwich ones and Quarx on the good old days, I think its very stable but it has a higher battery drain than the msginger4.0 but maybe its worth it for the customization
about POINT 2 I would like to get some feedback, I've been reading WhiteRabbit 1.8 edition and maniacs build, I find them very interesting but I would like to know your views after testing them, some people report bugs and this is the last thing my gf wants XD ¿could you guys tell me more about these 2 roms and why they are more stable or less than cm7 skanky?
3. MIUI? Good interface 0 bugs from my experience BUT highest battery drain out there
I know I should test myself and see, but I did that with cm10 2nd boot last quarx build (tested for 4 days).. It was the most stable rom + the best features (since it was latest build) and I decide it to put it on my GF defy... after 1 week I got the ext4 bug (didn't boot, my fault for formatting to ext4 since it was a experimental feature) so I went back to another rom but now my GF has commonly force close, freezes and data connectivity drops
SO... Don't take this a thread of what is the best build out there please, since I'm not asking for this.. Im asking for a stable rom for someone who doesn't like playing with this kind of stuff
P.D: Don't take anything I've said about all the roms badly please, I love them all and it has been my experience with them and I know maybe you have different views due to different experiences.. (I didn't believe 2 exact phones could give different bugs since I had 2 but this actually happen)
so, what is the most stable ROM out there? (thinking also about battery performance + features (this last one must be the least important when telling me your opinion ^^ thank you!))
30 views and nobody could give a short awnser
I have tried a lot of roms (CM,MIUI..etc)on my phone and there is always that one moment in the day when i feel like having the stock rom back . Unfortunately i cannot go back to the stock rom even if i wished too since i blindly flashed defy+ rom on my defy and there is no way to downgrade from BL7. Mobile companies spend a lot of money in R&D while preparing the stock rom keeping in mind a variety of users . Believe me a lot of people i know give me confused looks when i ask them if their phones are "rooted.". Thus mobile companies try to strike a balance between noob and the tech savy users and by no means are stock roms useless (yes some find them bloated) . I respect all developers for their knowledge and work and it is only because of communities like XDA can i run a JB based rom on my defy ( almost a dream) . If you are looking for a bug free rom with a good battery life i would suggest sticking to the rom that came along with the phone .
mariosanoguera, I read your assertion that this is not a "best ROM" thread, but the fact is it's close enough. The point behind that rule is to avoid debate about which ROM is good at anything....whether than be "most stable", "best for messaging", or whatever. What you're asking will cause a variety of responses, then one poster will disagree with another, then controversy starts, then arguments, and on and on. The admins of XDA have been doing this a long time, and you're not the first person to start a "best ROM" thread while trying their hardest to make it sound like it's not a "best ROM" thread. They will always be closed and always have been, and for good reason.
So please don't take this personally. This is a development-oriented site and we do whatever we can to foster an environment that promotes development. Threads which try to determine which developer's work is better than another's never turn out well, and therefore are never allowed, without exception.
Hello XDA'ers.
First let me say that this will be somewhat a post about frustration with Android devices, but it's not meant to be misconstrued as disrespect to those who contribute to the development community. I know you guys work hard at this and I do appreciate your efforts. Your ROMs have been lightyears ahead of what Samsung stock offers.
But with that said, here's my question: is there a single rom that will work properly, is stable, wont crash, etc? I have been through over a dozen different ROMs across two devices, and there's always been something small or large wrong with them. The one I'm using on my i9505 right now is by Antares One and yesterday it decided to show me three or four notifications that "Google Play Services has stopped working" per minute and today none of my SMS messages are being sent.
But it's not limited that, rather, there's always been something or other that the Android ROM didn't like, or I had to find a workaround, or had to completely reflash with something else.
Has anyone experienced this? Why can't Android just be a stable OS? I'm really thinking about switching to a Microsoft phone for my next upgrade.
DJ
Even stock roms have their problems and stability issues. If you look through the Q&A section you'll find several threads about stock rom issues.
It's not Android's fault entirely. It has to do with the phone too. Roms on my device are always stable. Yet another user running the same rom on the same device has various problems.
I am currently running AOSP Marshmallow by the JDCTeam, no problems. Bluetooth works, wifi works, mobile data works, battery is fine (I went to sleep with 70% left and when I woke up 8 hours later it still was at 70%).
the problem here is the impossible fix of many problems by developers..why? many developers are not soft engineer and maybe they dont even know how to program just know how to port and replace files and thats all..a big team for every single phone are just impossible..
so a stable rom will never come..just find the one "flawless" and keep it..
for me the stable roms are not cm..or aosp..stock rom debloated are very stable..like s6 port to s4 and debloated..is a good one
Use stock ROM for stability. Although they are not fast as AOSP but they dont exhibit strange behaviors.
Sent from my GT-I9505 using Tapatalk
DJRepresent said:
Hello XDA'ers.
First let me say that this will be somewhat a post about frustration with Android devices, but it's not meant to be misconstrued as disrespect to those who contribute to the development community. I know you guys work hard at this and I do appreciate your efforts. Your ROMs have been lightyears ahead of what Samsung stock offers.
But with that said, here's my question: is there a single rom that will work properly, is stable, wont crash, etc? I have been through over a dozen different ROMs across two devices, and there's always been something small or large wrong with them. The one I'm using on my i9505 right now is by Antares One and yesterday it decided to show me three or four notifications that "Google Play Services has stopped working" per minute and today none of my SMS messages are being sent.
But it's not limited that, rather, there's always been something or other that the Android ROM didn't like, or I had to find a workaround, or had to completely reflash with something else.
Has anyone experienced this? Why can't Android just be a stable OS? I'm really thinking about switching to a Microsoft phone for my next upgrade.
DJ
Click to expand...
Click to collapse
Like GDReaper said in his post. For us those roms run perfectly fine. Sure there are bugs, but most issues are known before you decide to flash the rom. Besides the obvious bugs that are present there is also the user. A lot of problems are caused by inexperienced users. They don't know how to set up their phone, they flash shady apps, or use modifycations of their own (Xposed for example).
Then they come to XDA and provide no usefull information at all. For example:
"The one I'm using on my i9505 right now is by Antares One and yesterday it decided to show me three or four notifications that "Google Play Services has stopped working" per minute and today none of my SMS messages are being sent."
- For example you say you use a rom by Antares One. This gives us no information at all. He has made like 4 roms for the I9505. What build? What android version?
- Google Play Services has stopped working. What gapps package did you use?
- Have you made modifications of your own?
- Are you running an up to date modem and bootloader?
Also keep in mind that if you use for example a MM build that it's a work in progress. It has to be coded from scratch. So surely there will be some bugs, but you will get the latest Android version in return with all the latest security patches.
This post is not intended to flame you in any way. I think most of your frustration comes from the expectations that you have. You cannot expect that a CM based rom will work flawlessly out of the box. It's a work in progress.
This is a very good observation. I was thinking to write this kind of post in december.
A lot of Roms are abandoned or never pass nightly and you have to flash and flash again. Then suddenly all people jump to MM as if the world is ending tomorow. It is hard to find a good rom starting with Lollipop. I see a lot of people crying after KK stability and downgrading.
People are in a hurry, devs too, to flash the newest rom.
I prefer stability. A phone is not a camera, nor a battle field for flashing.. My 2C opinion.
I like custom roms, but sadly i need stability before customisation or performance. The only rom that delivers in this is Stock TW 4.4.2. If you want to go back to Kitkat use the latest firmware for your region.
It's very hard to deliver stability with a custom rom as stability is achieved through manpower, time and resources, which can't be provided through just donations.
Roms are abandoned because people move to other devices at some point.
And you can't stay on the same android version. Most of the roms are built from other sources. Like Resurrection Remix. The developer is wescrip, and he owns an LG device. The version for our S4 is built from his sources by TJSteveMX. If wescrip switched to Marshmallow it's pretty much impossible to for TJ to keep it Lollipop.
DJRepresent said:
(...)Why can't Android just be a stable OS? I'm really thinking about switching to a Microsoft phone for my next upgrade.DJ
Click to expand...
Click to collapse
This is a more general answer:
In the Android world there is a huge diversity of devices (--> hardware) and Android versions. The next thing, you have to keep in mind: A lot of vendors and telecommunications companies include their modifications into the ROMs.
I think that due to the availability of new devices each year and all these modifications, which also include the full stop in official updates after 6 months after the release of the device, will lead to unstable (official) ROMs.
The community then tries to update the devices in their spare time to the newest versions. But they have to figure out some special settings and modifications per device. And this is a long way as it seems.
In my opinion, you should not blame the community and the developers. I think, it is more Google or the vendors that can´t agree on a good way to distribute newer Android versions (e.g. a new API layer between OS and Hardware).