yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] xrad:
Yeah I guess I am a bit sensitive. Any no need to take sides of course. But to me it sounded like no way on earth anyone could be any smarter than a CM dev.

I guess it just bothers me that CM keeps bragging about their large community in all of their marketing, while here, on XDA, where the community actually lives, CM reps are rarely seen. Usually with the argument that they can't be bothered with the stupidity of the members. It's on this background in which the words "don't try to be smarter" sounded harsh for me.

Having said that, I decidedly want to stress that myfluxi actually is a very positive exception from the rule. Take it as a memento mori. And sorry for the large OT.
[Nexus 5 Android Development] JulianXhokaxhiu:
Latest CAF nightly installed 8/11 and no HDR+ working on Google Camera. Am I the only one?
[Nexus 5 Android Development] Viper LABs:
Unfortunately, you are one among many, who doesn't want to search and read before asking. HDR+ is here, if you do everything right.
[Nexus 5 Android Development] JulianXhokaxhiu:
You know what's not working on in XDA lately? People like you that judge without even inspecting the context of the question.

It's not the first time I'm here in XDA, you can search about me if you want. My question was more related to this topic:

With the same setup as in my Signature below, I'm wondering why with hammerhead CM12 HDR+ it works, while with CM12 hammerheadcaf it doesn't.

Doesn't matter the kernel (stock or custom, same thing).

I'm using Google Apps Mininal Edition ( normal, no cleaning scripts ) for 5.0 and as before, HDR+ works but only with hammerhead cm12.

Finaly I was asking because I was searching for some kind of collaboration like what kind of logs can I give to inspect this issue. But any hope here on XDA is lost, only few people understand this. The most are exactly judging without even seeing who really the person that's asking is.

If you have any URL to refer me the solution I would be more than pleased to see that, but since I already searched for this and I didn't found nothing, I'm quite sure you'll not find nothing too :)

Kind regards!
[Nexus 5 Android Development] ssauger:
HDR+ is fine on march 10 CAF as you can see on the attached screenshot. So likely its your gapps doesn't work rigth. PA Gapps got a Addon only for Google Camera, try this. http://goo.gl/qYgdXG
[Nexus 5 Android Development] AciDB:
He said that cause I asked the same question and got the answers just few pages ago... :)
[Nexus 5 Android Development] Viper LABs:
JulianXhokaxhiu, this is not judging at all, this is the fact. For what one reason should I track all XDA history of anyone asking a question?? Question is question, no matter who is asking. The same is for an answer.

Your last post is WAY detailed as before, isn't it? That is why you can get more detailed answer. As always, when HDR+ is fine for everyone else, the reason is bad GAPPS package. Try PA GAPPS, they always works as it should.

P.S. You can still go blame XDA or whatever you want, but the real culprit is always inside of the person who is complaining.
[Nexus 5 Android Development] Nnyan:
You've been around awhile so you know you should search first, ask second. I did just that I searched for your in question (in context) and got the answer (multiple times).
[Nexus 5 Android Development] JulianXhokaxhiu:
Ok so, I've tryed what you told to me. I have two Nexus 5 ( one is mine, one is of my girlfriend ). Same configuration, same ROM, same Gapps, etc.

So, I've tryed to install PA Gapps Pico installer + Camera module addon. On my Nexus 5 HDR+ is now appearing (no data wipe, just wipe system, flash the 14/03 CM12, gapps + addon ).

While on the Nexus 5 of my girlfriend is not appearing. There I also wiped everything (system, data, cache, dalvik cache, etc. ) and I flashed everything from scratch ( cm12, gapps, addon ). HDR+ is not coming back again.

Do you have any suggestion about what's happening? Any system file that I can touch or maybe something living in /data ( even If I'm really sceptical about this, I wiped it so how it could have survived? ). Even logs are accepeted (which one?).

Thanks in advice.
[Nexus 5 Android Development] simplicio11:
Me too. Hammerdcaf 3/13 + PA Gapps Full Modular, no HDR+. I've flashed camera addon also, but installation failed (I get error 30 on twrp 2.8.5.2)
[Nexus 5 Android Development] djsubtronic:
Wipe system and cache, then re-flash ROM and try these gapps: http://fitsnugly.euroskank.com/?rom=banks&device=gapps
[Nexus 5 Android Development] mo976:
New regular build https://www.androidfilehost.com/?fid=95916177934541914 and I finally remembered to update the "about phone" screenshot in the first post to one that shows android version 5.0.2 even though 5.1 should be coming to CM sometime sooooooon... I tried pulling down the staging branch but its not fully there yet as far at the qcom stuff goes...

Do not flash the latest bootloader or you may not be able to flash the next build without this pick http://review.cyanogenmod.org/#/c/91276/

also there is a problem with custom kernels and gamma settings on the latest rom that causes the screen to get very dark probably because of this

http://review.cyanogenmod.org/#/c/90978/
[Nexus 5 Android Development] mamarley:
The new bootloader will boot the CAF builds fine, but attempting to flash one in the CM recovery with the new bootloader installed will fail because the version doesn't match.
[Nexus 5 Android Development] fluther:
Encryption weirdness

Hey [MENTION=4152171]myfluxi[/MENTION].

All going well on official caf nightlies, except for one thing:

I'm encrypted, and I like to have a good password at boot, followed by a pin for simple screen unlocking. To do this I've been using an app called cryptfs password from the play store.

However, I noticed this morning that at boot the lockscreen was accepting any four-character string as a valid password. I've tried changing the pin, both with and without setting it to ask for the pin at boot, and I've tried using cryptfs password, which used to work, to change the pin to a password. However, it still always accepts any four characters at boot.

So now I just have it set to a pin, and not to ask for it at boot, because that doesn't seem to work whether I leave it at the pin or change it to a password.

Any idea what's up?

Edit: no logs because I don't know if/which logs would be useful for this.
[Nexus 5 Android Development] kenshin33:
I was, wondering as the last time I tried the encryption was on the galaxy nexus 2 years ago. Does it ask for the password (the decryption one not the lock screen one) at each boot? (I know if there's now PIN/PASSWORD for the lock screen it doesn't ask).

I was thinking about changing the default one ("defaultpassword") in vold source to a very very long, randomly generated one an cripple it in a way that if I change the lock screen PIN/password it doesn't touch it, I wonder if it is a good idea though.
[Nexus 5 Android Development] salter83:
I personally use a password for my lock screen in conjunction with the Smart Lock feature. When you set the password, it'll ask if you want the password to be required upon boot. AFAIK, the password you set here for the lock screen becomes the decrypt key as well. So, if you use PASSWORD as your lock screen pass, and choose for it to be required on boot, you'll have to enter PASSWORD each boot. If you change the decrypt password with cryptfs password, though - (for example, to DECRYPT) each boot, you will have to enter DECRYPT and your lock screen will be PASSWORD. To the best of my knowledge, if you then remove your lock screen password, and then set it back to PASSWORD, and choose to require it upon boot again, I think this also changes the decrypt password back to PASSWORD. Let's go with 75% sure on this... Could be wrong. (I keep the two passwords the same). IMHO, to set the boot password to something really long would be unbelievably cumbersome.
[Nexus 5 Android Development] fluther:
Sounds exactly right to me, including re changing setting a new PASSWORD2 changing DECRYPT to PASSWORD2.

Any ideas why when I try to change the boot pwd, it accepts any four characters as valid?

Also, what are the actual security disadvantages of being encrypted but not requiring anything on boot? If a techno-literate crook nicked my phone, how easy is it to mount /data and /sdcard?
[Nexus 5 Android Development] salter83:
Well, with regards to your four character thing. I have no idea :D

As for being encrypted without requiring the decrypt on boot, if your lock screen was just swipe to unlock, the encryption would be pretty pointless as your data's there for the taking regardless. Assuming a strong lock screen password, and that this also sets the decrypt password on boot to same (without password on boot), I'd say you'd still be fairly safe with regards to recovery abuse as you would still need said password to decrypt /data. If, on the other hand, this doesn't set your decrypt pass to your lock screen pass, and it's a default auto decrypt thing.. then you're screwed. Can't say for sure what way this works as I've never tried it. (You can't decrypt currently with TWRP 2.8.5.2 for hammerhead, and CWM and cyanogen recovery doesn't allow for decryption of storage - afaik). Apologies if this is incoherent. Intoxication is setting in as I type.

Edit: hammerheadcaf*

Oh, sauvigon blanc.. :')
[Nexus 5 Android Development] fluther:
Ha ha.

I'm away for a tenday or so soon, so I don't have time to look into this now. Anxiously awaiting a TWRP update for hammerheadcaf that includes encryption, and for them to fix encryption for flo too.
[Nexus 5 Android Development] salter83:
I wholeheartedly agree :D
[Nexus 5 Android Development] kenshin33:
while the partition is un-encrypted (i.e the device is on and running) he'd need adb. and to have access to adb, one he need to enable --if not already enabled-- second he need unlock the screen and accept the connection for his computer.I was about to say a lot things, but now I see the error of may way. dumping the strings from vold will yield the default password ... I was about to say a lot things, but now I see the error of may way. dumping the strings from vold will yield the default password ...

/sdcard/ is not accessible (MTP) while the screen is locked.

offline (dumping the whole nand one way or the other) might allow that (the password has to be stored somewhere, in the case of requiring it at boot it's in your head, and now I see why hardcoding it is not a good idea, dumping the strings in vold will spit it faster than saying it - lenovo's superfish fiasco comes to mind -)

---------- Post added at 07:23 PM ---------- Previous post was at 07:16 PM ----------

that is with no addition contraption (as the app mentioned in the post I replied to)??

because you see, my beef with encryption (at least the way it used to be pre L), is that it prevents the phone from booting. If it is lost/stolen and for any reason it ls turned off, you kiss it good-bye (no cerberus, no android device manager no nothing, the upside is that the data is safe in a way --is the storage portion encrypted??--)
[Nexus 5 Android Development] salter83:
*nods* storage is encrypted. You kiss it goodbye :)
[Nexus 5 Android Development] myfluxi:
You guys know CAF better than anyone else, would you please try the attached kernel image?

Is overall performance smoother, laggier or just the same as with the regular builds? Please try opening apps, swiping around in apps that are known to be heavy on cpu and gpu. Any difference?
[Nexus 5 Android Development] simplicio11:
I'll try it.
[Nexus 5 Android Development] mamarley:
It won't flash in CM recovery. It says that the signature verification failed and the footer is wrong.

EDIT: I found the hammerheadcaf TWRP and flashed the kernel. Testing now.
[Nexus 5 Android Development] fleischbanane:
Everything works perfect. Can't say if any app opens faster or if it is placebo, but it's definitely not slower!
[Nexus 5 Android Development] kong:
I’d say it’s a little lag compared to the stock CAF kernel but for most of the time it’s unnoticeable… (Facebook, XDA, LINE, Play Store, etc)

However, the Phone dialing animation is somehow seems to be “skipped” on the test kernel. It is smoother on the stock CAF kernel. :fingers-crossed:
[Nexus 5 Android Development] fleischbanane:
I have none of your issues and I noticed that the Tapatalk app opens much faster and I don't have, to reload my pinned threads a few times to see them.
[Nexus 5 Android Development] nexzor:
My impression is that some things like activating GPS inside the menu is significant faster. With stock kernel i klicked on the slider and it tock aprox. 1,5sec till it switched to green.

Now its emediatly. Second thing is that i feel tinder is loding a little bit faster, also Facebook. also it feels that the xda app loads faster.

on the other hand some animations stutter a little bit when they are done the first time. for example if you open Tinder the pulsing Red circle is stuttering when you se it the first tim, after this there is no stuttering.

Also in Facebook when you scroll down. When you start ascrolling it "laggs" for aprox 0,1sec but then is fluid.

But as allways that are only my personal impressions. i´m on the 20150308 build with PA-gapps-pico-20150307. no themes or other modifications
[Nexus 5 Android Development] djsubtronic:
Something really weird happening. After flashing today's nightly (17th March), none of the other files I flash after it seem to do anything. TWRP says it's flashing and complete, but for example none of the Gapps are there? Even doing LS- L from ADB shell right after flashing the Gapps package shows nothing in system/app...

Edit: weirdly, after trying like 5 times it works... weird.
[Nexus 5 Android Development] Viper LABs:
It feels a little bit snappier to me. Apps start quicker, UI is faster in overall. Definitely might be placebo, I wonder if I noticed the difference at all, if there wasn't a spoiler.
[Nexus 5 Android Development] nexzor:
Have a little problem after aprox 8h of running this kernel.

screen switched to a yellowich color. reboot dosn´t solve the problem. will try to install the newest nightly
[Nexus 5 Android Development] myfluxi:
Sunset? Display/LiveDisplay/Display mode and Color temperature Day/Night?
[Nexus 5 Android Development] nexzor:
found the problem! colorcalibration (Farbkalivrierung) was set to green only. Don´t know how this happened.

Didn´t changed anything in settings since the initial install.
[Nexus 5 Android Development] wojwem19:
Hey guys does any of you know when CM team will update cm12 to 5.1 version?
[Nexus 5 Android Development] mmo.xda:
tomorrow at 17:15 EMT :) :) :)

First rule of CM, do not ask for ETAs.

It is unknown. It will be when ready.

So wait and enjoy your rom as it is now :)

Regards
[Nexus 5 Android Development] mo976:
Let me consult my magic 8 ball... as soon as its buildable I will post it here!
[Nexus 5 Android Development] djsubtronic:
CM12.1 is set to be released on May 5th (5.1). Not much longer to go, only about 6 weeks :D

I know this because 5.0 came out on the 0th of May last year.
[Nexus 5 Android Development] Logizar:
Then no more cm for me untill 5.1... Moving on.
[Nexus 5 Android Development] djsubtronic:
It was a joke... just wait for it, nobody knows the ETA.
[Nexus 5 Android Development] mo976:
I tried to make a test build on the staging branch but its not even there yet, probably sometime next week I think. Nightlys are probably a few weeks out at least.
[Nexus 5 Android Development] mamarley:
So, I have been running that test kernel that [MENTION=4152171]myfluxi[/MENTION] posted for a couple days now and have had significantly worse-than-usual (by a factor of about 2) battery life. Normally when I leave work, my phone is at about 95%. With this kernel, it has been at 89% both days. Has anyone else had any similar experiences?
[Nexus 5 Android Development] myfluxi:
Great feedback on the test kernel image, some of it is random but still. Sorry for being vague, I didn't want to bias you.

Basically, I tuned down various cpufreq parameters because my feeling is, we're using a lot of stuff that came from CAF because the interactive governor was broken (and it still sucks on Google AOSP - not our CM AOSP variant). Also, it appears certain other devices have problems which the maintainers try to compensate for by upping cpu power, keeping cores plugged and such. I can even go further and disable more stuff.

On the other hand, if somebody switches over to CM (both flavors) it shouldn't be a lag-fest. So the balance between optimum cpu (and thus energy) usage is really tricky.
[Nexus 5 Android Development] mamarley:
I thought I had noticed that Firefox might be a bit slower/jerkier, but I wasn't sure, so I didn't say anything before.
[Nexus 5 Android Development] mo976:
Here a new build https://www.androidfilehost.com/?fid=95916177934545538 still no CM12.1 unfortunately attempting to build resulted in 'no permission to make hammerhead kernel...' errors just going to have to wait for things to get sorted out but I will keep trying.

I will update the changelog later but the cherry picks are more or less the same.
[Nexus 5 Android Development] iammuze:
Well, in preparation for 12.1 at least, I've finally gotten around to updating the flashable zip to install the radio and bootloader from 5.1/LMY47D. That's radio-hammerhead-m8974a-2.0.50.2.25 and bootloader-hammerhead-hhz12f.

My XDA post is here and this is the download link. The file is currently hosted on my Google Drive, so if you'd be kind enough to upload it to your AFH account again my bandwidth limit would certainly appreciate it.

Anybody who uses this, please let me know if you have any issues. You shouldn't, but one never knows.

Thanks!
[Nexus 5 Android Development] mo976:
There is an issue with installing CM12 ROMs once the boatloader is updated. The updater script needs to be edited otherwise the install fails.
[Nexus 5 Android Development] iammuze:
Ohh that's right, because CM does a version check for the bootloader, ugh. So until it actually is 12.1... well shoot. I guess I should put the old one back up on my post. Oh well, at least I'm prepared...
[Nexus 5 Android Development] archish:
Does the LiveDisplay Automatic mode work? It never seems to control the color during night. Am I missing anything?
[Nexus 5 Android Development] vpraveenis:
[MENTION=1035583]mo976[/MENTION] There are unofficial 12.1 builds starting to pop-up for a couple of devices. Very early builds with quite a few issues though. But it is bootable. One of them here with build instructions too One Plus One thread.

So it looks like the frameworks part is compilable. Are you facing problems with the kernel repository?
[Nexus 5 Android Development] wintrxtrem:
Works for me, but I want to say the color doesn't change until around midnight.
[Nexus 5 Android Development] ssauger:
Don't know what timezone u are, but i thout it changes at 8pm i read somewhere
[Nexus 5 Android Development] wintrxtrem:
EST
[Nexus 5 Android Development] mo976:
Yea I had all the repo's set up in the local manifest, that wasn't the problem now that most everything is in the staging branch.

Correct kernel dependency issues.
[Nexus 5 Android Development] reas0n:
I booted my CAF CM12.1 build but have Setup Wizard FC... ergh.

EDIT: Seems like CyanogenModSetupWizard is broken.

If anyone is brave enough, I'll upload it in few minutes. You will need to delete CyanogenSetupWizard from system/priv-app, for example using TWRP file manager. Also a back button is fugly but i know how to fix it. See u on Vivid thread ;)

EDIT: Testing builds are going here, I already fixed SetupWizard by deleting it: https://www.androidfilehost.com/?w=files&flid=28153

OP: You should maybe try to use cm-12.0 device/kernel, it worked for me.
[Nexus 5 Android Development] mo976:
I thought about that but apparently telephone is not working at least on the first cm12.1 build that's out for the nexus 5.
[Nexus 5 Android Development] reas0n:
lol, so it's the first time when CAF is better than AOSP :D I was talking with my gf and then with my mum, everything is fine :p
[Nexus 5 Android Development] cubandanger05:
Is anyone having issues with the music player not saving the setting to repeat all songs?
[Nexus 5 Android Development] Cubel89:
One question. Wear official CM12 ROM. I can wear this as if it were a Nightly more?
[Nexus 5 Android Development] luisangel89:
I have no clue what the hell you're talking about. Sorry.
[Nexus 5 Android Development] Cubel89:
Sorry for my English. I've Official CM12. I can install this ROM unformatted anything?
[Nexus 5 Android Development] luisangel89:
You should be able to. BUT, do a backup and IF you run into problems do a clean flash.
[Nexus 5 Android Development] Oscarandco:
Hi, sorry for my noob question but I can't install any cm12 rom. I have run on stock 5.1 and I have installed TWRP 2.8.5.3 hammerheadcaf but it's don't work. I have failed message each times..So what I make wrong...?
[Nexus 5 Android Development] Sly_67:
You have wrong bootloader. Script check version of your bootloader. You have 5.1 and it fail to recognized it. Flash 5.0 bootloader and you will be fine. Or install CM 12.1 unofficial CAF. [emoji1]

Sent from my Nexus 5 CAF
[Nexus 5 Android Development] Oscarandco:
Yeah, I try CM12.1 but we can't receive or send message. So I have tried to return on 5.0 before flashing cm12 but it's failed also.

That's what I need help.
[Nexus 5 Android Development] Sly_67:
You have wrong bootloader. Download bootloader for 5.0.x and flash it from TWRP, than install CM 12.

Sent from my Nexus 5 CAF
[Nexus 5 Android Development] mo976:
If you question is can you flash this just like a nightly? yes you can go back and forth with no wiping at all.
[Nexus 5 Android Development] mo976:
New CM12 build https://www.androidfilehost.com/?fid=95916177934547681
[Nexus 5 Android Development] mo976:
CM12.1

This is a full CM12.1 build with myfluxi's kernel for 12.1 along with the proper 12.1 proprietary bits etc, meaning not a hybrid build with bits from AOSP 5.1 or CM12. It seems like at this point a wipe is required between 12 and 12.1, the good news there is no need to flash the new bootloader which would otherwise cause problems when restoring a CM12 backup or simply trying to go back to CM12 and would require reflashing the HHZ12d bootloader first. You can flash the new radio or any radio for that matter will work.

BUGS:

The only bug I noticed at this point is that incoming messages(SMS) cause messaging to crash, and with Google messaging only incoming SMS work, with hangouts it works both ways.

Thanks [MENTION=5047159]Tylog[/MENTION]

Installing apps from unknown sources (side loading) crashes but the app successfully installs.

Thanks [MENTION=4097218]ani55[/MENTION]

Everything else seems good in the short time I have been playing with it.

INSTRUCTIONS:

(tested with TWRP 2.8.5.2)

cm-12.1-20150329-UNOFFICIAL-hammerhead.zip

Latest 5.1 Gapps from banks/euroskank or bring your own!

Wipe system/data/cache use the advanced wipe option rather then standard factory reset!

Happy Flashing!!!
[Nexus 5 Android Development] ani55:
Thanks dev!
[Nexus 5 Android Development] Tylog:
Did you test sms with hangouts mo? From what i know works also.
[Nexus 5 Android Development] mo976:
Works... In the meantime didn't realize my lappy was unplugged and went into standby so had to restart the upload 35% now... and we are live https://www.androidfilehost.com/?fid=95916177934547884 see this previous post for important install information http://xdaforums.com/showthread.php?p=59754404
[Nexus 5 Android Development] Tylog:
Nice, thanks mo , testing :)
[Nexus 5 Android Development] ani55:
I've got to say that it's a very stable build and noticeably faster than cm12, I don't notice memory leak, good job, Mo! The only bug I've encountered is when side loading apks, it causes the package installer to force close but installs the app nevertheless