yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Alcibiade:
No two phones are alike??? What do you mean exactly??

Coming to overclocking yes, your miles may vary to some extent. But about performance when flashing another kernel..... Differences will be extremely tiny from one phone to another.
[Nexus 5 Original Android Development] Circaflex:
what works well on one phone, say a kernel, might not work well on another. im not going to argue that with you.

---------- Post added at 03:21 PM ---------- Previous post was at 03:20 PM ----------

AOSP, not everyone uses CM code, especially on a nexus device AKA Slim, AOSPA, OMNI those use AOSP as a base sure CM might have some fixes others use but they are not CM as you put it. CM isnt the only team capable of original development, i really wish new users would realize this.
[Nexus 5 Original Android Development] thederekjay:
It wasn't randomly broke. Its called development. Like I said, bleeding edge. There is no QA, no soak tests.. Its a nightly. Things are expected to be broken.

Well you are sensing wrong. I am perfectly fine.
[Nexus 5 Original Android Development] Alcibiade:
Take two Nexus 5, with same ROM installed. If one kernel works well on phone number 1, it will work well on phone number 2.

Overclocking would be a different story. Kernels no. Unless I missed something.
[Nexus 5 Original Android Development] 3bs11:
I guess it's an answer people like to use when they're too lazy to give you a detailed answer,
[Nexus 5 Original Android Development] Anthonok:
Wasn't just broken in nightlies. Also broken in M builds... That they are using as "stable"
[Nexus 5 Original Android Development] thederekjay:
It was borked because of the huge undertaking of all the CAF stuff. A lot of things needed to be ironed out.

And here some info about 'M' releases in case you missed it..

" ...the word ‘stable’ itself is a misnomer – it doesn’t mean bug free and it certainly never meant feature complete... "

http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m6-release
[Nexus 5 Original Android Development] Anthonok:
Still built from the "stable" branch no matter what they say. Either way it didn't take 4 months to fix a basic function.
[Nexus 5 Original Android Development] Smallsmx3:
Id like to know the same? CM camera have all the 4.4.2 changes?
[Nexus 5 Original Android Development] DrunkFuX666:
As far as I have tried, the cm camera which comes when you flash the gapps in the OP doesn't have all the 4.4.2 changes... Tho if you flash PA gapps then you get the stock 4.4.2 camera which includes the changes with HDR+ and photosphere...

Sent from my Nexus 5
[Nexus 5 Original Android Development] ssauger:
Please vote here https://jira.cyanogenmod.org/browse/CYAN-3149. Create an account and then vote for my allready created issue ;)
[Nexus 5 Original Android Development] Arthur4ik:
how can I set volume rockers as camera shutter?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] q1t1:
If you flash the stock camera from PA Gapps, the volume rockers control the camera shutter
[Nexus 5 Original Android Development] gparmar76:
Is there any plan on fixing the dialer? I don't even think CM is using the Kit Kat dialer...when receiving a call the slide to answer is over the screen to hang up...on other AOSP based ROMs you see the call across the bottom with option to answer or reject the call.
[Nexus 5 Original Android Development] letsgoflyers81:
Has anyone been having bad battery life lately. Up until fairly recently I could easily get 16 hours of between charging with 3 - 4 hours of screen on time, and still have plenty of battery life left before going to bed. I can't pinpoint when it started, but now I'm lucky if I get 10 hours with 2 hours of screen on time. The biggest battery drain other than screen is Android OS which has a keep awake time of about half of the total time on battery. I'm currently on the January 8 nightly but it's been this way for at least the last few nightlies. I'm wondering if it's just me.
[Nexus 5 Original Android Development] Ulver:
Do you use CM kernel?
[Nexus 5 Original Android Development] letsgoflyers81:
Yes, it's the kernel that comes with the CM nightly. Currently 3.4.0-cyanogenmod-g8151af0 build03@cyanogenmod #1 Wed Jan 8 03:21:27 PST 2014
[Nexus 5 Original Android Development] thederekjay:
The "non intrusive" dialer is a feature from omni ROM. CM is using the the AOSP dialer based off KitKat 4.4.2 sources.
[Nexus 5 Original Android Development] gparmar76:
Is the CM dialer the same as stock? I can't remember how the stock one looked now.
[Nexus 5 Original Android Development] thederekjay:
It looks the same as stock KitKat, but has a few added features.
[Nexus 5 Original Android Development] marcusva79:
The dialer is the same but does not have Google search dialer.
[Nexus 5 Original Android Development] Lanchon:
random freezes!

hey,

my CM11 M2 freezes for like 10 seconds, then continues. it can happen anytime while doing anything. it happens many times a week.

there's very little talk about this. only found:

is this uncommon on M2? are there guys on M2 who never experince this? i need to find out if my hardware is busted somehow and if so return it.

i never used the phone on stock, bought it day zero but i dont use new phones until i cant run CM on them :)

thanks!
[Nexus 5 Original Android Development] marcusva79:
My m2 was doing that to. Decided to just use a nightly. And I haven't had one. Night lies are just as stable.
[Nexus 5 Original Android Development] kellybrf:
Yes, pretty much the exact situation as you. I only flash nightlies every week or so, back on the early Dec 20s I was getting great battery life. Flashed the 28th or so and have done a few since then, including a clean flash of 1/1 and a "full wipe, return to factory image, reroot and clean flash" of 1/8. Still not near what I used to get, with both stock and Franco kernels
[Nexus 5 Original Android Development] letsgoflyers81:
Thanks. The 1/9 nightly was just released so I'm going to try that. Also, have you tried M2 yet? I was thinking about trying that.
[Nexus 5 Original Android Development] dkotoric:
Any news on fixing miracast on cm11 for nexus 5

Sent from my Nexus 5
[Nexus 5 Original Android Development] okyere:
off topic: #cfc4life
[Nexus 5 Original Android Development] Lanchon:
thanks! looks like software and not my hardware, great news then :)
[Nexus 5 Original Android Development] raptir:
So speaking of the Bluetooth issues... are they supposed to be fixed in M6? I'm still having some trouble where the bluetooth randomly disconnects from my car.
[Nexus 5 Original Android Development] thederekjay:
So no matter what CM says or anyone tells you, you already have all the answers and no one, not even the devs, can tell you differently. No sense in this useless banter then.. Probably a good idea to keep it development related in this thread anyways.
[Nexus 5 Original Android Development] Alcibiade:
Or they simply don't have one...
[Nexus 5 Original Android Development] magnamentis:
read the following :)

http://xdaforums.com/showpost.php?p=52394248&postcount=4819

especially the part about the distinction between bluetooth connection dropout and app dropout :) depending on you config ( i have no clue which of course ) this could be

a similar case since the improvement concerning the bluetooth connection itself has been widely confirmed and i've not heard much if anything tho the contrary.

and then after all there are two ends of a connection which always can cause some compatibility issue. ( not saying it is, just saying can be ) :)

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11-M6, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, AGNI up to 2.7.6, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11-M6, ElementalX, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, Chaos etc. )
[Nexus 5 Original Android Development] Theliels:
I dont know what was the problem really, but its much more easy:

If you think you can do better the next time, then please, clone git, make the changes needed and share them with all of us, so that in this way no one has to wait so many months...

CM guys do not have to post in this forum, does not have to explain what they do or not do... and not because it is free ROM, but because it is your project.

We who voluntarily choose to use your ROM, and obviously we do without any warranty of any kind. Despite all this, you have JIRA if you want to report a bug or other problem, you have access to the code repository to view or modify what you consider ... Each team / person has their own priorities, needs, some goals to comply, failure to fix ... please ... we must be a little more respectful and grateful and patients, and if we do not like... we always can simply change ROM
[Nexus 5 Original Android Development] raptir:
I am running into true device disconnects, not app dropouts. My car will show that the device is no longer connected and if I check my phone the bluetooth icon is dark grey (not connected). In some cases if I try to reconnect manually (go to the bluetooth menu and tap on the device to connect) the Bluetooth turns off and cannot be toggled unless I reboot the phone. It seems to occur more often if I do not turn off Bluetooth after I turn off my car.

I've been using my car bluetooth reliably on an HTC One X, Nexus 4 and Nexus 5 without any issues except for CM on the Nexus 5, so I doubt it is the car.
[Nexus 5 Original Android Development] crpalmer:
I am tagging you because your post is near the end. However, the comments probably apply to everyone that is *****ing...

Have you provided a bug report in the CM bug tracking system (along with the required info)? If not, your problem is not likely to be fixed.
[Nexus 5 Original Android Development] magnamentis:
weird

ok then you have a few choices, provide a logcat and report on Jira, try the many workarounds which i was posting throughout many threads here

or choose another rom.

your description sounds very much like it was pre-M6 so there could be some remaining app data and cache data. if you really believe that

it's not an incompatibility ( it's not about which part is guilty, incompatibilities are two-sided and simply mean that two ends don't fit without

valuing whose fault it is ) then you could try a clean install from scratch with formating the various partitions. once in a while that's a

good thing to do anyway. further check if you have latest bootloader and radios installed. of course the risk with the cleaninstall will

be that if it's a compatibility issue it will be in vain and all the work for nothing.

so if you have a working nandroid backup, i'd use that one until things are settling further, if not, that would go without further comment :) :)

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11-M6, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, AGNI up to 2.7.6, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11-M6, ElementalX, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, Chaos etc. )
[Nexus 5 Original Android Development] :
On m6, I'm having an issue where the Bluetooth audio is very quiet/bassy. Anyone else have this issue?
[Nexus 5 Original Android Development] raptir:
My original post was just asking if the bug was supposed to be fixed in M6 or not.
[Nexus 5 Original Android Development] jfim88:
Wow the smoothness increase with Elemental X kernel in this ROM is very important... It's perfect now...

A question from noob... Can anyone explain me in easy language what are the benefits from using CAF kernel instead of AOSP? Why CM take this way?

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] TheBenz:
No, nothing ..

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] ej8989:
Does franco gamma display app work with the default CM kernel?
[Nexus 5 Original Android Development] dannyella:
What's with the commotion going on here? recent nightlies have been smooth as butter. I don't even feel the need to flash other kernels. Those complaining of lag are doing something wrong.

Now, is the new theme chooser already in the latest nightly?
[Nexus 5 Original Android Development] magnamentis:
here and by the way :)

http://www.cmxlog.com/11/hammerhead/

by the way since you're judging about what others have to say, after i helped you out with that link

i take the freedom to say, that asking for being spoonfed is much worse and clogging the threads much more.

90% of the questions asked in this thread could be answered by typing 2-3 words into google search bar,

and your question is basics. if you really deal with nightlies on a regular basis, checking the changlog

(commits ) to find out whether it's worth the effort to flash the latest, is the least.

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11-M6, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, AGNI up to 2.7.6, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11-M6, ElementalX, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, Chaos etc. )
[Nexus 5 Original Android Development] dannyella:
Well, news says it's in latest nightly for some device. Checked changelog for those devices and nothing theme related. That's why I asked. -___-
[Nexus 5 Original Android Development] jfim88:
I don't have the same smooth with custom or stock kernel... It's much more smooth with custom.

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] djsubtronic:
Which kernel do you use?
[Nexus 5 Original Android Development] jfim88:
Elemental X!

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] djsubtronic:
Do you sometimes get a delay turning on the screen when using this kernel?
[Nexus 5 Original Android Development] jfim88:
No! Never seen this...

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] Tagtag123:
I flashed the latest snapshot.

Now, i see that there is some dark border on the top and bottom of the screen.
[Nexus 5 Original Android Development] ej8989:
Re-set your wallpaper. Make sure it fills up the entire screen.
[Nexus 5 Original Android Development] RJQXCV:
LOL
[Nexus 5 Original Android Development] FredC94:
I had the same issue today (at least 3 times)

Running the latest nightly with ART and elementax
[Nexus 5 Original Android Development] j3di:
Art running fine on latest nightly and stock kernel.
[Nexus 5 Original Android Development] _frog hair:
It's propably a mis-match in contacts data.. Try remove facebook, and reinstall.. Remove app data from contacts and re sync. Theres different ways to do this, but it is an acore process that has stopped, and its usually due to mis match in contacts data. After resync .. Also wipe cache and dalvik( if not in ART).

//Sent from within your closet
[Nexus 5 Original Android Development] davej23:
Hi everyone! Been on stock+unroot for the past month or so and then saw that milestone 6 was released. Do you recommend that I flash M6 or the newest nightly? Thanks!
[Nexus 5 Original Android Development] klin1344:
The nightlies have never given me a problem, they are rock solid for me. Flash it if you want bleeding edge fixes and features, otherwise flash M6, which is built from the stable branch and a little behind the nightlies.
[Nexus 5 Original Android Development] davej23:
Thanks. Will go for the nightlies!
[Nexus 5 Original Android Development] hyelton:
Loving running the nightlies :). So if I flash a custom kernel when updating to a new nightlie will the kernel stick? Or would I have go reflash it each time?
[Nexus 5 Original Android Development] jfim88:
I just tested that increasing the read ahead value with kernel tweaker to 512 (same default elemental x value) the smoothness of the rom is increased like having elemental installed...

Enviado desde mi Nexus 5 mediante Tapatalk
[Nexus 5 Original Android Development] maidenboston:
flash the custom kernel each time you flash the nightly

but i'm not sure how it works with the CM updater
[Nexus 5 Original Android Development] magnamentis:
?

considering your post history and number as well as the number of thanks it's not plausible that you would ask such a noob question,

one of the first 20 post of a newbe, especially considering the statement that you love running nightlies.

i also see that you are not contributing anything else in this thread !

so to me this looks very much like SPAM to advertise your website

which is not welcome and certainly against the rules.

however for the unlikely possibility that i'm wrong:

yes you have to flash each time you flash a nightly. there are was to automate it but result is the same, you flash the kernel after the rom

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11-M6, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, AGNI up to 2.7.6, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11-M6, ElementalX, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, Chaos etc. )
[Nexus 5 Original Android Development] hyelton:
I am not a spammer and Im sorry if I came off to you as spam/noob, but I kind of have took offense to that, as what spammer would have active threads AND be on here this long lol. I'm sort of a noob when it comes to CM I'm not gonna lie to that, Not sure if I posted it but the last true time I ran CM was CM6 and CM7 which was a good time ago... The website in my signature is just a small personal website which I sell nothing on so it would be kind of pointless to spam it . And I'd also like to add I've been referred to become a Recognized Contributor on May 19th.

Sorry for the off topic post in this thread.

Back on topic:

Okay thank you , always when running ROMs I just always performed a fresh wipe data before flashing updated ROMs , a reason why I'm liking CM its so simple to just update and updates seem to go smooth and not break anything for me (yet). My main reason for asking that question is I didn't know if its gonna break anything with it flashing back to the stock kernel when flashing the update over the custom kernel.
[Nexus 5 Original Android Development] tjizzle:
I've been getting a very weird bug for the past few weeks now on several different nightlies and even after a clean wipe. It happens randomly and with any app. The phone just freezes, then screen goes black, then lock screen loads up very slowly. Sometimes it is accompanied by the status and navigation bars disappearing and reappearing. I have no idea what could be causing this. It happens on both cm kernel and elementalX.

Is anyone else seeing this?
[Nexus 5 Original Android Development] djsubtronic:
This happened to me randomly a few times on one of the nightlies I was on earlier (mid to late April, forgot which one) but hasn't happened on M6 yet.

I didn't really delve into the technicality of the occurrence, but it seemed like the SystemUI process was getting killed.
[Nexus 5 Original Android Development] magnamentis:
understood

ok so i understand that your real question makes a bit more sense :) all about semantics :)

so now that's settled, no harm done you can flash cm over custom kernel back and forth as you like. only if you have been using another

kernel like franco's on an aosp rom ( does not work with cm ) and then want to flash elementalX for example, you would have to flash the

stock / rom-stock kernel first, because franco makes changes to the ramdisk.

usually that is done best by flashing the rom and then the new kernel and there we are, it's just the standard procedure to flash rom then kernel, not much to think about that.

again i apologize in case that came over too rude, just didn't make any sense at that time :) :highfive:

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11-M6, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, AGNI up to 2.7.6, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11-M6, ElementalX, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, Chaos etc. )
[Nexus 5 Original Android Development] tjizzle:
I'll try M6. Thanks for confirming that it wasn't just me.
[Nexus 5 Original Android Development] Circaflex:
The process is the same just as it was on cm7 and just because you dont sell anything doesn't mean you don't get ad revenue from visitors.
[Nexus 5 Original Android Development] hyelton:
I think I'll be using elementalX been using Franco in the past on stock ROM so time to change things up. I was beginning to really hate this phone running on stock when I took a trip to Virginia beach I kept having issues , phone almost went out the window lol.

All is well :D will load up the 5/7 then flash elementalx and go from there :D
[Nexus 5 Original Android Development] FredC94:
I didn't say it was not :D
[Nexus 5 Original Android Development] Puttermouth:
I have the same problem over the last weeks. What launcher are you using? I suspected a bug in Aviate.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] ali8383:
Google camera hdr + mod is not working in latest snapshot m6 .
[Nexus 5 Original Android Development] :
Install the camera compatibility fix from Slimkat. You can download it here.
[Nexus 5 Original Android Development] ali8383:
Thank you its working now
[Nexus 5 Original Android Development] q1t1:
Same here, resolved by clearing cache of list of contacts app
[Nexus 5 Original Android Development] lakersFan88:
Is yelp app crashing for anyone else ?
[Nexus 5 Original Android Development] kellybrf:
what exactly is this for? I use the full pa gapps and haven't had any hdr+ problems, except that since it was moved to the play store the setting doesn't stick all the time
[Nexus 5 Original Android Development] tjizzle:
Using trebuchet. I just switched to M6 a few hours ago and it hasn't happened yet. Keeping an eye on it
[Nexus 5 Original Android Development] :
Some gapps packages lack a few lib files and that causes crashes when trying to use HDR+. The fix adds those files. Most gapps are updated by now so using latest versions in most cases work out of the box.
[Nexus 5 Original Android Development] Vanderbily666:
Is it possible to create a custom tile in for the quick settings panel? Where would I start?
[Nexus 5 Original Android Development] jfim88:
I use the stock PA gapps and any problems... I prefer to replace the Trebuchet etc with the Google Launcher to have the Now...

Enviado desde mi Nexus 5 mediante Tapatalk