yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] myfluxi:
Good to see you're still here! It should be ok to allow untrusted apps to access su (that's what app-ops is for), I'll add this later. This should be a CM wide rule, I guess. Add to untrusted_app.te:

allow untrusted_app superuser_device:sock_file rw_file_perms;

This will be removed. AOSP adopted dt2w to their main tree and I wait until it's clear what CM will do about it.

New build later, still with broken cam recording.

Oh man, the 5x is boring and a total joke at its price tag in Europe. I'd prefer the LG G4 over it any time; great and beautiful device.
[Nexus 5 Original Android Development] :
Can't join the technical discussion between you and kenshin33 but I agree with what's written above. Plus I don't like in which direction we're going with device size! Back when I bought my N5 I thought that its 5 inch screen is my personal maximum - and now, around 2 years later, I'm still of the same opinion. I reduced the DPI value and now I can have lots of information on my screen as well. I don't need 6 inches or more... Would you guys prefer a bigger screen? Maybe I'm a bit conservative here... I don't know.
[Nexus 5 Original Android Development] asparaz43:
For me the Nexus 5 as size is perfect and is still very fast, I was tempted to take the 5X for novelty and a larger battery but now the price is too high for what little news that door, so I bought a new battery original for my nexus 5. Excuse my bad English :o
[Nexus 5 Original Android Development] Ajfink:
At the risk of taking this thread too off-topic, I got a 5X to replace my beloved N5, which is still a tinker-toy/backup, obviously. At first I thought I would have to go back to my N5...the vibration on the 5X is goofy, it's a little bigger, it was laggy...

...but I've gotten a little more used to the vibration, the size is okay, and Snapchat is what was causing me lag issues. **** Snapchat.

It's grown on me a lot, but it's not nearly as exciting as the N5 was when it came out, nor as good of a value. It's alright.

BUT

The European prices are insane and I totally get that no one there should want to buy it. The G4 is a sexier, better-looking phone, absolutely.
[Nexus 5 Original Android Development] caliban2:
Haha, same here. New Battery and now waiting for the phones of 2016 with Snapdragon 820.
[Nexus 5 Original Android Development] fleischbanane:
I'm thinking about a new battery for a few weeks now.

Can you recommend any battery and did you changed it by yourself?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] willybarca:
you think European prices are insane, you should see Australian ones, its same price as an iphone 6s, gana stick to my nexus 5, until myfluxi builds caf Roms
[Nexus 5 Original Android Development] caliban2:
After searching the web I got it as a spare part from the official LG-partner in my country. Not cheap (39€...), but seems to be the only way to get an original.
[Nexus 5 Original Android Development] kenshin33:
the privided one caomplained a bout a missig library (the tools from AOSP seems to use oudated libraries/binaries -- so far llvm, flex and audit2allow are broken in one way or an other -- ) so I installed the one provided by portage (gentoo) to try. it gave the above error
[Nexus 5 Original Android Development] myfluxi:
cm-13-20151103-UNOFFICIAL-hammerheadcaf.zip
[Nexus 5 Original Android Development] myfluxi:
source build/envsetup.sh
external/selinux/prebuilts/bin/audit2allow -p out/target/product/hammerheadcaf/root/sepolicy < ~/dmesg.txt > ~/allows.txt
[Nexus 5 Original Android Development] kenshin33:
external/selinux/prebuilts/bin/audit2allow
Traceback (most recent call last):
File "/home/kensan/android/cm-13.0/external/selinux/policycoreutils/audit2allow/audit2allow", line 24, in <module>
import sepolgen.audit as audit
File "/home/kensan/android/cm-13.0/prebuilts/python/linux-x86/2.7.5/lib/python2.7/site-packages/sepolgen/audit.py", line 20, in <module>
import refpolicy
File "/home/kensan/android/cm-13.0/prebuilts/python/linux-x86/2.7.5/lib/python2.7/site-packages/sepolgen/refpolicy.py", line 22, in <module>
import selinux
File "/home/kensan/android/cm-13.0/prebuilts/python/linux-x86/2.7.5/lib/python2.7/site-packages/selinux/__init__.py", line 28, in <module>
_selinux = swig_import_helper()
File "/home/kensan/android/cm-13.0/prebuilts/python/linux-x86/2.7.5/lib/python2.7/site-packages/selinux/__init__.py", line 24, in swig_import_helper
_mod = imp.load_module('_selinux', fp, pathname, description)
ImportError: libpcre.so.3: cannot open shared object file: No such file or directory

but "ln -s libpcre.so.1 libpcre.so.3" in /lib64/ did the trick
[Nexus 5 Original Android Development] myfluxi:
So I'm looking at bullheads (N5X's) kernel history and seriously, there is no way this stuff is teasing me. They made the right choice by going with the 808 chip but qcom's software on top is so boring and Google even disabled the fancy cpu scheduler stuff. Hats off for the LGE and Google dev team regardless, these guys truely know how to do it, so much better than the Motorola team, shamu's bringup was software war and not very convincing.

If you want or have to upgrade, get a G4 and also have a great CM maintainer. I'd even join in there.

cm-13.0 on our trusty N5 has awesome potential, we have all the fancy things already. If we could only get a dt2w panel firmware. We need a petition for LG ;)
[Nexus 5 Original Android Development] asparaz43:
When you have time, let us know where we need to put the signature to the petition ..... I put it on the forum Italian ;)
[Nexus 5 Original Android Development] Ajfink:
Sadly, in the US the G4 doesn't have great unlocked availability. I guess someone could walk into a carrier store and just buy one straight-up, but that can be a pain in itself.

Edit - I mean that there isn't an unbranded, carrier-unlocked version that supports US bands perfectly with all its oddball flavors. We could buy the international version unlocked, but no warranty and without all the bands we'd need.
[Nexus 5 Original Android Development] SedyBenoitPeace:
I was waiting for Nexus 5x to upgrade...but unfortunately it's not what i want...i will stay with my Nexus 5 until i can....with Marshmallow it has a new life (at least for me) then i can't complain, the unique thing that lacks it's dt2w shame on you LG :) and i think that a petition wouldn't change nothing ...can't wait to install CAF CM13...CAF is the perfect rom for me and i really miss it...i will wait when it will be more stable..thanks for your work [MENTION=4152171]myfluxi[/MENTION]
[Nexus 5 Original Android Development] lcrponte:
Aren't you the guy with some inside connections? Do we really need a petition at all? :p
[Nexus 5 Original Android Development] HotBlack77:
Would it be possible to have a separate thread for all the CM 13 stuff, it's getting very confusing when people report errors to figure out if which version they are talking about?
[Nexus 5 Original Android Development] lcrponte:
They shouldn't even report errors with CM13 to begin with.
[Nexus 5 Original Android Development] theodorius123:
:good:
[Nexus 5 Original Android Development] :
I also swapped mine yesterday. It was tricky because 1. the plastic housing clips of the back cover are very robust (be careful while detaching them - there's also one in the middle of the back cover. Don't forget to press on the back of your Nexus after swapping the battery so that this last clip goes back to its right position. Furthermore it was not that easy for me to remove the battery because of the glue. I never imagined it to be that strong :P Anyways, I swapped it and I think it's fine :) Can't say anything about battery life as of now...

I got my battery from spareslg.com and it's definitely not a fake. It looks exactly the same like the one I took out and if I use a battery app to check the temperature it's not stuck at 29°C <- most/all of the fake batteries do!

About the petition for a dt2w panel firmware. I'd be grateful if I could sign and provide the link in this thread and in my signature!

Yeah, they shouldn't report bugs at all. I'm sorry but it's not possible for me to stop it... anyways, I'll rename this project/thread to CM13 as soon as it's official! :)
[Nexus 5 Original Android Development] andrei1015:
Why rename? There should be a new thread.
[Nexus 5 Original Android Development] asparaz43:
Also I have bought from Spareslg, next week it expires guarantee the exchange :)
[Nexus 5 Original Android Development] lcrponte:
Sorry for the offtopic but, I'm definitely considering to replace my battery as most of you already did but... Mind if I ask you, what signs should I look for to understand if I should do it sooner or later?

Is it just battery duration? Temperature or any kind of current measure?
[Nexus 5 Original Android Development] :
Probably you're right. This thread should be kept alive for everyone who wants to stay on CM12.1. Maybe I should create a thread for unofficial builds and rename that one as soon as nightly builds roll out?

Well... I just had the feeling that after two years the battery wasn't that great anymore. I didn't measure anything. Just my personal awareness over the last couple of months...

Anyways - like said before - if you replace your battery, check temperature afterwards. If it's stuck at 29°C you probably bought a fake battery. It should vary depending on how extensive you use the device of course.
[Nexus 5 Original Android Development] :
Thread for CM13-CAF

Okay guys and [MENTION=4152171]myfluxi[/MENTION] -> Here we go with a thread for CM13-CAF. It says UNOFFICIAL in the title until nightly builds on cyanogenmod.org roll out. Hope that's fine with you :)

