yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Long Island NOOBIE:
N5 Build Number M4B30Z

Android security patch level also remained the same at: October 5, 2016.
[Nexus 5 Original Android Development] sanguine8082:
Which vendor.img to use?

Sorry if this is a noob question!

I was following the instructions on the wiki and flashed the latest vendor.img (Factory image for 7.1), and I get the issue about an internal device error. Would you guys kindly point me towards the correct stock image to download and flash the vendor.img from?

Also, having a weird problem with the Setup wizard where it will only let me copy settings from another device, and do nothing else.

Thanks,

EDIT: So sorry, posted on Nexus 5 page haha.
[Nexus 5 Original Android Development] MitsG7:
Hello all,

First of all till now any version i ve flashed is running smooth on my N5.Battery life is very nice,ofc better than stock one,the Nougat UI is really really great,i think the best one till now.but i am facing a problem.Many Gapps keep force closing and i dont know why. For example i cant open Google Photos,Gmail,Keep. I havent had any similar issue with non Google apps. Anyone knows what happening?
[Nexus 5 Original Android Development] gigis50:
Is this happening to anyone else? The user avatar in the upper right corner doesn't show up in lockscreen. It's been like that since i flashed it the first time.

Flashed ROM, Cleared Cache/Dalvik, Flashed Gapps, Restart.

This is the method i use on flashing CM every time Android version changes and had no problems.
[Nexus 5 Original Android Development] rudirahmana:
Where is the CyanogenMod Theme Engine?:(
[Nexus 5 Original Android Development] kissme99:
I saw in changelog some fixes about camera. Can someone confirm, is camera now fully working on this ROM? HDR, videos, etc? Or there are still some problems?
[Nexus 5 Original Android Development] szili9992:
HDR+ not working on Google Camera 4.1+ versions. Everything else is okay. If you want HDR+ downgrade to 3.2 version and untick auto-update for the app in play store.
[Nexus 5 Original Android Development] letsurock:
That patch is supposed to fix green flicker for Google Camera. Stock camera works fine.
[Nexus 5 Original Android Development] sandev9:
did anybody notice panorama mode in cm camera it seems having very low brightness...

i am on nightly20161206.

---------- Post added at 12:06 PM ---------- Previous post was at 12:03 PM ----------

thanks for the beautiful ROM but

panorama mode isn't look good in it i am on nightly20161206.
[Nexus 5 Original Android Development] numb_:
Just dirty flashed 20161208 build and SuperSU 2.78 SR5

It takes about 10 minutes to boot, but all working great! :highfive:
[Nexus 5 Original Android Development] Fumas:
Installed via OTA today's nightly, it take less than 10 minutes, flickering disappeared, blue robot is back in boot animation.

Yesterday i tested maps and it works as usual. Everything ok.
[Nexus 5 Original Android Development] stgaby:
had anyone tried hotspot or usb tethering?

if i make a hotspot it sais error and if i try usb tethering it stops.
[Nexus 5 Original Android Development] sevis:
same here...
[Nexus 5 Original Android Development] stgaby:
ok.. it's good i'm not the only one :))

hope it get's fixed in the next nightly
[Nexus 5 Original Android Development] razorloves:
known issue on all devices with cm14.1

in work https://review.cyanogenmod.org/#/q/topic:cm14-themes+(status:open+OR+status:merged)

Like mentioned couple posts back, the camera fixes were for the video tearing glitch and green screen flickering while video recording with Snap or google camera. So, now google camera 3.2 is fully working good so i recommend you use that. The hdr+ that nexus devices have is not supported in Snap. So that's why it's not there on any nexus devices with cm13 or 14.1.

That issue is happening in multiple device, if not all devices, with cm14.1 in Snap camera. So that's likely to be a bug in snap, which is undergoing a major overhaul right now so should be fixed soon. You can see all the changes and fixes here https://review.cyanogenmod.org/#/q/...android_packages_apps_Snap+branch:cm-14.1-wip

A change in 7.1.1 broke tethering on all devices with cm14.1. I'll have it fixed in the next nightly.

Submitted fix https://review.cyanogenmod.org/175760
[Nexus 5 Original Android Development] stgaby:
nice.

report on the 8.12 nightly:

everything seems to be ok. battery life is ok. google camera works fine (hdr too but on versions below 4.2)

one tiny thing. i tried elementalx 7.06 and it crashed..(google logo bootloop) after flashing the rom back i have problems with the notifications. i was forced to flash clean again the rom + gapps
[Nexus 5 Original Android Development] kissme99:
Sorry, but I don't understand. You wrote that HDR+ works just with Google Camera 3.2. I want to ask you, why doesn't it work with newer version of this app? And, do you plan to fix it?
[Nexus 5 Original Android Development] snives:
Newer versions use a newer API that our driver doesn't have support for. People have been attempting to build a wrapper/work around for it, but I've not seen anything released yet. Unless Qualcomm feels like releasing an update for us, we're likely stuck at 3.2 for good.
[Nexus 5 Original Android Development] tom0769:
When it's done
[Nexus 5 Original Android Development] abhishek_jadav:
thank you :o :good:
[Nexus 5 Original Android Development] idrgw:
Hello, I just wondering why I have problem in initialization after installing gapps aroma packages in the lineageOS?

The device is on the home screen but still loading to load data although I can open settings, and in the setting menu there are no application(s) that must be installed such camera app, google music, etc.
[Nexus 5 Original Android Development] metalfeild:
What's this?
[Nexus 5 Original Android Development] LaserChicken:
This ROM is running nicely. Thank you for your efforts.

I have two N5's, one of which is fully stock. The only benefit of running stock, so far, is the boot time. The stock phone boots much faster, by nearly 25 seconds. It is by no means a deal breaker, but I'm wondering if anyone has any suggestions on how to trim the boot time down a bit.
[Nexus 5 Original Android Development] Tecagaste:
Anyone having trouble with the calendar features in February 13th build? I can't successfully add an exchange server calendar. And the default calendar app is always throwing errors on startup.
[Nexus 5 Original Android Development] razorloves:
The opengapps zips have been deleting the cmsetupwizard for the past few weeks, which is understandable since it's broken.

But now the cmsetupwizard has been completely overhauled and rewritten and renamed to lineagesetupwizard, as you can see here.

It was just completed and merged yesterday, so it will be in the next weekly build that will come in a few days.

The link that you posted shows a new change to opengapps that will delete the lineagesetupwizard. That should not have been done. My guess is, the gapps dev thought that we only renamed cmsetupwizard as part of the rebrand to lineageos, not knowing it was also a complete overhaul. So we contacted the opengapps dev to let him know, and he has made a new change to no longer automatically delete the lineagesetupwizard.

Are you on the newest nightly from a few days ago? i just timed mine and from power on to lock screen it only took 28 seconds total.

clear app data on calendar app, and make sure exchange services app has all permissions
[Nexus 5 Original Android Development] Ysfzone:
Hi,

this ROM is STABLE for Daily Use ?
[Nexus 5 Original Android Development] zappa41:
Yes
[Nexus 5 Original Android Development] gAgNiCk nThViM:
Can't install mini dynamic gapps on 13/02 release

Folks,

I just clean installed lineage-14.1-20170213-nightly-hammerhead-signed.zip but I'm unable to flash Mini_Dynamic_GApps-7.1.x-20170215.zip, any ideas? Using latest twrp ...

Thanks

Nevermind, re-copied files, worked at second attempt.
[Nexus 5 Original Android Development] abhishek_jadav:
Recommended gapps flash open gapps (pico) and dynamic gapps (mini) try

And

Google assistant enable viva any mini gapps.
[Nexus 5 Original Android Development] razorloves:
wat? no
[Nexus 5 Original Android Development] scrack26:
--- apologize for this, wrong thread
[Nexus 5 Original Android Development] Taji34:
Can confirm this ROM MOSTLY works on Sprint (CDMA). It will connect to cellular and received calls and texts. It sometimes will have issues connecting (switching between searching for service and sprint rapidly), but a restart usually fixes that.

The issue, however, is it won't connect to sprint 3G or LTE at all.
[Nexus 5 Original Android Development] PRO>KOMP.<:
Hi, I'm new Nexus 5 user . I install LineageOS 14.1 and when I want to flash OpenGapps ARM>7.1>Mini I got error Low System storage space.

Is this normal or my system partition is different.

Before this ROM I use NetHunter after I wipe:

Dalvik/ART Cache

System

Data

Internal Storage

Cache

And flash stock android. Now I only do "Wipe Factory Reset" and flash LineageOS 14.1

