Most likely after the latest update, Google Play started reporting to me on my Galaxy S22 that the device is not certified, and I cannot make payments through Google Wallet. Has anyone had a similar issue?
matata86 said:
Most likely after the latest update, Google Play started reporting to me on my Galaxy S22 that the device is not certified, and I cannot make payments through Google Wallet. Has anyone had a similar issue?
Click to expand...
Click to collapse
I've come across at least one other post complaining of the same thing. There seems to be a CTS profile issue with the latest update. I assume you aren't unlocked and rooted?
I don't have root or any other modifications. I just changed the CSC when I bought the phone (a year ago) so that I could record calls.
Go to Developers Options and ENABLE OEM bootloader.
Restart phone.
Go to options and DISABLE the very same option.
Related
SO Android Pay is out, and since we lost ISIS/SoftCard we have been without Tap and Pay. It says that Android pay should work on any NFC Android phone KitKat or above. I installed the app and made sure I have the latest Google Services, which I do, but I keep getting an Android Pay Unavailable error when I try to run it. Has Anyone had any luck. I have a Note 3 with stock Deoxed Rom Rooted and Xposed.
Link to Pay
Link to Services 8.1.13 - 238
Same issue for me. Actually found services 8.1.14(238) and get same issue and am stock. I have unlocked the BL in the past though if that becomes info we need to see to understand this. Would be curious what luck a 100% stock and never messed sorta T-Mo person would have.
nygmam said:
SO Android Pay is out, and since we lost ISIS/SoftCard we have been without Tap and Pay. It says that Android pay should work on any NFC Android phone KitKat or above. I installed the app and made sure I have the latest Google Services, which I do, but I keep getting an Android Pay Unavailable error when I try to run it. Has Anyone had any luck. I have a Note 3 with stock Deoxed Rom Rooted and Xposed.
Link to Pay
Link to Services 8.1.13 - 238
Click to expand...
Click to collapse
It won't work on a rooted system. It also won't work if xposed is installed...even with root cloak. I think you have to be 100% stock unrooted and odexed. I really hope I'm wrong here, but that seems to be the case.
Sent from my SM-N900T using Tapatalk
I am 100% stock and get Samsung updates and the like. I had rommed prior and so had unlocked the BL, but am now 100% stock again other than the BL security flag that knows I once had BL unlocked. Getting this same exact message.
I have to assume this fist release of Pay has yet to address the missing tap to pay sorta NFC stuff on our T-Mo Note 3's and is basically won't load on our devices as it knows it won't work. Probably why none of us have seen Wallet upgrade to Pay in the Play Store just yet or got the services 8 upgrade without doing it manually. They probably need updated still to make our devices work.
The SM-N900T never had a locked bootloader. You may be referring to the knox flag, which shouldn't matter.
Sent from my SM-N900T using Tapatalk
Yeah...meant the Knox flag...other than tripping that awhileven back I am 100% stock again...recovery and all. Never realized the BL was always unlocked on this. I have just tried Google Services 8.1.15 and still the same error.....seems the base Pay app is still not compatible with all NFC capable hardware yet probably. I'm sure this is why I can load the new wallet app from Play, but still don't see the Pay upgrade to the old one.
New Pay app and still no luck...same Pay Unavailable error. This build of Pay may have added support for some devices other than ours though...
https://www.apkmirror.com/apk/google-inc/android-pay/android-pay-1-0-103131485-android-apk-download/
3rd play build still no good....the Play Store page for Pay now shows up and old Wallet is gone. The Pay page says my device is not compatible....so the NFC nonsense must will be an issue...so annoying they can't get this working.
Then they shouldn't say that it will work on any device with 4.4.4 and above with nfc because that is clearly a lie
Yeah....seemingly they should have said "Our goal is to" rather than it "It will" as if it would be good to go for everyone out of the gate.
Note 3 will not support android pay, ever...or samsung pay?
This is something I have researched for a while. It appears that the note 3 was built with an NFC not capable of host card emulation, which google wallet and now android pay depends upon. The work around I am hoping for is to pair a gear s2 with my note 3 and get samsung pay loaded somehow, so I can tap and pay with the watch. I was linked to a page by AT&T support that listed the note 3 as a non supported device on Google's android pay site.
As you may know there as many reports for the S8/S8+ (me included) of the Google App causing: 1. Playstore apps to install slowly or not at all. 2. Play havoc on the Google Voice widget. 3. Delaying the execution of manual software update check or PRL upgrade. Is anyone having these issues with the S9/S9+? Hopefully it is fixed.
Hi! I just bought my S9+ today and I can’t even install apps like Twitter, Instagram and PUBG Mobile on it because it says that the device isn’t compatible w the item. Anyone help??? This is my first Samsung device and I’m upset to why this is happening!
Defgha said:
Hi! I just bought my S9+ today and I can't even install apps like Twitter, Instagram and PUBG Mobile on it because it says that the device isn't compatible with the item. Anyone help?
This is my first Samsung device and I'm upset to why this is happening!
Click to expand...
Click to collapse
Usually that error is due to regional restrictions, not the phone itself
You can definitely install all those apps on an S9+
I am planning to buy a new phone, pocophone f1 is an option, but I don't know if the galaxy watch will work properly with it. Any one has experience with pairing it to pocophone or other non Samsung phones? Thanks.
Mine is paired to an Honor 8 Pro. It paired right out of the box with no problems. Works much better than my old Moto 360 2nd Gen. I don't have Samsung Pay but I don't care about that.
Mister-B said:
Mine is paired to an Honor 8 Pro. It paired right out of the box with no problems. Works much better than my old Moto 360 2nd Gen. I don't have Samsung Pay but I don't care about that.
Click to expand...
Click to collapse
What about recieving notifications on the watch and downloading applications from galaxy store from your phone?
MHH76 said:
What about recieving notifications on the watch and downloading applications from galaxy store from your phone?
Click to expand...
Click to collapse
I used my former S3 with a former Honor 8 and had no problem with notifications or downloading apps from Galaxy store. I wouldn't expect problems with the Galaxy.
Has anyone had their watch receive calls and your phone never rings and then when you turn your watch off phone calls go right to voicemail?
MHH76 said:
What about recieving notifications on the watch and downloading applications from galaxy store from your phone?
Click to expand...
Click to collapse
No problems whatsoever.
I have had NO issues with the watch and my Oneplus 5T.
MHH76 said:
I am planning to buy a new phone, pocophone f1 is an option, but I don't know if the galaxy watch will work properly with it. Any one has experience with pairing it to pocophone or other non Samsung phones? Thanks.
Click to expand...
Click to collapse
If phone is not rooted, bootloader locked, and so play store device status is certified :
You can download and install galaxy gear app, from which you'll be able to pair and manage the galaxy watch.
It's what i done on my oneplus 5 : unrooted, re-locked. Everything works. As a non samsung phone owner, the only things that do not are :
- samsung pay
- integrated tizen email app
Or you can download the apk from apkmirror and use it with root. That's what I'm doing now. Samsung pay may or may not work, I don't use it so I don't know.
You need Samsung accessory service, the galaxy gear plugin and the galaxy wearble app. Mine works flawlessly with a custom ROM with xposed, rooted.
davtse said:
Or you can download the apk from apkmirror and use it with root. That's what I'm doing now. Samsung pay may or may not work, I don't use it so I don't know.
You need Samsung accessory service, the galaxy gear plugin and the galaxy wearble app. Mine works flawlessly with a custom ROM with xposed, rooted.
Click to expand...
Click to collapse
Can you download them without rooting, or must I root the phone?
You can do it without root but you need to enable the install from unknown sources option
they have a modded Samsung store to stop that root check they have magisk mods to hide root
I can confirm that this works on non-samsung devices. I get everything pushed to my watch from my phone as long as I have the notification for the app enabled at the time. The only issues I see with the Samsung Pay is if you don't have the app installed on your phone due to the fact that it uses NFC to make the transaction now so as long as your phone supports NFC you can use Samsung Pay as well. If not then you can use the ported version of Google Pay, but I wouldn't personally recommended due to the fact that it is ran by a third-party developer. As for root, I have not seen an issue or been lock out of anything in the watch due to being rooted so I can't confirm nor deny if it is fully root functional.
Rooted pixel 2 xl and everything works as it should.
I'm on Google Pixel XL Unlocked and Rooted with Magisk 18.1 and on March 2019 security update. Thought I'd save others some possible frustration and embarrassment like I suffered this morning at the grocery store (with my wallet in the car)....it appears that the most recent updates to Google Play Services (I am on 15.0.0, but others are saying the issue occurs on 14.8.49 and higher)....circumvent MagiskHide and prevent Google Pay from working for payment in stores. Really strange in that SafetyNet still appears to pass. Hopefully an update to Magisk/MagiskHide will be incoming soon. You can track the progress and others' experiences at this thread within the Magisk forums....also there is a workaround posted within that thread that many have reported success with...it involves downgrading Google Play services....
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
Good luck!
S
Same here
Have always used google pay on my pixel xl rooted w/ Magisk systemless up until last month (March). Last month all of in store payment capabilities were suspended on all my cards with message rooted device detected. Like you, safetynet and everything still good????
Google Pay
alienG0D said:
Have always used google pay on my pixel xl rooted w/ Magisk systemless up until last month (March). Last month all of in store payment capabilities were suspended on all my cards with message rooted device detected. Like you, safetynet and everything still good????
Click to expand...
Click to collapse
This is a known issue and there are some solutions
see https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
Bought Unlocked Pixel 3 From Google, & T-Mobile Crammed an App Onto the Phone Anyway!
How to make a customer very angry, and concerned about security...
Bought a brand-new Pixel 3 from Google, inserted my T-Mobile SIM card, (Goodbye Sony Xperia Series! Good Riddance!) and went about my business with my new Android 10 phone.
But a few days after, just today, I see a screen pop up that was pink - I asked me if I wanted to check and see if my phone was "eligible" for unlocking.
One surmises that T-Mobile noticed the new device ID associated with the same old SIM card, and downloaded the app WITHOUT PERMISSION AND WITHOUT ANY NOTICE THAT THEY WERE DOING SO. They also did not even bother to check the ID against their own inventory to determine if they had sold the phone or not, if they did, they would have seen that it was a Pixel, which they don't offer.
At no time did I visit a T-Mobile sit or download any T-Mobile related apps. They just took it upon themselves to silently install software without even asking.
So here's the punchline - what ELSE might they have installed, and how can I be sure about this?
What else might they install in the future? On whose behalf?
packetfire said:
How to make a customer very angry, and concerned about security...
Bought a brand-new Pixel 3 from Google, inserted my T-Mobile SIM card, (Goodbye Sony Xperia Series! Good Riddance!) and went about my business with my new Android 10 phone.
But a few days after, just today, I see a screen pop up that was pink - I asked me if I wanted to check and see if my phone was "eligible" for unlocking.
One surmises that T-Mobile noticed the new device ID associated with the same old SIM card, and downloaded the app WITHOUT PERMISSION AND WITHOUT ANY NOTICE THAT THEY WERE DOING SO. They also did not even bother to check the ID against their own inventory to determine if they had sold the phone or not, if they did, they would have seen that it was a Pixel, which they don't offer.
At no time did I visit a T-Mobile sit or download any T-Mobile related apps. They just took it upon themselves to silently install software without even asking.
So here's the punchline - what ELSE might they have installed, and how can I be sure about this?
What else might they install in the future? On whose behalf?
Click to expand...
Click to collapse
I noticed the same thing on my pixel 3 xl and I'm on Google Fi and I can't uninstall that app to unlock my phone, I can only disable the app
lavin40 said:
I noticed the same thing on my pixel 3 xl and I'm on Google Fi and I can't uninstall that app to unlock my phone, I can only disable the app
Click to expand...
Click to collapse
What's worse is that the app itself claims that you CAN remove the app, after it has (correctly) determined that the phone is not locked.
Is your app also a "T-Mobile" app with a pink icon, or is it a variant that is branded for the Google FI service?
packetfire said:
What's worse is that the app itself claims that you CAN remove the app, after it has (correctly) determined that the phone is not locked.
Is your app also a "T-Mobile" app with a pink icon, or is it a variant that is branded for the Google FI service?
Click to expand...
Click to collapse
The app is pink I believe I got a Verizon pixel 3 xl cause the OEM unlock option is greyed out so I can't even root the phone
During the initial setup, there is a "sneaky" screen that asks if you want to finish (or something, I forgot). But if you expand that screen, there are several apps that Google intends to install, and you can opt out right there. Duo is definitely one of the apps, and several T-Mobile apps (I'm on TMO) as well as some others. I opted out and don't have any TMO apps.
Just like the above comment, it's in your 'additional-apps' section of the initial setup. If you uncheck? It doesn't install.
jbarcus81 said:
Just like the above comment, it's in your 'additional-apps' section of the initial setup. If you uncheck? It doesn't install.
Click to expand...
Click to collapse
Yep. This. If the app(s) are installed it's because you let the setup install them. They (Google/T-Mobile) didn't install them on the phone without your consent. You just missed where you have the option to not install them.
ktmom said:
During the initial setup, there is a "sneaky" screen that asks if you want to finish (or something, I forgot). But if you expand that screen, there are several apps that Google intends to install, and you can opt out right there. Duo is definitely one of the apps, and several T-Mobile apps (I'm on TMO) as well as some others. I opted out and don't have any TMO apps.
Click to expand...
Click to collapse
Well, that must be how it was done - anyway, the app is gone now, all by itself, so it appears to be yes, an undetectable silent install of an undelete-able "system app", but it seems that once you are verified as "unlocked", it self-deletes.
But I got nothing but the "unlocker", no Duo installed for me. (I like Google Authenticator - 2FA without anything else to carry, and SIM-swap-proof).
So this was the paternalistic Google trying to be helpful, but creeping people out yet again with their presumptuousness.
packetfire said:
Well, that must be how it was done - anyway, the app is gone now, all by itself, so it appears to be yes, an undetectable silent install of an undelete-able "system app", but it seems that once you are verified as "unlocked", it self-deletes.
But I got nothing but the "unlocker", no Duo installed for me. (I like Google Authenticator - 2FA without anything else to carry, and SIM-swap-proof).
So this was the paternalistic Google trying to be helpful, but creeping people out yet again with their presumptuousness.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.tmobile.pr.mytmobile
Tmobile silently installed this app on my unlocked pixel 3xl from best buy just yesterday after I set up my playstore account!
As a User app though.
packetfire said:
How to make a customer very angry, and concerned about security...
Bought a brand-new Pixel 3 from Google, inserted my T-Mobile SIM card, (Goodbye Sony Xperia Series! Good Riddance!) and went about my business with my new Android 10 phone.
But a few days after, just today, I see a screen pop up that was pink - I asked me if I wanted to check and see if my phone was "eligible" for unlocking.
One surmises that T-Mobile noticed the new device ID associated with the same old SIM card, and downloaded the app WITHOUT PERMISSION AND WITHOUT ANY NOTICE THAT THEY WERE DOING SO. They also did not even bother to check the ID against their own inventory to determine if they had sold the phone or not, if they did, they would have seen that it was a Pixel, which they don't offer.
At no time did I visit a T-Mobile sit or download any T-Mobile related apps. They just took it upon themselves to silently install software without even asking.
So here's the punchline - what ELSE might they have installed, and how can I be sure about this?
What else might they install in the future? On whose behalf?
Click to expand...
Click to collapse
Just to show that it was indeed installed to the device...
dirtyreturn said:
Just to show that it was indeed installed to the device...
Click to expand...
Click to collapse
As stated in this thread, you accepted the install of the T-Mobile app during the setup process.
ktmom said:
As stated in this thread, you accepted the install of the T-Mobile app during the setup process.
Click to expand...
Click to collapse
That's just exclusive to the pixel 3? Stock Rom?
Just wondering since it's a first that this happened for me. Being on the same carrier with previous phones this did not happen.
dirtyreturn said:
That's just exclusive to the pixel 3? Stock Rom?
Just wondering since it's a first that this happened for me. Being on the same carrier with previous phones this did not happen.
Click to expand...
Click to collapse
I think I had to disable TMO apps during setup on my PH-1. I'm sure that Google has agreements with the carriers who offer the device. Even (esp?) when the device comes straight from Google.
And yes, stock ROM.