whats happening to the builds I see on /cyanogenmod/Jenkins site?
http://jenkins.cyanogenmod.com/job/cm-build-all/276/console September 1
should be able to find it here http://mirror.internode.on.net/pub/cyanogenmod/jenkins/40098/
clearly on build list,, the fascinatemtd 10.1
but it never shows up
http://mirror.internode.on.net/pub/cyanogenmod/jenkins/40097/ cm-10.2-20130901-NIGHTLY-evita.zip,,, right before in the build list
http://mirror.internode.on.net/pub/cyanogenmod/jenkins/40099/ cm-10.1-20130901-NIGHTLY-find5.zip,,, right after in build list
Same thing on these days too, built but never made it anywhere.
http://jenkins.cyanogenmod.com/job/cm-build-all/271/console August 27 Should be file:: http://mirror.internode.on.net/pub/cyanogenmod/jenkins/39575/
http://jenkins.cyanogenmod.com/job/cm-build-all/270/console August 26
http://jenkins.cyanogenmod.com/job/cm-build-all/269/console August 25 Should be file:: http://mirror.internode.on.net/pub/cyanogenmod/jenkins/39314/
http://jenkins.cyanogenmod.com/job/cm-build-all/268/console August 24
Kind of ready for some answers,,,
the Captivate, Nexus S, and Galaxy S all have even received RC editions of CM10.1.3 RC1 and RC2,,, even ""cm-10.1.0 RC's"" prior to that too,,, where is our love?
I just want to see all the bug fixes make it our way,,, 10.1.3 or 10.2 would just be extra nice suprise.
I'm not asking for ETA's more less whats happenig to ones that appear to be out there.
.
I sent JT a private message. Probably not gonna get anywhere, but worth a shot eh?
by the way, jt never really made cm7 nightlies, thus, there arent any builds from march 1 for cm7. just thought i'd point that out
Related
Been using this ROM since day 1, April 11. There are over 1100 replies and 214,115 views, and I have read a lot of them and applied some fixes here and there but none of these have actually come from the Developer himself.
l admit I am not a programmer, just a mild-to-heavy user, but is this it? Have I missed an actual ROM update? I have seen kernals and other ROM's updated in the last month and was just wondering if there is going to be a RC2?
suvroadrage said:
Been using this ROM since day 1, April 11. There are over 1100 replies and 214,115 views, and I have read a lot of them and applied some fixes here and there but none of these have actually come from the Developer himself.
l admit I am not a programmer, just a mild-to-heavy user, but is this it? Have I missed an actual ROM update? I have seen kernals and other ROM's updated in the last month and was just wondering if there is going to be a RC2?
Click to expand...
Click to collapse
No, you haven't missed it, but you missed the vegan-tab specific forum gojimmy created off his main site - where he posts now and then to reassure people that he's still alive and working on stuff.
Given he bases his stuff off CM7, and CM7 has been changing 3-4 times a week, he's probably going to wait until it reaches some point of stability. Or not. Who knows. But I don't think he's stopped.
anyone know that what is difference between Unofficial CM9 Nightly and alpha 0.6 ?
hki_peter said:
anyone know that what is difference between Unofficial CM9 Nightly and alpha 0.6 ?
Click to expand...
Click to collapse
Nightlies are probably going to be less stable.
Basically, when you get a nightly, it's not yet been released. It's what somebody was working on last night...when they quit working on it, whether successful in what they had been working on or not, it was uploaded - hence the name, nightly.
And now you know.
And knowing's half the battle.
sean is here. said:
Nightlies are probably going to be less stable.
Basically, when you get a nightly, it's not yet been released. It's what somebody was working on last night...when they quit working on it, whether successful in what they had been working on or not, it was uploaded - hence the name, nightly.
And now you know.
And knowing's half the battle.
Click to expand...
Click to collapse
Well its slightly more than just something someone happened to be working on and left it!
I'm using the KANG of 20120216 and finding it is far better than my experience with .06!
And I'm about to flash 20120217.
pa49 said:
Well its slightly more than just something someone happened to be working on and left it!
I'm using the KANG of 20120216 and finding it is far better than my experience with .06!
And I'm about to flash 20120217.
Click to expand...
Click to collapse
EDIT: I re-read this reply after posting my response, and the first sentence is just incorrect. A 'nightly' is nothing "more than just something someone happened to be working on and left it".
The rest is subjective opinion, but the definition of what a nightly is can be found clearly explained below.
I think you've misunderstood me, or something else somewhere along the line.
I'm not saying that they're better or worse than official releases.
I was merely pointing out that the way they come about, is that they aren't fully evaluated and tested for stability in order to be released publicly as a finished product.
Before a major release, devs will typically spent time testing their software themselves, in addition to sending it out to 'focus groups' (they aren't REALLY focus groups but serve the same function) where they are further tested...then upon completion of testing, or when a threshold of minimum functionality has been reached (often with a pre-specified maximum number of bugs or critical failures) they can be released publicly.
Nightlies don't go through that extensive testing. That's where the name comes from. The devs 'clock out' and the ROM is built, and posted as a 'nightly'.
From the CM Team:
... Lastly we have the Nightlies, which are as volatile as a firmware can get. These releases keep coming at an interval of a day or two and if you do end up trying one of these, do not be alarmed if the your device goes cuckoo on you. These ROMs are largely untested, and as advised by CyanogenMod, not meant for use for an average user. These releases, are meant to test untested waters with tweaked codes that may or may not break your phone.
Click to expand...
Click to collapse
My understanding was that the nightlies were being built automatically by a script that pulls the most recent source from the cm server. As new code is added daily by devs it is automatically put into nightly builds for testing.
joggerman said:
My understanding was that the nightlies were being built automatically by a script that pulls the most recent source from the cm server. As new code is added daily by devs it is automatically put into nightly builds for testing.
Click to expand...
Click to collapse
As far as I'm aware, you are correct.
Hey guys,
I just want to add, the one of the developers of the official CM9 alpha release is recommending users install the nightly as there may not be an official update pushed put anytime soon.
http://liliputing.com/2012/02/nightly-builds-of-cyanogenmod-9-for-the-hp-touchpad-now-available.html
Anyone know which nightly is pretty stable?
wonshikee said:
Anyone know which nightly is pretty stable?
Click to expand...
Click to collapse
go for alpha 1 as dalingrin said the nightlies won't be based on alpha 1 until a few days later.
Anybody know whats going on with the Nightlies for our Note? They havent had one in two days now.. Everyone seems to be abandoning our phone
Atrix2destroyer said:
Anybody know whats going on with the Nightlies for our Note? They havent had one in two days now.. Everyone seems to be abandoning our phone
Click to expand...
Click to collapse
Nah ....
It's not uncommon for nightlies to break cycles, as CM does system changes, or merges new commits into the tree.
It's not a guarantee that nightlies will hit every day, and besides, we know that Samsung still hasn't dropped source for several tweaks that can hit our device.
It's all good ....g
loads of mr1-staging commits... id standby and not worry about it...
prepping for the jump to 4.2 no doubt...
/github.com/CyanogenMod/hudson/commit/c2784935c587a8b5bb78277bf6ea3f1925a36758
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
t3chn0s1s said:
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
Click to expand...
Click to collapse
We haven't had nightlies for a while now. What you see as nightlies aren't really worthwhile builds, they didn't have any device or kernel fixes for the g2.
A new 11 build is coming probably because half the android userbase relies on kitkat at the moment.
As for the s3, it's not getting CM12 nor 12.1, not the international version at the least. Archi is maintaining an unofficial version, but it still carries the bugs from 10.0/10.1.
Lastly, this is the commit that requires to be merged in order for the builds to even be considered started:
http://review.cyanogenmod.org/#/c/93181/
Without it, nothing CAF related can be merged, and as such, no CM12.1 builds can be had for our device. I believe the reason it's not merged because not all of the variants have a lollipop release, if they ever will get one. Also the whole bootstack/amount of users who don't reed is astonishingly dangerous to handle, so rashed simply preferred to skip building for now.
Finally, it's not that popular of a device. It's a nexus without being a nexus with a locked bootloader, which is a pain in the ass and not too many maintainers have it left (they either went with G3 or skipped LG entirely, as did a whole bunch from the exynos team back in the day).
t3chn0s1s said:
I saw you responded to my post about CM12 nightlies not continuing for the G2. Wanted to ask you (since you didn't mention) what 5.1 (CAF source) ROM you're running? What would you suggest for a stable AOSP ROM that has device/kernel specific updates for our G2s?
Click to expand...
Click to collapse
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Choristav said:
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Click to expand...
Click to collapse
Sorry - was on my phone when I saw your replies and it was just easier for me to respond in the other thread.
Anyways.. thanks for the info. I've done some research and I'm a bit more informed about CAF and what it means to device specific sources, ROMs, etc. Are you just using the stock Euphoria kernel or something else?
On this forum @varund7726 builds his rather excellent ResurrectionRom from the latest CM code release. I suggest you use that. For the D803, @zr239 has beaten all odds including LG not releasing CAF code, to build a fully functional pure CM 12.1 ROM that closely tracks official CM repos.
Lg G2 has it pretty good !
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
t3chn0s1s said:
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
Click to expand...
Click to collapse
I checked, you are right, several of the qualcomm variants have cyanogenmod support. This means that they have active maintainers, but they also don't have to deal with locked bootloader crap, which is why the bump commit is so important for our device.
I only mentioned the international version, which support was dropped because it had a lot of issues thanks to its closed source exynos processor (it requires extra work, and some stuff doesn't end up working anyway).
Not really much to say, the commit is already in CM's gerrit, it's just waiting for review. Maybe it's a CTS-side issue?
Aside from that, being a maintainer doesn't really require much, just effort and presence. It's not an easy task, I'm just saying anyone can apply to be a maintainer and get nighties rolling for a device you might not even have heard of.
@Rashed97 is the man for our G2 when it comes to CM. Dont mind nightlies as long as Rashed is around
Note: he is currently busy with the One M9 but we will hopefully see some cool stuff from him in the future.
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Ploxorz said:
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Click to expand...
Click to collapse
And it appears you're correct as there is another nightly build up with today's date. I apparently posted this thread prematurely.
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
zelendel said:
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
Click to expand...
Click to collapse
You are absolutely right. I had no idea until I posted this thread that CM nightlies did not contain any device specific updates. I honestly NEVER used to like CM at all. I honestly hated it... until owning a OnePlus One. I originally had the G2 right when it came out in 2013 and sold it off long ago & moved on to better devices - but when my OPO got stolen about 2 months back or so - I had to find a relatively cheap, but decent device and the G2 was the best bang for the buck (5.2" display, quick charge 2.0, 3000 mAh battery) and no other phones in 2013 came close to the specs the G2 had at the time.
So, now that I know CM is basically a sh*t ROM for this device I'll be moving on to a ROM that is compiled using CAF sources. Thanks everyone for your input!
Somehow doesn't look too good so far:
https://jira.cyanogenmod.org/browse/CYAN-6556
But why oh why?
The LG G2 still is such a modern and powerful device. It might be almost two years "old", but it's way better than a lot of other current devices.
I am using AICP on my g2. It is based on CM(5.1.1).
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
seanp25 said:
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
Click to expand...
Click to collapse
I would watch the Code Aurora forums where CAF comes from.
zelendel said:
I would watch the Code Aurora forums where CAF comes from.
Click to expand...
Click to collapse
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
adamz667 said:
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
Click to expand...
Click to collapse
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
zelendel said:
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
Click to expand...
Click to collapse
Okay, but @seanp25 probably want to follow source changes for our device, not common CAF source.
Just saw this:
Çetin ÇÖNE wrote on Jul 26 11:18 AM:
Why there is no nighlies it's really stable. Merge it please
Seth Shelnutt wrote on Jul 26 1:26 PM:
There are no nightlies because SELinux is not enabled. Sensors break with it enabled and I don't have time to address it yet.
Click to expand...
Click to collapse
Source:
http://review.cyanogenmod.org/#/c/103673/
Some days after that there came this:
http://review.cyanogenmod.org/#/c/103674/
So maybe there soon will be 12.1 nightlies?
are we expecting an update on the 4 of April?
updates are usually planned for the first Monday of the month right?
Right
I personally am not expecting this phone to get updated on the first Monday. And technically that would not even be a month from the last update anyway. For whatever reason Google really hasn't been able to keep this phone on the same schedule as the others. I could be due to the fact that it is the only one and Linux kernel version 5 all others are on version 4. Or maybe it's because they have too much other crap going on with dev previews. We had 12l dp which as really only a feature drop. Then we have 13 beta. And then they announced that the 12l program would be continues as a monthly platform for the next feature drop. So I personally think they took on too much. Then you add in the the p6 is a completely different phone than the previous generations of pixels. They still haven't figured out the modem yet.
So my answer is no I don't expect it the first Monday in April maybe the second Monday.... maybe
Yes l am expecting an update on Monday, Google need to start releasing timely updates for there latest phones.
Without any actual information on which to base my opinion, I'm guessing yes we'll see the update on the 4th. It's not a Feature drop month so the update will be simpler, and they really need to incorporate the dirty pipe patched kernel.
I'm not expecting anything. I'll wait until my Pixel 6 comes back from RMA (for the second time) and then I'll sell that POS.
Haptics!!!
The March update seemed to be on schedule for the older Pixel devices using older kernels. I believe that latest devices with the newer kernels were delayed because of the 0-day exploit that was discovered last-minute. They wanted to patch that in the March update.
So barring anything like that then I would expect Google to be on time with the April update. Or at least not as late as the March update was.
The only bad thing about updates is the unnecessary new threads from peeps not understanding what they are doing.
Also custom Roms create issues.
I guess flashing and modding for the hell of it with no idea why. Is like a drug to some peeps.
utnick said:
I believe that latest devices with the newer kernels were delayed because of the 0-day exploit that was discovered last-minute. They wanted to patch that in the March update.
Click to expand...
Click to collapse
The fix is in kernel version 5.10.102 and above and the kernel version for the March update is 5.10.66. The CVE for this vulnerability is not listed in the March update either.
I don't believe they fixed this in March.
TonikJDK said:
The fix is in kernel version 5.10.102 and above and the kernel version for the March update is 5.10.66. The CVE for this vulnerability is not listed in the March update either.
I don't believe they fixed this in March.
Click to expand...
Click to collapse
You are correct. They didn't fix the dirty pipe vulnerability with the March update and in fact Google confirmed that the delay in March was not due to this particular vulnerability.
TonikJDK said:
The fix is in kernel version 5.10.102 and above and the kernel version for the March update is 5.10.66. The CVE for this vulnerability is not listed in the March update either.
I don't believe they fixed this in March.
Click to expand...
Click to collapse
I guess I should have looked that up.
But I'm really not bothered about when in the month the updates come as long as they come. Though I'm coming from an LG phone and updates weren't really a thing I expected from them.
utnick said:
I guess I should have looked that up.
But I'm really not bothered about when in the month the updates come as long as they come. Though I'm coming from an LG phone and updates weren't really a thing I expected from them.
Click to expand...
Click to collapse
I am not too worried about this vuln. It requires physical access to the phone.
Based on previous updates I won't be in a hurry to install the next one right away.
TonikJDK said:
I am not too worried about this vuln. It requires physical access to the phone.
Click to expand...
Click to collapse
AS far as I know, the dirty pipe vulnerability can be included in a compromised app.
Fido hasn't listed anything yet.
The March update was released on 03/21, right? That will be two weeks tomorrow -- seems an awful short turnaround.
I'll be pretty surprised if the April update rolls out on the 4th.
It`s here.
Update 12.1.0 (SP2A.220405.004, Apr 2022) released 1PM EDT April 4th
Still Kernel 5.10.66.
where do we find a changelog?