yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] relevant_placeholder:
It's still January 05 build so no.

From build.prop:

ro.build.version.security_patch=2017-01-05

[MENTION=614507]razorloves[/MENTION], don't know if it helps but the build is about 20Mb smaller too, 406 compared to last week's 425.
[Nexus 6P Original Android Development] MazeHei:
Made a Clean install. Works
[Nexus 6P Original Android Development] razorloves:
that's just because we got rid of the cmwallpapers app.
[Nexus 6P Original Android Development] hanschke:
does anyone know why they dont merge the securtiy level?
[Nexus 6P Original Android Development] razorloves:
There's a problem with one of the changes in the February security update. It's causes all devices to bootloop. You can check progress on it here https://review.lineageos.org/#/c/160504/

And see the blog post here http://lineageos.org/Last-Week-in-LineageOS-2/
[Nexus 6P Original Android Development] NingaR:
guys is the update issue fixed??
[Nexus 6P Original Android Development] alexiuss:
not yet...

Enviado desde mi Nexus 6P mediante Tapatalk
[Nexus 6P Original Android Development] razorloves:
Like alexiuss said, not yet. We're working on the issue and will hopefully get new builds going soon. Our sys admin/dev opps has been busy but he just now pulled the bad build for our device, and all the other devices. I'll keep you all up to date on it.
[Nexus 6P Original Android Development] razorloves:
Ok... the problem that was causing 'error 7' on the 20Feb builds 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 6P Original Android Development] the_darkwing_duck:
I just installed the lineage-14.1-20170221-nightly-angler-signed build on my devices.

It all seemed to go OK, except when I try to work through the Setup Wizard, it stops while it is looking for updates. Then restarts back at step 1.

Looks like I may have to revert to stock unless anyone has any good ideas :( ?

Steps I took (with binaries from the first post)

adb push lineage.zip /sdcard/

adb push gapps.zip /sdcard/

fastboot flash bootloader

fastboot reboot bootloader

fastboot flash radio

fastboot reboot bootloader

fastboot flash recovery twrp-3.0.3-0-angler.img

reboot recovery

Install lineage.zip + gapps.zip

reboot bootloader

fastboot flash vendor

reboot system
[Nexus 6P Original Android Development] razorloves:
There's been a lot of new changes to the lineage setupwizard in the rom. It's suppose to work with the google setupwizard that comes with gapps, but maybe there's some issues. I think i heard it doesn't work right with dynamic gapps, so give opengapps a try. If it still doesn't work with opengapps just boot back into twrp and mount system and open the filemanger and delete the LineageSetupWizard folder in /system/priv-app/
[Nexus 6P Original Android Development] nathanchance:
It looks like we'll need to add LineageSetupWizard to our list of conflicting files. We added the CyanogenSetupWizard but either they recently updated or the person who requested it was on an old build :p I'll try to remember to get that in before the next release.
[Nexus 6P Original Android Development] razorloves:
We just finished a major rewrite/overhaul on cmsetupwizard and renamed it to lineagesetupwizard. The first nightlies with it just came out today, so there hasn't been much feedback on it yet. But the little I have heard is that it works fine with opengapps, and a couple complaints that it didn't work right with dynamic gapps. I haven't done any testing yet myself, so don't know details.
[Nexus 6P Original Android Development] NingaR:
I can confirm this, clean installed 20170221 build with Aroma Opengapps didn't face any issue
[Nexus 6P Original Android Development] ArobeeTV:
Did a clean install, but can't get past the setup. Setup Wizard keeps crashing when I try to connect to WiFi. Tried with no network and I get the same issue as well.
[Nexus 6P Original Android Development] peosb:
I had the same issue with 0220 build.

I installed 0212 which has the old setup wizard, went through the setup, and then flashed 0221 on that.
[Nexus 6P Original Android Development] nathanchance:
Will have to dig into it soon then thanks for the heads up
[Nexus 6P Original Android Development] the_darkwing_duck:
:good:

I'll give that a whirl tonight if I get time

:)
[Nexus 6P Original Android Development] razorloves:
That's the wrong thing to do. The old cmsetupwizard is broke af. I already gave you the proper workaround options. Why are you wanting to go another route?
[Nexus 6P Original Android Development] IonutGherman:
[MENTION=614507]razorloves[/MENTION] can you add in Lineage OS tristate location and sync quick tool? It will be great to see this features in Lineage back.
[Nexus 6P Original Android Development] razorloves:
If you're talking about custom quick-settings tiles, that hasn't been brought up from cm13 yet. it's in work here
[Nexus 6P Original Android Development] OhDae-su:
Hi everyone, I'm on the 02/21 build and on my device the do not disturb rules don't work. Additionally I was not able to update the ROM via ota update for the two last two weeks. When I applied the updates the device went to TWRP but only to the main menu. Flashing the ota manually via TWRP brings the corrupt file message. The 02/06 and 01/30 ota worked smoothly.

Coming from 01/23 build, clean install from stock as described in op, dynamic mini gapps, TWRP 3.0.3, no root

Any help would be much appreciated.

Cheers
[Nexus 6P Original Android Development] razorloves:
A fix for dnd is already in work https://review.lineageos.org/162968

And the updater has a known problem that's in work with downloads corrupting. For some people it happens a lot, for others hardly ever. Just have to manually download and flash if you want to avoid it.
[Nexus 6P Original Android Development] S /\ E E D:
Guys, can we use google camera app (from stock ROM) on this ROM?

If yes, please share the apk ...
[Nexus 6P Original Android Development] adame09:
Yes opengapps stock package includes the Google camera.

Apkmirror.com has the APK also.
[Nexus 6P Original Android Development] S /\ E E D:
Thanks, it's better than snap camera :)
[Nexus 6P Original Android Development] adame09:
You can also try this one.

https://xdaforums.com/nexus-6p/themes-apps/mod-camera-nx-v4-google-camera-zsl-hdr-t3494435
[Nexus 6P Original Android Development] Jammol:
Why not just download the official camera app from the play store?
[Nexus 6P Original Android Development] adame09:
It doesn't always show up
[Nexus 6P Original Android Development] Jammol:
Depends on your region. Good place to get your illegal (country wise) app fix on is apkmirror. I go there whenever an app in the store says I can't have it.
[Nexus 6P Original Android Development] adame09:
I'm in the US. Lol

I don't see why it would say this app is unavailable for me.
[Nexus 6P Original Android Development] Jammol:
That is weird!!!
[Nexus 6P Original Android Development] S /\ E E D:
Exactly :)
[Nexus 6P Original Android Development] Jammol:
Which Gapps did you guys flash and has your build.prop been modified for the assistant for example?
[Nexus 6P Original Android Development] S /\ E E D:
Dynamic Gapps

Nope ...
[Nexus 6P Original Android Development] HTC_Phone:
The OP lists the January vendor image, but I noticed on the Lineage blog that February patches have been merged. Is the January vendor still the correct one to use?
[Nexus 6P Original Android Development] Jammol:
Whenever it says there was a merge, it should be that month's patch that states it was merged but I would recommend testing just to be sure.

That is weird, it should allow it in the Play Store. Mine shows up as available for install so I'm not sure what's going on. I also don't have any mods on the device.
[Nexus 6P Original Android Development] S /\ E E D:
Delete
[Nexus 6P Original Android Development] razorloves:
It's pretty obvious to see how active i am in this thread. You think I would make a bunch of changes to the rom and not tell you all and cause everyone to use the wrong vendor image, which would cause everyone to have issues? lol. come on.

Maybe the blog is not worded very clearly, but it doesn't say feb patches were merged. It hasn't been done yet and is still in work. https://xdaforums.com/showpost.php?p=71109946&postcount=1263
[Nexus 6P Original Android Development] netboy3:
The blog does not state that _r21 (February patch) was already merged. The best way to verify if _r21 was already merged is to look at the actual Gerrit change which razorloves was kind enough to mention a few pages back. You'll see that the status is "Blocked on Code-Review Label". This means that a senior developer (Dan) forced a -2 verify on it so it will not accidentally be auto-merged. Once enough positive review credits are given, the update will auto-merge and will show on Gerrit as "Merged".

Edit: [MENTION=614507]razorloves[/MENTION] - sorry for reposting over your response. Didn't see your post.

---------- Post added at 07:40 PM ---------- Previous post was at 07:25 PM ----------

AFAIK, Google removed Google Camera from the general playstore and made it available only to certified Nexus and Pixel devices. From what I know, unlocked Nexi devices do not count as certified (you can see whether you are certified by going to the playstore settings on the phone and scroll all the way down). There's an 11 month old Reddit thread about this.
[Nexus 6P Original Android Development] alexiuss:
It won't show on a normal play store search but you can install it if you bother to find the link...

https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera

Enviado desde mi Nexus 6P mediante Tapatalk
[Nexus 6P Original Android Development] d1n0x:
At this point I think it would be wise to just ditch the February patches and wait until the March sources drop.
[Nexus 6P Original Android Development] netboy3:
I Wish it was that easy, but it doesn't work this way. The _r21 razorloves and myself were chanting about lately are what we call in Git language "tags". Tags are like little stop signs along the timeline of a project branch. This means that changes to a branch are additive and moving forward along the tags will only add more stuff. There's already a _r22 on the AOSP Google repositories and it contains everything _r21 had plus more stuff. If there was a culprit in the _r21 tag that caused issues in Lineage merge then it will still be there in the March tag and will still cause a problem. So the best thing for devs is continue working on merge issues and for us to support them in hope that the issues will be resolved quickly.
[Nexus 6P Original Android Development] d1n0x:
I see. I don't know anything about ROM building and merging, but I did figure that might be too easy lol
[Nexus 6P Original Android Development] razorloves:
The February security update (r21) was finally merged a couple hours ago, so next week's build will have security patch level of 5 Feb 2017. :good:

I've also just updated the kernel and proprietary files with google's N4F26O February security update.

https://github.com/LineageOS/androi...mmit/8b6437939eebe6c7b117ccc48fed6f8f8fdcdcb1

https://github.com/TheMuppets/propr...mmit/cc94f2109731f4b310c057fa504584ba7979ecc1

So, for the next new build that comes out, you'll need the new vendor img from N4F26O. Here's a download link if you want it now so that you have it ready.

I'll update the first post with this info when the new build is available for download.
[Nexus 6P Original Android Development] SergioTeddy:
Do we need a new radio and bootloader also??
[Nexus 6P Original Android Development] d1n0x:
Recommended, but not needed.
[Nexus 6P Original Android Development] razorloves:
The bootloader img is the same as in last month's update, that's linked in the first post. So, if you already have it, then you don't need to flash it. They did something a little odd with the radio img though.

If you noticed on the nexus factory image page, there are 2 different february factory images. NUF26K is for verizon users only and the other, N4F26O, is for everyone else. NUF26K has the same radio version as last month's update (version 03.79). But N4F26O has the same radio version from the december update (version 03.78).

So, only verizon users should use 03.79. They don't need to flash it since everyone should already have it on their device.

But the rest of us should use 03.78, so we need to flash it to downgrade from 03.79.

I'll also update the first post with this info.
[Nexus 6P Original Android Development] wilbarger:
The bootloader is the same as what we are already on. The radio has been reverted to 03.78. Not sure why they reverted back, but I flashed it just to stay in step.
[Nexus 6P Original Android Development] Jxcorex29:
Would the wrong vendor image cause a force close with setup wizard? I've never experienced that before. In fact I have the wrong vendor image on Pure Nexus. I had no issues getting past setup wizard on PN, which leads me to believe having the incorrect vendor causes the issue with the latest Lineage ROM.
[Nexus 6P Original Android Development] Jammol:
For testing VoLTE for Project Fi users.

---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------

OP...Check the OP my friend.
[Nexus 6P Original Android Development] razorloves:
No, that's not the cause. It's happening on several, if not all, devices with the latest lineageos and dynamic gapps.

It's a known issue that was discussed a few pages back, here.

For now, just use opengapps.
[Nexus 6P Original Android Development] Jxcorex29:
You know I've always used opengapps. I'm not sure why I used mini gapps. I guess because of trying something new. What's the current vision of lineageOS. Will CMTE return or is Substratum the new theme engine? I scanned the Clog very briefly, but didn't come across oms commits. I'm going to assume this ROM like so many others has substratum support?
[Nexus 6P Original Android Development] Jammol:
Only Substratum legacy will work. XDA posted an article starting CMTE will not be coming back but we shall see. Sad but if true, at least we can always opt for OMS support I guess.
[Nexus 6P Original Android Development] Jxcorex29:
Correct me if I'm wrong, but there are two Substratum versions? One called legacy the other not quite sure. Can I just download substratum from google play store or do I need to find the latest legacy version from XDA? I would like to edit the substratum themes to my own accord. School is almost done for me, so I have time to tinker.
[Nexus 6P Original Android Development] Jammol:
You can just download it from the play store but please know that it's very very limited in what themes you can apply.
[Nexus 6P Original Android Development] Jxcorex29:
Guess I'll go the custom rom route again....seems like the only options these days are Pure Nexus and Nitrogen. I think I'm going to get the OP3T.
[Nexus 6P Original Android Development] Balino:
Simple aosp is also very good. It's my daily driver and I prefer it over pure nexus
[Nexus 6P Original Android Development] rweddy1:
Adaway issues

Hello I am having issues using ad-away getting error "copying of host file failed!"

I had similar issue with my nexus 6 but cannot remember how to fix, any ideas?

Cheers,
[Nexus 6P Original Android Development] richii0207:
Did it happen on stock with the same root method? Keep in mind this is troubleshooting a 3rd party app that uses root methods that may change depending on installation method.

Best way to troubleshoot:

1) did it occur on stock?

2) any variables added? Root method, app versions

3) user error

There needs to be a sticky thread on how to troubleshoot issues correctly. It would really solve so many of the issues people are having.
[Nexus 6P Original Android Development] rweddy1:
Sorry coming from a 1+3 with system level root, found out I needed a newer version that works with system less root.

Needs to be version 3.2 or higher.
[Nexus 6P Original Android Development] edufur:
I am wanting to try this on my Google Fi phone. I have the latest "O" release. Does this mean I have to roll back to the older vendor and radio to install this rom?
[Nexus 6P Original Android Development] richii0207:
I would wait for tonight's nightly to install since that is based on your vendor.
[Nexus 6P Original Android Development] wilbarger:
You can leave radio as, but the vendor image will need to go back to "J". Or, you can wait till tomorrow and flash the nightly (if it comes out tomorrow) as it will use the "O" vendor image.
[Nexus 6P Original Android Development] razorloves:
New build is available for download. :good:

Remember, this new build is based on the N4F26O Feb security update from google, like I mentioned a couple pages back, here.

The first post is updated with the info and links to the vendor, radio, and bootloader img you need.
[Nexus 6P Original Android Development] kiefferbp:
Are the last two weeklies causing bootloops for anyone else? My phone is stuck on the Lineage OS logo after entering in my encryption password on both the 2/21 and 2/27 weeklies. The 2/12 and earlier weeklies work perfectly.

I am running everything stock, Open Gapps, and no SU zip. Is there any other information I can provide?
[Nexus 6P Original Android Development] edufur:
i am strongly considering installing this rom. i see it is supposed to work with Google Fi. Does anyone else have any issues with that? Also, does this ROM include the Google Assistant? One of the reasons I am thinking about switching is I like the new launcher they use... and I am having issues with my stock NOW feed.
[Nexus 6P Original Android Development] razorloves:
There was a screw up with contacts database upgrade, see here for explanation, and it's causing bootloops for some people. Try this to see if it fixes the bootloop for you.

When you're in twrp and you flash the newest nightly, open the twrp file manager and delete this folder:

/data/data/com.android.providers.contacts

That will delete the corrupt contacts database file and allow your device to boot normally.

NOTE: doing this will erase all your contacts on the device, but as long as you have them synced to your google acct, they will be added back after you bootup and your phone resyncs.

I don't use Fi but I just spoke to a lineage dev the other day that uses it and he said it works fine.

No, it doesn't have Google Assistant. This rom doesn't come with google apps.

Just make sure you read the first post.
[Nexus 6P Original Android Development] IonutGherman:
I didn't had bootloop after update. Lucky me ?
[Nexus 6P Original Android Development] Droid_JD:
Did anyone else lose cm file manager in this latest update?
[Nexus 6P Original Android Development] razorloves:
Yep, the cm filemanager has been retired. You can see the comments here for an explanation https://review.lineageos.org/163484

The "Downloads" app in your app drawer has been renamed to "Files" and some basic file manager functionality was added to it.
[Nexus 6P Original Android Development] hectorviov:
I have a problem where even after disconnecting from a Chromecast it still shows the volume slider. Is this a known issue?
[Nexus 6P Original Android Development] razorloves:
I've been seeing that too. I think it's related to this bug https://jira.lineageos.org/browse/REGRESSION-115
[Nexus 6P Original Android Development] kiefferbp:
Unfortunately my phone is still bootlooping after following these steps with the 2/27 nightly. I'll post my console-ramoops file in my moment.
[Nexus 6P Original Android Development] Kewbla:
I had 4 of then in my sound bar last week. Just thought it was a one off thing tho.
[Nexus 6P Original Android Development] razorloves:
I finally got a chance to look into the problem of setupwizard crashing with dynamic gapps on any devices with lineage rom. It was caused by lineagesetupwizard (big surprise right. lol). I'll explain...

Here's the important error:

That was causing the packagemanager to deny certain permissions to the google setupwizard.

And that was causing this error, which crashed google setupwizard

The reason this is not happening on opengapps is because they are using 7.0/sdk24 setupwizard apk, which doesn't require that UPDATE_LOCK_TASK_PACKAGES permission. And, as you know, your gapps is using 7.1/sdk25 setupwizard apk. It is just our luck that opengapps is using an old setupwizard apk due to some unrelated issues.

Good news is, there is an easy fix. Removing this line does the trick. So, we should have it fixed in the next day or 2, pending code review. :good:

UPDATE: It's been fixed so no longer an issue. https://review.lineageos.org/163702
[Nexus 6P Original Android Development] IonutGherman:
A visual bug that for me is annoying. This is happening when I have my bluetooth speaker connected to my phone and YouTube running in background and playing music.

Link to video: Link
[Nexus 6P Original Android Development] razorloves:
New blog post http://lineageos.org/Last-Week-in-LineageOS-3/
[Nexus 6P Original Android Development] rweddy1:
Cell Connection issue 2-27

Hello All, I am having issues with my cell connection. If I lose connection I have to reboot my phone to re-connect. I have tired toggle airplane mode, checked my APN settings, etc.

Thoughts?
[Nexus 6P Original Android Development] richii0207:
Did you do any mods such as root, build prop edits, root apps, etc? What carrier?
[Nexus 6P Original Android Development] rweddy1:
Yes rooted, no build props, Carrier it T-Mobile.

I did factory flash a few weeks ago and noticed radio was angler-03.79 so I flashed radio angler-03.78 from 1st post, this might have been my issue.
[Nexus 6P Original Android Development] the_darkwing_duck:
Just to confirm, when I changed to use the Aroma OpenGapps the setupwizard worked fine.
[Nexus 6P Original Android Development] richii0207:
That sounds like it should be fixed since carriers other than VZW should be on 3.78 radio
[Nexus 6P Original Android Development] razorloves:
Yep, thanks. It was confirmed in previous posts. It will no longer be a problem. The fix was just merged an hour ago, so on the next nightly people will be able to use Dynamic Gapps again. :good:

What do you mean "it should be fixed"? I don't see anything that needs to be fixed.
[Nexus 6P Original Android Development] richii0207:
I was implying that his issue should have been resolved following the flashing of the radio. Sorry for the confusion.
[Nexus 6P Original Android Development] rweddy1:
Sorry for causing the confusion, after flashing radio I am all good to go...
[Nexus 6P Original Android Development] rweddy1:
Google Camera

Anyone get google camera to work on this ROM with working HDR/HDR+?
[Nexus 6P Original Android Development] razorloves:
It work fine. Always has, as long as I can remember. If it's not working for you that's likely caused by you having the wrong vendor img installed. See first post.

Or maybe you have wrong version Google camera. Should be using 4.3.016.147548696

https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera
[Nexus 6P Original Android Development] anderssonyang:
I did the search and no answer was found... Does automatic live display work for everyone else here? Looks like it doesn't work properly...Sometimes it kicks in too late and sometimes it doesn't change at all while at sunset or sunrise. Any thoughts?
[Nexus 6P Original Android Development] hectorviov:
I found another bug, when I restart the device, the Bluetooth is automatically turned off, even if I had it on before restarting.
[Nexus 6P Original Android Development] Jxcorex29:
I've noticed that too - no idea what causes it.
[Nexus 6P Original Android Development] Droid_JD:
I noticed this too.

Thought it was specific to my setup though
[Nexus 6P Original Android Development] hanschke:
random total crashed and i have to use 30 sec power of to reboot the phone. very strange...
[Nexus 6P Original Android Development] htb2050:
Happened to me too a few days ago. Just not on angler only but on another phone running lineage too.
[Nexus 6P Original Android Development] S /\ E E D:
Guys, sometimes screen doesn't turn off ... Anyone experienced this issue?