So CM10.1 recently got an update to the m1 snapshot and I was wondering what's a milestone snapshot? Never knew what it is and how is it different from stable?
danshuynh said:
So CM10.1 recently got an update to the m1 snapshot and I was wondering what's a milestone snapshot? Never knew what it is and how is it different from stable?
Click to expand...
Click to collapse
Cyanogenmod said:
Something we have learned over the past few months is that if you don’t release, someone else will do it for you. Since we are open-source, we absolutely encourage it! Unfortunately, the quality of unofficial builds can vary, and we are serious about quality. Of course nightlies are always available, but we realized that having something that is a bit more stable on a more frequent basis is important. Starting now, we are rolling out our M-Series releases. M-Series builds will be done at the beginning of every month. We did a soft freeze of the codebase for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward.
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.
Click to expand...
Click to collapse
http://www.cyanogenmod.org/blog/cyanogenmod-10-m1
Hi, thanks to the great TeamApexQ I am running last week's modified CM and loving it. I have a very simple question which might be useful to others: everything I need is installed, and the phone works like a charm. I am in "steady state" - how often would you recommend upgrading to the latest nightly? This is the device I use every day for work and life, not an experimental setup. Are there any announcements posted about big breakthroughs in nightlies? I guess reaching stable versions would make it easier to follow.
thanks
g.
If it's stable, stay with what you have. If you're having troubles, if you hear of a particular bug of interest being fixed, or some feature you're excited for testing becomes available, upgrade.
Magamo said:
If it's stable, stay with what you have. If you're having troubles, if you hear of a particular bug of interest being fixed, or some feature you're excited for testing becomes available, upgrade.
Click to expand...
Click to collapse
Thanks. Will do - for reference, can you tell us specifically where to look for a) CM relay 4g-specific changelog/bugfixes/news, and b) TeamApexQ nightlies changelog/bugfixes/news?
Thanks again
The changelogs provided with CM Updater has apexq specific bits, as do the changelogs released alongside the TeamApexQ staging builds. All standard places really.
Hi all,
I first installed cm-10.1.3-xt897 since it is the latest stable release on CyanogenMod official xt897 downloads page. My main reasons for using CM are stockness and customization, and stability is a must so I generally stick to the stable releases.
However, cm-10.1.3-xt897 seems to suffer from frequent freezes lasting 5-10 seconds in landscape mode (unless HW overlays were disabled). So I decided to try cm-10.2-20131102-SNAPSHOT-M1 instead, and it seems to have resolved that specific issue, and I haven't encountered any other serious issues affecting my usage patterns with it.
Now, I had expected that my next upgrade would be to cm-10.2 stable, but I've noticed that no RCs or stables have been released for xt897, and the nightlies have jumped to CM11. Is a cm-10.2 stable release still a possibility?
If not, what is the reasoning for that? For me cm-10.2(M1) seems to work much better than the current stable release (CM 10.1.3), so it doesn't seem to make sense to not release a stable CM 10.2. Unless of course there are notable regressions from CM 10.1.3 that I'm just not seeing in my use? (I haven't seen anything in the CM10.2 dev thread, though, but I admit I may have missed it.) Thankfully it is not a huge loss for me, though, as M1 works fine, so I can just continue using it for now.
And if cm-10.2 xt897 stable is still planned, I apologise for my hastiness. (I would have expected nightlies to remain on 10.2 until such a release.)
In any case thanks to all the devs working on this, good to have a qwerty android phone running a decent firmware
As far as I have seen, CM has stated they are done developing 10.2 as of 12/5. I don't remember exactly what the difference is between a monthly snapshot and stable, but for my experience with CM since version 7, they don't mean a lot. I've seen issues with "stable" releases and and rock solid nightlies. I'm currently running the skrilax 11/29 nightly and its great. There are apparently still some issues with CM11 so i'm holding off on that for a while.
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
In an interview of Kondik, he said that now that they're a company and this is their product, they have actual paid devs working on the updates, which should make their code more higher quality and updates faster (though now that they have to make it stable means that it will slow updates down, I hope there will be a nightly channel)
mannu_in said:
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
Click to expand...
Click to collapse
Don't bet on that. Look at how poorly the community CM builds (i'm talking official nightlies, those are "community" builds from the point of view of Cyngn) for the Oppo N1 are. It's Cyngn's official position that they don't care at all if the community builds are completely broken and that users should have no expectations whatsoever from them.
Use nightline updates and you'll be happy :laugh: it helps a lot to devs make CM better and better
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
MrAndroid-HD said:
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
Click to expand...
Click to collapse
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
floepie said:
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
Click to expand...
Click to collapse
Remmember this is a special verison of CM, there is nothing like it used to that you can rely on. I know how things where in the past, but this is really one of their first projects where they are the main system on the phone from start - I know they where on the Oppo N1 also from the beginnign, but as far as I know, there weren't made a set deal like with the OnePlus..
Here OnePlus have a 2 year contract on a special version of CM.. Only time will tell us how much it differs from their normal releases..
As said before, the Cyanogen transition from a hobby to a company might give a huge benefit here.
It's true that the waiting time between stable releases has historically been quite poor, but I have extremely good experiences with CM nightlies. I'm running nightlies on my Galaxy Nexus and Nexus 7, and I can't really complain about anything. Hopefully we'll have an easy opt-in to the nightlies (like there is currently) and that the first nightlies get pushed out fast as Android is updated.
Also, we'll always have community builds.
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
LiquidSolstice said:
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
Click to expand...
Click to collapse
That's done via touchscreen controller firmware - which isn't itself opensource (it's just a blob encoded into a header file within the kernel), but will work no matter what you're running on the device with a only a few tweaks to the frameworks/kernel. Plenty of projects have experience with these tweaks since the Oppo N1 had the same capability.
floepie said:
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Click to expand...
Click to collapse
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
maxver0 said:
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
Click to expand...
Click to collapse
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Entropy512 said:
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Click to expand...
Click to collapse
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
maxver0 said:
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
Click to expand...
Click to collapse
That's bull****. The only thing they can blame Oppo on is the initial O-Click fiasco - nothing beyond that. (And I'm letting them slide for the O-Click mess, that really wasn't their fault)
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
dracinn said:
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
Click to expand...
Click to collapse
We're not talking about nightlies here, since there's no guarantee for users that they'll be anything but crap. Cyngn is ADAMANT about this position. If community builds (nightlies) for a Cyngn device are broken, you're SOL.
Entropy512 said:
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
Click to expand...
Click to collapse
Well that someone prefer more one rom than the other doesn't prove anything. I prefer custom rom Slimkat on my Nexus 4 even if stock is super stable or even a cyanogenmod rom on my phone. I tried OmniRom on my N4 tho but I couldn't find multiwindow at all in rom so I flashed over something else...
I'm a little confused by the range of options available for the Photon Q. Of course, CM12 is still in development, but does CM11 have a stable build at this point? What are people's experiences with it, and do they recommend updating from stock?
I'm mainly thinking about it because I'm starting - very slowly - to stumble across app compatibility issues, and I want to hold off updating my phone for at least another year. Kind of holding hope that Blackberry will finally release an Android phone.
kennyminot said:
I'm a little confused by the range of options available for the Photon Q. Of course, CM12 is still in development, but does CM11 have a stable build at this point? What are people's experiences with it, and do they recommend updating from stock?
I'm mainly thinking about it because I'm starting - very slowly - to stumble across app compatibility issues, and I want to hold off updating my phone for at least another year. Kind of holding hope that Blackberry will finally release an Android phone.
Click to expand...
Click to collapse
CM11 has EOL'd. Final official release 6-26 (obviously the jbbl version for the QHD). Newer builds with stagefright patches have been released (see MCP1's builds over in RHD).
CM12 has also EoL'd.
CM12.1 is still in development.
CM13 (Android M/6.0/Marshmallow) has not started yet.
Sent from my ATRIX HD using XDA Free mobile app