yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] Green Daddy:
I am sure it is totally unsupported, but I use the dark GApps package from Dark ROM by [MENTION=5445418]Dark_Eyes_[/MENTION] for my vanilla LOS (CAF): it includes working Google Camera and Pixel launcher and works like a charm for me ;)
[Nexus 5 Original Android Development] Joe Heller:
CAF variant

Are you one of the 50 or so folks using phoval's builds? Is there an XDA forum for those? Or a discussion site somewhere else?
[Nexus 5 Original Android Development] razorloves:
https://xdaforums.com/google-nexus-5/orig-development/rom-lineage-os-14-1-nexus-5-t3528849
[Nexus 5 Original Android Development] ssauger:
Not sure if were only around 50 users, maybe someone build herself or didn't update every day. https://stats.lineageos.org/ hammerheadcaf got around 1300 active installs.

Thanks [MENTION=614507]razorloves[/MENTION] for pointing him to the CAF thread and your amazing work for hh and LOS!
[Nexus 5 Original Android Development] aavvaallooss:
BlueBorne vulnerable

LineageOS 14.1-20170912

https://play.google.com/store/apps/...ector&hl=en&rdid=com.armis.blueborne_detector
[Nexus 5 Original Android Development] ssauger:
Cause Google fixed it in Septemper security patch which isn't applied to LOS yet.
[Nexus 5 Original Android Development] razorloves:
Yeah, google finally released the source code for september security patches about 14 hours ago. So by the time next week's build comes out, it should all be merged into lineage :good:
[Nexus 5 Original Android Development] rolex0815:
But only 7.1.1 MR1 as far as I have seen.

7.1.2 still missing, they did not write it in the corresponding Google group.

https://groups.google.com/forum/m/?hl=en#!forum/android-building
[Nexus 5 Original Android Development] razorloves:
i'm guessing it won't come since the devices on nougat that they support are only on 7.1.1
[Nexus 5 Original Android Development] razorloves:
The september security patches were just merged a few hours ago. :good:

https://review.lineageos.org/#/q/topic:sep2017asb

So the next nightly will reflect that.

The patches for the BlueBorne vulnerability were also merged today. :highfive:

https://review.lineageos.org/#/q/topic:blueborne-N

https://review.lineageos.org/189633
[Nexus 5 Original Android Development] GopalKaul:
Is this the last build? If it is considered ETA for Oreo sorry.
[Nexus 5 Original Android Development] tom0769:
How do you come to this strange conclusion:silly:
[Nexus 5 Original Android Development] GopalKaul:
Because DU declared September patch as the last Android N build.
[Nexus 5 Original Android Development] tom0769:
This is not DU! Wrong thread I'd say:D
[Nexus 5 Original Android Development] rolex0815:
I'm little confused while they abandon 7.1.2 and now only support 7.1.1 ... but who knows. :confused:
[Nexus 5 Original Android Development] razorloves:
7.1.1 was the end of the line for the nexus 6 and 9. So the monthly security updates it gets are 7.1.1.

https://developers.google.com/android/images#volantis

https://developers.google.com/android/images#shamu

But the security updates for those 2 devices ends next month, so google might only do one more for them.

https://support.google.com/nexus/answer/4457705?hl=en#nexus_devices

EDIT: Just wanted to add a note.

Just because google will stop providing patches for nougat, doesn't mean lineage will just give up and stop making nougat roms. Heck, there's people still backporting security patches to cm11 kitkat. lol. https://review.lineageos.org/186931

So, when they start releasing security patches just for oreo, that just means we'll have to backport them. Nothing new. And by "we", i mean anyone in the community that wants to contribute. Doesn't have to be a lineage dev. :good:
[Nexus 5 Original Android Development] GopalKaul:
Ok thanks boss! Love your work!!! Keep it on! But can new security patches be added to Android N? Or we need Android O?
[Nexus 5 Original Android Development] abhishek_jadav:
What about los theme engine :confused:
[Nexus 5 Original Android Development] GopalKaul:
CMTE died:crying:
[Nexus 5 Original Android Development] manojks256:
Could anyone let me know whether Device Encryption working fine or not, I mean is it supporting?

~Thanks.
[Nexus 5 Original Android Development] cheeze.keyk:
"So, when they start releasing security patches just for oreo, that just means we'll have to backport them. Nothing new."
[Nexus 5 Original Android Development] GopalKaul:
New for me
[Nexus 5 Original Android Development] manojks256:
Device encryption working?
[Nexus 5 Original Android Development] henningspruth:
Yes, it works.
[Nexus 5 Original Android Development] manojks256:
Thanks:good:
[Nexus 5 Original Android Development] frutex82:
Lineage os 14.1 on nexus 5 sim without signal

hello, i have the latest version of the lineage os on my nexus 5. The problem is that it detects sim but it is signalless. I tried to reinstall everything but it did not change. Any solution? thank you

PS: sorry for my bad english
[Nexus 5 Original Android Development] manojks256:
Any idea how to disable apps from startup?
[Nexus 5 Original Android Development] dodjob:
Hey there, I'm on Los 14.1 (last nightly)+ blusparks 141. When Bluetooth is connected to my boombox, the whole system become laggy and specially the wifi connection start to be very unreliable (is connected but no internet in app and/or simply disconnect from wifi and goes 4g) does anyone have the same behavior? Regards, doh!
[Nexus 5 Original Android Development] mooiemeneer:
19092017 nightly first boot

This one takes a looooong time for its first boot. No further remarks, so thank you razorloves!
[Nexus 5 Original Android Development] pluto123:
It depends on the app, but if it's possible then with the privacy guard ("run in background", "start at boot", etc.)
[Nexus 5 Original Android Development] tseeling:
older AOSP branches still receive security patches

Google stops *building* images and sending out updates to some devices.

But: they still develop the security patches and merge them into all (still) supported branches on AOSP.

Afaik Google pushes updates as far back as KitKat 4.4.

So if you *wanted* to build a 4.4 ROM it would still be current regarding security (as far as is possible where architecture changes happened etc.).

I still don't understand why they switch off the automatic build for abandoned devices.

It's ok to freeze the version and not release 7 or 8 for the older devices as long as security patches continue.

I'd have loved to stay on vanilla Android with my Nexus 5 and I don't think it's done because of lack of disk space.

Getting security patches is essential in this world today and if people have to stay on 6.0.1 on the Nexus 5 that's ok if security patches still roll.

Just my $0.02.
[Nexus 5 Original Android Development] Alex-V:
Hello,

Only one question..will the normal gapps pack work or not..?

I will get the nexus 5 tomorrow as it’s really cheap atm and I like to be back..so at the beginning i still wanted to be flash a good rom and don’t want to bootloop ??*♂️?
[Nexus 5 Original Android Development] razorloves:
no. that's wrong info. besides, his question was about something I said and I already answered him in a previous post.
[Nexus 5 Original Android Development] GopalKaul:
The ARM variant will.
[Nexus 5 Original Android Development] tseeling:
what exactly do you mean with "that's wrong info"?

Reading the Google Android Security Bulletings (e.g. https://source.android.com/security/bulletin/) it is my understanding that Google currently delivers fixes for older Android versions. Do you have a reliable source that says otherwise?

The sep 2017 security bulletin explicitly states that AOSP is updated for a lot of old versions.

CVE-2017-0752	A-62196835 [2]	EoP	High	4.4.4, 5.0.2, 5.1.1, 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2

I simply complained that Google stops providing official image builds and updates for abandoned devices. Please stop calling my statements "wrong" so generically.
[Nexus 5 Original Android Development] joha386:
Hi there - been using this ROM for quiet some time now - but I am experiencing some weird behavior with my N5. Maybe some of you know whats happening:

It seems like every time the phone goes to sleep mode, the phone becomes unresponsive and the only thing left is pressing the power button for a while to hard reboot it. I have a new battery, also the power button is working like its supposed to.

I fixed the problem by installing the app "SOD Killer" which was originally meant for the Nexus 4 and creates a wakelock, so the phone does not enter sleep mode. This fixes the problem for now. Does anyone have any idea what might be causing that strange behavior? Same is happening with the last factory image released by google and I also tried different kernels.

Any ideas are hugely appreciated.
[Nexus 5 Original Android Development] razorloves:
yes. the source code. https://android.googlesource.com

if it's happening on stock then it's not a problem with lineage rom.

sounds like hardware issue, but this is the wrong place to ask.
[Nexus 5 Original Android Development] lukss12:
You can enter in kernel/msm repo and clearly see that the last commit for hammerhead-marshmallow-mr2 branch was about 1 year ago.

The CVEs you are referring are platform level vulnerabilities, as platform code is shared (usually with some vendors modifications) between every device running the same android version, just fixing the problem in some branches of the repo (4.4 branch... 5.0.2 branch, etc) will fix the bug in virtually every device as more than 95% percent of devices run 4.4+ (of course exists the need of the vendor to build again and distribute the update).

Now when talking about kernel vulnerabilities it is different, the patch must be done per device (devices like hammerhead an bullhead share the same kernel/msm base code but the patches cannot be applied equally to both branches) and per android version. Google is not wasting time in fixing kernels for "forgotten" devices. This is the place where nice people like [MENTION=614507]razorloves[/MENTION] with a great understanding of linux-android kernel digg into commits from newer devices kernel branches and "backport"-"cherrypick" (wathever you like to call it).

I hope you understand why razor said you where wrong, don't need to hesitate... May be the man was in a hurry or just had a bad day. But it's necesaary to state when some info is wrong to prevent spreading.
[Nexus 5 Original Android Development] Yotoprules:
Trying to install this in multirom failed with Error: 7

Not sure what's up
[Nexus 5 Original Android Development] TioCareca:
Did you use data slot? Try to install in twrp...
[Nexus 5 Original Android Development] Yotoprules:
Not sure what you mean by this. I booted into twrp, selected multirom, add ROM, and attempted to flash the lineageos zip file
[Nexus 5 Original Android Development] tseeling:
thanks for the clarification, it wasn't clear to me that there's a distinction between Android and kernel fixes in AOSP.
[Nexus 5 Original Android Development] TioCareca:
Sorry i was talking about other dual boot app...

Efidroid (https://xdaforums.com/google-nexus-5/development/multiboot-efidroid-nexus-5-t3580493)

Try this multirom:

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

and this twrp:

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

Your primary rom has kexec-hardboot patch in kernel?
[Nexus 5 Original Android Development] Yotoprules:
Yeah, I've installed sailfish os in multirom no problem
[Nexus 5 Original Android Development] TioCareca:
Maybe bad download?

The links i gave you is a more recent multirom and multiboot twrp, you can try that...
[Nexus 5 Original Android Development] rolex0815:
For my own understanding in other words:

This means they are fixing in the master branch and if this code is used in several Android versions, then all of them affected are listed in the column "Updated AOSP versions", see below.

Is that correct?

I think they are different as hammerhead = 3.4.x kernel and bullhead = 3.10.x

Concerning drivers it's something completely different of course.
[Nexus 5 Original Android Development] Byronbgs:
Nexus 5 will except Open Gapps micro or smaller. Anything else will fail as the file size is too large. I have flashed AOSP, Resurrection Remix, and lineage OS 14.1 all are the same as they will take only micro or smaller.
[Nexus 5 Original Android Development] lukss12:
Not at all, there is a branch for every android version and the fix is merged in them. So that image is saying that the CVE detected in the framework (platform level) has been fixed in latest 4.4 branch, latest 5.0 branch, etc. When you talk about platform level patches like this one they only need to patch those few branches.

Well, kernel patches are far more complex than platform ones. There are a lot of variables you need to analize (kernel version is one of them). That's why Google does not fix kernels for older devices. Sometimes cherrypicking a commit is enough, sometimes you need to rework the patch and sometimes the patch relays in some feature that is not present in an older kernel.
[Nexus 5 Original Android Development] Yotoprules:
I installed it from the play store, I will try that, thanks for the help :)
[Nexus 5 Original Android Development] razorloves:
Wow. System profiles qs tile was added. I know some of you missed that from cm13.

https://review.lineageos.org/184653
[Nexus 5 Original Android Development] Jeeza:
Anybody using this rom with a Miband2?

Does your phone goes to deepsleep, or is it constantly woken up by bluetooth related wakelocks?
[Nexus 5 Original Android Development] dazrok:
Hi,

I've been using this ROM for some time now.

I'm on the latest build 20170919 and having some battery issue, only in this build I see the Android OS and Android system in the battery stats, also they are on the top of my battery usage. Is it normal? If not, is there a fix for it?

Thanks.
[Nexus 5 Original Android Development] shri_chanakya:
Found a bug. Installed this on a phone without sim and setup wizard keeps crashing on start up.

Using the latest build.
[Nexus 5 Original Android Development] tom0769:
Known bug, dev already knows about this.
[Nexus 5 Original Android Development] GopalKaul:
Flash only ROM, boot and restart and flash Gapps. But you cannot restore data backup
[Nexus 5 Original Android Development] razorloves:
There's a bug in lineage rom on all devices that's causing setupwizard to crash if there's no sim installed. We are looking into it.

In the meantime you can use last week's build if you're doing a clean install with no sim card. It will work fine. Then you can update to this week's build no problem.
[Nexus 5 Original Android Development] shri_chanakya:
Thanks all. Found an old sim lying around and popped it in the sim tray and all set now.

Thanks for the help.
[Nexus 5 Original Android Development] razorloves:
New changelog post on our site. https://www.lineageos.org/Changelog-14/
[Nexus 5 Original Android Development] razorloves:
The setupwizard bug mentioned in previous posts has been fixed. :good:

https://review.lineageos.org/191099
[Nexus 5 Original Android Development] Gab92:
Hello everyone

What are radio and bootloader images ?

Should I flash them with TWRP ? And do it after i install lineage OS or before ?

For now I am on stock android 6.0.1 with unlocked bootloader and root acess, and I would like to move on to lineage os with franco kernel.

Can you tell me in which order I should flash ROM, kernel, radio and bootloader ? Thanks in advance !
[Nexus 5 Original Android Development] osm0sis:
Flash bootloader, reboot bootloader, flash radio, then flash whatever else (kernel, recovery, etc.) whenever.
[Nexus 5 Original Android Development] Gab92:
But if I flash bootloader, will it "erase" twrp ? because you are talking about flashing recovery, and well I don't know how to flash ROM and kernel without TWRP, I got my Nexus rooted and with recovery with Nexus Root Toolkit.

Thanks !
[Nexus 5 Original Android Development] GopalKaul:
No. TWRP will be okay and intact.
[Nexus 5 Original Android Development] Gab92:
Thanks again, one last question ! When flashing an image, TWRP give me two options :

"Select partition to flash image :

-Boot

-Recovery"

Which one should I choose ? Many thanks.
[Nexus 5 Original Android Development] GopalKaul:
If a kernel, then boot else if TWRP then recovery..

You can't flash bootloader with TWRP. You need and on a PC
[Nexus 5 Original Android Development] osm0sis:
Neither if you're not flashing a boot (kernel) or recovery image. Bootloaders and radios need to be flashed via fastboot. You can Google and find fastboot instructions quite easily so I suggest you do a bit of reading before you go any further.
[Nexus 5 Original Android Development] Gab92:
Oh ok I saw some things about flashing with adb but last tim I tried didnt work, and with TWRP I actually can flash image, this option are when I want to flash either bootloader or radio. But if you teel me I should not then I will look for this other way via pc.

Thanks for the help.
[Nexus 5 Original Android Development] osm0sis:
TWRP doesn't know the difference, it just knows you named the file with .img as the extension. I hope you understand if you flashed something that isn't a recovery to the recovery partition you'd lose TWRP and have to reflash it with fastboot. Again, you've got some light reading ahead of you.

Don't be afraid of the command line, fastboot is pretty simple and you're better off knowing how to do this stuff without a rootkit.
[Nexus 5 Original Android Development] Gab92:
I don't know much about how it works, I use to do command line for my opo, but when i tried again, it didnt work, but I will do some reading again and try to figure out few things.

Another option in TWRP is flash image in boot, but I guess it doesnt work ?
[Nexus 5 Original Android Development] osm0sis:
Like I said, boot = kernel, recovery = recovery. These are the names of the partitions on the device and correspond to the names of the files in the Google Factory Images (boot.img, recovery.img). This is pretty basic stuff. You should definitely find and read a guide about downloading the Factory Image for a device and how to fastboot the images it contains.
[Nexus 5 Original Android Development] pavik62:
https://nyyu.tk/cm/ From here download bootloader&radio_HHZ20h+2.30 and install through TWRP
[Nexus 5 Original Android Development] osm0sis:
I dunno man, I think you should let him read about it all and learn to fastboot.. he sounds like he's going to brick his device at some point.

"Teach a man to fish", and all that..
[Nexus 5 Original Android Development] abhishek_jadav:
Any news about los15 :confused:
[Nexus 5 Original Android Development] GopalKaul:
No ETAs!!!?:crying::silly::eek:
[Nexus 5 Original Android Development] abhishek_jadav:
#gopal I'm just asking for los15 work start or not I'm not asking for new version or how many days. Very advances ur. When. Asking for new version for fake Nexus build or not that time u telling me not asking for ETS i know it's rules so don't remind me ok and if u don't know what is news than don't reply ok bro.
[Nexus 5 Original Android Development] Xaif:
The work on LineageOS 15 has been started but I don't see any device tree, Kernel for hammerhead. You need to wait for some months to get stable LineageOS 15 for our hammerhead.

The only thing you can do is wait for some months. You can see there is one guy who successfully booted Oreo for Nexus 5.

https://xdaforums.com/google-nexus-...14-1-nexus-5-hammerhead-t3510548/post73538805
[Nexus 5 Original Android Development] manojks256:
Here is the AOSP Oreo thread BTW

https://xdaforums.com/google-nexus-5/orig-development/aosp-oreo-8-0-0-nexus-5-t3664033
[Nexus 5 Original Android Development] Respect!:
O.T. And here the latest build https://xdaforums.com/devdb/project/dl/?id=26855

Respect!
[Nexus 5 Original Android Development] osm0sis:
Speaking of respect, stop posting links to other ROMs.
[Nexus 5 Original Android Development] Respect!:
Pardon.

I added "OT"

Respect!
[Nexus 5 Original Android Development] manojks256:
My phone is encrypted and running LOS 14.1

Can anyone let me know how can I decrypt it, I no longer need it.
[Nexus 5 Original Android Development] pluto123:
Usually factory reset.
[Nexus 5 Original Android Development] razorloves:
no, factory reset doesn't do it. you have to format the data partition.
[Nexus 5 Original Android Development] manojks256:
Actually even that didn't help. I wiped all the partitions and was still asking for decryption pin/pattern on recovery ( data, system, internal storage, cache and dalvik).

Command that helped me - "fastboot erase userdata"

Thanks:svetius:
[Nexus 5 Original Android Development] razorloves:
you picked the wrong options. there is a "format data" button in twrp. that's how you format data in twrp.

the fastboot method you did does the same thing as the "format data" button.
[Nexus 5 Original Android Development] manojks256:
Oh ok Thank you sir :good:
[Nexus 5 Original Android Development] scutworker:
Evening,

I'm going to install this on my phone, but just wanted to ask a quick question:

Does it have the random reboots that used to plague Cyanogenmod?

I used to use it on my old phone and it seemed to happen quite a bit.

And if it does still do it, how often does it happen?

Thanks for any help.

Cheers.
[Nexus 5 Original Android Development] manojks256:
Bro.. this is very much stable ROM. No issues and random reboots.
[Nexus 5 Original Android Development] scutworker:
Magnificent. Thanks for letting me know.

I'll be installing it soon.

Cheers
[Nexus 5 Original Android Development] osm0sis:
Hmm Nougat MultiROM issue in general then, definitely related to the encryption options though from the logcat I logged at, and will likely need to fixed on the ROM side.
[Nexus 5 Original Android Development] MitsG7:
Hey there.

Do you guys use any other kernel for better performance/battery life or you stick with the one from CM?
[Nexus 5 Original Android Development] armando_rod:
Dirty flashed the build from Dec 14, was greeted with an empty dialog "select your SIM card" tapped outside and it went away, all good.
[Nexus 5 Original Android Development] Renton91:
Hello everybody, I'm using the latest version (2016.12.14) with Blu Spark kernel (110).

In LiveDisplay settings, colour calibration and temperature seem not to work (screen colours don't change).

Moreover, with the Prevent accidental wake up feature on, display still turns on both if I tap on the screen or I use the physical button.

Is there someone who can confirm these issues?

I can attach a logcat or anything else if needed.

Besides what I reporterd, ROM works flawlessly (considering that wifi chipset on my Nexus is gone and doesn't work anymore).

Thank you all in advance.
[Nexus 5 Original Android Development] razorloves:
kernel related
[Nexus 5 Original Android Development] Renton91:
Thank you for your prompt reply.

Therefore, both issues are kernel related?

If so, since I like the DT2W, which kernel do you suggest to use without compromising the functioning?
[Nexus 5 Original Android Development] pankajramnani:
I'm unable to update the contacts app from Google Play, it gives me error 505 all the time. It's only with this app though, all other apps update fine.

edit: even the APK doesn't work.
[Nexus 5 Original Android Development] sukhpreet011:
Can you please let me know how you installed Santhosh M's ROM as secondary ROM. I tried with modified update-script but no success, it stays on android logo forever.
[Nexus 5 Original Android Development] antmasi:
Hello, i'm using the lastest nightly 15/12 and the aroma installer of openGapps i'm getting a few random fc's in google camera. Is sombody else experiencing the same?

Enviado do meu Nexus 5 através de Tapatalk
[Nexus 5 Original Android Development] sevis:
I'm getting the same on todays hammerheadcaf nightly. I cannot reproduce it. It happens from time to time on random actions.
[Nexus 5 Original Android Development] numb_:
What version of Google Camera did you use?

4.2 has some problem, 3.2 works great :good: