yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] tbtregenza:
This is a noobish question I'm sure, but I'm hoping someone can point me in the right direction.

I'm all set with the latest LineageOS and Stock Gapps. Been running great for months. I update the nightly every week.

I'm starting to run out of space and am considering flashing a different Gapps package. I tried to install the Aroma package from recovery but it didn't work. What are steps I need to take to replace stock Gapps with a new Gapps package?

Does this require a full wipe and redo?
[X 2014 Original Android Development] Gus Ghanem:
Are you talking about System Partition space? Because that's where Gapps are installed when flashed by recovery. I think Aroma never worked with this phone's TWRP recovery.

One option is using a gapps-config file with Open Gapps to install only the apps you want, while removing their Lineage equivalents:

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options

As I have done in the picture.

The other option is to use Delta Gapps to download individual apps which will replace the Lineage apps when flashed.

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

It is best to clean flash LOS and Gapps by wiping System and Data, to avoid any problems when trying to remove and replace apps. Some apps need to be flashed with the ROM, when replacing stock apps, such as Keyboard...

I don't recommend mixing Open Gapps with Delta Gapps.

EDIT: I attached an example config file that you can edit (mainly for Open Gapps Stock)
[X 2014 Original Android Development] tbtregenza:
Ok...I figured a full wipe would likely be needed since they would conflict. I was trying to avoid that and just flash "over" the sock open Gapps but I think I knew deep down that that wouldn't work.

Once I work up the courage I will wipe and reflash using Delta Gapps, that sounds like the way to go.

Thanks for the help!
[X 2014 Original Android Development] Gus Ghanem:
I'm not quite sure if you can downgrade the Open Gapps package by just flashing a smaller one, which will then remove the extra apps. When you update or install apps from the Play Store, they are installed to the Data partition, which will reduce storage space available to you, but I doubt apps really use up that much space.
[X 2014 Original Android Development] Gus Ghanem:
I just did a clean, minimalist install of Lineage October 20, 2017 Build with Open Gapps Stock, using a gapps-config file.

EDIT: There's an entry in the config file that enables Google Assistant.
[X 2014 Original Android Development] oblib__:
lost active display

I recently installed lineage OS after a full wipe. When I started, the waving gestures (active display) were working, and I could see the IR sensors light up. However, now that everything is restored, I seem to have lost all my gestures. The settings are all on. I tried turning them off, restarted the phone and then turned them on again, and still nothing. The infrared lights do not light. Any ideas how to get this feature back?

Hmm, now it's working again so never mind, I guess?
[X 2014 Original Android Development] oblib__:
Looks like my problem was that in AOSP-land, active display only works while the screen is locked. I usually like to bump my security settings up to "don't lock screen for 30 minutes" which meant Active Display was usually disabled. This is different than Moto's display preferences. So here you go, future person to have this same issue :)
[X 2014 Original Android Development] RockyTV:
They have a mismatching description for the ambient display gesture, if you disable it ambient display stops working completely, while the gesture's description doesn't tell you that.
[X 2014 Original Android Development] BootloopedMillennials:
Ambient Display is very bad on LineageOS in comparison to stock. Far too sensitive and far too battery draining, it's worthless. At least on LineageOS for the Moto X 2014.

I'm always accidentally turning the screen fully on because of it. I usually walk with the phone in my hand, it's constantly turning on ambient display, which results in the previous issue. These were never an issue with Moto Display. I miss it.
[X 2014 Original Android Development] dagmoller:
You can try Ambi-Turner from playstore: https://play.google.com/store/apps/details?id=com.compass.ambiturner

It have some tune options...
[X 2014 Original Android Development] Bristow Xavier:
i am having a problem in substratum. when applying a theme or something, it is required to reboot the device for the applied changes to take affect...

but when i was in Lineage 15.0, there was a "update & build" option available.

but in 14.1 i am having only two options...

pls help...i am fed up of the restarts...

(i roll back to 14.1 due to the volume problem)
[X 2014 Original Android Development] RockyTV:
There's nothing wrong with Lineage or substratum. The reason you need to restart to apply a theme in 14.1 is because Nougat (Android 7.1) didn't have a built-in OMS-like theme service, which substratum makes use of in Oreo (Android 8).
[X 2014 Original Android Development] LexX-V:
Yes, it doesn't. But I talked about IR-sensors, not proximity.
[X 2014 Original Android Development] LucaProdan:
Sorry, my bad
[X 2014 Original Android Development] dego_:
I started having weird issue. The phone can shut down at around 50% of charge and won't boot. When I plug the charger it shows that battery is 1% on the turned off device. Then I charge it to full, turn it on and everything is fine until the issue repeats once in a week or two. Any ideas folks?

---

UPDATE: looks like it's a hardware problem https://xdaforums.com/moto-x-2014/general/tip-battery-calibration-fix-powering-t3598942
[X 2014 Original Android Development] InnerSanctum:
It is hardware indeed, had the same problem and changing the battery solved 100%.
[X 2014 Original Android Development] 6HONG:
thanks for your work
[X 2014 Original Android Development] trancid:
Does anyone use Google Assistant on this ROM? I use it (enabled by using the enabler - Magisk Module) but I am wondering why the setting "from any screen / app" is greyed out on my Moto X 2014. As consequence, I can only use the Google Assistant from the home screen; not when the screen is off or from within another app. If I do remember well, I got that setting enabled in the past and had this working (well, at least the "OK Google" behavior). Anyone more luck on this ROM?
[X 2014 Original Android Development] Bristow Xavier:
I can't use Tez ( payment app by Google ) in my Device

it says "your device may not be secure"

please help...
[X 2014 Original Android Development] kedar a.k.a. 3K:
Try cloaking root via magisk and try again
[X 2014 Original Android Development] Bristow Xavier:
currently I'm in SuperSU Sr5
[X 2014 Original Android Development] kedar a.k.a. 3K:
Can't you cloak root for a specific app ? I think there's an xposed module for that
[X 2014 Original Android Development] dego_:
How did you get that navbar?
[X 2014 Original Android Development] huatz84:
I think he uses THIS one.
[X 2014 Original Android Development] RockyTV:
Isn't that Android Pay?
[X 2014 Original Android Development] tbtregenza:
Anyone else having problems downloading the 11/11/17 nightly?
[X 2014 Original Android Development] Gus Ghanem:
I just tried from Canada's Capital, no problem:

https://mirrorbits.lineageos.org/fu...eage-14.1-20171111-nightly-victara-signed.zip
[X 2014 Original Android Development] Bristow Xavier:
No, its technically the Indian version of Android pay

currently Android pay isn't compatible in india...

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

it just works fine now, after the 11/11 update...

anyway thanks for your advice...:good:
[X 2014 Original Android Development] tbtregenza:
Worked today. Weird.
[X 2014 Original Android Development] nuke01:
With nightly build 2017-11-11 my microphone is only working in speaker mode, not with bluetooth headphones and also not in "normal" mode.

Last Monday, while being line 2017-11-03, I remember having a normal phone call. Before that it also seemed to not work some times?

Anyone knows what I can do? I tried to install magick module to fix microphone volume, but that didn't help, now I disabled it.

Testing my microphone with a recording app works.
[X 2014 Original Android Development] ATGardner:
Since about a week or two ago, my phone started hanging completely (when I need to shut it down with a 10-seconds power hold), or randomly restart itself occasionaly. I tried updating to 11-11, after a system wipe, and today I did a full wipe (including data). I thought I fix the problem, but even after the full wipe I keep getting those hangs and crashes.

Anybody else is having similar issues lately? Or maybe has any tips on how I can try and debug this, and find out if maybe a specific app is causing it?
[X 2014 Original Android Development] zahidm:
Go back to stock once
[X 2014 Original Android Development] ATGardner:
Is there an easy way to go back to stock? A link to stock image I can flash with TWRP?
[X 2014 Original Android Development] zahidm:
Yes there is flashable zip available at XDA

---------- Post added at 09:07 AM ---------- Previous post was at 09:05 AM ----------

And a thread below link,

https://xdaforums.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121

---------- Post added at 09:08 AM ---------- Previous post was at 09:07 AM ----------

Remember don't execute OEM LOCK command
[X 2014 Original Android Development] nuke01:
Now I'm back on 2017-11-03, I wiped data, system & cache. Microphone in call works again, also with BT headsets.

