yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] pcaseiro:
Video calls are working great with a headset using the 3.5mm jack.

That means the audio issue during video calls only is a lineage bug. You were right Paulenski ?

Can someone else confirm this?
[X Style (Pure) Android Development] mp44christos:
While on hands free I have had this problem from the beginning I started using los. I thought I phone was broken!
[X Style (Pure) Android Development] pcaseiro:
Android 7 is coming out to this phone so once it comes out devs might want to get its firmware and place it on lineage. I believe that will take care of this issue.

*** Comment retracted ***
[X Style (Pure) Android Development] annoyingduck:
I flashed the 8/21 build clean over the weekend and just updated to 8/28 this morning. Everything has be perfect except for one thing. Just now was the first time I tried using navigation and what is happening is very strange. While using Waze the location keeps going in and out - and after a few min it just says that it cannot get a gps fix (I have a clear line of site, it's not a data or lack of sky issue). Google maps seems to work, but Google maps uses a combination of GPS and network location, so it's not the app to test gps performance with. This was driving me nuts in Waze, so I opened up GPS Test Plus and what that was showing was even weirder. Basically my heading would constantly change from north to south every second or so along with the actual connected satellites randomly changing every second. This would explain the issues in Waze.

Can someone test their phone using Waze while driving on the highway (you cannot test it without driving, as staying in a fixed location will show a positive result). I restored my backup of stock 6.0 while driving and GPS/Waze/GPS Test Plus all worked as expected so it's definitely something in the build. I did not test GPS on the 8/21 build, only the current 8/28 build. Is anyone showing the same thing? Do older builds have proper GPS function? Any feedback would be helpful, as this to me is a pretty significant bug.

Edit: Is this patch "use system clock" a possible culprit? https://review.lineageos.org/#/c/185237/
[X Style (Pure) Android Development] TalionDread:
Same for me on another lineage based rom. Not sure when it started exactly but it doesn't do it on a build I had from the 21st. Started for me on a build from the 27th. Very annoying.
[X Style (Pure) Android Development] jason2678:
link
[X Style (Pure) Android Development] annoyingduck:
It's been a few months since I ran Lineage on this device and there were not GPS issues before. So good to know that a current build on another LOS based rom is doing it to. I'd like users to look into this to track down what is causing it. The latest build was running just beautifully. One big thing that always kept me from custom os's on this device was signal strength. I must say the latest Lineage has had some improvements because the signal strength was great on the 28th build. Unfortunately the GPS issue was too big for me to remain on Lineage so I returned to stock. At this time I cannot provide logs, but hopefully some of you guys can help track this down.
[X Style (Pure) Android Development] pcaseiro:
I'm sorry if my comment made you uncomfortable. In no way I'm trashing devs. I actually do appreciate a lot their work and without them we wouldn't have CM or now lineage.

You sir I believe over reacted to my comment.

I will however retract my comment about devs won't be spending time with this issue. I do apologise for only this comment.
[X Style (Pure) Android Development] TalionDread:
Here is a logcat from what I could capture. I can never make much sense of these lol. Maybe this will help someone else.
[X Style (Pure) Android Development] bamaredwingsfan:
So I did a complete wipe and fresh install of the latest version of Lineage last night. And everything seems to be working fine. I have one problem that I can't seem to figure out. When I put the phone down, the phone screen will not go into sleep mode. I don't really have an idea what might be causing it. I have disabled everything that I can think of that pertains to the screen. I am wondering if there are any known apps that conflict with rom and cause this. Any suggestions is appreciated
[X Style (Pure) Android Development] Doktaphex:
Having had a look at your log, it seems quite clear that there is a problem with GPS.

From some very quick digging online, it would appear that the GnssLocationProvider (which, correct me if I'm wrong, first became available to developers in the 'N' release) is constantly throwing errors. Whether this is down to the implementation within LineageOS of the GPS radio "drivers" I do not know, but I would hazard a guess that it is, considering the fact that the developers have been having to implement many creative solutions in order to use the previous 'M' proprietary blobs.

My assumption is that this issue will disappear once the guys are able to finish reversing all of their previous solutions for the 'M' blobs, and fully implement the 'N' blobs now that they are available.

Of this I am certain though, they will definitely have to find new and interesting solutions in order to implement the 'N' blobs, as there is absolutely no way that Lenovo managed to release non-buggy, clean proprietary code ;)

In conclusion... Wait patiently and be thankful that we still have devs working for us all :angel:
[X Style (Pure) Android Development] TalionDread:
Thanks for the post. Makes sense. I'm ALWAYS appreciative of the devs work. If I expected no bugs I would stay stock lol. Fwiw, I have been compiling XenonHD ROM for Clark which is lineage based and shared the Waze issue. I compiled today and clean installed and the Waze issue seems fixed. Maybe the lineage source was corrected, or blobs. Either way, it is working again :good:.
[X Style (Pure) Android Development] mtalbert63:
First time on a MotoX Pure. Gave my wife my Oneplus 3t bc she was having fits with this aging X Pure. Threw RRon it and it has really brought it to life. I only have one problem that I can find. My Fitbit is having a terrible time connecting to Bluetooth...know problem or am I missing a fix for Bluetooth issues. Thanks Dev and everyone that has contributed. You have saved me $400 for the time being at least!
[X Style (Pure) Android Development] dzidexx:
Last build(and others?) has gps issues - can't get stable connection with any positioning system.

Easy check - waze app - drive.

I think - All others custom roms with LOS sources have it.

My moto e2(RRemix July 2017) hasn't bug. [MENTION=2385005]invisiblek[/MENTION]

Restored from backup RRemix(13.08) also hasn't this bug.
[X Style (Pure) Android Development] annoyingduck:
Have you tried today's build (9/4) or are you on the 28th build? There is a gps commit in todays which is available now. I'm curious myself if it has been fixed, it's the only thing that made me go back to stock.
[X Style (Pure) Android Development] dzidexx:
No,

I flashed LOS only to check where the bug is from.
[X Style (Pure) Android Development] annoyingduck:
I had faith that the GPS commit in today's build was the issue (certainly made sense given it was using boot time vs real time) so I dove in. GPS is working perfectly on today's 9/4 build. No issues with Waze or other GPS apps.
[X Style (Pure) Android Development] JTaylor69:
Using last week's build, it was clear that GPS was having issues as it was zooming in and out.

This week's build is working fine when using Waze and Android Auto. No problems driving back from work tonight.

Great work team.
[X Style (Pure) Android Development] kaaskop:
Same here with the 09.04 update.

(stock kernel, magisk, T-mobile US)
[X Style (Pure) Android Development] jason2678:
Dirty flash?
[X Style (Pure) Android Development] kaaskop:
Yes dirty flash
[X Style (Pure) Android Development] Paulenski:
I managed to update to 8/21 and 8/28, I think something from magisk breaks it. Uninstall magisk, wipe system partition, then install update, and gapps. Do backup before all this, but it's definitely something on the system partition that breaks after all of my attempts.
[X Style (Pure) Android Development] jason2678:
I think it is Magisk, just like Paulenski said.

The same thing has been reported in the AICP thread.
[X Style (Pure) Android Development] kaaskop:
It is Magisk causing problems

This is what I did

1. In TWRP flash Magisk uninstaller zip

2. Reboot

3. Update with the updater

4. In TWRP install Magisk and reboot

All ok!

Thanks for all advice.
[X Style (Pure) Android Development] Thomas_BA:
Hi folks,

after running quiet a time the Stock-ROM i decided to flash this ROM. Everything perfect, but for some reason the telephon app does not show some names of the incoming calls even they are in the address book.

More específic.

I have all numbers in international code. (I'm in Argentine +54).For example:

+54 9 11 1234-5678

But if somebody is calling me from inside Argentina appears

+54 11 1234-5678

So, because the 9 is missing (which is the international code for cell phones, not needed when you call from Argentina) , the number in the Adress book isn't recognized. On the stock Rom (Marshmallow 6.x) this was no problem.

Using a third party dialer like ExDialer, and everything is ok.
[X Style (Pure) Android Development] Sir2taj:
Hi there , could anybody confirm me whether the rom has got multiple sim toggle (the option to toggle any one single of the two sim or both the sim at a time) ?
[X Style (Pure) Android Development] Bwangster12:
Still no update on the speakerphone mic not working? I've noticed on most of the recent updates that the person can barely hear me when I put the call on speakerphone.
[X Style (Pure) Android Development] TheYoz:
Not much in the change log for the 9/11 release. Hopefully this means the development is going toward LOS 15!
[X Style (Pure) Android Development] cyanbaig:
Front flash and Volte support

I think that front flash was working in the few early builds,

But in the latest build the front flash is not working for my Moto X style

And also I wanted to ask about the volte support mine is not working for XT1572

Any suggestions for the front flash??

By the way I'm new on the XDA...

Help appreciated...
[X Style (Pure) Android Development] csrow:
What might be causing no detection of SIM?

I have tried could of different versions but none of them recognize the SIM card.

This is on a fresh clean install.
[X Style (Pure) Android Development] TheYoz:
This happened to me as well when I flashed the test build a few pages back. There were instructions on how to fix it but what I ended up doing before reading about the fix was flashing stock back to the phone using fastboot. This also happens to me when I dirty flash the weekly which i believe is due to Magisk (correct me if I'm wrong.).
[X Style (Pure) Android Development] csrow:
I've read from page 74 when the test build was introduced but I didn't see any instruction on fixing SIM problem. Could you locate the post for me?

I do not have Magisk. Using supersu.

TIA.
[X Style (Pure) Android Development] JohnMcW:
If you are using an old version of GApps, that is most likely your problem.

see https://xdaforums.com/showpost.php?p=73301236&postcount=6850
[X Style (Pure) Android Development] MacFett:
Did you have any radio problems with 11 Sept? I just did a clean flash (os and gapps only) and I can not connect to cell data, only wifi. Everything is enabled as usual, just no cell data.
[X Style (Pure) Android Development] csrow:
I'm install the rom with the latest OpenGapps nano. Should I try a different Gapps? Which one would you recommend?
[X Style (Pure) Android Development] JohnMcW:
OpenGapps should be fine, that is what I use. If you are using the latest then, that probably isn't the issue with your phone...

Have you tried un-installing the SU mod, re-installing the rom without superUser and let it boot up---if it boots up with recognizing your sim,

then it is SuperUser.

If it does, then you might be able to install SuperUser afterward and still have your sim recognized.
[X Style (Pure) Android Development] MacFett:
A few reboots and the cell radio was working again.
[X Style (Pure) Android Development] csrow:
I've already tried without supersu and still will not recognize the SIM card. Weird.

Don't know what else to try.
[X Style (Pure) Android Development] TheYoz:
There is a new 9/18 build.

Flash that, with newest GAPPS and maybe try the latest MAGISK instead?

Before flashing be sure to erase everything minus SD card in the "advanced" option in TWRP, reboot into TWRP - Transfer files to flash back to phone - Flash ROM -> GAPPS -> Magisk.
[X Style (Pure) Android Development] csrow:
I've wiped all including internal storage and then pushed zips.

When installing LOS, I am getting an error on modem toward the end of the script

detected filesystem ext4 for /dev/block/bootdevice/by-name/modem
mount: failed to mount /dev/block/bootdevice/by-name/modem at /firmware: Device or resource busy
Extracting modem firmware
Firemware extracted
script succeeded: result was [1.000000]

I guess this is what causing the problem with SIM.

Any help would be appreciated.
[X Style (Pure) Android Development] TheYoz:
Ooof.... Honestly, if I were you I would totally flash back to stock then back to a custom ROM.

I'm pretty sure there are STOCK 6.0.1 files in the Dev forums that you can download. Flash the one with the MAY security update then have it update to September so you get the modems with the best functionality since the December update kinda kills the Bluetooth. Once you have the September update, boot into the bootloader --- Fastboot flash the latest TWRP --- Flash the latest LOS, GAPPS, MAGISK and you should be good to go. I'm pretty sure in your case, root is messing with your radio. This is all assuming you know how to fastboot flash back to STOCK, If not I can link ya.

I had your issue in 3 cases:

1.) Coming from a N DirtyUnicorns ROM

2.) Dirty flashing new version

3.) Testing the "test" build with the N kernel a bunch of pages back.

I do exactly what I posted above and it fixes it.

Another note - when you get to the point where it's time to flash the custom ROM again, make sure you do the advanced erase like I said a few posts up then reboot into recovery. I create a folder on my PC called "Flash" and put the ROM, GAPPS and MAGISK files into. The only folder at this point that is available on the phone is "TWRP". Copy and paste the "Flash" folder into the root of the device so you should now see "TWRP" and "Flash". Once everything is flashed and you are booted into the ROM I delete the "Flash" folder off the phone. Hope this helps!
[X Style (Pure) Android Development] fdc77:
make a double flash of the rom, at the second flash everything goes fine, this is an issue present in various rom (lianeageos based and aosp)
[X Style (Pure) Android Development] csrow:
Double flashing cured the error message but still no SIM. Thanks for the suggestion.
[X Style (Pure) Android Development] TheYoz:
Do what I said above and your issue will be fixed. Then careful flashing going forward.
[X Style (Pure) Android Development] xabr3:
You need to get back to stock 6.0.1.

Then, do not take the 7.0 update. Otherwise, you can flash again to stock 6.0.1.

I was having the same problem. Came from stock 7.0 and could not install LOS14.1, it is a modem problem. LOS14.1 is still not updated with 7.0 blobs/modem so you need to get back to stock 6.0.1. before installingen the current LOS14.1.
[X Style (Pure) Android Development] csrow:
Okay. Will take the long road and report back if that fixes the problem.

Now I need to find a stock in zip format.
[X Style (Pure) Android Development] TheYoz:
This can't be done in TWRP. Has to be done with fastboot. The partition flash may fail but you can "disregard" the failure on that. If anything else fails, make sure you fastboot flash it again right after the failure and it will succeed. I find this happens on the modem files.

If you are on Moto X Style: (make sure you grab the right one for your region)

https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/

If you are on Moto X Pure: (18-8 is the Sept Sec Patch)

https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/
[X Style (Pure) Android Development] csrow:
Okay I'll start with 18-8 and make sure the SIM is recognized and then try installing LOS once more.

Thanks for your guidance.
[X Style (Pure) Android Development] Greymon:
If I were to flash this over my previous ROM, would I be able to restore my apps afterward with the adb backup I made beforehand?
[X Style (Pure) Android Development] ashoka.inder.dev:
This update issue (in attached image) was fixed in few build back is now again popping up. Basically the update should never offer build older than the one installed. And wondering why it is offering me to download the already installed build :confused:
[X Style (Pure) Android Development] ashoka.inder.dev:
Is there any development in lineage community going somewhere with the X Pure android 7 kernel that was released sometimes back? Curiously waiting for the lineage kernel to get updated to latest version.
[X Style (Pure) Android Development] xabr3:
No one knows. Might take a while. Few months.
[X Style (Pure) Android Development] acr2d:
I am stuck in the Lineage logo.

- Unlocked Bootloader, rooted and twrp (3.1.1-0) installed.

- Wiped dalvik/ system/ data/ cache

- Installed lineage-14.1-20170918-nightly-clark-signed.zip and gaaps micro

- Wiped dalvik and rebooted

after this got stuck

i dont get what i am doing wrong.
[X Style (Pure) Android Development] Louis1977:
look that bro https://github.com/invisiblek/android_kernel_motorola_msm8992/tree/lineage-15.0

Enviado desde mi XT1575 mediante Tapatalk
[X Style (Pure) Android Development] xMDKx:
I had this problem when installing LOS 14.1 after officially upgrading to Nougat. It seems the correctly way to fix it is to first downgrade to official Marshmallow and after that installing LOS 14.1 (but right now I'm still with LOS 13.0).
[X Style (Pure) Android Development] Sir2taj:
I flashed modem , modem 1 & modem 2 ( only ) via command prompt from the appropriate marshmallow package
[X Style (Pure) Android Development] Bob n Ohio:
Like this rom a lot except I miss Moto display.

Third party imitations aren't any good & ambient display isn't much better.

If anyone knows how to get Moto display lemme know.

Also...since we prolly can't get Moto display does anyone know how to control pattern & or color of light for notifications on top middle bezel?
[X Style (Pure) Android Development] acr2d:
Can you point to instructions how to do it?
[X Style (Pure) Android Development] csrow:
Success.

Went back to 18-8 and then flashed 9/18 LOS. Now I have SIM.

Thank you for your help.
[X Style (Pure) Android Development] t895:
HashBang173 already implemented the blobs in some unofficial builds that are working very well for me. The only problem is if you flash the system image and you want to go back to some other ROM, TWRP will crash is you try to wipe anything. Then you have to flash stock MM and erase userdata to get TWRP functional again.

Your call.

Here's that latest available on his androidfilehost page:

https://www.androidfilehost.com/?fid=673368273298979379

Edit: After a bit of testing, I also noticed a problem where music cuts out when the screen is off. It makes the rom really frustrating to use since I listen to music a lot.

I also just figured out that you only have to erase userdata from the bootloader to flash anything new
[X Style (Pure) Android Development] axman916:
flashed with the latest one (09/18) but flashlight doesn't work. It did suddenly turn on torch by unknown reason then I couldn't find any way from setting to turn it off. Finally It was rebooted for off-torch.
[X Style (Pure) Android Development] TheYoz:
Glad to hear! [MENTION=699288]csrow[/MENTION]
[X Style (Pure) Android Development] ashoka.inder.dev:
Swipe from top, select edit tile (pencil type icon) and when you are edit tile screen just hit return without making any changes. The tourch icon on the top panel will now start working as expected.

*Repeat this procedure on every reboot once*

Thats the only way I'm aware that is 100% successful. The other option is chop chop type feature that sometimes work and sometimes don't.
[X Style (Pure) Android Development] ashoka.inder.dev:
Update page of the latest build. (Screenshot Attached)

Looks like the 11th September built has become Agent Smith or facing Ecistential crisis back at home ?
[X Style (Pure) Android Development] Bwangster12:
It's not an issue on Dirty Unicorns.
[X Style (Pure) Android Development] jweaks:
https://download.lineageos.org/clark = Internal Server Error
[X Style (Pure) Android Development] jweaks:
Flashed the latest and lost root. Can't seem to get it back.
[X Style (Pure) Android Development] ashoka.inder.dev:
Flash this file:

https://mirrorbits.lineageos.org/su/addonsu-14.1-arm64-signed.zip
[X Style (Pure) Android Development] thyagomn:
Hi guys, I flashed this rom, but I'm stuck on boot.

During the flash, everything appears normal, only one message seems odd:

mount: failed to mount /dev/block/bootdevice/by-name/modem at /firmware: Device or resource busy

This is normal? If not, what I need to do?
[X Style (Pure) Android Development] jason2678:
That's normal. Are you coming from stock 7.0?
[X Style (Pure) Android Development] dancho2000:
Off topic: Sorry for the stupid questions, but I'm coming from LG G2 and most of things, are completely different from Moto X Style....

Can someone tell me how is the quality of the sound and the camera, compared to the stock one? Can you take 4K videos and how loud are the speakers? Thanks in advanced :) Also, can someone tell me what is the right (because most of the information is outdated) way to downgrade to MM, root and "flash" TWRP recovery to flash LineageOS 14.1?

Изпратено от моят XT1572 с помощта на Tapatalk
[X Style (Pure) Android Development] thyagomn:
Yes, I'm on stock 7.0 with august security patch.
[X Style (Pure) Android Development] jason2678:
You need to track down the right 6.0 modem for your region and flash it. None of the nougat custom roms work with the 7.0 stock modem.
[X Style (Pure) Android Development] thyagomn:
Oh yeah! Worked like a charm.

Btw, I think that this information was supposed to be in the main post of this thread.

Since yesterday I was searching the reason why this rom don't boot. I could not find this information anywhere.

Thanks a lot.

PS.: Sorry for my poor english.
[X Style (Pure) Android Development] dsnunes:
Hey, can you point out which MM modem did you use? I am also brazilian and I am trying to make a XT1572 Dual Sim work with a custom ROM. Coming from a 7.1 Stock, I am on constant bootloop, even after trying some 6.0 modem files (LA DS).
[X Style (Pure) Android Development] ashoka.inder.dev:
Agent Smith is still popping out ???
[X Style (Pure) Android Development] Dutchblader123:
AOSP Apps

Does this rom come with AOSP apps installed by default?

Also can anyone with this rom test wether this camera app will work

https://www.google.nl/amp/s/xdaforu...oto-camera-6-0-43-10-modded-apk-t3459690/amp/

How is camera quality compared to stock?
[X Style (Pure) Android Development] Kefir.net:
Some are AOSP, some are LineageOS specific.

That camera works great with this rom, also I haven't noticed much difference in quality.
[X Style (Pure) Android Development] silvernirvash:
Ok so before I install this over RR does Lineage OS come rooted? I want to keep root and have something stable and smooth but RR is extremely slow in its current version.

ALSO is there a stable branch of this rom available? I know this is the nightlies thread and the link sends you to the nightlies download page but is there a stable download page??? I can't seem to find it if it exists.
[X Style (Pure) Android Development] Pastinakel:
Nightlies come weekly and are pretty stable, no need for a stable download page. :silly:

For root you'll have to install the addonsu package, which can be found in the 'extra' menu on the download page