So here's the predictable thread; I haven't seen it elsewhere here.
Have a RETLA beckham, dual-SIM... finally upgraded from my dual-SIM Z2 Play... ugh wish I'd known that I get to choose two SIM or SD card but not both; the Z2 Play accepted all three cards at once
OTA'd to PPWS29.131-27-1-15 (just today, though -11 also failed), Magisk 20.1, tested with no other modules installed... and GPay is rejecting the device for NFC. The Z2 Play has been working great with GPay for some time, but I knew this was a risk with going to a newer device.
Any MagiskHide or one-off module patches out there to make GPay happy on this device? (If you have it *working* in a config like this, I'd love to hear about it too.)
Oddly, after a factory reset, it's now working. However, one thing I don't remember whether I set properly the last time: Once Magisk is installed, it's necessary to turn *off* "OEM Unlocking" in the developer options menu (this doesn't actually lock the bootloader, of course, it's faked by Magisk)... and this time around it activated NFC payments successfully.
Sorry for the noise, though hopefully this can help someone else's search in the future.
Related
Hi,
Has anyone noticed that starting in late April, NFC based payments no longer work?! I wonder because other NFC usage works (e.g. Android Beam or simply reading various NFC tags or cards). I can't figure the exact date, but the last payment that I made with my phone was around 24 april, then it comes the april security update. And after 1 May I noticed that it simply don't work.
Regards
net4u said:
Hi,
Has anyone noticed that starting in late April, NFC based payments no longer work?! I wonder because other NFC usage works (e.g. Android Beam or simply reading various NFC tags or cards). I can't figure the exact date, but the last payment that I made with my phone was around 24 april, then it comes the april security update. And after 1 May I noticed that it simply don't work.
Regards
Click to expand...
Click to collapse
I also have the april security patch, but i could still do a payment yesterday with the NFC of the phone.
So no problem for me.
Yes, Google Pay stopped working for me in mid-April, *but* before I installed the April security patch so that wasn't the cause for me. I was hoping the April patch might fix it but no joy. I've been checking here to see if anyone else had the same problem but this is the first report I've seen.
It's very annoying as I'd got very used to using it... as you say other NFC things are fine.
I've done all the usual tricks of uninstalling, wiping caches, trying an earlier version (it seemed to stop working after the Google Pay update was installed that was released on the 15th, so I thought that might help), etc. etc. but no joy at all. It just doesn't trigger.
Same problem, suddenly NFC doesn't work anymore. Weird thing I discovered is that it might work at that moment when I press the power button to switch display off. ... Strange
Using Magisk with it? Rooted device?
Ah, ok, maybe i wasn't clear enough.
For me it still works, but i do NOT use Google Pay, i use the app from our bank for NFC payments.
I think that i have read some time ago about problems with Google Pay, so maybe that is the case.
I also found out some time ago, that i have to have the lockscreen on-screen, otherwise i cannot do a payment.
So unlocking the phone makes payments impossible and screen-off is also a no-go.
But i suppose you guys already knew that.
xsycox said:
Using Magisk with it? Rooted device?
Click to expand...
Click to collapse
Nope, pure stock (apart from most evenwell apps disabled for this user).
EDIT: Two threads about it now on the Nokia forum at https://community.phones.nokia.com/categories/nokia-7-plus
Fixed by uninstalling Google Pay
Just an FYI, I had my NFC issue resolved by uninstalling Google Pay. May help someone else.
I did not use Google Pay (since is not available in my country), but two tap and pay apps from two banks where I have accounts. Both have updates in april, and one of them tryied to became forced my default one without asking explicitly. But as I say: other NFC functions works: I can beam, I can read tags or cards.
I didn't use Google Pay as well, however, it seemed to interfere with my banking app (couldn't pay anymore) and access to buildings.
Nexustb said:
I didn't use Google Pay as well, however, it seemed to interfere with my banking app (couldn't pay anymore) and access to buildings.
Click to expand...
Click to collapse
No, I mean since is not available in my country yet, I haven't it on my phone.
....and fixed in the latest version of Google Pay, released last week
It may be related to this: https://nvd.nist.gov/vuln/detail/CVE-2019-2041 ?
Hi, so recently I bought my Mi A2 and then decided to unlock it. All seems well, installing custom rom wasn't a problem at all.
However I find something rather annoying, so here's the thing. After unlocking the bootloader, the device build fingerprint was changed, from Jasmine_sprout into taimen, then Play Protect said my device wasn't certified. Installed Magisk, SafetyNet pass both cts and basic integrity but then nothing.
Play Protect now said my device is certified but I can't find some apps that I want to install, which on stock locked bootloader these apps appear on Play Store *such as Lens Distortions, Netflix, Torque Drift*. Then I figured out maybe the device fingerprint was the culprit, but no.
MagiskHide Props Config used, changed the fingerprint into legit Mi A2, still won't work. Trying another SafetyNet module, still won't work. It makes me wonder, why is this happening?
Previously was using Nokia 8 and it didn't have this kind of problem on the same condition e.g. unlocked and systemless root with Magisk, play protect said the device is certified yet these apps that I mentioned before still appear on Play Store.
But on Mi A2? No luck. SafetyNet does work but in the same time it doesn't. Does anyone here understand what might be the culprit of this annoying problem that I have? Tbh I'm really curious about it right now.
I updated from 12.0.2 to 12.0.3 of MIUI recently and I now cannot pay by NFC with my banking app. My banking app doesn't use Google Pay and I don't have or want Google Pay so I can't try that.
I have checked that "Use HCE" wallet is set. Is there anythign I can do to get things working again?
Does no one have any suggestions on this at all?
@ludditefornow can you elaborate a bit what do you mean by "cannot pay by NFC" - what exactly happens when you place your phone near the terminal: is there any reaction (message) from the banking app or no reaction at all? Did you try to pay with the banking app open? Did you try disabling and re-enabling contactless payments in your banking app? In MIUI settings just below the option where you select "Use HCE" there's another option to select application for contactless payments - maybe the upgrade reset it to "Google Pay"?
I also have MIUI Global 12.0.3 (upgraded from 11.something) but didn't try paying by phone yet.
Thanks for the response. I have always paid with the banking app open. And have never had an issue.
Since 12.0.30 I have had two reactions from the 'pay wave' NFC payment terminals. Either they state that they can't read and throw up an error. or simply do nothing.
I have tried to disable and reenable contactless payments and no difference.
I have confirmed that Google Pay is not the default and that my banking app is. I have also confirmed that my banking app has NFC permissions.
I really have no idea. But I appreciate your reply.
For me (Global version) it's still working fine.
Never used my phone for contactless payments, so can't give specific advice, but a couple of simple questions to help troubleshoot.
Does NFC work at all? Can you communicate with other phones, e.g. can you send a photo to another phone using Nearby Share (or whatever name NFC sharing might be called on MIUI, if it's not the same)
How did you update MIUI? OTA or manually? If manually, did you flash the correct ROM? Because Indian MIUI versions don't have NFC functionality, as the physical device is missing on Indian phones.
Robbo.5000 said:
Never used my phone for contactless payments, so can't give specific advice, but a couple of simple questions to help troubleshoot.
Does NFC work at all? Can you communicate with other phones, e.g. can you send a photo to another phone using Nearby Share (or whatever name NFC sharing might be called on MIUI, if it's not the same)
How did you update MIUI? OTA or manually? If manually, did you flash the correct ROM? Because Indian MIUI versions don't have NFC functionality, as the physical device is missing on Indian phones.
Click to expand...
Click to collapse
Thanks,
three different NFC checking apps return positive to NFC and HCE. There is no Android Beam and as far as I recall there never has been.
Updates always OTA. And the current ROM is global as is my phone.
I've completely uninstalled the app and reinstalled it and then added the card again. I will check it today and see the result.
Thanks for the assistance all.
Yesterday I paid successfully with my phone (as I mentioned - MIUI Global 12.0.3 upgraded from 11.something).
Interesting outcome (for me anyway).
After removing the credit card from the app and then deleting the app, I then reinstalled the app and added the card. This led to the NFC HCE function again working.
Another symptom that appeared at the same time on the update was that I could turn on airplane mode at the icon on the pull down draw on the home screen. I couldn't turn off the airplane mode in the same way. To turn off airplane mode I needed to do so with the slider in settings.
After HCE function started working again, my airplane mode on / off functionality came back as well.
I am just writing this here in case someone at sometime gets something similar and may have another option to try to repair it.
Now that Magiskhide is a thing of the past, I am holding off on any phone or OS upgrades that will force me to use a newer version of Magisk than v23 (stable or canary). I have a OnePlus 9, and was considering trying a Pixel6, but now I will just stick with my phone, on it's current update until we have a working Magisk again.
I almost always buy the new OnePlus that comes out in spring, but if Magisk still doesn't have a hide when the 10 is released in 2022, I'm going to pass on it.
Wondering if anyone else is in the camp.
Funny thing is, I tested the app you mentioned in your other thread and had no issues making it start on the current Canary (23011), once added to the Deny list.
mx597turbo said:
Now that Magiskhide is a thing of the past, I am holding off on any phone or OS upgrades that will force me to use a newer version of Magisk than v23 (stable or canary). I have a OnePlus 9, and was considering trying a Pixel6, but now I will just stick with my phone, on it's current update until we have a working Magisk again.
I almost always buy the new OnePlus that comes out in spring, but if Magisk still doesn't have a hide when the 10 is released in 2022, I'm going to pass on it.
Wondering if anyone else is in the camp.
Click to expand...
Click to collapse
Nope, its just you
A12 on a Pixel 4XL, doing just fine...whether i use official, a forked magisk or an old alpha it still works...i just currently use the old alpha because theres less work to do for the same effect on the very edge cases i have running Samsung Wearables/Samsung Pay...once the (very recent) dust settles i think it will be less fiddly than it currently is.
Solved one niggle today, Samsung Pay, by upgrading the Active 2 to Watch 4....it has Play Store access and can use Google Pay, like on my phone...no longer need two different payment methods and apps.....nice
I dont get people getting all bent out of shape as if magisk is the be and end all of everything, yes its nice to have, but people need to remember, theres millions of people out there not even rooting their devices...averga epeople, the unwashed masses
Life goes on for them....no matter what happens on Magisk github
If Magisk ever goes away, we'll survive...the way some carry on you think they need a 1-800 number to call to avoid walking off a cliff edge
Didgeridoohan said:
Funny thing is, I tested the app you mentioned in your other thread and had no issues making it start on the current Canary (23011), once added to the Deny list.
Click to expand...
Click to collapse
Thanks. I'll have to check it out. That app is the only one that doesn't work for me, and has very limited use anyway.
Right now, 23stable is working perfectly. Doesn't make much sense to change unless I can be sure I'll retain all my current functionality.
73sydney said:
Nope, its just you
A12 on a Pixel 4XL, doing just fine...whether i use official, a forked magisk or an old alpha it still works...i just currently use the old alpha because theres less work to do for the same effect on the very edge cases i have running Samsung Wearables/Samsung Pay...once the (very recent) dust settles i think it will be less fiddly than it currently is.
Solved one niggle today, Samsung Pay, by upgrading the Active 2 to Watch 4....it has Play Store access and can use Google Pay, like on my phone...no longer need two different payment methods and apps.....nice
I dont get people getting all bent out of shape as if magisk is the be and end all of everything, yes its nice to have, but people need to remember, theres millions of people out there not even rooting their devices...averga epeople, the unwashed masses
Life goes on for them....no matter what happens on Magisk github
If Magisk ever goes away, we'll survive...the way some carry on you think they need a 1-800 number to call to avoid walking off a cliff edge
Click to expand...
Click to collapse
I listen to Music a lot. I'm not willing to give up custom James DSP/Viper profiles or call recording. Sorry, those are deal breakers for me.
I don't understand why a good audio app and call recording aren't available in the US without root, but guess I'm one of those very few people for whom root is a necessity.
On another note, I never understood the appeal of Samsung pay. Maybe if it worked on a wearable without a data connection (ie, go for a run, watch only, no phone, no data connection). Obviously it doesn't, so no real use that you couldn't get out of Google pay.
mx597turbo said:
Right now, 23stable is working perfectly. Doesn't make much sense to change unless I can be sure I'll retain all my current functionality.
Click to expand...
Click to collapse
If your setup is working and there are no major fixes necessary there's really no need to upgrade. If it isn't broken, no need to fix it...
On a side note I tested that app on a device that still had the 23001 Magisk build installed and had no issues there either. All I did was to make sure the Magisk app was repackaged with a random name and the AZ ID app on the Hide list.
mx597turbo said:
I listen to Music a lot. I'm not willing to give up custom James DSP/Viper profiles or call recording. Sorry, those are deal breakers for me.
I don't understand why a good audio app and call recording aren't available in the US without root, but guess I'm one of those very few people for whom root is a necessity.
On another note, I never understood the appeal of Samsung pay. Maybe if it worked on a wearable without a data connection (ie, go for a run, watch only, no phone, no data connection). Obviously it doesn't, so no real use that you couldn't get out of Google pay.
Click to expand...
Click to collapse
TrueCaller just introduced Call Recording
Wavelets is really good, and what @pittvandewitt actually focuses on now. As for call recording, the apps mentioned above should work.
daemonspudguy said:
Wavelets is really good, and what @pittvandewitt actually focuses on now. As for call recording, the apps mentioned above should work.
Click to expand...
Click to collapse
Wavelets actually makes sound worse
Case in point:
Anyone who has Galaxy Buds downloads it and then applies the tunings for them in Wavelets (not realising theyre already tuned from the factory) and gets garbage sound. I went through this more than year ago with the dev, but yet, you can still do this...
Short version: dont install Wavelets if you like sound, we'll work out a solution for Viper....
I use Wavelets with the AKG K52 headphones, and they sound fantastic with or without wavelets
Hello team! How are you?
I'm struggling to make this app work again, after they put a 'zygote' process after a update, it's not working anymore. Being a digital bank, I cannot access thru anywhere else. I've tried a lot of things already, HMA, zygisk, riru, nothing works. I'm not a nerd of android, so, can anybody help to figure this out?
Much appreciated!!
Hi, it works with zygisk disabled in Magisk. I am trying to make it work while passing safetynet, that unfortunately needs zygisk