yashsingh1/xdaforums huggingface dataset:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] freed_de:
I just do the tests, you do the work. :) So the thanks go to you alone.

I will find an alternative way for the file when I get back from work.

EDIT: [MENTION=6235294]ThE_MarD[/MENTION] Please try this link: https://my.hidrive.com/lnk/EjMYlmqX

Best regards

Freed_de
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] alalalalalal:
Hello, a few days ago I updated my phone from and older version from 17.1 July to the lastest, but now my mobile data doesn't work anymore. I'm not sure what to do now, I would really rather use a solution that doesn't involve completely reinstalling LineageOS if possible.

If there's any more information I can provide to help I am more then willing to provide it.

Thanks for your help anyway.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo [MENTION=11270397]alalalalalal[/MENTION], by chance can you provide logcat?

If you're unsure how, here is the LineageOS Wiki entry for it:

https://wiki.lineageos.org/logcat.html

[MENTION=9324770]freed_de[/MENTION], I'm still working on NFC... Turns out it's not even loading the libpn553_fw.so... oof... So we need to solve that too...

Also, please don't quote and mention in the same post. I got double notifications for your post. :silly:
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] alalalalalal:
Thanks [MENTION=6235294]ThE_MarD[/MENTION], so here's the entire log (pst d°t i can't send links yet moe bar paste bar ifghbt),here's the part of what happened when I enabled mobile data(pst d°t moe bar paste bar drclxj).

Also I think SMSs are not working correctly with the default I sent a message two times to someone right next to me and they didn't get the message but I got theirs. I can try to reproduce that again tomorrow.

Thanks :)
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
[MENTION=11270397]alalalalalal[/MENTION], your post is missing the link to the logcat hmm, maybe try PM'ing it to me? If that doesn't work? I'm on Telegram if you use that app. https://t.me/ThE_MarD
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
[MENTION=9324770]freed_de[/MENTION], another test build is going up! The upload will be done within 30 minutes of this post. I found some other fixes for NFC and I did perform a fresh format data on my payton which tbh I don't think you will need, but this build REALLY improved NFC reliability on my payton so that I can scan my test NFC tags anytime and they respond just as nicely as my Asus Zenfone 5z does). ;)

https://osdn.net/projects/lineageos-for-payton/releases/74015
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] freed_de:
[MENTION=6235294]ThE_MarD[/MENTION] Thanks again for continuing to work on the NFC problem. I had some trouble while flashing (details below). In the end I made a clean flash:

adb sideload <new_testbuild>

wiped data / cache / dalvik

rebooted to recovery

adb sideload OpenGApps

rebooted system

Unfortunately I can't report any success again. :( Log is attached and here: https://my.hidrive.com/lnk/vHs4FbzK

What irritates me: my payton uses NFC Service 1.1 again :confused:

Best regards

Freed_de

P.S.: Details about flashing: I first tried LOS Recovery, but then I found out that only a factory reset is possible here and not just clearing cache and dalvik. After the reboot into the recovery I had a boot loop again...

P.P.S.: About the double notifications: I'm sorry if I annoyed you here. I thought that it might be useful in this case because I changed my last mail afterwards to create the link to the log. Anyway, I didn't want to be a spammer...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @freed_de, hmm darn! android.hardware.nfc is still crashing for you and that darn app hmm... I wish I knew german and had an ID to test with so I could also test lol oh well...

That last build was with NFC HAL 1.1 as I was testing a fix for libpn553_fw.so and it did work for cleaning that up.

So here's a test build meow using the fix for the NFC FW blob and also updating to NFC HAL 1.2 and using river Q NFC FW blob and configs. NFC works for me with these changes so that's a good sign... worst case scenario where NFC still crashes for you? We can do an extreme last resort attempted fix by using NQ NFC stack with Xiaomi Mi Note 3 (jason) configs and NFC FW blob I guess as this AusweisApp2 might rely on NQ NFC for some reason (and Motorola don't use it) :silly:

The build is uploading and will be done within 30 minutes of this post

https://osdn.net/projects/lineageos-for-payton/releases/74025

Oh, just to check, that AusweisApp2 works on stock payton ROM?

Did the app by chance work on LOS 16.0?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] freed_de:
@ThE_MarD

Okay, next try:

fastboot boot twrp

adb sideload [yourBuild]

adb reboot recovery

adb reboot recovery

reboot system

Unfortunately as always: no success and log is attached.

I checked if "AusweisApp2" works on stock payton ROM:

Reinstalled stock rom (from TWRP backup; using boot, data, system image, vendor image, efs, persist, fsg, dsp, boot logo and Bluetooth). Unfortunately no success either.

I did not try LOS 16.0 so far. I've got no image anymore.

Uff. What can we do? I was hoping it's just a small configuration change ... :rolleyes:

Some time ago I had an HTC One M9 (hima). There were also problems with NFC there. The developers found a problem in configs/nfc/libnfc-nci.conf (see https://gerrit.aicp-rom.com/c/AICP/device_htc_hima/+/97272). I don't really understand these things, but maybe it helps?

Best regards

Freed_de
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @freed_de , oof! Doesn't even work on stock ROM? Hmm, that's not good... :(

I asked the guy who maintains Hima and the guy who recommended that commit to him and he said he doesn't think it'll help us as it's usually just NFC Extended Length feature that we would need, but meh, I'll try this just to see if it helps.

https://osdn.net/projects/lineageos-for-payton/releases/74040

If that doesn't work? I think next is I'll switch to pure CAF NFC configs and see if they help. If not? Then I guess Kang Jason (Xiaomi Mi Note 3) configs, FW blob and also switch to NQ NFC stack as a last resort. 🤪
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
if you are liking LineageOS on your Moto X4 let's get the dev behind all this a Moto X4 and get official LOS support.

https://xdaforums.com/moto-x4/how-to/lineageos-dev-erfanoabdia-moto-x4-t3808858
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Sparkledonkey:
Dialer/phone app problems

So, incoming calls show no caller ID and I have no options for answering calls. When I place a call, the window never changes after pushing the green "call" button, so I have no way to hang up(except airplane mode), can't mute, or turn on speaker phone.

Have tried reinstalling the dialer app, no change.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] dj_L:
GApps issue with the updated dialer. Set phone app as default and it should start working.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
can you please get us a logcat?

we checked with our testers and they dont have this issue.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] jhedfors:
As it creates a terrible user experience for others to scroll through, please attach logs, or provide a link to the logs.

This will be greatly appreciated by many.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
Terminal

adb logcat >call_issue.txt

go to phone

call someone, change volume (increase and decrease)

hangup after a few seconds.

back to terminal

ctrl+c or just pull the cable

Attach txt file here.

Thanks.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
So this rom seems fine other than my calls don't always pop up until it's missed. Also, Android auto does not work at all... It won't pop up on my infotainment screen.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
Can you tell me what you did to get this to work? It does NOT work on my phone. The app does launch on the phone, but it wont activate on my infotainment system in my car. This is a worse state than stock. At least with stock, it worked most of the time.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] elementbreaker:
You need to change your default phone app.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
Did that... will see how it goes, but the Android Auto problem is more important to me. No one seems to have an answer to that.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] LazyCountry:
I succeed in XT1900-5
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] munchy_cool:
did you use the firmware copy zip ? or one of the firmware packages, if so which one ?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] LazyCountry:
I flash this one firmware_27.251.12_payton_retail_xt1900-1.zip
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] edufur:
So is this ROM not based on the newest firmware? I think I know what is going on with Android Auto not working... it would appear that the MTP option is not showing up when plugging in USB. I don't know it this is related or not but I at least found that to be concerning. Anyone else?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] dzdzjb:
Mobile hotspot / wifi tethering also not working for me (xt1900-1 / Project Fi) on 20180617. As ptn107 described, I can connect a device to it, but no data is getting through and I'm alerted on the connecting device that there is no connection to the internet through the hotspot.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] michael28056:
Only issue I've noticed so far is with WiFi calling on projectfi / hangouts. I can hear other party but they can't hear me. Cell calls are fine. I think the APN settings in the rom need to be tweaked for fi, or something to fix VoIP.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Neffy27:
My understanding is the project Fi app automatically configures the APN settings, not the ROM. If you uninstall the app, the APN menu becomes visible.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] michael28056:
Yes that's right. I tried a bunch of fixes and just went back to stock rom.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] Rodriigo69:
The ROM works fine on xt1900-4 flashing retail ROM whit march security patch
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] freed_de:
Hey @ThE_MarD ,

I installed your latest test build. This time there is something new to report, although not really helpful: my payton boots up to the setup screen, after about 10 seconds there is a reboot into LOS recovery. There it says that the system could not be loaded successfully and a factory reset is necessary. But that doesn't help: if you follow the instructions, the same thing just happens again.

The bug seems to be somewhere in your test build. Anyway, I just installed an official LOS NIGHTLY and the error is gone.

I'm sorry, but this time I can't do an NFC test as long as the build doesn't boot.

Best regards

Freed_de
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Oof! @freed_de I think during the forum migration my post was lost for the NFC test build with CAF NFC config files, so here it is

Release lineage-17.1 lineage-17.1-20201206-UNOFFICIAL-payton - lineageos-for-payton - OSDN

Release lineage-17.1 lineage-17.1-20201206-UNOFFICIAL-payton - lineageos-for-payton #osdn

osdn.net
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] freed_de:
And I already thought our common search was over... :D

I installed the last test build (adb sideload via TWRP, clear cache/dalvik, reboot). Up to here without problems.

Reading the test cards was difficult. I have the impression that it is unstable overall. I did manage to get a log of the AusweisApp2 though. It still says "ExtendedLengthApduSupport missing." unfortunately. (see logs).

Thanks for persevering

Freed_de
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Hmm, well this NFC log doesn't show the NFC service crashing... so maybe it's an improvement? 🤪

One thing that is seriously concerning is how the AusweisApp2 website clearly states the Moto X4 isn't supported

https://www.ausweisapp.bund.de/mobi...c22c8aa0b0cf117a0f9db6601660bc8#mobiledevices

yet that HTC One M9 is...

https://www.ausweisapp.bund.de/mobi...be46e14e9f79418983d487e00df66f6#mobiledevices

I'll have to try that NQNFC stack with CAF configs next I guess and see what happens...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] hele-hh:
Hey @ThE_MarD, @freed_de,

I installed the AusweisApp2 on two Moto X4 (XT1900-7):

- Stock-ROM, PPWS29.69-37-5

- LineageOS 17.1.20201208-NIGHTLY-payton

I successfully tested the app on both devices, see Screenshot.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @hele-hh , thank you for the insight. Just to check, is this the build and firmware you were on?

https://mirrors.lolinet.com/firmware/moto/payton/official/DTPL/

Or was it RETEU SS or DS?

https://mirrors.lolinet.com/firmware/moto/payton/official/RETEU/
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] hele-hh:
@ThE_MarD,

firmware and build (received by Motorola OTA-Update):

https://mirrors.lolinet.com/firmware/moto/payton/official/RETEU/XT1900-7_PAYTON_RETEU_DS_9.0_PPWS29.69-37-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

LineagOS 17.1:

https://mirrorbits.lineageos.org/full/payton/20201208/lineage-17.1-20201208-nightly-payton-signed.zip
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@hele-hh thanks! And just to check, was that with or without Magisk?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] hele-hh:
Phones not rooted, Magisk not installed ...
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] freed_de:
@hele-hh , @ThE_MarD

It's nice to hear that there is a payton that works :)

I looked here on my device:

fastboot getvar all

supplies

[...]
ro.build.fingerprint[0]: motorola/payton/payton:9/PPWS29.69
ro.build.fingerprint[1]: -37-5/63ca8:user/release-keys
[...]
ro.carrier: reteu

So it seems to be hele-hh's device firmware?

@ThE_MarD , should I reflash the one? And if so, is this guide correct?

How to Install Stock Firmware on Motorola One Vision via Fastboot Commands

In this guide, we have listed detailed instructions on how to Install Stock Firmware on Motorola One Vision via Fastboot Commands.

www.droidwin.com

It is different from this one:

How To Flash Motorola Firmware And Updates | Blog The Tech

Do you want to flash your Motorola Android smartphone or you want to unbrick it, today?, I am going to tell you how to do that.

blogthetech.com

(I have never done this before... :rolleyes:)

Or is it possible just to flash the zip files from lolinet via "adb sideload ..." ?

Thanks for your hints.

Freed_de
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] hele-hh:
@freed_de

I installed Ausweisapp2, new version 1.22.0 as of Nov 30, what about you?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] freed_de:
Same here. 1.22.0
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@freed_de , I use this script and the instructions are contained with it

https://mirrors.lolinet.com/software/windows/TinyFastbootScript/

Please be sure that everything important is already backed up off of your payton and I select flash full firmware and erase just to ensure the stock ROM is flashed and working as intended.

As hele-hh mentioned he didn't use Magisk so please also don't flash it
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] freed_de:
@hele-hh , @ThE_MarD

I have fantastic news: Indeed, it works now!

I did not re-install the firmware at first, but only installed the NIGHTLY that hele-hh mentioned. There was nothing else to do. It just works now.

By the way: Magisk seems not to be the problem. I do have installed Magisk, there seem to be no side effects.

I can not say which NIGHTLY fixed the function, because I last tested only the UNOFFICALS from ThE_MarD with the AusweisApp2. Hmm. Maybe hele-hh knows since when it works?

Either way, maybe someone can find the crucial changelog? There was some NFC work in the last build:

https://review.lineageos.org/c/LineageOS/android_device_motorola_payton/+/294712/

https://review.lineageos.org/c/LineageOS/android_device_motorola_payton/+/294713/

https://review.lineageos.org/c/LineageOS/android_device_motorola_payton/+/278359/

https://review.lineageos.org/c/LineageOS/android_device_motorola_sdm660-common/+/295067/

Maybe one of these solved the problem?

Oh man, thanks. You guys are the greatest.

Freed_de
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JimDandy68:
Sorry if I've missed information that applies here, but anyone else having issues lately losing data after flashing this LOS?

I just tried from my existing stock (original, RETUS, updated as far as it went over stock OTA), no data on booting LOS. Then I went back to stock using the next-to-latest RETUS image from lolinet, rebooted with data working fine, and now I've flashed the latest LOS nightly again and again have no data on reboot. I used copy-partitions both times before flashing the ROM, and think I followed instructions as I should.

Thanks

EDIT:

I missed this: https://xdaforums.com/t/rom-official-payton-nightlies-lineage-os-17-1.3802265/post-78261236

I may try again and not flash Magisk before initially booting the ROM. Not sure if this has anything to do with my issue.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
Heyyo @JimDandy68 , you will need to Format Data as mentioned in the official install instructions as custom ROMs cannot carry over decryption from stock ROM for payton. :(

Please follow the official instructions here:

https://wiki.lineageos.org/devices/payton/install

@freed_de that is epic news! I'm glad everything worked out in the end! 😁
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JimDandy68:
Hey, @ThE_MarD, I did Format Data each time, so that wouldn''t be the culprit. Ultimately, even after going back to stock using Lolinet firmware and scripts from the return-to-stock thread, I was getting reboots after initial setup, so I ended up getting LRSA and restoring from there.

Turns out, Lolinet had a Fi firmware posted under RETUS, so LRSA detected that and now my phone is FI with Pie (updated to security patches for October). But it's working fine, with data again. In case anyone tries to grab it, PAYTON_RETUS_9.0_PPWS29.69-39-6-6 appears to be just a renamed FI, even thought it's posted under RETUS.

When I have time, I think I'll try again with LOS, but start with just the ROM and Gapps, and see how that goes. I was rebooting recovery after each flash and using ADB sideload for each, but I didn't boot the ROM until after flashing ROM + Gapps + Magisk, so maybe that's a problem?

Interestingly, I never had issues booting the 1st time, but missing data (only, not Wifi) in LOS and reboots after initial setup were problems I encountered until I used LRSA.
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JimDandy68:
Ran into the same loss of data issue trying to flash LOS again. Back to using scripts/LMSA/LRSA to re-flash stock. If anyone has any ideas what could be wrong on my end, other than formatting data (which I've been doing), please reply.

I just realized that the instructions from LOS have confused me, too. I've been flashing TWRP from fastboot, and getting a bootloop to recovery, directly after returning to stock.

TWRP's instructions: "If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image."

So I guess you should really never "fastboot flash boot twrp.x.x.img"
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] mikedeaster:
Hi.

How run wide camera in stock camera app, cant found. Show on screenshot please.

if it can`t be runned, why 'disable' button inactive for apps like camera, gallery?
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JimDandy68:
Now I've installed TWRP on stock the correct way (fastboot boot twrp.x.x.img, then install zip from sdcard). I managed to also then install Magisk, also rebooting back into recovery and flashing it to both slot_b and slot_a.

Question: Before I try LOS again and possilbly lose data (I've gone thru this many times in the past few days), does anyone think, or know, that this might have been my problem all along? Would I need to flash LOS 2x, once to slot_b and once to slot_a? The slots still confuse me.

Thanks
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] ThE_MarD:
@JimDandy68 , as the official installation instructions mention for payton? The most important part for A/B partitioned devices is the copy-partitions zip so that the active partition is properly copied to the inactive partition, so that both slots have matching device firmware and any other important partitions.

Specificaly for payton as well, as the installation guide also says

https://wiki.lineageos.org/devices/payton/install

I would also recommend following that guide as it recommends using Lineage Recovery instead of TWRP. I've noticed on my Z01R (Asus Zenfone 5z) for some reason formatting data and rebooting to recovery sometimes swaps the slots which is not good...

Potentially though? Your problem could have been the device firmware or Magisk. Device firmware can cause all kinds of issues like what freed_de had with that AusweisApp2 and NFC

Before formatting data, it is always recommended to backup any important data off of the device first to prevent any data loss
[Moto X4 ROMs, Kernels, Recoveries, & Other Develop] JimDandy68:
@ThE_MarD, thanks again for the help and advice.

To be clear, I have been doing my best to follow the instructions, which included starting with latest firmware (I was running the last Pie update for RETUS when I started my attempts) and running copy-partitions latest zip, all before flashing LOS, rebooting to recovery, then flashing GApps, etc. My woes with loss of data and reboots made me think I had issues with A/B swapping.

Note that LOS's own instructions mention using TWRP, and it was there that I found the instruction to flash it from the bootloader. It's on TWRP's site that I later found this is not recommended. Long ago, I must have followed those instructions correctly (adb boot temporarily to TWRP image and then flash the TWRP zip from within TWRP), because I have been successfully rooted via Magisk and had TWRP installed for well over a year.

I think you're right that it might be worth trying all of this without TWRP at all, starting with another return to latest stock, then booting temporarily to the Lineage recovery from fastboot, running copy-partitions, then installing LOS, etc.

Finally, I have backups and most of my important data on my external SD, but I've given up trying to recreate my most recent setup, other than reinstalling the majority of the non-Google apps and restoring some backed-up configs and SMS/call-logs/wifi.

I will report back the exact steps I take if I manage to get this right. FWIW, I think the LOS instructions under "Temporarily booting a custom recovery using fastboot" step #5 should be removed:

I think this causes trouble, and I should stick to just "fasboot boot <recovery_filename>" or flashing TWRP from a zip within a truly temporary recovery.