When I upgraded to 2017-11-11 I did it via an OTA update I got. Maybe it would have needed a full wipe?
[X 2014 Original Android Development] ATGardner:
no luck :(

Thanks for the tips and links. Today I reverted to stock, rebooted, then back to bootloader, installed TWRP again, full wipe and re-installed LineageOS 11-11 with OpenGapps 11-13.

I had a crash midway when it was reinstalling my old applications, and after it finished, and I was in the middle of logging into the various apps and services, had another random crash. So I don't think it worked, sadly. :(
[X 2014 Original Android Development] zahidm:
Why you are getting trouble ? Are you at latest TWRP recovery?
[X 2014 Original Android Development] zahidm:
I would suggest you to use latest TWRP and then don't restore your app backup, just skip all in setup wizard, setup new device...
[X 2014 Original Android Development] huatz84:
Try clean flash and don't restore apps. Use pico gapps only not the full one.
[X 2014 Original Android Development] ATGardner:
Thanks for the tips. Yeah, I think this will be my next, unavoidable, step. I'll just install OS + gapps, and not restore my google backup. It will be a pain to install everything manually afterwards, but I'll manage.

What might be the problem, though? Are there any known apps that may cause this? Because I am afraid I will manually install my apps like before, and end up with the same original problem.

Or maybe there's something specific to look for in logcat, right before my phone crashes, to somehow identify the culprit?
[X 2014 Original Android Development] zahidm:
None of the app in ROM is culprit, there might be some app in your backup
[X 2014 Original Android Development] Gus Ghanem:
Jenkins is down, there are no builds happening:

https://jenkins.lineageos.org/

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

The "spheres" should be blue or pulsing blue.

https://status.lineageos.org/

It's building again, check links for status...
[X 2014 Original Android Development] BootloopedMillennials:
It appears my 2014 is on it's final breaths, battery life has become abysmal. It's not rom related and I won't be buying an aftermarket battery to keep it going. Anyway wanted to post final thank yous to [MENTION=2385005]invisiblek[/MENTION] and the whole LineageOS team for keeping this phone alive for as long as they have.

:good:
[X 2014 Original Android Development] trancid:
Same here (I have it for 2 years and 3 months now), but I do get good results using Naptime and Amplify (which requires the Xposed framework). Without those optimizations, my battery life is terrible as well. But now, running this ROM for several months, I manage to get a full day without any problem. But it is a pity that we need to apply those kind of modifications.

:)

PS: which new phone do you have in mind?
[X 2014 Original Android Development] dego_:
I want to join saying thank you to all who made it possible to run a stable build of LOS 14.1 for such a long period (I mean devs and enthusiasts who tracked and posted bugs and shared their experience/solutions/tricks on this thread).

By the way there's a great tread dedicated to discussing the "what should be my next phone" topic. Personally I'm thinking about Galaxy S8, since it's shape and how it lays in a palm reminds me a good old Moto X 2gen. Hope there will be a LOS stable build made in a year or so, since I'm a bit addicted to stock Android.
[X 2014 Original Android Development] icaptainkidd:
Hello,

I installed it but my phone freezes randomly and reboot. I use lineage-14.1-20171111-nightly-victara-signed and open_gapps-arm-7.1-stock-20171121 and addonsu-14.1-arm-signed and twrp-3.1.1-0-victara .
[X 2014 Original Android Development] huatz84:
Flash lineage ROM then gapps (Use pico gapps to minimize any conflicts and less bloatware). Reboot your phone. After finish booting then reboot to recovery and flash root apps (superSU or magisk - your choice).
[X 2014 Original Android Development] icaptainkidd:
It caused by the gapps?
[X 2014 Original Android Development] Bristow Xavier:
all same except , SR5 SuperSu is used instead of that root method..no problems for me till now...;)
[X 2014 Original Android Development] huatz84:
Maybe..try pico gapps. For root apps,magisk is my favorite. It's great and powerful.
[X 2014 Original Android Development] BootloopedMillennials:
Mine is beyond software tweaks making a difference.

Will keeping using my N6 or picking up the original Pixel.
[X 2014 Original Android Development] dagmoller:
Someone getting bootloop after facebook app update?
[X 2014 Original Android Development] zahidm:
No after update FB no issues
[X 2014 Original Android Development] dagmoller:
I've uninstalled facebook app and bootloop stops... Installed facebook again and bootloop is back... So, no facebook installed at moment...
[X 2014 Original Android Development] nuke01:
Today I did an OTA update from 2017-11-03 to 2017-11-25. Phone is working with BT Headset. Thx
[X 2014 Original Android Development] rupalazzi:
What version of LOS did you experience this issue in first place? Just asking cause my wife's phone started presenting the same issue she is running 01/09/2017 nightly.

