yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] samwebbo1990:
I didn't think Franco's kernel was compatible with this ROM?
[Nexus 5 Original Android Development] tibere86:
Go to Settings>Sound, scroll down and untick link ringtone and notification, turn up volume to desired level then retick link. More than likely notification volume got set to silent. Happens to me on occasion on first boot.
[Nexus 5 Original Android Development] hanschke:
you made my day tibere86:good:
[Nexus 5 Original Android Development] rcook55:
Which GApps are you using? I'm asking to see if an issue I had with an older build was CM updater or GApps related. I'd like to install the M2 with PAGapps and then hopefully use CM updater without having to reset my homescreens after each update.
[Nexus 5 Original Android Development] deanesn:
I use banks standard but I fixed my issue by deleting the cwm's log file.
[Nexus 5 Original Android Development] rcook55:
Ok good, it must have been CMUpdater related then. I was able to update but doing so with PAGaaps caused all the homescreens to revert to first-boot status.
[Nexus 5 Original Android Development] deanesn:
Are you using Launcher3? I use Apex and I have ran into this issue.
[Nexus 5 Original Android Development] marcusva79:
Now I am getting the urge to update from 1/05 to 1/06. Damn you nightlies!
[Nexus 5 Original Android Development] Pekempy:
Not sure about other people but 20140106 theme chooser isn't working for me. No idea about earlier builds.
[Nexus 5 Original Android Development] marcusva79:
Did you use a different kernel?
[Nexus 5 Original Android Development] Smallsmx3:
Anyone using the cm camera over the stock camera? Better? Worse?
[Nexus 5 Original Android Development] Pekempy:
Didn't think that would affect it.. That's annoying.
[Nexus 5 Original Android Development] marcusva79:
I know with faux kernel it kept fc'ing with it. Went to Franco's and it works fine :)
[Nexus 5 Original Android Development] Jsparta26:
So far I found that faux's kernel is the culprit behind theme chooser's FC's. Franco, elemental, and chaos kernels are compatible (although these kernels break the led charging light) due to the fact that they havnt implemented the fix in their kernels. Its kinda sad to see faux kernel not support cm..:(

Edit: seems like faux kernel was already acknowledged. Carry on guys :)
[Nexus 5 Original Android Development] Smedo:
This is a good question. How do we get this to be fixed by the CyanogenMod team?

What does CyanogenMod team needs to fix this?

You should think that a few of them have a Nexus 5...maybe they use an other ROM or non-stock kernel?
[Nexus 5 Original Android Development] Pekempy:
Swapped to Franco. Still getting FCs :/ tried clearing data and reflashing
[Nexus 5 Original Android Development] marcusva79:
Try wiping and start all over again with Franco
[Nexus 5 Original Android Development] Arthur4ik:
Miracast with Samsung TV causes a reboot.. how could it be? well its a nexus Wirth kernel sources available..

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] rcook55:
Well, the GEL launcher, shoot, that's more likely the issue isn't it? Though I noticed on my SGS3 when I installed M2 + PAGaaps after opting in to Google now the GEL launcher was already there.
[Nexus 5 Original Android Development] stumpy352:
I'm using elementalx & theme chooser is working. It force closes but still applies the theme.

sent from beyond the neXus
[Nexus 5 Original Android Development] Pekempy:
System wipe and full reflash worked. Previously only did data/cache/dalvik
[Nexus 5 Original Android Development] @wells:
update bootloader.
[Nexus 5 Original Android Development] brooksyx:
I thought I did. Guess it didn't stick.
[Nexus 5 Original Android Development] FAdrums:
LMAO dudes chill out! Let me try to explain myself before you guys cyber lynch me! Lol

I tried CM on my N5 early in the game and it simply wasn't "doing it for me" for various non important reasons. But I did subscribed to the thread to keep up (or try to) with the development. I then gave it another go when I found out that the kernel had gamma control but yet again it didn't do it for me, at least at that time. I then continued to (at least try) keep up with the thread and from my vague wondering through the thread the thing popping out was bugs, buged features, hence my post!

I'm still one of the xda users that believe in helping, experience it before talking (writing) and most of all respecting is a must in a community! :)

I hope it clears out! ;)

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] @wells:
k is latest. check.

or maybe a bad download.

all works fine with cwm6045 t/nt and twrp 2700.
[Nexus 5 Original Android Development] ASHURiCAN:
Latest nightly works fine for me. Nothing wrong, go go CM!
[Nexus 5 Original Android Development] kealke:
Not trying to lynch you! I just don't get why you (and others) say the rom is bugged, because if you follow some simple instructions and guidelines, it's simply not. I myself have been using CM since so long i don't even remember and always have been very happy with it. Sure, there are some things that don't work perfectly, but for each of those there is a good workaround. Just use the search and if that doesn't give you a solution, just ask. I also have tried some other roms, which like CM for you, didn't "do it for me". Despite that, you won't find a single "this rom is bugged/crappy/bad" post from me. I just revert to the rom that does "do it" which in my case happens to be CM.

What i'm trying to say here is that if you use a custom rom and certainly the nightly builds, you shouldn't be amazed if sometimes something doesn't work the way you expected. It's for free, there are a lot of people trying to work out the little flaws, also for free.

Sure, the stock roms work without a lot of these little flaws, but they are not exactly customisable or nearly as feature rich as most of the custom roms. And as i said, for al these things there's almost certainly some workaround, just do your best searching for them or ask for them in a nice manner if you can't find them yourself. You'll find that the responses you get are alot more friendly than the ones you got now.

To add to that, the reason most posts are about "bugs" is that people who don't have problems usually can't be bothered to post about how happy they are, so threads like these get biased to the "bad" side no matter how good the rom may actually be or isn't.

Again, i'm using CM for literally years and on a lot of different devices and i almost never have any problem. I'm using the nightly's as soon as they come out. CM is and will be for a long time my daily driver and for me it just keeps getting better. I just read the known issues and when needed i use a workaround for them. Please try that for yourself and if you still have a real problem, try asking for a solution in a nice and normal way. You'll be amazed how good and fast you'll be helped if at all possible
[Nexus 5 Original Android Development] FAdrums:
Top answer dude! Kudos!

Will give it another spin over the weekend as I have more time to play around with my device. :)

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] ASHURiCAN:
Top top! ?
[Nexus 5 Original Android Development] myfluxi:
Check this out: https://github.com/myfluxi/kernel_msm/commit/4e79d2ecf49f4ce5af98001d665b881b333f42c2

My approach was similar and performed even better, CAFs is much, much more elegant with the scheduler stuff on top. Key is cpu-boost and especially interactive's timer function with external boost awareness. I'll pick my thingie up if I have the time, doing much more sports these days.
[Nexus 5 Original Android Development] djsubtronic:
Noticed a lot of people saying they need to update their bootloader to get the newer nightlies to work. I haven't updated mine since I got the phone around 6 weeks ago. I'm on bootloader HHZ11k. Should I be updating it?
[Nexus 5 Original Android Development] cjwaggsrx8:
Naw you're good to go bro..
[Nexus 5 Original Android Development] sn0warmy:
I'm sorry man, but you completely contradicted yourself within the first 3 sentences of your post.

To say that CM doesn't have "bugs" is completely false and such a typical fanboy statement. CM does have bugs, just like many other custom ROMs. The issue is that the bugs (that do exist) in CM seem to be a consistent ongoing problem that many other ROM developers have already figured out months ago.

The main bug I am referring to is Bluetooth streaming. It's broken, plain and simple. Sure it works for some with various devices/cars but I know that I have personally tried to get CM's bluetooth pairing to function properly with 3 different cars of varying brands and a home theater system. It simply will not work. Meanwhile, many other custom ROMs available have absolutely no issues pairing with any of the 3 vehicles or the home theater system.

I know people will chime in and say "it works for me" but for many of us, it doesn't. And others will say that they don't even use Bluetooth so it's a non-issue. However, the simple fact is that Bluetooth is STILL an issue and is very much a known "Bug", whether you want to believe it or not. And unfortunately for me, it's a deal breaker.

Believe me, this is coming from someone who has sworn by CM ROM's since the Nexus One. It has always been my go to ROM and on most phones I wouldn't even bother rooting the phone until a stable CM ROM was out. However, Since the release of CM11 it just isn't the go-to ROM for many who used to swear by it due to the lack of progression that other developers have achieved. It's sad but true.

And for reference, I've tried every CM11 "M" build and various nightlies. All of them resulting in the same broken Bluetooth.
[Nexus 5 Original Android Development] kong:
^

This. And also the annoying crackling notification sound.
[Nexus 5 Original Android Development] :
I am using M4 with latest bootloader, no additional kernels or mods. No bugs for me at all. Bluetooth streaming works perfectly for me. Above poster maybe having problems but I am not. I am not sure why. Maybe streaming on certain hardware doesn't work with cm. You're not using a custom kernel right?

I used m3 for a couple weeks then m4, I would consider them stable. I never liked nightlies.

Sent from my Nexus 5
[Nexus 5 Original Android Development] sanstrom:
bluetooth is not stable...flat out.

And it's broken for me and has been since day one. I'm on modified stock due to this. Bluetooth on aosp is a crapshoot. I think cyanogen is having issues with the CAF drivers or something. I want to use cyan bad but this is a dealbreaker. If bluetooth works for you or u don't use it more power to you but in todays growing age of laws that force you to use bluetooth to drive and talk on the phone this is essential.
[Nexus 5 Original Android Development] :
Bluetooth streaming on completely stock no other kernels, M Snapshots builds isn't working for you guys at all?

Sent from my Nexus 5
[Nexus 5 Original Android Development] kealke:
Ok, i admit my choice of words wasn't the best one. It's kind of hard for me to put things exactly as i mean them in English, because it's not my language, i'm Dutch. What i mean is that there are bugs, but they are as you say very known. Knowing that, it's not very useful to keep complaining about them, that's maybe a better way to put it. Again, not trying to lynch or flame!

The bluetooth, as you also say, is indeed no problem for me. I only use bluetooth with an OBD2 adaptor and occasionally to transfer some pictures from one phone to another.

The notification sounds are somewhat fixable. I pull the sound files from the phone and normalize them to have a somewhat smaller frequency range, mainly to have less high frequency tones in the file itself. Also i lower the volume. Then i put them back on the phone and edit the mixer_paths.xml file to have higher volume on the speaker, to compensate for the lower volume of the sound files themselves.

This does not fix it 100% but it makes it so it's really barely noticeable. For me that is, results may vary. Also i have noticed that it's more noticeable with some sounds than with others. Why this works is a question i don't have an answer to, i'm far from an expert and am indeed happy with the way they are now.

Again, i'm sorry for being not as clear as i should have been :)

Do i hope the very known and old bugs get fixed? Ofcourse! But i don't see the use in keeping on complaining about them or ranting about them. As i said, we should be happy with all the things that do work. If we were paying the devs for this rom it would be another story altogether, but we aren't. We download it for free and get a whole heap of features we would never get with any stock rom. For me and i think alot of other people, this compensates at the very least partially for the few things we have to miss.

To each his own, and for each his own free choice of roms. The perfect rom is still to be made :)
[Nexus 5 Original Android Development] kellybrf:
try elemental x, it solved all my Bluetooth issues
[Nexus 5 Original Android Development] :
Currently on M4. What's the best way to change the size of the NavBar without Xposed?
[Nexus 5 Original Android Development] Pithism:
it fixed my woes as well. I didn't have bluetooth on CM since January so i left, and once elemental X did what ever he did, bluetooth with CM works for me.
[Nexus 5 Original Android Development] om22:
There can and will never be a completely bugless experience on android. I don't have any issues with 4 bluetooth devices (3 headphones and 1 vw car audio) on stock cm kernel. I can't reproduce any bluetooth bug mentioned here.

There are more important things in life than having a perfectly smooth notification sound. If you want everything bug free buy a closed soirce iPhone for the double price and loose all the android fun.

Besides of that battery life is much better on cm compared to stock.

I haven't had any major flaw since CM7 on the sony xperia arc. Yes I am a CM fanboy but that doesn't change anything.

People have too high expectations. Also the CM devs are humams like everyone here. Humans make errors you can't convince anyone of anything else.

<\offtopic>

Sent from my Cyanexus 5
[Nexus 5 Original Android Development] magnamentis:
perhaps this would be for you ?

hi, was following the little back and forth and thought that i would mention quick that,

albeit cm was a bit short of features for me compared to some of the other "CM-BASED"

roms, i'm totally happy with it now as for combining it with XPOSED FRAMEWORK.

xposed lets you do many of the little tweaks which make sense to me without being toyish,

those which cm is missing, which again i like for it's orderly structure.

atl4ntis, the dev of cataclysm brought it very well to the point in my opinion:

he wrote that he would never add much to his rom that could be achieved, sometimes

even better, with an app.

so CM11 + Xposed + LMT + SWAPPS + HOLOLAUNCHER + TASKER etc. do that for me

and there is no more reason to say, the rom does not do it for me :)

then add a nice little kernel which which gives me 1% battery in 8 hours idle over night

and the possibility to tweak the display colors and gamma to my liking and things are indeed great if not perfect :)

further, another little advantage of going with apps and xposed as far as possible is, that it makes

us more independent from rom makers whether they add features or not.

as you can see in my sig i have devices from various makers and/or various age and all of them,

back to the GS2 are, UI-wise, identically set up and running well on last edge 4.4.2 software with this concept.

expcept of course the n7000 which i keep stock to remind me to flash the others regularly haha.... just kidding,

it's in case that i f... up the n7100 and i night one big working at all times :)

regards

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, AGNI Kernel 2.7.5_r3, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, 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, ElementalX Kernel 0.34, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, etc. )

_________________________________________________________________________________________________________________________________________
[Nexus 5 Original Android Development] djsubtronic:
Can I just say that even iPhones aren't bug free. There is no such thing. Not even aircraft autopilot.
[Nexus 5 Original Android Development] crpalmer:
FYI, cyanogen already merged this commit into the HLTE kernel:

https://github.com/CyanogenMod/andr...mmit/5df8acb230755c8b6087f2b4dc2f6ec4fe006047

I'm not sure how different what you want to submit is from the CAF commit though.
[Nexus 5 Original Android Development] myfluxi:
Awesome stuff from CAF, this patch series fixes the load issue that becomes apparent in 3D apps and improves general scheduling performance.

Jitter/stutter is still there. My stuff is hacky, wip and has side effects, I'll send patches when (if) I would no longer embarrass myself.
[Nexus 5 Original Android Development] sledge3n8:
A few people I know are always *****ing about losing contacts, data and random freezes and reboots on their precious iPhones. Not even CrApple is free of bugs.
[Nexus 5 Original Android Development] InterFace86:
since 29/03 i cant use any build. just throws tons of error and they never stop. for example callui stopped, dsp stopped working, system stopped working etc.

if i flash 28/03 again the everything is ok.

elementalx kernel and art
[Nexus 5 Original Android Development] kong:
Revert to Dalvik and you'll be OK.
[Nexus 5 Original Android Development] brooksyx:
I definitely have the latest bootloader but I am still getting error 7. God this frustrating. :mad:
[Nexus 5 Original Android Development] Circaflex:
art should be fixed in the next nightly http://review.cyanogenmod.org/#/c/62152/
[Nexus 5 Original Android Development] boxcar8028:
this is great news! I love cm11 but I miss the smoothness of ART
[Nexus 5 Original Android Development] McCol1:
Looking for a bit of help advice for getting usb audio to work.

Applied this rom to my nexus this afternoon but its been a while since ive rooted android devices and not sure if i'm missing something.

I chose CM11 as I'd read that it supported USB audio. I've tried connecting my Sony PHA-2 Dac/Amp with a OTG cable bought from Amazon but getting no sound from earphones. The music cuts out on the phone but no signal it seems to the Dac.

Could it be that my Dac just doesnt want to work with android or the cable? Or am i missing something else.
[Nexus 5 Original Android Development] Circaflex:
did it work on the stock rom?
[Nexus 5 Original Android Development] Pumpino:
I've just switched from stock with the Xposed framework and GravityBox.

One of the things I miss from GravityBox is being able to set the background of the settings menu to black rather than the standard grey gradient.

What's the easiest way to do this in CM?
[Nexus 5 Original Android Development] Circaflex:
install xposed and use gravitybox
[Nexus 5 Original Android Development] McCol1:
No, its the main I rooted and flashed this ROM. Google not supporting USB audio at this time.

I'd read of people getting it to work with CM11. Cable seems OK, just tried a USB flash drive and that worked OK.

When I play a music file it plays with no sound for a few seconds then the song pauses. Have tried poweramp pro, Apollo and google music. Same result every time.
[Nexus 5 Original Android Development] kealke:
Why wouldn't you just use a 3,5mm jack cable? And just because i'm curious, why would you use any phone for that?

Not trying to be a jerk or something, i really don't know what the point would be of using your phone for that, so please enlighten me!
[Nexus 5 Original Android Development] raptir:
Using the 3.5mm audio jack is running the audio through the phone's mediocre DAC. USB audio out gives you the unaltered digital stream and allows you to run that into a higher quality external DAC.
[Nexus 5 Original Android Development] Pumpino:
Ha! Yes, I could do that but CM does everything else that GravityBox did so it seems a shame to have to use it just for the black background. There must be another way.
[Nexus 5 Original Android Development] McCol1:
I use really nice sounding earphones that the phone just does not do justice to, although I do have dedicated dap's for music there are times I want to use the phone for music. The Dac greatly increases sound quality and volume on harder to drive ear/headphones.

Sorted it now and in the end could've done it without rooting!! App called USB player pro has solved the problem. I looked at all sorts of sites and couldnt find anything that said the Nexus could use usb audio without rooting.

No issue though as I had been thinking of rooting the phone.
[Nexus 5 Original Android Development] magnamentis:
recommendation :)

after using a great variation of configs, kernels and roms for many month i would say that GB is best for stock and/or very very close to stock while for CM and other roms with more built in tweaks i recommend xblast.

i changed from gravity box to xblast because gravity box had a tendency to interfere with rom features while xblast is able to switch almost all if not all redundant tweaks of with a slider or by not checking them.

now as to your question, xblast let's you set the background to black but i remember that gb does at well, just don't remember where it was misc or somehting, just look it up or try xblast the next time you come across interfering settings.

regards

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, AGNI Kernel 2.7.5_r3, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, 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, ElementalX Kernel 0.34, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, etc. )

Please Click The Thanks Button If I Helped You Out ______________________________________________________________________________
[Nexus 5 Original Android Development] kealke:
Ok, thanks for explaining :good:
[Nexus 5 Original Android Development] alvintimothyjr:
How do I enable haptic feedback... I'm on the latest nightly
[Nexus 5 Original Android Development] kealke:
Settings > sound > scroll down > vibrate on touch. Might be labeled somewhat different, i'm on Dutch language. If it doesn't work, deactivate it, reboot, activate it again.
[Nexus 5 Original Android Development] gravis86:
Anyone tried ART in the new 2014-04-05 nightly?
[Nexus 5 Original Android Development] iamnotkurtcobain:
Guess it still doesn't work. The commit which fixes it isn't included in the nightly. :/

Gesendet von meinem GT-I9505 mit Tapatalk
[Nexus 5 Original Android Development] mcscruff:
Random question but does anyone know how to make the default font smaller? Everything is so big
[Nexus 5 Original Android Development] Dirkenberg:
There is the com.android.keyguard app showing at the top of the list under the 'All' apps, in 'Setting', 'Apps', without any form of description. I don't recall seeing this from much more earlier builds. It doesn't affect any functionalities but it's just an eyesore to me. Anyone can shed a light what might have cause this? I am using Banks's gapps by the way. Thanks.
[Nexus 5 Original Android Development] bmakk2055:
Go settings/ home/ trebuchet settings/ general
[Nexus 5 Original Android Development] Bleys43:
Many theme-engine themes change the background color in menus, including the settings menu. Search the play store for "cm11 theme" and chose one you like.