yashsingh1/xdaforums huggingface dataset:
[Magisk] pndwal:
@HippoMan,

Thanks.

FWIW, since I rooted my RN8T, I haven't needed SQLite fix in any form; G Pay simply works with MagiskHide, and I've not had any issues since.

https://xdaforums.com/t/working-mag...s-of-gms-17-1-22-on-pie.3929950/post-84037881

This was certainly not the case a year ago, and I believe something has changed in G Pay configuration as others also report success with proper MagiskHide settings only. I therefore really can't comment on whether to add data clearing for Google Play Services etc to SQLite Fix module...

I'm wondering if having the fix now can actually cause issues, but it does seem more likely that some manual changes made by @HippoMan are the likely culprit on reflection, especially as we haven't heard of this particular issue before now.

For me, treating G Pay like many Bank apps that use only basic SafetyNet checking works. - ie have full SafetyNet pass and playprotect certification, install app, toggle on to hide root from it in MagiskHide list, reboot, clear it's data (apparently clearing Google Play Services data at the same time can fix some issues too), setup (cards etc), --> done!

For me (in Sydney), this method is all I need for my BankWest, Google Pay, mymacca's, Opal Travel, and WhatsApp (hides warning) apps... I currently have no need even to hide Magisk app!

PS Thanks for Payload app!... I'll check that out some time. 👍 PW
[Magisk] 73sydney:
You're blooming special, so of course it works for you with little to no fiddling :)

But what do i do for the rest of humanity and their quirks? :)

Also stop giving money to that cancerous American company with the creepy clown

One of these days ill have to track you down and buy you a coffee - was going to do a Marrickville Metro run tomorrow but going to Bondi Junction Woolies instead s need to pick up my repaired Galaxy Buds+ from JB Hifi (only waited 3 weeks for them) - miss my buds. Be nice to have the entire family together tomorrow, Pixel 2 XL, Active 2 Watch and Buds+. I may like my wearables a bit too much :)
[Magisk] HippoMan:
With regard to my issue of GPay forgetting cards and payment methods, it turns out that my /cache directory is not empty, after all. I might gave been looking at the wrong directory before.

Among other things, it contains a payfixfirstrun.log file, but that file is essentially empty: it's one byte long, and it only contains either a newline or something unprintable.

Also, it turns out that the xXx_NoLimits software that I mentioned doesn't seem to do anything to any caches, and so it isn't likely to be the cause of GPay eventually forgetting cards and payment methods on my device.

So, I still don't know what is going on with this issue. I'll keep investigating.
[Magisk] 73sydney:
Glad that you have the log file, meanwhile i found out why its blank, last update the pipes in service.sh that output the lines seems to have gotten mangled in the upload?

In any event i have fixed it and uploaded a new module zip, rather than install all over again, you can if you like just extract service.sh form the zip and replace it in /data/adb/modules/73sydney.gpay and reboot to see if it will tell you anything
[Magisk] 73sydney:
Updates to Gpay SQLite Fix Module

v2.4 9/3/2021

Changes to service.sh:

Fixed broken/mangled pipes that left the log file blank - dont ask me why

If you need logging (only useful if youre having an issue and want to troubleshoot) you can choose to install the new zip, or extract the service.sh from the zip and overwrite the one in /data/adb/modules/73sydney.gpay
[Magisk] HippoMan:
I installed the new module and rebooted, and now, /cache/payfixfirstrun.log is no longer empty.

Here's what it contains ...

System boot completed

/system/bin/chmod....accessible

/data/data/com.google.android.gms/databases/dg.db....accessible

[titanium] SQLite3 binary found in: /data/data/com.keramidas.TitaniumBackup/files

Google Pay stopped successfully

Chmod 777 command completed successfully
Permissions reported as: 777

SQLite3 command completed successfully

Chmod 440 command completed successfully
Permissions reported as: 440

Just keep in mind that although the module did what it is supposed to do, this doesn't seem to address my issue, which is ...

even though SafetNet does pass (and has been passing for a long time). and ...

even though GPay can run, and ...

even though I can install and enable cards and payment methods in GPay, the problem remains that ...

after some time passes, these cards and payment methods disappear from GPay

In other words, even though my system gets set up to enable proper functioning of GPay, something changes my system after a while so that GPay no longer functions properly.
[Magisk] 73sydney:
So, glad the module is definitely doing its thing (even though we were sure it was), and beyond checking for known conflicting apps or speedup or cache altering ones, i have no further suggestions...

Nothing normal within Android should be wiping that data, has to be a 3rd party app or process
[Magisk] HippoMan:
Yes, and as I mentioned, that is what I am investigating.

Thank you for all your help!
[Magisk] HippoMan:
PS: Do you know where GPay actually stores these payment methods? On the device itself? Somewhere in Google's cloud? ... ???
[Magisk] HippoMan:
Further follow-up concerning my problem with GPay payment methods eventually disappearing ...

I now am starting to think that the problem might be related to my choice of ROM on my device.

I have an old phone with a broken screen of the same type as the one I normally use: OnePlus 7 Pro (GM-1917). I use it for testing things. My normally utilized phone is set up with stock OOS 10.3.8, but lately I have been trying the Resurrection Remix ROM on the testing phone (the RROS-Q-8.6.7-20210213-guacamole-Official.zip version of that ROM).

Today I set up the testing phone to run most of the same software that I am running on the normal phone, and that includes Magisk 22.0, and Riru/EdXosed, as well as the following apps ...

Tasker

AutoNotification

AutoApps

AutoTools

AutoInput

SecureSettings

TitaniumBackup

PayPal

GPay

SafetyNet passes after I have done the appropriate Module Hide actions in Magisk.

I then enabled PayPal as a GPay payment method on the testing phone. So far,. this payment method has not disappeared, despite my having waiting a long time as well has having done a number of reboots. And installing GPay.SQLite.Fix.v2.4.zip isn't even necessary.

So now, I'm starting to wonder if there might something about stock OnePlus ROMs such as OOS 10.3.8 running in a rooted Magisk environment which somehow causes GPay payment methods to disappear after a while. I had this same GPay problem under OOS 10.3.7 and maybe even one or two earlier versions. And this happened on these stock OS's with earlier Magisk versions, as well.

This is only a tentative, preliminary finding. I will do more testing and investigation, and I'll report my results.
[Magisk] pndwal:
Nah. Somethings changed, that's why it works.

You've done heaps, 'n you're already famous as the mod Dev for GPay, but nothings static; sometimes we're forced to embrace change.

I never know where I'll be working each day, but like my AM coffee at Vesbar... n re. Maccas' app, I've actually only used it once, just to see if it works on rooted device since so many complain it detects root. 😳

Hope to spot you sometime by your limp in a Woolies coffee aisle wearing a big smart watch and bright yellow earbuds n carrying a laptop or two (shouldn't be hard)... 😛 PW
[Magisk] 73sydney:
Hey, no one will be more grateful if the GPay module is no longer needed. Ill soon be back using bank where i can even test that theory out myself.

I thought the non-need for the module was random, but youre now saying its more prevalent than 1st thought?

Should have my new GPay (and Android Pay) compatible card form Westpac in about 5 days....

Hehe i had to google Vesbar...im never down near the station, im usually doing a food run at the Metro or in Marrickville proper visiting a friend

As for spotting me, sometimes it not hard, i could be out with my offsider :)
[Magisk] pndwal:
Think you need another thread for that... I had heard of BPay, but now I know what it is. 😋 PW
[Magisk] HippoMan:
Regarding my ongoing problem involving the eventual disappearance of GPay payment methods ...

However, I spoke too soon. It seemed at first that the problem disappeared when I tried a different ROM, but that is not the case, after all. The GPay payment methods also eventually disappeared when I was using the second ROM. It initially took longer for this disappearance to occur with that ROM, but later, some disappearances occured on the same time frame as with the first ROM.

I'm running a number of root-only utilities such as AutoInput, AutoNotification, AutoTools, AutoApps, SecureSettings, 3C Toolbox, and various Tasker capabilities that are only meaningful under root, and I use these utilities to make my device work the way I want under various scenarios. I suspect that one or more of the things I'm doing with these utilities might be interacting with GPay in a way that pushes GPay to delete the payment methods.

However, I do not want to stop running any of those utilties in the ways I currently use them. This and a number of other things in my life are more important to me than spending time trying to get GPay to work. I'm therefore deferring any further investigation of this GPay issue to some time in the future.

The "never give up" motto is still in effect, but "revisit this some time in the unspecified future" is not inconsistent with "never give up".

I'll keep checking here to see if anyone else might come across this issue and perhaps have a solution.

Thanks for all the help.
[Magisk] pndwal:
Just for the purpose of elimination, could you try with GPay-SQLite-Fix module disabled (after reboot of course)? PW
[Magisk] HippoMan:
I already tried that before, and it made no difference. I had SafetyNet and GPay working identically, with or without GPay-SQLite-Fix.

GPay works fine for a while and then forgets its payment methods in both cases.
[Magisk] 73sydney:
What are you trying to say, i caused it? :)

Why i never....

You forget i know where you get your coffee fix, you told me :)
[Magisk] pndwal:
I was pretty sure your fix wasn't poisoned. - Didn't I already say 'it does seem more likely that some manual changes made by @HippoMan are the likely culprit'? ... Now I'm more sure GPay-SQLite-Fix does no harm.

It may even help restore working GPay; IIRC @ipdev said he 'reset' his setup using it, but didn't need it later (not that I understand how that works).

Anyway A.M, I remember your innuendo re target practice from your special training days... and I'm NOT scared!... YOU told me where to find you and the bear... So don't even think about some poisonous fix for my coffee ... Take c A r e of the b E a r ! 😉 P.W.
[Magisk] 73sydney:
Oh i dont shoot people these days, or poison them, i do far worse....

I'll turn up for coffee like this...did this to a friend of mine to mess with him

I have aspergers, i dont care what people think, so nothing is off limits :)

Please bear this in mind :)
[Magisk] HippoMan:
To be clear: I have been sure for a while that GPay-SQLite-Fix has nothing to do with my issue, given that I get the same behavior with or without that utility. And I've been equally certain that this issue must indeed have to do with some other software that is running on my device. And with the latest Magisk (which gives me SafetyNet and which allows GPay to work), GPay-SQLite-Fix doesn't even seem to be needed any more ... at least on my device and my OS.

In order for me to diagnose this better, I would need to know what software actions under Android could cause GPay to forget its previously working payment methods. It would also be helpful to know where GPay stores these payment methods ... on the device itself? ... somewhere in the cloud? If they are stored on the device, I could write something which copies them somewhere initially and then restores them before each run of GPay.

Some day, I'll try to dig deeper into GPay to attempt to find out where these payment methods are stored and what things could trigger them to be forgotten. In the mean time, I just won't use GPay.
[Magisk] Lord Sithek:
I experienced absolutely weird thing. After many weeks of no problems with Google Pay I've got the messenge: "Your device doesn't meet security requirements". I dismissed it, open GPay app and what? Everything looks OK. My device still support NFC payments 🧐 What the heck?? 🤔
[Magisk] raulci:
You're lucky. In my case, I pass safetynet, device certified, sql fix installed, I configure correctly GPay, reboot, everything is fine.

After some hours, when I open GPay, it says "Your device doesn't meet security requirements" and NFC payments change to unconfigured.

Looking at the attest rows in dg.db, everything looks good: read-only permissions and value 0.

I have to clear data for Google Play Services again and configure again the credit card. Normally then it works, but sometimes don't.

Very weird. Yesterday I tried to pay using my bank app directly, without GPay, and it worked, even when GPay said root detected.

I don't know if someone has the same issue as I do.

So for now, I decided to stop using GPay. Although I liked more because the NFC field was working better than with my bank app. With GPay I barely have to touch the payment device while with my bank app, I have to stick the phone some seconds to the payment device.
[Magisk] HippoMan:
I have the same issue with GPay, as I have described above. It works for a while, and then the payment methods disappear. I can reinstall the payment methods, and they work, but then they disappear again after some time passes.
[Magisk] Lord Sithek:
I faced this too when I was on Android 10 older build. What helped me then was installing fingerprint with MHPC module. But since I'm on latest beta A11, I've never needed MHPC
[Magisk] HippoMan:
I can't find anything called "MHPC", and I assume that it's the initials for something ...???
[Magisk] Lord Sithek:
Magisk Hide Props Config 🙂
[Magisk] 73sydney:
@pndwal , all....

Okay

So i got my new card and can use GPay again

Does one need GPay Magisk Module on a Pixel 2XL and an 11 ROM?, lets see...

Flashed a new ROM clean (Pixel Experience ROM)

1) Magisk Manager - check Safetynet passes - CTS not passed and GP Store not certified (expected)

2) Enable MagiskHide

3) Airplane mode on

4) Cleared data for Google Play Store and Google Play Service

6) Reboot

7) Airplane mode off

8) Google Play Store certified

9) Magisk Manager - check Safetynet passes - OK (must have Universal SafetyNet Fix Integrated in ROM as without on 11 on my device its needed)

10) Added card...issuer sends code, verified and card added

Need to test in store but fully expect it to pass

Note: Also managed to add my new card to Samsung Pay (for use on my Galaxy Active 2) with nothing but hiding the relevant apps in MagiskHide
[Magisk] HippoMan:
I'd be interested to know whether your card remains active in GPay, or whether it disappears after a while.

If it remains, then perhaps the issue that I and at least one other person are encountering might be related to Android 10.
[Magisk] 73sydney:
I'll certainly let you know

Previous to the GPay Module, my bank would eventually, after maybe a week, invalidate my card in my Google Wallet - id get an email saying my card has been removed form Google Pay...happened on 9, ive been using the module so long so i cant remember the last time i had an issue
[Magisk] 73sydney:
@pndwal and other Aussies using Westpac:

Interesting tidbits/tips when setting up any payment system with Westpac Bank (which is what ive just joined)

Do NOT add your card to Google Pay directly, add it via the WestPac Bank app...which then adds it to Google Pay

Failure to add it this way will exhibit issues, most notably not being able to add the card to Samsung Pay, if you want to add it to a wearable as well

I found this out the hard way and had to clear data on Google Pay and Westpac app to get it all working
[Magisk] Lord Sithek:
Well, GPay threw me the same message when I entered it again. But in the contactless payment configuration my device meets requirements still. What...? o_O
[Magisk] HippoMan:
Thank you. In my case, the payment methods disappear within 10-20 minutes, usually.

Also, this isn't done by the banks themselves, because I set up two different banks and PayPal as my payment methods, and all three of them disappear at the same time.
[Magisk] Lord Sithek:
I belive it can shed some light on this...

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-84650663

Safetynet fails now...

EDIT: And GPay finally failed as well... 😩
[Magisk] HippoMan:
SafetyNet passes on my device (magisk 22.0 on Android 10) without UniversalSafetyNet Fix. GPay eventually forgets payment methods in the way that I have described, irrespective of the fact that SafetyNet succeeds.

PS: And GPay never throws that "your device doesn't meet security requirements" message for me. Therefore, I think my problem is different from yours.
[Magisk] Lord Sithek:
I think it IS different. Actually I've never linked my issue with yours... 😅

By the way, this occurred in my case soon after flashing latest MIUI beta with March security patch. So I'm eager to belive it has something to do with this
[Magisk] 73sydney:
Sadly (for you), mines still there....whether the bank kills it in a week, we'll see
[Magisk] HippoMan:
I was the one trying to link my problem to yours, @Lord Sithek :)

And I'm glad you are not experiencing the same thing as I, @73sydney

Anyway, GPay just hasn't been worth this much trouble for me. I'll just keep watching for messages here that might pertain to my own situation.
[Magisk] pndwal:
Bearly worth considering - you look like a teddy bear too...

For the record, I don't like Ass Burgers (or South Park for that matter), but I'll go a well cooked Bear Burger any day.

https://www.missallieskitchen.com/bear-burger/ 😋

PW
[Magisk] pndwal:
FWIW, I'm with Bankwest.

No problemo setting up card thru G Pay directly for me, and Bankwest App works fine with standard MagiskHide only... You guys like to make things hard for yourselves don't you? 😉 PW
[Magisk] 73sydney:
Duuuuuude, i said don't set it up in GPay directly if you want to also be able to set your card up in Samsung Pay as well, at least for Westpac Bank....i didnt say you couldnt set it up directly in Google Pay...because i tried it that way first and found it the hard way about Samsung Pay..

i.e. If you dont have the card setup for Google Pay via the Westpac app first, it toggles something their end that prevents you adding it to the digital wallet their app, and also blocks you adding it to Samsung Pay....i dont make the rules :)

And yes, i am only using standard MagiskHide toggled on - though not enabled for Google Pay, but everything Samsung is hidden for Samsung Pay to work - they hate you using a non-Samsung device for that :)

p.s. Dont you make fun of my assburgers :)

p.p.s. Leave the bear out of this, he gets stabby
[Magisk] 73sydney:
@pndwal , all

Updates to Gpay SQLite Fix Module

14/03/2021

Back and able to test again, and able to confirm the experience of some others, who have reported not needing the module recently to have Google Pay working. No one is quite sure why this is, or how long it will last. No one will be more happy than i if we can retire the module. For those wanting to try the minimal non-module method, ive added the steps i took below:

Open Magisk Manager and enable MagiskHide (Settings -> toggle MagiskHide on)

Toggle Airplane mode on

Clear data for Google Play Store and Google Play Service (Settings > All Apps (toggle Show System) the search for and clear data for these packages)

Reboot

Toggle Airplane mode off

Check Google Play Store is certified (Google Play -> Settings, scroll to bottom)

Open Magisk Manager - check Safetynet passes (If not try steps under Pre Installation Checks)

Add card and test

If this fails for you, please continue on below for further steps in Pre Installation Checks (in OP: here) to try passing safetynet (adding fingerprints), or to try the module....
[Magisk] pndwal:
Fair enough!

For me, standard MagiskHide for GPay includes toggling on hide root from GPay in MagiskHide list. You may want to do this if it does detect root in future.

Important: After a failure due to 'root' (modified/insecure environment) detected, ensure hide root from GPay is toggled on in MagiskHide list (and MagiskHide is still toggled on in settings), reboot then clear Google Pay data before setting up cards.

... So you do care? This one's off limits???

Fun Fact:

Cartman sold Ass Burgers in South Park since 2012 after mishearing the explanation for Stan's cynical outlook, attributed to recent vaccinations and diagnosed medically as... wait for it... A S P E R G E R S !

Anyway, I'll blame that lot ... Have you had your shots?

Fun Fact 2:

He's the patron saint of cobblers, curriers, tanners, and leather workers. Once got thrown in a river with a millstone round his neck and survived! Then got beheaded during the reign of Diocletian... Don't think he'd be easily offended... Probably got Asperger's and doesn't care anyway! PW
[Magisk] HippoMan:
Once again regarding my problem of cards and PayPal "disappearing" from GPay, I have three things ...

(1) When I say that the payment methods "disappear" for me, I now realize that I need to be more clear about what this means. The payment methods are always shown in GPay (2 credit cards and PayPal). They just lose their activation, and I have to keep re-activating them. I am sure that this is not due to the banks or PayPal doing anything, because all three items (2 credit cards and PayPal) all get de-activated at exactly the same time; i.e., they are initially all activated, and then after a certain period of time (10-20 minutes), all three of them get de-activated at once.

(2) Is there any Google setting (or lack thereof) on my device which might be causing this? I normally disable anything and everything I can regarding Google. I have disabled Play Protect, Auto-Fill, and every other disable-able Google setting. In order to diagnose this issue, I have re-enabled those two settings, but the problem persists, and this makes me wonder if there might be some other Google setting that I have been overlooking which might cause Google to decide to de-activate PayPal and my cards all at once, after a while. By the way, Google indeed shows my device as "certified". Also, I can always successfully use any of my payment methods to pay for apps from the Play Store. My problem only pertains to contactless payments via GPay.

(3) In answer to my own question above, I now know that the payment methods are not stored on the device itself, but rather, somewhere in Google's cloud. I can see the payment methods even when my device is shut down and I go to Google on line. However, I'm still trying to figure out whether the activation status of the payment methods might be stored on the device itself. Does anyone know about this?