Thanks for help.
[Nexus 5 Original Android Development] ozhan10:
Hey when i use proximity sensor in telegram to hear a voice from top speaker it still comes from bottom speaker pls fix this
[Nexus 5 Original Android Development] idrgw:
Can you explain? Please. I have repartitioning the storage, so I can install aroma package
[Nexus 5 Original Android Development] metalfeild:
Sorry for being nosy and noob, but does this help pass the safetynet/allow snapchat login?
[Nexus 5 Original Android Development] LewisGauss:
Can I ask about the monthly security update, when normally will Lineage get it in a month?
[Nexus 5 Original Android Development] Balino:
2-3 days after google pushes code to aosp
[Nexus 5 Original Android Development] LewisGauss:
Don't think so..The latest nightly build is still running on the January security patches.
[Nexus 5 Original Android Development] razorloves:
No, it's just a security patch from here.

Normally, just a few days, like Balino said. But one of the changes in this month's update is causing rom not to boot up. So that's why it hasn't been done yet.

See comments here for more details.
[Nexus 5 Original Android Development] revik2:
I once did some flashing of those sprint.zip files and I got Data to work but it went away after a few hours.
[Nexus 5 Original Android Development] Rondeau7:
Theme engine

Curious if Lineage will be merging the theme engine into this ROM.
[Nexus 5 Original Android Development] razorloves:
New blog post. :good:

http://lineageos.org/Last-Week-in-LineageOS-2/
[Nexus 5 Original Android Development] szili9992:
You need to create a bug report on Jira. Right now bug reporting is closed but when it's open create a ticket and specify the wrong apn settings and include proof of that and it will get fixed. I don't know exactly when they are accepting bug reports, but I'm sure [MENTION=614507]razorloves[/MENTION] can shed some light on this subject. :)
[Nexus 5 Original Android Development] LewisGauss:
Hi, anybody knows if there is a quick toggle for live display? I would love to be able to toggle the live display between on, off, and auto on the notification quick settings.
[Nexus 5 Original Android Development] Disrupthor:
[MENTION=614507]razorloves[/MENTION] Hello, I have a question, is it possible to enable\force the Wi-Fi driver to use channel bonding (40 MHz) when it is avaliable with the routers? On my tablet I did it just by editing the config file but I guess the N5 uses other radio...
[Nexus 5 Original Android Development] Metalbuster:
Anyone know how to fix the issue that my phone is only "slow charging"? Im using the original cable and adapter and have the stock kernel that came with this rom.
[Nexus 5 Original Android Development] llotech:
So after installing everything form the first post in this thread (bootloader, radio, rom, gapps, su) I get stuck on the first boot where it says it's checking for updates. I'v tried a reset a couple of times but it wont go past this screen. It's been here now for over 20 min. I don't think this is normal, any ideas?
[Nexus 5 Original Android Development] razorloves:
It's charging normally. The 'slow charging' range went up in nougat so older devices will show that.

there's been some changes in the rom and gapps lately that i think are causing some issues with dynamic gapps.

so try with opengapps, http://opengapps.org/?arch=arm&api=7.1&variant=nano

[MENTION=8027548]LeetPirate[/MENTION] on weekends. http://wiki.lineageos.org/bugreport-howto.html

Custom tiles have not been brought up from cm13 yet. It's in work https://review.lineageos.org/156593
[Nexus 5 Original Android Development] llotech:
Thanks, I'm done for the night but I'll give it a try tomorrow.
[Nexus 5 Original Android Development] osm0sis:
With a good enough cord it'll show "Charging".

I actually went through all of my old cords last night with the Current Monitor app and only kept the ones charging at least at 1300 mA or greater, and paired off the optimum cords for my chargers (a really good pairing will get around 1700 mA). :p
[Nexus 5 Original Android Development] fastoy:
https://xdaforums.com/search/thread/3510548?query=slow charging
[Nexus 5 Original Android Development] razorloves:
The max you can get with LG stock charger that came with the phone is around 1200 mA though. Maybe it's ok to use other chargers with higher output, but I wouldn't recommend it.

There is a simple overlay change I could do to lower the threshold levels that determines the text shown on lock screen. Maybe that would be the proper thing to do. I would just add it as an overlay in the device tree. See here. Nougat changed the threshold measurement to microwatts (μW).

Before it was in microamps (μA) as seen here.

Just like this device did here. Except that was adjusted higher, but still a good example.
[Nexus 5 Original Android Development] razorloves:
Ok... in case you all didn't know, there was a problem that was causing 'error 7' on all the new weekly builds that came out today. The builds were canceled and purged before it got to hammerhead though. But the problem has been discovered and fixed. https://review.lineageos.org/162875

New builds are on the way :D https://jenkins.lineageos.org/view/All/job/android/
[Nexus 5 Original Android Development] Bhgprox:
Anyone knows the google default values for the night light and day light? I really thought the default google values on AOSP very good for night and day values. Im currently at 6000K for day and 3500K for night.

Also, is there any way i could change the appearance from my navigation bar?

Thanks a lot. Im in love with Lineage :)
[Nexus 5 Original Android Development] Paolo_lav:
[MENTION=614507]razorloves[/MENTION]

It seems that there are two problems with battery LED configuration:

1. LED shows the color that we have chosen for "battery charged" when battery reach 100% but, in fact, it's not full charged.

2. Battery LED notification is on also when the screen is on, ignoring the proper setting about screen in "Notification light" section.

I don't know if these are device's problems (maybe liblight.so?) or frameworks things, in doubt I report here.

Other than these problems and "Slow charging" graphical thing I can't see any other bug :)

Thank you for your work!
[Nexus 5 Original Android Development] rolex0815:
I'm using this charger since the very beginning (January 2014): Samsung ETA-U90EW Micro-USB Charger 2000 mAh

With that, my N5 charges exactly with the promised 2000 mAh - and therefore a lot faster than with stock LG charger.

Check with

dmesg | grep -i current

during charging.
[Nexus 5 Original Android Development] mbellot:
Unless it's changed in LOS, CM has always gone green (or whatever "fully charged" color you choose) at 90%, not 100%.
[Nexus 5 Original Android Development] Paolo_lav:
I missed the percentage value but the problem is the same :D Based on what you said it seems a precise choice of developers, not device related bug.
[Nexus 5 Original Android Development] ANDROIDRAZRM:
There's no reason you shouldn't use a higher current charger. The battery BMS will control the flow accordingly.
[Nexus 5 Original Android Development] hiemz:
[MENTION=614507]razorloves[/MENTION] when we can download latest build? :D
[Nexus 5 Original Android Development] thelittlesteevee:
Checking on Jenkins, it says it failed. :P So I think they'll try again after they get through the rest of the devices or push it to next week...(hopefully not)
[Nexus 5 Original Android Development] razorloves:
umm, whenever you want. :confused:

Dont know what you're looking at but it hasn't even gotten to h yet, so hammerhead still hasn't been built. It's on g right now so hammerhead will be up in the next hour or so.
[Nexus 5 Original Android Development] thelittlesteevee:
Sorry, thought it failed looking at #927. Was that when they cancelled everything yesterday?
[Nexus 5 Original Android Development] razorloves:
yep
[Nexus 5 Original Android Development] manojks256:
Flashed latest build from OTA, flashing took less than a minute.

Phone stuck in bootloop even after 45 minutes. Looks like there is some problem with latest build.

Tried clearing Cached/DalvikCache didn't help. Any suggestions?
[Nexus 5 Original Android Development] ssauger:
I am a CAF user, but since i noticed that "do not disturb" automatic rule didn't work anymore on builds, i think after 15 february, i did a nandroid and wiped everything. Clean install of AOSP lineage-14.1-20170221-nightly-hammerhead-signed.zip￼ with nano open gapps. All whent fine, Setup wizard after 3-5 minutes i think. So there must be a problem on your side. Maybe try to download it manually https://download.lineageos.org/hammerhead and flash it again.

So i tried automatic do not disturb rule on AOSP version and now it is also broken on this build, last nightly was ok for this szenario.

Back to my CAF nandroid.
[Nexus 5 Original Android Development] planet33:
In settings>account there is only Google account. There is no more WhatsApp account,Gmail account even if they works normally. If I press add account I can add only a google account and I can't delete any other.
[Nexus 5 Original Android Development] szili9992:
It's a problem on your end. Just flashed latest weekly on top of the last build and all went well.
[Nexus 5 Original Android Development] greytroy:
same problem :confused:
[Nexus 5 Original Android Development] amirmt71:
yeap, I have the same problem.
[Nexus 5 Original Android Development] basti314:
Same for me :(
[Nexus 5 Original Android Development] tom0769:
Wow, so much effort just to help out another fellow:good:
[Nexus 5 Original Android Development] spyserk:
I made dirty flash the latest rom over the previous without any issue.
[Nexus 5 Original Android Development] razorloves:
Can all of you provide details. Maybe there's one certain thing causing it. Maybe you all are using encryption? Or f2fs? Or custom kernel? If so, which? And which build were you updating from?
[Nexus 5 Original Android Development] manojks256:
Please let me know how to resolve this issue if you know. Thank you :good:

---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------

I am not using Encryption, not using custom kernals. Using the bootloader and radio mentioned in the OP.

I made a dirty flash from previous version of build (lineage-14.1-20170213) from OTA (Lineage updater)

Thank you :good:
[Nexus 5 Original Android Development] Renton91:
I noticed to have the same problem.

I updated from 13022017 nightly, don't use encryption, neither f2fs, but I use Blu spark kernel, OpenGApps and Magisk.

I flashed all by sideload in this order:

-uninstalled Magisk;

-flashed unSU script;

-wiped cache, dalvik and system;

-sideloaded Lineage, wiped cache/dalvik;

-flashed SUremove add-on;

-sideloaded GApps;

-flashed Magisk, wiped cache/dalvik;

-reboot in recovery;

-sideloaded Blu spark kernel;

-flashed BetterBatteryStats and UKM;

-wiped cache/dalvik;

-reboot.

Is needed any other detail?
[Nexus 5 Original Android Development] greytroy:
the same way, reflash lineage-14.1-20170213 all ok...
[Nexus 5 Original Android Development] Marvi70:
I upgraded from build 20170213. OTA didn't work -> stuck on "patching system image unconditionally".

Downloaded the image manually and installed successfully with adb sideload. Wiped cache/dalvic.

After that setup wizard stopped working and other apps too.

Re-installed gapps and su-addon -> no setup wizard error anymore. But google+, camera and many other apps stopped working. Wiped cache/dalvic -> no success.

Uninstalled and installed the affected apps again. At the moment no issue.

no encryption, no custom kernel, ext4 on data and system, f2fs on cache partition.
[Nexus 5 Original Android Development] rodhull:
I'm affected by this too on 20170221 nightly - OTA updated from the 20170213 nightly. The OTA went fine but I now only have "Google" listed in Settings-Accounts. I have many more functioning on the phone (a few different Exchange, WhatsApp etc.) - I can therefore not modify any existing non-Google accounts and only have the capability to add a new Google account, no other types.

I have nothing fancy - no custom kernels, no encryption, everything stock LOS, just the SU add on. The only apps I regularly use that has root perms is AdAway, nothing fishy from my end to cause this...

Got to be honest, though - I haven't been into the "Accounts" area for a while - this could well have been broken for some time and I wouldn't have realised until seeing this reported here.
[Nexus 5 Original Android Development] HermannSenator:
I can confirm this

Upgraded from 13/2 to 21/2
[Nexus 5 Original Android Development] mooiemeneer:
Same here on 2017021 nightly, coming from 20170213 nightly. No custom kernel or encryption. No problems with installation or boot, Facebook, Whatsapp, working ok but accounts seem to be removed from Settings-Accounts. Google account and Exchange account are the only accounts left. SU add on installed, Open GApps nano, TWRP 3.0.3.0. Apart from cLock apparently not updating since beginning of Nougat, no problems.
[Nexus 5 Original Android Development] Newmanl:
I can confirm this, same issue and for make a point on past builds in fact this area was working ok and I made a manual install as usual
[Nexus 5 Original Android Development] ssauger:
The missing accounts started with changes from 20170216 i think as you can read here in the CAF thread, cause there are unofficial daily builds. I clean flashed the lineage-14.1-20170215-UNOFFICIAL-hammerheadcaf.zip and can confirm that there accounts are listed and can be added, also the do not disturb automatic rules are working on this build.
[Nexus 5 Original Android Development] razorloves:
We already know the problem and have a fix for the accounts issue. No need to report details on that. https://review.lineageos.org/162969

I think some of you got confused. I asked for details on the bootloop problem some people are having, not the accounts issue. thanks
[Nexus 5 Original Android Development] bautrupp:
I also have the account problem which is not device specific. (same on flo (n7 2013))

edit: no bootloop, dirty flashed over last weeks version in twrp. I always flash supersu and franco kernel immediately afterwords.
[Nexus 5 Original Android Development] razorloves:
Here's the fix for that https://review.lineageos.org/162968
[Nexus 5 Original Android Development] hiemz:
i have same problem with the other on the latest build, there no another acount except google acount, i was clean install manually from twrp, use open gapps (couse error setup wizard with dynamic gapps), but every things good and i think battery work good than previous build.

<LineageOS build 21022017 nightly>

i am a junior here please give me easy way if have solution to fix that, thanks
[Nexus 5 Original Android Development] LaserChicken:
Just as a follow-up on the boot speed--the latest OTA seemed to clear up the issue. The phone now boots FASTER than stock by nearly 20 seconds. Amazing.
[Nexus 5 Original Android Development] ANDROIDRAZRM:
The easiest solution is to just wait for the next build, which fixes the problem.