yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV General] mub786:
i user my pda with laptop to surf internet @ work

i use to use Ameo after surfing from 9:00 till 16:00 i still got 30-40% left on my Ameo

with MDA C4 with out TF3D used it for 30. battery drop from 99 to 84%.

if i use TF3d battery drain like mad.
[Touch Diamond, MDA Compact IV General] liamski:
Having a few issues myself, stock T-mobile UK ROM, TF3D running. Reading through somebody mentions an issue with the version of Google maps that is pre-installed, basically doesn't shut down the GPS fully even after closing the program. I uninstalled it, and installed the latest version from Google, version 2.1.0.10. Not sure about anybody else, but my battery life has improved hugely today, with the same usage as yesterday. Used Opera, several emails, several calls, Google maps, and general fiddling and battery is still around 80% (took it off charge 11.00 last night). Don't know if its a solution for everybody, but has REALLY worked for me......
[Touch Diamond, MDA Compact IV General] Bass-man:
4&5) What one do you recomend?

6) But with Nokias you never use it, the phone wakes up when you press any button

7) Yes, but how often?
[Touch Diamond, MDA Compact IV General] -=Dennis=-:
This is my 2nd day without recharging and still 40% left. I haven't made any calls but the phone was on and I used wifi a couple of times. Looked upon the album in tf3d a couple of times and some other things. So I think I cannot complain on battery capacity
[Touch Diamond, MDA Compact IV General] nazir:
MDA compact 4 Battery life

Hi

I left the phone for 4 days unused and the battery suvived,

but unfortunatly after changing the original rom and after inserting the sim card the phone now does not stand by more than one day

i tried the minimum use just phone on standby but still less than a day.

any idea about best rom on t-mobile for battery life. or at least the original rom to try

thanks
[Touch Diamond, MDA Compact IV General] VerusAmos:
I just installed AZTOR's x2 ROM, maybe it will prolongue the battery life. The original ROM last just a day, max 1,5 days. I hope it will improve now...
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] farshidheidary6:
Hi i have question , can i change my firmware? for example i flash a8 2018 firmware on a5 2017 ?

Or change the model number to any samsung phone i want ? (I'm using a5 2017)
[Samsung Galaxy A3, A5, A7 (2017) Questions & Answe] Fire1511:
no you can't, however [MENTION=4658360]corsicanu[/MENTION] managed to bring the firmware of A8 2018, try Hades rom
[OnePlus 7 Pro Guides, News, & Discussion] lollyjay:
Tru dat
[OnePlus 7 Pro Guides, News, & Discussion] galaxys:
Good luck...cheers
[OnePlus 7 Pro Guides, News, & Discussion] toxicimpression:
I got a full enclosure case and been out in rain all day. 15$ amazon. Just ignoring the girls lol. Kinda off-limits right now.
[X 2014 Original Android Development] npjohnson:
[IMG="LineageOS logo"]https://cygwin.de/rr/lineage-os-logo.png[/IMG]

Moto X 2014

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

Introduction:

This is the Official Lineage OS 17.1 thread for the Motorola Moto X 2014, codename victara.

How to Install:

Please follow the instructions on our Official LineageOS Wiki page here.

If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.

Known Bugs:

None.

Download:

LineageOS Updater

npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll find no support for these.

XDA:DevDB Information

[OFFICIAL] [NIGHTLIES] LineageOS 17.1, ROM for the Moto X 2014

Contributors

npjohnson, jeferson1979, linckandrea, tortel

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

ROM OS Version: Android 10

ROM Kernel: Linux 3.10.x

ROM Firmware Required: Newest firmware available for your variant/locality

Based On: LineageOS

Version Information

Status: Stable

Created 2020-05-15

Last Updated 2020-05-15
[X 2014 Original Android Development] franciscorizzo:
Hello,

this Android version don't have navigation bar?
[X 2014 Original Android Development] jeferson1979:
If you want the old behavior, you have to set in settings/system/gestures ;)
[X 2014 Original Android Development] idksomuch:
Just to confirm, we can't root our devices running this version of LOS, right?
[X 2014 Original Android Development] jeferson1979:
Soon it will be available a fix for magisk, it's in test yet, if you want to try, I've build one version with the fix. You can install at recovery, and after boot install the manager. It will ask you extra setup and reboot. Available here: https://sourceforge.net/projects/victara-universe/files/Android10/Lineage-17-1/Magisk/
[X 2014 Original Android Development] idksomuch:
That worked, thanks!
[X 2014 Original Android Development] jwhite5840:
Confused, only seeing LOS 16 builds on the official link from above?
[X 2014 Original Android Development] jeferson1979:
17.1 nightlies will be available soon. Hold with us a litlle :fingers-crossed:
[X 2014 Original Android Development] jeferson1979:
Official nightlies available :highfive:
[X 2014 Original Android Development] ChrisAG:
Installed without a hitch! Thanks guys!

(Dirty install using TWRP & factory reset, I'll see how it behaves).
[X 2014 Original Android Development] lantsem:
Installed latest lineage-17.1-20200530 build today. Found the following bugs:

1. In commit by [MENTION=5848265]npjohnson[/MENTION] CID 0x0 moved to XT0197's guard. So my XT1095 with 0x0 detected now as 1097. Purely cosmetic, but maybe it needs a correction.

2. No MCC and MNC codes or operator names visible on the roaming network. This bug was present also in 16.0. Last time it worked with 14.1.

3. rild crashes when I try to manually select a network (Network & internet -> Mobile network -> unselect Automatically select network) and I get 'Couldn't find networks. Try again.' in GUI. logcat attached.
[X 2014 Original Android Development] ywlke:
Amazing work! That my XT1095 which shipped with Android 4.4.4 can now run 10 is remarkable. The 5/30 build is working great so far, using the beta Magisk from a few posts back.

Prior to LOS 17.1, I was running LOS 15.1 (unofficial). I noticed that neither official LOS 17.1 nor LOS 16 (which I used for 1 day, and then 17.1 came out!) can drop the screen brightness as low as 15.1 could. Is it possible to bring back the lower-than-OEM brightness feature?
[X 2014 Original Android Development] jeferson1979:
I'm aware of this and now a potential fix wich I will test tomorrow. (Rild on searching). Thanks for the log

---------- Post added at 12:49 AM ---------- Previous post was at 12:48 AM ----------

We will look for it ASAP
[X 2014 Original Android Development] jwhite5840:
Just attempted to install LOS 17.1 official nightly 20200601 using TWRP 3.2.1-0 today.

Clean flash completed without error but on reboot got "Encryption Failed" splash screen indicating a factory reset was needed.

Went ahead with that - it booted to TWRP and did a wipe, then rebooted again to the same splash.

Detailed steps were:

(1) Successfully boot OS to LOS 16 20200419

(2) Mount internal storage and copy lineage-17.1-20200601-nightly-victara-signed.zip and open_gapps-arm-10.0-stock-20200530.zip

(3) Boot to recovery TWRP 3.2.1-0

(4) Standard wipe (factory reset)

(5) Install lineage-17.1-20200601-nightly-victara-signed.zip

(6) Wipe cache/dalvik

(7) Install open_gapps-arm-10.0-stock-20200530.zip

(8) Wipe cache/dalvik a second time

(9) Attempt to boot OS to LOS 17.1 20200601 - got LOS boot animation followed by "Encryption Failed" splash indicating factory reset needed

(10) Accepted factory reset "Erase Everything" button

(11) Boot to recovery automatically

(12) Automatically perform factory reset wipe

(13) Attempt to boot OS to LOS 17.1 20200601 - got LOS boot animation followed by "Encryption Failed" splash indicating factory reset needed

... loop ...

Was able to restore from TWRP LOS 16 20200419 backup without issue.

Any suggestions?
[X 2014 Original Android Development] Jaytn:
Interesting, I got the same screen dirty flashing over 16.0 and just thought it was due to my dirty rom (I messed something up before, regular 16.0 updates wouldn't boot) or me screwing up the update process. But since you got it on a clean flash, maybe it's something different?

For completeness, I followed the guide from the updater (see here), namely:

- LOS 16.0 2019-12-27 installed (with opengapps)

- (make a backup in TWRP)

- (not wiping anything)

- reboot to sideload

- reboot to TWRP and use sideload there (regular wasnt working for some reason)

- sideload 17.1 2020-06-01

- flash new opengapps (as per instructions) from TWRP (not sideload, because that wouldn't apply my gapps.config)

- reboot "Encryption failed"

- (restore to backup and give up for the moment)

Also not to mention, I didn't have my phone encrypted on 16.0
[X 2014 Original Android Development] jeferson1979:
Answer to all points: you need to be full ext4 at your filesystem for lineage-17.1. As well dirty flash Android version to another never delivered good results.
[X 2014 Original Android Development] jwhite5840:
DATA was f2fs - switched to ext4 and repeated previous steps, worked like a charm. Thanks!
[X 2014 Original Android Development] MauricioJorge:
magisk does not work

Any solution? already installed beta version and it doesn't work
[X 2014 Original Android Development] Deleted member 10693049:
Does anyone else experience bootloops if you try to boot the device with Secure Startup enabled?
[X 2014 Original Android Development] jeferson1979:
As you commented on issue, connected you are able to boot?
[X 2014 Original Android Development] :
[MENTION=8863813]jeferson1979[/MENTION] No, plugging the charger in does not help with booting, it still continues bootlooping.

I managed to get it booting once by connecting the charger, but I was unable to reproduce this behavior. The single successful boot with the charger may have actually been pure coincidence.

But I just noticed that there is a certain chance that it boots up fine the very first time after enabling Secure Startup. But all (?) subsequent reboots seem to result in a bootloop.

EDIT: After continued testing today, I could no longer verify the issue without Open GApps installed, so I guess this might be related somehow to Google apps? I've updated the bug report accordingly.
[X 2014 Original Android Development] lantsem:
camera HDR bug

mm-qcamera-daemon crashes with HDR mode for camera (snap).
[X 2014 Original Android Development] jeferson1979:
HDR is fixed for next nightly
[X 2014 Original Android Development] ywlke:
I noticed the other day that the DTMF tones with preprogrammed numbers (i.e. saved in a contact with pauses) are way too long and not getting interpreted correctly by the other end. Googling around suggests there is a system setting dtmf_tone_type that can be changed (https://xdaforums.com/galaxy-s3-att/decrease-length-touch-tone-dialer-t2810483) which is often exposed in the Dialer app (https://help.ting.com/hc/en-us/articles/115005081167-Changing-the-DTMF-Tone-of-your-Android-Device) but I can't find the setting, or how to change it on Android 10 which no longer uses a SQLite database for system settings storage. Any thoughts?
[X 2014 Original Android Development] MauricioJorge:
magisk doesn't work, i don't know what else to do.

I already installed the beta version and it didn't work
[X 2014 Original Android Development] ttocs99:
Patch the boot.img then install magisk manager.
[X 2014 Original Android Development] jeferson1979:
You need to install app.debug.apk attached few posts later, then, allow additional setup
[X 2014 Original Android Development] TomOehser:
That worked for me - what is it doing? Will it eventually roll into magisk, or roll into lineageos, or stay a separate step?
[X 2014 Original Android Development] MauricioJorge:
how do i do this? have any tutorial? where do i download?
[X 2014 Original Android Development] jeferson1979:
I'm not a magisk builder, but seems the installer don't make the work itself, it won't install magisk manager, that app is magisk manager and the last step is related to environment setup
[X 2014 Original Android Development] MauricioJorge:
the system is working perfectly so far with no bug found, with the exception of the magisk that I couldn't make work

the 4g signal is perfect for the first time in years of testing with lineageOs

what should i do to solve the problem with magisk?

where do I find Patch boot.img?
[X 2014 Original Android Development] ttocs99:
If you have this ROM installed. Open the zip file and extract the boot.img and put it somewhere on your phone or as card. Install magisk manager and click install magisk, from the list click patch boot.img and let magisk do its work. Once completed pull the newly patched boot.img of device and flash it via fast boot as fastboot flash boot boot.img. reboot phone and check magisk manager and it should say that it is installed.
[X 2014 Original Android Development] TomOehser:
It was in the fifth post of this thread, https://xdaforums.com/showpost.php?p=82680415&postcount=5
[X 2014 Original Android Development] MauricioJorge:
I will test thanks ?

---------- Post added at 04:27 PM ---------- Previous post was at 04:26 PM ----------

tested it and it's working perfectly thanks ????
[X 2014 Original Android Development] TomOehser:
Seems that "hey google" is still broken. It's a known bug, right?

In 16/pie, the "ok google" capability broke - I saw, I think, that it was a known issue and that there was disagreement (between lineage/magisk maybe?) about who was doing the "the wrong thing".

I'm disappointed to see this still broken? Is anyone else irked, are there any workarounds, is there any view-forwards to a resolution?

-Thanks....
[X 2014 Original Android Development] jeferson1979:
Workarounds are not the right way, you can help to fix providing log ;)
[X 2014 Original Android Development] ttocs99:
Flashed this all works great. Even passed safety net with no root.
[X 2014 Original Android Development] D@rekills4:
Oh man. Thank you for supporting such an old device!

I want to flash this, but my battery is dead and there is not a single online store in my country selling battery for this device. :(
[X 2014 Original Android Development] ttocs99:
Just flashed latest July patch but it is still stuck on June security patch is that correct like as in July patch hasn't been merged yet.
[X 2014 Original Android Development] jeferson1979:
Check build date. Last week we have a failed build, this now is fixed.
[X 2014 Original Android Development] jeferson1979:
Oof sad, maybe imported?
[X 2014 Original Android Development] ttocs99:
My build date has changed but security patch hasn't so I downloaded it again as I'm using lineage without root and when I flash through twrp it says failed to magisk add-on but I've never flashed magisk with this rom also mention something about decryption but my device is all ready decrypted
[X 2014 Original Android Development] ttocs99:
Screen shot of about phone, build date is correct but security isnt?
[X 2014 Original Android Development] Jaytn:
That is correct, July patch isn't out yet.
[X 2014 Original Android Development] Manosdocpap:
Any chance of VoLTE being enabled on this ROM?
[X 2014 Original Android Development] jeferson1979:
Victara unfortunately never supported volte
[X 2014 Original Android Development] D@rekills4:
India v/s China.

All imports are held by customs.

Anyone know of a battery in the European market?
[X 2014 Original Android Development] Jaytn:
I've bought my second one now here in Germany. Apparently they do still make them.

The search term you need is "EY30", that's the name of the battery. Maybe you find one with that.

Something else. With the latest update the "Pixel Launcher keeps stopping" issue is back.

Anyone else? I'm going back to previous version.
[X 2014 Original Android Development] Manosdocpap:
A fantastic ROM, a fantastic phone, a fantastic execution.

Phone launched with 4.4 kitkat. Still supported, still ahead of its time.

AMOLED, AOD, GESTURES (nobody had it back then), small bezels, compact phone.

I found a new EY30 battery at Aliexpress and it is holding more than a day.
[X 2014 Original Android Development] jeferson1979:
:victory: Another passionate as me
[X 2014 Original Android Development] ttocs99:
Been suffering random reboots the last few days, either when on call or using reddit. It could be out of memory situation as it could go fine for few days but then reboot just happens.
[X 2014 Original Android Development] jeferson1979:
Imma go try to reproduce here
[X 2014 Original Android Development] astrod:
Are the batteries easy to replace?
[X 2014 Original Android Development] Manosdocpap:
Not so easy, not so hard.

https://www.youtube.com/watch?v=fidHKn-J-0M

It took me about 20 minutes, being careful. You'll need adhesive tapes to re attach the back cover.
[X 2014 Original Android Development] Jaytn:
I'd say fairly easy.

Not like "removable battery" easy, but much easier than the new glass-back phones. It's a little work, but if you know how a screwdriver works, you'll be fine.

Here's a good guide too: https://www.ifixit.com/Guide/Motorola+Moto+X+2nd+Generation+Battery+Replacement/40717

The hardest part IMO is getting the back off the first time, since it's pretty well glued in, but if you got a plastic back you can bend it pretty hard, and as you can see in the video, there are only a few areas with fragile parts, so you can scrape with a plastic tool under the back to get the glue off. (And if that's the hardest part, you know how hard it is to do ;))

A few tips: You can lift the entire back half off, once you undo all screws and unplug the two "Lego" connectors under the rubber things. You don't need to undo the little "lever" thing. There you only need to lift the little board it's in up, because it's glued to the battery. See step 7, I also didn't need to remove the back logo, just be careful if anything hangs when you remove the battery.

Be careful with what screwdriver you get. Some guides say T4, others T3 - apparently both screws were used by Motorola. Mine were T3. If you can, try which ones you got. But I'd say invest the 5-10 bucks to get a good one, you really don't want to strip the heads, then you're "screwed" (I'll see myself out)

If you need any help, just ask, I've had mine open ~10 times now :laugh:
[X 2014 Original Android Development] renzs:
edit: found it :)
[X 2014 Original Android Development] Manosdocpap:
WOW. latest build, scrolls smoother ever.

Dafaq happened ? Thumbs up
[X 2014 Original Android Development] ptitrusse:
Just installed, works beautifully, thanks very much !
[X 2014 Original Android Development] ttocs99:
Installed 6 September build. Running smoothly. No reboots as yet. Don't know what's happened but its running notable quicker, apps open faster etc?? But I'll take that! Thank you.
[X 2014 Original Android Development] bundys:
Can't Install Magisk in TWRP on MotoX 2014

Just installed los 17.1 after using 16 for a while. I don't like messy upgrades, so I wiped the phone and flashed LOS, GApps and Magisk all in one go. No error messages, so I was happy, until it booted and Magisk Manager told me Magisk wasn't installed - strange. So I booted into TWRP, flashed the magisk zip again, looked at the screen, no error messages, so good to go, right - wrong! Still no Magisk after rebooting. Tried a couple more times, wiping caches and such, but no difference. There are no errors being thrown, but for some strange reason it won't flash the Magisk module.

Has anyone else run into this? Any help would be appreciated.
[X 2014 Original Android Development] linckandrea:
Flash the latest magisk canary build
[X 2014 Original Android Development] marcelo2866:
Victara get Lineage 18 ?
[X 2014 Original Android Development] Vitnim:
Clean install of current 17.1 nightly and I have no audio from the earpiece during calls (radio or internet calls). Speakerphone, bluetooth audio works. Everything else seems to be functioning perfectly. Any ideas of where to begin looking for the issue?

Thanks
[X 2014 Original Android Development] juanchotazo99:
Wanted to say that Magisk 21 now works out of the box for official LOS, no need to do anything to get it working. Just flash in recovery like any other phone and install your modules.

Safetynet passes out of the box too, no issues.
[X 2014 Original Android Development] Unisys:
Any plans for LOS 18 on this device?

I have the possibility to purchase this device. I would do so because I have seen how smooth LOS 17.1 works on the Victara. Any chance of bringing android 11 on this device? Thanks in advance.:good::fingers-crossed:
[X 2014 Original Android Development] mife2032:
Thanks for the ROM it's working like a charm. However I noticed the device performance slider located under battery and performance settings is missing, it was there in LOS 16. Any way to bring it back?
[X 2014 Original Android Development] leo_97:
Guys, anyone here had problems encrypting the phone? I installed this ROM, used for some days and then tried encrypting. Now the phone (when in TWRP) doesn't accept the password and got a bootloop.

Any links or recommendations?

Thanks in advance.

Edit: I've managed booting the phone again reflashing the stock ROM
[X 2014 Original Android Development] juanchotazo99:
I've found that after encrypting, when it gets stuck in the loading animation after entering your pin/pattern it helps to completely turn off the phone (use hardware keys to reboot to fastboot, then turn off), then turn it on, and wait a little before entering your credentials again. It'll eventually boot.

Want to recover your data through TWRP if you can't get it to boot? As you've found, TWRP can't decrypt, latest version (3.5.0_9-0) included. Doing it through adb and manually entering your password or pattern equivalent password doesn't work either.

This is annoying, so I just formatted /data and I'm not using encryption. I'm using lineage-17.1-20210124-nightly-victara-signed.zip, clean flashed.

Despite all this, it's an improvement. Back in the 14.1/16 days you couldn't encrypt, or encrypting resulted in a permanent bootloop. At least it sometimes works now.
[X 2014 Original Android Development] npjohnson:
I have every one of my other QCOM devices running LineageOS 18.1 at the moment, so it's a shame to see victara stuck on 17.1. I did the bringup work here:

npjohnson/android_device_motorola_victara

Contribute to npjohnson/android_device_motorola_victara development by creating an account on GitHub.

github.com

It doesn't boot currently, it loops and hard hangs then reboots.

If anyone has any ideas, or can get it at least not to hard-hang, I can take another look but I just have no idea why it's crashing right now.
[X 2014 Original Android Development] ptitrusse:
Hi

Thanks for the great rom ! anyone having echo in VOIP apps like signal ?

thanks
[X 2014 Original Android Development] *_Axl__Rose_*:
Front Camera and video recording not working on this build 20210214,help please 😄 Brazil 🇧🇷
[X 2014 Original Android Development] douglasmarx:
Low quality of recorded videos (LOS 17.1 21/02/2021)

I'm having some problems recording videos. When record with WhatsApp (e.g), I can't send it, because a message ask me to choose another video. When record with the stock camera, or Gcam, or Cameringo+... the quality of the recorded video is very low, an the options to change between resolutions inside the apps are very limited, when they show some options...

I've tried Open Camera and Moto Camera (ported, xda...), but still recording in very low quality. The video informations says that's recorded in .3gp format and 0.1 MP, don't matters what camera app I'm using... Probably something with the rom video codecs, I guess...

Have some kind of camera app or another way to solve this problem? Thanks.
[X 2014 Original Android Development] npjohnson:
I fixed it - will be adding it to 18.1 roster soon :)

We are aware, and testing potential fixes.

Will be fixed in next build - sorry about that!