yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] Chetan-123:
Eagerly waiting for next build of lineage os .!!!!!!!!!:confused:
[X Style (Pure) Android Development] bronkish:
Thanks for the ROM

This ROM runs well on my XPure. I ran LOS official and it was excellent. I went to stock 7.0, took the quick 8MB upgrade, then to 14.1 unofficial. It's terrific, thanks.

Only 'issue', is the date of last checked in the LOS upgrade interface - Last checked: December 31, 1969.

Thanks for the ROM.
[X Style (Pure) Android Development] xabr3:
Will there ever be an official build based on Nougat modem?
[X Style (Pure) Android Development] Hashbang173:
There are currently a few issues preventing me from making the official builds based off of the Nougat modem.

The new kernel has F2FS changes that cause issues with TWRP and the stock ROM. I don't want people having bootloops trying to restore to stock.

There is also the issue of the ROM not working with the Marshmallow modems, but I suppose I could alleviate that issue by adding a check in install script and aborting if the user is not on the Nougat modem.

The LineageOS 15.1 Oreo builds will definitely be based on the Nougat modem.

If you want a new LineageOS 14.1 build based on the Nougat modem, feel free to ask.
[X Style (Pure) Android Development] StankFiss:
I'm coming from stock MM using the 14.1 1-8-17 build. For some reason with substratum it breaks the power menu when I add overlay. When I hit power button it reboots phone. Is this a known bug if so is there a fix for this?
[X Style (Pure) Android Development] fritzophrenic:
Installed unofficial with latest official TWRP, some issues

Thanks for putting out the test builds for Nougat modem! I was stuck when I got a replacement for a busted screen and Nougat came pre-installed.

It's mostly working for me so far, with a few glitches here and there.

First though, I was lazy and tried installing with the latest official TWRP (3.2.1-0) rather than the unofficial build shared in this thread...and it actually worked! Looking back at the thread I'm a little surprised it did work. Are there possibly subtle issues that could have caused?

I did have some rather annoying issues I wanted to see if there's an easy workaround/fix for. I'll keep digging at these, maybe they're just something acting up on my phone rather than a real problem, but if it's a known issue, or if you want more data, that's good to know as well:

I use Sprint as my carrier. Every time I reboot, I am not able to connect to data, until I disable wifi and "Update Device Config" in the carrier settings.

I think my battery life is a lot shorter (compared to stock). This one I'm not so sure about. I encrypted my phone and installed a couple extra apps compared to what I had on stock. Nevertheless, something is keeping my phone "awake" at all times and battery life is considerably shorter.

I'm even less sure about this one: Bluetooth seems to be working poorly. I paired to my car but when someone called me it only rang on the phone itself. Also getting severe stutters in streaming music. This didn't happen on stock. But I only tried it once; it could be a fluke if nobody else is noticing issues. I plan to keep an eye on it.

Camera is extremely slow to launch.

Oh and as someone else mentioned the update check shows 1969 as the "last checked" time...but since there will never be a valid update found from there until it's an official build I don't think that matters in the slightest. :)
[X Style (Pure) Android Development] fritzophrenic:
Regarding this issue I noticed with the unofficial Nougat-based build:

I'm pretty sure this one isn't just a fluke after all. I plugged into a charger overnight (which I've used every night for months at least) and it doesn't charge. Two nights I thought maybe the cable came loose; last night I can see in the battery details that it was "charging" the whole time (very slowly). When my alarm came on, and kept the screen on while I snoozed, the battery *drained* even though the phone was still plugged in. Per the battery use details, the main offender was "LineageOS System". I've seen about 140% battery drain over 17-18 hours with less than an hour and a half of screen-on time!

I'm *pretty sure* I also saw battery drain while plugged into my car charger. I'll see what the charger I keep at work does...if it isn't much better, this build might just be unusable for me. :(

I was going to attach a couple screenshots of the battery app, but it looks like I can't do that directly through the web interface. Overnight my charge went from about 55% to about 70% and then dropped in the last half hour (still on the charger) to 62%. "LineageOS System" shows as using 21% compared to "screen" at 13%. The phone is "awake" the entire time with some gaps yesterday where it dozed normally (I have no idea what event started the constant "awake" status, a reboot didn't help).
[X Style (Pure) Android Development] blargh22:
First off, really appreciate everything that you have done/are doing. I would like to ask your opinion. I am currently on Nougat. Do you think I am better off flashing the MM modem and running the official Lineage OS builds from the website? I believe MPHS24.49-18-8 is the most recent MM firmware that I have access to. This way I at least have access to automatic updates. Or should I just remain stock and wait for Lineage OS 15? Given the official ROMs are updated weekly, I do not want to bother you for updated builds. What do you recommend? Will I have to use your custom build of TWRP? My device is currently on NPHS25.200-22-1 (Nougat).
[X Style (Pure) Android Development] OverkillSRB:
Would it be possible to make a lineage kernel with voltage and frequency control and how would one go about doing that?

If a the dev could do it that would be great, but i know more than to bother developers who already provide their effort to bring us this great rom.

Where could i learn how to do it and would it break anything?
[X Style (Pure) Android Development] jason2678:
There's some good building guides on XDA to get you started. Search and you'll find more.

Willingness to setup a linux environment and learning how to interact with it for building stuff, as well as learning how to use git effectively are the biggest barriers to entry. You don't need a really deep knowledge of writing code to fork a working repo and cherry pick some new features, at least as long as everything goes well ;). So don't be intimidated; everyone has to start somewhere.

I used to tinker some with roms and kernels, and I certainly don't have a computer science background. The box I use to build on has some java library problems that prevent me from building anything newer than marshmallow, and I've never taken the time to update it. Maybe someday...
[X Style (Pure) Android Development] wizardknight:
Have you tried the handbag kernel?

https://xdaforums.com/moto-x-style/development/handbag-kernel-t3606987

It is a little older. Maybe you could use it as a base, and update the core code to the newest kernel version(s).
[X Style (Pure) Android Development] OverkillSRB:
I took a look at the guides, but it seems like a kernel repository is not the same as rom repository, i couldn't find kernel files in hashbangd LOS repository.

Also, handbag is a little old, i would rather add my modifications to the los kernel hashbang uses.

https://github.com/HashBang173/android_kernel_motorola_msm8992

Is this the kernel hashbang uses in the new LOS releases, or are the kernel files in the rom repos?
[X Style (Pure) Android Development] fritzophrenic:
Again, regarding the unofficial Nougat-based build:

I encrypted my phone after flashing the unofficial build, and now neither the official TWRP nor hashbang's unofficial TWRP from October can decrypt. System decrypts and boots just fine, I just can't decrypt data in TWRP (so no backups for me). :(

The issue with connecting to my data network seems to have resolved itself after I wiped cache partition. Bluetooth as well, after wiping cache partition and all app cache. Camera is also a little faster now but still slower than I remember it.

The battery still drains much faster than it did on stock, however. I am pretty sure it is draining faster than it did on the OFFICIAL build. I got it into a state that is actually somewhat usable (although still annoying) by:

Wiping cache partition and app caches; this took care of Lineage/Android system eating all my battery.

Using Privacy Guard to deny "keep awake" permission to a dozen or so apps (Hangouts and Facebook were the worst offenders, a few other Google apps were pretty bad as well); this allowed my phone to actually doze from time to time.

Disabling "Ambient Display" (which is a shame, that's one of my favorite features).

---------- Post added at 06:01 AM ---------- Previous post was at 05:48 AM ----------

Hey Hashbang: any chance at a new unofficial build with the January security patches?
[X Style (Pure) Android Development] Hashbang173:
https://www.androidfilehost.com/?fid=962187416754456544
[X Style (Pure) Android Development] AsquareX:
Is this for N modem?
[X Style (Pure) Android Development] antariksh:
yes
[X Style (Pure) Android Development] kb8no:
I have more than one Moto X Pure. I have been using LOS 14 official on my previous DD and I have lots of experience with the official LOS 14 which is favorable.

I am using a different Moto X Pure device now. I unlocked the boot loader and using TWRP official I backed up stock Android 6. I. I then took the OTA to Android 7. I installed TWRP unofficial and saved Stock Android 7 and then wiped system, cache, and Dalvik. I installed Lineage OS 14 unofficial and used LOS addonSU. I used pico Gapps as I am used to using this with my other low RAM devices. I am now using this as my DD.

I am very happy with LOS Unofficial. Here are my observations. I am not really having battery problems. If my attachment came through, you can see my battery graph on a usual kind of day when I am using it in my normal way. This seems quite unremarkable, not bad, not good, but acceptable and similar to LOS 14 Official. It is mostly hard for me to tell the difference. I am not seeing the battery problems described by others.

I too noticed start up of the camera was slow after booting. Having said that, after the first time of loading the camera it comes up quickly and normally. Surprisingly, the behavior on Official LOS 14 is identical, I just hadn't noticed it.

I too have noticed some Bluetooth anomalies. I don't use BT in my car for speaker phone. I do have a Anker SoundCore 2 which I use as a music center. My LOS 14 Official device I was using mainly as a sound system and I did not have a SIM installed. It worked perfectly. I was using newly updated LOS unofficial device in the same manner with a SIM card. When I received a phone call it locked up, kept ringing even though the phone call had dropped, and then there was a soft reboot. This is readily repeatable every time. I then went to the LOS official device and have the exact same behavior. I have not flushed out every BT possibility.

So with LOS 14 official and unofficial I am finding the same slow start camera and the same observed BP anomalies. i.e. they seem identical to me. The face sensor activated lock screen wake of stock Android 7 does not work in either LOS 14 Official or Unofficial. WaveUp installed through F-Droid works perhaps even better and is a nice work around when set to 2 waves and pocket mode is disabled.

I have no data problems on ATT or Verizon. I dislike Ambient Display and disable it as soon as I get my hands on a phone.
[X Style (Pure) Android Development] glfngmble:
Google app and Google Play Services using Fine Location

I have been on nightlies since they came out. I enjoy the 14.1 updates but I noticed some odd battery drain issues. I started monitoring Privacy Guard and it seems that these two apps don't sleep. These two turn on Fine Location and it runs constantly. Now, I wiped the Data and Cache for both apps and they behave for about 10 minutes then they go back to Fine Location running constantly.

I switched them to Always Ask instead of Allowed and they seem to behave better. They stop and take a break but now I have to constantly allow (I don't select "remember") the app to run.

Thoughts?
[X Style (Pure) Android Development] fritzophrenic:
Does anyone using the unofficial Nougat build have encryption enabled? If so does TWRP decrypt successfully for you? I'm thinking about decrypting and re-encrypting to see if it helps, but I have an account on my phone that requires encryption enabled, so it's a bit of an involved process to do that.

---------- Post added at 01:52 PM ---------- Previous post was at 01:38 PM ----------

I don't have experience with Bluetooth on the official build, I only ever connected to Bluetooth headphones on official Lineage. I had good experience with connecting to my car on stock, which is now inconsistent in unofficial Lineage. The speaker phone features tend to work most of the time for me now, but text messages sometimes don't become available and Pandora probably works less than half of the time.

Camera I agree works pretty much the same as official Lineage. I was hoping for improvement, the comments on this bug implied the official Nougat release would help things, but I guess there must still be work to do to take advantage of it: https://jira.lineageos.org/browse/BUGBASH-236
[X Style (Pure) Android Development] xabr3:
Bluetooth issue sounds exactly like the bleutooth issue with the Moto X 1st Gen., unfortunately it was never fixed. (Device now abandoned due to lack of maintainers.)

Anyway, I have the same experience as you, car stereo is a problem + Moto 360 keeps reconnecting.
[X Style (Pure) Android Development] danikane:
Just FYI.

Latest official from 29.01.2018 dirty flashed over official 22.01.2018 via LOS Updater (thru TWRP 3.1.1-0 unofficial by hashbang) caused bootloop.

I did install the latter thru the same TWRP though, so I can't blame the recovery.
[X Style (Pure) Android Development] wizardknight:
You might want to update to the newer official TWRP.

https://twrp.me/motorola/motorolamotox2015pure.html
[X Style (Pure) Android Development] Alibaba0101:
I found that the Bluetooth issue is a cpu issue. los cripples the CPU to save battery. Try kernal aduitor and change the CPU to ondemand and enable input boost for the large cores. Battery life is less, but at least it works.
[X Style (Pure) Android Development] danikane:
Same thing, man. :)

Except I also got bootloops trying to restore the backup I made with the newer TWRP. :laugh:

I restored the previous recovery and backup.
[X Style (Pure) Android Development] kb8no:
Sorry if I am stating the obvious or am I missing something? Official ROM and official TWRP are for M firmware. Unofficial ROM and unofficial TWRP are for N firmware. It should be no surprise that N TWRP doesn't work in M firmware environment and that M TWRP doesn't work in N environment.
[X Style (Pure) Android Development] Chetan-123:
[MENTION=1689574]HashBang[/MENTION]

The 29.1.2018 build of LOS 15 is it stable..Can i flash??
[X Style (Pure) Android Development] GRVsingal:
And is it based on nougat or can i flash it over marshmallow firmware?
[X Style (Pure) Android Development] kb8no:
I stream music to an Anker SoundCore2 BT headset speakers as my effective "sound system" using a phone without a SIM and my favorite streaming app TuneIn Radio. I otherwise don't use BT much. I added a SIM and when I receive a call while streaming it locks up, keeps ringing, and usually ends up with a soft reboot. I thought it was "The Bluetooth Problem" described but the Kernel Auditor problem above did not help. I began to suspect the headset so I tried my Sony MW600 headset with ear buds and same problem. I began to suspect the app so I cleared the cache and data of TuneIn Radio no improvement. I streamed an mp3 with VLC app and problem gone. I began to suspect Lineage OS and I found the same problem on either LOS14 Official or Unofficial. I tried stock and the problem is gone. Google is your friend. It is a described LOS bug exactly described.

https://jira.lineageos.org/browse/BUGBASH-306

Maybe this will help someone else. This bug is listed as closed but obviously it is still a problem.

---------- Post added at 12:15 PM ---------- Previous post was at 11:34 AM ----------

Hashbang's answer is that LOS 15 will be new firmware.

https://xdaforums.com/showpost.php?p=75283005&postcount=1114

Anybody tried it yet?
[X Style (Pure) Android Development] Alibaba0101:
It based on M modem. I had trouble with the upgrade (got some errors) went back in twrp and reinstalled it. Everything looks ok. Not impressed with the CPU governer settings though. I'm not sure if its the powersave auto optimization, but the large cores were throttled and the phone was sluggish.

Oops, didn't see the question was about los 15. My answer was for the the 1/29/2018 14.1 nightly.
[X Style (Pure) Android Development] kb8no:
LOS15.1 flashed on new O firmware and working extremely well. The Hashbang anddroidfilehost link and Magisk links are provided below for your convenience. The Open Gapps pico that I found is linked below. I don't doubt that others would work but this is what worked for me. I use TWRP Unofficial and I came from LOS14 Unofficial which I backed up of course. Then Wipe cache, Dalvik, and system. Then flash ROM, Gapps, and Magisk in this order all together. Then boot system.

Hashbang LOS15.1 https://androidfilehost.com/?w=files&flid=244563

Open Gapps Unofficial 8.1 https://xdaforums.com/showpost.php?p=74862007&postcount=5

Magisk https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

The flash time surprised me at how quick it was. The Google sign in was uneventful but although I was able to login to my WiFi it wouldn't move forward so I hit "skip" and it dropped WiFi and went to SIM data and without skipping a beat I was finished. Thus, SIM data works. I logged back onto WiFi and it works just fine, thus WiFi data works. Playstore loads apps as it should. Magisk and root work fine. Seems very smooth and quick. Bluetooth wants to turn on but is not working and can't be seen. Wi-Fi Hotspot appears to work and you can set it up but there is no signal. Camera doesn't work and something about "Media Server died" and "can't connect to the camera". Just my limited time on this ROM it seems like it is pretty close. Very exciting and eager for his next build.
[X Style (Pure) Android Development] FanboyStudios:
Since LineageOS does not have Substratum OMS commits, Substratum runs in the older RRO Legacy mode. This is a bug, unfortunately afaik this has to be fixed at the system level so you're stuck with it. To fix this boot into recovery mode and install the Substratum Recovery Legacy .zip file and reboot. Then apply your themes overlays excluding "Android System". I have the same issue on some of my other phones and from research that was the fix. Hopefully LineageOS would apply OMS commits someday, but it's probably not going to happen. This is why CyanogenMod 13 is my favorite rom on my Moto E LTE, because there I had a working theme engine (CMTE).
[X Style (Pure) Android Development] Pastinakel:
Once lineage 15.1 is released, you can use Andromeda to apply substratum themes.

https://www.xda-developers.com/custom-themes-android-oreo-substratum/
[X Style (Pure) Android Development] stevejohnson42:
I use Black Swift theme with Hasbang's Lineage that he did for N Modem on clark - it has a selection for Lineage OS ; it installed without issues ; I don't use theme on WhatsApp , Google + or Hangouts -- i seem to recall he quit trying to keep up with the changes that kept being done to WhatsApp that appeared to be trying to stop people from theming it - your results may differ
[X Style (Pure) Android Development] fritzophrenic:
I just wanted to pop in again to mention that my battery issues seem mostly to be gone after installing Hashbang's unofficial Nougat-based build from the end of January. This time, I installed it using the unofficial TWRP as well, I wonder if that made a difference. Now I can leave it off the charger most of the day as long as I'm not actively using it.

Bluetooth is still having trouble connecting to my car stereo, but I've found it works more frequently if I fully unlock my phone before enabling Bluetooth, all while the car stereo is on and ready for me to connect. If it doesn't fully connect, a soft reboot often fixes it. So that's something I can live with.

I'm back to a usable Lineage install. Thanks, Hashbang!

(I'm still not able to decrypt in TWRP to take backups though)
[X Style (Pure) Android Development] KC69:
thanks Hashbang for keeping this forgotten device alive.
[X Style (Pure) Android Development] Hashbang173:
I have a test kernel for those on the official cm-14.1 marshmallow based builds

Let me know if there are any issues

https://www.androidfilehost.com/?fid=673956719939817427
[X Style (Pure) Android Development] dzidexx:
Do you mean:

Bulids for MM modem?

Has it kcal support?
[X Style (Pure) Android Development] Hashbang173:
Yes, it is for official builds (which are based off of the MM modem currently)

---------- Post added at 09:40 AM ---------- Previous post was at 09:12 AM ----------

I plan on adding an assertion in the zip to detect modem version to prevent flashing on an incompatible modem

Can somebody on the MM modem please run the following command?

adb shell "getprop | grep ro.boot"
[X Style (Pure) Android Development] jason2678:
I've never updated past MM. See attached.
[X Style (Pure) Android Development] mrvanx:
Will give it a go, im currently re-starting again as the battery died earlier and fried my install (it was bootlooping). Thankfully it doesnt take long to do a default wipe and be back up and running. Might this test kernel help with battery usage?? (I raise my flame shield now just incase its a REALLY STUPID question).

Cheers btw dude for the work on the ROM.
[X Style (Pure) Android Development] Hashbang173:
Was it my test kernel that caused the bootloop? I suppose it could have only worked on my device due to the mix of bootloaders and radios I currently have installed
[X Style (Pure) Android Development] mrvanx:
Hi dude, no I haven't had a go with the test kernel yet. My device has a tendency to crap out just as I get the 15% battery warning without shutting down. I think it corrupted something as a result...the only thing that fixed the boot loop was a default factory wipe and reinstall of everything.

I'm on the nightly from 29th January, just got back up and running.

Shall I wait before I test the kernel?
[X Style (Pure) Android Development] bushibaa:
It booted. Camera and torch are not working.

I'm on self-build of official source.

Dmesg attached.

My bootloader is 0xA050, radio 0x3(xt1570 flashed retla_nph25.200-15 bootloader and gpt)
[X Style (Pure) Android Development] Breezeblocks:
Hi, I've been trying to install LineageOS for the past few hours but to no avail. I keep encountering an endless boot screen after flashing the LineageOS zip and GApps zip through TWRP. I followed all of the instructions on the site and even did a test run with a different phone before I tried with my primary. The first time I did it, I waited about half an hour before I shut it down and re-flashed it. Second time I waited an hour and now I'm on my third attempt approaching an hour.

Things I've tried:

-Flashing an earlier nightly.

-Formatting and wiping through TWRP.

-Reflashing TWRP and then going from there to flashing LineageOS and GApps.

Not sure if it's an issue or not, but I already had the official 7.0 update installed. I recall reading something about modem issues, but I also read that you can still flash custom roms regardless. Any help would be appreciated, thanks!
[X Style (Pure) Android Development] dzidexx:
https://xdaforums.com/moto-x-style/general/custom-roms-nougat-modem-t3733105
[X Style (Pure) Android Development] Breezeblocks:
Awesome thanks so much, worked like a charm.
[X Style (Pure) Android Development] kb8no:
Wrong forum