On 12X the same :/ today stopped workingAnyone having problem with gpay since today ? I couldnt pay with it right now because it detected the unlocked device. I have a Poco f4 munch.
On 12X the same :/ today stopped workingAnyone having problem with gpay since today ? I couldnt pay with it right now because it detected the unlocked device. I have a Poco f4 munch.
Your understanding is correct...For K40, K40p, 23.4.17.DEV will be the last DEV version, my understanding correct?
-------------------------------------------------
Starting on 21 April, due to the discontinuation of China Beta ROM support, we will no longer provide weekly ROM updates for the following devices:
Redmi K40/POCO F3, Redmi K40 Pro/Mi 11i, Mi 10S and Mi 11 Lite 5G.
Settings -> Notifications & Control center -> Status bar -> Status bar icons -> NFCUpdated my F3 to what seems like the last weekly ROM (rip). Went smooth over OTA as always, no problems.
One question i do have tho, an icon appeared in the Status Bar that I do not recognize and wish to turn off, does anyone know what it is? The one next to the clock
I didn't test it yet on Poco F3 (non-rooted) but many Weekly and Stable reports confirming this GPay issue today.Anyone having problem with gpay since today ? I couldnt pay with it right now because it detected the unlocked device. I have a Poco f4 munch.
Same on my 12X. I guess that Google found a new way to block rooted phones againOn 12X the same :/ today stopped working
Yup, it was always just a matter of time until Google patches existing SafetyNet workarounds.I didn't test it yet on Poco F3 (non-rooted) but many Weekly and Stable reports confirming this GPay issue today.
Anyway my "Play Integrity API Checker", "Yet Another SafetyNet Attestation Checker" and "DRM Info". (annex)
Note: All certificate updated Settings / Password & Security / Fingerprint Unlock / < certificate > (annex)
Friendly question: Will there be a possibility for you to fix this problem ?Yup, it was always just a matter of time until Google patches existing SafetyNet workarounds.
Actually, correction, looks like it was some server issue on Google's side. SafetyNet CTS passes fine now.Friendly question: Will there be a possibility for you to fix this problem ?
You shouldn't use "Universal SafetyNet Fix" with our ROMs though, use Magisk's DenyList instead.No issue with Magisk and Universal safetynet fix installed so far.
I use Magisk Delta + kdrag0n's USNF + Enable SUlist as well with no issues.You shouldn't use "Universal SafetyNet Fix" with our ROMs though, use Magisk's DenyList instead.
Google Play services, Google Play Store and Google (search app), to be safe. That allows passing SafetyNet at least.I use Magisk Delta + kdrag0n's USNF + Enable SUlist as well with no issues.
Couldn't use MagiskHide DenyList for some reason. My banking apps and payment app detects root if I use DenyList but all 4 apps work perfectly with SUlist enabled. Weird maybe but works for me.
Thanks for your recommendation.
Use DenyList to add which apps exactly ?
--
Sent from my Mi 11 Ultra (star)
Seems to be fine again, tests inserted. (annex)Actually, correction, looks like it was some server issue on Google's side. SafetyNet CTS passes fine now.
I reproduced your steps on my device.Hey guys, there is an issue on the 11 ultra that I noticed since the past 10 days or so. After the alarm goes off the refresh rate gets bugged, it drops to 60Hz automatically. After that happens I need to switch to 60 and then to 120 again for it to be normal. Confirmed 100% that it's the alarm causing it. Doesn't matter if I disable the alarm or snooze it with volume buttons, it's the same result.
Yes, issue can only be reproduced with auto refresh rate turned off. Wondering when Xiaomi will notice this...I reproduced your steps on my device.
But my model only works with dynamic refresh rate enabled then a few seconds after the alarm turns off the rate backs to 120Hz.
Then I don't confirm this issue at least on Poco F3 (alioth)
Wondering when Xiaomi and Google will notice the never fixed reported issues... still countingYes, issue can only be reproduced with auto refresh rate turned off. Wondering when Xiaomi will notice this...
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation