yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] Wheels564:
I get about three days on a charge with the original battery with no heat problems. I also use a slow charger because I don't think fast charging is good on the battery. It sounds like you have a process running out of control in the background. Go into settings/battery and see what process is using up battery. Also if your using gestures only use the pickup mode. The hand wave tends to be too sensitive tending to keep the phone awake more. Magisk and Exposed can also cause problems. I also keep my battery saving mode on efficiency and turn off everything I don't use like bluetooth, location and even data when not needed. The last thing I would do is a fresh install formatting data, cache, dalvic and system. But also make sure you use the right TWRP version for your bootloader. If on MM bootloader you want to use an older version like twrp-3.0.2-0-clark, but if on Nougat bootloader maybe use twrp-3.3.1-0-clark.
[X Style (Pure) Android Development] kb8no:
Battery problems have been a nagging problem on this phone. It has been said that the charge control circuit resides in the battery but I am skeptical. I have been amazed at how rapidly the TurboCharge charges the battery. I have been gradually getting suspicious that TurboCharge harms the battery and gets eratic charging and charge readings, particularly on aftermarket batteries that maybe were not made for that rapid a charge. TurboCharger says 2.85 amps "regular" 5v and "TurboCharge" 9v which could certainly be excessive in the quest for speed. I have also switched to a "slow" charger of 1.0 amps. My initial impression is that this may be the answer.
[X Style (Pure) Android Development] ashwin.terminator:
Thank you for your reply.

I checked the apps section under the battery section. Nothing seems amiss there. I have disabled all the gestures for now. I will keep this thread posted if that helps improve this horrible battery life.

The phone is not rooted, so no Magisk/Exposed modules either. The fresh install is the last step for me too. I am on the Nougat bootloader. I have used twrp-3.4.0-0-clark.

As for the charger itself, I too believe that the phone heats up a lot during charging and it can't be good for the battery itself. But with the rapid discharge, waiting for a 1A charger to charge up the battery is a compromise that is hard to make. :\
[X Style (Pure) Android Development] Wheels564:
lineage-14.1-20210218-UNOFFICIAL-clark (mm bootloader)

New build up

Feb. 5, 2021 security patch

mm bootloader only

Md5: 0054134b72564381d14451148e991fa5

Always a good idea to do a backup when dirty flashing.

Thanks again to the Lineage team for the updates.
[X Style (Pure) Android Development] Wheels564:
lineage-14.1-20210218-UNOFFICIAL-clark (Nougat bootloader)

New build up

Feb. 5, 2021 security patch

Nougat bootloader only

Md5: f920871e22e23fa24ffe8135cc37e7d2

Always a good idea to do a backup when dirty flashing.

Thanks again to the Lineage team for the updates.
[X Style (Pure) Android Development] RomanOnARiver:
Thank you so much for this. I've installed it on a spare device and it works pretty great. My question is, which gapps package should I install, or specifically, "Full" vs. something larger - the main question is should I replace the stock camera from Lineage with whatever is in the Gapps - which camera is better?
[X Style (Pure) Android Development] Wheels564:
Go to https://opengapps.org/ and pick Arm64, 7.1 and whichever size you like. Pico leaves the smallest footprint and installs the least junk. I haven't used the google camera in quite a while so maybe install it next to the Lineage snap camera. I would also do a backup in TWRP of the clean rom in case you don't like it. The moto camera is quite good but whenever I did an update it would remove the camera and had to be reinstalled. Maybe someone has fixed that since. On some phones I just leave gapps off and install the apps seaparately.
[X Style (Pure) Android Development] RomanOnARiver:
I just mean which camera is better - the one from Lineage or the one that replaces the Lineage camera if you install anything larger than Full from the gapps?
[X Style (Pure) Android Development] Wheels564:
I can't tell you withiout installing google camera. I haven't tried it in years. Try installing it from the Play store and see how it works. If you don't like it you can always uninstall it.
[X Style (Pure) Android Development] RomanOnARiver:
Thanks for the response. Unfortunately the Google Camera doesn't show up as installable from Play Store. It seems like I have to flash it with gapps or not have it all. LineageOS camera either I get it from the OS flash or not at all. Such a dilemma. And the Moto camera I can still get from the Play Store.
[X Style (Pure) Android Development] Wheels564:
Try Apk mirror for google camera https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=google+camera
[X Style (Pure) Android Development] RomanOnARiver:
Cool. So if I install it this way, will it auto update from the Play Store if/when updates become available or no?
[X Style (Pure) Android Development] Wheels564:
I don't remember it's been a while. If not you should be able to flash right over it.
[X Style (Pure) Android Development] RomanOnARiver:
Is there perhaps a way to tell the gapps package to not remove the Lineage camera after installing the Google Camera from gapps?
[X Style (Pure) Android Development] Wheels564:
It looks like the only way your gonna get google camera is open gapps stock version and higher. Google no longer supports anything below Oreo. There's no way to not overwrite Lineage camera unless you know how to change the install script.
[X Style (Pure) Android Development] BZJoe:
Excellent. Just dirty flashed unto my Clark to update to this version and all seems to be working fine. Will report if anything comes up but so far so good. Thanks Wheels!
[X Style (Pure) Android Development] Nickolime:
Just installed the lineage-14.1-20210218-UNOFFICIAL-clark (Nougat bootloader) I have to say thanks for keeping this phone going. It's my daily for 5 years now. I had to use stock because I'm on Verizon, and I could never get the APN to load correctly for MMS. I came across the fix, and wanted to post it here too for anyone that might have the issue.

Connect the phone for ADB debugging. Then open ADB shell and use the command:

am start -a android.intent.action.INSERT content://telephony/carriers --ei simId -1

It won't let you edit the current one or list, but you can add a new one now, and use it. Worked great for me, and I'm up to date on security. Thanks again!
[X Style (Pure) Android Development] kb8no:
@Wheels564 I have been spending hours and hours trying to unravel things now that 17.1 and 18.1 have been shut off from ATT SIM's due to lack of VoLTE. I have managed to keep Verizon working on 18.1. I will soon be traveling and want to take advantage of both Veriaon and ATT with one phone on each.

Thank you for keeping 14.1 alive because it has VoLTE and it passes Safety Net. I was having a problem after flashing 14.1 Stock and then flashing this 14.1 LOS with boot looping. After lots of angst, I found that the latest Stock "23" Data is formatted to f2fs which causes the bootloop after flashing 14.1. If I re-format it on TWRP to EXT4 and re-flash, then it boots and runs as expected. Is this a known issue?
[X Style (Pure) Android Development] Wheels564:
I have not had an issue coming from the latest stock Nougat to Hashbang's 14-1. However I don't use the latest TWRP because I believe it's geared towards Pie and Q. If he used any of the changes he made with his 16.0 build and used those to make official TWRP that could screw up 14.1. The TWRP I tested with was 3.3.1-0 from official download. Everything seemed to work fine with it.
[X Style (Pure) Android Development] kb8no:
Indeed, TWRP 3.3.1-0 works perfect to flash 14.1 for N bootloader coming from stock N which has data formatted with f2fs. Thank you.

TWRP from Chris works perfect for 17.1. But if you use it to flash 14.1 it cannot handle f2fs and will bootloop unless you reformat data to ext4 first.

Then if you are flashing 18.1 you need LOS recovery from Chris which works OK but has no ability to back up.

It was not easy to figure out all these nuances. Wouldn't it be nice to have a unifying TWRP that works for 18.1 and was backwards compatible?
[X Style (Pure) Android Development] Wheels564:
Yes it would but the more Android changes the device trees change and backwards compatability gets harder to work out.
[X Style (Pure) Android Development] RomanOnARiver:
I see. So if I do want to Flash the last Google Camera version from the Gapps, is it just the one apk file or do I need others? I'm seeing a cameragoogle, cameragoogle-comon, cameragoogle-legacy, cameragoogle-legacy-common. The common folders have like Jar and XML files as opposed to an apk.
[X Style (Pure) Android Development] ashwin.terminator:
Does this requirement still exist?

I've a spare XT1572 that I can use for this test (I can still come back to 14.1, yes?)
[X Style (Pure) Android Development] Wheels564:
He's no longer developing 17.1 but I'm sure he would like to see a logcat of 18.1 with the dual sim variant. And yes you can go back to 14.1 but I believe you will have to flash back to stock Nougat again and use the TWRP I listed a few posts back to kb8no with Nougat bootloader.
[X Style (Pure) Android Development] Wheels564:
lineage-14.1-20210410-UNOFFICIAL-clark (mm bootloader)

New build up

Apr. 5, 2021 security patch

mm bootloader only

Md5: 3fd354cf6af4d7828c35f4275fba6ea9

Always a good idea to do a backup when dirty flashing.

Thanks again to the Lineage team for the updates.
[X Style (Pure) Android Development] Wheels564:
lineage-14.1-20210410-UNOFFICIAL-clark (Nougat bootloader)

New build up

Apr. 5, 2021 security patch

Nougat bootloader only

Md5: b46ae03b20c368330ffbcf6b306a631b

Always a good idea to do a backup when dirty flashing.

Thanks again to the Lineage team for the updates.
[X Style (Pure) Android Development] kb8no:
@Wheels564 I flashed back to stock. Then I installed TWRP 3.3.1-0 and clean flashed this nougat ROM. It starts up into the Goggle login but hangs at Google Assistant and can't get past it. Thoughts?

Addendum. I think my motherboard is borked.
[X Style (Pure) Android Development] Wheels564:
Did you try a clean flash without google to see if it boots properly? Sometimes you just get a bad build of gapps. Maybe try formatting each partition in TWRP instead of just wiping. If you flash stock again and everything works ok then I would have to think trying an older gapps.

Edit: Just don't format EFS partition unless you have a backup.
[X Style (Pure) Android Development] kb8no:
@Wheels564

Wipe - not

partition formatting - not

new 14.1 build - not

Gapps version - not

SIM card - not

Motherboard - not

I never suspected but you were right. The Gapps release was the problem. Not flashing Gapps allowed the LOS login and start the ROM. I arbitrarily grabbed 1/14 release from OpenGapps of my favorite mini version and it worked fine. The Google login is not playing well with the LOS login. It seems to be a regression bug in Gapps that generated the problem of the interface between the two.

Marginally related, We often need to do a clean flash back to stock. If you make a backup of a cleanly flashed stock, does restoring the backup work as well as a clean flash from scratch?
[X Style (Pure) Android Development] Wheels564:
I've never had an issue restoring a backup and I always do backup when dirty flashing updates. I rarely do a clean install unless there's a change like the one after the last official release of 14.1. I clear dalvik and cache once a month when I dirty flash my updates. I haven't run my N bootloader roms LOS14.1 and Crdroid rom with a sim for a long time to see how reliability is compared to MM.
[X Style (Pure) Android Development] virginwidow:
REALLY grateful to see active work on 14.1 (for any device)

Only Question - before I drop any more $$ tryin' to replace my Blackberry Passport (for that diabolical VoLTE)

(Q) Haven't found (yet) any comments how's the Camera?

Rly sorry, the "search" thingy didnt work that well before they broke XDA... Any input how to get the most out of the camera please?

THANKS in advance

VW
[X Style (Pure) Android Development] kb8no:
@Wheels564 I did a clean flash of 7.1 today using today's latest version of OpenGapps and it installed just fine without hanging at Google Assistant. It must have been a short lived regression or else a corrupted download before. Everything OK now. On another topic, this is the only LOS ROM for this phone that works on VoLTE and thus has not been been banned by Tmo (I think) and ATT (for sure) so I need this ROM for my ATT SIM. Verizon still works on LOS 18.1 but I don't know how long that will last.
[X Style (Pure) Android Development] Wheels564:
VOlte is why I'm sticking on 7.1 for now. However if you want you can try CRDroid I made for N bootloader. It's much more customizable and I'll be switching to it soon for my daily driver. It's pre rooted so you will have to use Lineage's root uninstaller zip then install magisk if you want to pass safety net.
[X Style (Pure) Android Development] virginwidow:
Where's the proper place to get assistance when installing twrp (3.1) fails after unlocking bootloader? (Which worked perfectly via Moto)

I've got a nasty "BSOD" nag screen, phone vibrates - and can't get to twrp at all, much less load a ROM... How do I get around this please?
[X Style (Pure) Android Development] Wheels564:
The BSOD is really just a nag telling you the the bootloader is unlocked.

From the bootloader flash "fastboot flash logo logo.bin". Here is the logo for Nougat bootloader.

Also you do not want to use the latest TWRP. That version is written for Pie roms and you will have an issue with F2FS. See post 1823 from Kb8no. You want to use TWRP 3.3.1-0 available from official TWRP website. When you flash recovery from the bootloader go directly into recovery from the bootloader with the buttons DO NOT reboot the phone as it will overwrite the recovery you just installed. Once your into recovery it will be saved. Make sure to do a backup in recovery then flash the rom by the instructions in the first post.
[X Style (Pure) Android Development] virginwidow:
Have saved logo.bin provided - maybe this will negate dis-permitting the successful boot into any TWRP (am gona factory reset, start again from 00, and take careful screeny's and log prompt output in future)

I thought there was bugs in the later ones - Will look up the post for further explains...

And try again with 3310 - I think my issue is there's something in the stock ROM that over-writes the TWRP as well as providing the ugly vibrating BSOD
[X Style (Pure) Android Development] virginwidow:
SUCCESS!!

the KEY Element is to use volume keys to select "recovery" right after getting TWRP (3310, as suggested) in there...

e.g. don't let the fone natively reboot, pressing the keys to get to recovery - that'll getcha a solitary dead robot with "no command" (meaning it's over-written TWRP, drop back and punt, rinse, repeat :mad:)

I've yet to experiment whether reboot to recovery NOW works using the keys from a "live" screen (after getting a ROM in...)

Gawd it takes old folks 4ever to learn... Sincere thanks for the help

VW
[X Style (Pure) Android Development] Wheels564:
lineage-14.1-20210619-UNOFFICIAL-clark (mm bootloader)

New build up

june 5, 2021 security patch

mm bootloader only

Md5: 9a631f7b09443b503c0efcc85d0ea271

Always a good idea to do a backup when dirty flashing.

Thanks again to the Lineage team for their continued support.
[X Style (Pure) Android Development] Wheels564:
lineage-14.1-20210619-UNOFFICIAL-clark (N bootloader)

New build up

june 5, 2021 security patch

Nougat bootloader only

Md5: 1670bcead58e64f4cde6e2cba30390c7

Always a good idea to do a backup when dirty flashing.

Thanks again to the Lineage team for their continued support.
[X Style (Pure) Android Development] Wheels564:
lineage-14.1-20210929-UNOFFICIAL-clark (mm bootloader)

New build up

June 5, 2021 security patch (with July security patches)

This may be the last update for Nougat based roms unless someone fixes the V8 vulnerability. https://review.lineageos.org/c/LineageOS/android_build/+/313397

mm bootloader only

Md5: 31f1be4010361927662e45b7f31934ca

Always a good idea to do a backup when dirty flashing.

Thanks again to the Lineage team for supporting Nougat as long as they have.
[X Style (Pure) Android Development] Wheels564:
lineage-14.1-20210930-UNOFFICIAL-clark (N bootloader)

New build up

June 5, 2021 security patch (with July security patches).

This may be the last update for Nougat based roms unless someone fixes the V8 vulnerability. See previous post for link to whats going on.

Nougat bootloader only

Md5: 84e8f6c9378b3a82cb7220ccad7065d4

** I have not had a chance to test this yet so make sure you do a backup. Send a reply if there's an issue. **

Thanks again to the Hashbang173 and the Lineage team for supporting Nougat as long as they have.
[X Style (Pure) Android Development] zanozaXX:
Everything work fine,thank you.
[X Style (Pure) Android Development] Fogasox:
Hola a todos. me funciono la rom 14.1 nightlies con la actualizacion 2018/11/22 con open gapps arm64 pico 7.1 en mi moto x style xt1570. dual sim funcionando y hasta ahora tiene buena estabilidad. La bateria mejoro bastante. Todo esto usando el bootloader TWRP.

Mod translation: Hello everyone. The 14.1 nightlies rom worked for me with the 2018/11/22 update with open gapps arm64 pico 7.1 on my moto x style xt1570. dual sim working and so far it has good stability. The battery has improved a lot. All this using the TWRP bootloader.
[Touch Dual, MDA Touch Plus ROM Development] Pharaohnough:
Folks,

Can someone upload or send me the file \Windows\CustAPLauncher.exe?

Thanks!
[Touch Dual, MDA Touch Plus ROM Development] therealholg:
just copy APLauncher.exe and name it CustAPLauncher.exe they are identical.
[Touch Dual, MDA Touch Plus ROM Development] Pharaohnough:
Thanks mate... Turns out I had it all along but it was hidden...
[Google Pixel XL Accessories] lioryte:
Mod please pin?

With the slew of new cables and chargers, you wanna keep your device safe. Here is the list done by Benson Leung and Nathan K.

https://docs.google.com/spreadsheet...qENiY2kgBJUu29f_TX8/pubhtml#?branch_used=true
[X 2014 Original Android Development] invisiblek:
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.

#include <std_disclaimer.h>

/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.

Download Links

LineageOS:

Nightly: https://download.lineageos.org/victara

Google apps addon:

OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 7.1)

HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.

Misc Links

Changelog:

Link: https://download.lineageos.org/victara/changes/

Learn to build yourself:

Link: https://wiki.lineageos.org/devices/victara/build

The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!

XDA:DevDB Information

[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Moto X 2014 (victara), ROM for the Moto X 2014

Contributors

invisiblek

Source Code: http://github.com/LineageOS

ROM OS Version: 7.x Nougat

Version Information

Status: Nightly

Created 2016-12-05

Last Updated 2016-12-05
[X 2014 Original Android Development] t0per666:
The awesome dev of our Victara! Thank you! ??
[X 2014 Original Android Development] BootloopedMillennials:
Thank you.

Is the storage menu in settings reading correctly? Using over 7GB of 14.xxGB space.

Edit Maybe it is right.
[X 2014 Original Android Development] loftwyr:
I installed this with a full wipe and gapps core. I'm not offered trebuchet as a launcher only pixel and google now. How do I get trebuchet back?
[X 2014 Original Android Development] Javten:
edit
[X 2014 Original Android Development] Gus Ghanem:
Some Gapps replace/remove the default/stock launcher (Trebuchet). Reflashing CM will not restore it, because Gapps have a script that prevents it. So, you would have to do a clean flash with a different Gapps package, or use Aroma or a gapps-config file to choose what gets installed and what gets removed.

Edit: or use Delta Gapps
[X 2014 Original Android Development] GustavoAvellar:
Which package is GApps Core? Did you mean Stock?
[X 2014 Original Android Development] loftwyr:
Yes, sorry, stock.
[X 2014 Original Android Development] GustavoAvellar:
The icons on Google Now Launcher are round, just like on Pixel Launcher?
[X 2014 Original Android Development] BootloopedMillennials:
Trebuchet was my launcher with the pico gapps.
[X 2014 Original Android Development] Gus Ghanem:
With Nano Gapps, and not much else. I'm still not that familair with Nougat yet.
[X 2014 Original Android Development] julian.c28:
Thank you! I'm excited now that it's available in Nightlies, downloading files now! :D
[X 2014 Original Android Development] efrainmarinho12:
I'm sorry. But how do I enable SystemUI Tuner and it's functions?
[X 2014 Original Android Development] mELIANTE:
Is anybody else having trouble with the mic?
[X 2014 Original Android Development] BootloopedMillennials:
Thank you. My install must have went bad. Did you see any errors while flashing CM14.1?
[X 2014 Original Android Development] Ghivoo:
I have trouble with the mic......
[X 2014 Original Android Development] Gus Ghanem:
Only the known 2 red errors, E: Unknown command (log), which actually don't affect anything. I wiped all 5 partitions before flashing, then the 4 non-system ones after. but. I think it's just reading space differently from MM, I don't think there's a problem. What you see under the Data image above, is what I usually see in Android 6 MM.

No I can't type, but the mic is working for me in the Search App.
[X 2014 Original Android Development] RockyTV:
Is video recording working? What about Snapchat (I think the issue with the app might be related to video recording).
[X 2014 Original Android Development] mELIANTE:
Mine's not working with any app...

I have installed Stock Gapps. Maybe the Pixel and Now launchers installed bring this about?
[X 2014 Original Android Development] Gus Ghanem:
I just tried a 4K video with the CM Camera, seems to be working fine. I can only get OK Google working from the Google App (Search). I only have Pixel Launcher installed, from the Play Store, so not in System, I have to tap the G then tap the mic to be able to talk.

Edit: I have the same things installed on my Nexus 7 2013 tablet, and I can get OK Google from any screen. The option is missing on this phone...