yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Better news than I expected to hear. Are the contacts broken above board level? If so a fix may well be possible by re-soldering the contacts. This could be tricky in as much as it may be difficult to prevent heat transfer down the wire into the board. I had assumed they had been wrenched out below the board surface. If you just glue the connector housing withe contacts in place you might be lucky and find it reliable. However I would worry that with every knock or jolt you.ll find the pone will turn of and you'll have to keep re-starting it.

Mike
[8525, TyTN, MDA Vario II, JasJam General] DocSoton:
See attached, not great quality, but you can see the contacts...

What on earth do I use to stick it back on???
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
From that it appears to have snapped through the soldered joints without any real damage. If that's the case then it is fixable. The last example we saw of this on the forum the contacts broken inside the board, but it looks like you are lucky.

Mike
[8525, TyTN, MDA Vario II, JasJam General] boog:
From your comments, it sounds like you don't have any experience with soldering. I would look for an electronics repair shop, or find a friend that has experience soldering.

If you can't find that you may only have the option of selling it somewhat cheap. I do my own soldering, so I don't know what direction to try to point you for that. Hopefully this will help you getting your hermes back up and running.
[8525, TyTN, MDA Vario II, JasJam General] DocSoton:
Thanks for all your help.. lukily the old man is a sparky.. so Im sending it up to him to have a go, if not him, then his mates and electronics whiz.. so hopefully I should get it back all sorted.

Cheers
[8525, TyTN, MDA Vario II, JasJam General] DocSoton:
Its been a while since I started this post... just not got around to getting it sorted until recently...

Now, does anyone know what the different contacts do?? We have partial success with resoldering the contacts, the device now turns on, when on power, but it is not charging the battery.. I can only assume the contact(s) responsible for charging the battery may have a poor solder...

The battery says 100%, but when I remove power, it turns off after a very short while...

Can anyone help..?? Its come along way since I originally broke the device, and I wasnt sure if it would ever work again.. but I seem to be so close to breathing life back into the phone, and am sure we only need to resolder a couple of the contacts.... Would be handy to find out what all the contacts actually do...
[8525, TyTN, MDA Vario II, JasJam General] ultramag69:
The battery may have gone bung, especially as its 6 months later that this problems started. If it started right away I'd say it could be the contacts but if it has only just reared its head I'd say that the battery needs replacing. If you can get your hands on a spare, they are fairly cheap through ebay (less than $10), then you can check if it is the battery.

Cheers...:D
[8525, TyTN, MDA Vario II, JasJam General] DocSoton:
I already had a spare battery.. I get the same on both...

After powering on, the light goes amber for a couple of mins, suggesting it is charging, then goes green.. show 100% charged.. but dies after a few mins...

If the power is not connected, phone wont even turn on... I can only assume neither of the batteries is being charged...

I did read somewhere, although cant remember, that one of the contacts is responsible for charging.. would be good to know what the contacts do...

Thanks
[8525, TyTN, MDA Vario II, JasJam General] ultramag69:
Best idea would be to go to Mike Channons site. He is the guru of all things HTC. At the very least you could pm him but I haven't really seen him hanging around the Hermes site for a while. The link to his site is in his sig.

Cheers...:D
[Samsung Galaxy S9  Questions & Answers] mark55555:
I'm on T-Mobile with my S9+ and I've been pulling my hair out for months trying to find a solution.

Using 4g for calls leads the phone to glitch and drop the majority of my conversations, but not drop.

I've had T-Mobile replace my SIM, used my SIM on other phones with no issues, factory reset my phone and used safe mode. The only workaround I have come up with is running my phone on 2g/3g constantly, because some geniuses at T-Mobile disabled the ability to turn off VoLTE. I am losing money and opportunities because of this - busy people generally don't like when you hang up on them when you can't hear them and they can't hear you.

Since rooting the phone, using ODB magic or kernel/rom changes are not an option due to the chipset, I pose the (very desperate) question:

Is there any software or trick that anybody knows that will allow me to disable VoLTE on my T-Mobile Samsung S9+? Or any sort of workaround? I am stumped!
[Samsung Galaxy S9  Questions & Answers] Youdoofus:
flash a CSC for a different carrier. The csc is what tells the phone which carrier specific software to install/use and voLTE is very carrier specific
[Samsung Galaxy S9  Questions & Answers] mark55555:
Where might I be able to find the correct CSCs for North American carriers?
[Samsung Galaxy S9  Questions & Answers] Youdoofus:
ACG – Nextech/C Spire

ATT – AT&T

CCT – Comcast

LRA – Bluegrass Cellular

SPR – Sprint (CDMA)

TFN – Tracfone

TMB – T-Mobile

USC – US Cellular

VMU – Virgin Mobile USA

VZW – Verizon

XAA – USA (unbranded/unlocked/default)

XAS – USA (unbranded/unlocked)

https://www.**********.com/how-to-change-csc-in-samsung-galaxy-phones/

and the firmware is available at www.sammobile.com/firmwares but when downloading, use samfirm or frija, theyre literally 4x faster than a direct DL. Frija and samfirm are free and available here on good ol XDA
[Magisk] lapwat:
NFC Screen Off

Read NFC tags when screen is off.

Disable NFC tagging sound.

Tap to pay when screen is off.

ALWAYS include Magisk installation logs when posting an issue.

Useful integrations: NFC Card Emulator Pro - Tasker

Installation metrics: Grafana dashboard

How does it work?

The NFC app is patched during installation into a `modded` version. This `modded` version is injected at boot time by service.sh so that the phone thinks the screen is always on and unlocked.

This patch only applies to NFC Service so it does not impact any other functionality of the phone that involves screen state detection.

The `modded` app was generated using this method.

Help section

MY NFC IS NOT DETECTED ANYMORE

If you did not unlock your device since last boot, unlock it and wait 30 seconds for the module to be loaded.

After that time, if NFC does not start automatically or manually, it means that the patch does not work for your device. You can uninstall the module and create an issue.

I AM STUCK IN A BOOTLOOP

Remove the module manually.

1. Boot into TWRP

1. Advanced -> File Manager

1. Delete /adb/modules/NFCScreenOff

1. Reboot

THE MODULE IS NOT WORKING SINCE LAST UPDATE

Perform a clean reinstallation.

1. Uninstall the module

1. Reboot

1. Install the module

1. Reboot

If it does not solve your problem, you can create an issue.

I LIKE THE MODULE
[Magisk] marcozpaulo:
Only for rooted devices ok?
[Magisk] maujogue:
It broke my nfc payments. Any fixes ?

Should it work normally with Google pay ?
[Magisk] rodken:
Not yet. It's on the To-Do list.
[Magisk] crime_of_heart:
Thanks for enabling this option.

It may not necessarily be a bad thing that it breaks safety net.

Enabling mobile payments while phone is locked is NOT a good idea. Your phone will be vulnerable to money theft with some special NFC devices. They can get close to your phone while it is in your pocket or purse and that is enough for them to steal your money.
[Magisk] maujogue:
Yes, that's a bad idea. I just want it to not brake payments, as I couldnt use Google pay even if I unlocked with this module
[Magisk] SatanicShanker666:
[MENTION=6471406]lapwat[/MENTION] Hi, awesome module. It is not working for me since the path (and app name) for nfc app is system/app/NxpNfcNci/NxpNfcNci.apk

Android 10.3.0

Oneplus 6

Stock ROM

Edit:attach log
[Magisk] lapwat:
Yes it should continue to work normally with Google Pay.

What I meant in the description of the module is:

For now, it only works for reading NFC tags. For payments in stores, the phone still needs to be at least on. If the module is working for tags but breaks your payments, leave a comment.

Is it the case for you? The module works for NFC tags but the payments are broken?

What are your specs (device, rom, android version)?
[Magisk] lapwat:
Yes, only for devices rooted with Magisk.
[Magisk] rodken:
Now I get it regarding Google Pay.
[Magisk] maujogue:
Exactly. I tried paying but nothing happens, like if nfc didn't exists on my phone. I desinstalled the module and I could pay again. Paying is more important than reading nfc tags for me !
[Magisk] rodken:
That's good to know. Will wait for further development.
[Magisk] lapwat:
Thanks for the logs. Can you send those files to me:

/system/app/NxpNfcNci/NxpNfcNci.apk

/system/framework/framework-res.apk

I will do a version for people with NxpNfcNci app (I guess it is OnePlus customized NfcService).

My stock Xiaomi ROM had a NQNfcNci app.
[Magisk] SatanicShanker666:
Ok nice, thanks! Here you go:

http://www.mediafire.com/file/2zcmud0i2z8y0vy/framework-res.apk/file

http://www.mediafire.com/file/fys9ee6s308qmy9/NxpNfcNci.apk/file
[Magisk] lapwat:
I've done it! Try installing the module and tell me if it works!
[Magisk] virseph:
Not the same guy, but also using Oneplus. It installed successfully but doesn't seem to be working.
[Magisk] 2me3:
Is it possible to modify the installation script to account for ncinfc with other names? For instance on the Razer phone 2 it is named NQNFCnci so the script can't find it
[Magisk] lapwat:
From what I understand from feedbacks, the apk app can have several names:

NfcNci

NQNfcNci

NpxNfcNci

Those names do not depend of the device but depend of the ROM.

Two apk with the same name will in fact be different. They are very related to the framework of the ROM.

Loading an APK from another ROM even if it is the same Android version will have little chance to work.

I cannot detect all the specs of the device. Magisk only gives me the Android SDK Version that's all.

I could make an apk for every ROM.

2 possibilities:

- Zip framework.apk + (NQ/Npx)NfcNci.apk, send it to a server. The server will return a custom apk just for your ROM. This is the one that Magisk will use.

- Build the custom APK directly on the phone, but I cannot find how to run apktools, jarsigner, etc on Android (because there is no JAVA env on Android)
[Magisk] lkp171:
Hi, on my first try a few days ago it didn't install i think it was because the path too, but now it works perfect. Thanks dev:good:

oneplus 6

Android 10 OB 33

xXx magisk on stock rom

Blu spark kernel
[Magisk] 2me3:
Yes I extracted the zip and modified the customize/service.sh scripts to properly work with my rom and as you stated it did not work. as soon as the script killed the nfc service it triggered a reboot to recovery.

I PM'd you a gdrive link to the stock apk's from the razer phone 2 Pi stock rom. If you have some time would please build it for me? I tried to do it myself a while ago but ran out of steam before i even got all the dependencies running on my computer lol. I can modify your magisk package to work with it myself.

I like your idea of a server that automatically runs the process to patch the apk. Would every use need to upload both the framework.apk and nfcnci or just the nfc? The only concern I would have is bandwithd as the framework apk is 30+ MB's. If you could build the server into a docker container I think it would be easy enough for others to host you could probably find some people willing to host it for free. Another option could be using a google drive account to allow people to upload the apk's for their phone then batch process them all and sort them by model/build # or something to cover most phones/roms . I have a gapps for business account with unlimited storage I could probably lend for this purpose

Once again thanks for all your work! If you have a bitcoin address i'd like to buy you a beer
[Magisk] off69sys:
@lapwat

Good day! Help,. please. My installation failed.

Android 12L

Xiaomi Poco X3 Pro

Custom ROM

Thanks!
[Magisk] badhabit_wb:
Same here on pixel 6 pro
[Magisk] Valiante:
Is it possible to add a vibration upon scanning an NFC tag?
[Magisk] Drahy:
Hello,

Will the pay feature with turned off screen be enabled again? Or is there any different module for it? I would appreciate it. Thank you.
[Magisk] lapwat:
Please try to replace the curl binary located at /system/bin/curl by this one: https://github.com/Magisk-Modules-Repo/NfcScreenOff/blob/master/bin/curl

Do not forget to give it the execution rights: chmod +x /system/bin/curl

Do a backup of your curl binary before!!!
[Magisk] lapwat:
It will depend on your ROM, mine does vibrate when scanning a tag.
[Magisk] lapwat:
This feature never actually worked.
[Magisk] XtraWater:
Mine vibrates too. If not, you can add it with Tasker.
[Magisk] Jon8RFC:
@lapwat is there a specific IP I can force the module to use if DNS isn't updating properly? I'm getting server failures. Thanks for this awesome module--it's very handy when I can't look at or unlock my phone.
[Magisk] Jon8RFC:
Sometimes it works on Pixel 6 now, never on Pixel 7.
[Magisk] lapwat:
What's your error ? The server is hidden behind a proxy, I cannot give out the IP address.
[Magisk] 3zozHashim:
does this module automatically enable and disable NFC when needed or should the NFC be enabled?
[Magisk] lapwat:
NFC should be enabled to detect a NFC tag. This module does not turn on NFC automatically.

Keep in ming that leaving NFC enabled on your phone does not have significant impact on the battery draining.

https://www.reddit.com/r/Android/comments/1sllvq/_/cdyxh8t
[Magisk] Jon8RFC:
Here's one log each from a Pixel 7 Pro and a Pixel 6 Pro yesterday. Unfortunately, I've erased the log from a few days ago when the Pixel 6 Pro had the same two errors as the Pixel 7 Pro.
[Magisk] lapwat:
It seems that there is a problem in version 0.3.3. Can you try to install it directly from Magisk, by searching for "nfc" ? It should try to install version 0.3.2.
[Magisk] lapwat:
Also it would be good to know if your phone can actually reach my server :

curl https://patcher.lapw.at > data.csv
[Magisk] Jon8RFC:
Attached is a log with 0.3.2 which appears to have the same errors.

Side note that Magisk doesn't natively support a repository anymore, which is a bummer. Your 0.3.3 does show up with Fox's Magisk Module Manager.

It worked and grabbed the file. Interesting to see my numerous failures of exception & fail-disassemble.
[Magisk] lapwat:
I am going to ask several files from your phone to try to understand why those exceptions arose:

- NfcNci.apk (should be in /system/app/NfcNci/ folder)

- /system/framework/framework-res.apk
[Magisk] Jon8RFC:
Attached are those two files.
[Magisk] lapwat:
It seems that your decompiled code was in `smali_classes3` directory:

Update patcher.py (46ffc560) · Commits · Quentin / NFCScreenOffPatcher · GitLab

GitLab.com

gitlab.com

I have updated the server can you try again ?
[Magisk] Jon8RFC:
It received a different error this time:
[Magisk] lapwat:
Another version has been pushed where I update apktool to latest version.

It should handle latest Android versions correctly this time.

Let's try again :)
[Magisk] Jon8RFC:
Woohoo! Successful patching, rebooted, and it's scanning with my pixel 7 when the screen is off.

Thank you very much for looking at this and updating it! I wish others could know to retry it if they also had different smali directories, because many of those "failures" looked like mine. You could post a "maintenance" update of 0.3.4 and maybe that'll let them know to try again. I want them to try again, haha.

Thanks again! This is so handy and I'm glad my new phone will now have the same functionality.
[Magisk] SubjectGinger:
Where can we get this updated version?
[Magisk] lapwat:
Just install it from Magisk and it should work. The server has been updated but the Magisk installation script stays the same.
[Magisk] SubjectGinger:
Got it, thanks!

Working well, but the sound is still present. Not sure if that's an issue for anyone else.
[Magisk] Jon8RFC:
Bummer.

Looks like the December 2022 update for Pixel 7 Pro broke things again.

Attached are an installation log and the two apk files you had requested before, if you don't mind taking a peek.

Maybe it's just needing an apktool 2.7.0 update. I appreciated hearing what you were finding and fixing last time. I like learning new things!
[Magisk] lapwat:
Should be fixed in last version

fix: check nfc dir exists (7e8cba9e) · Commits · Quentin / NFCScreenOffPatcher · GitLab

GitLab.com

gitlab.com
[Magisk] Jon8RFC:
Gave it another shot and it worked!

You're awesome, thank you!
[Magisk] fergalc:
Hi, where can I find v0.3.4?

Fox has 3.3 and that fails to install

Best regards
[Magisk] Oramous:
Hi. Same issue for me. Module install keeps failing on old galaxy s7. I've tried multiple times but it keeps getting stuck in the same place. It says:

--uploading archive for odex modding (/data/adb/modules_update/NFCScreenoff/bin/curl), it may take a while (42mb)

!! odex strategy failed.

! Installation failed
[Magisk] Jon8RFC:
@lapwat sorry to bug you again, but it seems like the March 2023 update for Pixel 7 Pro doesn't want to cooperate. I tried twice today (saved a log file the second time), and saw another pixel 7 pro failed as well.

I've attached those two apks and the magisk installation log. If you get some free time to take a look, thank you!

I saw that DisableFlagSecure patcher had to update apktool...yet again...for it to keep working.

Thank you for keeping your awesome project going!
[Magisk] Filelor:
Also failing on Pixel 6 (oriole) with the May 2023 update. It would appear there is an issue contacting what ever server it is trying to access. (ver. 3.3)
[Magisk] Stefamag09:
Same issue here. Is this module dead?
[Magisk] Alessandrotischer:
Hope not... 🤞
[Magisk] pratyush28:
@lapwat can you please help me? Im getting the odex strategy failed error. I'm using OnePlus 8T running OOS Android 11. Could be problem be that I don't have r/w access to /system on my device? I'm attaching the magisk logs too.

Please let me know if someone getting r/w access can fix this problem also I have xposed so maybe somehow I can use your old xposed module?
[Magisk] J0KER!:
getting that odex strategy failed error too

is there no solution for it? :(
[Magisk] DmitryArkh:
Regarding the installation issues: the NfcNci.apk package of new ROMs may contain a new smali directory, which the patcher cannot handle at the moment. I've already created a merge request, but it seems that the developer isn't very active lately.

To fix that, you can manually deploy the patcher with Docker and edit the Magisk module so that it connects to your container. Don't forget to add 'smali_classes4' to the possible_folders list in the patcher.py file.
[Magisk] Jon8RFC:
Update to my above, heavily-edited post.

Tasker profile attached that should, itself, be no impact on battery. I've turned off both gestures of "tap to check phone" and "lift to check phone", so that things don't run wild. It might work just fine with those enabled since there's "wait 3 seconds" on the task so that the prior "nfc enable" has a chance to complete. The "nfc 7" MUST be able to run before NFC is turned back on.

It's especially necessary for me since NFC only turns on (via tasker) under certain conditions, which is almost always when the screen is off, so it needs to be properly reset or else it won't work properly with the screen off with this magisk module (as of June 2023 Pixel 7 Pro factory image). So I also will have it reset whenever tasker turns on NFC.

It runs

adb shell service call nfc 7 & adb shell svc nfc enable

once when the screen turns on and NFC is on (which android now resets NFC functionality even if the screen is locked), and once when the screen turns off and NFC is on.

Lapwat is the expert who created the whole module and the patcher server, but I may run a patcher server if he's become bored with the maintenance of it. I'd only be able to make small updates/tweaks, not create anything new--I've learned a decent amount in the last 3 weeks, but it's still above my pay grade.

POST EDIT

@ 2023-07-07T08:06-05:00

Possibly the March or June 2023 update has policy changes for the nfc service and others:

Google Pixel Update - March 2023 - Google Pixel Community

Google Pixel Update - June 2023 - Google Pixel Community
[Magisk] lapwat:
Dear everyone,

Thank you for your patience.

Concerning the code, I am happy to see that some of you could edit the patcher and run it on locally.

I just have released a new version of the patcher on github/gitlab where I have updated apktool to version 2.8.0, and added smali_classes4 folder as suggested. The patcher has been deployed on my server.

About the NFC Service, I am not aware of this issue since my phone is not up to date. Maybe we can find something in AOSP source code. What the patcher does is retrieving the value of SCREEN_STATE_ON_UNLOCKED

https://cs.android.com/android/platform/superproject/+/master:packages/apps/Nfc/src/com/android/nfc/ScreenStateHelper.java;l=16?q=ScreenStateHelper&ss=android%2Fplatform%2Fsuperproject

And injecting in checkScreenState so that SCREEN_STATE_ON_UNLOCKED is returned by checkScreenState everytime it is called:

https://cs.android.com/android/platform/superproject/+/master:packages/apps/Nfc/src/com/android/nfc/ScreenStateHelper.java;l=31?q=ScreenStateHelper&ss=android%2Fplatform%2Fsuperproject

https://cs.android.com/android/platform/superproject/+/master:packages/apps/Nfc/src/com/android/nfc/NfcDispatcher.java;l=480?q=checkScreenState&sq=&ss=android%2Fplatform%2Fsuperproject

https://cs.android.com/android/platform/superproject/+/master:packages/apps/Nfc/src/com/android/nfc/NfcService.java;l=575?q=checkScreenState&ss=android%2Fplatform%2Fsuperproject

A more serious option would be to take the source code of your ROM, edit those lines manually in Java, and build the ROM, but I have never managed to build the AOSP project.
[Magisk] Jon8RFC:
Just documenting more for anyone coming by...

I whitelisted the apk from being suspended when the screen turns off and the command execution was successful and persisted through reboots, but the goal was not attained.

dumpsys deviceidle whitelist +com.android.nfc

I let my computer search through every decompiled file (6,500 files, I think) to find screen_on references, and it found nothing of consequence beyond the two files already edited. One found file referenced the edited screenstatehelper file, so it was no good. The other 3 were in the cardemulator folder, so they're irrelevant.

I tried an older apk and it suffers from the same eventual problem which my Tasker nfc off&on profile solves.

Something must be going on at the system level, I would think, for power saving. I'm stumped about where to go next and it's all new territory to me that I'm learning as I go. It's great that they're potentially fixing the non-root NFC battery draining (never going into deep sleep) I posted about shortly after the Pixel 7 Pro came out, but that trickled down to the rooted phones. I only have NFC turned on when I need it to be, but they got really aggressive with disabling NFC when the screen is off, it seems.

I'm sticking with the stock Pixel 7 Pro ROM and only doing magisk/lsposed modules. It'd be nice to figure out a non-Tasker solution, but at least I have that for now.
[Magisk] wyt18:
Thank you. What is your Tasker solution and can you share how you achieve the same effect?