yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Android Development] The_Virus:
Is HDR+ camera working in the 2015/02/28 hammerheadcaf build?

Any other known problems?
[Nexus 5 Android Development] kenshin33:
it should be. and if it's not just edit /system/build.prop (use cm file manager editor or any build.prop editor -plenty of them on the play store) and make sure that 'ro.product.device' is set to 'hammerhead' then reboot.
[Nexus 5 Android Development] fluther:
Works fine for me, didn't need to edit anything. No other problems either. Top stuff!
[Nexus 5 Android Development] NoLimit64:
HDR+ is still not working for me. I'm on the 28th build and tried every workaround suggested here but no HDR+ in google camera.

I'll try re-installing the camera app among a few other things and report back here.
[Nexus 5 Android Development] mo976:
New Build (not CAF) with latest hammerhead kernel stuff merged by fluxi today...

https://www.androidfilehost.com/?fid=95916177934535958
[Nexus 5 Android Development] Matt Devo:
sure I'm missing it somewhere, but where does one enable the sound mode panel on the power menu? I had dirty flashed the 03-01 rom over OptiPop and it was there (and functional), but did a clean install due to the dialer crashing (even after clearing data), and now I can't find it. TIA
[Nexus 5 Android Development] stevae:
disregard...
[Nexus 5 Android Development] maddes1402:
[MENTION=4152171]myfluxi[/MENTION]

Don't know if you read this yet

https://cyngn.com/press/cyanogen-and-qualcomm-collaborate-to-raise-the-bar-on-user-experience

Will we benefit from this decision as well?

Regards, Matt
[Nexus 5 Android Development] mo976:
Probably not... Its really for getting OEM's to use Cyanogen OS on shipped phones and not for the CyanogenMod project. Second its for new or upcoming chipsets and not legacy stuff.
[Nexus 5 Android Development] ast00:
Snapdragon 800 is already legacy? That's pretty sad.
[Nexus 5 Android Development] mo976:
Sure the 820 has just been announced and the 810 is shipping the 805 is six or so months old and the 801 is a refresh of the 800 so legacy...
[Nexus 5 Android Development] raol.xh:
is it possible to remove the carrier logo from lockscreen with this rom?
[Nexus 5 Android Development] ast00:
I get that, but it still makes me sad. Current chips are so powerful and they just keep making them faster and fastest and faster. There is no point. Android is not the most efficient thing ever. If they would take their time to make some changes there, we wouldn't need more than a 400.
[Nexus 5 Android Development] myfluxi:
It won't help us. You can trust me if I say that with the caf builds, we're doing what's technically possible on msm8974. If only LGE responded to my requests and gave us a panel firmware that allowed knock-knock. Until then I'm trying to improve the pick-up gesture (shorten the delay until panel is on to be exact) so we don't need LGE at all. I'll have to bug Steve with this as I failed with my not-so-leet IDA Pro skillz.
[Nexus 5 Android Development] ast00:
So... Is there any chance of we ever getting proper knock on? Without the battery drain?

Maybe I totally misunderstood this, but I hope not.
[Nexus 5 Android Development] mikegapinski:
Yup, but they will not give us the code anyway. #beenheredonethat
[Nexus 5 Android Development] kenshin33:
knock knock as in tap to wake?

I have been trying to convince my self to read this : http://www.synaptics.com/sites/default/files/511-000136-01-Rev-E-RMI4-Interfacing-Guide.pdf for quiet sometime now. would it have been for naught ???
[Nexus 5 Android Development] myfluxi:
This is the world of Synaptics, we had to dig into JDI's.

Are we ready for nightlies? I'd say we were long ago but you know, I'm too shy most of the times :)
[Nexus 5 Android Development] fluther:
Yes please!

When the nightlies do start, will caf be the only hammerhead nightlies, or will hammerheadcaf still be a separate device?
[Nexus 5 Android Development] Hiro Nakamura:
Anyone else got a freeze on hammerhead-caf when you go to display color and click it?
[Nexus 5 Android Development] fleischbanane:
Works here with no problems on today's build.
[Nexus 5 Android Development] Viper LABs:
It does for me sometimes for the first try and always OK for all other tries.

---------- Post added at 01:41 PM ---------- Previous post was at 01:39 PM ----------

Absolutely! Check for the OTA in CMUpdater every day, please let the party begin.
[Nexus 5 Android Development] Hiro Nakamura:
Seems like it always happens on first try on my phone. If you reboot and click on it it freezes. Second time it doesn't.
[Nexus 5 Android Development] aldyu:
Sure, the caf builds are very stable for me.
[Nexus 5 Android Development] nexzor:
tryed it and happened too. So i produced a logcat.

here are my steps:

-unlocked device (on homescreen now)

-attach devic to pc

-start terminal

- start logcat

- pull down statusbar

- pull down quicksettings bar

- enter settings

- display & LED

- Blidschirfarbe (color settings)

- got black screen

- pressed back button

- window "wait for response?"

- no

- settings app killed

- reentered color settings all is fine

- end of logcat

i´m still on 28022015-hammerheadcaf

https://www.dropbox.com/s/uwbbshef30a8vc1/Color_settings.txt?dl=0
[Nexus 5 Android Development] kenshin33:
I was under the impression that the touch thingy is controlled by a Synaptics thingy (according the the IFIXIT tear-down),

ready ? I'd say yes, been using this since the very beginning. No show stopper to report from this part of the world!!

go for it!

PS : a way to get the target files zip ?? for those who want to re-sign everything with their own keys

PPS: on thing to report, it seems to me more of a general problem that device specific : removing something from the admin list crash the phone.
[Nexus 5 Android Development] reas0n:
[MENTION=4152171]myfluxi[/MENTION] What are the parts of the phone encryption in the ROM? Does it need any app, script in .zip of ROM, anything? Because I have a problem with encryption in my ROM, I maybe deleted one app too much or turned off something.
[Nexus 5 Android Development] myfluxi:
What problems and since when?
[Nexus 5 Android Development] mo976:
Updated Build https://www.androidfilehost.com/?fid=95916177934537433 Enjoy!
[Nexus 5 Android Development] reas0n:
http://xdaforums.com/showpost.php?p=59241104&postcount=214

It's probably my fault, that's why i'm asking what are the parts of that function. Is UpdateSetting needed? (I was said, it's just a LG OTA part so I deleted it from building without issues). I also disabled building CM recovery, because it's not needed too.
[Nexus 5 Android Development] myfluxi:
We are using H/W crypt.
[Nexus 5 Android Development] GTI6speed:
Phone boots up for about 30 seconds and then reboots on the latest build.
[Nexus 5 Android Development] reas0n:
so it seems like it could be the F2FS issue, I have the automount for data and cache.. nah.
[Nexus 5 Android Development] mo976:
Which build? And in any case get a logcat.
[Nexus 5 Android Development] Jiggs82:
Its a known issue on most cm based Roms from last night when using a theme , doesn't happen on stock tho
[Nexus 5 Android Development] iPsychoGeek:
Same here with latest 03.05 rom and franco.kernel.

Edit: choosing stock theme resolve the problem.
[Nexus 5 Android Development] Viper LABs:
SOON! - http://review.cyanogenmod.org/#/c/90614/
[Nexus 5 Android Development] prabhu_91:
Merged ??

http://review.cyanogenmod.org/#/c/90614/

Sent from my Nexus 5
[Nexus 5 Android Development] nexzor:
need an official CAF thread

maybe we should think about an official thread now that hammerheadcaf is in the wild.
[MENTION=1035583]mo976[/MENTION] some thime ago you saied maybe you will stop your builds after caf is official. if this is your plan you maybe could rename this thread as the official caf thread, since all important info about it are allready here.

if not some one other has to open a thread, but the problem is it can´t be in de dev-section if it is not a cm-member if i understand correct.

i think [MENTION=4152171]myfluxi[/MENTION] is not willing to maintain this thread, becouse of lagg of time and interest (you told multiple times).

i would maintain such a threads OP, but i not a cm member, so if this would be the case i had to talk to the mods first if its ok to open a thread in dev-section.

i don´t want to push any one in any direktion, but if we don´t get a official thread there will be chaos. new people wouldn´t know where to post bugreports. and in the hammerhead thread it would be verry confusing.
[Nexus 5 Android Development] :
Guys, sorry if I have to bring this up again.. I guess I misunderstood something.

I'm using 'hammerhead' nightlies. When 'hammerheadcaf' appears, will I have to do a clean flash or just dirty-flash?

Thanks in advance for clarification! :)
[Nexus 5 Android Development] rohit25:
Clean
[Nexus 5 Android Development] :
Ah okay, thanks a lot! I guess that's what myfluxi meant by not being able to switch between flavors [emoji14] Will clean-flash and switch to official CAF builds then :) Can't wait to see them!
[Nexus 5 Android Development] mamarley:
I have been able to dirty-flash between CAF and regular. I think the pitfall is that you can't dirty-flash if you have encryption turned on.
[Nexus 5 Android Development] :
Maybe someone can bring us clarification :D Would be important for me. I'm not using encryption though :) Thanks in advance!
[Nexus 5 Android Development] nexzor:
i used the searchtool for you. myfluxi allready answered yopur question. you should first search and than post if the question was not solved:
[Nexus 5 Android Development] :
I know about that post and I know about the search tool.

myfluxi says that the option to switch between hammerhead and hammerheadcaf will be is gone. mamarley says that it's working for him, though. That's what I'm referring to.

Thanks anyways :)
[Nexus 5 Android Development] mamarley:
At the moment it works, but once the official CAF nightlies start, it will stop working (unless you disable the device name check.)
[Nexus 5 Android Development] kenshin33:
you can if you don't have encryption. one potential problem you might encounter is the value of ro.product.device.

try it, if it complain (most probably it will) about not the same device (it will say something resembling this : the zip is for hammerheadcaf not hammerhead), just reboot and edit /system/build.prop (plenty of apps/ways of doing that) change "ro.product.device=hammerhead" to "ro.product.device=hammerheadcaf", reboot into recovery and try flashing again, it shouldn't complain anymore.

as always make a backup before doing anything !!!!!!!!!!!!
[Nexus 5 Android Development] neobuddy89:
And the first official nightly of hammerheadcaf is out!!! Bliss.. :)
[Nexus 5 Android Development] Viper LABs:
Yeahhh!! Congratulations, myfluxi, you are the man!!
[Nexus 5 Android Development] ast00:
Gonna need a kernel for it. I can't live without undervolting.
[Nexus 5 Android Development] neobuddy89:
Tonight (IST), it's time for Chaos... :cool:
[Nexus 5 Android Development] fleischbanane:
Can't flash the official caf build. My recovery tells me it's the wrong device, but I think there is no twrp for "hammerheadcaf".

Shouldn't the device name in the caf build still be "hammerhead"?
[Nexus 5 Android Development] Sly_67:
Pleas read post #2236 [emoji1]

Sent from my Nexus 5
[Nexus 5 Android Development] fleischbanane:
Wanted to try this method but my build.prop already says hammerheadcaf.
[Nexus 5 Android Development] AA1973:
Unmount /system in TWRP.
[Nexus 5 Android Development] fleischbanane:
It's unmounted. :(
[Nexus 5 Android Development] willybarca:
I'm using chaos with f2fs cache/data, if i flash the myfluxi recovery would there be any issues
[Nexus 5 Android Development] Viper LABs:
As a temporary solution, remove first row from updater-script (with command assert) and you're good to go for flashing within any recovery.
[Nexus 5 Android Development] ssauger:
CAF Version install

hope it's ok to post also in this thread.

I was on the latest unofficial CAF from [MENTION=1394147]myf[/MENTION]luxy and got the install error in TWRP and CWM recovery. So i used the recovery he linked on afh here:

https://www.androidfilehost.com/?fid=95916177934537992

and the install is fine. Phone is booting up right now and updating system.

Hope we'll get twrp support back.
[Nexus 5 Android Development] fleischbanane:
This works for me.
[Nexus 5 Android Development] meinnameisthase:
Anybody tried changing from 3G to 4G or 2G on the CAF nightly? Somehow doesn't work, always stays on the old one...

I will do a full wipe and report back with a logcat if it persists...

Gesendet von meinem Nexus 5 CAF mit Tapatalk
[Nexus 5 Android Development] prabhu_91:
Updater script

Can some please upload default/unedited hammerheadcaf updater script of official nightly. i didn't take backup of original while editing.

TIA
[Nexus 5 Android Development] fleischbanane:
Heres a link: https://dl.dropboxusercontent.com/u/19544533/updater-script
[Nexus 5 Android Development] luisangel89:
What is live display?
[Nexus 5 Android Development] salter83:
Live display is similar to this: https://justgetflux.com/
[Nexus 5 Android Development] Sly_67:
Can you tell me where can I find updater-script, and how to remove first line. Pleas step by step. Thanks in advance.

Sent from my Nexus 5
[Nexus 5 Android Development] Tylog:
You can find it in the zip. Extract the zip , Meta-inf/com/Google/android/Updater-Script. To Change the File in Text File and use a Text Editor to edit it. After you changed you need to archive the zip.
[Nexus 5 Android Development] neobuddy89:
myfluxi recovery is CM12 recovery.

CM12 recovery makes me feel like being in stone-age. CWM 2 years back is still better than CM12 recovery.

It's better you update the updater-script (someone posted lately in this topic) :) and flash via TWRP.
[Nexus 5 Android Development] kenshin33:
sorry, my mistake, it seems that this is defined elsewhere too /default.prop in the recovery's initramfs (I just noticed, b/c I did something sometime ago and I forgot about it, that explain why it worked in my case). editing the updater-script / special recovery seem be the only way around it.
[Nexus 5 Android Development] myfluxi:
Sorry about the recovery mess, there is no way around it in CMs infrastructure. I myself prefer TWRP every day and we'll get it as soon as they have the time to add us to the builds. Remember, we're just one device amongst many.

Hack the updater script or use our recovery in the meantime.
[Nexus 5 Android Development] nh5:
Hate to be that guy, but I've been spending months following this thread and the caf stuff and I've came to the following conclusion, there's absolutely no benefit from caf. All this confusion with those who aren't willing to read and the lack of actual benefits that caf provides leads me to ask, myfluxi and cm team, why is development still going in this direction?
[Nexus 5 Android Development] Viper LABs:
nh5, you still have hammerhead WITHOUT caf. So, what the problem? Let others enjoy what they want and need.
[Nexus 5 Android Development] AciDB:
I like it very much! Screen is much much better and subjective feeling is that is much smoother...

Only downside beside recovery is that I cant flash zips for hammerhead and there is no HDR...
[Nexus 5 Android Development] myfluxi:
hammerheadcaf is the very first CM build that does NOT come from an OEM, that's quite an interesting fact. We are the only device that offers a variation of two CM builds, that's fun, isn't it?

Also, the fact that you don't spot the advantages does not mean they're not there. Following your argumentation, none of the custom kernels should exist, neither should any of the CM derivates. Do you want that?

If you don't like it, ignore it (like I do with all the stuff that does not matter to me). Saves you and everybody headaches.

TWRP will be there. The encrypted folks will not be able to flash from /sdcard, though. It's give and take, that's life. Regarding HDR+, is it broken again?
[Nexus 5 Android Development] ssauger:
HDR+ is there on the first official CAF :) [MENTION=4152171]myfluxi[/MENTION] if i use hardwareencryption in future, i have to adb sidload a update? Is this only for TWRP or can we flash directly in CM recovery when the phone is encrypted?
[Nexus 5 Android Development] AciDB:
[MENTION=4152171]myfluxi[/MENTION] broken indeed or i did something wrong
[Nexus 5 Android Development] djsubtronic:
HDR+ is fine on 8th March CAF nightly.
[Nexus 5 Android Development] mshook:
Adb sideload only

If you use hardware encryption, you have to use adb sideload to update whether you use TWRP, CWM or CM recovery (so the whole "download the update" on your phone doesn't make much sense).

Because these recoveries don't know how to read the hardware encrypted partitions.
[Nexus 5 Android Development] AciDB:
So I guess I used wrong gapps or something like that?
[Nexus 5 Android Development] djsubtronic:
Possibly, I use these: http://fitsnugly.euroskank.com/?rom=banks&device=gapps
[Nexus 5 Android Development] ssauger:
Thanks for clarification. And does backup/restore still work when hw encrypted? Or is the hole recovery useless. Thx in advance.
[Nexus 5 Android Development] mshook:
Useless recovery

The recovery is useless simply because you cannot read/write your data partition: it's encrypted... So no, you can't run backup nor restore. What I've used so far (I've always had my N5 encrypted) is Titanium Backup. I regularly pull the backup to my computer using adb pull (and sync it in the cloud).

It's a pain in the butt but then I like the idea of not having much compromised if I lose my phone or it gets stolen.
[Nexus 5 Android Development] myfluxi:
You can use adb backup.

There is a discussion about the security driven approach with CM recovery where no backups should reside on the phone (instead on the connected PC). Many maintainers would prefer the traditional options. If it was my decision, I'd warn the user on Open Source builds but leave the decision whether he'd want to take the "risk" up to him/her.

The OnePlus One is using H/W FDE as well, this should help to get things sorted once they push CM12 nightlies there as well.
[Nexus 5 Android Development] Spinergy02:
Where is the March 8 CAF build? I'm not seeing it in the usual spot.

Edit: Nevermind. Didn't even think to check the official site :)

So while I'm here..is there any way to migrate from caf to aosp without a full wipe? Seems like my favorite custom kernel dev is not going to be pursuing caf anymore.
[Nexus 5 Android Development] d1n0x:
Ninja'd :D
[Nexus 5 Android Development] Spinergy02:
Just installed the Official CAF build for 3/08 and having some issues. So far the device has frozen twice while idle for roughly 10+ minutes each time. Settings crash when first accessing display control, and tweaks to the color saturation have no effect. Also, with the required CM Recovery, Xposed will not flash and instead returns an error that the footer was invalid.
[Nexus 5 Android Development] kong:
So I modified TWRP 2.8.5.2 so its default.prop says “hammerheadcaf” instead of “hammerhead” and was able to flash 3/10 Nightly successfully without editing updater-script…

I uploaded it to MediaFire in case anyone want to give it a try :silly:

I also took the liberty of replacing the curtain with the image in attachment. Hope you don’t mind :p
[Nexus 5 Android Development] nexzor:
i´m on stock CAF 3/08 and have no problem. i think myfluxi would say :"don´t use xposed!"
[Nexus 5 Android Development] tsubus:
[MENTION=4152171]myfluxi[/MENTION] why not add a TARGET_OTA_ASSERT_DEVICE entry in the BoardConfig.mk file? Any side effects caused by adding this?

TARGET_OTA_ASSERT_DEVICE := hammerheadcaf,hammerhead

Would it still not work in recovery?

edit: I tried building the ROM with this line, and it now installs correctly using stock TWRP. So I guess only the initial question remains: any side effect caused by adding the line to the BoardConfig.mk file?
[Nexus 5 Android Development] wintrxtrem:
Why would he say that, because it's still alpha?
[Nexus 5 Android Development] myfluxi:
No, it installs incorrectly, as hammerheadcaf != hammerhead. Read my comments, be patient, don't try to be smarter.

Freezing: You're holding it wrong.

QCOM display control: occasional freezing when accessing first time after boot is a known micro-bug, there is movement in display and I couldn't care less at this point as we don't know what's next.

Xposed: will never be supported, you're all on your own. Every CM maintainer hates it as it produces the weirdest bugs, even memory corruption and kernel panics. It's a nightmare for us but an amazing piece of software regardless, so hats off for the devs but please stay away from me.
[Nexus 5 Android Development] tsubus:
Just for educational purposes, if you don't mind, I have just a question: doesn't adding that line simply add an extra assert to the updater-script? Why do you say it flashes "incorrectly"? The ROM is up and running and all seems ok, what should I be looking for? Thank you if you'll answer.

ps: I did read your previous posts, at least most of them, which is where I got the idea of adding that line (at some point you said to edit the assert in the updater-script as a workaround).
[Nexus 5 Android Development] myfluxi:
We can't hack stuff at CM, it will backfire up to a point where people lose their data, e.g. when encrypted and acting in panic. We don't have to make it fool proof, it's gotta be damn fool proof.

Btw: Interesting fixes for the AOSP kernel so there may be hope for hammerhead, have to check what's useful for -caf (I already added some of the fixes there a while ago because I was sure they're very useful).
[Nexus 5 Android Development] Viper LABs:
Awesome splash screen! As I don't flash any other ROMs instead of CM-CAF, will use it for all future TWRP builds. Thanks!
[Nexus 5 Android Development] mo976:
Ok lets try that again

https://www.androidfilehost.com/?fid=95916177934539580

NO its not 5.1 and as far as I know source has not hit AOSP yet....

and it seems people are still downloading and using my builds (or at the very least download them thinking its caf :p )

Enjoy :D

Correction: Source had already finished being merged to AOSP when I posted this but CM has yet to merge the code...
[Nexus 5 Android Development] fleischbanane:
I can't set an launcher for a second user on my device. Tried it with every official CAF-Nightly, but after choosing it my launcher is not saved but nothing is chosen.

Guest works, but no other user.

Can anybody try and confirm this?
[Nexus 5 Android Development] xrad:
What kind of users do you devs expect, I sometimes ask myself. Clearly the guy is trying to help, improve, contribute. He may be still at the beginning of his learning curve, and his attempts may look feeble to you. But there's no need for insults. SCNR.
[Nexus 5 Android Development] lcrponte:
Not trying to take any side but, where do you see an insult in there anyway? People are becoming too sensitive nowadays...

*Sensitive it is [MENTION=2662301]djsubtronic[/MENTION] :P
[Nexus 5 Android Development] djsubtronic:
*sensitive
[Nexus 5 Android Development] wolfen69:
5.1 is coming soon for CM12! http://www.unlockpwd.com/lollipop-android-5-1-coming-with-the-next-nightly-cyanogenmod-12-1/

Could be available in a day or 2, since they said merging it will be virtually painless. I hope to see Xtra Cherries get it soon, as it's my favorite rom.
[Nexus 5 Android Development] salter83:
*nods* that looks very official. Plenty of well cited sources.

And grammatical mistakes.