Android Pay stopped being officially supported/working on Android Wear (starting with the Oreo update) outside US/UK: https://www.androidpolice.com/2018/...ate-disables-android-pay-users-outside-us-uk/ and https://support.google.com/androidwear/thread/26579
I created small proof of concept app that streamlines launching/enabling of Android Pay so even with it disabled, it will only take up to two additional taps to pay with Android Pay:
Launch "Pay Enabler" (instead of Android Pay). If Android Pay is already enabled, Pay Enabler will just launch it directly.
Tap "Enable" (not needed since version 5, requires Accessibility service)
Tap "Open" (not needed since version 4)
Note 1: Google started geo blocking Google Pay on Wear OS H (Android Pie/9) so Pay Enabler doesn't work on newest firmwares. It still works on Oreo.
Note 2: When connected to iOS, Play Store requires standalone connectivity (WiFi or cellular data) for enabling as it doesn't use caches (unlike when paired with Android).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download
Play Store: https://play.google.com/store/apps/details?id=com.brouken.wear.payenabler
Source: https://github.com/moneytoo/PayEnabler
They added few more countries but there is still dozen more countries affected.
To use Google Pay on your watch, you need to: Be in the US, UK, Italy, Spain, Australia, Canada, Poland, Russia, or Germany.
Click to expand...
Click to collapse
https://support.google.com/pay/answer/7293863
Update 2018/11/19:
Uploaded Pay Enabler version 5 here to XDA (not on Play Store, yet). It uses Accessibility service to automate enabling of Google Pay, no more tapping "Enable". (Source is also available on Github.)
Requires manual enabling in "Settings -> Accessibility -> Pay Enabler".
Works only with English - texts "Google Pay" and "Enable". Post texts in your languages and I will include them (That shouldn't be necessary as of version 5d which supports two dozens of languages - at least for the "Enable" button).
Accessibility service is registered only for Play Store so it shouldn't cause basically any battery drain (as it doesn't poll anything)
Update 2018/11/29:
Version 5 submitted to the Play Store.
Update 2018/12/16:
Version 6 fixes detection of the enable button in some non English languages (cs, fi, hi, ko, th).
For me I have no issue yet, never got 8.0 and I do not want it.
I bought this watch for Android Pay and it has worked fine since May 2017.
Even though I hate Samsung for abandoning Android Wear, I maybe forced in time to try Samsung Pay; I know my Canadian Bank supports Samsung Pay.
Anybody have any clue why Android Pay on the Android Wear watch only works in the US, UK when other countries support it ?
AstroDigital said:
For me I have no issue yet, never got 8.0 and I do not want it.
I bought this watch for Android Pay and it has worked fine since May 2017.
Even though I hate Samsung for abandoning Android Wear, I maybe forced in time to try Samsung Pay; I know my Canadian Bank supports Samsung Pay.
Anybody have any clue why Android Pay on the Android Wear watch only works in the US, UK when other countries support it ?
Click to expand...
Click to collapse
This app is a good solution until Google finally fixes. Thank you!
Enviado desde mi SM-G930F mediante Tapatalk
No, no, thank YOU Mr Acavano.
Thanks for the fix!
moneytoo said:
Android Pay stopped being officially supported/working on Android Wear (starting with the Oreo update) outside US/UK: https://www.androidpolice.com/2018/...ate-disables-android-pay-users-outside-us-uk/ and https://support.google.com/androidwear/thread/26579
I didn't test it myself (yet, I'm still on Nougat) but based on user reports, Android Pay is only getting disabled (by Google Play services?). It is reported that payments are still working if it's manually enabled.
Based on this, I created small proof of concept app that streamlines launching/enabling of Android Pay so even with it disabled, it will only take two additional taps to pay with Android Pay:
Launch "Pay Enabler" (instead of Android Pay). If Android Pay is already enabled, Pay Enabler will just launch it directly.
Tap "Enable"
Tap "Open"
Version 1 vs Version 3
It was reported to me that Android Pay doesn't show up in Settings (list of installed apps) so since version 2 it uses Play Store for manual enabling. (I will try if I can open the app manually from background once enabled to save the second click to "Open").
Download
Play Store: https://play.google.com/store/apps/details?id=com.brouken.wear.payenabler
Source: https://github.com/moneytoo/PayEnabler
Click to expand...
Click to collapse
My friend, if you find a way to enable android pay on the wear24 i'll get a lot of money, you can sell a app to do this, there's a lot of people looking for it include me! The wear24 is very cheap on ebay, by without android pay is a little useless.
https://forum.xda-developers.com/android-wear/help/verizon-wear24-to-unlock-carrier-t3715300
Im in Australia, Google play store says my device is not compatible with this app.
Downloaded the version 1 and 3 apk, but upon installing it says there is a problem with parsing the package.
Help?
erwinsie said:
Im in Australia, Google play store says my device is not compatible with this app.
Downloaded the version 1 and 3 apk, but upon installing it says there is a problem with parsing the package.
Help?
Click to expand...
Click to collapse
The app is compatible only with Android Wear devices running Android Oreo. You must either select your watch when installing from web or search for Pay Enabler in Play Store directly on your watch. It's standalone app for Android Wear and nothing gets installed elsewhere.
moneytoo said:
The app is compatible only with Android Wear devices running Android Oreo. You must either select your watch when installing from web or search for Pay Enabler in Play Store directly on your watch. It's standalone app for Android Wear and nothing gets installed elsewhere.
Click to expand...
Click to collapse
Ah, ok. Got it. No worries it works. Than you very much from Australia.[COLOR="Silver"
Just to be clear, this will not work on nougat?
Because as mentioned before it would be great if this brought android pay to the wear24. Verizon's videos show the watch with the android pay app so its obviously a possibility.
Thanks
AstroDigital said:
For me I have no issue yet, never got 8.0 and I do not want it.
I bought this watch for Android Pay and it has worked fine since May 2017.
Even though I hate Samsung for abandoning Android Wear, I maybe forced in time to try Samsung Pay; I know my Canadian Bank supports Samsung Pay.
Anybody have any clue why Android Pay on the Android Wear watch only works in the US, UK when other countries support it ?
Click to expand...
Click to collapse
Thank you OP, it works! I wish Google would fix this or just re-enable.
And how does Samsung Pay on Gear (watch) devices work? I heard it doesn't unless you hack it hard.
transitnowapp said:
Thank you OP, it works! I wish Google would fix this or just re-enable.
And how does Samsung Pay on Gear (watch) devices work? I heard it doesn't unless you hack it hard.
Click to expand...
Click to collapse
Really do I need to spell it out ?
If I am forced to use a Gear I would need to dump "Google" Pay and use Samsung Pay.
But for now my watch has not been upgraded to Oreo works fine, I will never upgrade to Oreo as my first choice.
If I have to in time go to Oreo and have the same issue everybody outside of the UK, and US has I will do two things get annoyed at the arrogance of Google "hey we do not care if you been using Android Pay now Google Pay for months, we will stop you" then I will install the Pay Enabler.
The chances are I will never be forced to by a Gear, though new watches with NFC have not been released.
I'm using it since yesterday and it is so much helpful. Thank you so much!
They added 3 more countries but there are still 14 more countries affected.
To use Google Pay on your watch, you need to: Be in the US, UK, Spain, Australia, or Canada.
Click to expand...
Click to collapse
https://support.google.com/pay/answer/7293863?co=GENIE.Platform=Android&hl=en
Great news! Thanks
Enviado desde mi SM-G930F mediante Tapatalk
Is there any way to emulate being in the US from the watch? I get to the download page with the app, but can't download it as it "is not available in my country". Any way to bypass this?
Mart1neZ said:
Is there any way to emulate being in the US from the watch? I get to the download page with the app, but can't download it as it "is not available in my country". Any way to bypass this?
Click to expand...
Click to collapse
Had the same problem. A long time ago I had created a Google Account via US VPN. Now I added this as a second account on the watch and selected the account in the play store and it works.
I hope it still works like this.
It's not just Android Wear
Will your fix also work on "regular" Android 8.1 on a smartphone? I have the same issue with Google Pay on my Nexus 5x, as I now live in Hungary.
In my case, the "back-end" part of Google Pay continues to work, and I can make payments at contactless terminals using my installed credit or debit cards. But the "front-end" user interface part is disabled just as described here. If I need to change the payment card used for a transaction (or add or remove a card) it's a real pain in the ass to enable the app.
Ironically, the availability of contactless payment terminals in Hungary is excellent, while in the US they almost don't exist.
From the little research I've done on the internet, there are lots of people with Google Pay on smartphones facing the same issue, and so you might want to consider a version of your fix for the rest of us!
ikijibiki said:
Will your fix also work on "regular" Android 8.1 on a smartphone? I have the same issue with Google Pay on my Nexus 5x, as I now live in Hungary.
In my case, the "back-end" part of Google Pay continues to work, and I can make payments at contactless terminals using my installed credit or debit cards. But the "front-end" user interface part is disabled just as described here. If I need to change the payment card used for a transaction (or add or remove a card) it's a real pain in the ass to enable the app.
Ironically, the availability of contactless payment terminals in Hungary is excellent, while in the US they almost don't exist.
From the little research I've done on the internet, there are lots of people with Google Pay on smartphones facing the same issue, and so you might want to consider a version of your fix for the rest of us!
Click to expand...
Click to collapse
As Hungary is not a country supported by Google Pay, are you using your payment card that was issued by US bank? I'm curious to know what is Google Pay policy on using it abroad (as on vacation or expat) - I thought the bank requirement was only for setup/card linking. (I understand you're talking about frontend vs backend as all card data and emulation is done by Google Play services)
Anyway, you should be able to use the attached apk in the first post.
moneytoo said:
As Hungary is not a country supported by Google Pay, are you using your payment card that was issued by US bank? I'm curious to know what is Google Pay policy on using it abroad (as on vacation or expat) - I thought the bank requirement was only for setup/card linking. (I understand you're talking about frontend vs backend as all card data and emulation is done by Google Play services)
Anyway, you should be able to use the attached apk in the first post.
Click to expand...
Click to collapse
Yes, all my cards are from US banks. Although I now live abroad, all my banking/finance is still US-based. I've been using Android Pay and no Google Pay for about a year without any issues from either Google or my banks. My banks are fully aware of my situation and have been really great about shipping new credit and debit cards to Hungary.
There are rare occasions where the terminal has some issue with the phone emulation, but mostly using the phone is the fastest way to pay, as the fingerprint authentication to unlock the phone eliminates the need to enter any PIN. Interestingly, as all US chip cards are non-PIN and require a signature, when using the phone to pay, I also don't need to sign any slips. The two-factor authentication does all the work.
I'll download the apk and give it a try. Thanks!
---------- Post added at 08:18 PM ---------- Previous post was at 07:54 PM ----------
ikijibiki said:
I'll download the apk and give it a try. Thanks!
Click to expand...
Click to collapse
No joy. Payenabler-3.apk won't install on my phone.
ikijibiki said:
No joy. Payenabler-3.apk won't install on my phone.
Click to expand...
Click to collapse
My bad. It only works the other way (phone apps work on Wear). Please see the first post again for "-phone" version.
Hi all. Today I've received a notification from "poste italiane", the notification say that I can finally use my "Postepay Evolution" to pay contactless, but when I try to enable these I got the message on the screenshot
Evasi0n3r said:
Hi all. Today I've received a notification from "poste italiane", the notification say that I can finally use my "Postepay Evolution" to pay contactless, but when I try to enable these I got the message on the screenshot
Click to expand...
Click to collapse
For some reason google pay thinks your phone has been modified.. If bixby got the translation of that image right.
Google pay will only work on a device that is flagged as certified by google play protect status... So if your running the firmware provided by Samsung for the phone, or firmware provided for the phone that comes from a different compatible model (like the G965U and G96U1 firmware can be flashed on either device without issue) then your status should say certified.
If you have enabled or toggled OEM unlock (which unlocks the bootloader) then google pay will not work. Because this falls under the "phone modification" category you will have to re-lock the bootloader in order to use google pay.
If you have rooted the phone then google pay will not work. There maybe a way to hide root from google pay, but you will either have to do some research into that or someone else might have some ideas (assuming this is what you have going on).
If you are using the Samsung One UI beta (the android pie beta) firmware then Google Pay will not work. This is because the firmware has not been officially released, so the google play protect status will flag it as not certified.
scottusa2008 said:
For some reason google pay thinks your phone has been modified.. If bixby got the translation of that image right.
Google pay will only work on a device that is flagged as certified by google play protect status... So if your running the firmware provided by Samsung for the phone, or firmware provided for the phone that comes from a different compatible model (like the G965U and G96U1 firmware can be flashed on either device without issue) then your status should say certified.
If you have enabled or toggled OEM unlock (which unlocks the bootloader) then google pay will not work. Because this falls under the "phone modification" category you will have to re-lock the bootloader in order to use google pay.
If you have rooted the phone then google pay will not work. There maybe a way to hide root from google pay, but you will either have to do some research into that or someone else might have some ideas (assuming this is what you have going on).
If you are using the Samsung One UI beta (the android pie beta) firmware then Google Pay will not work. This is because the firmware has not been officially released, so the google play protect status it will that it isn't certified.
Click to expand...
Click to collapse
Thanks a lot, I'm using one ui beta.
Other payment solutions may work despite the beta.
GPay works with the official release of Pie.
I decided to root ky Pixel 6 and found out that i couldn't get around the security from germans banking apps.
simple soloution. have magisk/zygisk installed and set the root mode to "user" in the settings of magisk manager.
then go to your settings and setup a second user (wont have root) install your banking apps and enjoy the ability to use them with an rooted device
edit: this method was tested for Sparkasse app's
• S-Push Tan
• Mobiles Bezahlen
IndubidablyStoned said:
I decided to root ky Pixel 6 and found out that i couldn't get around the security from germans banking apps.
simple soloution. have magisk/zygisk installed and set the root mode to "user" in the settings of magisk manager.
then go to your settings and setup a second user (wont have root) install your banking apps and enjoy the ability to use them with an rooted device
Click to expand...
Click to collapse
I'm not being critical of your choices but why would anyone chance having a banking institution or any financial app including
GPay on a rooted device? Isn't there a much greater chance of being compromised by an app or inadvertent web link? And if the banking institution sees that a bogus user was created what are the chances of recovering funds obtained through fraudulent activity? I understand why people want to root don't get me wrong, but money transfers and transactions on that device seem a little reckless to me. But I could be wrong, just curious of the thinking here.
i Understand, but if you want to have an custom DAC like Viper4Android you kinda need root. my intention isnt to do fraudulent activity, as i mentioned in the Post you dont have Root access on that second user
IndubidablyStoned said:
i Understand, but if you want to have an custom DAC like Viper4Android you kinda need root. my intention isnt to do fraudulent activity, as i mentioned in the Post you dont have Root access on that second user
Click to expand...
Click to collapse
You misunderstood my concern wrt banking activity. I didn't suggest that you were doing anything fraudulent but if you were the victim of fraudulent activity would the bank still cover you with a bogus account you created? I don't know if what you did was entirely proper or not but that was not the issue I thought you might be concerned about.
As I said, I completely understand your desire to root be it V4A or DAC or even ad blocking. I just wonder the benefit vs the exposure if you are using banking apps. Without financial transactions occurring on the phone I doubt there is much to worry about other than what we are all concerned about root or not.
bobby janow said:
I'm not being critical of your choices but why would anyone chance having a banking institution or any financial app including
GPay on a rooted device? Isn't there a much greater chance of being compromised by an app or inadvertent web link? And if the banking institution sees that a bogus user was created what are the chances of recovering funds obtained through fraudulent activity? I understand why people want to root don't get me wrong, but money transfers and transactions on that device seem a little reckless to me. But I could be wrong, just curious of the thinking here.
Click to expand...
Click to collapse
Considering DirtyPipe exists and has not been patched yet (plus how long it already took to even acknowledge the problem in the first place), rooting is the least of our worries when it comes to monetary transactions/banking and android.
Bear in mind that DirtyPipe is only one elevation exploit that we've heard about. And for every disclosed vulnerability there are dozens of others that nobody's aware of. The market for rooted android users is very small compared to the overall android phone-user market. Creating exploits specifically targeting rooted phones would be a waste of time and effort compared to working on privilege escalation on non-rooted devices; from a hacker's perspective you want to hit the largest volume of targets in cases like these.
I've been rooting my phones for 10 years now, and my usage of banking/fintech apps on my devices has increased consistently. Applying common sense opsec/infosec practices can negate a large percentage of the perceived risk that root access exposes you to.
On the other hand, if someone wants to target you specifically, as an individual, you're screwed, root or no root, unless you're aware of the risks that come with technology and the pitfalls of android (iOS can be perceived as more secure but when it comes to individual targeting/attacks, there are expensive tools made by some of the world's top intelligence organizations that can wreck havoc on iOS as well)
TL;DR you're never truly safe, root or no root.
Unfortunately that doesn't worked for me
I tested the following apps:
SecureGo
VR SecureGo
Mobiles bezahlen
Every App doesn't launch. Sparkasse is quitting instantly and SecureGo Apps are stuck with their logo.
On the rootet user I get the Browser-warning (of SecureGo) that my device doesn't meet the security requierements. So far so good, but on the non-rooted uses i would have expect that they're working.
Any Idea? I'm on April Build.
i dont know currently, i dont have root anymore since i had to update to the April Update. i'll update if there is something that can be done
Maybe you could confirm that these Apps launch on April build without root? That could help to research the problem a bit. Thanks!
hanni2301 said:
...but on the non-rooted uses i would have expect that they're working.
Any Idea? I'm on April Build.
Click to expand...
Click to collapse
Maybe these apps are not supporting fully Android 12?
I have an app which, until recently, was freezing when the location was enabled. To be exact, when "Use precise location" was enabled. Only location access the app was not freezing, but couldn't get the coordinates.
Maye this is a similar situation here.
Cheers
Tom
hanni2301 said:
Unfortunately that doesn't worked for me
I tested the following apps:
SecureGo
VR SecureGo
Mobiles bezahlen
Every App doesn't launch. Sparkasse is quitting instantly and SecureGo Apps are stuck with their logo.
On the rootet user I get the Browser-warning (of SecureGo) that my device doesn't meet the security requierements. So far so good, but on the non-rooted uses i would have expect that they're working.
Any Idea? I'm on April Build.
Click to expand...
Click to collapse
I managed to get the VR Secure Go app working by doing the steps in the op plus using ice box and freezing magisk and the bank apps. I'm on April, too and I'm using radioactive kernel. Rooted stock kernel works as well on my device, but I had issues with the bank apps on some other kernels.
So to confirm, you need to freeze magisk on the rooted user and you're able to use the bank apps on the second (non rooted) user?
On which user you would freeze the bank apps? I doesn't have them installed on the rooted user.
Thanks in advance that you can definitely confirm its not the fault of April built.
hanni2301 said:
So to confirm, you need to freeze magisk on the rooted user and you're able to use the bank apps on the second (non rooted) user?
On which user you would freeze the bank apps? I doesn't have them installed on the rooted user.
Thanks in advance that you can definitely confirm its not the fault of April built.
Click to expand...
Click to collapse
I only have one user (the rooted user). I've done the following steps:
1. Configure magisk: activate Zygisk and setup deny list for the banking apps
2. Hide magisk app
3. Freeze magisk and banking apps with Ice Box
ok, that is the normal way which is different to the approach the thread starter has chosen.
I use deny list plus hide my applist and works fine with Sparkasse, s-push and mobil bezahlen no need to freeze or use a second user profile
How do you do that, hide applist?
You can bypass it by
Download App Named Shelter from Play store.
The App will create work profile and you can bypass any bank or app you facing issue with it.
When completed create work profile you can clone Bank App and use if.
As Information, It works out of the Box with Magisk denylist,
You only need to Install Ice Box and hide Magisk Manager, even if it is using a random name, "Mobiles Bezahlen" would detect it.
Magisk + Ice Box is sufficient on latest Miui 13 as well!
Regards!
Not sure but I think island could help not sure though as I'm not rooted the app is made by greenify
Only as info, these 2 Apps, Postbank Finanzassistent and Postbank BestSign working by default on a rooted device.
I like Postbank