yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] 12vlt:
update, I have no cell data on the 8-11 build, going to try and revert to the earliest build available just to be safe. Has anyone else had this problem?

Edit: Reverting to the earliest build available solved my problems.
[X 2014 Original Android Development] k4tfish:
no, dirty flashed though.
[X 2014 Original Android Development] Gus Ghanem:
September 8, 2017 Build dirty flashed fine, but no September Security Patch (?). Those of us who dirty flash the update obviousely can't tell if there's a problem with the Setup Wizard, since it was completed on an earlier build.
[X 2014 Original Android Development] BootloopedMillennials:
So does LineageOS not use GLONASS for a gps fix? SatStat show Glonass satellites but they are not getting a fix. Has anyone experienced this?

---------- Post added at 02:05 PM ---------- Previous post was at 01:50 PM ----------

And I found the reason. Disappointing.
[X 2014 Original Android Development] Gonzalo8500:
Hi, is the Setup Wizard bug solved? I am planning on flashing this rom, in fact I was about to but then I read about that bug on clean installs, I am running stock rooted 6.0 and want to give LineageOS a try but I will need to do a clean install and need to know if there is a bug.

Thank you guys, its my first time posting here on xda but I have been reading for years :)
[X 2014 Original Android Development] RockyTV:
The latest (September 8) build has two commits related to SetupWizard. I don't know what was the issue but maybe it was fixed?
[X 2014 Original Android Development] natalia86:
Did a clean install and everything's working great!
[X 2014 Original Android Development] Gonzalo8500:
Just flashed the Septemer 8 build and so far so good, its snappier than ever and haven´t encountered any hiccups or bugs yet, although I would like to get the google dialer i had before, the Pixel style one, but I don't remember how I got it working on MM haha.
[X 2014 Original Android Development] Gus Ghanem:
Which Gapps package did you use? Do you mean this dialer: https://www.apkmirror.com/apk/google-inc/google-phone/

Open Gapps Stock would replace the Lineage dialer with the Google one, or you can install the APK and set it as the default dialer. To install an APK, you need to go to Settings, Security, enable Unknown sources.

Edit: You can only install APKs for ARM on this phone.
[X 2014 Original Android Development] Gonzalo8500:
I used the mini package from opengapps, for ARM since thats what this device uses.

I will try to download the Pixel version on an APK, I had it on stock MM, just not the official one since its not compatible with this phone.
[X 2014 Original Android Development] Gus Ghanem:
Doesn't Google Phone show up for you now in the Play Store? Anyway, version 11 should work, the APK is the official unmodified Google app.
[X 2014 Original Android Development] RockyTV:
https://play.google.com/store/apps/details?id=com.google.android.dialer

Doesn't it show up for you on the Play Store?
[X 2014 Original Android Development] Gus Ghanem:
Yes it does, and it allows me to install it. i think there was a time when it wouldn't.
[X 2014 Original Android Development] RockyTV:
Might have been the time where Dialer wasn't available to everyone.
[X 2014 Original Android Development] raynayx:
Can we hope for an Oreo for our beloved moto x 2nd gen?
[X 2014 Original Android Development] Gus Ghanem:
There was one alpha released, which boots but is unstable, with sudden reboots, and some functions not working. I think it's a matter of kernel drivers, if they can get all the hardware working properly.
[X 2014 Original Android Development] tbtregenza:
Dirty flash earlier today without a hitch. Seems to be running great and potentially fixed a WiFi issue I was having previously with the 9/1 build.
[X 2014 Original Android Development] don537:
Does anyone know if this rom is compatible with Verizon? I flashed it awhile ago and my 4g would continuously connect and then disconnect... 3g wouldn't work at all and would just say no service in certain areas...
[X 2014 Original Android Development] tbtregenza:
Works without issue for me.
[X 2014 Original Android Development] don537:
Ok thanks... I guess I'll just flash the latest version and see what happens... May have been a bug in the previous one.
[X 2014 Original Android Development] don537:
Just installed... This is what I mean... the 4g suddenly dropped for a little bit and then came back. I'm stuck as to what's going on? I really don't want to keep running MM as it's outdated, if anyone has anymore suggestions it would be much appreciated.
[X 2014 Original Android Development] Gonzalo8500:
Yes thank you, I downloaded that version which is now available for Nougat I guess, before, on MM stock I had to download the apk from chrome

What happened was that I didnt enlable it as default and when I opened the Google Dialer I downloaded the app would close and when I opened it again it seemed like it worked ok but in reality it was opening the default one, weird.

Anyways I enlabled the google one as default and disabled the stock one and it works flawlessly now.

Thanks guys :)

---------- Post added at 09:52 AM ---------- Previous post was at 09:47 AM ----------

Yeah I noticed that yesterday when I had wifi on, cell signal would suddenly drop to 0 and come back, but since I had wifi on at home it wasnt a problem, when Im on the street or at work without wifi cell is always at max signal though
[X 2014 Original Android Development] don537:
Really? Unfortunately for me when I go out somewhere my cell signal will never stay stable at all... It will continously disconnect and reconnect every few minutes... Back on MM rom for now... Thanks for the help though
[X 2014 Original Android Development] Gus Ghanem:
September 15, 2017 Build dirty flashed fine, but still no September Security Patch! Google was a little late releasing this patch.

Changes are always here: https://download.lineageos.org/victara/changes/
[X 2014 Original Android Development] Casper1982:
wich gapps recommend?
[X 2014 Original Android Development] Gus Ghanem:
Open Gapps are always the most up-to-date, Pico installs only the Play Store, then you can install any apps you want from the Play Store. You can find out what all the different packages contain here: https://github.com/opengapps/opengapps/wiki

OR

You can use Delta Gapps to replace the Lineage apps with the Google Play Store versions (you need at least Base Gapps to get the Play Store).

Don't mix Open Gapps and Delta Gapps, or you might have problems. When you flash Open Gapps in TWRP, it will remove any Gapps you may have flashed before.

https://xdaforums.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368

Lineage/AOSP apps that can be replaced (using Delta Gapps, or Open Gapps Stock which will add a lot of bloat)

Browser

Calculator

Calendar

Camera (only Google Camera 2.7.010 works on this phone)

Clock

Contacts

Email

Gallery

Messaging

Music

Phone

Keyboard

Text-To-Speech

(Trebuchet Launcher is replaced by Open Gapps Stock, but not by Delta Gapps)

This way you will have a clean, minimal system, without duplicate apps.
[X 2014 Original Android Development] shawndak:
9/1 Build just boot looped on restart from dead battery. I've seen this on earlier builds but it somehow sneaks back in. Battery life was about 3.5 OST, not bad. Biggest downfall with this phone is the 30% shut offs.
[X 2014 Original Android Development] papsr6:
The last build is very good.

Stable quick and snappy.

Battery looks very very good.

I need tume to be sure for the battery and i will come back again.

Need to make phone app more quick at launch ambiend desplay more snappy (some time not responce to my hand )

And the internet browser not have force zoom like all other browsers and not full screen view like gelio.

Many thanks to developers.
[X 2014 Original Android Development] bernardo94:
Hi all, i want to flash a custom rom in my moto x, anyone plz tell me about bugs, lags, battery life (hours on and SoT) and another thing important? Thanks
[X 2014 Original Android Development] GustavoAvellar:
I'm running 20170811 build. Nothing to complain. I advise you to read the last few pages of this topic.
[X 2014 Original Android Development] dego_:
Do you mean it's better compared to previous builds?
[X 2014 Original Android Development] papsr6:
I think is litle bit faster.

Is
[X 2014 Original Android Development] dego_:
And is battery life better?
[X 2014 Original Android Development] papsr6:
I think is the same.

Need about two days to take about 5 hours SOT and 20 hours battery time. You take a full day very easy.
[X 2014 Original Android Development] Casper1982:
Someone who is in the last build, how's the battery going?

Do you recommend staying in stock 6.0 or switching to a custom rom with android 7.1.2?
[X 2014 Original Android Development] trancid:
With this LineageOS ROM you get Android 7.x and good battery life (easily 24H with a full charge (but I am not a heavy user... mainly mail / reddit / twitter); is better when I compare it to official ROM Moto).

Give it a try... you won't regret it.

:)
[X 2014 Original Android Development] Shubham.3.96:
Does this still have the bootloop issue when the battery dies around 30%? I moved from LOS to CM13 back in July when multiple builds started bootlooping when the battery died. Considering checking this out again if its been fixed.
[X 2014 Original Android Development] Gus Ghanem:
I've had my phone for about 2 years now, an XT1097 RETCA, and I've used almost every version of CM and LineageOS, and I've never experienced the battery issue that I've seen a lot of people have. I always get the 15% warning, and I can always let the battery drain to 1% until it shuts off normally. I thought maybe some units or variants were defective, but it seems to only happen under certain conditions. One thing I can suggest is reflashing the latest full factory stock firmware, then starting over, although this may not solve the battery issue.
[X 2014 Original Android Development] thousandecibels:
May be, the battery just die out depending on the number of charge cycles it goes through.

Hence, the more it completes a cycle - the more it degrades. It all depends on usage too.
[X 2014 Original Android Development] InnerSanctum:
Would like to know about that too!
[X 2014 Original Android Development] k4tfish:
with security in mind, an outdated stock image is no option.

my battery works well with LOS - no issues yet.
[X 2014 Original Android Development] Gus Ghanem:
September 22, 2017 Build dirty flashed fine, finally has September 2017 Security Patch!
[X 2014 Original Android Development] BootloopedMillennials:
Flashed the Sep 22 build flashed fine too.

The combo of this device with LineageOS, Magisk, and MicroG is perfect. It flies, feels smoother without the Google services. Battery life hasn't been much of a gain 15mins or so extra SOT. Same 8 percentage drain overnight. Wish there was something to be done about the camera overall, not referring to the camera with LineageOS but in general.
[X 2014 Original Android Development] shawndak:
It went away for a while but came back on an Aug build. Its a real pain!
[X 2014 Original Android Development] raynayx:
Looks like the link to yesterday's build is broken. There's a 404 error on the page.
[X 2014 Original Android Development] natalia86:
I've just checked and I see the link on the website. For the past couple of updates, I haven't been able to download them through settings, but had to go to the website and find the file myself.
[X 2014 Original Android Development] Casper1982:
Same here. it seems that ota from settings does not work the download .

---------- Post added at 12:12 ---------- Previous post was at 12:12 ----------

Same here. it seems that ota from settings does not work the download.
[X 2014 Original Android Development] Gus Ghanem:
OLED burnin protection in the next build, not that I can see it on mine:

https://review.lineageos.org/#/c/187647/

New Blog entry:

https://www.lineageos.org/Changelog-14/
[X 2014 Original Android Development] papsr6:
Clean flash and loop setup wizard again.

The setup wizard stop working and ask me to restart again.

I dont know why all the time have this issue lineage.
[X 2014 Original Android Development] RockyTV:
What GApps package are you using?
[X 2014 Original Android Development] papsr6:
Open gapps pico arm 7.1.
[X 2014 Original Android Development] Casper1982:
how to put selinux in permissive mode?

without using any app?
[X 2014 Original Android Development] Bristow Xavier:
:confused:I'm currently in 20170915 ROM....

I'm unable to update to 20170922, showing an error message "the download failed, please check your internet connection and try again....
[X 2014 Original Android Development] pokereth:
It sounds like your download might not have completed correct. Possibly this was caused by a faulty connection link to the internet.
[X 2014 Original Android Development] BootloopedMillennials:
I imagine it's too late for many Moto Xs. I can only see it on mine on certain backgrounds.
[X 2014 Original Android Development] Gus Ghanem:
Yes I figured implementing this feature after 3 years (this phone's age) would be kind of too late for this phone, but I guess it may "save" other, newer phones from now on. I've never seen the effects of burn-in before, wether on a phone or tablet or TV, but I'm not a heavy user; most people probably get rid of their devices before it starts to happen anyway.
[X 2014 Original Android Development] Bristow Xavier:
How to make SuperSu as superuser instead of privacy guard
[X 2014 Original Android Development] Jaytn:
Honestly I don't think it's gonna help much. If all it's doing is moving the icons around a bit, that is only going to prevent (or delay / smear out?) burn-in in the form of "ghost" images of those icons on plain backgrounds. That's not the burn-in I see on my phone, or at least I can only make it out if I'm REALLY looking for it (including deliberately using a background I can see it on). What I see is rather the strip of the navigation bar being a slightly different shade on even backgrounds. I guess you might call that "reverse" burn-in since it's the pixels in the navbar constantly being off and thus not burning in as much as the rest of the screen. So moving around the icons in the navbar doesn't change the fact that the navbar is still there and those pixels are off.

I'm not complaining about the burn-in, it really is a non-issue even after several years now; and I'm not saying they shouldn't have implemented this, it's better to try to do something than nothing - I'm just saying that neither do I think this is going to help much with, nor do I see a solution for the IMO more prominent (though still subtle) burn-in issue.

//edit: Re-reading the code review, I basically agree with Danny Baumann's opinion in that it won't really help, but doesn't hurt either.
[X 2014 Original Android Development] R4to0:
My phone just shutdown itself at 68% battery and now went in bootloop AGAIN... Here go another reset
[X 2014 Original Android Development] linckandrea:
You probably have to change the battery,

I recommend you back to stock rom

the bootloop after the sudden shutdown has not yet been resolved ...:rolleyes:
[X 2014 Original Android Development] dagmoller:
After last update (09-22) google now was enabled and there is no option to disable that...
[X 2014 Original Android Development] dego_:
you mean you want the now on tap to have back?
[X 2014 Original Android Development] dagmoller:
I want to disable google now... disable pull right on homescreen...
[X 2014 Original Android Development] Gus Ghanem:
It depends on the Launcher, but usually long tap on an empty space on the Home Screen, then tap settings...
[X 2014 Original Android Development] dagmoller:
There is no option to disable google now or feed...
[X 2014 Original Android Development] Gus Ghanem:
If you don't want the Google App/Now/Search, you have to clean flash the ROM and use OpenGapps Pico, or Delta Gapps Base.
[X 2014 Original Android Development] zahidm:
Each and every ROM for Moto X2 have bugs, tested all of them, initially you can't find bug but when using for some days bugs show up, Developers are working hard but at last we have to revert back at stock... Lineage was the only one those bugs are acceptable others all are to date useless...
[X 2014 Original Android Development] Gus Ghanem:
I read it on Reddit! The signing machine was down, so they couldn't sign the builds even if they succeeded, so they couldn't release them...

https://jenkins.lineageos.org/job/android/6430/

EDIT:

A third unofficial build of Lineage 15.0 (Android 8.0 Oreo) was released; it's almost fully functional, but lacks most current Lineage features. It seems stable enough, and I didn't get any error popups, but I only used it for several minutes before going back to 14.1.
[X 2014 Original Android Development] Gus Ghanem:
The new official 14.1 Build is released as October 1, 2017 Build

https://download.lineageos.org/victara
[X 2014 Original Android Development] RockyTV:
What do you consider as "fully functional"?
[X 2014 Original Android Development] Gus Ghanem:
Basically, that all of the phone's hardware is working, you can make and receive calls and SMS, play audio and video, camera works, apps install and work as they're supposed to, wifi and bluetooth work, etc.
[X 2014 Original Android Development] Gus Ghanem:
October 2017 Security Patch is here!

https://download.lineageos.org/victara
[X 2014 Original Android Development] raynayx:
How's battery life?
[X 2014 Original Android Development] Gus Ghanem:
I'm a very light user, and my phone is idle most of the time, it usually lasts about 2 days maximum, I remember an earlier time when it would go for 3 days on Lineage. I've never checked screen-on time.
[X 2014 Original Android Development] Gonzalo8500:
I found that my moto x has been awake for a couple of days, doze seems to not have been kicking in and I can notice it on battery life, right now its at idle havent touched it in an hour or so and it has 30% and estimates that I have about 5 hours of use left, I dont know why but it is always awake, I must have a wakelock or something I guess.

I flashed the last build and it keeps happening, I have cleared the cache and rebooted and it is still always awake, dont know why.

My email accounts have been set to update every hour and I dont use any new app that I didnt already use before this happened...

I guess that I will have to clean flash to get this better, I am a light user and dont really have much SoT at the end of the day but my battery is usually depleted anyways, when I use it I would say it even lasts more!
[X 2014 Original Android Development] nickjf20:
I've had the phone boot loop for a second time now!

Phone dies at around 50% out of the blue and then will not boot. Gets stuck on the animated boot logo.

This is using two different builds about 1 month apart
[X 2014 Original Android Development] dego_:
Do you use Greenify?

---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------

Sounds like you need to calibrate your battery. I would like hear what others will suggest.
[X 2014 Original Android Development] Gonzalo8500:
No because I didnt see good results using it in the past but I will give it a go if necessary, do you recommend it?
[X 2014 Original Android Development] dego_:
I use it since I first time rooted the phone. I had a chance to compare it with battery life without Greenify and the difference is noticeable. When the phone is idle Greenify makes the battery drain around 1% overnight.
[X 2014 Original Android Development] Jaytn:
I agree. Keeping in mind that this is a 3-yo phone (and thus 3-yo battery) by now, it is expected to get worse. And since it had these shutdown issues from the beginning, I'd only expect them to get worse. I looked a bit into the logcat during a bootloop, and to me it looks like it corrupts something important, thus I doubt it is related to any build really (except the devs could build in protections, but I doubt that).

What has helped me is to "treat" my battery well. I try to avoid partial charging and periodically do a full deep charge. For that I drain the battery as much as possible (so the charging indicator says 1%) and charge it fully while the phone is turned off. (If you wanna call that "calibrating", fine.) Fully discharging may be hard to do since it turns off during boot, then I boot into recovery, it will usually still do that.

As for the boot-loops, I think the best first step is to do the above to avoid the random shutdowns in the first place. Secondly, in my experience the bootloops happen not on a random shutdown, but rather on shutdowns during boot - I may be wrong there, but to be safe I avoid turning the phone on again after a shutdown before I can get to a charger. Thirdly, one word: Backups. Make it a good habit to always have a recent (TWRP) backup. That way when you do encounter a bootloop, you can just go back to the most recent backup and shrug it off.

Hope this helps. With the above, I only have issues if I don't stick to those rules. I understand it's a bit cumbersome, but to me, the alternative is buying a new phone (or at least a new battery)
[X 2014 Original Android Development] linckandrea:
Flash stock(only rom haven't bootloop issues after

prevent shutdown)

I fix this problem changing battery
[X 2014 Original Android Development] nickjf20:
Yeah, I need to change the battery again really! I've reverted to the stock ROM and all is well for now.

The first battery lasted 2 years, but the eBay battery has barely lasted one :(

I do wonder why the stock ROM has no issues with boot loops after unexpected power failure.
[X 2014 Original Android Development] Gus Ghanem:
Friday The 13th October 2017 Build + Open Gapps Stock + Pixel 2 Launcher. I clean flashed these from Moto stock 6.0. October 13 Open Gapps Stock installs the "old" Pixel Launcher 7.1; the new launcher updates the old one (it's on APK Mirror). Pixel 2 Launcher supports Android 5.0 - 8.0, but probably has less options on Lineage/Android 7.1. There's no option to reposition or disable the search bar.

https://www.apkmirror.com/apk/google-inc/pixel-launcher/
[X 2014 Original Android Development] LexX-V:
Unfortunately I had a need to enroll back to CyanogenMod 13.0 (6.0.1), because IR-sensors work bad through copule of days after install. Someone have this problem too? How I can catch the logcat or something else with this problem? Maybe this can be found in kernel log?
[X 2014 Original Android Development] k4tfish:
which bugs are you facing on this rom?
[X 2014 Original Android Development] LucaProdan:
I have an issue with proximity sensor on N and O roms... Isn't that happening on Marshmallow?
[X 2014 Original Android Development] papsr6:
How is the battery of the last version?
[X 2014 Original Android Development] dego_:
I don't think it changed over few last builds.
[X 2014 Original Android Development] papsr6:
I am using rr 5-8-5 final for now and is going very very good.

But i like lineage and wait a good battery version.

Rr leave you to optimize the google play servises and i feel the battery life is best.
[X 2014 Original Android Development] dego_:
By the way, how do you optimize google play services in RR? Maybe that's something you can do in LOS as well.
[X 2014 Original Android Development] papsr6:
Rom let you to select optimize google services on battery optimization settings
[X 2014 Original Android Development] dego_:
It's a basic functionality of a stock android since 6.0 or even earlier.
[X 2014 Original Android Development] BootloopedMillennials:
it was never possible to optimize google play services on stock android.

Anyway there is a Magisk module if I remember correctly that allows you to. I assume everyone is using Magisk by now. There is no reason not to imo. It passes SafetyNet.

Systemless Xposed is working fine on this rom too.. It will break SafetyNet nothing can be done about that. Not even Magisk can help there.

The last two builds or so I can't get Arise/Viper4Arise to work. Gave up on that.