Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
kortik9 said:
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
Click to expand...
Click to collapse
Don't know if there will be an official build, but unofficial build by crpalmer works great.
Rutr said:
Don't know if there will be an official build, but unofficial build by crpalmer works great.
Click to expand...
Click to collapse
Yup, I saw that, just wondering if we will get official anytime soon.
kortik9 said:
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
Click to expand...
Click to collapse
I've never quite figured out why people get so hung up on "official"... When there is an official build of CM, it will still be me maintaining it and the only differences will be that:
* you'll get nightly and M builds which makes them more frequent
* you'll get slower device specific updates to the core software (right now I change it and build it, when it's official it can take weeks to get a change in the frameworks approved and you won't see it until it's approved).
that said, it will be official but doing so takes effort from me and from other people that are very busy and so all I can say is it isn't official yet.
crpalmer said:
I've never quite figured out why people get so hung up on "official"... When there is an official build of CM, it will still be me maintaining it and the only differences will be that:
* you'll get nightly and M builds which makes them more frequent
* you'll get slower device specific updates to the core software (right now I change it and build it, when it's official it can take weeks to get a change in the frameworks approved and you won't see it until it's approved).
that said, it will be official but doing so takes effort from me and from other people that are very busy and so all I can say is it isn't official yet.
Click to expand...
Click to collapse
Actually before creating this thread I saw your "unofficial" build thread and checked your profile to see if you are somehow connected to CM dev team, but you have no information in your profile. I don't like unofficial builds because often they have something tuned\installed\uninstalled, but I like how CM works and I don't want anything else, this is why I want official build. But in this case I think I should try your build, as you maintain official ones anyway.
Thanks for clarifying this!
kortik9 said:
Actually before creating this thread I saw your "unofficial" build thread and checked your profile to see if you are somehow connected to CM dev team, but you have no information in your profile. I don't like unofficial builds because often they have something tuned\installed\uninstalled, but I like how CM works and I don't want anything else, this is why I want official build. But in this case I think I should try your build, as you maintain official ones anyway.
Thanks for clarifying this!
Click to expand...
Click to collapse
Not necessarily having visibility into any framework changes I've made is a pretty reasonable concern. There's only one change that I have already submitted for review so nothing too magical going on behind the scenes. Everything else is available in my public git repos for anyone to verify.
Most of the time official builds start out as unofficial builds. At least that's what I've noticed.
Related
to be honest with you guys.
i have no idea what the heck is the difference betwenn the two.
especially all the builds.
are there something different with each build?
can someone out there explain to me?
sorry,i've tried searching it up but nothing.
if there isn't something different about each build for the cyanonogenmod nightly
then why do they have soo many builds?
i mean why keep the only builds there.
you know everyone wants the recent update.
to fix the bugs or what not.
but if i can get some really good explanation on this,it would be really night.
thank you.
the nightlys are beta versions, so they can be buggy.
6.0 is a stable version which is solid and has no bugs
-
btw this topic should be in general or something, some people around here get upset easily for posting in the dev section.
stoney05 said:
the nightlys are beta versions, so they can be buggy.
6.0 is a stable version which is solid and has no bugs
-
btw this topic should be in general or something, some people around here get upset easily for posting in the dev section.
Click to expand...
Click to collapse
You could read the changelog. It has the added features since 6.0 listed (called 6.1). 6.1 isn't released yet, but when it is the nightlies will be changed into 6.1.
Nightly just means they rebuild the rom every night and allow people to download it to install.
Caspers25 said:
to be honest with you guys.
i have no idea what the heck is the difference betwenn the two.
especially all the builds.
are there something different with each build?
can someone out there explain to me?
sorry,i've tried searching it up but nothing.
if there isn't something different about each build for the cyanonogenmod nightly
then why do they have soo many builds?
i mean why keep the only builds there.
you know everyone wants the recent update.
to fix the bugs or what not.
but if i can get some really good explanation on this,it would be really night.
thank you.
Click to expand...
Click to collapse
this should be in the q&a
Quick summary:
Final builds: Relatively stable, tested, and at the point that Team Douche is comfortable with how it handles.
Nightly builds: Compiled every night at 00:00 GMT directly from the github source. Has all the latest features (like the nightlies currently have a newer kernel and some nice camera features) but can be quite unstable and typically aren't recommended for day-to-day use.
I would Edit your Title for this thread..
please Remove [ROM] as it signifies this is a ROM thread and this is, of course, not..
The CyanogenMod development process produces nightly builds automagically for bleeding-edge users. Here's sort of how the process works generally:
1. Bugs/feature requests/etc are submitted to Google Code:
http://code.google.com/p/cyanogenmod/issues/
2. Items are then transported to Gerrit for code review once a solution is written / being worked on:
http://http://review.cyanogenmod.com
3. Once tested/approved, commits happen to GitHub, which is announced via cmsrc on Twitter:
http://github.com/CyanogenMod/
http://twitter.com/cmsrc
4. Nightly builds happen automatically via BuiltBot with all commits from GitHub (even if they break stuff, so these nightlys aren't for the uber-novice). You can watch nightly builds happen, which are typically around 9pm EST unless kicked off manually:
http://buildbot.teamdouche.net/waterfall
5. Downloads available nightly here (by build number):
http://mirror.teamdouche.net/
And that's pretty much it. You can keep a close eye on Cyanogen's personal Twitter (twitter.com/cyanogen) and even converse with him and some of TeamDouche as well on IRC via FreeNode, in #cyanogenmod. They're great guys and very open to the future of CM. I've known Cyanogen for years and he's a great, fun guy with a brilliant mind and a passion for open source.
Anyway, I hope this clears up the CM nightly process for those who don't really grasp it yet. There may be a few diversions from the process, but generally that's how it works, and is a great way to keep very close track of what's happening when. Understanding is the key to NOT asking 'when will this be done?' or 'where's the changelog!?', etc.
Moved to Q&A as not development.
do the current nightlies, or the future 6.1 release, require the engineering bootloader 0.76?
i did unrevoked3 and ended up with 0.79 of course. i've been playing with many roms but not yet CM6 due to this restriction ... the ENG bootloader thread reads like a cautionary tale, there doesn't seem to be any understanding of why some phones play well with the update and others don't.
i'm sure there's a very good reason, but i don't understand the need for 0.76 for only CM6.
coastal said:
do the current nightlies, or the future 6.1 release, require the engineering bootloader 0.76?
i did unrevoked3 and ended up with 0.79 of course. i've been playing with many roms but not yet CM6 due to this restriction ... the ENG bootloader thread reads like a cautionary tale, there doesn't seem to be any understanding of why some phones play well with the update and others don't.
i'm sure there's a very good reason, but i don't understand the need for 0.76 for only CM6.
Click to expand...
Click to collapse
As far as the CM code, *any* bootloader version is permitted as of a commit last week. This shouldn't be an issue anymore on nightlies, but likely will be in CM6.0.0.
We get FM radio tonight
http://github.com/CyanogenMod/cm-kernel/commit/6dcd7908655309f231d090d7714a312f2b8a5483
Kernel Source for Google Nexus S Released
December 15, 2010 By: ElCondor
Android development for the Google Nexus S has now begun. The kernel source – originally made available upon the official phone release – has already been released by Brian Swetland, an Android kernel developer. This source code can be further investigated and explored by developers. Ultimately, this will lead to achieving development milestones much earlier than usual. One example is to root the phone just a few hours or days after it gets released.
Originally posted by supercurio
History for the Nexus S sources begins now.
Original source is here :
http://twitter.com/#!/dnaltews/status/14849739858116608
By Brian Swetland, Android kernel developer.
Thank you Brian !
XDA member supercurio created a thread in the Nexus S forums. Make sure to check it out to follow the discussion, or continue directly to the developer kernel site.
yeah.. it's out:
http://www.engadget.com/2010/12/17/android-2-3-gingerbreads-source-code-now-available/
i wonder why it takes to long to get a first build
Probably its just a matter of mili seconds before one pops up Cant wait >.<
d3sm0nd said:
yeah.. it's out:
http://www.engadget.com/2010/12/17/android-2-3-gingerbreads-source-code-now-available/
i wonder why it takes to long to get a first build
Click to expand...
Click to collapse
Long like more than half a day? Lol.
Don't you need the source for the rest of the OS as well to build a full system?
The source is available now.
tomhierl said:
The source is available now.
Click to expand...
Click to collapse
Here you can see whats going on with the CyanogenMod devs.
The question will soon become 'do I root and flash a custom Gingerbread rom... or wait to see if HTC release one...'
Lothaen said:
The question will soon become 'do I root and flash a custom Gingerbread rom... or wait to see if HTC release one...'
Click to expand...
Click to collapse
root anyway the custom roms are far superior
Theres a test build of Gingerbread in the oxygen thread
I'm unable to find it. Could you post a link?
Stretlow said:
root anyway the custom roms are far superior
Click to expand...
Click to collapse
Tempted, even if I just had a rooted stock and remove some of the junk that is in the rom's...
If you're happy with the stock ROM, don't bother. You'll end up flashing ROMs all the time, always trying the newest or different ones - which is fun for sure, but not really necessary and often quite frustrating.
Can't wait to boot 2.3 on my Desire!
schiznik said:
Theres a test build of Gingerbread in the oxygen thread
Click to expand...
Click to collapse
It's just a themed version I think.
hi guys, we've got 5.1.1 officially but cm13, based on android 6.0, is even sweeter (doze, app permission control, etc) . did you hear any news from devs?
It looks like that Temasek and Joshndroid are already preparing an unofficial CM 13 Build for our SM-P600 Tablet.
Look at https: //github.com/temasek/android_packages_apps_Settings/commits/cm-13.0
&
https: //github.com/Joshndroid/device_samsung_lt03wifi/tree/cm-13.0-test-rebasecm12
I can tell you that the p600 will get official CM13 if @joshndroid, @ Shawn, and myself can figure out why we get a black screen after rebooting from recovery.
Sent from my SM-P600 using Tapatalk
we are trying as hard as we can. hopefully we all can come up with the goods, I have put a lot of time into it already pushing to cm's gerrit to fix broken things, but unfortunately i cant do it on my own. Shawn and orion116 are definitely assisting in getting this done, hopefully raymanfx comes to the party as well lol
joshndroid said:
we are trying as hard as we can. hopefully we all can come up with the goods, I have put a lot of time into it already pushing to cm's gerrit to fix broken things, but unfortunately i cant do it on my own. Shawn and orion116 are definitely assisting in getting this done, hopefully raymanfx comes to the party as well lol
Click to expand...
Click to collapse
How is the status? Any progress?
Stogie87 said:
How is the status? Any progress?
Click to expand...
Click to collapse
i am getting succesful builds but am getting black screen (back light turns on but nothing shows). unsure whether its kernel or vendor related or even tree related with something not activated? looking at some other device trees to see what they have changed
ok, this tricky problem still reamains. I have seen, that temasek released his second alpha build of cm 13. You don't want to use his source again for further releases?
Stogie87 said:
ok, this tricky problem still reamains. I have seen, that temasek released his second alpha build of cm 13. You don't want to use his source again for further releases?
Click to expand...
Click to collapse
best to work on the base cm rom first before working on derivatives. I will be releasing a temasek rom for cm-13.0. But we need cm-13.0 working first. More hands on a single distro makes hopefully better/lighter work. Once we get a cm happening, all the derivatives will come next so everyone wins.
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Doofitator said:
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Click to expand...
Click to collapse
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
It goes back to 6.0.1 but no further.
It will do both, apparently.....
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Sent from my HTC One M8 using Tapatalk
MJPollard said:
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Click to expand...
Click to collapse
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
LilAnt530 said:
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
Click to expand...
Click to collapse
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
MJPollard said:
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
Click to expand...
Click to collapse
That's pretty epic dude! I have an LG Lucid vs840 from that had a CM9 out fot it was considering doing the same thing. As for helping them with their efforts I have no idea where to start.
But I do have a question, do you think it'd be very hard to update the cm7 cm9 or cm11 to Marshmallow devices? This might sound foolish but im still curious lol
The CM repo is moved wholesale to LineageOS, so if you know how to build, you could still build any version you like from the new source, provided that the older version was there previously in CM. I've built Lineage 13 (CM13) for several of my devices just now since I still need Xposed.
You can't expect any useful updates for <CM12.1 though, as CM had stopped working on them long ago. Not worth the extra effort of maintaining them, plus unfixable security holes.
Not looking to maintain them, simply to update them to compile from the LinOS repo. Specifically, the default.xml in the android package needs the references to CyanogenMod changed to LineageOS, and other references need to be changed as well. Once that's done, nothing further needs to be done.
Sent from my HTC One M8 using Tapatalk
Hi im looking for lineageOS 13.0-20170513-nightly-x2 this must be the last official version of that rom right?
i got it at my device but delete the zip and i dont found any working download link...
did someone got it for me please?
thx chris
jhedfors said:
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
Click to expand...
Click to collapse
You say that, but there was CM for my old 2011 LG phone but I would be tremendously surprised if a LOS ROM ever shows up because there doesn't seem to be any active development for that device anymore. Makes me sad because I would love to have LOS on it (and security updates newer than 2012) but I wouldn't bank on it... the newest CM ROM I can find for it is from 2015.
The following probably sounds like a dumb question, but I'm genuinely confused. Would I be able to flash the SGH-1337 version of Lineage OS onto my SGH-1337M model of the Samsung S4? Or are they completely different models? Any answers will be greatly appreciated.
TipTopHiatus said:
The following probably sounds like a dumb question, but I'm genuinely confused. Would I be able to flash the SGH-1337 version of Lineage OS onto my SGH-1337M model of the Samsung S4? Or are they completely different models? Any answers will be greatly appreciated.
Click to expand...
Click to collapse
Maybe you will find an answer there: https://forum.xda-developers.com/ga...anadian-s4-i337m-jfltecan-rom-t3101107/page39
kurtn said:
Maybe you will find an answer there: https://forum.xda-developers.com/ga...anadian-s4-i337m-jfltecan-rom-t3101107/page39
Click to expand...
Click to collapse
Thanks. I'll check those out. Now that I view Lineage OS, they only have nightly builds available for the S4, which is not what I am looking for.
TipTopHiatus said:
Thanks. I'll check those out. Now that I view Lineage OS, they only have nightly builds available for the S4, which is not what I am looking for.
Click to expand...
Click to collapse
Nightly lineageOS build is the most stable thing you will find, besides stock ROM. Most other custom ROMs are based on lineageOS.
kurtn said:
Nightly lineageOS build is the most stable thing you will find, besides stock ROM. Most other custom ROMs are based on lineageOS.
Click to expand...
Click to collapse
But aren't nightly builds being updated nightly because they're still buggy and in the development phase? Also, I couldn't find anything better, so I've settled with GoldenEye 5.0.1. It works super well, and it runs smoothly. It also doesn't make the upper screen feel like the bottom of a clothing iron lol.
TipTopHiatus said:
But aren't nightly builds being updated nightly because they're still buggy and in the development phase?..........
Click to expand...
Click to collapse
Just an FYI...
What you had asked is the reminisce from the former CyanogenMod build structure.
CyanogenMod used to use the label "Nightly" for builds that may/might be unstable. Like a prerelease of its "Stable" builds.
Not long after the Official Launch of LineageOS, they had streamlined and such that had added "Stability" to the builds and changed the term "Nightly" to mean Stable Builds that are automated to be released with the fixes and such that were approved and pushed via Gitlab.
So LineageOS doesn't use the term "Stable" any longer since the "Nightly" builds are considered Stable Builds that are released on a Daily Basis (for the most part).
This is not to, personally, mean that Nightly Builds are without its bugs and such that they strive to improve on.
I've used Nightly Builds and had various degrees of issues I've reported but, most of the time, the Nightly Builds has been pretty stable for me.
Sorry for the lengthy explanation but, I do hope that I had explained this okay via text...
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Ibuprophen said:
Just an FYI...
What you had asked is the reminisce from the former CyanogenMod build structure.
CyanogenMod used to use the label "Nightly" for builds that may/might be unstable. Like a prerelease of its "Stable" builds.
Not long after the Official Launch of LineageOS, they had streamlined and such that had added "Stability" to the builds and changed the term "Nightly" to mean Stable Builds that are automated to be released with the fixes and such that were approved and pushed via Gitlab.
So LineageOS doesn't use the term "Stable" any longer since the "Nightly" builds are considered Stable Builds that are released on a Daily Basis (for the most part).
This is not to, personally, mean that Nightly Builds are without its bugs and such that they strive to improve on.
I've used Nightly Builds and had various degrees of issues I've reported but, most of the time, the Nightly Builds has been pretty stable for me.
Sorry for the lengthy explanation but, I do hope that I had explained this okay via text...
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Click to expand...
Click to collapse
Thanks for the information. Have a good one!