yashsingh1/xdaforums huggingface dataset:
[Magisk] Lord Sithek:
Up to Android 10 there are two Xposed modules which I know:

- LockscreenDisabler for AOSP roms (https://repo.xposed.info/module/com.lr.keyguarddisabler2)

- CustoMIUIzer for MIUI roms (https://xdaforums.com/t/mod-xposed-3-2-1-customiuizer-customize-your-miui-rom.3910732/)

Unfortunately, as far as I know and remember, they both dont work since A11. There are some forks of CustoMIUIzer which work on A11+, but not with all features, and Im afraid this particulare one doesnt
[Magisk] rpmccormick:
Thanks for the replies. Consider it a request. A non-rooted device is a requirement for all payment apps as well, yet people made a workaround for that. I am sure it must be possible to make Google think I have a lock-screen while allowing me to use and even reboot my device without having to enter a code.

How about a module that auto-enters a given pin for me whenever the lock screen is shown? ...it must be possible, not "end of discussion".
[Magisk] Lord Sithek:
Yes, this is definitely possible. You can use Tasker app with AutoInput plugin: https://play.google.com/store/apps/details?id=com.joaomgcd.autoinput&hl=pl&gl=US

You'll find many guides in the web on how to set it up
[Magisk] rpmccormick:
Thanks for the suggestion. Can you confirm it can function on the lock-screen and detect the lock-screen to start auto-inputting? That would be an awesome solution... I will look in to it even if you don't confirm. Totally thanks if it works!

I also dove in to the previous link saying to extend the lock timeout to be like 24 hours instead of 5 seconds. That's not a bad method.

I also thought of maybe making SmartLock think I am always home so it never locks.

Tasker and Auto-Input would be best if it can actually work on the lock-screen. That way it will unlock after a reboot as well.

<rant>

Unless you are in the habit of losing your phone or want to keep certain people from looking at it, I challenge everyone to set the lock-screen to Swipe only for a week. Then go back to having to unlock it however you like, and it is my bet you will soon be frustrated with unlocking as well. My Windows auto logs in. My web and app logins are auto filled. Humans should not be forced to type codes over and over again. We made computers to automate things, why can't authentication be one of them, especially on machines that only one person ever uses.

If I do ever lose my phone, I will notice quickly and remote-wipe through Google (likely before anyone has had time to do anything with it).

It is absolutely ridiculous that I can't use built-in VPN to my home, see my saved passwords, or use PhonePay apps without enabling a lock-screen... especially the passwords one, as any thief could just set a lock code, then see your passwords... what is the point Google???

Hopefully the Tasker method solves this long-time issue of mine, and then I can move on to making my phone allow me to take a gosh-darn screen-shot any F-ing time I ask it to. I get so angry when I have to borrow some ones phone to take a picture of my phone. Ridiculousness! I can still take a screen-shot of any website on my PC (for now... I hope Google and M$ aren't reading this and getting any bad ideas).

</rant>
[Magisk] pndwal:
Very simple pattern? ... Mines not much more than a swipe! 😜

🤔 Oh! ... Please could you explain how this can be done?... I may have a false sense of security!?!... 😟

*Nice new scrabble word - just learned it's real! Thanks. PW
[Magisk] rpmccormick:
I have used a simple "not much more than a swipe" pattern before. It is very annoying when I get it wrong, especially while driving or something. Having a lock is unsafe. The times I really need to quickly check my phone are always the times I can't swipe the dots good enough for it. Same thing with fingerprint, usually not an issue, but sometimes it is, and always at the worst of times. I have never tried face unlock. Plus all of these require a code after reboot, and if you flash a lot it becomes an annoyance.

Explanation: What I was saying was if you don't have a lock, then Chrome won't let you see saved passwords until you add a lock. I often need to set a code, see the password I need, then unset the code. This is dumb. Anyone who stole my phone could do the same. Why would Google force me to do that every time I need to see a saved password for use on another device? It does nothing to enhance security.
[Magisk] rpmccormick:
Well, I got GPay working with Universal SaftyNet and Zigote. Unfortunately I have needed to enter my 0000 pin many times, due to reboots. I don't understand how y'all just live with that... waste of my life and I want it gone!

PS: No, tasker can't enter 0000 for me after a reboot, even with AutoInput. I pray someone will invent a solution.
[Magisk] pndwal:
Sorry, what's unsafe?? - If you're caught touching the phone while driving where I am, a lock pattern is the least of your worries...

At least do others a favour; pull over, park up, then unlock phone (or don't) and then do phone fiddling... 😮

Oh! Now I see what your saying...

It does enhance security as it ensures users have lock set to use G Pay, access saved passwords etc, etc, which generally means a thief would have to bypass cryptography to access any data on device, let alone passwords, bank funds etc... Of COURSE it's dumb to just un-set the code... That's not the intention!!!

That's a bit like removing your seatbelt once you reach the open road... de-activating an over-speed warning buzzer.... texting while driving... parachuting with no reserve chute... taking the guard off an angle-grinder... in order to fit a table-saw blade for hand trimming.... or skull penetration... whichever comes first!

Not to put too fine a point on it, you're trying to defeat an effective built-in safety mechanism on an already compromised device!...

... and I do understand that we are all actually 'subverting Google's security model' by using available mods here (only possible because they don't happen to view 'Magisk community' as nefarious but rather as 'white hat' combined with the fact that they know other cryptography and safeguards are still effectively protecting all concerned parties including banks).

I've also modified the 135° guard on my angle grinder by cutting it down to 85° in order to penetrate into a 90° folded-steel corner. (I've thus overcome a restriction that previously limited the effectiveness of this device)... But I wouldn't consider removing the guard entirely to cut the steel... even if it is tempting to cut corners! 😂 PW
[Magisk] pndwal:
Universal SafetyNet Fix

Zygisk?

Reboots not needed except for initial USNF setup... Just put G Pay in denylist, check you have Play Protect Device is certified in Play Store (clear Play Store and possibly Play Services data if not to fix), clear G Pay data and open it... PW
[Magisk] 73sydney:
I refer you once more and hopefully only once more to this:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-87163153

I have larger things in my world to worry about and shake my fist at than entering a blooming lockscreen password, which is there for security

Feel free to let big bad Google know theyre ruining your life in their forums

I bet you yell at kids to get off your lawn and keep their balls too
[Magisk] rpmccormick:
I want to say thank you to Lord Sithek for trying to help and providing many links to threads about the issue and workarounds... I am not the only one who hates entering a code. Many have done it for Android 7, and some for 8 and 9. It seems 10 and 11 have blocked most workarounds, which is sad.

Also thanks to PW. We have different views, but the discussion is valid and fun. I have taken the guards off of all my saws and have not lost a finger yet. I have also changed hundreds of lights, outlets, and switches and seldom resort to flipping any breakers. I understand the need for security, please also understand some peoples need for instant access when security is not needed.

73sydney... It is not wrong of me to ask and request that a new workaround be developed. Just cause you like entering the same code 1000's of times in your life doesn't mean I have to. I love it when kids play on my lawn. I hate when companies dictate how I get to use my own devices.
[Magisk] pndwal:
👍

Our views might be much the same in fact... But we gotta get real and accommodate the views of other parties...

Yeah... If you're gonna risk losing digits, at least ensure you have fun doing it!

Wow! ... Maximising the fun?

... 'Yet' being the operative word. 😛

Same... But don't do it in the wet, without RCD's, without checking footwear or without cognisance of the path current will take where opposite hand contacts an earth conductor... Or with a supervisor watching...(We may only get to make a mistake once.)

Sure... But it's never not needed in the eyes of the app Devs and cyber-crime researchers... so depends from who's perspective...

👍

But they hate it when you dictate terms for running their code! 🤪 ...They are another party with interests in your device use and code on your device...

Modern law recognises that code as their (intellectual) property, so they legitimately get to dictate how it's used on your device!... Your options are outwit them or refrain from using it...

But don't hate the rules... They actually facilitate this symbiosis... In this sense, banks, Google etc are your benefactors!... And you signed up for their help ... somewhere, sometime! PW
[Magisk] rpmccormick:
What are you talking about bro?

My phone has the option to set a lock screen to None or to Swipe. This is for login to my device, and doesn't need to have anything to do with encryption or anything else (I realize it does, but that is a flaw... it should be a UI setting only).

While your statement may make some sense for purchases, it makes zero sense for connecting to my home VPN or for looking at my stored passwords. As I have said before, my company does not require me to keep my physical credit cards under any sort of lock. Some one is just as likely to be able to steal my wallet and tap-to-pay as they are to steal my phone and tap-to-pay. They have no right to disable advertised functionality because I choose one of the provided options in my settings for login.
[Magisk] rpmccormick:
What if they decided you had to use a super small font to use your bank apps, so someone could not as easily look over your shoulder? Is that their right because they wrote the code? What if they forced you to hold up your drivers license to your camera before you pay? These are just as arbitrary. I am happy to enter a code before paying. I am not happy to be forced to enter a code every time I turn on my phone, about 50+ times each day, in order to ever be able to make a payment. You should not be happy about that either. That is the whole point of this forum and rooting... to do what we want with our UI.
[Magisk] 73sydney:
This has widely veered off into ideology

And i cant believe im saying this..... but can we get back on topic ?
[Magisk] pndwal:
That's just timing etc, before password/security kicks in...

... and who mentioned encryption?... I did mention cryptography in earlier post... Of course these have everything to do with password/security, which is what the apps detect is enabled or not...

🤔

If you don't have it at home, you're hardly going to enable it (or remember to) whenever you go out!... They aren't stupid!

Nah... They're happy if you leave them on your dash with the car window down for easy/quick access... Good point!

But banks in many places will cover you/reimburse funds in these circumstances... So they naturally want to minimise possible fraud with new methods, and may not reimburse if (cryptographic) lock requirement is bypassed... Or may not offer mobile solutions w/o lock security on any platform... And Android security is already notoriously poor compared to iOS...

... That's where you'd be wrong! ... and prerequisites are most likely also advised somewhere...

Of course...

Doesn't worry me to enter pattern or touch fingerprint sensor, and I do... 😛

This one's to use G Pay!

... within reason...

As I said, you own device, Google/banks own code... All have rights... Users can try their luck...

Sorry mate!...

But ideology (not to mention common sense for living in a technologically advanced, fraud-filled age) does enter into G Pay / Magisk use/discussion...

And it's such fun too! ... Like noisykids playing in the park opposite your tenement... 😜

Best regards AM... PW
[Magisk] rpmccormick:
73: I will respect the forum and take my discussion with PW to PM. Just know that your "there is no workaround, end of discussion" was the beginning of this ideological argument.

On Topic: We have used workarounds in the past, and I hope someone will invent a work around in the future, that allows me to use GPay with whatever security settings I wish, be it root (very dangerous due to possible remote execution) or no-password/auto-login (should not be dangerous at all if my phone is physically secure). Please let me know if some kind dev will afford me this basic freedom.
[Magisk] 73sydney:
Some days i just think you want to revive the quote pyramids once seen in dodgy old forum software :)

No one can have GPay without a screen lock/PIN code unless The Bear says so....and he's much like Thatcher, not for the turning...
[Magisk] BigBoss0327:
Hello all,

Just chiming in for the quarterly google pay update (now google wallet) = your phone is rooted and can't add card / conduct contactless payment help thread.

Are there any fixes out or shall I check back in a week or two?
[Magisk] pndwal:
Thanks... Just updated to new Wallet... No issues so far for me; just added another card too... Config still shows 'Google Pay', but guess they'll get round to updating nomenclature...

Perhaps you could elaborate on issue you face & when it occurs (I haven't tried actual contactless payment w/ new Wallet; will soon 😜)... Also, some setup details... PW
[Magisk] xdxita:
Updated to the new wallet app today then made 2 payments on the third it failed saying that the phone is insecure. Checked deny list, safety net, universal safety net fix, cleared play services, store and wallet data, restarted the phone and didn't worked.
[Magisk] patrickneil:
Thanks, at least I'm not alone here! Google Pay also stopped working for me today and is detecting root for the first time in a year or so of using USNF, which is the latest, 2.3.1. I'm passing Safety Net, Play Store is certified, but contactless payments aren't working. I also get a new bug if I clear Play Services data where Google Pay just says it "is updating now, so you won't be able to access the app." My only way out of that is to uninstall GPay and install an old version, but that detects root too. Here's some of screenshots of what I'm seeing.
[Magisk] glennza:
Same for me, as of this morning. I updated from Pay to Wallet a couple of days ago. Everything was working. Now, I'm passing Safety Net, Play Store is certified, but contactless payments aren't working.

Must be a new Play Services update? Hope there'a a way around it.

I'm on latest Magisk Canary, USNF 2.3.1 and Shamiko 0.5.1
[Magisk] FloofyPeachy:
Same, right here. I have a Google Pixel 4a with 5G. This was working before, and even SafetyNet passes, but no contactless?

Universal Safety Net Fix 2.3.1, Magisk 24.3, DenyList as well.

Does anyone have any idea on why this is happening now and not before?
[Magisk] g0t.milkk:
Same as many here : Updated to Wallet yesterday, everything was fine, this morning contactless payment is disabled.

Pixel 4a, stock Android 12 + June 2022 security update, Magisk 25.1 + USF v2.3.1 + Zygisk enabled for Wallet
[Magisk] g0t.milkk:
Wait... I've updated to Magisk 25.2 and it seem that contactless payment is enabled again ? I don't have a way to check IRL, and I don't see anything related to Wallet in Magisk's 25.2 release note...
[Magisk] spiou:
It's probably the Google play services update.

On my device, Google Pay was not updated to Wallet and I received a notification saying I was rooted. I checked the version of play services and I saw that it was updated seemlessly the 19th July.

I don't know if it's related, but now I have forced the update of the play store, and it seems that's it's ok again (Google Pay say now all is ok). Can someone confirm updating the play store solve the issue ?

Edit :

I still have the notification of rooted phone, so the update of the play store does not solve the issue.(Strangely it not appears at every launch of Pay).
[Magisk] stereo007:
I have three devices in the family. PIXEL 4a. On two of them it works without problems. With one I get the error. "google pay is updating at the moment". Version 2.150.461926512

I have Magisk 25.2 + Universal Safety Net Fix +DenyList. All settings are identical on all of them.
[Magisk] pndwal:
You folk with unending "updating" / contactless payments disabled - some tips / clues here:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-86981221

... And if you then have 'Activity' snowing nothing 😢, this:

https://xdaforums.com/t/discussion-google-pay-magisk-discussion-thread.3906703/post-86991951

Hope it helps... 🙃 PW
[Magisk] alangt:
Sorry, but no... it doesn't work for me. But I have a guess... when I do that and after installing the Pay app again (strangely before the process it was "wallet" and now it's "pay" again), I realized that the app was gone from the Denylist in magisk. So, I had to check it again, but that makes me think if the app was already open in backgroud and able to detect the root, so maybe I'm trapped on a loop? I wonder if there's any way to enforce denylist to all apps by default and then remove the ones I want it to see the root. My device is an LG G7 G710EM w/ Android 10 and Magisk 25.2 + Zygisk, SafetyNet passing without issues.
[Magisk] aricooperdavis:
Note that rather than having to wait for a pop-up at launch you can manually check whether Google Wallet is happy with your phone by:

-> Tap your profile icon

-> Tap "Contactless setup"

The second item with the shield icon tells you whether your phone meets security requirements.
[Magisk] CSX321:
Was gms.unstable still supposed to be checked in denylist? It wasn't when I looked just now.
[Magisk] GabbyWC:
If you use the Universal SafetyNet Fix module, Google Play Services is supposed to be unchecked in the DenyList.
[Magisk] g0t.milkk:
That's the strange thing I have now : Sometime when I launch Wallet I've got a message saying my phone doesn't met the requirement, yet when I check in "Contactless setup" everything is OK, and on my lockscreen I still have the little "Wallet" icon I can click and "supposedly" use contactless pay... Again, didn't had the occasion to check if it's working IRL yet
[Magisk] rodken:
Within the 'Google Wallet' app

-- Tap your icon

-- Tap 'Tap to pay setup'

-- Next screen shows confirmation on whether your device can be used or not
[Magisk] aricooperdavis:
Interesting, our Google Wallet apps have different UI's, as mine still says "Contactless setup". Mine is version 2.150.461926512
[Magisk] Gleniu:
Here we go again... I'm getting too old for this :D Probably some new checks by Google, maybe they now check if the SafetyNet evaluation is basic or hardware backed. Maybe they have some list of devices that should have hardware backed evaluation and if it's basic, then Google knows that the phone is rooted.

Redmi Note 10 Pro, newest Magisk, newest SafetyNet fix, NFC payments were working fine before updating to the new Google Wallet.
[Magisk] swour:
This message popped up several times only to disappear again. I was able to complete a contactless transaction despite this warning.

Either the new version of the Wallet app introduced a bug that will affect all users whether the phone is modified or not, or the verification checks will eventually fail permanently. Which would mean having to find a new solution to the problem.

So far it appears to be working.
[Magisk] Lada333:
Same here. I updated to Google Wallet this morning. Payments were working fine for a while, until they weren't. Was able to tap in at the London underground, but was unable to tap out like 20 minutes later.
[Magisk] rodken:
At least - you can always revert back to GPay until further notice.
[Magisk] spiou:
Same thing here : the popup appears sometimes, but in the Contactless Page all is fine.
[Magisk] alangt:
I always had Google Pay on my phone, today Google changed to the Wallet app (there are quite a lot of news on the web about this), but then after I came with the root issue for contactless pay, I started "messing" with the app/magisk, etc. Then after I reinstalled and wiped all data, there it comes the old Google Pay icon on my phone again, with all the old Pay interface, even though the Play Store now shows "Wallet". I have exact the same version on my phone 2.150.461926512.
[Magisk] Gleniu:
Unfortunately, that doesn't work for me. I believe there are some new checks on Google's side.
[Magisk] _Raziel666:
I got an email and update notification for the new Google Wallet.

I updated but never saw its interface. The app was trying to update Google Services but I got a message that something went wrong. I even tried cleaning the data from Play Store/Wallet/Services and trying again but nothing - now I get stuck at checking info after selecting Google account.

I even tried uninstalling and going back to an older version of Google Pay but some internal check doesn't allow it.

Hopefully a solution will be found sooner rather than later.

Wonder if it's a problem with root or the custom ROM altogether, ie. if I disable root will it work?
[Magisk] rodken:
Interesting - I was able to reinstall GPay v.157.1.3 without any issues.

-- Any cards that were on the server were restored without any error messages regarding contactless setup
[Magisk] rodken:
Which version of the old GPay were you trying to install?
[Magisk] _Raziel666:
The last before the current (2.143.460223562)
[Magisk] Gleniu:
Hmm, I will try to do more in the evening. I'm surprised by the version you are using - 157.1.3, because I found version 2.43 on Apkmirror. As you can see it is totally different versioning.
[Magisk] rodken:
Try v.2.100.275591585
[Magisk] ShadT75:
I believe it must be something else than just Goggle Pay -> Goggle Wallet update. My phone got updated over the night and I also cannot use contactless payments now. But my app is still Google Pay, it was not updated to Wallet. Yesterday it was working, now doesn't. Most probably the issue came with Google Play Services update. I've updated Magisk and Magisk App to latest version, updated SafetyNet fix, installed latest Shamiko module, but no luck here. Safety net check passes OK, but Google Pay app keeps showing message that Phone is rooted and payment are not possible.
[Magisk] rodken:
Incidentally, which modules do you have installed on your device?
[Magisk] rodken:
What has worked for me in the past

-- Check out this project to circumvent signature verification when installing an older version.
[Magisk] _Raziel666:
There are various versions of Google Pay/Wallet. The 157.1.3 was one working only in USA/India and somewhere else.
[Magisk] alagga:
I tried some older Version, also this one and I'm not able to add my cards anymore. It gives the same error as on newest Google Wallet..
[Magisk] Fukel:
my ass old Galaxy S7 has been working for a long time with Google Pay / Magisk , I never update the apps on it. Suddenly have notfication no contactless through Google Pay allowed.
[Magisk] Gleniu:
That's a list of my modules. Sorry for screenshot, I'm on mobile right now and it's just quicker 🙂
[Magisk] rodken:
I am assuming that you already followed the old rhetoric

-- Enter Airplane Mode

-- Clear cache and data of Gpay/Wallet > uninstall Wallet and/or Gpay

-- Clear cache and data of Play Services

-- Clear cache and data of Play Store

-- Restart device [cross your fingers and toes]
[Magisk] rodken:
Experiment with different previous versions of USNF.
[Magisk] Lada333:
Did try immediately, did not work for me
[Magisk] rodken:
FWIW- this is my setup [to name a few].