Related
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.
This might be a silly question, but what exactly are the differences between the three Jellybean ROMs I see in the dev section (Paranoid, CM10, AOKP)?
None of these seem to have any kind of "feature log" or changelog.
Anyone have any insights?
tehkingo said:
This might be a silly question, but what exactly are the differences between the three Jellybean ROMs I see in the dev section (Paranoid, CM10, AOKP)?
None of these seem to have any kind of "feature log" or changelog.
Anyone have any insights?
Click to expand...
Click to collapse
Paranoid Android Is Jellybean
AOKP....not going there with that one
CMX, Pure build from code. Great rom.
differences, not exactly sure, but most will have a twitter to keep up with changes if possible
leo72793 said:
Paranoid Android Is Jellybean
AOKP....not going there with that one
CMX, Pure build from code. Great rom.
differences, not exactly sure, but most will have a twitter to keep up with changes if possible
Click to expand...
Click to collapse
I'm not trying to be a ****, but you kind of didn't answer my question in any way.
a) What's wrong with AOKP?
b) I know Paranoid is JB, that's why I mentioned it. Are you saying it's stock JB? Kinda confused on the wording here.
c) Obviously, you're a fan of CM10 (aka CMX). What makes it so good compared to the other two? I see the thread for it has more posts (and thus seems to be more popular), but why?
Again, I'm not trying to be difficult. Just hoping to get an answer without having to flash 3 different ROMs.
Each ROM has different features.
CM isnt just straight AOSP
Rxpert said:
Each ROM has different features.
CM isnt just straight AOSP
Click to expand...
Click to collapse
As much as I am grateful that people are paying attention to this thread and attempting to answer, this is the 2nd non-answer I've received so far.
I know each ROM has different features, that's why I made this thread.
I know CM isn't just straight AOSP.
My issue is that unlike most of the Sense ROMs, these JB ROMs have no feature list at all, and don't even cite any sort of changelog. Thus, I can't make an informed decision on which ROM to flash.
leo72793 said:
Paranoid Android Is Jellybean
AOKP....not going there with that one
CMX, Pure build from code. Great rom.
differences, not exactly sure, but most will have a twitter to keep up with changes if possible
Click to expand...
Click to collapse
That's like.. not even fully correct.
Please make sure you know what you're talking about before you answer questions, as not knowing the answer will only cause more confusion.
To OP,
Paranoid: Paranoid Android is an AOSP JB ROM that focuses on the fusion of phone mode and tablet mode. Typically putting a phone into tablet mode would be cool, but some features of tablet mode just don't work that well on a phone. So they've worked on making the tablet mode experience work better on a phone. You can read more about it here.
AOKP: AOKP (Android Open Kang Project) is a highly customized AOSP build that is somewhat similar to CM in that it has a lot of tweaks available to it. AOKP actually has a bit more customization than CM, allowing you to center the clock, add the day of the week to the clock, weather in your notification menu, and a few other neat tricks. You can read more about it here.
CM10: CyanogenMod is the most popular custom Android ROM around, with a very large user base. It supports many different devices. We just recently received official support, meaning we will get official releases and nightlies on a daily basis. This is a plus for CM, because we don't have official support for AOKP and Paranoid, which means we might not always get the newest updates. While it has less ability for customization than AOKP, CM is still a very solid AOSP ROM. You can read more about it here.
All three are great ROMs, and at this point they have mostly the same bugs. I would personally suggest CM10 because the development for it is a bit more active and I've noticed better battery life and less buggyness while running that over AOKP.
SoraX64 said:
That's like.. not even fully correct.
Please make sure you know what you're talking about before you answer questions, as not knowing the answer will only cause more confusion.
To OP,
Paranoid: Paranoid Android is an AOSP JB ROM that focuses on the fusion of phone mode and tablet mode. Typically putting a phone into tablet mode would be cool, but some features of tablet mode just don't work that well on a phone. So they've worked on making the tablet mode experience work better on a phone. You can read more about it here.
AOKP: AOKP (Android Open Kang Project) is a highly customized AOSP build that is somewhat similar to CM in that it has a lot of tweaks available to it. AOKP actually has a bit more customization than CM, allowing you to center the clock, add the day of the week to the clock, weather in your notification menu, and a few other neat tricks. You can read more about it here.
CM10: CyanogenMod is the most popular custom Android ROM around, with a very large user base. It supports many different devices. We just recently received official support, meaning we will get official releases and nightlies on a daily basis. This is a plus for CM, because we don't have official support for AOKP and Paranoid, which means we might not always get the newest updates. While it has less ability for customization than AOKP, CM is still a very solid AOSP ROM. You can read more about it here.
All three are great ROMs, and at this point they have mostly the same bugs. I would personally suggest CM10 because the development for it is a bit more active and I've noticed better battery life and less buggyness while running that over AOKP.
Click to expand...
Click to collapse
Thanks you so much for your in-depth answer.
I'll do some more research with the provided links, and will probably flash something tonight.
Thanks again.
tehkingo said:
Thanks you so much for your in-depth answer.
I'll do some more research with the provided links, and will probably flash something tonight.
Thanks again.
Click to expand...
Click to collapse
No problem. I would suggest trying them all, since there are differences between each of them.
tehkingo said:
As much as I am grateful that people are paying attention to this thread and attempting to answer, this is the 2nd non-answer I've received so far.
I know each ROM has different features, that's why I made this thread.
I know CM isn't just straight AOSP.
My issue is that unlike most of the Sense ROMs, these JB ROMs have no feature list at all, and don't even cite any sort of changelog. Thus, I can't make an informed decision on which ROM to flash.
Click to expand...
Click to collapse
It was directed more twards the poster above me. My pizza got delivered in the middle of typing so I had to go let the guy in. Sorry my post was so short and abrupt.
SoraX did a great job of explaining the main goals/differences between the ROMS>
The reason there isnt a changelog is because at this point the developers are more focused on getting things working 100%. Its the nature of the beast.
Rxpert said:
It was directed more twards the poster above me. My pizza got delivered in the middle of typing so I had to go let the guy in. Sorry my post was so short and abrupt.
SoraX did a great job of explaining the main goals/differences between the ROMS>
The reason there isnt a changelog is because at this point the developers are more focused on getting things working 100%. Its the nature of the beast.
Click to expand...
Click to collapse
Ah, gotcha. Sorry for the attitude.
Per josegaire's post:
http://forum.xda-developers.com/showpost.php?p=50702685&postcount=148
It's even a featured news item:
http://www.xda-developers.com/android/pac-rom-updated-to-android-4-4-2-more-sweets-for-everyone/
To say i'm excited would be an understatement. Very interested in seeing what this rom has to offer.
Ohh.
I was just at the downloads section after the time passed, and didn't see anything for Ruby or Amaze.
Drat.
It's still exciting though.
http://jenkins.pac-rom.com/job/PAC-man ROM Nightly Build/
This is the nightly building process page, the green ones are successfully built, the red ones indicates failed builds and gray in progress of building, You will need github account to view this page.
you will find building pac ruby was unsuccessful today, so guess we have to wait for tomorrow or for building process to start again.
Was creating an entire thread for this really necessary? Posting in the PAC thread would've been a better idea in my opinion.
SuperAfnan said:
Was creating an entire thread for this really necessary? Posting in the PAC thread would've been a better idea in my opinion.
Click to expand...
Click to collapse
I apologize SuperAfnan, "General" thread seems a fine place to disseminate a little news, especially considering this sort of news might reach a different audience than that found in the PAC Dev thread, and this might be a more apropos place for trivial discussion. It is in that thread also.
Update by josegaire:
http://forum.xda-developers.com/showpost.php?p=50778981&postcount=153
It's available now:
http://forum.xda-developers.com/showthread.php?t=2669292
I checked the webpage, and the camera exposure issue is still with that rom.
Gotta say, I hope somebody fixes it soon (if it can be fixed at all)
Waiting for build with camera Fix....
Thread locked at OP's request.
I'm not in any way asking for an ETA, or stating that I could do anything that our Devs do better or quicker. Simply asking.
Is there a current set back that there have been no aosp updates while other devices like the d855 are receiving updates? I have a GREAT running Bliss pop ROM that I have been using, but has some issues already posted by others in there perspective threads.
Really just trying to feed the curiosity in my flashaholics mind at this point.
Thank you again for all that you do!
Purely guessing on my part that the stock LG Lollipop being available first via leaks and as of now via KDZ has been keeping most everyone busy and/or satisfied. I think that Lollipop was received by the other G3 variants before now, so maybe that's why they're still/resumed making AOSP/CM builds.
By the way, have you looked to see if there's automatic official new CM builds of 12.x?
They are having issues with data for 5.1, that's why updates seem to have stopped.
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?