yashsingh1/xdaforums huggingface dataset:
[X 2014 Original Android Development] kedar a.k.a. 3K:
What recovery and version are you using?

if (recovery is not twrp && version < 3.0.2.2):

Flash latest twrp recovery and try

else:

This was caused because you probably wiped system (and build.prop along with it) before flashing the ROM.

build.prop contains the device info which is verified by the ROM before installing as a safety mechanism to prevent installation on a non-compatible device.

One solution is to make a flashable build.prop zip

OR

remove the verification checks from the ROM itself as described in the thread below:

https://xdaforums.com/showthread.php?t=2522762
[X 2014 Original Android Development] [Acme]:
Recovery twrp 3.2.3-0
[X 2014 Original Android Development] [Acme]:
I did a clean installation of lineage-14.1-20181007-nightly-victara-signed.zip (all wipes), after flash it no wipe and when I finished I tryed to update to lineage-14.1-20181014-nightly-victara-signed.zip with same error message, Updater process ended with ERROR: 7
[X 2014 Original Android Development] Scorpius666:
I wonder if anyone here has resolved indefinitely the WiFi problem (it disconnects when you leave and never reconnects until a reboot)?

This is really annoying and I think the only way to solve it is to buy another phone.
[X 2014 Original Android Development] ericcostes:
wifi works well here

I dont have this problem her .:good:

Have a look to your internet box parameters first ...

---------- Post added at 07:33 PM ---------- Previous post was at 07:25 PM ----------

the situation is very strange because many item are still opened on lineageOS dev site, some of them since june ...

personally I am a bit pessimist for a 15.1 ..

but not a problem as our 14.1 rom is really very good :good::good::good: , so that I can live a long time with it, no problem ..

regards,

eric :cowboy:
[X 2014 Original Android Development] jennydevil:
HW Clock still an issue in October 21 build

The time and date reset to the last build date and time, and count forward from that date. I.e. I flashed the Oct 21 build on the 23rd at 8:30pm, rebooted, then the device thinks it's Oct 21, 7:00pm. On Oct 24th, the device will think it's Oct 22nd. If I go back to a Sept build, the date will count up from the Sept date.

Issue occurs even if device is set to not automatically update time & date.

I use my Moto X offline very frequently, and having the wrong date/time is quite annoying, as calendar entries and reminders are incorrect.

Any idea if there's a fix planned for Linneage, or if there is a standalone utility that can maintain the clock through a power cycle without network (as hinted at above)?

Thank you for the insights on the Qualcomm limitation!
[X 2014 Original Android Development] Leonardoliveira:
I am no longer able to update my victara ... when downloading the update package it opens the twrp but it does nothing, I am not able to do the installation manually with the dirty flash. Does anybody know how to solve this?
[X 2014 Original Android Development] :
same here.
[X 2014 Original Android Development] [Acme]:
same for me
[X 2014 Original Android Development] mefarhan:
I'm having the same problem. I have 0930 Nightly build installed and when I try to update, it gives me Error 7. I even tried to edit the update file by removing 'assert' code, still giving me Error 7.

Did you manage to fix the problem?
[X 2014 Original Android Development] [Acme]:
Did you delete the assert line completely???

Your first line will start from mount...

When I did it I can update but I lost everything
[X 2014 Original Android Development] mefarhan:
No, I only removed the first line that ends with a semi-colon

assert(getprop("ro.product.device") == "victara" || getprop("ro.build.product") == "victara" || abort("E3004: This package is for device: victara; this device is " + getprop("ro.product.device") + "."););

Now the first line is

ui_print("Target: motorola/lineage_victara/victara:7.1.2/NJH47F/2a7654d5d0:userdebug/release-keys");

:confused:
[X 2014 Original Android Development] mefarhan:
Editing updater-script in com/google/android

Hi, I did some digging and found some interesting information.

See screenshot below:

[IMG="Screenshot of Updater-script"]https://i.imgur.com/zqOViVR.png[/IMG]

Screenshot Link

Every time I try to install an update, it gives me Error 7, but before that, I can see this line: "Can't install this package on top of incompatible data. Please try another package or run a factory reset".

Now this is either line 12 inside IF, or line 16 inside ELSE.

I changed the words and tried to update, I found out that when data partition is mounted, Error from Line 12 shows up, when I un-mount data, Error from line 16 shows up.

What should I do now? Can I remove all these checks and remove all the line above Line 19 (green line in screenshot)? Is it safe. It looks to me like everything above line 19 are security checks and the actual update process starts on line 21.

Why am I getting these errors? Is there any way to fix it. I don't wana dirty flash new updates every week.

Regards,
[X 2014 Original Android Development] Leonardoliveira:
The same thing happens to me. and not only for the victara, this also happens on Titan and Galaxy S3... I already tried to delete the command lines above, and the installation ends up in error in the zip file

---------- Post added at 09:44 PM ---------- Previous post was at 09:39 PM ----------

soon we will have the official lineage 15.1 and believe that this problem will be solved.
[X 2014 Original Android Development] Leonardoliveira:
for those users who were having problems with OTA updates, this has already been fixed in the last builds ... I believe that a clean install is necessary
[X 2014 Original Android Development] ericcostes:
close 14.1 dev item - leonardoliveira

Please can you tell us if your 14.1 dev item is actual ?

https://review.lineageos.org/c/LineageOS/android_device_motorola_victara/+/203645

else is it possible to close the file ?

thanks a lot :)
[X 2014 Original Android Development] Leonardoliveira:
it seems that this has not yet been merged ... what do you want me to see specifically?
[X 2014 Original Android Development] ericcostes:
14.1 lineageos dev

as it is old and not resolved why not abandon it ?

is there a special reason for this 14.1 change ?

regards,

:)
[X 2014 Original Android Development] RockyTV:
Yes. When your phone is charging and isn't booted to Android, the charging animation is ugly. I took the original charging animation image and created that commit.

However, it looks like crpalmer (the maintainer) no longer owns a Moto X 2014, which meant that its development is kinda halted (a few commits get merged and the porting process is a bit slow). Now that I got a new phone, I may be able to help the other developers that are working on the port to get it done.

P.S.: I'm not affiliated with Lineage, I'm just a contributor from the community.
[X 2014 Original Android Development] ericcostes:
do you think we will have a 15.1 for victara ?

seems dev is closed :(:(:(
[X 2014 Original Android Development] BootloopedMillennials:
Don't think so. Just last month the LineageOS team dropped many 14.1 devices that were no longer being maintained. The Victara wasn't one of them. I think they moved 14.1 updates to a monthly schedule.
[X 2014 Original Android Development] Leonardoliveira:
exactly, and the Lineage team itself spoke about this in their last survey.

all 14.1 builds are now updated monthly.
[X 2014 Original Android Development] rlopess:
I cant install Instagram on Google Play, the way I found is thought the APK. Anyone else with this bug too?
[X 2014 Original Android Development] TuksOID:
Also with me. At each reboot, the date and time are reset to the registered time of the build, established in build.prop. This has happened since the October 20 version.

This is a likely solution for lineageos 15.1.

https://review.lineageos.org/c/LineageOS/android_system_timezone/+/232321

But it can be a starting point for solving this problem in lineageos 14.1, right?
[X 2014 Original Android Development] RockyTV:
This commit has nothing to do with the wrong date being set in your phone. It just changes the way the packaging script appends the date to the name of the ROM's OTA package.

I've literally just updated to December 20th nightly and the clock is fine. It's probably an issue with the RTC in your phone.
[X 2014 Original Android Development] TuksOID:
Why on my device, if I did tests and found that with stock and roms from last year can I reboot without any internet connection and date and time remain?

One thing that sets this apart is that there are other device owners who have been reporting this problem after recent updates (from October to today).

I really thought that point would be important to remedy that problem. The problem should be in the source of ROM. It certainly is not keeping the configuration. Could it be a problem of setting permissions on configuration files?
[X 2014 Original Android Development] Victortraba:
Hi guys, first of all let me sorry for my english :D

Well, i have a moto x2 and was in 6.0 stock official rom, then i downgrade to 4.4 kit and everything was working well.

Looking for some nice custom rom, i find this one from u guys! So i download the lineage-14.1-20190120-nightly-victara-signed.zip, gapps nano and lineageOS SU.

But i think that i mess it up when i wipe through TWRP, cause now i'm without OS and i cant find my phone to do the adb sideload!

I try to copy the zip to internal memory and install through twrp and didnt work either!

There're any version of this that i can install through TWRP?

I've already install usb drivers, universal adb drivers, motorola drivers and cant make it show up in ADB.

What i do now? T_T
[X 2014 Original Android Development] RockyTV:
Boot into TWRP. Plug phone to PC. Uninstall ALL drivers you had installed for the phone. Install Google's USB drivers.

Once you plug in your phone, you need to check if it works by running "adb devices".
[X 2014 Original Android Development] Victortraba:
Works! Thx so much.:D:good:

But the OS seems instable, time to time its rebooting. Especially when i try to open Facebook. And sometimes even when im not using the cellphone it reboot, weird.

I've done wipe and clean flash again, but the problem persist.:(
[X 2014 Original Android Development] Leonardoliveira:
this ROM has a bug in the Facebook app, uninstall it or else your phone will always restart, use Facebook Lite or go to LineageOS 15.1 unoficial
[X 2014 Original Android Development] mefarhan:
20190120-NIGHTLY-VICTARA

I'm having two problems.

1. When my phone is connected to wifi, and I go out for some work and come back. It won't show my wifi name in the menu. Instead it shows the wifi of the place where I went for work. e.g.

My home wifi is 'abc' and I'm connected to it.

I go out for some work at a place where they have 'xyz' wifi. I didn't connect to it,

I come back home and take my phone out of my pocket, and the wifi isn't connected to 'abc', when I check the wifi menu, it shows that only 'xyz' is avaialble to connect, and it doesn't even connect to it (work place is almost 2 km away).

I try to toggle on and off the wifi, but still my wifi won't show up. It keeps showing 'xyz' and doesn't connect to it.

Only solution is to restart my phone, and then the wifi starts working again. I don't wana restart my phone 3-4 times a day.

This started happening in the last week or so.

2. When I restart my phone, time resets to 5am in the morning (date is fine), and it doesn't update unless it connects to the wifi. It's not that big of a deal, but it's annoying, shouldn't it update time from cellular network?

Let me know,

Regards,
[X 2014 Original Android Development] BootloopedMillennials:
I think the end may be near on the LOS 14.1 branch. At least on device specific fixes, look for the last victara specific commit/change. It still appears to be updated with general fixes and patches.
[X 2014 Original Android Development] Leonardoliveira:
this is because the victara developers are focused on version 15.1
[X 2014 Original Android Development] LinkSnows:
Do you know if there is a plan to bring Lineage OS 16 for us? Im not into XDA forums anymore, and I saw a thread of a 9.0 ROM, but seems too unstable to use.
[X 2014 Original Android Development] Leonardoliveira:
I've been following up on some victara groups, and the same unofficial LineageOS 15.1 dev is working on a stable LineageOS 16 version
[X 2014 Original Android Development] mortza98:
For me, in both 15.1 and 14, both color problems are found
[X 2014 Original Android Development] ericcostes:
Does somebody knows something about official 15.1 final setup ?

Hi Guys,

Jira shows nothing in devs about our victara 15.1 ...

Does somebody knows which problems are still remaining , can we really expect an official 15.1 ?:confused:

Regards,

Eric
[X 2014 Original Android Development] RockyTV:
RIP https://review.lineageos.org/c/LineageOS/hudson/+/242408/1/lineage-build-targets

tl;dr: no more monthly builds for victara.
[X 2014 Original Android Development] BootloopedMillennials:
Yea when LOS 16 is released (should be soon, maybe March), LOS 14.1 will be dropped for all devices. That means RIP Victara since it has no official builds of 15.1 or 16. Apparently a developer is working on LOS 16 for the Victara but who knows if it ever becomes official status. LOS has stricter requirements for official releases than in the past.
[X 2014 Original Android Development] ericcostes:
ok but ...

:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:

who knows which problems are stopping 15.1 ? :confused::confused::confused:
[X 2014 Original Android Development] ericcostes:
Motox 2014 dropped from LOS yesterday 26 feb ?

this is incredible after all these efforts and near the goal

some infos for future 16.0 or totally abandonned with so x1000 los users ?
[X 2014 Original Android Development] BootloopedMillennials:
IIRC SELinux was a problem. From what I understand, following the Nexus 6 development, it's extremely difficult to properly setup SELinux. Keyword is properly.

I haven't been following Victara development too closely to know if it's fixed. My Victara battery is dead and I have no interest in reviving it. I thought about donating it to a local rom developer but I doubt any is in my area.
[X 2014 Original Android Development] BootloopedMillennials:
Did you find anything else out? Are they building in a separate repo than the official LOS one? Official LOS 16 dropped today for other devices, 14.1 is sadly now gone.
[X 2014 Original Android Development] RockyTV:
This and I spoke to one of the devs and he said it's a pain to port 14.1 devices to 15.1, if they don't have kernel sources. A lot has changed.
[X 2014 Original Android Development] BootloopedMillennials:
Yep and going from 15.1 to 16 is extremely difficult too. Talking to one of the developers who brought up the Nexus 6 to 16.0, he said SELinux was a true PITA this time around. It was hard to track down denials. Also IMS doesn't work and likely never will. Then there is the issue of encryption and decryption. Basically yea it's not an easy process, never really was but this is more complicated.
[X 2014 Original Android Development] ericcostes:
so conclusion is motox 2014 wil never move to pie ?

?:confused::confused:
[X 2014 Original Android Development] zahidm:
One of the developer is trying on LOS 16 for Victara, May be soon test build will be released, Unofficially
[X 2014 Original Android Development] ericcostes:
Somebody to upgrade security patchs in the future ?

If Los 15.1 and 16.0 are stopped for victara , do we have a dev to continue to port security patchs ? :confused:
[X 2014 Original Android Development] mmrahul:
How do I get the last released build?

My device has been lying in a corner since August 2018. I just turned it on and realized all the 14.1 ROMs officially have been scraped. When was the last released ROM and how do I get that?
[X 2014 Original Android Development] mmrahul:
That worked, Thank you very much!
[X 2014 Original Android Development] LexX-V:
For those who need the latest official build (it is not available at the official site already) I made the mirror:

Motorola Moto X (2014) - victara
[X 2014 Original Android Development] mefarhan:
Hi,

I'm using 20190220 Nightly. Sometimes when battery is below 50 (let's say 42%), and I start playing a CPU intensive game, phone shuts down. When I connect the charger it shows the same 42/41%. I turn the phone ON and it works fine.

Is there any way to check if battery has worn out? Can/should I calibrate it? Let me know.

Regards.
[X 2014 Original Android Development] IrvinGarcia1821:
cuestions?

Why does the facebook application restart the terminal every time I open it?:confused::confused::confused:
[X 2014 Original Android Development] zahidm:
That's a bug in all custom Nougats after November 2018 builds!
[X 2014 Original Android Development] Bristow Xavier:
how old is your device?
[X 2014 Original Android Development] albatros_1994:
Change the battery. i'm 99% sure :good:
[X 2014 Original Android Development] FLAmbuRNE1:
Now that Lineage 14.1 is two versions old, all the official downloads are gone. Anybody got the latest zip for LOS 14.1?
[X 2014 Original Android Development] rahimali:
here -> https://androidfilehost.com/?w=files&flid=290769
[X 2014 Original Android Development] mefarhan:
Today I got a pop-up on my phone that a new update is available. When I checked it showed me 2 updates of LineageOS 16.0, dated 29 and 30 August. I checked the official download section and updates are there too. Has anyone tried these?
[X 2014 Original Android Development] zahidm:
Los16 goes Official... From 29th August
[X 2014 Original Android Development] mefarhan:
Is there any official thread regarding LOS 16? where can I report the bugs and issues?

Thanks,
[X 2014 Original Android Development] zahidm:
Still there is no Thread and nobody authorized to
[X 2014 Original Android Development] RockyTV:
It's actually this thread.
[X 2014 Original Android Development] renzs:
you can report on the unofficial LOS16 thread. it's the same developer for official, just hasn't rename the thread. remember to attach logs for bugs

cheers
[X 2014 Original Android Development] PositronWolt:
Flashed the latest 14.1 build I found (the one that Lex mirrored) and my phone stopped playing sounds and vibrating. My microphone is working, I sent an audio via WhatsApp and the other person could hear me, but I can't hear nothing. The only sound it produces is when I'm on a call, and it's VERY LOW. What should I do?

Edit: Tried the 16.0 and got the same problem. I know it's not a physical issue, since my phone vibrates on TWRP and when rebooting.
[X 2014 Original Android Development] RockyTV:
Depends on the theme you choose.
[X 2014 Original Android Development] Heroeagle:
off charging indicator is not working , just question mark inside the battery !!
[X 2014 Original Android Development] midnightdevil66:
Yes it's known. Does that prevent you from making calls and SMS? No, get over it.
[X 2014 Original Android Development] Cybertron713:
No need to be rude, dude. It has a purpose that it is currently not fulfilling, a purpose that some people rely on it for.
[X 2014 Original Android Development] muabaylentroi:
Can I ask a stupid question?

On Moto X with CM 14, do we have Ambient Display when pick-up the phone or waving hand in front of it?

I haven't use Moto X before, but in my HTC M8 with CM14, Ambient Display only work when received notification.
[X 2014 Original Android Development] kedar a.k.a. 3K:
Yes it works.

Settings>gesture shortcuts

Btw ambient display is different , the one you are referring to is called "wave" in gesture shortcuts.
[X 2014 Original Android Development] midnightdevil66:
Yeah
[X 2014 Original Android Development] RockyTV:
One thing that I noticed: screen will still wake when screen is off and "Block visual disturbances while screen is off" and "Ambient Display" are turned on. Not sure if this is expected.
[X 2014 Original Android Development] zander21510:
I'm getting some wakelocks that are burning up my battery. Better Battery Stats narrowed it down to CM Window Manager. I can usually resolve it by restarting. Any idea what's causing it, anybody else getting bad battery drain?
[X 2014 Original Android Development] EagleSoldier:
Me too, since last update....

Lets see, maybe new update will fix this!
[X 2014 Original Android Development] Jaytn:
First off, thanks for your effort making this ROM.

Weirdly enough, on my first install the Gestures section in Settings only showed one item (I think it was twist for camera), so I promptly went back to Stock. But some research and googling later I found that there should be most of the Moto features available in CM and now multiple installs later it works, so I'll guess the first case was a hiccup / fail on my part. Thanks for making these features available on other ROMs, they're what's making Moto phones special.

But one feature I am missing dearly is wave to snooze the alarm. I am quite spoiled with the comfort of just having to flail my arm around to stop that pesky noise in the morning. Am I missing it or is it not available? Can I bodge it in myself? Googling on this topic turns out more difficult than I would've expected.
[X 2014 Original Android Development] belumira:
Is there a way to include pulsing notifications with ambient display? I relying on the LED for now but I prefer pulsing notifications.
[X 2014 Original Android Development] lukethejohnson:
Does anyone else have horrible wifi reception, where it used to be fine after installing this?
[X 2014 Original Android Development] zander21510:
I actually noticed this the other night in my house. I was in my house where I usually get full reception, and now I get pretty poor reception in the same place
[X 2014 Original Android Development] R2D2-AKU2:
My WiFi reception seems to be fine but WiFi dies every once in a while (like one a day). The WiFi icon shows a question mark in it. Reboot clears it.
[X 2014 Original Android Development] xb360:
Didn't see that option. But there's wave to silence call. So maybe the developer can implement it on future build.
[X 2014 Original Android Development] Gus Ghanem:
Long Live Lineage!

https://github.com/LineageOS/android_device_motorola_victara
[X 2014 Original Android Development] doug.passerini:
I could see LineageOS repository on GitHub is exactly the same as CyanogenMod one - at least for our victara, at this time.

So, what should we expect from this (apparently new) repository?
[X 2014 Original Android Development] Gus Ghanem:
Because the Cyanogen Inc. company is dead, it's trademarks can no longer be used, so CM will have to change to a different name, apparently Lineage is one possibility, this new name for CyanogenMod may not be final though.
[X 2014 Original Android Development] Heroeagle:
I am reporting a bug , i searched on gerrit first if there any fix and there was no fix , so i report it here to help the dev if he did,t addressed it , thanks for your odd reply
[X 2014 Original Android Development] RockyTV:
www.androidpolice.com/2016/12/12/li...-to-be-cyanogenmods-new-name-at-least-for-now

We should be getting an official notice in the next days.
[X 2014 Original Android Development] FreVDP:
Nothing new, because it is Cyanogenmod, LineageOS (LAOS) is the new name: http://www.androidpolice.com/2016/1...to-be-cyanogenmods-new-name-at-least-for-now/
[X 2014 Original Android Development] niket09011994:
Does this mean, VoLTE will now work on victara with Reliance Jio?
[X 2014 Original Android Development] thousandecibels:
Let's see, on Victara LTE does not work ATM in select cities (currently not in Punjab) through JIO.

I am curious to know too. I used JIO a while ago for a day or two when I was on a holiday back at Himachal.

Now, I am back at work and I got no network coverage in Punjab when using JIO. Kind of disappointing.
[X 2014 Original Android Development] niket09011994:
That's because in Punjab, Jio doesn't have Band 3 licensed spectrum.