yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] kb8no:
Batteries can be flakey on this phone. I've experienced sudden low battery percent like you are seeing and it is commonly reported. I did lots of googling and reading other threads in the past about this. What I read from more than one source is that the battery charge reporting circuit is in the battery unit itself and what you see is end of life behavior from the battery. These batteries tend to fail abruptly and not gradually. This seemed very plausible to me and a new battery has always fixed it. Fortunately they are readily available and inexpensive on Ebay. I have several of these and messing with and cannibalizing them for years so I have gotten very good at the nuances of replacing batteries. Myself, I believe that this is the price you pay for the amazing rapid charging of this phone. It is not the ROM or software.

Just wait for your battery to come. Replacement batteries are flat and are made to be bent. Remember to tweak the edges of the battery a bit with your fingers so they curve down and match the curve of the phone back like the original battery. It is not necessary to use double sided tape and i just lay them in there.

Another common battery issue is that some batteries will loose their charge if they sit for a week. You will not notice it if you keep it charged every day.
[X Style (Pure) Android Development] xda_maddogdean:
Thanks [MENTION=4465682]kb8no[/MENTION], battery should be in tomorrow or Monday. I agree, for $10USD it's not like we can complain :)

Cheers
[X Style (Pure) Android Development] kb8no:
Reflash the ROM and gapps nano using full clean wipe. Get the ROM booted. Then sideload Magisk manager and use that to download the zip and flash it. See if that helps. You sure you have a previous good Nougat?
[X Style (Pure) Android Development] tj90241:
Open the dialer app, and dial (do not enter in the text input!) this: *#*#4636#*#*

Then, press "phone information" and you get a ton of hidden options.

Note: you can't simple "enable" VoLTE. It requires a lot of integration with the ROM/telcos - there's special daemons that have to be built/configured into the ROM and other things. I would guess that VoLTE is not functional in this ROM - and it's likely something that can't be enabled without more cooperation from the telcos.
[X Style (Pure) Android Development] Rockford the Roe:
Hello, I am currently planning on porting Lineage 17.1 to this device but OP's kernel GitHub page says that it's on the 16 branch. OP's device config GitHub also has an option for 17.1. Should I use that kernel or just wait for the 17.1 branch to get backported? Thanks
[X Style (Pure) Android Development] Rockford the Roe:
I found out that even if I used that kernel, I couldn't even build it and someone on the GitHub repo reported the same issue. [MENTION=1776875]randomblame[/MENTION], can you post the kernel sources from your most recent build?

EDIT: I have tried to build Pie for myself but the device gets in a bootloop, can OP provide any build instructions?
[X Style (Pure) Android Development] Industrial_chickens:
sounds daft, but this works :)
[X Style (Pure) Android Development] kb8no:
I have run into the barcode scanner problem. Some work fine and some are broke. The pinhole makes sense because it won't focus.

Indeed, this may be a more generalized problem. I have found that sometimes the camera loses ability to focus close. I have found that if you back off some distance it suddenly finds out where it is, refocuses, and then you can move in close with a retaining the focus.

I wonder if you back way off the barcode and let it find itself, and then move in on it, if it might then retain its focus and work. I'm going to try that the next time I have a barcode problem to see if that also might be a solution.
[X Style (Pure) Android Development] Industrial_chickens:
Yeah, i tried moving about but couldnt get it to work. I ended up just using my fingers the second time round and managed to get the same result. Saves wasting paper :)
[X Style (Pure) Android Development] kb8no:
I'm having trouble with my phones holding an LTE signal and dropping down to 3G. It's relatively new phenomenon and happening on several phones. Anybody else noticing this?
[X Style (Pure) Android Development] kb8no:
While trying to understand the loss of LTE I think I fixed the delayed boot with the error "Process system isn't responding". I couldn't figure out why some were not reporting it. 1/13/20 build not only needs a clean flash to get Netflix working. I flashed back to Nougat Stock first. Then flashed 1/13 build and delayed boot disappeared.

I can't hold LTE on Verizon SIM only. ATT works fine.
[X Style (Pure) Android Development] R77:
I did a clean wipe and flashed the ROM it booted up just fine. I then charged it since it had low battery then I flashed the new version of magisk 20.3 it booted on the Moto white screen. It turned off and it just became a boot loop. I have the nougat firmware that I flashed a coupe of years ago. The twrp version 3.1.1-0?

In order to fix this do I need to reflash the nougat firmware again?
[X Style (Pure) Android Development] kb8no:
We are using twrp 3.3.1-0. I doubt that is the problem but update it. Is this your first LOS since stock Nougat? Try to flash LOS again with complete wipe. Use OpenGapps nano. If it boots, load Magisk app and let the app install the zip. Let us know.
[X Style (Pure) Android Development] R77:
I have downloaded and flashed the ROM before would do a clean wipe flash opengapps nano, but always had bootloops. If I relfash nougat firmware again would that fix the problem the bootloops?
[X Style (Pure) Android Development] kb8no:
Yes. I think so too. Try it. You are flashing Randomblame 1/13/20 build, correct?
[X Style (Pure) Android Development] R77:
I'm trying to flash 1/13/20 build is this the most current version of the nougat firmware https://xdaforums.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142

at the end there's a google drive link that contains a zip file CLARK_RETUS_7.0_NPHS25.200-23-1_cid9_subsidy-DEFAULT_CFC.xml.zip. The person says that worked for him since the original link gave him a bootloop with no OS. Is that also nougat firmware?
[X Style (Pure) Android Development] kb8no:
This is the correct forum. Go to the Androidfilehost download link on the OP. It's right there and it works. Flashing this stock Nougat is complicated. Have you done it before?
[X Style (Pure) Android Development] R77:
Yeah once, but you know just wanted to make sure
[X Style (Pure) Android Development] kb8no:
Don't forget to see the modem flashes. Sometimes need to reflash.
[X Style (Pure) Android Development] kb8no:
I use 22 all the time and no bootloop. I doubt the link is borked. 22 was thought to be the last Nougat when they captured it and started this other forum. Then Verizon released 23 through an OTA but it was not available. At the time none of the other cellular providers released 23. I took the OTA on Verizon on one of my phones but everyone including myself could not see one bit of difference. Now I see someone captured 23. I still use 22 when I flash stock. I don't think it makes any difference which one you use. They are both Nougat and have the same firmware. It's the firmware you need as a base and is the whole reason for flashing back to Nougat stock. Now that 23 is available you could use it but it doesn't matter. Read back in that forum and see if you can figure out how they got 23 and why anyone cares. You can still take 23 update from 22 through OTA. I haven't looked at that forum for a very long time but it is how I learned to flash stock and got the Nougat stock back on my phone so it was a very important key forum back in the day.
[X Style (Pure) Android Development] zohar_ml:
I found the time to update my son phone, but I still have echo problem while taking a call with the speaker on.

When using the speaker in a phone call, the other side would hear himself twice (and it’s supper annoying to be on that other side).

I did a supper clean install and even fastbooted the original Nougat rom.

While using both V22 and V23 original roms I have no echo problem. In both these roms the baseband is m8992_125531.29.01.88.09R.

After changing to the latest 20200113 lineage (and preforming a full wipe before) I get the echo problem again.

Also found out that In the original roms, while with speaker only to lower speaker works. but in lineage both speakers work.

I wish to have a Pie rom on this phone, but this echo problem is annoying.

Is there any idea on what I could do to fix this problem?
[X Style (Pure) Android Development] kay3y3:
someone noticed diffrences in speed or batter life beetwen android 7 and this os?
[X Style (Pure) Android Development] Ferchurito:
I get error 7 when flashing it. My phone is a xt1575
[X Style (Pure) Android Development] Strephon Alkhalikoi:
Insufficient details. Is your bootloader unlocked? Do you have TWRP installed? Is the Android 7 baseband installed?

Error 7 is a general error and could mean anything. Thus the questions.
[X Style (Pure) Android Development] Ferchurito:
Well, I obviously have the boot loader unlocked and also have twrp. I came from the stock nougat rom so I believe I have the android 7 baseband? I honestly don’t know and have no idea how to know that.
[X Style (Pure) Android Development] Strephon Alkhalikoi:
It wasn't obvious at all or else I wouldn't have asked. That said, I believe you are on the right baseband.

Download the ROM again as your copy may be corrupt.
[X Style (Pure) Android Development] Ferchurito:
Well, later this day I will download the ROM again and update to the latest TWRP and flash it. I attached an image of my baseband version which I believe is the correct one to flash this ROM. Thanks for your help
[X Style (Pure) Android Development] Tails83:
Mirrors don't seem to be working anymore to download most recent build, anyone know of another place to get this (20200113)?
[X Style (Pure) Android Development] kb8no:
Androidfilehost link on OP from Randomblame works fine and downloads for me.
[X Style (Pure) Android Development] benc2010:
CM16 for Moto X Pure: Open Gapps package with working camera

Hi,

I just found out that the Full version of OpenGapp also do not overwrite the stock camera. So one more choose for Gapp packages.

Great rom, I just resurrent my Moto X pure.

Many thx.

Bench
[X Style (Pure) Android Development] kb8no:
Thanks for the info. There is now a highly functional LOS 17.1 you should be using where we are hanging out. Check it out. Be advised that there issues with TWRP and Android 10 that have not been worked out yet and only works when coming from stock Nougat so he is using a custom LOS recovery for now. If you use his recovery I think you can dirty flash it right over this LOS 16.0.

https://r.tapatalk.com/shareLink/to...7&share_fid=3793&share_type=t&link_source=app
[X Style (Pure) Android Development] pereric:
First, thanks for building Lineage-16.0 for clark!

Two questions: I installed the original version of the ROM in this thread, which worked fine for quite a while. However, I got some strange problems recently - mostly the software navigation buttons only working sporadically (and it's probably not hardware - they work fine in TWRP). Tried solving by flashing the current build with adb sideload; however gets error "mkdir "/cache/recovery/<long hex string>" failed: no such file or directory".

1. any solutions to the problem above - is /cache/recovery somewhat missing? I have re-flashed the latest TWRP (3.4) with fastboot.

2. should I try reinstalling stock nougat? If so, what are the most reputable sources?

System information:

Boot loader: A0.52

Baseband M8992_1255331.29.01.88.09R CLARK_EMEA_CUST

Product: XT1572 32G P3C

best regards

Per Eric (still new to android hacking, mostly used to regular GNU/Linux)
[X Style (Pure) Android Development] randomblame:
Camera is being difficult haven't had time to diagnose it further. Solved the blob incompatibility, tried switching the kernel driver, patched the new driver to ignore the failure to read the sensors eeprom which should only contain calibration data and should be mostly unnecessary but haven't had time to diagnose the next level of breakage.
[X Style (Pure) Android Development] :
Donut...even better days. I think the first time I rooted and rom'd was on Eclair. I've always been a fan of you guys, devs. I really appreciate you giving some much needed attention to this amazing phone. I looked through the OP but didnt see a donate button.
[X Style (Pure) Android Development] randomblame:
That links in my signature. If I can't get camera going with these blobs I may go nuclear and move to freedreno and open source blob free methods I'm tempted to start working on a modern kernel and ditch the qcom blobs entirely but the problem is by the time it was all finished the device would be even more obsolete than it is already. Even tegra socs are less of a pain than Qualcomm, Nvidia doesn't deserve Torvalds middle finger nearly as much as they do imo
[X Style (Pure) Android Development] :
I dont see a signature to be honest. Maybe cause I'm on mobile? I dont have a PC. I see other devs signature.
[X Style (Pure) Android Development] randomblame:
Https://paypal.me/kelsiraed

I think the next step is going to be kernel work, freeing the camera from the blobs in the existing 3.10 kernel or pushing ahead with something newer like I started on 3.18
[X Style (Pure) Android Development] frank0312:
are you still looking for a solution for the other camera?
[X Style (Pure) Android Development] randomblame:
Big shout out to [MENTION=8994059]cafelattegames[/MENTION] for sending me their old style it's going to save me a lot of time
[X Style (Pure) Android Development] randomblame:
Working on 3.18 yesterday I got spmi compiling and the LCD backlight driver, worked in msm clk driver, tonight I'll fight the msm platform drivers that are causing a panic

Depending on how obnoxious it is to adapt the new msm stuff I may opt to startover with Google's 4.14 common kernel. If I have to rework everything in 3.18 anyways I might as well go for the newer base
[X Style (Pure) Android Development] joheli:
New kernel sounds great... Is it possible to add Vulkan-support than? ( Because Moto never did, but the processor supports it...)
[X Style (Pure) Android Development] randomblame:
Going through the the SOC drivers trying to bring up all 6 cores all the msm8992 support was dropped from this kernel so it's one piece at a time
[X Style (Pure) Android Development] randomblame:
Maybe -it depends on how much of the newer code I can adapt. I haven't even started going through the gpu specific stuff yet but hopefully the adreno 418 support is still extant
[X Style (Pure) Android Development] randomblame:
https://pastebin.com/ey6hU92f

Some progress all 6 cpus are online now
[X Style (Pure) Android Development] joheli:
I've been using the trainwreck-2 ROM as my daily-driver now and have noticed some more bugs

-Sometimes the battery stops charging at round about 84%(but that could be a hardware issue)

-Homebutton (I guess the quickstepp-launcher) stops working

-(more of a question) is it normal for the ROM using 26Gb of storage?
[X Style (Pure) Android Development] randomblame:
26gb? I have a 16gb pure here so that seems unlikely. I haven't seen the other problems either mine charges over night and the touchscreen is garbage so maybe I just don't notice the home button going out
[X Style (Pure) Android Development] randomblame:
3.18 getting further now loading rootfs starting schedulers initializing bluetooth before the panic on mdss_mdp https://pastebin.com/A23TdGfW

Tracked most of my problems back to a messy clk driver change I made that's next
[X Style (Pure) Android Development] :
Supposing you get a fully functional Pie rom going, what are the chances you could complete a fully functioning Oreo rom? I tried Pie for a few days on my Nexus 6 and I cant say I like it.
[X Style (Pure) Android Development] randomblame:
You can disable gestures I assume that's what you dislike
[X Style (Pure) Android Development] :
No its not what I dislike, Oreo roms usually have fling and I use it. Its just a step backwards, you have to press buttons twice where you had to only press once in Oreo, like in youtube to make replies. And its design just reminds me of my old lg g2 with the flat circle quick settings. No problem though.
[X Style (Pure) Android Development] kadopt:
I'm using the available build, it's working fine, battery usage is kinda high and I've changed the CPU governors from performance to on demand/interactive.

I've had to rename the NFC APK to end the "logcat" errors related to it.

Audio seems fine.

I know that you are trying to make a new kernel functional but could you try to fix the Bluetooth issue?

Also if you have new builds feel free to share.

Thanks!

[edit]the file system issue I've reported before remains[/edit]

[edit2]some settings also crash when accessed but I can make a report on that if necessary[/edit2]
[X Style (Pure) Android Development] randomblame:
Yes I'll get back to fixing up the rom i spent the whole weekend working on this kernel
[X Style (Pure) Android Development] Part.time.fixit.droid:
Is the camera working on your ROM. I've used LOS 15 and GoundZero 8.1. I love both except I can't deal with the cameras not working. And I can't use any Nougat custom ROMs now that I have upgraded. Hoping to find another option to use.
[X Style (Pure) Android Development] kadopt:
Cameras are broken as it says in the OP.
[X Style (Pure) Android Development] :
Obselete1 (Collection of my random roms, its just a couple threads down from this thread) has several Nougat roms that work on Nougat modem. I personally like Aex. If you try it out, I got the best battery life from the March update.
[X Style (Pure) Android Development] DjDill:
As the back camera never worked in 8.1 it's unlikely it will ever work in 9? please correct me if I am mistaken
[X Style (Pure) Android Development] kadopt:
Just because the previous dev could not find a way to make it work does not mean the current one can't do it...
[X Style (Pure) Android Development] randomblame:
Trying to shoehorn the msm 3.18 camera kernel stuff into 3.10 currently. The msm code is like a cancer in the kernel it spreads deep and stretches little tendrils into every major organ so many dependencies everywhere for every little thing. I've got the gpio and pinctrl differences between 3.10 and 3.18 mostly isolated and that's where my work on the 3.18 kernel is focusing. Backporting stuff to 3.10 may just result in blob incompatibility but I'm trying anyhow
[X Style (Pure) Android Development] randomblame:
Looks like 4.10+ now has a pinctrl driver for msm8994/2 built in which is handy I won't have to rewrite the old driver after all I'll just transplant the new one

Another thing I need to do is pull in the last couple years worth of fixes to 3.18 my base is at 3.18.71 and gkh has been updating it, it's at 3.18.126 currently
[X Style (Pure) Android Development] vityas_off:
Want to try this, but download link in the OP-post is broken.
[X Style (Pure) Android Development] randomblame:
New build up now, op updated - same functionality but pulled down new stuff from lineageos
[X Style (Pure) Android Development] joheli:
Now up and running on TrainwreckV3, however there seemes to be a problem with the rotation sensor not working properly.

It does not show any action even after a reboot (I tried rebooting on the last version to fix it). But numerous other bugs are gone, so great job and keep on coding ;)

Edit 1: I looked up the sensor-readouts in "sensor-mulittool" and while being detected, they aren't showing any values (as expected)

Edit 1.5 Now it's working...

Edit 2: The proximity-sensor for turning the srceen of during calls is not working
[X Style (Pure) Android Development] kadopt:
Let your device go to sleep unplugged for a few minutes after booting up. The sensors will be working then, it's a known bug.
[X Style (Pure) Android Development] frankystar3:
Sim not working

Sim not working for xt1572, looks like baseband version in the photo you've added, Its similar to the one i uploaded just see if I missed out something. Thank you
[X Style (Pure) Android Development] randomblame:
Are you using Nougat or mm bootloader/modem? This is compatible with nougat firmware only.

*edit I just tested on an xt1572 and it is working properly. The only reason the ril wouldn't be working is if the modem firmware is incompatible.
[X Style (Pure) Android Development] Pantherrra:
I'm currently on LineageOS 15.1, flashed with TWRP on my xt1572 (coming directly from stock). I'm new to all of this so forgive me for asking, how does one update the modem firmware? I'm looking forward to test this ROM as well. Sorry if I'm asking the obvious, I just can't seem to find it :/

@OP: from what I read, this ROM looks promising! thank you for all the hard work!
[X Style (Pure) Android Development] randomblame:
there is a guide here to flash the stock nougat firmware including modem - https://xdaforums.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235 make sure you flash the modem twice as instructed. This may be irreversible which means only nougat compatible roms will work in the future
[X Style (Pure) Android Development] vityas_off:
Installed this successfully. Everything went smooth, but during calls volume of speaker is extremely hight even at minimum, everyone can hear my conversations :). Is this a known problem?
[X Style (Pure) Android Development] kadopt:
Never noticed that, although the idea now is to move to 3.18 kernel, fix major problems then fine tune the device (I think).
[X Style (Pure) Android Development] frankystar3:
I updated to 7.0 before i started using custom rom, i have the backup of 7.0 stock firmware backup using twrp. I'm currently using broken os 6.0 but I'm not sure before I Start using broken os I downgraded to 6.0 stock firmware, if I just restore the 7.0 backup firmware will it work(baseband/modem will change or no)?
[X Style (Pure) Android Development] randomblame:
Yeah the kernel has stolen my attention at the moment getting further though it boots, sets up the cpus and memory unpacks the ramdisk starts to set up bluetooth talks to the modem and panics due to a memory mapping issue. Most likely culprit is msm bam dma
[X Style (Pure) Android Development] kadopt:
A backup will not flash the bootloader or the modems, you have to flash a complete stock 7.0 motorola rom.
[X Style (Pure) Android Development] Fabiett83:
if it can be useful I have downloaded the 7.0 stock rom I'm using right now from here:

https://yadi.sk/d/MCliEyCPfj7ZZ/MOTO.X3/Style/XT1572/EU

i were on LOS and returned to stock using this file: CLARK_RETEU_7.0_NPHS25.200-15-8_cid7_subsidy-DEFAULT_CFC.xml.zip

obviously this is for the EU XT1572 model, if you need the American version can be downloaded from here, but i have not tested any of them:

https://yadi.sk/d/MCliEyCPfj7ZZ/MOTO.X3/Style/XT1575/US
[X Style (Pure) Android Development] frankystar3:
Ok, now I understood. So, what I need to do is to flash the full stock firmware... I have the 7.0 full firmware link that I downloaded from here:- https://firmware.center/.zdrive/z_gdrive_viewer.php?ID=0Bw_NsGJYGFyVd3luRHVKTG5iWGs After I flash this firmware the imei number its blank baseband blank... And I'll add a screenshot of fastboot command which I flashed this firmware OK.

Thank you so much regard Frankystar :good:
[X Style (Pure) Android Development] kadopt:
I assume you flashed a rom specific for your device model and region right? Like if you have an european Moto X Style you should flash xt1572 RETEU 7.0 rom.