Database Info

[SOLVED] Google Play Services battery drain post OOS 10 update

Since updating to Android 10 (OxygenOS 10.0.GM21AA) through Oxygen Updater, I've been having heavy battery drain from Google Play Services.
It's top on the battery usage and I've seen anywhere from 10-25%
Things I've tried:
- Opt-in for Google Play Services beta (Curr. Ver: v19.4.19)
- Checked permissions on all apps and disabled any that don't seem right
- Cleared data for Google Play Services
Things I want to avoid:
- Wipe /data or factory reset
- Downgrade
Does anyone have any info or possible fixes for this problem?

Revert back to pie

If you have root use app ops

Are you root ??
If yes.. try installing greenify.. as well as fde.ai...

Seems like Google Play Services is just hogging all my battery even after OOS 10.0.1 update. Does anyone else have this problem or is it just me?

If you're root, try using the magisk module named "Universal GMS Doze" it should solve the drain problem.
If you're NOT rooted, try searching for the Google Services Beta Program, join it and then upgrade your app, it MAY solve the problem.
Good luck

Daenjel said:
If you're root, try using the magisk module named "Universal GMS Doze" it should solve the drain problem.
If you're NOT rooted, try searching for the Google Services Beta Program, join it and then upgrade your app, it MAY solve the problem.
Good luck
Click to expand...
Click to collapse
I'll try this. But it seems like play services is never in the background, all of its battery use seems to be while the device is in use

Daenjel said:
If you're root, try using the magisk module named "Universal GMS Doze" it should solve the drain problem.
If you're NOT rooted, try searching for the Google Services Beta Program, join it and then upgrade your app, it MAY solve the problem.
Good luck
Click to expand...
Click to collapse
Doesn't that magisk module break notifications though? Like notifications are delayed?

I've attempted a bunch of fixes, one of which has fixed this issue, at least so far.
1. Opted in to beta and updated to latest beta Play Services.
2. Installed GMS Doze magisk module
3. Moved apps (particularly my launcher, Hyperion) from battery optimisation Intelligent Control to Optimise.
Not sure which of these fixed it, but my money's on the battery optimisation. YMMV.

valeriee said:
Doesn't that magisk module break notifications though? Like notifications are delayed?
Click to expand...
Click to collapse
I've never encountered anything like that, and I've been using this module since 2018 over various devices/roms.
You should be good to go.

Daenjel said:
I've never encountered anything like that, and I've been using this module since 2018 over various devices/roms.
You should be good to go.
Click to expand...
Click to collapse
So your notifications are never delayed? I thought it was a common side effect of universal gms doze?

Please Close

Hi, I am facing this issue of SafetyNet API error in Magisk Manager from past week. Even though it displays error the banking apps are working fine. What could be the issue and any idea to solve and pass the safetyNet?
Thanks in advance.

The SafetyNet API is part of Google Framework Services. It's used from within apps what are interested in knowing whether Android OS got tampered or not. Not all payment / banking apps runs this test so they may work flawlessly.

jwoegerbauer said:
The SafetyNet API is part of Google Framework Services. It's used from within apps what are interested in knowing whether Android OS got tampered or not. Not all payment / banking apps runs this test so they may work flawlessly.
Click to expand...
Click to collapse
Actually its the issue with the Magisk Manager app, I used a 3rd party app to check the safetyNet and it passed without any problem.

Magisk CTS Profile Failed

Please help Magisk Safetynet is failed

Google seems having updated SafetyNet today...
What an annoying thing...

Same thing here. Was all good until about an hour ago. Highly irritating...

Try this, worked for me:

Magisk General Support / Discussion
This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases. All information, including troubleshoot guides and notes, are in the Announcement Thread
forum.xda-developers.com
@Displax provided the perfect fix. It worked for many ppl. Check it out. I just flashed the USFN v1.2.0-MOD and it worked.

bzkrtSLAYER said:
Please help Magisk Safetynet is failed
Click to expand...
Click to collapse
THE SAFETYNET ATTESTION API NOW NO LONGER QUERIES CTS PROFILE ON ANDROID DEVICE BUT SUCH ONE STORED ON GOOGLE SERVERS BY OEM/CARRIER.

I followed the embedded video and it works perfectly! Beware, though, that when you clear Play Store data, auto-updating of apps will get enabled, so if you don't want your apps being updated, go to airplane mode and change that setting in the play store before re-connecting.
I also had the issue that at first the play store wouldn't recognize the installed apps and wouldn't offer manual updates for those that are available. Killing and re-starting play store did the trick.

tOz666 said:
Try this, worked for me:
Click to expand...
Click to collapse
This worked for me, albeit it has slowed my phone down quite a bit (at least, for the first 15 minutes or so after booting. It settles down after a while). I'll take it, though.

ttar ttar said:
@Displax provided the perfect fix. It worked for many ppl. Check it out. I just flashed the USFN v1.2.0-MOD and it worked.
Click to expand...
Click to collapse
I suppose that you mean this https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85573473

Didnt work for me
Pixel 5a

Also didn't work for me...

Question google wallet error

Device doesn't meet security requirements

Is your device rooted or do you have adb enabled? If the device is rooted you need to do some things to hide it. If your device is not rooted, maybe check to make sure adb is disabled.

Like the comment above says, if you're rooted with Magisk, install this and it should start working fine after wiping the app.
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Adding on to this just because it's about Google Wallet...
What's the point of Google Wallet when there's Google Pay? The Pixel 7 setup kinda tried to make you download Wallet instead of Pay. Isn't Wallet just a piece of Pay that they took out?

Curiousn00b said:
Like the comment above says, if you're rooted with Magisk, install this and it should start working fine after wiping the app.
Releases · Displax/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - Displax/safetynet-fix
github.com
Adding on to this just because it's about Google Wallet...
What's the point of Google Wallet when there's Google Pay? The Pixel 7 setup kinda tried to make you download Wallet instead of Pay. Isn't Wallet just a piece of Pay that they took out?
Click to expand...
Click to collapse
Wallet is the successor to Pay. They just haven't removed the old app

synesthete said:
Is your device rooted or do you have adb enabled? If the device is rooted you need to do some things to hide it. If your device is not rooted, maybe check to make sure adb is disabled.
Click to expand...
Click to collapse
I am currently rooted I am able to pass safety net I also have hide google wallet in magisk

highgrade said:
Device doesn't meet security requirements
Click to expand...
Click to collapse
Is this when you're trying to pay with Wallet or just setting up the app?
If it's while trying to pay, it might be because you unlocked your phone via face unlock before paying. You might have to unlock with the fingerprint scanner to make sure it works.
Might not be your issue here and I hate to say it but man, the fact that this is an issue at all makes me mad, for any regular user such an error would make absolutely no sense, and you would never understand it unless someone tells you.

highgrade said:
I am currently rooted I am able to pass safety net I also have hide google wallet in magisk
Click to expand...
Click to collapse
I am rooted and wallet is working. Here is how I have set mine up:
Magisk installed:
Zygisk enabled
Enforce Denylist enabled
Denylist blocking: Wallet, Pay, Google Play Services, and some other banking apps.
Install the Safetynet Fix module from this post: https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-2-3-1.4217823/post-87198517
Then install the MagiskHidePropsConfig module. (No need to configure it).
Force quit Wallet and wipe its data.
For quite and wiped data for Google Play Services.
Reboot
Then added card.
Those were the only modules that I needed. Maybe disable anything else you don't need while doing this in case they conflict.
JakeDHS07 said:
Wallet is the successor to Pay. They just haven't removed the old app
Click to expand...
Click to collapse
I think Pay has transitioned to being an app to send money to friends/family/etc like Venmo. I haven't used it since its split with Wallet, though.

Curiousn00b said:
What's the point of Google Wallet when there's Google Pay? The Pixel 7 setup kinda tried to make you download Wallet instead of Pay. Isn't Wallet just a piece of Pay that they took out?
Click to expand...
Click to collapse
JakeDHS07 said:
Wallet is the successor to Pay. They just haven't removed the old app
Click to expand...
Click to collapse
As I understand it, Wallet holds all your "cards" like loyalty cards, gift cards, and transportation passes (metro, train, bus) -- hence "wallet" -- while GPay handles the credit cards for transactions for in-store/shops.
I guess Wallet is the app while GPay might be classified as the process...
Also...
synesthete said:
I think Pay has transitioned to being an app to send money to friends/family/etc like Venmo. I haven't used it since its split with Wallet, though.
Click to expand...
Click to collapse
Yes I noticed that GPay is transitioning to be like Venmo. I haven't used GPay in a long time, but since setting it up on my P7P, it was pushing hard to set things up so I could "easily send/receive payments to my family & friends" (like Venmo, i imagine...)...

simplepinoi177 said:
As I understand it, Wallet holds all your "cards" like loyalty cards, gift cards, and transportation passes (metro, train, bus) -- hence "wallet" -- while GPay handles the credit cards for transactions for in-store/shops.
I guess Wallet is the app while GPay might be classified as the process...
Click to expand...
Click to collapse
Just an FYI, but Wallet is just a part of GPay. What @Curiousn00b had said earlier in this thread is correct. GPay can do everything that Google Wallet does - and more. So therefore, GPay can handle credit cards, debit cards, gift cards, loyalty cards, transit passes, tickets, etc.
The reason why Google has released the Google Wallet app - an app specifically for adding your payment cards, transit cards, loyalty cards, etc - is because a large swarm of people were complaining about GPay being too difficult to use (as the newer features were seemingly confusing to the less tech-knowledgeable folks - which is still around 75-80% of the global population). Google had announced this publicly on a blog post around 1-2 years ago.

highgrade said:
Device doesn't meet security requirements
Click to expand...
Click to collapse
Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
SafetyNet

Hello,
I have a successfully rooted Pixel 7 and the November update.
Magisk modules:
AOSP Mods (Full version)
Call Recorder - SKVALEX
Systemless Hosts
Universal safety Net fix
Zygisk - LSPosed
DenyList contains enabled:
Google Wallet
Google Play Protect service
com.android.systemui.plugin.globalactions.wallet
Play Integrity API Checker
Everything was fine until now, but when I open Wallet today, I get the following information:
"Device doesn't meet security
requirements You can't tap to pay with this device. It may be rooted or running uncertified software. Contact your device manufacturer or visit Google Wallet Help for more info."
My cards were not removed, it seems that the wallet is functional, but this information worries me. This information is not displayed every time when the wallet application is turned on. Everything else works for me (banks, netflix...), I go through safetynet.
I have one more question.
I don't know exactly how these things work...
How about the safetynet? Could it happen that one day GooglePay and Bank apps will stop working for me without an OS update or some other magisk module installation??
If it works for me now, and I don't do an OS update, will it still work for me?
I ask because these applications are very important for my daily work and I can't afford to be surprised by a malfunction at an inopportune moment due to root.
Thank you very much!

efkosk said:
Hello,
I have a successfully rooted Pixel 7 and the November update.
Magisk modules:
AOSP Mods (Full version)
Call Recorder - SKVALEX
Systemless Hosts
Universal safety Net fix
Zygisk - LSPosed
DenyList contains enabled:
Google Wallet
Google Play Protect service
com.android.systemui.plugin.globalactions.wallet
Play Integrity API Checker
Everything was fine until now, but when I open Wallet today, I get the following information:
"Device doesn't meet security
requirements You can't tap to pay with this device. It may be rooted or running uncertified software. Contact your device manufacturer or visit Google Wallet Help for more info."
My cards were not removed, it seems that the wallet is functional, but this information worries me. This information is not displayed every time when the wallet application is turned on. Everything else works for me (banks, netflix...), I go through safetynet.
I have one more question.
I don't know exactly how these things work...
How about the safetynet? Could it happen that one day GooglePay and Bank apps will stop working for me without an OS update or some other magisk module installation??
If it works for me now, and I don't do an OS update, will it still work for me?
I ask because these applications are very important for my daily work and I can't afford to be surprised by a malfunction at an inopportune moment due to root.
Thank you very much!
Click to expand...
Click to collapse
I have Play Store, GPay, and Google Wallet on the DenyList and don't have this error.
And yes, Google can easily decide one day to bypass the DenyList or force hardware attestation at which point you would have to choose between your apps and root. It's been a whack a mole game for awhile now and that's just expected to become worse.

