yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] sam3000:
The developers who write cm code have gone nowhere. Project name and server infrastructure may change but "cm" is not going away.

https://www.cyanogenmod.org/blog/a-fork-in-the-road
[Nexus 6P Original Android Development] maximusmullivan:
One more post, pretty informative http://www.androidpolice.com/2016/12/24/cyanogen-shutting-service-nightly-builds-december-31-2016/
[Nexus 6P Original Android Development] Jammol:
So rebrand and remerge under a different OS name? Interesting. They didn't deserve the slap in the face. As much as each individual deserves to be successful and have a bright future, I wish he didn't go about it the way he did. Now all these people are probably going to be without a job.
[Nexus 6P Original Android Development] maximusmullivan:
McMaster screwed it up for everyone. Kondik got crapped on because of it.
[Nexus 6P Original Android Development] cbond007:
In the new year, I expect to be running some "Lineage" Roms. I like it.
[Nexus 6P Original Android Development] D@rekills4:
So, I clean installed today's nightly with today's OpenGApps Micro.

Still having the colour issue, although a temporary fix is available, turning the sRGB mode on and off and it stays fixed until I reboot the phone.

Screenshots always capture the correct colour but the display shows the saturated colours.

I have also provided a logcat in the post below:

http://xdaforums.com/showpost.php?p=70121962&postcount=632

And I have attached pictures as a proof that something is really wrong with the colours.

The colour difference might be more noticeable or less noticeable to you guys compared to me, depends on the type of colourblindness I have.

Please let me know if the colour difference is noticeable for you guys are not.

Also, XDA likes to rotate the images I upload for some reason. :rolleyes:
[Nexus 6P Original Android Development] Jammol:
Whoa that's crazy saturated man. I don't know if I can say is a ROM issue. My colours definitely aren't that saturated at all.

Are you using a kernel auditor or custom kernel?
[Nexus 6P Original Android Development] D@rekills4:
Really? Didn't expect "crazy" saturated.

I am not even using any custom modifications.

Just plain CyanogenMod with the latest vendor, bootloader and radio from NMF26F.

[MENTION=4613660]Jammol[/MENTION], can you do me a favor?

Can you change the DPI to 480 is Settings → Developer Options → Custom width?

Then reboot the phone and tell me if you have similar saturated colours?
[Nexus 6P Original Android Development] Jammol:
Here's what I got. Looking g at your screenshots again, to me it's crazy saturation. I expect that from LG but not on a Nexus. To me, my level saturation is ideal.

Thanks for the DPI change. I'm actually liking it a lot.
[Nexus 6P Original Android Development] D@rekills4:
I still wonder why am I the only one with this issue.

It's not as if I am doing anything different. Everything is pretty much the same. Stock CM 14.1 (no modifications), OpenGApps (micro) and a clean flash.

Yeah, the DPI is on lift of first things to do after flashing any ROM. With a screen as big as Nexus 6P's, it's nice to have a lot more information on the screen at a time.
[Nexus 6P Original Android Development] d1n0x:
I got the same impression. I clean flashed the latest nightly with nano Gapps and it's as if the sRGB mode was turned on constantly. As you say, toggling it on and off again does the trick, but I have no idea why it defaults back to these weird colors.
[Nexus 6P Original Android Development] D@rekills4:
Previously, after fixing the colours using sRGB mode, the colours would revert back to the saturated levels at any moment.

But since the last few nightlies the colours revert back to the saturated ones only after I restart the phone.

[MENTION=614507]razorloves[/MENTION] and [MENTION=1890382]sam3000[/MENTION]

Where does the development state of our CM14.1 lie now that CyanogenMod is shutting down.
[Nexus 6P Original Android Development] NoobInToto:
Steve kondik and all other developers (grarak, etc) have moved to lineage distribution I heard. So they are all set to work on the new branch I guess :D
[Nexus 6P Original Android Development] D@rekills4:
Yeah, I read that too, I was asking about development related changes if any.
[Nexus 6P Original Android Development] Bobbaloo:
http://xdaforums.com/oneplus-3t/development/rom-unified-lineageos-cm14-1-t3525551/page1

• I'm wondering if the labor with the current CM 14.1 will yield fruit or if y'all might want to take a look at the above link and then decide how to move forward. Just sharing. I love CM. I use it on my older device and was hoping to use it on this one. Let's see what the future holds. Meanwhile, there are lots of great Roms for our device. Unless you're a developer and want to help with the CM-Lineage project. Good luck all

---------- Post added at 03:39 PM ---------- Previous post was at 03:18 PM ----------

GOOD READ: http://m.androidcentral.com/goodbye-cyanogenmod-hello-lineage-android
[Nexus 6P Original Android Development] D@rekills4:
Well, goodbye CM. It was a good run, thank you for all the convenient features.
[Nexus 6P Original Android Development] Bobbaloo:
Not necessarily goodbye ^____-
[Nexus 6P Original Android Development] sam3000:
No difference except name and server infrastructure changes. Development work stays the same.
[Nexus 6P Original Android Development] digesh9870:
I just updated to latest nightly build of cm 14.1 on my nexus 6p. The build date is 25 December 2016. The update went well, however, now I don't see any notifications in the status bar when I am actually receiving them. Also when I pull down the status bar, I can't see the expanded quick settings tiles. Only the top row appears. I had developer options enabled and even now I can see the developer options tab but when I open it, it says that "developer option not enabled for this user". Also pressing the recent button and the home button nothing. I can only use the back button. Before factory resetting the device, it would be nice if someone could help me out.

Thank you. ﻿
[Nexus 6P Original Android Development] prana_Sky:
looks like you are logged in as another user? try go back to device admin and see if that changes anything.
[Nexus 6P Original Android Development] digesh9870:
Thank you for your time. I navigated to settings and I can see that I am logged in. However, when I click the users tab, nothing happens. Maybe I'll clean install.
[Nexus 6P Original Android Development] kingbooga:
Edit: never mind it worked
[Nexus 6P Original Android Development] Jammol:
Did clean flashing solve the issue? I'm running the Christmas nightly without issue.

---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------

So Sam, is it safe to assume no more nightly builds for a while?
[Nexus 6P Original Android Development] digesh9870:
I moved on to a different rom now (back to pure nexus again). Still don't now what caused those issues .

Thanks by the way.
[Nexus 6P Original Android Development] styckx:
Looks like the 25th was the last of the nighties.. RIP.. Been using it since the Nexus 4G.. Gonna be weird without it as a ROM and a base for other ROMS but considering everything it was and now is.. It is indeed time to put the dying dog to rest...
[Nexus 6P Original Android Development] wilbarger:
I am guessing there will be one more nightly. The changelog is loaded up with quite a few modifications, so maybe one more.

to be included in next nightly:

cm: Track AOSP for unmodified external projects (android)

angler: add missing line continuation slash (android_device_huawei_angler)

build: Ensure that we can always find the CM envsetup script (android_build)

build: envsetup: Ensure that we can always run roomservice (android_build)

[2/2] settings: support setting a separate encryption password (android_packages_apps_Settings)

[1/2] base: support separate encryption/lockscreen passwords (android_frameworks_base)

Add wakelock option for flashlight (android_frameworks_base)

StatusBarIconView: Enable notification icon count by default (android_frameworks_base)

CMParts: statusbar: Enable notification icon count by default (android_packages_apps_CMParts)

cm: Remove def_notif_count overlay (android_vendor_cm)

SettingsProvider: Remove def_notif_count overlay (android_frameworks_base)

sf: hwc1: Add support for secondary color matrix (android_frameworks_native)

sf: hwc1: Set SF EventThread to SCHED_FIFO in all cases (android_frameworks_native)
[Nexus 6P Original Android Development] amandeepparmar:
This thread should be renamed to Lineage OS

Development stated by [MENTION=614507]razorloves[/MENTION]....thank you

https://github.com/LineageOS/android_device_huawei_angler?files=1
[Nexus 6P Original Android Development] D@rekills4:
Does anyone else see two of each contacts in the contacts app?