http://xdaforums.com/google-nexus-5/development/rom-cyanogenmod-13-nexus-5-t3241046

By the way:

- I also updated this thread. For example I now recommend Open GApps for CM12&12.1 (and gapps-mm from TheXorg for CM13).

- I updated the TWRP links in this and the CM13 thread since the official builds aren't updated that frequently. Thanks to Yash98 we have an up-to-date CAF 2.8.7.1 build! :)

If you find any bugs/errors in any of my threads please just tell me :)

Happy flashing!

- experience7
[Nexus 5 Original Android Development] raenye:
Mine just started to die randomly around 30%. And then full charge would finish in 10 minutes. And then it's die again after 30 minutes.

After roughly two weeks it became worse: it died around 65%.

I suspect one cell out of three died, and then a second died.

First replacement battery was not charging, -32 degrees or so; second battery made it as good as new.
[Nexus 5 Original Android Development] myfluxi:
Indeed, 12.1 is now as stable as it gets. Maybe I let some stuff trickle down from 13.0 but I'm not sure if it's worth it, my focus is 100% on M. Get (occasional) nightly snapshots in the other thread, CM is already amazing.
[Nexus 5 Original Android Development] wkwkwk:
Answering my own question, it leaves it as is (twrp can mount /data) and the performance is the same, about 50MB/sec with dd from /dev/zero on 256-512mb file.

