[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Moto X Pure 2015 (clark) - X Style (Pure) Android Development

LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Download Links
LineageOS:
Nightly: https://download.lineageos.org/clark
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM64 platform, Android version 7.1)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Misc Links
Changelog:
Link: https://download.lineageos.org/clark/changes/
Learn to build yourself:
Link: https://wiki.lineageos.org/devices/clark/build
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Moto X Pure 2015 (clark), ROM for the Moto X Style (Pure)
Contributors
invisiblek, Hashbang173
Source Code: http://github.com/LineageOS
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-12-05
Last Updated 2016-12-05

---

reserved ahahahahaha :laugh:

---

Thanks for this!

---

Anyone give this a run yet? I want to jump in, but am wondering about bugs before I do. I might just hop in anyways.

---

Cm14.1 with cmrecovery dont boot?
Gesendet von meinem XT1572 mit Tapatalk

---

Prazaar said:
Cm14.1 with cmrecovery dont boot?
Gesendet von meinem XT1572 mit Tapatalk
Click to expand...
Click to collapse
Why even bother using cmrecovery instead of twrp? CM boots fine for me and many others, and I'm guessing most of them use twrp.

---

wont boot for me either

---

couple of bad issues
Installs and boots fine with twrp for me, using open gapps 64 7.1 nano
Clean install
ext SD Card can be seen, but data can't be accessed
No Theme Chooser app

---

CM14.1+OpenGapps+CMRecovery = Dont Boot
CM14.1+OpenGapps+TWRP = all fine
Idea why CM Recovery dont work?
Gesendet von meinem XT1572 mit Tapatalk

---

With last night's update I am unable to install apps as it says there is no space left. However as you can see in the screenshot below, I have plenty of space available

---

Maybe someone can point me in the right direction.... Nightlies are by definition nightly automated builds? Bugs/fixes are made by CM and pushed out and code is automatically compiled? Am I totally wrong? In our case as " invisiblek" is our maintainer, what exactly does he do? Is he helping by monitoring the builds and fixing things above and beyond to get to a Snapshot, RC or Stable? Hypothetically, why did that never happen for 13 or 13.1.
Just trying to learn. Thanks

---

Just curious if the ring and notification volumes have been separated. The last unofficial nightly I was running they were still combined.
Thanks.
Sent from my Pixel XL using Tapatalk

---

Bwangster12 said:
Maybe someone can point me in the right direction.... Nightlies are by definition nightly automated builds? Bugs/fixes are made by CM and pushed out and code is automatically compiled? Am I totally wrong? In our case as " invisiblek" is our maintainer, what exactly does he do? Is he helping by monitoring the builds and fixing things above and beyond to get to a Snapshot, RC or Stable? Hypothetically, why did that never happen for 13 or 13.1.
Just trying to learn. Thanks
Click to expand...
Click to collapse
Invisiblek and Hashbang are our device maintainers, which means they do device specific work. The main base is for every phone, but you still need someone who changes and adds stuff so it can run on their phone. And btw, they were doing this for the 13 and 13.1 builds too.

---

chris_dis said:
Invisiblek and Hashbang are our device maintainers, which means they do device specific work. The main base is for every phone, but you still need someone who changes and adds stuff so it can run on their phone. And btw, they were doing this for the 13 and 13.1 builds too.
Click to expand...
Click to collapse
Gotcha, thanks for the explanation.
So the next question... how common is it for these nightlies to get to Snapshot or above status? I feel like I've followed the CM community across a few phones (HTC Thunderbolt, LG G2, now Moto X Pure) and really only remember a few instances of getting out of "nightly." Is it up to a lot of work by the device specific maintainer to get it stable enough? I feel like 13 and 13.1 have been available for awhile and they are still just nightly, right? This is not intended to seem disrespectful... I'm just trying to learn how this works.

---

Bwangster12 said:
Gotcha, thanks for the explanation.
So the next question... how common is it for these nightlies to get to Snapshot or above status? I feel like I've followed the CM community across a few phones (HTC Thunderbolt, LG G2, now Moto X Pure) and really only remember a few instances of getting out of "nightly." Is it up to a lot of work by the device specific maintainer to get it stable enough? I feel like 13 and 13.1 have been available for awhile and they are still just nightly, right? This is not intended to seem disrespectful... I'm just trying to learn how this works.
Click to expand...
Click to collapse
Not sure why there wasn't an RC or stable release.... Again I'm not sure if this is down to the main core or the device maintainers.
We did a decent job of keeping track of the "recommended" most stable nightlies in cm13 (the thread was very active) and it just worked well..... I would t be too bothered if cm14.1 went the same way really.
Just sit back and keep an eye on the changelog link and this thread [emoji1]
Sent from my XT1572 using Tapatalk

---

Thank you to the maintainers for bringing CM 14.1 to the Pure!

---

mrvanx said:
Not sure why there wasn't an RC or stable release.... Again I'm not sure if this is down to the main core or the device maintainers.
We did a decent job of keeping track of the "recommended" most stable nightlies in cm13 (the thread was very active) and it just worked well..... I would t be too bothered if cm14.1 went the same way really.
Just sit back and keep an eye on the changelog link and this thread [emoji1]
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
Good approach.
The way CM releases roll out the stable tree can be cut months behind the nightlies. So if you're on a nightly where everything works for you, then you're really not gaining anything by flashing stable. In fact, you probably need to clean flash from a nightly to a stable unless your nightly is like three months old because while roms are usually pretty tolerant of dirty flashing when moving forward, that's not always the case when you go backwards.

---

JohnMcW said:
Installs and boots fine with twrp for me, using open gapps 64 7.1 nano
Clean install
ext SD Card can be seen, but data can't be accessed
No Theme Chooser app
Click to expand...
Click to collapse
Can you get a dmesg and a logcat?
I ask for a dmesg since I think there could be selinux denials causing this

---

alershka said:
Just curious if the ring and notification volumes have been separated. The last unofficial nightly I was running they were still combined.
Thanks.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
They're still stuck together on 12/5.
I can't find too much else to ***** about, however.

---

Prazaar said:
Cm14.1 with cmrecovery dont boot?
Click to expand...
Click to collapse
TWRP. Why use some old skool CWM clone? Makes no sense.