EtherealRemnant said:
I have Play Store, GPay, and Google Wallet on the DenyList and don't have this error.
And yes, Google can easily decide one day to bypass the DenyList or force hardware attestation at which point you would have to choose between your apps and root. It's been a whack a mole game for awhile now and that's just expected to become worse.
Click to expand...
Click to collapse
Thanks!
In the meantime, I cleaned the google play cache storage, added the cards again. I haven't received a bad notification yet
Do I understand correctly that at any time without any action on my part (update app, updateOS) my bank apps, gpay can stop working due to root?

efkosk said:
Thanks!
In the meantime, I cleaned the google play cache storage, added the cards again. I haven't received a bad notification yet
Do I understand correctly that at any time without any action on my part (update app, updateOS) my bank apps, gpay can stop working due to root?
Click to expand...
Click to collapse
If you turn off updates, it's extremely unlikely that it would change, but you're also taking added risk when it comes to exploits and I wouldn't recommend this path.

are we talking about an application or OS update?
If it can stop working for me after the next OS update (via pixelflasher, for example), then that is acceptable for me.
But if it can happen to me after an automatic update of the application via Google Play, it's a problem.
Sorry for possibly stupid questions, I'm trying to understand how it works.
Thank you very much for your help and giving of your time.

efkosk said:
are we talking about an application or OS update?
If it can stop working for me after the next OS update (via pixelflasher, for example), then that is acceptable for me.
But if it can happen to me after an automatic update of the application via Google Play, it's a problem.
Sorry for possibly stupid questions, I'm trying to understand how it works.
Thank you very much for your help and giving of your time.
Click to expand...
Click to collapse
Either can happen. There are ways to detect root that get past our attempts to hide it as it is so an app update can add further detection easily. Just ask my Security Service Federal Credit Union app that won't even open on a rooted phone no matter what I do.

Can I "quickly unroot" it by uninstalling magisk? Does it wipe my data? I want rooted, but I need planB in a crisis situation.
Thx for your reply!
Users with root are not afraid of the situation that they ask for a bill in a restaurant and Gpay won't work for them?

efkosk said:
Can I "quickly unroot" it by uninstalling magisk? Does it wipe my data? I want rooted, but I need planB in a crisis situation.
Thx for your reply!
Users with root are not afraid of the situation that they ask for a bill in a restaurant and Gpay won't work for them?
Click to expand...
Click to collapse
Unfortunately removing root just exposes the unlocked bootloader and GPay won't work with that condition either. It's why I rooted in the first place so I could pass SafetyNet again as Discover is 5% with mobile wallet this quarter.
I carry credit cards with me everywhere I go. It's only recently I've started using tap to pay as it wasn't really available in the Denver area. Even now I can only thing of a couple places that take it - namely the liquor store I go to with my husband lol. Interestingly I went to Dollar Tree yesterday and they have added it.

So if I want to unroot, I will lose data, because after re-locking the bootloader, the data is wiped. I'm right?

efkosk said:
So if I want to unroot, I will lose data, because after re-locking the bootloader, the data is wiped. I'm right?
Click to expand...
Click to collapse
Correct. Honestly I wouldn't say you're at immediate risk of having an issue and that dumping root and all that just for a remote possibility isn't worth it.
You can also turn off automatic app updates for the individual apps in the Play Store. As long as you leave automatic updates on for the rest of your apps, the ones you disable individually will just be sitting there showing updates and you can choose to update them when you're ready.

Question Wallet not working

I'm on a rooted phone and I have the safety net fix v2.3.1 mod v3.
It says your device doesn't support contactless payments. Sometimes says try again. I've tried clearing cache for the wallet app play services and play store, didn't work.
What to do ?

You've the answer in your hand
Wallet is being more strictly about rooted/modded device.
SafetyNet is deprecated and now Google use a new method to check it.

zSyntex said:
You've the answer in your hand
Wallet is being more strictly about rooted/modded device.
SafetyNet is deprecated and now Google use a new method to check it.
Click to expand...
Click to collapse
Is there a way to bypass or is it just not possible at this time(s, until someone finds a way)

TheShinyEnd said:
Is there a way to bypass or is it just not possible at this time(s, until someone finds a way)
Click to expand...
Click to collapse
Not for the moment. Every app that use the new method couldn't work with that bypass

zSyntex said:
Not for the moment. Every app that use the new method couldn't work with that bypass
Click to expand...
Click to collapse
Will downgrading the wallet app work?

TheShinyEnd said:
Will downgrading the wallet app work?
Click to expand...
Click to collapse
No, it's server side.

zSyntex said:
No, it's server side.
Click to expand...
Click to collapse
Okay, thanks for the information.

TheShinyEnd said:
I'm on a rooted phone and I have the safety net fix v2.3.1 mod v3.
It says your device doesn't support contactless payments. Sometimes says try again. I've tried clearing cache for the wallet app play services and play store, didn't work.
What to do ?
Click to expand...
Click to collapse
zSyntex might be incorrect.
USNF version you are using is outdated. Also, for the Pixel 6 & 7, using Displax's Mod is more successful (I've hyperlinked to the post where you can get information to it in the quote below;post 3223).
In any case, I suggest you do what I have quoted below... I am able to get contactless payments working with the latest Wallet version on the March firmware doing the method below...
simplepinoi177 said:
you might want to check out Post #3223, for Pixel 6 & Pixel 7 particularly, that mod works out real well...
And of course the obligatory clear cache & data of Google Play Protect, Google Framework, Google Play Services, Wallet, Gpay, all these apps' ticks in their respective sub-menu is ticked in Zygisk DenyList, and be sure to restart (personal experience; I did all that and couldn't add card, but after restart I could). Also, I passed safetynet and successfully added card, but had to call the banks on two cards to get it working without error at a store...
Click to expand...
Click to collapse

simplepinoi177 said:
zSyntex might be incorrect.
USNF version you are using is outdated. Also, for the Pixel 6 & 7, using Displax's Mod is more successful (I've hyperlinked to the post where you can get information to it in the quote below;post 3223).
In any case, I suggest you do what I have quoted below... I am able to get contactless payments working with the latest Wallet version on the March firmware doing the method below...
Click to expand...
Click to collapse
Okay.. I'll try this method, thanks for the update.

simplepinoi177 said:
zSyntex might be incorrect.
USNF version you are using is outdated. Also, for the Pixel 6 & 7, using Displax's Mod is more successful (I've hyperlinked to the post where you can get information to it in the quote below;post 3223).
In any case, I suggest you do what I have quoted below... I am able to get contactless payments working with the latest Wallet version on the March firmware doing the method below...
Click to expand...
Click to collapse
I'm not wrong. Google deprecated SafetyNet officially, check its Source Blog.
I don't know if dev updated the patcher
Some device need to patch the bootloader while others not

Yeah, I see.. they've made a post - they are going to switch to "Play Integrity API" from their "SafetyNet Attestation API" and will fully enforce it in June of 2024.
Discontinuing the SafetyNet Attestation API | Android Developers
developer.android.com

My wallet still works...

zSyntex said:
Not for the moment. Every app that use the new method couldn't work with that bypass
Click to expand...
Click to collapse
zSyntex said:
I'm not wrong. Google deprecated SafetyNet officially, check its Source Blog.
I don't know if dev updated the patcher
Some device need to patch the bootloader while others not
Click to expand...
Click to collapse
Yes, it's been a long time coming that Google has depreciated SafetyNet. Most apps don't even employ that protocol in "stability" checks. But the devs of UniversalSafetyNetFix had long anticipated that as well. I believe they only kept the name because that is what everyone knows it as; it's not to mean that it only applies to SafetyNet. This "bypass"(USNF) does still work.
TheShinyEnd said:
Yeah, I see.. they've made a post - they are going to switch to "Play Integrity API" from their "SafetyNet Attestation API" and will fully enforce it in June of 2024.
Discontinuing the SafetyNet Attestation API | Android Developers
developer.android.com
Click to expand...
Click to collapse
Yes, this is true, but as I've just stated, it has been a long time coming and has been anticipated by the devs for almost as long.
That is why, in THIS DEFACTO CENTRAL THREAD on everything outside of stock (by roirraW "edor" ehT) actually presents using the USNF Mod (that works particularly with our Pixel 6 & 7's in spoofing not just SafetyNet but Play Integrity API) but also strongly suggests using the "Play Integrity API Checker" app after implementing the mod/fix to make sure you pass enough of the checks (everything but STRONG_INTEGRITY; is explained in the thread why that isn't to be worried about)! I mean, doing what was directed in the thread and what I had quoted before, I'm like @gpvechhi and my contactless payments in Wallet work, even though i am rooted -- only using USNF Mod and Zygisk DenyList...

TheShinyEnd said:
I'm on a rooted phone and I have the safety net fix v2.3.1 mod v3.
It says your device doesn't support contactless payments. Sometimes says try again. I've tried clearing cache for the wallet app play services and play store, didn't work.
What to do ?
Click to expand...
Click to collapse
Try with USNF v2.4.0 mod v1.2 (Displax).

So I tried to use my credit card on my phone, says your device doesn't support contactless payments. the issue still persists, by any chance I need to re-add the wallet's information? - Already have it saved.
YASNAC - Passing
Play Integrity - Passing
I've resetted cache for all the play related apps and services, wallet as well, still nothing.
Sometimes, I do notice that the GMS(Google Play Services), com.google.android.gms, Is turned off in configure-deny list of magisk, I have it turned on, but probably after a phone restart or something related, it turns off for some reason.
Is GMS in the enforced deny list a necessity ?
And do I need to re-add my wallet information ?

TheShinyEnd said:
So I tried to use my credit card on my phone, says your device doesn't support contactless payments. the issue still persists, by any chance I need to re-add the wallet's information?
Click to expand...
Click to collapse
I think this might be another issue than root detection...
I spoke a little about it at the bottom of my quoted post:
simplepinoi177 said:
you might want to check out Post #3223, for Pixel 6 & Pixel 7 particularly, that mod works out real well...
And of course the obligatory clear cache & data of Google Play Protect, Google Framework, Google Play Services, Wallet, Gpay, all these apps' ticks in their respective sub-menu is ticked in Zygisk DenyList, and be sure to restart (personal experience; I did all that and couldn't add card, but after restart I could). Also, I passed safetynet and successfully added card, but had to call the banks on two cards to get it working without error at a store...
Click to expand...
Click to collapse
I recall running into that "doesn't support contactless payments" because it needed to be activated/enabled in the bank's system -- I had to call the bank to confirm things and get it working. This may be the case here.
TheShinyEnd said:
Sometimes, I do notice that the GMS(Google Play Services), com.google.android.gms, Is turned off in configure-deny list of magisk, I have it turned on, but probably after a phone restart or something related, it turns off for some reason.
Is GMS in the enforced deny list a necessity ?
And do I need to re-add my wallet information ?
Click to expand...
Click to collapse
So, if you are using USNF Displax Mod (which I linked to in the quote as Post #3223 and Fishawy suggested), the mod takes care of a lot of the GMS things under the hood to bypass the root checks that, as a result/side-effect, GMS and some other Google services ends up not staying "ticked" in the deny list after a reboot.
TheShinyEnd said:
...by any chance I need to re-add the wallet's information? - Already have it saved.
YASNAC - Passing
Play Integrity - Passing
I've resetted cache for all the play related apps and services, wallet as well, still nothing.
Click to expand...
Click to collapse
You should try again what I quoted; if all done correctly, you would need to re-add the cards and wallet's information again -- so it seems that you may have not since you mention needing to still "need to re-add". Also, you can't just reset the cache, but you must clear data as well (as directed in the quote I left).
Fishawy said:
Try with USNF v2.4.0 mod v1.2 (Displax).
Click to expand...
Click to collapse
It really is most important you try what I quoted and what Fishawy suggested -- it's most likely why things aren't working for you as they are working for most of us.
TheShinyEnd said:
Okay.. I'll try this method, thanks for the update.
Click to expand...
Click to collapse
You stated this, but have yet to indicate if you implemented the Displax Mod instead of the regular USNF.
At worst, if you are implementing Displax's mod and passing everything, and have done the steps I quoted before (particularly ticking sub-selections), you may need to completely re-initialize Google Services and Wallet, which I found the best directions on how to do quoted below...
V0latyle said:
Given that everything was working prior, it sounds like Shamiko won't help in this particular circumstance as this isn't a attestation/certification issue.
...since this happened after clearing data for Google Play Services (which removes your Google account) you might have to basically start over with apps that require Google sign in. This will be a pain in the butt, but may be worth a try:
Manually remove your Google account
Force stop and clear data for Google Play Services, [Google Frameworks, Google Play Protect,] GPay, Play Store, and Wallet
Reboot
Add your Google account
Open GPay, Play Store, and Wallet, and set everything back up
Reboot again
Basically, clearing data for Play Services has ripple effects that can cause problem in dependent apps, since they use the GMS suite to access your Google account data
Click to expand...
Click to collapse

simplepinoi177 said:
I think this might be another issue than root detection...
I spoke a little about it at the bottom of my quoted post:
I recall running into that "doesn't support contactless payments" because it needed to be activated/enabled in the bank's system -- I had to call the bank to confirm things and get it working. This may be the case here.
So, if you are using USNF Displax Mod (which I linked to in the quote as Post #3223 and Fishawy suggested), the mod takes care of a lot of the GMS things under the hood to bypass the root checks that, as a result/side-effect, GMS and some other Google services ends up not staying "ticked" in the deny list after a reboot.
You should try again what I quoted; if all done correctly, you would need to re-add the cards and wallet's information again -- so it seems that you may have not since you mention needing to still "need to re-add". Also, you can't just reset the cache, but you must clear data as well (as directed in the quote I left).
It really is most important you try what I quoted and what Fishawy suggested -- it's most likely why things aren't working for you as they are working for most of us.
You stated this, but have yet to indicate if you implemented the Displax Mod instead of the regular USNF.
At worst, if you are implementing Displax's mod and passing everything, and have done the steps I quoted before (particularly ticking sub-selections), you may need to completely re-initialize Google Services and Wallet, which I found the best directions on how to do quoted below...
Click to expand...
Click to collapse
I am indeed using "USNF v2.4.0 Mod v1.2 (Displax)", resetted data & cache.. I'll re-add the cards see how that goes.
Thank you very much for the help, much appreciated !

TheShinyEnd said:
I am indeed using "USNF v2.4.0 Mod v1.2 (Displax)", resetted data & cache.. I'll re-add the cards see how that goes.
Thank you very much for the help, much appreciated !
Click to expand...
Click to collapse
Resetting the data & cache for every single Google app in the quoted steps (there are 6) should remove all the cards in the Wallet app anyways...so that'd be the next step regardless...
Good luck!