If I go to contacts.Google.com, I have only one contact of each name but on the phone I see double the contacts. :(

Why so?
[Nexus 6P Original Android Development] Bobbaloo:
Ha! If you solve that, please let me know. I've been dealing with that since I've been flashing Roms. I think it's BC of my Gmail acct automatically syncing SOME of them on top of my restore. That contacts app is just a pain in so many ways #_____#
[Nexus 6P Original Android Development] Jammol:
I'm assuming your contacts have multiple fields of information? Back when that first happened to me on CM12(I think), I used the merge feature on all of them and it never happened again.
[Nexus 6P Original Android Development] D@rekills4:
Seems to be a CM wide issue then. I have faced this on CM12 and CM13 of Samsung Galaxy Note (GT-N7000) as well.

Is there a way to merge them all together?

I see a merge option below each contact, but I don't want to merge all contacts one by one.
[Nexus 6P Original Android Development] Arcide:
It's not exactly rom related, but I have an issue.

All of my phone messages just suddenly disappeared.

I have a backup, but it is too old.

Is there any way to restore them, maybe if they automatically backup with google account or something?

I've also made a nandroid backup, so if nothing else works, there's that, but is there a way to restore messages from usb otg?

I know there's nandroid manager, but it doesn't recognize usb storage.

I'm a bit short on phone memory, so it would be a bit too much hassle to transfer stuff.

Or maybe someone has another idea?

Maybe the messages aren't deleted, they could be not displaying correctly?

I've tried to reboot, but no luck.
[Nexus 6P Original Android Development] Jammol:
Unfortunately that's the only way I knew of doing it is one by one. The Google contacts app has a slightly more robust way by searching and actually finding them.
[Nexus 6P Original Android Development] ironjon:
Yeeep :) :)

https://review.lineageos.org/#/q/status:open

Enviado desde mi Nexus 6P
[Nexus 6P Original Android Development] styckx:
FYI - They don't plan on renaming branches until the next Android release.
[Nexus 6P Original Android Development] Jammol:
SMS backup and restore by carbonite in the play store may be able to help you.
[Nexus 6P Original Android Development] Arcide:
I know about the app, but I didn't have auto backup enabled and my last backup was a month ago.

I did however make a nandroid few days ago
[Nexus 6P Original Android Development] Jammol:
Best bet then is to probably restore the data and cache partitions.
[Nexus 6P Original Android Development] Arcide:
I guess I'll have to do that.

I was just wondering if there was another way, because this will take some time, since I'd have to move some things around.

But thanks for the help.

EDIT: I just restored just data from nandroid backup, checked the messages, and all that were supposed to be there were there.

So I went to back them up with the app, it only backed up calls, said there were 0 messages.

I went into messenger app, there were no messages. What the hell!?
[Nexus 6P Original Android Development] Jammol:
Try restoring the data again, verify its there, send and receive a few messages and see if they stick around after a reboot. Then try backup
[Nexus 6P Original Android Development] OmegaBlaze:
Mine does the same thing. I think you have to pack up the cache.

Edit: My cache is at 0MB. I don't even know if backing it up is possible.
[Nexus 6P Original Android Development] Jammol:
Just because it's 0MB doesn't mean it's not there. Give it a try and report back.
[Nexus 6P Original Android Development] bauwoo:
Will this project continue now that CyanogenMod business has closed down?
[Nexus 6P Original Android Development] Lawlrus:
Read the last page or two ?
[Nexus 6P Original Android Development] sam3000:
The project has already continued - https://review.lineageos.org/
[Nexus 6P Original Android Development] ongjingxian:
Quick question, for the final cm13 snapshot build, which vendor image should I flash? The build number in ROM says MOB31K (which is a nexus 6 build).
[Nexus 6P Original Android Development] NingaR:
Am using MTC20L.
[Nexus 6P Original Android Development] razorloves:
Here's a new nightly i just made to satisfy you flashaholics while we wait for official nightlies to come. :p

No wiping needed if you're just updating from older cm rom.

lineage-14.1-20161230-UNOFFICIAL-angler.zip

Device specific changes since last official nightly:

angler: Move carrierconfig overlay to device/

angler: Pin boot oat and services dex from /data

angler: Pin camera app in memory

angler: add missing line continuation slash
[Nexus 6P Original Android Development] Jammol:
Thank YOU! I was about to head out to my first Android Anonymous meeting right before you posted this!!!?
[Nexus 6P Original Android Development] htb2050:
Wow these changes especially the camera one will be really great. Opening the camera had slight delay but since s7 keeps it in memory so we can spare 35mbs easily with swap and already 3gb of RAM.
[Nexus 6P Original Android Development] amandeepparmar:
Deleted
[Nexus 6P Original Android Development] IonutGherman:
No. Just the default "android" bootanimation and a ? rounded at start.
[Nexus 6P Original Android Development] razorloves:
there is no new logo and bootanimation yet. you've been deceived. rebranding is still in work.

EDIT: This is the new logo. As of a few minutes ago it was made public. https://www.reddit.com/r/LineageOS/

(See banner along the top)
[Nexus 6P Original Android Development] infus38:
Delete :

request from razorgloves

Reason fake website
[Nexus 6P Original Android Development] Jammol:
You did see Razor posted a build he made for us 2-3 posts above right? Lol.
[Nexus 6P Original Android Development] Ozzy0708:
I just got my Nexus 6P 2 days ago and I'm wondering whether battery life is better on stock Android 7.1.1 or Cyanogenmod? Even though I've never had this device, I almost feel as though it should be lasting longer than it is. I bought it pre-owned and it had AOSPA on it, and I immediately flashed official Android 7.1.1 to it because I only use stock or Cyanogenmod. Before deleting everything I've got on it and flashing CM14.1 (or even the LineageOS link razor shared), I wanna know whether or not I'd see any improvement. I'd appreciate any input!
[Nexus 6P Original Android Development] razorloves:
new nightly i just made. enjoy

lineage-14.1-20161231-UNOFFICIAL-angler.zip

no device specific changes, but you can see all changes here https://review.lineageos.org/#/q/status:merged
[Nexus 6P Original Android Development] wilbarger:
Running smooth. Are you going to post a change log for your nightlies?
[Nexus 6P Original Android Development] styckx:
Working fine.. Thanks for taking the time to build it..
[Nexus 6P Original Android Development] diddly3000:
What gapps you guys use? Is open gapps still broken with regards to ok google anywhere?
[Nexus 6P Original Android Development] htb2050:
since you got it preowned so it might be that the battery health is already detoriated to a point to have ntoiciable decrease in battery life. download accubattery and check your battery health after a few charges.
[Nexus 6P Original Android Development] talkcc144:
Are there any critical issues in this ROM as far as any users know?

Thank You
[Nexus 6P Original Android Development] razorloves:
Yes opengapps still has an incompatible hotword apk which breaks "ok google"... and cmsetupwizard is still horribly broken too.

You should use this gapps https://xdaforums.com/android/software/gapps-dynamic-gapps-t3487192

For a clean flash, i myself factory reset, wipe system, flash rom, flash dynamic gapps, and now also flash su zip if you want root, since official lineage 14.1 does not come with root.

Then while still in twrp, mount system and open the twrp file manager (or use adb) and delete this folder /system/priv-app/CyanogenSetupWizard/

Then reboot

EDIT: As of the 15th of Feb, the cmsetupwizard has finally been completely overhauled and renamed to lineagesetupwizard, as you can see here. So, there is no longer a need to remove it.
[Nexus 6P Original Android Development] diddly3000:
Ah OK cos I use these gapps myself but the setup got stuck on restore from another device. So thought was gapps issue. Thanks will try your suggestion of removing setup folder
[Nexus 6P Original Android Development] SchmilK:
I had the same problem. After the wifi setup, just keep tapping the next area, for a very brief second there is a skip button, Going back adn trying again once or twice and you will get it.
[Nexus 6P Original Android Development] Ozzy0708:
Alright, I've got it downloaded. I'll report back after a few charge cycles.
[Nexus 6P Original Android Development] razorloves:
Since the build servers are having issues for a few days now, here's a build i just made.

It's the same as an official nightly.

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

Here's the changelog. Everything in the "to be included in next nightly" section is in this build.

https://www.cmxlog.com/14.1/angler/
[Nexus 6P Original Android Development] razorloves:
only vendor in twrp.

bootloader and radio use fastboot.
[Nexus 6P Original Android Development] tdg2k15:
Or go to WETA rom download page to obtain twrp flashables.
[Nexus 6P Original Android Development] Lawlrus:
You're telling the kernel dev what his kernel is/isn't for? Lmao
[Nexus 6P Original Android Development] Jammol:
Weird thing just happened after waking up today. OkGoogle hotword detection is no longer working even after resetting and setting up again. This is getting weird.
[Nexus 6P Original Android Development] NoobInToto:
Does anyone get system error at the start of each boot? Also it asks for pin at each boot, after entering it boots with boot animation again.

I've been wondering that this is messed up since I flashed initially using flashfire. There wasn't an option to wipe system, but there was an option for system data wipe.

Other than that, there seem to be no issues.
[Nexus 6P Original Android Development] tdg2k15:
Make sure you've flashed bootloader, radio and vendor img's before flashing this ROM. Also coming from any other ROM I do suggest you to do a clean install.

It asking for a pin on startup has only happened to me when I had to register my fingerprints and it asked me if I wanted to use the pin on start up.
[Nexus 6P Original Android Development] info[]box1:
I had notice that after ward wanted to edit then it slipped my mind. Lol.

Plus I notice Dev create a cm build. That's want there last time I was in the thread. After the fact I peep that.

I had been so long enough to thats funny as hell.
[Nexus 6P Original Android Development] antmunny:
dirty flashed it over 11/11 nightly and everything's working great!

thank you for making an updated build for us
[Nexus 6P Original Android Development] Jammol:
Here's a stupid question, has any of you tried dirty flashing 14 over 13?
[Nexus 6P Original Android Development] smeatr0n:
I dirty flashed this sucker over cm13. Used openGapps mini, vendor, boot, modem, etc. No gallery issues, no weird boot loops. But I get a message on every boot that cm bug report has closed. That is almost the only issue I've encountered. Gesture keyboard is borked, using google play version instead. And SMS app gets stuck sending, so using play store version for that also. No other issues to report here.
[Nexus 6P Original Android Development] Lawlrus:
The cyanogen team has stated in the past that the way they produce their ROM, you can dirty flash one version to another.

Not sure I've known anyone that felt the need to do so though lol.
[Nexus 6P Original Android Development] Apoena:
OOPS!

no mirrors found.

:crying::crying::crying:

Can anyone post in a different file host?
[Nexus 6P Original Android Development] sam3000:
This should work fine. It was made a requirement of cm-14.1 before nightlies were shipped.
[Nexus 6P Original Android Development] Pycuklr:
Where can I find the Theme Engine for CyanogenMod 14.1 ? If there is such a :)
[Nexus 6P Original Android Development] nags92:
I haven't personally flashed this yet, but my assumption based on how previous CM builds have been done is that you might have to wait a few builds before new features are implemented.

They generally make a build stable when a new android version is released then add features on top !
[Nexus 6P Original Android Development] Lawlrus:
Not to mention getting to wait for themes to update it once cm14 theme engine comes out lol. I dunno why everyone is worried about it when its going to take time
[Nexus 6P Original Android Development] Arcide:
Hey, weird issue here.

All of the videos have a bug, the video only plays for a second and it freezes, but you can hear the audio still going.

Edit: sorry that was because of the 20161114 unofficial version, I just flashed 20161111 back and it works fine.
[Nexus 6P Original Android Development] Jammol:
Sweet thanks for the info.

Yeah. I'm just trying to find a way to fix this stupid okgoogle bug introduced by Gapps. About to go up from 13 with 8132016 Gapps(last one i think that had working hotword), and hopefully it still works once on cm14.

---------- Post added at 08:47 PM ---------- Previous post was at 08:46 PM ----------

Thank you for the info. And thanks for your contribution to CM!!!! :)
[Nexus 6P Original Android Development] funebral:
please could someone tell me apart from vendor img what other do i need to flash before cm14.1 .zip?
[Nexus 6P Original Android Development] Enhanced:
nevermind
[Nexus 6P Original Android Development] Ozzy0708:
I just want to clarify that even though I haven't had accubattery long enough to test for the health, I'm no longer worried about the battery. I've used it fairly heavily all day today. A fair amount of YouTube, a lot of VR (another Christmas gift), and tons of Facebook, Instagram, and Snapchat. I took it off 100% at around 10:00 this morning, am at 28% and have 3hrs of screen on time currently. I believe it just took a day or two for the OS to settle in, because this kind of battery life is more than enough for me.
[Nexus 6P Original Android Development] D@rekills4:
What's the recent apps scene?

My recent apps list automatically get cleared. Only 3 or 4 are left when I wake up in the morning.
[Nexus 6P Original Android Development] d1n0x:
Normal. In Nougat, the apps that aren't used for a while get cleared from the list.
[Nexus 6P Original Android Development] D@rekills4:
But are they removed from the memory as well?
[Nexus 6P Original Android Development] htb2050:
Oh man! The latest patches to keep camera app in memory is the BEST!!! Previously I had to wait for 2-3 secs for camera app to launch after pressing the power key twice, but now its almost instantaneous!
[Nexus 6P Original Android Development] d1n0x:
Don't know about that, sorry
[Nexus 6P Original Android Development] IonutGherman:
There is a freaking out a problem with this ROM!! Everytime I want to test a ROM, I do a backup of my actual system. Good. But when I restore the system with this one, when my phone boots up, the patern NEVER works. I've tried to enter it about 1000 times. I don't know exactly if it's Lineage related or a TWRP problem, but it freaks me out because now I need to reinstall it...Last LineageOS build with TWRP 3.0.2-3 version.