yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] freitaz:
My problem was happening because I was trying to replace AOSP dialer with Google dialer, both of them works if I keep them side by side but it reboots if I replace it. Any hints? I've checked apk permissions and they are set with 644
[Nexus 5 Original Android Development] Fihlvein:
So far I have not found a way to manually focus a shot, although in video mode touch to focus works. Other than that I'm liking the app so far.
[Nexus 5 Original Android Development] runtime@xda:
Go to Settings-Apps, press Gear button - Default apps and assign Phone app there.
[Nexus 5 Original Android Development] kenshin33:
How to try that ? (here's what I did: I pressed the icon in the tiles, when it asked for where to cast, the chromecast --the acrtual thing-- in the list, and voila, I the screen of my phone on my TV and I took a picture)
[Nexus 5 Original Android Development] banciii:
I am not familiar with Chromecast, I have only a Samsung UE40H6400AW smart TV, which you can choose what kind of source you want to see (like TV, scart, HDMI1-4, DLNA servers etc. or ScreenMirroring). You choose ScreenMirroring and then the TV shows up on your phone's list of devices in the Cast settings and you can connect to it via your Wi-Fi network, just as your Chromecast with (I guess). I tried the same with another Samsung smart TV, with another Nexus 5 and I got the exact same result. Perfect audio cast, but only with a blank green screen. :( And I saw here that other mate got the same bug with a Panasonic smart TV, so it should be a common bug, not device specific. :(:o
[Nexus 5 Original Android Development] wfd:
Hard reboot on 20160111. Last boot reason: tz_err

And my Mi Band stopped to connect with the phone since 20160109 or 20160108 nightly.
[Nexus 5 Original Android Development] kenshin33:
Oh,I see. can't test then, all I have is an old dumb TV :)
[Nexus 5 Original Android Development] luca.giannatiempo:
Up. Nobody checked? [emoji17]

Furthermore I can't find the copy, cut and paste function in the file manager app..

Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
[Nexus 5 Original Android Development] dude_75:
I noticed the issue with the Mi Band too...mine works up until the 20160109 Nightly. I hope they fix it soon :(
[Nexus 5 Original Android Development] paul222008:
is it okay to back-up my whole system january 09 2016 nighty and clean flash january 11 nightly . and restore data in my 01-09-2016 build? because i got bootloop in dirty flash 01-09-2016 build thru 09-11-16 build. sorry bad english
[Nexus 5 Original Android Development] amnher:
hows the Snap Camera right now? is it better than google camerA?
[Nexus 5 Original Android Development] galakanokis:
I cannot get the flash to light up when trying to focus. Annoying when it is dark. Bug? Overlooked?
[Nexus 5 Original Android Development] amnher:
are you using snap?
[Nexus 5 Original Android Development] luca.giannatiempo:
With the today nightly still no contacts app. I had to extract the apk from my friend's nexus with an old nightly and copy it into the system folder..really annoying..why this?

Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
[Nexus 5 Original Android Development] galakanokis:
Sorry, yes, new snap camera. Installed and tested Google camera and it was fine.
[Nexus 5 Original Android Development] ssauger:
It sounds like you used gapps that replace the dialer contacts app with the google one? See if you have in /system/addon.d/ any scripts that remove things like contacts apk. The easiest way is, wipe cache, SYSTEM, and flash again rom and desired gapps. In this way you won't loose your data. Be sure the gapps you use didn't delete the contacts app, i use open gapps from here http://wiki.cyanogenmod.org/w/Google_Apps
[Nexus 5 Original Android Development] luca.giannatiempo:
I've always used opengapps and never had problem. Furthermore I use the aroma package that let me choose which stock app replace or not. Plus, I just flash gapps once, not every time I update a nightly, so when I install the updated nightly I should find that app again..and when I install gapps along with nightly I always perform a SYSTEM wipe..as I always did..what I'm trying to say is that I haven't changed my way of flashing that never gave me problems..

Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
[Nexus 5 Original Android Development] DaLuigi3:
yeahh welcome gello browser :angel:

question:

is the gello browser like caf browser optimized for caf?

thanks
[Nexus 5 Original Android Development] kong:
Flashed 20160112 nIghtly and Contacts app is there... so the problem isn't caused by the ROM for sure.
[Nexus 5 Original Android Development] luca.giannatiempo:
Thank you for check it out. So which gapps do you use? I don't know why..I just do a simple flash as I always did.. Any suggestions?

Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
[Nexus 5 Original Android Development] d1n0x:
It's still the same old green browser in today's nightly...
[Nexus 5 Original Android Development] luca.giannatiempo:
Definitely the culprits are the gapps. I see some remove contacts in the log file but I can't understand why the previous package worked well..anyway why when today I flashed only the update nightly (without gapps) it didn't restore contacts apk?how does the flash works?

Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
[Nexus 5 Original Android Development] d1n0x:
The Gapps update script checks your previous aroma setup and repeats the steps, so you don't have to remove your unwanted apps every time.

Try a clean flash and use a smaller package like Micro or Nano. You can add other apps from the Play Store and remove unwanted ones with something like Titanium Backup.
[Nexus 5 Original Android Development] luca.giannatiempo:
Thanks for replying, I know the scrips checks for previous installation and repeat the steps but the point is that I don't remove any app along with the installation of gapps..so how could it be?in the aroma package there isn't even an option to remove contact.apk..the 25 DEC package didn't create me any problem..i use aroma installer because it's very comfortable and fast and let you choose which gapps install..

Never mind: I just wrote in the aroma gapps thread and the developer told me that there is an error in the script!so they will fix as soon as possible!

Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
[Nexus 5 Original Android Development] djalfy:
I've noticed in the changelog of the next nightly that f2fs support will be added to hammerheadcaf. Does that mean that i won't need to flash an f2fs kernel to get f2fs to work anymore?
[Nexus 5 Original Android Development] fly23:
I have the same problem as on CM12.1 CAF: my LTE is not working. Provider Vodafone Germany.

Phone connects only to H+

edit: ok, I said nothing. 2 min later LTE is connected :)
[Nexus 5 Original Android Development] Dininthedrider:
Do I have to make a clean install in order to try snap camera? After dirty flash, the app does not appear. Thx!
[Nexus 5 Original Android Development] ssauger:
You can dirty flash. Make sure your gapps doesn't delete camera2. When you use gapps with integrated google cam, it is possible that camera2 is deleted per script.
[Nexus 5 Original Android Development] gautam_nexus:
is anyone facing Sys.ui force close issue? i clean flashed the latest nightly i am currently sys.ui force close issue 3-4 times a day.
[Nexus 5 Original Android Development] Dininthedrider:
I see. Then it seem like I misunderstood something. I thought that snapdragon camera will replace camera2. I have camera2 on my device with 0109 nightly.
[Nexus 5 Original Android Development] ssauger:
The new cam was activated after your nightly for caf and aosp hammerhead. Take the latest from today and you will be fine.
[Nexus 5 Original Android Development] szili9992:
Had a random reboot yesterday when i pressed the power button to view an sms that just arrived. I am on the 13. nightly.
[Nexus 5 Original Android Development] dude_75:
I updated to the 20160113 Nightly yesterday and tried the Snap Camera. It looks good, but it seems that the Touch Focus setting doesn't work. No matter to what time I set it, the camera always refocuses within a few seconds. Does anyone have the same issue...?
[Nexus 5 Original Android Development] sumo_31:
I have the same problem staying on 20160108 Nightly. I hope they fix it soon too :(
[Nexus 5 Original Android Development] Ar-Dinthalion:
I have a question, what features/improvements does this ROM have over AOSP CM13?
[Nexus 5 Original Android Development] Primokorn:
Same reply as CM12: http://xdaforums.com/google-nexus-5/help/difference-caf-cyanogen-t3231069
[Nexus 5 Original Android Development] lcrponte:
It has been said (and you know it very well, as well as I do) that CAF is NOT behind in features. If you want to post fact sources, at least correct them or get a truthful source.
[Nexus 5 Original Android Development] Primokorn:
I know since I use it. It was only for general information. He is perfectly capable of using the search or his favorite search engine to find deeper/official information...
[Nexus 5 Original Android Development] RichAggie:
I am currently on CM 12.1, and I've started to have big lag problems. So i was looking for a fresh start on CM 13.

Do I need to update bootloader and radio prior to the update, per the procedure below?

http://xdaforums.com/google-nexus-5/general/nexus5-update-bootloader-radio-lmy47d-5-t3052571
[Nexus 5 Original Android Development] ssauger:
Yes, update youre bootloader and radio. AOSP has bootloader and radio in the ROM file, CAF doesn't. Also for CAF you need a twrp CAF recovery.
[Nexus 5 Original Android Development] RichAggie:
Ok, thanks. So to clarify, if I stick with the AOSP build, I can just just wipe and flash? Manual radio/bootloader update only for the CAF build?
[Nexus 5 Original Android Development] ssauger:
I think its ok when you do so, wipe also system and flash 6.x gapps. Then you dont lost any data.
[Nexus 5 Original Android Development] ninja_rancher:
So I'm new to the Nexus 5 and, as of this morning, new to CAF. I flashed the AOSP first and then found out that there are features that will most likely only be in the CAF variant. One of those features I grew to love from CM 12.1 was Ambient Display. I'm not sure whose "responsibility" it is (base CM or device-specific), so I'll ask anyway and apologize if it's just something that hasn't been done in base CM yet. Coming from CM 12.1 on a Galaxy S4, Ambient Display had further settings under the top-level "Gestures" menu that, among other things, had a setting that used the proximity sensor to trigger Ambient Display when you removed the phone from your pocket (or flipped it from front to back, or waved your hand over the proximity sensor). Any chance of this feature coming to the Nexus 5? Again, if this is a base CM thing, just say so. Thanks.
[Nexus 5 Original Android Development] luca.giannatiempo:
Hey guys, does anybody use xposed on the cm 13 caf?it's the first time I try to use so I don't know very well. In the xposed 3d I couldn't understand if it is already compatible. Could you give me some informations?

Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
[Nexus 5 Original Android Development] minidou-77:
Yes it works fine.

You have to flash it again after each update.

Envoyé de mon Nexus 5 CAF en utilisant Tapatalk
[Nexus 5 Original Android Development] luca.giannatiempo:
Thank you very much. I have to download the files attached in the main 3d of xposed on XDA?how does it works?I just flash from recovery the latest zip for arm7 and install the apk to manage the modules?

Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
[Nexus 5 Original Android Development] Stefano187:
You have to just flash via recovery the zip file of xposed every time you update your nightly. The apk is just to manage modules (activate/deactivate and download/update) and you can install it once.

Here the links

Xposed zip file for recovery

http://xdaforums.com/attachment.php?attachmentid=3580247&d=1450386638

Xposed installer apk

http://xdaforums.com/attachment.php?attachmentid=3383776&d=1435601440

Best regards

Ciao

Stefano

Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
[Nexus 5 Original Android Development] ssirK:
http://review.cyanogenmod.org/#/c/128573/
[Nexus 5 Original Android Development] rogers11:
Oops :(
[Nexus 5 Original Android Development] Stefano187:
This is really sad... Thanks [MENTION=4152171]myfluxi[/MENTION] for your hard work for our device
[Nexus 5 Original Android Development] andrei1015:
Damn. he says he doesn't have the device anymore. And no internet. Does this mean the hammerhead main build will also be dropped?
[Nexus 5 Original Android Development] ssauger:
I also will thank you [MENTION=4152171]myfluxi[/MENTION]

Was great what you did for us. All the best for you!
[Nexus 5 Original Android Development] luca.giannatiempo:
What a shame.. I thanks myfluxi too..please don't leave us..if we can do something to help you come back..please let us know..this is a great ROM..I don't want to leave it :(

Inviato dal mio Nexus 5 CAF utilizzando Tapatalk
[Nexus 5 Original Android Development] asparaz43:
Sad news, thanks for all your great work, I hope we can find a solution :(
[Nexus 5 Original Android Development] mmo.xda:
Dear Marc.

Thank you for your time, endless effort and so many many great things you've done.

You've been the best maintainer a cyanogenmod device could have.

Best regards
[Nexus 5 Original Android Development] tlwhitec:
Too much ETA PMs? Or a different cause? Reading through this forum, I haven't seen much reason to give us the finger, so it has to be something else..?

I was so happy to have you, such a wonderful and communicative maintainer. And then you give up, just a few weeks before the 1st CM13 snapshot :( Well, it must have surely been unbearable.

A big respect for your contribution! [MENTION=4152171]myfluxi[/MENTION], we will always stay grateful that you managed to find enjoyment in such a horrible role :D Please, expect some €€€ as a little thank you for your work, which I surely be enjoying a long time on.
[Nexus 5 Original Android Development] :
hammerheadcaf is my alt device now but it's really stable thanks to you, Marc. Thank you for all your hard work. All the best.
[Nexus 5 Original Android Development] fly23:
I have a bootloop (google logo/off, repeat) if power cable is plugged in. if not, pushing or holding power button does nothing. T

I had CM13caf for 5 days. The devices froze in normal usage and the bootloop began. It varied, sometimes the CM logo showed up. I was able to get to recovery and did wipe data/cache/dalvic (. failed with an error.)

After many reboot cycles recovery stayed alive. I was able to flash CMrecovery and CM13 (nonCAF) rom, the nexus started up, but after 5min the bootloob began again.

50 reboots later the fastboot mode stayed alive and I was able to recover to stock rom with the flash-all.bat. The device run for about 20min, I installed some Apps and now I have the same boot loop, what means exactly:

if power cable connected: boot loop (google logo, off, google logo, off, ...); if i press power+volDown, I see fastboot mode, I have time to push one time up or down, but after 2 sec the device reboots.

This is somehow causes bei die CAF rom. I had already downloaded the nonCAF rom and wanted do flash, but minutes later I got this system freeze and reboot and the problem began. I had these freezes in the 5 days of usage about once a day.

Now it seems that I can't get to fastboot or recovery. I tried it a lot, opened the nexus, dis- and reattached the battery.
[Nexus 5 Original Android Development] amnher:
Too bad. Google is about to end the updates (except security) and now we also loose our maintaner. Does this both affect both caf and non car?
[Nexus 5 Original Android Development] Dininthedrider:
Is it normal that HDR mode is not present in snapdragon camera with latest 0115 nightly build? My wife's elephone trunk with same nighlty cm13 build has HDR.
[Nexus 5 Original Android Development] tlwhitec:
In short, yes it is normal. Features like HDR depend on the capabilities of the chipset, which is likely to be (at least a bit) different for every device. So this always depends on the fact whether the device maintainer managed to make it work for the particular device. It's apparently not the case here.

Also, you might notice that we recently got to know our maintainer gave up on maintaining, probably because of impatient people constantly asking similar questions, while not letting him do the work (man, snapdragon camera is here like a week, you might expect it not to be working right away!). Connect the dots. Now we don't know where this will go. Maybe he'll have a drink and return back to us after the weekend, or someone takes it over, or we'll end up screwed forever. Forget about the camera. Think.
[Nexus 5 Original Android Development] Dininthedrider:
I meant no offense and I had no intention to press on the maintainer. I wanted to ask an innocent question from the community, to find out if my installation is faulty, or this is a known issue and will change during development. I am sorry that I thought that this forum, and forums in general are the place for the community to ask and discuss such topics about the rom dev and device. I won't annoy you with such foolishness anymore [MENTION=5290873]tlwhitec[/MENTION], just please kindly let me know what is this topic for?
[Nexus 5 Original Android Development] tlwhitec:
Hi, sorry to sound maybe a bit rough before, but I suppose you got the picture of the current situation. The air is not entirely clear..

For the topic, as I understand it, it's in the devs section, which should originally serve to get the devs (and public power users willing to test and provide useful reports) together to discuss and solve bugs. Many people are abusing the thread for ETA nagging or babysitting questions, which pollutes the thread and annoys the skilled people a great deal. Especially killing is when someone starts to ask why this/that brand new bleeding feature is already implemented/stable/skinned/polished after a week the world got to know about it :) Such questions from the public become legit only after a much longer period, when the feature becomes more or less stable and thus is expected to work and fail only exceptionally. During the initial stages the devs surely know about every problems you also see. Mind that it's burning enough for them that the feature doesn't work out-of-the-box and they usually try their best in making it work. Even without anyone else's attention.

I know you meant no harm, I suppose this is just not emphasized enough. Penetrating into the environment is hard and takes time. Normally everyone gets over it without a comment. But we're in a bit of a grief now (kinda secretly hoping our dev finds some mercy and return), so.. y'know.
[Nexus 5 Original Android Development] :
A few words to myfluxi...

First of all a huge "THANK YOU!" for everything you did for the Nexus 5. I bought this device back in 2013 when it came out and had a freaking great time with it. Trying ROMs, kernels and stuff like that - that's me. It's like a hobby and I like doing it.

But then one day something stranged happened. CyanogenMod for our beloved hammerhead got a 'little' brother called hammerheadcaf. In the first place I was a bit disappointed that we can't have both - CAF features and 'custom kernel stuff'... but soon I realised that my obsessive ROM/kernel flashing disorder stopped. I realised that CAF provides everything I need. I think I donated one/two times because I was so happy about what was going on :)

Now it seems like hammerheadcaf reached it's end. Let me say this again: It was a good time and I'm still a bit balled up that it's not going to be updated anymore. To be honest - I've seen developers here on xda which have 100k+ "thanks" and claim that their kernel is the best for the Nexus 5 - by all means... I tried. I saw. I left - just to go back to stock hammerheadcaf again :D

Wish you the best!

PS: Please let me know as soon / if you plan to do your magic for another device! And between all those ETA-questions and not-providing-any-logs guys... I just hope you had a fine time here :P

From a happy hammerheadcaf user,

- experience7
[Nexus 5 Original Android Development] Balino:
What device does [MENTION=4152171]myfluxi[/MENTION] have ATM??
[Nexus 5 Original Android Development] ssauger:
Thanks for this fine words. Exactly what is in my mind. Without the loved CAF, hammerhead is a little died at this time.

sent from Nexus5
[Nexus 5 Original Android Development] amnher:
Does that mean both caf and aosp version are now abandoned?
[Nexus 5 Original Android Development] djalfy:
This is very sad news and i want to thank myfluxi for all his hard work. Thanks to him my nexus 5 is the best device i've ever had and will ever have. I know that nobody will ever do such a great job like him but does this really must result in our device being removed from cyanogenmod official support? Can't someone else take over myfluxi's work and keep maintaining the rom for nexus 5? I understand that only hammerheadcaf will be removed from cyanogenmod and i still can have an up to date rom(cm aosp) but hammerheadcaf's features and performance are so great that it's very hard for me to downgrade to cm aosp.
[Nexus 5 Original Android Development] eternal70:
Well, not only me, but all of us are hoping for someone to continue the caf branch. With the n5 is reaching the last official update, the journey after being dropped from aosp official support is always unpredictable [emoji5] Thanks [MENTION=4152171]myfluxi[/MENTION] for all your contribution to hammerhead !!
[Nexus 5 Original Android Development] q1t1:
Same problem for me with a connected object (Chipolo)...

Do you have an idea of which commit broke it?
[Nexus 5 Original Android Development] dude_75:
For me it was the 20160110 Nightly...with the 0109 the Mi Band and the Sony Smartband worked fine and after that the Mi Fit app couldn't find the Band and sometimes the Smartband was disconnected too.

To be honest, I'm thinking about going back to the official Android + root. There are no great benefits by CM13 at this time and a lot of things doesn't work. I know it's a nightly and not a stable version, but there are just a few small drawbacks with the official Android that I can live with. Maybe when there will be a Snapshot of the CM13 then I'll try again :)
[Nexus 5 Original Android Development] sherincal:
Remove HammerheadCAF has been merged, new Hammerhead maintainer appears to be ciwrl.

http://review.cyanogenmod.org/#/c/128830/4/CONTRIBUTORS.mkdn

http://review.cyanogenmod.org/#/q/owner:"Marc+vdW"

I am really sad to see myfluxi and CAF going. CAF was THE most interesting developing going on with our beloved Hammerhead at all. The increased battery life alone was massive (I left my phone playing a 3 and a half hour podcast on youtube while I went to sleep, woke up to 56% of battery). Not to mention the increased performance and so forth. For a Nexus device, Hammerhead has not been too exciting sadly. Maybe it's the age of the cancer that is xposed. And with Layers, less people seem to be inclined to use CM at all.

Right now I don't know what to do with my Nexus 5 anymore. To run CAF until it gets removed from Cyanogenmod updates or go back to AOSP CM, or Cataclysm or...

Thanks - CAF has been a lovely wild ride and with it, Nexus 5 felt better than most newer devices.
[Nexus 5 Original Android Development] djalfy:
But maybe someone will go ahead and also continue maintaining the CAF version as well. If aosp allready has a new maintainer maybe it will take a few days to find one for the CAF CM. If i'm wrong please correct me. I don't know very much about how maintaining a rom works. If Remove HammerheadCAF is merged now can't someone later merge "Add HammerheadCAF" and take control from where myfluxi left? I'm sorry if i'be made any mistakes. :(