I woke up to a notification saying "your phone is no longer ready for contactless payments." It was working yesterday. I did the software check and it failed. Anyone else have this pop up?
I'm on A12 beta1, rooted, hardware off 2.0 module. Safetynet fails but has been for a couple weeks.
Related
Hi
I'm kinda new around here so don't really now where to post it.
So today Google Assistant randomly appeared on my phone. I have done nothing to install it. I tried to open Google Now (via holding the Home button) and fully functional Assistant showed up. It works perfectly - just as on a Pixel device.
I'm running SliMM 3.8, obviously rooted, locked bootloader (I think). I also have 'N-ify' Xposed module installed, which I think may have something to do with that.
Anybody got any ideas how and why I suddenly got it on my phone?
Finezol said:
Hi
I'm kinda new around here so don't really now where to post it.
So today Google Assistant randomly appeared on my phone. I have done nothing to install it. I tried to open Google Now (via holding the Home button) and fully functional Assistant showed up. It works perfectly - just as on a Pixel device.
I'm running SliMM 3.8, obviously rooted, locked bootloader (I think). I also have 'N-ify' Xposed module installed, which I think may have something to do with that.
Anybody got any ideas how and why I suddenly got it on my phone?
Click to expand...
Click to collapse
Definitely it is Android N-Ify,if you want to disable it go to the N-Ify app and go to Check for Updates and click the N logo about 6 times until it says You have unlocked experimental features and then go back,open Experimental Settings and uncheck enable google assistant
A friend of mine installed Good Lock on his Note 9 running Pie. Every week or so, Good Lock modules stop running and have to be toggled off and on to get them working again. He checked to make sure all updates were installed. When it stops working, the modules still show they're "ON". I checked the battery usage and there's no indication it's putting Good Lock to sleep. Is there a possibility that his installed theme, from the Samsung Store, is conflicting somehow? Does anyone else have this issue or a solution?
The only times that's ever happened to me on Oreo was when I'd get a system update, or Good lock updated, but it certainly wasn't a regular occurrence.
Background - switched from xposed to Edxposed to get Google Pay to work. It does now work but caused buggy side effects.
1. System soft reboots directly after a manual boot completed but is then okay usually if left to settle.
2. Screen says always on, will not respond to display settings options set to 'off' after 1 min. It will off by power key, just not auto off.
3. One xposed module does't work at all (Niwatori One Handed Mode). Xposed Edge and Gravity work fine so far.
I have 2 devices, an LG V20, LG G5 both on Oreo and both exhibiting exact same problems. 1 device uses Edexposed Manager, the other Edxposed Installer. Is installer now obsolete?
So the One handed Mode is the biggest problem. Is there a way to look under the hood to fix a non working module? If I could fix the other problems maybe I could find an alternative app for one handed mode.
Okay well "HiddenCore module" (xposed module) was causing the screen to stay on. As I said I just installed it cause I saw it thinking maybe it was necessary for Gpay. Turns out I uninstalled it, the screen will now auto off, and Gpay still works.
Only issue now is the soft reboot after boot completed. Not a huge deal, maybe it will be resolved in an edxposed update, although I am now using the latest Canary alpha, alas no change.
Okay well "HiddenCore module" (xposed module) was causing the screen to stay on. As I said I just installed it cause I saw it thinking maybe it was necessary for Gpay. Turns out I uninstalled it, the screen will now auto off, and Gpay still works.
Only issue now is the soft reboot after boot completed. Not a huge deal, maybe it will be resolved in an edxposed update, although I am now using the latest Canary alpha, alas no change.
ezzony said:
Only issue now is the soft reboot after boot completed. Not a huge deal, maybe it will be resolved in an edxposed update, although I am now using the latest Canary alpha, alas no change.
Click to expand...
Click to collapse
I experience the same and already reported it to devs.
https://github.com/ElderDrivers/EdXposed/issues/373
C3C076 said:
I experience the same and already reported it to devs.
https://github.com/ElderDrivers/EdXposed/issues/373
Click to expand...
Click to collapse
That thread is saying something about using a modified build of magisk. Did you try that and do you know where to get it?
edit: I'm using latest magisk 20 version.
The Edxposed Manager Canary release fixes this for me
all of a sudden safetynet is failing and i woke up to my phone saying you can no longer do contactless payments. What can I do?
It does pass when I hide modules but I have not installed anything new in months
Play Services update. https://twitter.com/topjohnwu/status/1245956080779198464?s=19
I'm on V12.5.1.0.RJOMIXM, Magisk v23.
I woke up this morning and all of a sudden my device is not passing safetynet, failing on CTSprofile. It has worked fine for months and I haven't changed anything, other that play store auto updates being enabled
Edit: I awoke to a notification off gpay saying device doesn't meet security standards and that I can't use contactless if that makes a difference, never had a problem with it before
Certainly, you made some changes on the device.
I made no changes on the device. Do not state something as certain when you can not be certain
Regardless, I fixed it using the instructions here
If you are using magisk, so yes, you made changes on the device.
Lurxs said:
I'm on V12.5.1.0.RJOMIXM, Magisk v23.
I woke up this morning and all of a sudden my device is not passing safetynet, failing on CTSprofile. It has worked fine for months and I haven't changed anything, other that play store auto updates being enabled
Edit: I awoke to a notification off gpay saying device doesn't meet security standards and that I can't use contactless if that makes a difference, never had a problem with it before
Click to expand...
Click to collapse
Same thing happened here on Mi Mix 2S.
pancomido said:
Same thing happened here on Mi Mix 2S.
Click to expand...
Click to collapse
I can only assume Google updated something stealthily, I fixed it using this guide, follow at your own risk