Since it's a bug reported by a few people now, a log would be helpful to troubleshoot the issue. Please send one when reporting it
I can reproduce it. I can also not charge my card of public transport neither scan a sensor through librelink app. However, gpay works. What I mean is that NFC works only when used for very short period, but not for longer use like for charging cards or for scanning a sensor which they both need couple of seconds of touch.Hi! I tested the rom in my SM-A705MN, use Magisk, Safetynet patch, and almost everything works flawless, except an application that uses NFC to recharge a public transport pay card in my country, that was a deal breaker for me and i'm back to stock. The NFC works, i use NFC tools and read the card ID, and another data, but the payment application says that the card can't be readed.
Edit: I'm open to install it again if that helps to debug. Thanks for the Hard work.
If you could try to reproduce that issue on 19.1 it would be very helpfulI can reproduce it. I can also not charge my card of public transport neither scan a sensor through librelink app. However, gpay works.
Not working in 19.1, same behaviorIf you could try to reproduce that issue on 19.1 it would be very helpful
Thanks!That's a new issue, but NFC itself is proved working so I'm not sure if anything can be done about that. Anyways I'll update some NFC-related stuff and see if it changes anything.
Sure is, I've been using it for a week on FN without any issues
Ops, muito obrigado pela dicaUse o kernel de linhagem, é mais estável e tem bom desempenho também. Kernels "mod" mais antigosnãofuncionarão com o Android 13
With what I have tested from the rom in my sm-a705mn, the cause of the data reset may be due to pressing the volume buttons + - and the power button at the same time and it restarts and then does a kind of factory reset (still don't know why)PSA: If you reboot your device often, please back up your data since it was just discovered that there is a very slim chance of a data wipe after a reboot for yet unknown reasons, which is difficult to troubleshoot.
This could happen next reboot, in a week, or never, depending on your luck. This has never been reported on 19.1 so if you want to feel safer, jump to that.
I'll update the first post with this info.
Newer firmware should be working fine too. Since I haven't pushed out a fix for encryption yet, I'd suggest using lineage 19.1 for the time being to avoid data lossCool, thanks for the rom really nice work, im waiting to be published! Btw can i flash on the newer firmware or downgrade to DVG3? Because the newest is DVK3
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
adb sideload <rom-file>
Apart from that, only thing you could do is use OneUI mods.. volte might happen one day if someone takes the time to reverse engineer it but so far we're out of luck. This is a problem on every samsung device on AOSP, and with other makes, YMMV.Thanks, due to needing Volte for calls and texts, now that 3g is shut down, looks like im stuck using stock.