yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] masterepiece321:
Hi all, I have recently gotten a oneplusone bacon unit. It's was preinstalled with LOS14.1 with opengapps and TWRP v3. All the wifi and bluetooth functionalities were working as expected.

I proceeded to upgrade with clean install on LOS 18.1 with the instructions on https://wiki.lineageos.org/devices/bacon/install by flashing lineage recovery and LOS 18.1 with opengapps. Then all the wifi and bluetooth are no longer working as expected. When I toogle to turn on Wifi/Bluebooth, it just toogle off again after few seconds.

I have tried to downgrade back to LOS 14.1 but all the wifi/bluebooth still not working. What could be the underlying issue on here? Is it due to the firmware or baseband version?

Thank you in advanced for your advise here.
[ONE Original Android Development] pbankar7:
Check mac and Bluetooth address in setting if there is no any address present then you should have at least backup of your phone's EFS partition to restore it for fixes.
[ONE Original Android Development] masterepiece321:
You're totally right. I couldn't see any mac address on settings. and here comes my next question as I haven't touched anything regarding EFS. With that said, I don't have any backup :(

From online search, it seems requires to flash back to Oxygen OS - https://xdaforums.com/t/guide-efs-partitions-what-they-are-and-how-to-get-it-back-if-lost.3307793/ - Is it good idea to do that and is there any where I can get the official Oxygen files? It's kinda too old at this stage.
[ONE Original Android Development] pbankar7:
I don't think after flashing oxygen os you will get back your EFS partition restored...

Link is here of all official stock roms (only last final builds) for bacon

15.48 GB folder on MEGA

165 files and 44 subfolders

mega.nz
[ONE Original Android Development] T53N:
I have the same issue. Now running the 20210902 version. It's pretty annoying. Sometimes the wifi remaind connected and sometimes wifi keeps disconnecting after being connected for only several seconds.
[ONE Original Android Development] Mt Everest:
Unfortunately I couldn't get it to work no matter what I did. So I resorted to clean flash. Well it's a hassle but it seems to be working "OK" now meaning wifi dropping is very rare, though it still happens sometimes. I suspect it might be because of my router..
[ONE Original Android Development] T53N:
I'll try a clean install. I thought it was a bad wifi signal from the router, so I bought a new AP. But still have the same issue.
[ONE Original Android Development] livingbeings:
Thank you for your answer,
[ONE Original Android Development] riahc3:
Where can I download Lineage 17.1 ? Seems more stable than this.
[ONE Original Android Development] npjohnson:
We don't keep old builds.

What about it is more stable? 18.1 runs just as well.
[ONE Original Android Development] deadrat-:
Firstly, thanks for making it possible for me to use my Oneplus One up until this day!

Since my upgrade from 18.1 I'm having issues with wifi and mobile network disconnecting and not automatically reconnecting.

Rebooting fixes the mobile network temporarily. Turning wifi off/on or selecting the network again fixes the WiFi issue.

This seems to be a common issue, but apparently not for everyone. Is there any way I can help fixing it?
[ONE Original Android Development] babbo96:
Hi guys. Do you know any kernel to use with LOS 18.1? One that supports kcal at least?
[ONE Original Android Development] npjohnson:
File a bug with logs like the wiki says.

Not really, especially not for 18.1.

Any external kernel would probably mess up zram and perf tunings. Be careful.
[ONE Original Android Development] deadrat-:
It's difficult to reproduce/to pinpoint when the issue happens and my phone isn't rooted. Shall I just make a bug report when it has happened during that day? Or is there a different type of bug report you can use?
[ONE Original Android Development] npjohnson:
Need a short snippet of when it happens, the wiki guide doesn't need root.
[ONE Original Android Development] brwntree:
Just wanted to quickly followup with I have successfully did just this very procedure but left out the 'set to none' in 17.1 thinking a basic swipe is the 'none' but beware it isn't. After rebooting for first time seemed ok but quickly started boot looping. So went into 'data/system' dir and removed the three locksettings.* file and then it booted stable from then on. In my case it was from lineos17.1-030421 to lineos18.1-101421 w/pico gapps dated today 19 & magisk-V23.zip but I had thought and updated twrp to 3.3.1-K1 k-version for the initial nandroid bkup & subsequent installs. Are the k-vers no longer recommended - should iget latest reg twrp-v352?
[ONE Original Android Development] npjohnson:
I'd just use lineage recovery - it _just works_ - and TWRP might be funky with encryption requirements changing as of 18.1 and such.
[ONE Original Android Development] seanwlk:
Hello,

how are you guys using the modem with LOS 18 ? On my end the SIM card is not detected and i tried to flash stock COS modem i had saved back in time but nothing. Is there a custom firmware somewhere in the lineage page i didnt find ?
[ONE Original Android Development] LoLoBear:
SIM card reader material issue ?

I had to change mine a few years ago because SIM card was no more detected.
[ONE Original Android Development] npjohnson:
if you have mix and matched oxygenos firmware, you need to flash full COS before lineage.
[ONE Original Android Development] seanwlk:
i was on LOS16 before this, but right before that i had flashed the stock rom completely. Was just messing around anyway, this phone was lying around in the drawer.

Will try flashing stock again. Thanks
[ONE Original Android Development] TheAlmightyOgreLord:
Is GPS not working? Or do do you need a sim card for the GPS chip to be activated on this phone? I'm all EXT4 partitions, full disk encryption and can't get the GPS chip to activate...
[X 2014 Original Android Development] npjohnson:
moto x 2014

- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:

This is the Official Lineage OS 18.1 thread for the the moto x 2014.

Downloads:

Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.

Official Builds:

victara

Unofficial - built once a month by me, includes GApps and Pixel goodies:

victara

If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:

Front camera cam be a little overexposed or blown out sometimes - can't figure it out.

Find any? Report them according to this guide.

Notes:

The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.

Kernel Source: https://github.com/LineageOS/android_kernel_motorola_msm8974
[X 2014 Original Android Development] *_Axl__Rose_*:
Thanks man!! working perfectly on my moto x 2014.
[X 2014 Original Android Development] npjohnson:
Update: we are now in the official build roster and queued to get an official 18.1 build on Sunday morning :)
[X 2014 Original Android Development] douglasmarx:
Hi npjohnson!

I've follow all the steps for the upgrade, that happened without fails (the only unusual thing that i've noticed is that process finshed as OK on the device screen when progress was around 47% on pc cmd adb screen, for the rom and for the mindthegapps), but the device do not unlock when I enter my pin. The screen turns black for a moment and return to lock screen. Any idea of how to solve this?

Update: After restore the backup, I've remove screen lock pin and try again. Now the device is rebooting when try to load the first screen after the boot...
[X 2014 Original Android Development] amkirk94:
How is this even possible? 😅
[X 2014 Original Android Development] curiousrom:
Moto X 2014 victara Upgrade to LineageOS 18.1 Fail & Workaround

For the Motorola Moto X 2014 (victara) the LineageOS upgrade wiki page now says that you need to format data before installing LineageOS 18.1: https://wiki.lineageos.org/devices/victara/upgrade

In this LineageOS subreddit thread Can't go past locking screen after installing 18.1 on bacon (OnePlus 1) there is a post made by haggertk who is one of the 9 Lineage directors that explains why.

The workaround in that thread posted by OffizierMichael to avoid formatting the Data partition & losing your apps, data & settings was confirmed by a few OnePlus One users but not for the victara yet confirmed by victara user @douglasmarx:
[X 2014 Original Android Development] douglasmarx:
Works for me too (the workaround)! Thank you very much, again!
[X 2014 Original Android Development] Stk14:
Hello,

I'm very new here.

I've been able to install the update without any problem (formatted the phone before installing the update).

I would only like to tell that since the update, my phone is unable to connect to Netflix. It's stuck at "Netflix" with black background. I've already reinstalled the app, deleted cache and data multiple times. No luck.

Also, Chrome is now unusable (works for a couple of seconds then it freezes). I'm using Opera right now.

Last, maybe it's my internet, but the phone seems to lose the WiFi connexion more frequently since the update and often doesn't reconnect to our network even if it's within range (I have to either restart my router or reset my phone's network settings).

That said, thanks for all the devs for making my old Moto X still work and compatible with newer apps ^^
[X 2014 Original Android Development] npjohnson:
1. Netflix should be fixed next build, update and let me know

2. Looking into it

3. Not sure, seems fine to me
[X 2014 Original Android Development] juanchotazo99:
Lovely work! Thank you for this.

I think both cameras are misbehaving a bit.

For example, lets say I open up the default LOS camera or Open Camera. If I'm pointing at something that's bright while the camera app is opening, then exposure will be correct on screen for that scene and the live preview is fast and snappy as you'd expect on good lighting conditions.

While having the camera app open, if I point it to something dark or black, exposure adjusts a few stops up to compensate, but then it won't readjust back when pointing back to what was bright. Camera preview gets laggy and stays laggy, as if shutter speed got too low.

Front camera tends to always get exposure wrong, too bright, blown out and laggy. I'd guess auto exposure is not working correctly, shutter speed being the problem. Closing and opening the camera app again fixes the issue until it happens again.

Camera behaved as expected on 17.1.

How can I collect and provide more information about this? A logcat? I'm on 18.1-20210418-NIGHTLY-victara, phone is a XT1097, latest Marshmallow firmware. 18.1 was clean installed, the usual factory reset wipes and /data formatted in TWRP.
[X 2014 Original Android Development] muni_es:
Thanks a lot for this build!

My old Moto X is a new phone now!

I have some problems with the flash when taking pictures, the Photo App crashes...not very important for me though...

Other than that, everything seems to work smoothly!!
[X 2014 Original Android Development] jeferson1979:
Can you guys do a logcat while using and post steps to reproduce? It will be really helpful for us. Thanks in advance
[X 2014 Original Android Development] muni_es:
Sure, I will try to do it this weekend
[X 2014 Original Android Development] muni_es:
Here are the logs:

I rebooted the phone, then I opened the camera and try to take a picture. This happened around 14:15:29.661

The flash was on by default. The timer (3 seconds) started but the picture was not taken. Then I tried few times more, but then the application get non responsive and crashed.

I hope it helps!

Kind regards
[X 2014 Original Android Development] ptitrusse:
Hi

Thanks for the update, just performed a clean install, coming from LOS 17.1.

The echo during calls in Signal is still an issue, as previously reported in the 17.1 thread.

Camera works, indeed it sometimes starts completely overexposed but not always, so closing it starting it again seems to fix it. Strange. Video recording seems to work, it didn't work in 17.1.

Also, there is no AOSP email app. Could be a problem with Mindthegapps, I usually never install Gapps but this is not my phone :)

To me the major problem is the echo during VoIP calls. Using signal with video and or speaker is just not possible.

Thanks !
[X 2014 Original Android Development] juanchotazo99:
Here you go. This is on yesterday's build, 20210425

First opened OpenCamera while pointing at sunlight, confirmed fluid camera preview with correct exposure, then pointed to something black, reproduced behavior as per my previous post (laggy camera preview as if shutter speed got too low to get the correct exposure on something black, as expected), then pointed back to sunlight to confirm bad behavior (shutter speed stuck too low, camera preview laggy and completely white, too much light captured, not auto correcting back to initial status as you'd expect).

Closed OpenCamera, opened LOS' stock camera, did the same steps, reproduced same behavior, then closed it.

Let me know if you need anything else. Thank you!
[X 2014 Original Android Development] npjohnson:
The echo: we're working on it, its quite tough.

The AOSP email app: It was dropped, old and insecure.
[X 2014 Original Android Development] sumomogg:
Well, i've installed this build (lineage-18.1-20210425-nightly-victara-signed.zip) and I have to say its incredible. I've installed Lineage on a number of devices (LG G Pad 8.3, Galaxy S5 Plus, LG G2) and none of the builds are as smooth and bug free as this one. I followed the install guide on the Lineage Wiki page and it went exactly as planned (though I did find some old youtube videos to help point in the right direction sometimes such as when going through the Motorola website unlock bootloader process)

I'd given up my old Moto X 2014 but this has breathed new life into it. Many thanks npjohnson!

The only minor thing I can't fix is that I had planned to give this to my 10 year old son and use Google Family Link, but it wont let me do this as it gets stuck in a loop - I think this may be an issue with mindthegapps. Either way, its not a big problem, just happy to have an all new Victara on the latest build :)

SInce putting this OS on I've also re-discovered what a lovely phone it is - great to hold in the hand (one hand unlike todays huge slabs) and the glass is so smooth. Its just a really nice phone.
[X 2014 Original Android Development] npjohnson:
FamilyLink is Safety net related I think :/
[X 2014 Original Android Development] sumomogg:
Sorry - I'm not sure what Safetynet is (even after Googling!) - does that mean Familylink wont work with Lineage?

Thanks
[X 2014 Original Android Development] npjohnson:
It is a check to ensure device integrity done google server side. Sometimes flashing Magisk will allow you to pass, but no guarentees.
[X 2014 Original Android Development] lantsem:
Long press vibration doesn't work after 18.1-20210425 build.
[X 2014 Original Android Development] npjohnson:
what do you mean?
[X 2014 Original Android Development] lantsem:
Long press action (empty space on home screen or some app icon to launch app shortcuts) doesn't give vibration feedback anymore.
[X 2014 Original Android Development] npjohnson:
What launcher do you use? It's called for by that.

Does your vibration motor work elsewhere?
[X 2014 Original Android Development] lantsem:
Launcher by default - trebuchet. Vibration motor works ok, it's not a hardware problem here - tested with my two xt1095. I made clean install to confirm, that with build 20210418 it works and with 20210425 it's not.
[X 2014 Original Android Development] Stk14:
Hello, sorry for the late answer but I wanted to wait in case you needed more time.

1. Netflix is still not working. Still stuck on the boot logo (Netflix) and after awhile it says "Device failure occured. Please restart your device and try again (501.109)."

2. Chrome still freezes. It works fine for maybe 30 seconds/ 1 min before freezing.

3. I think you can forget about the network problem. Seems like a carrier related bug.

Really sorry if I seem to only post bugs, and again for the very late reply.

Maybe these are problems that only occur on my device ? If so, let me know and I'll just live without Netflix and Chrome.

Thank you very much for your kindness ^^
[X 2014 Original Android Development] jeferson1979:
I had no issues with Netflix, but chrome seem a bit borked... I'll take a look at it
[X 2014 Original Android Development] npjohnson:
netflix works for me - maybe you need to wipe data to have it take effect? We did swap DRM blobs.

Chrome, I can't recreate, so weird.
[X 2014 Original Android Development] Stk14:
Hello! Thanks for your replies.

As for Netflix, I cleared the data and rebooted my phone. When I relaunched the app it said "Sorry We Cannot Reach The Netflix Service (-9)"

After deleting the data (without rebooting the phone) I got the previous error : "Device failure occured. Please restart your device and try again (501.109)"

So I guess it was an internet connection problem all along... What's weird is that I never had these problems on Lineage 17. When I do speed tests, it's pretty much as before (at the beginning, just after upgrading to 18.1 though, it was a bit slow).

Maybe our internet connection just isn't up to Android 11 standards...
[X 2014 Original Android Development] npjohnson:
That almost sounds VPN/DNS related, any mods there?
[X 2014 Original Android Development] Leandro031:
Good rom thanks.

Only have issues with chrome (freeze with +-2 min use)

And the app "ifood para entregadores"

iFood para Entregadores - Apps on Google Play

IFood for couriers connects deliverers to iFood orders

play.google.com

doesnt work, any fix? Pls
[X 2014 Original Android Development] Leandro031:
I still can't get the app to work. unfortunately the application crashes on startup. app: ifood and ifood para entregadores. I am on latest build
[X 2014 Original Android Development] yuhrim:
Hi. I have a problem triggering the camera with a gesture. Everything works well when unlocking the screen. But when I start the camera from the off state, then the application crashes. Pin not set.
[X 2014 Original Android Development] npjohnson:
fixed - sorry, that was a weird bug.
[X 2014 Original Android Development] FurionStormrage:
Hi all,

First of all I'd like to thank everyone that have worked on this ROM for this device. My main phone died so I dug up my XT1092 and was super surprised to see I could have Android 11 on it with this ROM! Just amazing. Runs fine, just am encountering some minor issues that I'd like to post here, perhaps they can be fixed.

1. I can't grant Google play services permission to SMS. I find the setting, set it to Allow, but then it just doesn't get set to allow. Tried many many times, rebooted, didn't work. For example to restore a backup of Signal chats this permission is required (found a workaround too for those interested).

2. Chromium based browsers freeze after a minute or so. Tried Chrome, Edge, Vivaldi. All exactly the same. Firefox does not have this issue.

3. Netflix and Disney+ don't work. Disney+ just stays black for me, no splash screen or log in screen whatsoever. Netflix shows the Netflix logo on black background. After waiting long enough it errors with attached error message.

Happy to provide logs or test things out if that helps.
[X 2014 Original Android Development] juanchotazo99:
Can also confirm 2 and 3.

I just got my victara back to the last official Lineage 17.1 build (just before April 1st 2021) which doesn't have any of these issues nor the others mentioned in the thread, for the time being, a few months ago.

Here's my copy for anyone who would like to go back.
[X 2014 Original Android Development] FurionStormrage:
The Google Play services thing is fixed for me now. Not sure if Google fixed it on their end or it got fixed in Sept 12 update that I installed.

I encountered one other weird thing, not sure if it is related to this LineageOS build. I can't download the Microsoft Office app. It downloads up to 80-90 something percent then stops and it ends with an error. See attached. Anyone else experience this? Tried all the things Google recommends, doesn't help.
[X 2014 Original Android Development] 54Samuel:
Without a doubt a great job, but I have a question, is it possible to make the Motorola Camera app work? I looked at what previous versions of LineageOS worked.
[X 2014 Original Android Development] Pedro_PH:
The GPS is not working on my phone, did I do something wrong?
[X 2014 Original Android Development] morgessa:
Probably. I have two devices running fine with no GPS issues.
[X 2014 Original Android Development] morgessa:
Is there still development/bugfixing happening for this device?

Is it worthwhile submitting bug reports?

My main issues are with chrome freezing and the camera app (several issues - rather unusable in current state). Other than that excellent work with lineage OS for victara - kudos to the developers.

Used to play around with custom ROMs back in the good old early days - Windows Mobile and for the first Android devices like the G1.

I have to get used to gitlab first, currently fighting with the search function there. :S
[X 2014 Original Android Development] npjohnson:
What camera issues?

The Chrome one I can't recreate, so no clue...
[X 2014 Original Android Development] chgr008:
Hello npjohnson,

can you fix NFC Extended Length support or is this a hardware issue?

I tried F-Droid AusweisApp2, the official german governmant app for ID-cards. There i get the information: extended length not supported.

Thank you for your efforts to keep victara alive.
[X 2014 Original Android Development] npjohnson:
I don't think our device supports this? try on stock
[X 2014 Original Android Development] lincolnthalles:
In terms of performance and battery life, this ROM is astonishing. It also surprised me that Motorola's Ambient screen and sensors are working fine.

As this is not my main phone, it was forgotten in a drawer. Last time I messed with it I flashed Lineage 14.1 and performance sucked. Most apps were stuttering as hell and redrawing screen.

With Lineage 18.1, so far I only found issues in the camera app. All settings menu vanished after first use. Then, it bugged when switching front/back camera and image was persinstently in wrong orientation and stretched. The issue persisted even in Open Camera and I had to reboot in order to fix it.

The settings only came back after clearing Camera app storage. So if anyone experiences camera issues, I suggest this workaround for now.
[X 2014 Original Android Development] ptitrusse:
Hi,

Thanks very much for maintaining this phone ! I also have a lot of camera issues since 18. Frequent crashes, the app refuses to take pictures in low visibility, sometimes starts with a blank or black screen and you need to force close it or restart the phone.

I also still have the echo / audio issues in voip apps.

It's a bit sad that 17 is not maintained as it worked a lot better in the end !

Anyway thanks very much for your work, a little crazy to see such an old phone with A11 !
[X 2014 Original Android Development] Cocruler:
Here are my log files for the chrome freezing issue. I have also had a problem with apps force closing until restart, but do not think I have a log of that. I had the chrome freezing issue after a dirty flash, but I recently did a factory reset and have the same issue. All chromium browsers have this same behavior. Firefox works fine.
[X 2014 Original Android Development] jeferson1979:
Thank you. Very helpfull log. Wait some good news on this issue
[X 2014 Original Android Development] Speed42:
Does anyone know if there will be lineage 19 for moto x2014?
[X 2014 Original Android Development] jeferson1979:
Our kernel doesn't meet the requirements on Android 12.
[X 2014 Original Android Development] Speed42:
Ok