yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] djsubtronic:
Forget about synthetic benchmarks, they are completely meaningless in real world usage. And forget about undervolting/overclocking. Just stick with stock for the best experience IMHO. What's the point of messing with something just to get a higher number on some pointless benchmark app?
[Nexus 5 Original Android Development] asung415:
I am confused.

Thank you for your quick input, if synthetic benchmarks are meaningless, there aught to be some improvements maybe? In real world situations? Or rather there are none because of how little "real-world" tasks use cpu/gpu?
[Nexus 5 Original Android Development] :
1. Copy latest nightly + BaNkS GApps to your phone or download them directly on your phone.

2.While in bootloader and connected to PC execute:

fastboot format system
fastboot format cache

3. Boot into recovery and flash ROM + GApps

Everything should be fine :) I've done it a few days ago and it's working flawlessly :)

In my opinion: Stick with stock kernel. I know, you'd like to underclock/undervolt/whatsoever... but you'll just make the whole system a lot more unstable with custom kernels. There has been a lot of changes and features which require kind of an interaction between the system and the kernel - remember when custom kernels broken theme support or didn't work with power saving mode? That's just two examples... there's just so much more going on under the hood. I wouldn't risk bricking features just by swapping kernels :P Just my two cents :)

By the way: Stock setup (CAF ROM + CAF kernel) have great performance and battery life :) If you're not satisfied, it's more likely an app that went rogue or wakelocks :)
[Nexus 5 Original Android Development] dom2684:
where are you changing DT2W ? I don't see it . I thought it wasn't a feature in CAF
[Nexus 5 Original Android Development] asung415:
Thank you for your advice, but unfortunately, I have reverted back to the latest Euphoria OS and UberL kernel. I would have stuck with CM12.1 but again, there as many advantages with CAF as I expected. But what I don't understand, if there is negligible performance gains with CAF, why do people opt to use it? And I only use 'synthetic benchmarks' to see what my nexus can actually achieve, not only for bragging rights or anything like that.
[Nexus 5 Original Android Development] bjoswald:
Ah, you're right. I meant DT2S. Anyway, I'm not sure if it even has anything to do with anything; I just turn it off because I don't use it.
[Nexus 5 Original Android Development] scrack26:
Hi Guys, is there any possible way to have the color profiles of the custom kernels for franco.Kernel and ElementalX but without changing the stock kernel?
[Nexus 5 Original Android Development] wintrxtrem:
Don't worry about custom kernels with CAF, bud. If it makes you feel any better, though, this was from a recent nightly..
[Nexus 5 Original Android Development] happiness4u:
It's not possible to change the kernel for CM Caf, as some of the features within the rom relies so much on the stock kernel. I also think that this rom has it's own color calibration in display settings via "Live Display". If you want to use other kernel's function, use CM AOSP.
[Nexus 5 Original Android Development] scrack26:
Thank you! I just went to that option, and just realize that there's a new option with the vivid colors. Thanks again!
[Nexus 5 Original Android Development] funkyslap:
Color profiles are working without problem on stock kernel. Just grab Kernel Adiutor from Play Store and go to Kernel, Screen and then choose your profile [emoji106]
[Nexus 5 Original Android Development] Primokorn:
When I hit my user profile it says that the account does not exist. :eek: I had the same bug on the AOSP version. Can you confirm?
[Nexus 5 Original Android Development] AvivEliyahu:
Go to contacts and ull see at the first row to make a contact which is you and then ull be able to edit it. People asked it a lot just use the search
[Nexus 5 Original Android Development] Primokorn:
Actually I don't need to go through the Contacts app to edit my avatar with other custom roms. That's why it looks like a bug for me...
[Nexus 5 Original Android Development] ea_umea:
Anyone else having issues with BT battery drain. Checking with better battery stats gives this:

Partial Wakelocks: bluedroid_timer

Kernel Wakelock: bluesleep and msm_serial_hs_dma

These seems to prevent deep sleep. Tried clean install(wiped system, data, cache), running with Gapps linked from CM-wiki but problem is still there. Running the CAF-nightly from 20150428.

Is there any more tools that can be used to dig deeper why it occurs?
[Nexus 5 Original Android Development] Primokorn:
GSam + GSam root companion. I'm charging my phone atm so I'll check later.

EDIT: [MENTION=3202112]ea_umea[/MENTION] I also have bluedroid_timer in BBS but there is nothing to worry about.
[Nexus 5 Original Android Development] myfluxi:
You run incompatible apps or additions or you hardware can't handle it. I can't/won't fix this, AOSP is for you, sorry.
[Nexus 5 Original Android Development] BAZZI_US:
As long as there're people power-using the device (which, if you flash nightlies, should usually apply to you) and have no freezes and hardly any crashes in daily use, it is definately a problem of your configuration (hardware failure, incompatible software, wrong installed,...), when any ROM doesn't run well on your device.

This is my experience with flashing custom ROMs.

By the way, why is ART rebuilt after every update? Waiting for 146 apps to be "optimized" after every nightly is really.... not so good. ;)

Is this necessary? It wasn't on CM 11.
[Nexus 5 Original Android Development] SedyBenoitPeace:
Hi [MENTION=4152171]myfluxi[/MENTION] then i'd like to ask to you one thing...the freeze issues are from incompatible apps? I imagined because i tried a kernel manager (Synapse) with official CM Caf and i had that freeze issue...but for example on another CAF rom (AICP) i had freeze in a random way...how can i see what causes these problems? Because i was using same apps on boh AICP and official CAF, i know that you can't answer to me for problems on another rom...in fact i'd like to know if i can see who and what causes these issues...for now i reverted to AOSP but i want to come back to CAF...really guys the smoothness and the battery life are something that i never see on my Nexus 5...i exclude hardware problems because in the past i tried your nightlies (when CAF wasn't yet on official CM page) and i never had a SOD...thanks in advance for the answer...i wish that i won't bother you! :)
[Nexus 5 Original Android Development] el_smurfo:
Both versions have freeze issues for many users.
[Nexus 5 Original Android Development] myfluxi:
AOSP?? We are 99.9% Google AOSP there, kernel and devicetree-wise.

Many? Many would be at least a hundred, given the popularity of the N5? Link, exact error, dmesg, logcat. No vague hints.

Edit: If you are referring to the well-known problems that exist for Sprint users, that are documented in the CM Jira, that are being worked on for weeks, that are here because Google changed their entire telephone stack to support a new Google device with 5.1 after a total fail with 5.0 that is a bug-fest, a change that ruins the experience for almost every supported CM device out there and the free time of many CM developers that are working their asses off for you.

And if you generalize this isolated and very specific error to a case of "mass freezing" in the context of the very obvious gfx errors with the CAF builds for a few users, because you do not think before you type, instead look for somebody to blame and point fingers on, this is my final contribution to xda. Because I can't take it any more and it's better to ignore stuff.
[Nexus 5 Original Android Development] Primokorn:
I'm on CM CAF since yesterday and no freeze with excellent battery life and better sounds! Good job myfluxi.
[Nexus 5 Original Android Development] mshook:
Here sideload stops at "47%" but it works. Looks like a "cosmetic bug".
[Nexus 5 Original Android Development] crash087:
it stops at 47 and then the adb on hte phone fails out, cant remember exactly what it says but it goes from saying ready to having red writing all over the screen and saying failing (i changed from TWRP to CM recovery, at least on CM it starts to send the sideload)

---------- Post added at 06:10 PM ---------- Previous post was at 05:22 PM ----------

theres no rom on here, i was having issues with apps and music constantly just closing out, so i wiped everythign and was going to sideload CM back on to start fresh (like ive done a bunch of times) and then it just.....didnt work.

where do you get the RSA key fingerprint, the only screens i really have right now are the bootloader and recovery.
[Nexus 5 Original Android Development] happiness4u:
That would be a problem. Because it only appears when the device is ON, connected to the pc, and USB debugging enabled. Sideloading is the only way now. But I haven't encountered an issue like yours, I may not be of any help. :(
[Nexus 5 Original Android Development] crash087:
the rom is there, sort of, i get to the set up screen and make it to the CM account page and then when i hit next it says the set up wizard has stopped and goes back to the language selection screen

im not getting the install failed message on adb anymore....so...progress at least? now i just have to figure out why the set up wizard keeps casting fireball spells on himself

EDIT:regular CM finally loaded and runs, but i have no idea why CAF wouldnt, i tried it with the CAF TWRP and the CAF CM Recovery
[Nexus 5 Original Android Development] hectorviov:
I have a problem with the ROM. Sometimes when I try to turn on the screen with the lock button, the screen turns on, but completely black. Then after it shuts off I press the lock button again and it turns on normally. I have it happening a lot and sometimes the screen wont turn on normally until I reboot. It seems that this can be reproduces if trying to turn on the screen quickly after a notification or an alarm is going off. Does anyone see this happening? Or is it just me? I have AmbientDisplay shut down.
[Nexus 5 Original Android Development] d1n0x:
Will this flash the 5.0.1 boot loader and radio? Or can I use it with the 5.1 variants?
[Nexus 5 Original Android Development] AndrasLOHF:
I have.
[Nexus 5 Original Android Development] d1n0x:
Yup, same here.

EDIT: Installed 3/18 nightly and updated, now everything's working fine. Love the "vivid" color option!
[Nexus 5 Original Android Development] 13pointseven:
Anyone got a link for just the 5.0.1 bootloader.img & radio.img
[Nexus 5 Original Android Development] d1n0x:
https://www.androidfilehost.com/?fid=95857557620393223

Just flash in recovery.
[Nexus 5 Original Android Development] happiness4u:
Build was failing for our caf nightly. :( Does anyone here know where to find CM12 caf kernel changelog?
[Nexus 5 Original Android Development] d1n0x:
Yeah kind of a bummer, the regular hammerhead build was built just fine and at hammerheadcaf it broke. Lol
[Nexus 5 Original Android Development] happiness4u:
Hahaha! Yeah. I've reviewed the feed on Jenkins, it's been retrying to compile the build since last night and until now it failed. WTH?! I'm so annoyed by the GMS wakelocks that's why I'm impatiently waiting for the caf build. :D
[Nexus 5 Original Android Development] razorloves:
http://review.cyanogenmod.org/#/q/s..._kernel_lge_hammerhead+branch:cm-12.0-caf,n,z
[Nexus 5 Original Android Development] d1n0x:
Haven't been getting wakelocks since GPS updated to v .97
[Nexus 5 Original Android Development] caliban2:
Others including myself still get them. But let's see if they're gone with those two commits.

Edit:

After a dirty flash from caf to aosp - yes, they're gone. :)
[Nexus 5 Original Android Development] nitinvaid:
Where is the vivid color option:D:D
[Nexus 5 Original Android Development] d1n0x:
Settings - Display & lights - LiveDisplay - Screen color
[Nexus 5 Original Android Development] nitinvaid:
Ahh I am on aosp build I don't have that option. Strange....
[Nexus 5 Original Android Development] d1n0x:
It's in the CAF builds only. This is the CAF thread btw :D
[Nexus 5 Original Android Development] myfluxi:
I'll pm you with a test kernel that adresses something that's on my mind later this evening.
[Nexus 5 Original Android Development] Sly_67:
I had some freezes in earlier unofficial builds, but now everything is OK.

Everyone must accept some imperfections in nightly builds. One reboot or freeze every couple days must be acceptable in this stage.

Thanks [MENTION=4152171]myfluxi[/MENTION] CAF is what we need ;)
[Nexus 5 Original Android Development] SedyBenoitPeace:
Thank you very much mate...i'm happy to help...i will made other questions after your PM...thanks again!
[Nexus 5 Original Android Development] scrack26:
Yeah, same here. I have some freezing when i flash the 20150426-Nightly. But that's the risk of using nightly. So i just go back to 20150424 until the next built. Currently I am on 20150428 and everything is all good. No freezing for me. Thanks [MENTION=4152171]myfluxi[/MENTION]
[Nexus 5 Original Android Development] happiness4u:
Just give it up guys. Everyone should accept the fact that Android Lollipop, especially 5.1.1 are not made for every device, like the Nexus 5. Most of the known custom rom developers already ditched out the N5 on their projects after 5.0.2, the rest that's still developing for 5.1.1 are just forked from CM and other known roms Git and not proven as stable. Since Google release the 5.0, it's been really been a big blow for this device having the dreaded memory leak.

For me the last fully working CM caf build was CM12-20150416, tried the 12.1 but immediately reverted back to 12 because of some missing functions and never moved forward again. So guys, just stop complaining about the instability of this rom, instead find an alternative rom that suits you better, which would not give you too much of a headache. By that, you won't be able to disappoint the device maintainer as well. Maybe they have their own beta-testers to report certain bugs to them, I guess, there's no need for us to report issues anymore. :)
[Nexus 5 Original Android Development] djsubtronic:
Not sure what you are referring to, I'm on CAF CM12.1 2015-04-28, everything is working like a charm, and I've never had any problems with freezing/crashing.
[Nexus 5 Original Android Development] happiness4u:
Really? Equalizer? Volume Button to skip tracks not working when ambient display is ON? I'm not having any freezes as I kept my device near AOSP, with less and only lollipop compatible apps installed.
[Nexus 5 Original Android Development] djsubtronic:
Those are minor bugs; I don't use Ambient Display, and I have been using Viper4Android (which is far superior to the inbuilt EQ app) for years now, and works fine on CM12.1. I see what you mean, but I don't think these issues stop the phone from being a daily driver nor would I consider those bugs as rendering the phone "unstable".
[Nexus 5 Original Android Development] el_smurfo:
Pretty sure the EQ was fixed several nightly builds ago anyways, leaving one very minor bug which can be fixed by using an app AndrasLOHF posted a bit ago...hardly a reason to "just give it up guys"

http://review.cyanogenmod.org/#/c/96050/
[Nexus 5 Original Android Development] happiness4u:
Your preference and choice is different from mine. I use Ambient Display all the time. That's why I stick with CM12 04/16 because it's more functional than 12.1 in my perspective, I don't have that EQ and Playback button issues. Just like what I've said in my previous post, "find an alternative rom that suits you better, which would not give you too much of a headache". In my case, CM12 satisfies me more. In fact, I didn't complain about that issues, coz it wasn't there on CM12.

One minor bug? But you guys complaining about the freezing? Have you read [MENTION=4152171]myfluxi[/MENTION]'s post #780 right after yours?! It sounds like you're getting in his nerves once again. That's why he wanted to be out on xda, because users doesn't fail to annoy him.
[Nexus 5 Original Android Development] kong:
Normally if I quit using a ROM, I wouldn't stay in its thread and keep telling people that they should also go use another ROM too... :silly:
[Nexus 5 Original Android Development] el_smurfo:
I was just addressing your two specific issues that you mentioned. As far as getting on people's nerves, it's always a personal choice to let other's words and actions effect you. You seem to be pretty good at it today as well. People call me names on the internet all the time...it's just bits and bytes. XDA is especially bad for stuff like that, but it's the only place to go for nightly build user support and bug tracking, so here we are.

I have attempted to capture a log of my specific freezing issue, but generally it happens when I need the phone and find it locked up in my pocket, so I have to quickly reboot to finish my task. It's nothing really all that terrible, sometimes twice a day, sometimes nothing for several days. It's certainly not as bad as the memory management issues that were in stock 5.0 and I'm sure it will get resolved in due time.
[Nexus 5 Original Android Development] ea_umea:
Thanks for checking! To stop the confusion here and now, was NOT a BT issue as i suspected first. Since the wakelock was on top of the list in BBS I suspected it for the battery drain, but it was another app that was the bad guy here that caused the device not going to deep sleep, https://play.google.com/store/apps/details?id=se.ica.handla, that was visible under "Alarms" in BBS. Uninstalled it and everything works as it should again. [emoji2]
[Nexus 5 Original Android Development] giovanniro98:
Quickboot and fastreboot

In hammerheadcaf build fast reboot and quickboot doesn't work. Someone else have this issue?
[Nexus 5 Original Android Development] tattedupboy:
I've been unable to flash any of the past few nightlies. I keep getting the same error, error updating installer binary, or something like that. I'm using the correct TWRP version and my bootloader is up to date, so I don't know what the problem could possibly be.
[Nexus 5 Original Android Development] funkyslap:
Recovery log? [emoji6]

Try this with TWRP 2861 hammerhead, not hammerheadcaf:

http://xdaforums.com/showthread.php?p=59574695

Maybe [MENTION=4145479]experience7[/MENTION] can put this link on the first page [emoji106]
[Nexus 5 Original Android Development] tattedupboy:
I have no problems flashing the non-CAF version. I want to try the CAF version, and can't seem to flash it. And how do I produce a logcat of something failing to flash in TWRP?
[Nexus 5 Original Android Development] funkyslap:
What about this?

http://rootzwiki.com/topic/24120-how-to-get-a-log-from-twrp/

The previous link is what you need to do in order to flash hammerheadcaf build with TWRP 2861. If you want to flash hammerheadcaf without modifying updater-script then you have to flash a proper recovery!

http://dl.twrp.me/hammerheadcaf/

Btw [MENTION=4152171]myfluxi[/MENTION], just a big thank you for all your hard work. CAF builds are perfect! [emoji106] [emoji106]
[Nexus 5 Original Android Development] tattedupboy:
I do have the proper recovery for flashing hammerheadcaf, TWRP version 2.8.5.3. Still can't get it to flash though, and I can't figure out why.
[Nexus 5 Original Android Development] el_smurfo:
Update bootloader
[Nexus 5 Original Android Development] tattedupboy:
That's also up to date. I mentioned that in my original post. I can't remember the sequence of letters, but it's the version that ends in the letter f.
[Nexus 5 Original Android Development] dom2684:
small issue I've noticed....

does anyone use snapchat?

if so have you noticed the quality of video recording with the back camera? It comes out really pixelated , no issues on the front camera though.
[Nexus 5 Original Android Development] rockknee:
I must say there's some serious s**t talking on couple last pages. "X isn't working, why?" "I don't like this ROM because it freezes" "There are some better ROMs out there" ...and not a single log provided. I wish some mod would clean this thread up and ban some users (yes, behaviour is really that rude here) . The amount of off-topic is insane. Cm12.1 caf latest nightly here running smooth and lagfree as he*l. Thanks [MENTION=4152171]myfluxi[/MENTION], please don't give up the CAF cause of some users here who get on your nerves for sure..

C'mon just wipe the whole device once, install factory image or something and then come back here saying you have freezes (cause you won't have). It's something on your/other users side that freezes. Maybe some logs? Try and get some of them and go through them, you'll find the root cause maybe..
[Nexus 5 Original Android Development] el_smurfo:
Very likely. Hasn't done it for a few days, so its hard to catch a log
[Nexus 5 Original Android Development] d1n0x:
I really have no idea what some of you guys are talking about. I have had ZERO freezes or reboots in the 4 weeks I've been using CAF nightlies. It has been rock stable and 12.1 has made it even smoother and faster.

I do understand that [MENTION=4152171]myfluxi[/MENTION] doesn't want to contribute to this forum anymore, it has really gone downhill FAST. People expecting to be spoonfed answers and whining around because of some minor inconvenience are swarming in here and f*cking everything up. These people don't appreciate the work developers put in to bring us an awesome experience. With experimenting come errors and that is to be expected. So either you deal with it or stay on stock and reconsider if rooting/modding is really something you should do, if you can't even be bothered to read through a thread, let alone even know how to use basic adb/fastboot commands or know about the basics of modding/rooting/flashing.
[Nexus 5 Original Android Development] bray424:
Both versions are also completely free of freezes for many other users. Since hardware can't be a variable, maybe give some other details. Are you using a custom kernel, stock kernel with a tweaking app, what launcher you're using, if you're using any themes. Since the rom seems work fine for a lot of people, it sounds more like a "rom+_____" problem.

Remember, the point of this thread is to aid in development of the rom, not receiving tech support. Posts of a "I have a problem, I don't know what's causing it, but fixing it should be your top priority" nature don't help anyone.
[Nexus 5 Original Android Development] el_smurfo:
My last comment on the topic then you can please report the whole thread and have it cleaned out. I never would have even mentioned freezing issues if I hadn't seen others say the same thing. I have had the issue from the very first clean flash of CAF. I did not ask for anything and have said more than once it's something I can live with and am actively trying to track down the cause on my device (app, setting, etc). Now back to your regularly scheduled "How can I flash CAF" posts.
[Nexus 5 Original Android Development] VQ30DE:
Agreed. There are several of us who have reported freezes and I don't believe any of us has been annoying. This is a development thread and a freeze is a significant issue to report to a developer. I posted a last_kmsg a week or so ago, though I'm not sure anyone looked at it. When I try CAF again I will post full logs if I get more freezes. None of us is complaining or asking to be spoon-fed anything related to the freezing issue--that is just the noobs frequently posting about TWRP or bootloader issues because they can't read.

I think I speak for all of us when I say we appreciate and respect what [MENTION=4152171]myfluxi[/MENTION] has done as device maintainer.

Regarding running unsupported apps/software, I do not run MultiROM or Xposed or anything like that. Almost all the apps I have installed have been updated in the past few months so I would expect them to support Lollipop, but I can't be 100% sure of that. If anyone knows any specific apps or types of apps that are known to cause problems, please advise.