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
Hello guys, how are you doing?
I just wanted to share with you my own opinion over how Samsung deals with updates to a Galaxy Note 10.1.
Actually, many users have reported software bugs in Galaxy Note 10.1 and Samsung confirmed many like the bug of clipboard. But the bad part is Samsung ignorance of bug fixing. It is good that we will receive 4.1.2 update with premium suite preinstalled, but it is bad that we did not receive a bug fixing package!
It has been several months since the launch of the Note 10.1 that many owners of the product started to get frustrated of the bugs. I cannot copy an article and save it as note in S Note app or share it in Facebook!
Besides, Samsung released JB 4.1.1 update to some regions, stopped then started releasing 4.1.2 in the time users still have the buggy 4.0.4 for many months in several countries, if not most! Even though 4.1.1 has stability issues, Samsung shall fix current bugs of 4.0.4 before caring to release a major 4.1.2, as this needs a quite long time by Samsung for a frustrating bug to remain!
Software is as important as hardware. I do not care for receiving a new major update with hundreds of new features, as we will receive it soon or later! But for me, a stable software with only two features is far far better than a buggy one with hundreds of cool features that I am unable to use!
Samsung used to release improvement packages and push them to their software update server for their products, but it is really strange why this is not the case for Note 10.1!
Sent from my GT-I9300 using xda app-developers app
You write that you are still on N8000XXLGA.
Sorry man, but it is your fault if you chose not to update by flashing the newest firmware.
Thanks to Samsung, Samfirmware and XDA, you have this option.
Other big companies, for example Acer, LG, will not even give you this.
So why do you not update?
tweetatoo said:
Hello guys, how are you doing?
I just wanted to share with you my own opinion over how Samsung deals with updates to a Galaxy Note 10.1.
Actually, many users have reported software bugs in Galaxy Note 10.1 and Samsung confirmed many like the bug of clipboard. But the bad part is Samsung ignorance of bug fixing. It is good that we will receive 4.1.2 update with premium suite preinstalled, but it is bad that we did not receive a bug fixing package!
It has been several months since the launch of the Note 10.1 that many owners of the product started to get frustrated of the bugs. I cannot copy an article and save it as note in S Note app or share it in Facebook!
Besides, Samsung released JB 4.1.1 update to some regions, stopped then started releasing 4.1.2 in the time users still have the buggy 4.0.4 for many months in several countries, if not most! Even though 4.1.1 has stability issues, Samsung shall fix current bugs of 4.0.4 before caring to release a major 4.1.2, as this needs a quite long time by Samsung for a frustrating bug to remain!
Software is as important as hardware. I do not care for receiving a new major update with hundreds of new features, as we will receive it soon or later! But for me, a stable software with only two features is far far better than a buggy one with hundreds of cool features that I am unable to use!
Samsung used to release improvement packages and push them to their software update server for their products, but it is really strange why this is not the case for Note 10.1!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Agreed, I had to resort to manually flashing the German JB update to "fix" the PDF import problem on my Canadian N8010. I feel sorry for the average customer that bought the Note but doesn't know how (or even think) to flash a firmware.
This is why Samsung will remain a second-rate manufacturer of mobile devices: ineffective software QA and silly update rollout schedules.
Samsung is known for slow firmware updates, mostly due to the most customization of android in the world. Second-rate manufacturer? Not sure about that my friend. You are smart enough to Google Samsung.
This post is an argument waiting to happen.
My tuppence, IF users don't have the capacity to download 1 program (Odin) and 1 file (the updated rom) then follow a simple set of instructions, put tab in download mode by pressing 2 buttons, connecting a charger cable to the device and the computer/lapto, run Odin, run the update, then they should be buying that fruit based logo device. You know, the one designed for numpties :silly:
Riki1kenobi said:
This post is an argument waiting to happen.
My tuppence, IF users don't have the capacity to download 1 program (Odin) and 1 file (the updated rom) then follow a simple set of instructions, put tab in download mode by pressing 2 buttons, connecting a charger cable to the device and the computer/lapto, run Odin, run the update, then they should be buying that fruit based logo device. You know, the one designed for numpties :silly:
Click to expand...
Click to collapse
Likewise i fail to see why XDA Developers has so many users wanting Samsung update path posting .
First job i do is remove Kies and OTA .
jje
Riki1kenobi said:
This post is an argument waiting to happen.
My tuppence, IF users don't have the capacity to download 1 program (Odin) and 1 file (the updated rom) then follow a simple set of instructions, put tab in download mode by pressing 2 buttons, connecting a charger cable to the device and the computer/lapto, run Odin, run the update, then they should be buying that fruit based logo device. You know, the one designed for numpties :silly:
Click to expand...
Click to collapse
Haha... so true... hehe... I like your humor...
The note isn't my first Android tablet, but it is the best that I've owned to date. My first Android tablet was an Archos 101. In addition to poor quality control that led to dead USB ports and speakers on multiple units while under warranty, the company's constant push of half-backed updates drove me and others away from that brand. You need to test code changes to make sure one "fix" doesn't break something else. Archos engineers didn't test updates thoroughly and rushed out updates that created additional issues. I quit updating that tablet. Thank goodness Samsung is more diligent. No OS is perfect and some of the things we might be unhappy with really are deliberate design features that Google incorporated into JB (or, in your case ICS). I would also suggest that you update to JB, you'll gain valuable features with the s-pen. At this point in time, I am happy with stock JB. I will probably root it soon (I wanted to use it on stock JB for a while before rooting). Eventually, I may flash one of the custom ROMs developed by the talented developers on this forum. The great thing about the popularity of Samsung products is that the popularity generates more developer interest, a big win for adventurous owners willing to root and flash.
Riki1kenobi said:
This post is an argument waiting to happen.
My tuppence, IF users don't have the capacity to download 1 program (Odin) and 1 file (the updated rom) then follow a simple set of instructions, put tab in download mode by pressing 2 buttons, connecting a charger cable to the device and the computer/lapto, run Odin, run the update, then they should be buying that fruit based logo device. You know, the one designed for numpties :silly:
Click to expand...
Click to collapse
Having to do all that is, to me, what is required from buying a second or third-rate product. I wouldn't buy a car, for example, and be happy to expect that I need to change the spark plugs or some nonsense when I bring it home.
I mess around with R/C cars and I have in the past bought crappy cars because I enjoy tinkering and making them better, but I don't want or expect to do that with a mass market product lol.
skadebo said:
Having to do all that is, to me, what is required from buying a second or third-rate product. I wouldn't buy a car, for example, and be happy to expect that I need to change the spark plugs or some nonsense when I bring it home.
I mess around with R/C cars and I have in the past bought crappy cars because I enjoy tinkering and making them better, but I don't want or expect to do that with a mass market product lol.
Click to expand...
Click to collapse
Nice analogy er, maybe not...... Thing is, no one is forcing you to update/upgrade/tinker. An update message pops up from time to time on the device and you click ok and it installs. That is as simple as it gets. That's NOT what we are talking about here though. We are talking about folks getting their flossy in a twizzie because a newer version of the OS is available and it hasn't been pushed to their device yet.
I have never seen anything written anywhere on the terms and conditions of any device I have bought that states I am entitled to get any upgrade to OR should expect to be updated to the latest software. In fact, iirc it says that on occasion an update may, yes MAY become available for the device and to either follow the onscreen instructions or visit (insert website here) for instructions on how to update.
Now to get back to the point, peeps EXPECT TO GET THE LATEST UPDATE, but they don't want to follow the instructions to do it. These instructions are usually made as simple as 1-2-3 so that even the technologically challenged can follow them. Turns out they ain't simple enough for some though and then the moaning and bleating begins, followed by the blaming. My device is stuffed, Samsung is rubbish, this cheese toastie is mouldy etc, but you never hear anyone saying, aargh fecked it up but it was my fault, I was born with two left brains or life is like a box of chocolates lieutenant Dan!
Sorry for such a long post. But I hope it helps clear things a tad
Riki1kenobi said:
Nice analogy er, maybe not...... Thing is, no one is forcing you to update/upgrade/tinker. An update message pops up from time to time on the device and you click ok and it installs. That is as simple as it gets. That's NOT what we are talking about here though. We are talking about folks getting their flossy in a twizzie because a newer version of the OS is available and it hasn't been pushed to their device yet.
I have never seen anything written anywhere on the terms and conditions of any device I have bought that states I am entitled to get any upgrade to OR should expect to be updated to the latest software. In fact, iirc it says that on occasion an update may, yes MAY become available for the device and to either follow the onscreen instructions or visit (insert website here) for instructions on how to update.
Now to get back to the point, peeps EXPECT TO GET THE LATEST UPDATE, but they don't want to follow the instructions to do it. These instructions are usually made as simple as 1-2-3 so that even the technologically challenged can follow them. Turns out they ain't simple enough for some though and then the moaning and bleating begins, followed by the blaming. My device is stuffed, Samsung is rubbish, this cheese toastie is mouldy etc, but you never hear anyone saying, aargh fecked it up but it was my fault, I was born with two left brains or life is like a box of chocolates lieutenant Dan!
Sorry for such a long post. But I hope it helps clear things a tad
Click to expand...
Click to collapse
Riki1kenobi said:
This post is an argument waiting to happen.
My tuppence, IF users don't have the capacity to download 1 program (Odin) and 1 file (the updated rom) then follow a simple set of instructions, put tab in download mode by pressing 2 buttons, connecting a charger cable to the device and the computer/lapto, run Odin, run the update, then they should be buying that fruit based logo device. You know, the one designed for numpties :silly:
Click to expand...
Click to collapse
Your advices are sick my friend. For me, I did flash many firmwares of other regions onto my devices. But in the same time, good may be overwhelmed by bad things. These 1-2-3 steps were sometimes helpful and other times disasterous! For example, I have flashed many firmwares before on my Galaxy S i9003, Galaxy S II i9100, and my latest Galaxy S III.
For unknown reason, my Galaxy S III got bricked and went into a boot loop. It was not a noticed hardware failure neither it was a corrupt Odin package, but for some reason, a hidden hardware failure has become obvious following the flash. Samsung has reported that the motherboard was completely damaged and that unofficial firmware flashing of different CSCs was the cause. It could be also a manufacturing error. Whatever it is, I was lucky that Samsung did not void my warranty as it was rooted at that time with the flash counter > 0.
Besides, I have more than five Samsung Galaxy devices in the house, and they look to me as their software geek!! Whenever an update is released, I cannot say always to them yes, and let me flash things to you!!!!
Besides, why am I supposed to flash the German one? For the learning hub that does not work in my country? Or for Music and Video hubs that are also forbidden in my Country?! And why does Samsung have all these software variability? Why does not they make a united software with custom configurations based on country; like Apple?! Apple used to release the update worldwide with blocking un-allowed features based on country chosen!
I love to update using OTA; AS SIMPLE AS THAT, apart from all the BLA BLA BLA you have said!!!
no one is forcing you to upgrade, after all it's your tablet and you can do whatever you want, i am still on ICS and plan to stay that way for a while because i feel personally it's stable for me and works, i don't really care about new features i will hardly use, best thing is to root and then you can decide if you want to upgrade your tablet at a later date or not, the option is still there with odin.
i too also prefer uk firmware because some features that are on the uk firmware won't specifically be on the german firmware, different regions different features.
tweetatoo said:
Besides, why am I supposed to flash the German one? For the learning hub that does not work in my country? Or for Music and Video hubs that are also forbidden in my Country?! And why does Samsung have all these software variability? Why does not they make a united software with custom configurations based on country; like Apple?! Apple used to release the update worldwide with blocking un-allowed features based on country chosen!
Click to expand...
Click to collapse
HUYI said:
i too also prefer uk firmware because some features that are on the uk firmware won't specifically be on the german firmware, different regions different features.
Click to expand...
Click to collapse
Hehehe The biggest joke of all is that the UK version is INCLUDED into the German version. You just need to change csc and you have the UK firmware, not a firmware LIKE the uk firmware but THE UK firmware.
Some people just prefer to complain instead of moving a finger themselves.
Just flashed premium bugs 4.1.2... not bad so far! Well woth the upgrade from ics unless you use the gallery, as that isn't fixed!
tweetatoo said:
I love to update using OTA; AS SIMPLE AS THAT, apart from all the BLA BLA BLA you have said!!!
Click to expand...
Click to collapse
Then stop being a complainawhinger then and just wait for Samsung to deliver your update to you OTA. While you're waiting for it I'll continue to try and help people wanting to update to the latest version, with my sick, but helpful advice, :good:
Riki1kenobi said:
Then stop being a complainawhinger then and just wait for Samsung to deliver your update to you OTA. While you're waiting for it I'll continue to try and help people wanting to update to the latest version, with my sick, but helpful advice, :good:
Click to expand...
Click to collapse
haha we need more people like you Riki1kenobi... some fun but helpful post... :laugh:
people should not get easily offended over some jokes the man was just trying to help... and as JJEgan said i also can't understand why so many xda members here are waiting for ota updates... i understand that xda is the place to look for all things android but really the 1st step you should do is not rely on kies and learn some odin and flashing..
but hell we're all in one community... there are always some whiners and whatever kind of people and that just adds to the fun of being here on xda..
Riki1kenobi said:
Nice analogy er, maybe not...... Thing is, no one is forcing you to update/upgrade/tinker. An update message pops up from time to time on the device and you click ok and it installs. That is as simple as it gets. That's NOT what we are talking about here though. We are talking about folks getting their flossy in a twizzie because a newer version of the OS is available and it hasn't been pushed to their device yet.
I have never seen anything written anywhere on the terms and conditions of any device I have bought that states I am entitled to get any upgrade to OR should expect to be updated to the latest software. In fact, iirc it says that on occasion an update may, yes MAY become available for the device and to either follow the onscreen instructions or visit (insert website here) for instructions on how to update.
Now to get back to the point, peeps EXPECT TO GET THE LATEST UPDATE, but they don't want to follow the instructions to do it. These instructions are usually made as simple as 1-2-3 so that even the technologically challenged can follow them. Turns out they ain't simple enough for some though and then the moaning and bleating begins, followed by the blaming. My device is stuffed, Samsung is rubbish, this cheese toastie is mouldy etc, but you never hear anyone saying, aargh fecked it up but it was my fault, I was born with two left brains or life is like a box of chocolates lieutenant Dan!
Sorry for such a long post. But I hope it helps clear things a tad
Click to expand...
Click to collapse
I absolutely, totally agree with you. People see something new and they just WANT to update, because we are consumer whores.
However, I needed to update to fix the notorious PDF import problem in S-Note (as noted in first post in this thread). Basically, if I wanted to import PDFs from school into S-Note, S-Note would crash. This only happens to specific versions of the N8010 firmware (Canada being one of them).
I don't come looking for fights etc. as a lot of people do, I just speak (sometimes shout!) the truth.
Different regions /countries have different legal requirements which I suspect is one of the big delays for some regions. If you want everything done for you (OTA) , be patient and stup reading forums lokking for the latest updateor you will never be happy.
Of course you could also encourage your government to remove some of the restrictions, but for that I think you will be waiting much longer! I for one am amazed the updates get out as quickly as they do, re-evaluating every rom in every country for legal issues has to be a very expensive nightmare. Samsung is a big international company, ignoring regional laws is not really an option.
Sent from my GT-N8010 using xda premium
I have lost my hope that New Zealand will be able to get JB Update. So now after reading many threads for months I am plunging into this forum to know how I can update my machine.
My tablet
Model Number
GT-N8000
Baseband version
N8000XXALI3
Android version
4.0.4
1. Please suggest me which firmware is going to be suitable for my tablet
2. If tomorrow NZ firmware is released and I be able to flash it manually will it be back to normal for OTA upgrades ?
Thanks
l. Put German Jellybean
2. Yes
Sent from my GT-N8000 using XDA Premium HD app
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).