Hi, i was on Cm11 20140306 (i'm followed ota of cm11 from january) and all works perfectly, i use elementalx kernel from about 1 month, this morning i've updated to cm11 20140307 with cm stock kernel, after about 15/20 minutes when i've tried to wake the phone the screen stay black, if long press power button nothing happened (I was very very scared), i long press again power button and the phone power on with google logo etc, this happened 2 times, after i've tried to flash elementalx and it would seem ok, but what's wrong with last update of cm11 and its kernel?
Greetings
Well it's a nightly. Issues are too be expected, as the builds are untested and automated, containing the latest merged git commits which may or may not work well. When you choose to use a nightly that's what you sign up for.
Sent from my HTC Desire using xda app-developers app
is there a stable cyanogenmod for nexus 5? or what's best smooth performance stable rom?
anthraxx90 said:
is there a stable cyanogenmod for nexus 5? or what's best smooth performance stable rom?
Click to expand...
Click to collapse
Theres no officially labelled stable builds yet, however there are a few snapshot builds. They should be more stable than nightlies.
Asking for the best rom on xda is against the rules. The question is subjective and thus it varies from user to user. Try a few out and see what satisfies your needs. To answer your question though, most roms here are somewhat stable. Just read through the last few pages of the particular rom's dev thread to see if there are any issues before flashing.
thanks for advice, is there a changelog of last snapshot cm11?
Related
Can anyone please tell me what are most stable nightlies for Team EOS, CM and Code name ?
Thanks .....
madazam said:
Can anyone please tell me what are most stable nightlies for Team EOS, CM and Code name ?
Thanks .....
Click to expand...
Click to collapse
Nightlies are developmental builds, meaning, the developers are trying to implement new different things into their builds and release them in "nightlies" for people to download, test, and then report back their findings of smoothness, any bugs and such, so really the stability can change from one nightly to another under the same developer.
Example: random ROM nightly 114 woks fine, random ROM developer tries to integrate a theme engine into random ROM nightly 115, which then causes the OS to become unstable under certain conditions, testers that downloaded random ROM nightly 115 notice this problem and report back to random ROM developer and send them their catlogs so random ROM developer can see what is happening in the system that is causing the problem, fixes it and includes it in random ROM nightly 116 to be tested again.
Though nightlies are usually pretty stable themselves(especially EOS,) if you want TRUE stability, you will be better off going with a stable release from one of those developers, some options that nightlies offer after may not be available to you till the next stable release.
Thanks man for such s comprehensive reply. I understand the process but browsing the forum posts I alwaye see people atleast rating the nightlies in some level of stability , though not completely stable like Eos 2 or 3. I meant that kinda relative stability. A nightly rom that is least buggy and not extraordinarily crashy.
I would have experimented myself if I had the time but to tell u the truth I neither have the time nor the patience
Sent from my GT-N7100 using xda app-developers app
Just test them. Thats what they're there for.
Which one of these is the better CM11 to download? The most current nightly or the M Snapshot that was uploaded 12/5?
ILowry282 said:
Which one of these is the better CM11 to download? The most current nightly or the M Snapshot that was uploaded 12/5?
Click to expand...
Click to collapse
Anyone??????
Depends on what you want. The snapshot build has been tested and confirmed to be somewhat stable, while the nightlies are completely untested automatic builds that contain all code that has been submitted to the git.
If you want the latest and greatest, and are willing to deal with possible bugs then go with the nightly.
If you value stability and dont care for the latest commits incorporated in the rom, go with the snapshot.
Patience is the key young padowan.
Flash Nightly. It is proven to be much better than Milestone, and plus it includes more features. It is really stable and is definately daily driver worthy if you do not use bluetooth often (some people report bluetooth problems).
Hit that thanks button tho
Sent from my Nexus 5
Hey guys, I need some help regarding various KitKat Roms. I used to keep myself updated with xda an year back, but now as its my 12th going on, I couldn't do so, and I don't even have enough time to read those 1000s of posts!:banghead:
So plz help me differentiate b/w mainly these two roms-
1) http://forum.xda-developers.com/showthread.php?t=2572199
And
2) http://forum.xda-developers.com/showthread.php?t=2589303
Below are my queries--
1) Which of them is more stable for daily use?
2) I read that speaker phone isn't working. That means the normal mode(when we pickup call) or when we switch it to loudspeaker?
3) In the 1st thread posted above, there are 3 builds- Jenkins build, OMINI Rom, and a build by hephappy. What's main diff. Between them??
Any help is very appreciated!
Also, please don't post posts like -- "Flash this its awesome!!"
Or,
"I use this, it'll blow your mind"
Suggestions from developers are more recommended
Sent from my LG-P500 using xda app-developers app
1) Which of them is more stable for daily use?
Click to expand...
Click to collapse
I use the one from mukulsoni as daily Driver and am totally ok with it, I chose is as the other one still sais that it's early experimental. If you use the sweetnsour Kernel and the newest Version (v5) you should be happy.I don't realy see any bigger troubles so I'd suggest you install it and see for yourself, as flashing doesn't take to long and before installing to much, you just check if the main Functions suit your needs
2) I read that speaker phone isn't working. That means the normal mode(when we pickup call) or when we switch it to loudspeaker?
Click to expand...
Click to collapse
Talking when you pick up is fine just the switching to loudspeaker is supposed to not work. I never use loudspeaker in calls so I can't tell you if it's true but normal calling works
3) In the 1st thread posted above, there are 3 builds- Jenkins build, OMINI Rom, and a build by hephappy. What's main diff. Between them??
Click to expand...
Click to collapse
Can't really help you there, but it has as far as I know to do with the different defs working on it.
Hope this helped.
D3oDex3D_AyusH said:
3) In the 1st thread posted above, there are 3 builds- Jenkins build, OMINI Rom, and a build by hephappy. What's main diff. Between them??
Click to expand...
Click to collapse
Jenkins build is original cm 11 build
Omni rom is different rom its based on omni sources its still in very early stage
so dont use them
Hephappy build is far old one
its just a preview version of kitkat
so dont use this one
IF u wanna use daily use jenkins cm 11 build
if u r intrested to try new rom
try omni
There's basically no difference between those two ROMs. Almost the same.
Both ROMs are pretty stable except battery drain and Bluetooth issue with some phones. And for SD-EXT, only link2sd works at the moment.
Yea. You cam talk normally by picking up the phone but won't hear anything in loudspeaker mode.
Jenkins is a kind of build server and Jenkins build are the builds built by it. You can set its source from Github and downloads from androidarmv6's jenkins.
Omni ROM is a kind of with many added features other than stock android or CyanogenMod. Its not much stable as of now. You can get experimental builds from here and submission tests here
Builds by Hephappy are the ones which Hephappy (a great developer) built. They were the first ones to have workinh KitKat. But not suitable for daily use. You can find them here (KitKat builds). Hephappy's folder (all builds)
Every build except the Omni ROM is pretty stable to use as daily driver. Omni to become stable soon :good:
Hope this helped you
Bartlebyxxx said:
I use the one from mukulsoni as daily Driver and am totally ok with it, I chose is as the other one still sais that it's early experimental. If you use the sweetnsour Kernel and the newest Version (v5) you should be happy.I don't realy see any bigger troubles so I'd suggest you install it and see for yourself, as flashing doesn't take to long and before installing to much, you just check if the main Functions suit your needs
Talking when you pick up is fine just the switching to loudspeaker is supposed to not work. I never use loudspeaker in calls so I can't tell you if it's true but normal calling works
Can't really help you there, but it has as far as I know to do with the different defs working on it.
Hope this helped.
Click to expand...
Click to collapse
Thanks a lot for that info. ! Thanks for clearing my confusions! :thumbup::thumbup:
Gave a thanks, hope I could give more than one for a post.......
Sent from my LG-P500 using xda app-developers app
kprsnt said:
Jenkins build is original cm 11 build
Omni rom is different rom its based on omni sources its still in very early stage
so dont use them
Hephappy build is far old one
its just a preview version of kitkat
so dont use this one
IF u wanna use daily use jenkins cm 11 build
if u r intrested to try new rom
try omni
Click to expand...
Click to collapse
Thanks a lot for the valuable info! :thumbup:
I am left now to think only about mukulsoni's thread and Jenkins build!
Thanks again....
Sent from my LG-P500 using xda app-developers app
rhar**** said:
There's basically no difference between those two ROMs. Almost the same.
Both ROMs are pretty stable except battery drain and Bluetooth issue with some phones. And for SD-EXT, only link2sd works at the moment.
Yea. You cam talk normally by picking up the phone but won't hear anything in loudspeaker mode.
Jenkins is a kind of build server and Jenkins build are the builds built by it. You can set its source from Github and downloads from androidarmv6's jenkins.
Omni ROM is a kind of with many added features other than stock android or CyanogenMod. Its not much stable as of now. You can get experimental builds from here and submission tests here
Builds by Hephappy are the ones which Hephappy (a great developer) built. They were the first ones to have workinh KitKat. But not suitable for daily use. You can find them here (KitKat builds). Hephappy's folder (all builds)
Every build except the Omni ROM is pretty stable to use as daily driver. Omni to become stable soon :good:
Hope this helped you
Click to expand...
Click to collapse
Thanks, now I got it, i'll give a try to version 5 in Mukulsoni's thread:thumbup:
Sent from my LG-P500 using xda app-developers app
So I've just been running a stock rooted flashable ROM nothing else. I want to have CM or a CM based ROM due to easy updating etc.. Anyway I'm ocd when it comes to what's on my phone I just don't want any bugs or issues.
Sent from my Nexus 5 using Tapatalk
Yes, CM and most other roms found in Android development forums are stable enough to be used as a daily driver. But obviously you will face fcs sometimes!
Why don't you try it out? If you're not happy with it, just restore the nandroid backup!
Don't use nightlies, use release candidates or releases those will be the most stable. I think the snapshot would be your best bet or read the CM thread and see what problems users are reporting if anything.
http://download.cyanogenmod.org/?device=hammerhead
There are more ROMs besides CM. Those Devs work hard and don't want to be overlooked just because CM is the most well-known aftermarket ROM.
Depends how picky you are regarding stability/daily driver of a phone.
If you want to play it safe, just root phone and install Xposed + GravityBox.
If you want to explorer more capabilities, go with a stable build of CM.
However, from my past experience with CM/custom roms, it's really all random. I've had unstable experiences even on a stable CM build, and I've had fairly stable daily driver of a rom when using nightlies too. It's really all a gamble.
Always make backups.
But I will say from where you are coming at, I'd try the Xposed framework + GravityBox 1st before you attempt going CM.
I'm using CM11 snapshot M3 and it's working fine for me. No bugs so far. Give it a shot.
Aria807 said:
Depends how picky you are regarding stability/daily driver of a phone.
If you want to play it safe, just root phone and install Xposed + GravityBox.
If you want to explorer more capabilities, go with a stable build of CM.
However, from my past experience with CM/custom roms, it's really all random. I've had unstable experiences even on a stable CM build, and I've had fairly stable daily driver of a rom when using nightlies too. It's really all a gamble.
Always make backups.
But I will say from where you are coming at, I'd try the Xposed framework + GravityBox 1st before you attempt going CM.
Click to expand...
Click to collapse
Thats what I'm currently doing... Lol. I only use the status bar signal colours and nothing else. I like stock with a little changes.
Sent from my Nexus 5 using Tapatalk
hyelton said:
Thats what I'm currently doing... Lol. I only use the status bar signal colours and nothing else. I like stock with a little changes.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I too recommend gravity box, but give cm a shot, Just back up, play around with CM, if you don't like it just restore, good as new :good:
I'll be flashing the latest nightly right now, 3-5-14
I'm a little OCD myself, I dislike having all those Play Apps to be honest lol, :silly:
You can play it safe with multirom manager. Use it to keep your current rom and dual boot into other rom to test them out. That's what I'm doing.
Sent from my Nexus 5 using Tapatalk
I'm for GravityBox + stock honestly. Xposed gives me all the tweaks I really need.
IMO yes it is very stable. I've chosen to run PA purely because I love Pie. They are all very stable these days, only the ones which say that they are unstable are unstable.
Devs and contribs are getting pretty good
Sent from my Nexus 5 running PA 4.1 and franco.kernel
Monthly, release candidates and releases are stable.
+1 to avoid nightlies w/out nandroid backup.
for example all of the nightlies sincd 03/01 breaking google dialer and voice+.
Hi.
I am new to this.
I am running RR for a while.
Every Time there's a new build up, dev instructs to flash latest CM NIGHTLY.
I was thinking - why not just run the Nightly build as a daily rom?
Am I missing something? Is it strictly for development purposes?
I am looking for rock solid stability mainly.
Thanks!
benyben123 said:
Hi.
I am new to this.
I am running RR for a while.
Every Time there's a new build up, dev instructs to flash latest CM NIGHTLY.
I was thinking - why not just run the Nightly build as a daily rom?
Am I missing something? Is it strictly for development purposes?
I am looking for rock solid stability mainly.
Thanks!
Click to expand...
Click to collapse
That's usually only recommended if there's a change in firmware in CM. It's not necessary to flash CM13 every time before flashing RR. I've never even used RR but I'm sure that's the only reason he would advise to flash CM.
Latest CM13 works great, rock stable at the moment so if you wanna switch go ahead
Sent from my A0001 using Tapatalk
CM nightlies contain firmware files in it. So what the dev wants is for you to update to the latest working firmware from CM nightly, and when you flash RR after, the firmware stays.