Right now I'm downloading 25/11/2017 nightly to try fix the issue. But I think this problem might be related to an app update that is causing trouble with the OS.
[X 2014 Original Android Development] ATGardner:
I am currently running the 11/11/2017 nightly.

I finally did a full wipe, and restarted my phone without restoring the cloud backup. It worked well for over a day, and then I started re-installing apps slowly. I am %99 sure I found the culprit - When I stalled Facebook, I started having those crashes/hangs/reboots almost immediately. I uninstalled it, and everything is working fine again.

I admit I am running the alpha build of facebook, so I don't expect it to happen to everyone. But anyway, this method of slowly restoring my phone from scratch worked well for me.

Thanks to this forum for giving me some helpful tips.
[X 2014 Original Android Development] zahidm:
BTW i tested all ROMS and finally at AEX 5.0 12/11, Please try that too
[X 2014 Original Android Development] rupalazzi:
Thanks, I read your reply before flashing my wife's phone. So as a test I uninstalled Facebook, just to see what would happen... Guess what, phone started working just fine, no issues at all.

Again thanks for the tip. :good:
[X 2014 Original Android Development] TCattd:
My daughter's phone is having the same issues as some of you have described.

Random full reboot (not soft reboots).

Here's the last_kmsg from the latest full reboot: https://pastebin.com/CfZw7wBS

Hope that can be of any help, [MENTION=2385005]invisiblek[/MENTION]

Her phone is on lineage-14.1-20171125 but, as far i can recall, this random full reboots happened as long as lineage-14.1-20171103 too.

LOS jira tracker is not open right now, so i can't create a new bug report for this.
[X 2014 Original Android Development] renzs:
My phone was rebooting with FB installed since the 1103 update. Uninstalled FB phone is OK. Clean flashed 1111 and manually installed FB from Google Play and was OK on 1st day but started rebooting the next day. Removed FB and phone ran OK.

Cleaned flashed 1125 and currently running without FB. So far so good...
[X 2014 Original Android Development] [Acme]:
Facebook kills ROM
[X 2014 Original Android Development] ATGardner:
Wow, so it is Facebook?

I thought it was because I'm on the alpha channel, but I see that it happens with the release channel as well. Is it something that Facebook is doing, or does it expose some specific bug in the ROM?
[X 2014 Original Android Development] [Acme]:
I'm using again LineageOS, lineage-14.1-20171125, with Facebook Lite and Messenger Lite and everything works fine.

(sorry about my english)
[X 2014 Original Android Development] zahidm:
Facebook has issue not the ROMS, even phone reset when facebook get in not responding Mode
[X 2014 Original Android Development] TCattd:
Well, after checking the logcat for some minutes, i thought the obvious: if it's a kernel panic, another kernel will avoid this issue?.

So i decided to install another kernel over LOS14.1, just to try something else. I have already cleaned up her phone from a lot of apps she had installed, trying to find the culprit.

First i tried to install Pop Kernel, but always got the same error when flashing the zip: "Updater process ended with ERROR: 1".

So i went with RealOne X, here: https://xdaforums.com/moto-x-2014/orig-development/realone-x-kernel-cm13-22th-fev-uber-5-2-t3320406 it's for CM14.1 but as LOS14.1 is the same codebase, and some people saying it works fine, i flashed it to test it.

I can happily report that after three days my daughter haven't experienced any random reboot (full or soft, none at all). Not a single reboot since i installed that kernel into her phone.

Yes, she has Facebook installed. And even with that app still in her phone, with the RealOne X kernel, the phone isn't crashing and full rebooting anymore.

My daughter is not with me right now, but when she comes back i can tell you exactly what governor did i set up (with kernel adiutor, and rooted with magisk for this to work).

Hope that help somebody else.

*** Edit ***

It's the intelliactive governor. Using kernel adiutor and rooted with the latest magisk (14.0 as today).
[X 2014 Original Android Development] Gonzalo8500:
Has something been done regarding battery management on the last update? Battery life is stellar, almost as good as when I originally bought the phone almost 2 years ago, its quite impressive.

I really want to thank the devs for the work they are doing :D
[X 2014 Original Android Development] trancid:
I am still struggling with my battery. Are you using and tweaks (NapTime, Amplify, ... or something like that)?
[X 2014 Original Android Development] RockyTV:
I can tell that most battery issues we face are due to our battery being old or having reached it's "lifetime". Seeing the commits that got into the last nightly, I don't think anything was done to improve battery life. Maybe it's a placebo or your battery is going crazy.
[X 2014 Original Android Development] trancid:
Well, okay. Anyway, I won't invest in a new battery as I don't believe I will keep the phone for another year. Will need to deal with it.

:)
[X 2014 Original Android Development] Jaytn:
Disclaimer: This is a great ROM and I like it ;)

Now that's out of the way, I have 2 little problems and was wondering if anyone has the same and/or can help :)

- Audio volume

It's hard to describe but sometimes the audio volume seems to glitch out. Sometimes it will just randomly get louder/quieter (while definitely nothing is touching the volume buttons ;) ) - seemingly switching between two levels (sometimes back and forth multiple times). And sometimes I have the feeling the volume doesn't really increase beyond ~60% ish - what I mean is it gets louder until the bar hits 60% and then it doesn't really change the volume anymore beyond that. Also sometimes it seems the quietest setting is still quite loud (eg when listening in bed), but then sometimes it isn't.

My feeling is that the volume controls somehow are "mapping" (for the lack of a better word) incorrectly - ie 1-100% doesn't really control 1-100% but rather the first 1-60% control 1-100% and the last 40% are irrelevant. (eg setting to 20% in reality sets to ~30% ish, 40% to 70%, 60% to 100%). And then sometimes it swaps between those two "mappings" which causes the volume glitching.

But that's just my tinfoil-hat-theory, maybe someone has some helpful input.

- Magisk + System Root

This is somewhat specific and maybe it's already well-known, then my google-fu isn't strong enough. My situation:

I never installed the lineage "addon-su", but the stock(-lineage) installation already allows for ADB root (through developer options), which is enough for me. But now I installed Magisk in order to play Mario Run and Animal Crossing, now ADB root doesn't work anymore, at all. The option in developer options is greyed out and I can't seem to manage to make Magisk give ADB root. I can open a terminal or ADB shell and get root via "su", but "adb root" doesn't do anything, which means I can't "adb remount". Through my google-fu I found setting "ro.debuggable" should make it work, and it did once; but that seems to reset on reboot and now it doesn't set anymore.

Maybe I'm just stupid, if so please tell me how much :D
[X 2014 Original Android Development] Febryan_Uchiha:
Turn off the audiofx and the sound glitch will be gone
[X 2014 Original Android Development] Jaytn:
Thanks. That's a shame, I was hoping to keep them on as I do like them. But I will try the next time this happens.
[X 2014 Original Android Development] dagmoller:
are you using f2fs?
[X 2014 Original Android Development] TCattd:
No.
[X 2014 Original Android Development] Bristow Xavier:
first time meeting a techy parent...hehe

anyway how old are you..?
[X 2014 Original Android Development] TCattd:
My daughter, the one with the X2, goes to the university already.

Not that old, i think ;)
[X 2014 Original Android Development] zahidm:
Try LOS 15 Latest I'm using from a week it's good
[X 2014 Original Android Development] Casper1982:
I have random reboots in the latest version

I come from lineageOS 15.
[X 2014 Original Android Development] [Acme]:
It is a Facebook issue.
[X 2014 Original Android Development] kedar a.k.a. 3K:
There were some crashes occasionally and the battery issue still persists , so I moved to mokee 7.1.2 (comes with xposed and substratum pre-installed) and it has been working flawlessly so far and it has daily nightly builds
[X 2014 Original Android Development] Vicalvi:
[MENTION=2385005]invisiblek[/MENTION]

I made a video of the problem I previously reported on bluetooth, if you can please take a look. Thank you :)

BUG:

Link video: http://i.imgur.com/6vNC3pl.gifv
[X 2014 Original Android Development] xb360:
Thanks for replying.

Maybe I need to wipe and flash everything to see if it can still work again.

---------- Post added at 09:31 PM ---------- Previous post was at 09:29 PM ----------

Same issue with my phone. The Hotspot can be detected by other device but can't join.
[X 2014 Original Android Development] cheffy11:
Location is missing from quick settings.
[X 2014 Original Android Development] hyppykeppi:
You can edit quick settings by pulling it all the way down and clicking the pencil icon.
[X 2014 Original Android Development] cheffy11:
Schoolboy error thanks bro :good: