yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] sage of six paths:
I managed to fix the phone and the fix was cheap, something about voltage.

I'm back to stock for now, will be waiting news here for further progress.

edit

Installed the stock nougat with the pixel laucher found here on xda, fantastic experience.

Disabled all of the moto preinstalled apps and got my self just the rom i wanted.

Might not need to move away from if at all.
[X Style (Pure) Android Development] kb8no:
Read before you post. No less than 3 of the last four posts have the answer.
[X Style (Pure) Android Development] ghurkan:
Read before you reply.

I specifically mentioned FRONT camera.

I know that the main camera is not ready yet. Everyone who uses Oreo usually says "Only the front camera is working" or something similar. So I thought the front camera is photo capable at the moment and my phone has some issue.

If the front camera wasn't also working, I think people would have said so.

So, yes, I have read the recent posts, rest of the whole topic actually. They don't say anything about front camera.
[X Style (Pure) Android Development] kb8no:
Sorry for being so snippy and making assumptions. Back camera broke as we all know. FRONT camera appears to work but crashes when you try to take a photo. However video works on front camera. There is a post on this but I can't find it now. I'll keep looking, might be on different forum.
[X Style (Pure) Android Development] kadopt:
[MENTION=4465682]kb8no[/MENTION] [MENTION=7804913]ghurkan[/MENTION]

It's on post #1571 by myself.
[X Style (Pure) Android Development] ghurkan:
Even if there was a post on this matter that answers my question completely ( which apparently there is one, thank you [MENTION=3723165]kadopt[/MENTION] ), this does not require such response. You could have been just as useful by saying "Yes, it's a known issue".

We are all here to discuss and share information on something we love and try to make better. Let's keep it that way
[X Style (Pure) Android Development] kb8no:
My bad behavior had nothing to do with [MENTION=508042]kodo[/MENTION]pt useful post. I was only trying to redeem myself and refer to his post to be helpful after a mistake jumbling up front and back cameras. Sigh.
[X Style (Pure) Android Development] ashoka.inder.dev:
Checking Battery Health

Hi,

I'm on official lineage os, this battery issue just killing me. The issue are:

1) Phone will switches off between 20%-35% charge. No pattern on specific %. (Regular)

2) Random switch offs when battery is below 50%. (Once in 2-3 days).

The issue now I believe is probably driven by dying battery despite the fact that last month stock rom gave me descent performance, I'm still doubting that its the dying battery.

No issue in buying new battery but the little environmentalist in me suggests to use the battery till it has juice and does not damage the phone.

So is their any way I can identify after year of deterioration how much charge my battery is holding (like 40% of original charge) and how is the drain pattern. I tried some apps like Ampere by Braintrapp and all but they are not the expected app. I want to see the entire battery health status (I have su access so believe its possible I can use some alternate to linux's upower -i `upower -e | grep 'BAT'` command with busybox?)

Out of battery question:

I'm trying to identify the reason as to why phone when disconnects from Wifi and moves to cellular data and thereafter, the phone literally cries while running. In fact it takes a good amount of time to open the dialer itself(I use google dialer and rom default dialer removed via opengapps). And the problem is not limited after Wifi to cellular switch but during most of time when its on cellular network. What could be possible reason? to limit options, I use greenify app and also have hard configured the privacy gaurd (in lineage setting) to limit very very few app with background and boot access. Even without greenify the response is slow, so I'm doubting that some setting by me in within the ROM is causing this issue to me.

For this I'm not exactly looking for solution as it could be caused by multiple reasons, therefore looking for guidance to move in right direction so that I can identify the sudden drop in ROM response during Wifi disconnection and cellular data.

sorry for such long post.
[X Style (Pure) Android Development] muelo1000:
Yeah same for me ,phone randomly will shut off even with 40% battery ..and now it's just stuck on a boot loop
[X Style (Pure) Android Development] AsquareX:
You can try this app called "AccuBattery". After a few charging cycles, it shows the overall battery health and how much charge it can hold compared to its original capacity. You can try it know if it's your battery dying or there's any software thing that's causing the reboots.
[X Style (Pure) Android Development] bezangeloo:
I had the same shutdowns problem you guys describe (I have my phone for 2 years+). It was the battery fault.

I replaced the battery and the problem disappeared.

But unrelated to that, I'm having (very very annoyingly) poor performance. It's like that for the past few months.

I have the XT1752 model with LineageOS (14.1-20180606). Any Ideas?
[X Style (Pure) Android Development] OverkillSRB:
Maybe update to new lineage version?
[X Style (Pure) Android Development] bezangeloo:
It was a typo :-\

My version is 14.1-20180606 (latest one)
[X Style (Pure) Android Development] OverkillSRB:
Did you have issues on the earlier ones? How does the bad performance manifest?
[X Style (Pure) Android Development] bezangeloo:
Nope. When I moved to LineageOS everything was great.

But performance got worse with time.

Now sometimes when I typing the character appears with delay (even more than 1 sec sometimes), apps takes forever to load (30+ seconds to open waze isn't reasonable), overall response time got longer than my old galaxy 2 :-\

I tried to wipe everything (cache&dalvik&data) for several times. The situation improves for realy short time than back to suffer.
[X Style (Pure) Android Development] OverkillSRB:
With time, you mean with every new build or with the same build over time?
[X Style (Pure) Android Development] bezangeloo:
I always update through Ota when an update is available. So I guess with every new build.
[X Style (Pure) Android Development] OverkillSRB:
Did you try wiping the whole system, and flashing from 0?
[X Style (Pure) Android Development] bezangeloo:
nope. I will try it
[X Style (Pure) Android Development] OverkillSRB:
Definitely try.

Wipe system, dalvik, cache, data.
[X Style (Pure) Android Development] ashoka.inder.dev:
Battery Screenhot

Screenshot of Battery charge, this screenshot is when the device switched off at around 60% and on switching on booted with 2 or 3% charge only. On charging it immediately climbed to 50% with android expecting that the battery will get fully charged in under 2 mins at this speed. It is different story that after 60% it charged normally as usual.

Other times it fails at 30%, 20% or any other percentage that android finds optimum and then it wither does not switch on or switches on with 2-3% battery only.

Made my mind to test with new battery, so as soon the battery is available at the local Motorola Service center, I will asap change and post update.
[X Style (Pure) Android Development] KC69:
Does anyone know if camera works on latest 15.1 from today?
[X Style (Pure) Android Development] ghurkan:
Sorry but nope. Only the front camera works and that can only take videos, taking photo crashes.
[X Style (Pure) Android Development] biggy238:
OK. I need help.

I had a notification for the ROM update that I've been putting off. For the last 3-4 days I was getting messages about my camera app not having needed permissions, and no matter how many times I set it as the default, it would ask again.

The battery died at 4pm yesterday. I brought it home and it was on charge ~5hrs. I came inside, unhooked the phone and powered it on. I saw the boot logo and I sat it on the arm of the couch. I picked it up about an hour later, and the backlight was on, screen black. Every 10 seconds the feedback motor would vibrate, and the right of the notification bar would display the battery circle! Icon and no SIM icon and the incorrect time.

Recovery also displayed the wrong time.

I rebooted several times, and would either get a short boot with the screen described above, or splash screen for lineage. It ran the splash screen for 6 hours. I made a backup of my data partition.

This morning I removed my external. SD, wiped, installed 0606 nightly and latest Gapps. It booted, repopulated applications, made phone calls.

I flashed Magisk V16 and same boot problems.

I wiped at reinstalled. This time I restored the data part. Failed to boot.

Now, everything is fresh and working.

The real problem: I can't see the SD card contents. I can see in settings/storage that the SD card has about 18gb of data on it, but I can't view any of it, and Ubuntu can't see it.

The folder structure from before is still there, but the folders are all showing empty.

I need a way to extract the files from the SD card.

I hate to wipe the external/extended SD just to make use of it again.

Any help would be appreciated.

EDIT: NM. It's all gone.

WTF happened?
[X Style (Pure) Android Development] ashoka.inder.dev:
Had faced similar issue in past. Worst case, no recovery tool is good enough for sd cards. I too lost data. All tools are hit or miss case with sd card data recovery.

Try to fix free recovery tools available on internet. No benefit of purchasing paid solutions.
[X Style (Pure) Android Development] pbialy:
VoLTE & WiFi Calling

Does anybody know, whether VoLTE and WiFi calling work in this ROM for operators in Poland (Orange, T-Mobile, etc.) ? Or do I need to flash extra settings from somewhere?
[X Style (Pure) Android Development] Breezeblocks:
Does anyone know how stable 20180513 for 14.1 is, or rather what is the most stable of the unofficial 14.1 builds? I'm currently on 20180210; I like it well enough except for the calling issues (calls constantly get dropped or other person can't hear me, especially if data is turned on). Thanks.
[X Style (Pure) Android Development] Chris001:
I am using the latest unofficial build since release date. Pretty stable so far :good:
[X Style (Pure) Android Development] kb8no:
Same experience. Good DD. No luck with VoLTE on Verizon however.
[X Style (Pure) Android Development] ashoka.inder.dev:
Update bug is back again :crying:
[X Style (Pure) Android Development] pbialy:
Bootloader 0xA052

Is there a way to install official nightlies with bootloader 0xA052, which comes from newest Nougat official OTA?

Another question - among HashBang unofficial updates:

https://androidfilehost.com/?w=files&flid=131793

the most recent which works for me, is lineage-14.1-20171227_144801-UNOFFICIAL-clark.zip, the later ones cause bootloop - after Motorola "unlocked bootloader" warning I'm getting constant restarts to the same warning screen.

Just one more question - are LineageOS builds showing aggregation like "LTE+" or "4G+" in an icon? I see that LTE aggregation works, but cellular icon is just showing 4G and nothing more.
[X Style (Pure) Android Development] kb8no:
Your question is just shy of having enough information. I must assume you took OTA Nougat which had a firmware upgrade so you are now on Nougat firmware. Then No in this case.

Official 14.1 is for MM firmware / bootloader only. Nougat firmware / bootloader will bootloop or error if you try to use official 14.1. There is no official for Nougat firmware yet. If you are on Nougat OTA and firmware you can use unofficial 14.1 or unofficial 15.1 from Hashbang which are made for Nougat firmware. They work well.

Hashbang uses a bootloader whitelist to try to manage MM and N firmware issues. This is all well documented above so read more. This forum has inherent confusion because it is for Official MM firmware and 14.1 but most of the current discussion is about Unofficial N firmware and 15.1. Make sure you are doing completed clean install.
[X Style (Pure) Android Development] pbialy:
Is this possible, that I revert from current Nougat firmware / bootloader to MM firmware / bootloader to have possibility to install official 14.1 updates? I have of course unlocked bootloader.
[X Style (Pure) Android Development] kb8no:
If my assumptions are correct, then I bet this is your problem. Early Hashbang unofficial 14.1 needed system formatted in a nonstandard f2fs and an unofficial TWRP to support. I believe the 2018/2/10 was the first release where he upgraded to the proper version of f2fs which used the official TWRP . When he made this change you needed to use official TWRP to manually reformat and unofficial TWRP was obsoleted. This is well documented "back in the day". With the proper formatted f2fs and proper official TWRP the recent unofficial 14.1 will not bootloop. I think it was the data partition.

---------- Post added at 07:19 AM ---------- Previous post was at 07:12 AM ----------

This is the problem. You are crossing over between different firmware without knowing. Can't tell for sure what you did. So you use official TWRP? We can solve this. Can you get yourself back to stock Nougat? There is no need to go back to MM and use official 14.1. Do you have unofficial 2017/12/27 working? If so, this proves you have Nougat firmware.
[X Style (Pure) Android Development] pbialy:
Ok, I will sumarize:

- I had latest official Nougat working, however as we know, full of Motorola bugs (e.g. GPS);

- I have bootloader 0xA052, which comes I suppose from the latest official Nougat from Motorola (7.0);

- I have unofficial TWRP 3.1.1.0, as latest official 3.2.1.0 was displaying only TWRP logo and resetting;

- I have unofficial 2017/12/27 working, later builds were bootlooping;

So, should I format system partition to F2FS from current unofficial TWRP, and try to install official TWRP, and then unofficial latest build from 2018/05/13?

My system partition is EXT4 and data is F2FS currently.
[X Style (Pure) Android Development] cafelattegames:
bootloader firmware downgrade

No it's not possible to downgrade your bootloader firmware. Just use the latest unofficial firmware from hashbang's AFH. Currently 14.1 is the more functional as the rear camera works.
[X Style (Pure) Android Development] kb8no:
OK. You have unofficial 14.1 from 2017/12/27 working. Therefore you have nougat firmware using obsolete f2fs on your data partition from unofficial TWRP. You must format data with updated f2fs using official TWRP. Only then will the current versions stop bootlooping. Those of us starting N firmware from the beginning all went through this. Read way back in the forum how to do this, I don't have time now. I could help you more later.

You could also fastboot stock nougat which formats all the partitions with proper f2fs data. Then flash official TWRP and use that to flash the latest unofficial 14.1. I can give you the link later.
[X Style (Pure) Android Development] hasekev99:
Have flashed the 15.1 ROM of Hashbang. The Trust APP always shows SELinux Disabled. Is that correct ?
[X Style (Pure) Android Development] parker.stephens:
If you downgrade your modem (NON-HLOS, erase modemst1/2, fsg) and bluetooth then technically yes you can flash the latest nightly with a bit of tinkering the zip file. Hop on your PC and extract the .zip, then navigate to META-INF/com/google/android and then open updater-script in a decent text editing program (eg. Notepad++). Then on the second line, change any bootloader, for example 0xA01C to 0xA052. Then overwrite the file, not as a .txt file, and then recompress the archive. Then sideload it to your device and flash it. Note that you will have to do this every update.
[X Style (Pure) Android Development] fritzophrenic:
Problem building unofficial 14.1 kernel?

[MENTION=4630246]Hashbang173[/MENTION], thanks for your continued work on this phone!

I have been self-building from your 14.1 repos since sometime in April, so that I could have a signed build, and so that I could grab security patches, etc. without waiting on a new build on your androidfilehost. The attached roomservice.xml file was working for me.

Sometime this month, the build stopped working. My last successful build was on May 27. I have tried several times since then but get errors during the build. I notice your last build on androidfilehost is from May 13, so I'm not sure whether it's something I'm doing wrong or if something is broken. I attached the errors from today's attempt in build.out. Other than the roomservice file, I don't think I have any local modifications (at least, none that are intentional). I checked a few repositories including the kernel and device trees but not all of them. It looks like you have not made any changes to the kernel or device trees on the 14.1 branches for several months now, so something else may have changed to be incompatible. Do I just need to pull some other repo into my build? Am I on the wrong branch? Did you forget to push some changes? Or is this a real failure that needs to be addressed?
[X Style (Pure) Android Development] Hashbang173:
Try running this before building (after lunch probably)

export LC_ALL=C
[X Style (Pure) Android Development] hasekev99:
The Nightlies by lineage os do not work with the nougat firmewae, or ?
[X Style (Pure) Android Development] Invisibleman123:
When is lineage OS 15.1 coming to the x pure.
[X Style (Pure) Android Development] ghurkan:
Yes.

Nightly Builds are official and use MM, they don't work with Nougat Firmware. Unofficial ones use NM, both 14.1 and 15.1.

NM using ROMs are pretty few. Here is a list https://xdaforums.com/moto-x-style/general/custom-roms-nougat-modem-t3733105
[X Style (Pure) Android Development] drock3260:
Just loaded hashbang's lineage-14.1-20180513-UNOFFICIAL-clark on my moto x pure. I am on verizon and most things seem to be solid, but mms is not working. If I try to send any mms (group or picture) I get an invalid address error. I took a look at the APN settings and it they don't look right. All APN settings are grayed out and I do not have the option to edit. anyone else run into anything like this or have any ideas?
[X Style (Pure) Android Development] mddunner:
I had this come up for me on other lineage based roms with Verizon. Also issues with cdma calls. I was running fine for a year or so then the problems started in the last couple months. Never got to the bottom of it unfortunately.
[X Style (Pure) Android Development] fritzophrenic:
Thanks, that got me past the build issue in my post. Unfortunately something is still wrong, because now I'm getting link errors in the bluetooth stack. The attached build output is one I captured yesterday but I am getting the same errors today, after increasing the max size for "jack" to avoid out-of-memory errors, and after clearing ccache in case there were any corrupted items.

Should I just delete my lineage folder and recreate from scratch? I assume you're able to build still.

*Edit* to mention: I am not following the standard build instructions but rather the instructions for creating a signed build. So I ran "mka target-files-package dist" instead of "lunch clark". And I did "mka clean" before that in an attempt to do a full build, it appeared to have worked but I'm not sure that's the right command.
[X Style (Pure) Android Development] drock3260:
I think I might be able to edit the apn XML file to force the correct settings on an APN refresh. Just need to verify which set it's grabbing (it pulls 5 different ones that are all wrong)
[X Style (Pure) Android Development] kb8no:
I get the wrong Verizon APN from the SIM Card occasionally when I flash an update. I reset the APN's and pick vzwinternet.
[X Style (Pure) Android Development] *.jpg:
I, too, have had that problem. It may be related to your SIM. Nougat seems to have changed something related to access to the SIM. Others have reported that a new SIM fixed this problem.

I'm using one that I cut down that I've had since the Note 2 came out so I ordered a free replacement and will report back whether this fixes it or not.
[X Style (Pure) Android Development] mddunner:
The first time I had the MMS issue, a new SIM card did fix it. This second time, the new SIM did not resolve the issue, but I had already messed with settings in the hidden Menu. In the nucleaROM thread, [MENTION=5781153]ResistanceIsFutile[/MENTION] pointed out that the modem seems to go haywire if you touch the region settings. They had success reflashing modem files from fastboot. I ended up with a complete stock flash from fastboot and have been running that since...
[X Style (Pure) Android Development] fritzophrenic:
As it turns out, somehow the files in system/bt repository had been modified. I did not do this myself and I have no idea how it would have happened. But a "git reset --hard github/cm-14.1" in that directory fixed the issue for me.

I learned to use "repo status" and "repo diff" commands in the process. :)
[X Style (Pure) Android Development] KC69:
New 15.1 out. Have to ask. Camera??? And I know it's OT but is the havoc ROM I see Oreo? Or nuoghat? Sorry to ask here but I don't see a topic for it anywhere.
[X Style (Pure) Android Development] hasekev99:
I habe installiert the last ROM 15.1 from 09.07.2018 and i received following messages

This build was sind with puplic keys

SELinux is not striked

SELinux ist deakriviert

Are they known and what it means ?

Sorry for my Bad english
[X Style (Pure) Android Development] Chris001:
Does your camera work? Back camera in particular?
[X Style (Pure) Android Development] hasekev99:
No
[X Style (Pure) Android Development] Chris001:
okay :(
[X Style (Pure) Android Development] rafmal000:
I keep getting this error trying to install Hashbang's 20180513 build:

This package supports bootloader(s): 0xA050, 0xA052; this device has bootloader .
Updater process ended with ERROR: 7

I have bootloader A0.52 so I don't understand why I'm getting this issue.

Edit: I edited the updater-script to remove the bootloader check and it works fine now.
[X Style (Pure) Android Development] GabryBSK:
Hi all! I've been out of the loop on custom roms for months. Can someone describe me the situation about LineageOS for our device? I've read some old posts, but i haven't understand very well: too many different versions, which has confused me :p

I'm currently on an old version of AICP rom (december) and I want to flash a fully functional stable version of LOS. Can someone explain me step-by-step what to do?

Thanks (and sorry for the noob question) :D