Interestingly enough, fstrim no longer works on CAF so I remounted with discard (not sure if it's necessary though).

What kind of write perforce do you guys get with the caf encryption?

---------- Post added at 11:37 PM ---------- Previous post was at 11:34 PM ----------

Is there a 'performance' tab hidden somewhere in settings (there was in OmniROM) near debugging where one can see the wakelocks and also mess around with cpu speeds etc?

Thank you
[Nexus 5 Original Android Development] xdaboobs:
hmm, problem updating to cm-12.1-20151110-NIGHTLY-hammerheadcaf.zip.

Error executing updater binary in zip '/tmp/mr.update.zip'

is this because my bootloader is HHZ12k? and is there a quick way around, like changing the assert(getprop("ro.bootloader") == "HHZ12h" in updater script?

edit: the answer is yes, that is a quick way around :) cool!
[Nexus 5 Original Android Development] amnher:
I am on stock locked android 6.0 right now. If I am flashing this one, the only thing I need to do is unlock bootloader, flash recovery then flash rom then GAPPS? am I right?
[Nexus 5 Original Android Development] Jleeblanch:
I'm gonna just leave this here...

Cyanogen's new C-Apps for 12.1+

https://cyngn.com/c-apps

More info here: http://www.cyanogenmod.org/blog/introducing-the-cyanogen-apps-package
[Nexus 5 Original Android Development] xdaboobs:
it depends.. looks like if you have the new HHZ12k bootloader then you will have to change updater-script like i did :good:

good point yeah.
[Nexus 5 Original Android Development] :
Or downgrade the bootloader. I recommend this one to be honest. Downgrading bootloader has only be done once. If you change updater-script of a nightly, it only will let you install that modified nightly - no updates ._.
[Nexus 5 Original Android Development] Enzious:
My Sprint data patch is included in the latest nightly:

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

See if data is working for you Sprint users! A lot of other ROMs have already been using it.

I've migrated to T-mobile (FYI, LG G4 H811/H815 just got CM12.1/13) so I can't do much more for Sprint devices. Is data working on CM13 so far for Sprint? It may need to be pushed there, too.
[Nexus 5 Original Android Development] dannyella:
Flashed it yet? Any issues? Does it replace pre-installed variants??
[Nexus 5 Original Android Development] crian:
Got no issues. It replaces the dialer and theme apk.

If you want the cm stuff back just wipe system and reflash rom, gapps,...
[Nexus 5 Original Android Development] Dkadr1:
I think this reddit discussion could be interesting for [MENTION=4145479]experience7[/MENTION] and [MENTION=4152171]myfluxi[/MENTION]

https://es.reddit.com/r/cyanogenmod/comments/3sja88/why_there_is_no_caf_of_another_nexus_devices/

Do you have future plans to merge both branches into just one called hammerhead with CAF features?

I think we already know all the benefits of CAF.
[Nexus 5 Original Android Development] myfluxi:
We cannot have a lot of features without an entirely new codebase, hh-aosp basically stopped at July 2013. Google had to rush out hammerhead and left CAFs tree in too many aspects, so there is no sane upgrade path (Steve tried but everybody knows what happened with cm-11.0).

On the other hand, if you can live without the new features, hh-aosp is awesome and LGE sent the best dev team they had that kept it in great shape, even with M. Google still loves the N5, while I'm not so sure if they do with the N6. shamu has most of the features with M though, so there is no point for a -caf build, except you just want the latest bleeding edge base.

I'm a one-man-show on hh-caf and it's more than a handful of work. Every time something goes wrong, I'm ****ed Users are generally not very forgiving. While they pay $$$ on their device, other gadgets and the latest gear in general, they get CM for free and do not see that everybody there (except for the inc. people but including me) is doing it for fun. So much time used or wasted and always something broken and those ignorant comments with a demanding tone, confusing cm and cyngn. hh-aosp is my backup and insurance and keeps me from going insane.

Regarding the "stable" version. There is none, so why call it stable. I can safely say that hh-aosp is totally stable device-wise but L never matured, not Google's, not ours. I can't test the stable branch, I don't have a test team, you are my test team sometimes. Google has one and cyngn should have one. I can't sign up the snapshot version and I wonder how other maintainers do it.

P.S. And to make sure I'm understood clearly: Many great people from cyngn already did an awesome job bringing up M. I love their work and their skill is amazing, CM is really amazing all around.
[Nexus 5 Original Android Development] henk_j:
So why not change/add one word to the topic, the word alpha and "work in progress"? Otherwise there's another sentence that crosses my mind " read first try later..."
[Nexus 5 Original Android Development] Dkadr1:
[MENTION=4152171]myfluxi[/MENTION] So if I understood right, you are keeping the AOSP variant for all those people who are always arguing when something is broken. But your heart is with the hh-caf lol. I suppose your daily driver is the CAF variant.

Maybe you misunderstood the N6 example. What it did intend to say was that as there is only one shamu variant (or one mako, or flo...or any other nexus device), the same should be for Nexus 5. Just one variant with whatever you consider it's best to be included there.

I understand your stress with all these demanding tones. In fact, my only problem with all of these it's just the name. I'm a bit OCD when entering the About device screen and see there that my device is not called "Nexus 5" but "Nexus 5 CAF". Like someone said on the reddit post I feel like I have installed an "abnormal" variant since it's not called just hammerhead.

For a newbie who wants to install CM on his Nexus 5 entering the download page and seeing something called [CAF] next to his device name may confuse him. Instead for any other person with another device without this differentiation they just download their rom and that's all. They don't have to care about what kernel they have. They just enjoy CM and that's all.

I hope you understood my point on this. If you want to promote CAF, maybe merging the two variants it's the best solution. The average person would not notice. I myself would have not noticed if instead of separating the two branches you just kept making the changes you considered were best on the hh build.

I also own a Nexus 7 2013 with CM12.1 installed on it and I still don't have a way to know if it runs on AOSP or CAF. But I don't care because it just works fine and smooth.

Keep on with your hard work man, you are making this device awesome. :good:
[Nexus 5 Original Android Development] Rev4:
Im trying to flash cm 12.1 latest nightly through twrp, but I keep getting this error:

E:Error exectuting update binary in zip ........

im on running latest stock 5.1, can anyone help me I tried everything.

Thnx in advance
[Nexus 5 Original Android Development] Hunter008:
Use twrp for hammerheadcaf
[Nexus 5 Original Android Development] myfluxi:
This is not possible. If you can't stand the CAF thing in the device name, edit your build.prop.
[Nexus 5 Original Android Development] amnher:
Just another question. So when using caf version I need the specific caf version of TWRP. So what will be the significance of the recovery in the download page in get.cm for hammerheadcaf?
[Nexus 5 Original Android Development] Primokorn:
get.cm doesn't provide links to download TWRP but CM Recovery.

You can flash CAF builds with the AOSP TWRP version if you edit some lines in the zip file.
[Nexus 5 Original Android Development] migueldbr:
This is still the best rom for nexus 5 imo...just downgraded from android 6 back to my backup of this rom. It's as smooth as MM and the battery is almost the same. But with all tthe extra functions!
[Nexus 5 Original Android Development] Rev4:
Is it possible to add/turn on call recording. If so how? Thnx in advance!
[Nexus 5 Original Android Development] nexzor:
you can search for this topik in the cm 10 and 11 thread. in some countys it´s not allowed due to lawregulations. so first check your law. but principle the feature is or was implemented in cm by default. you only have to change a falue in the build.prop. but this is only possible if it´s allowed in your country.

otherwise no one on xda will help you and you have to make your owen build. i once did it but it was hell of work to setup a linux machine and the buildserver.
[Nexus 5 Original Android Development] amnher:
So that CM Recovery can or cannot flash CAF builds?
[Nexus 5 Original Android Development] Primokorn:
Yep. That's its main feature.
[Nexus 5 Original Android Development] amnher:
So In short cm recovery from hammerheadcaf download page is not useable for flashing rom from the same page itself?
[Nexus 5 Original Android Development] Fihlvein:
Edit: nevermind.
[Nexus 5 Original Android Development] amnher:
But with cm 12.1?
[Nexus 5 Original Android Development] Fihlvein:
Yeah sorry was in wrong thread, I don't know about that.
[Nexus 5 Original Android Development] Rey0:
If I am currently on Marshmallow MRA58N build, will I be able to install this ROM despite it being on Lollipop 5.1 and for it to work properly?

Also wanted to ask some tips for a newbie on how to do everything properly, thanks in advance.
[Nexus 5 Original Android Development] Primokorn:
In short, you are wrong. CM Recovery allows you to flash ROMs. Anyway I don't see the point of using it since it has limited features for now.

Yes, you can. Learn yourself for the other things. XDA is not a spoon-feeding forum and we are in a dev thread...
[Nexus 5 Original Android Development] lcrponte:
In short, I don't know how did you get to that conclusion but he just said the opposite. You can use hammerheadcaf's CM recovery to flash hammerheadcaf.
[Nexus 5 Original Android Development] playitlouder:
I am getting pretty poor battery life on CM 12.1 CAF.

Mostly when I am on the go. I noticed the modem/radio got much more aggressive in searching for reception than in KitKat days.

Would I break things, if I just flash the 4.4 Modem and test it for a day?

Or jump ship and try CM 13 with its new modem :D (And probably buying a new battery).
[Nexus 5 Original Android Development] :
[MENTION=4038245]playitlouder[/MENTION]: Just test it :) Worst case: You'll be stuck in an endless bootloop. You can use the key combination to boot in bootloader again and flash the proper radio.img.

And for CM-13.0: I'm using the unofficial CAF build from myfluxi and it's already working great! It's definitely a daily driver already. If you want to upgrade be careful because yesterday he uploaded 2 versions. The first one has something like "no pickup" in it's name. This one has working camera. The latest one includes a commit that breaks some functionality regarding saving photos.
[Nexus 5 Original Android Development] playitlouder:
I think my battery is just on its way out. The thing was a replacement phone (original nex5 was from day 1 and the power button gave up), and the battery in it is from 2013. The previous owner could have used it heavily and I own it for half a year now and have drained my Nexus numerous times (because the battery life sucks). ;)

I used to be so impressed by my nexus 5 compared to my S2 in terms of battery life. Nowadays the S2 gets better SOTs than my nexus ;) (CM 11 vs 12.1)

The S2s original battery died when it was less than a year old (had weird percentage glitches, droping a lot, going up again, due to cell voltage stabilizing after heavy loads). And my Nexus has done the same from time to time, but not as drastically.
[Nexus 5 Original Android Development] myfluxi:
cm-13.0-20151124-UNOFFICIAL-hammerheadcaf.zip

Argh, wrong thread. Too many.
[Nexus 5 Original Android Development] wkwkwk:
I found a strange bug in the CAF encryption.

Not sure how I caused it but the steps were:

- encrypt the phone with a PIN

- run: "vdc cryptfs changepw password aaabbbccc". It returns 200 0 -1 so something went wrong.

- reboot, full keyboard appears and password accepted.

- run vdc with pin, same error and only the keypad appears after reboot.

Afterwards I accidentally noticed that any password / pin is accepted as encryption password and the phone boots normally. Twrp won't accept any password but that's expected however, how come android will boot with any password / pin (at least 4 digits)?

It kinda defeats the purpose of encryption.

Thanks
[Nexus 5 Original Android Development] d1n0x:
I noticed that it accepts any pattern/pin, but didn't do any of the fancy stuff you did, just encrypted it normally.
[Nexus 5 Original Android Development] myfluxi:
Fixed just yesterday: http://review.cyanogenmod.org/#/c/121817/

Edit: Try this updated kernel image: https://drive.google.com/file/d/0B4LorYIBlqSSQmJLOXc4V2daX0U/view?usp=sharing

Edit2: This example shows that encryption is basically useless on a rooted device...