Related
Ok, so I have rooted s8 and I can get Android pay working on the phone using magisk hide, but when I try to activate AP on the watch it somehow detects that my phone is rooted and does not let me setup any cards. I have even used magisk hide to hide root from Android Wear. What am I missing? Any ideas?
As I said, no problems with AP on the phone so it seems crazy to me that the watch is somehow detecting root...
I am on the latest preview version of 2.0
Sent from my SM-G955F using XDA-Developers Legacy app
Anybody got Android Pay working on the watch anyway?
Android Pay doesn't work on the preview. I've read several posts with similar results. AP is the main, and probably only, reason I'm curious to try 2.0 if it's EVER released.
Android Pay finally works on the final version of AW2 for the W200*
The only way at the moment is to sideload it because the update have been release just in korea: http://android.googleapis.com/packa.../af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8.zip
Hey all, any news on this since WearOS came out? I'd been looking for confirmation on whether Pay would work on the Urbane, and whether it would work with a rooted phone connected. Also I read somewhere that Pay on watches doesn't actually sync with Pay on phones (like it doesn't automatically pull in the same cards I think?), so I was wondering if maybe you could have Pay JUST on a watch and not even bother with hiding root on the phone. Any thought or updates? Did you get Pay working on your Urbane once WearOS came out? Thanks!
Hi all,
I've had my LG Watch Sport since the beginning of the year and Android Pay worked fine in Android 7.x on this device. Since the update to Android 8 it is always disabled. I have manually re-enabled it and updated it which then it works for a short while, then it disables itself again.
I've used it fine and the bank I am with supports this, but it is starting to frustrate me that this function has now gone (well, not really, just have to re-enable the app every time I want to use it so not convenient) when I have gotten so used to it. I can use it on my phone fine.
The Android Wear version from the watch information is 2.7.0.1778645119 and there do not seem to be any other updates available at this time.
Someone on one of the Google threads has indicated that it is due to the region being locked on these devices - so if you are not in the US or UK, you cannot use Android Pay.
I am curious to know if you are experiencing this issue if you are located in the US or UK. There doesn't seem to be too much noise in the forums here about this, so I am guessing it is working fine for the US and UK folks where this is supported.
Also wondering if anyone knows how it determines its location - whether it is like the Microsoft Band 2 where you can set your phone up as US first, then change your time zone, etc to your location and keep using it, or if the new Android Wear and Android Pay do a GPS lookup on the watch before operating.
If this works fine for all our US and UK owners, maybe we can set the watch up thinking it is in a different location and see if it gets disabled? It would seem silly to have it disable once set up, as I would forsee travelling with this device and just being able to conveniently use this for both store cards and credit card without having to bring anything else.
I can not believe this, it do not want either.'
Any country that supports Android Pay the app should work
deswong said:
Hi all,
I've had my LG Watch Sport since the beginning of the year and Android Pay worked fine in Android 7.x on this device. Since the update to Android 8 it is always disabled. I have manually re-enabled it and updated it which then it works for a short while, then it disables itself again.
I've used it fine and the bank I am with supports this, but it is starting to frustrate me that this function has now gone (well, not really, just have to re-enable the app every time I want to use it so not convenient) when I have gotten so used to it. I can use it on my phone fine.
The Android Wear version from the watch information is 2.7.0.1778645119 and there do not seem to be any other updates available at this time.
Someone on one of the Google threads has indicated that it is due to the region being locked on these devices - so if you are not in the US or UK, you cannot use Android Pay.
I am curious to know if you are experiencing this issue if you are located in the US or UK. There doesn't seem to be too much noise in the forums here about this, so I am guessing it is working fine for the US and UK folks where this is supported.
Also wondering if anyone knows how it determines its location - whether it is like the Microsoft Band 2 where you can set your phone up as US first, then change your time zone, etc to your location and keep using it, or if the new Android Wear and Android Pay do a GPS lookup on the watch before operating.
If this works fine for all our US and UK owners, maybe we can set the watch up thinking it is in a different location and see if it gets disabled? It would seem silly to have it disable once set up, as I would forsee travelling with this device and just being able to conveniently use this for both store cards and credit card without having to bring anything else.
Click to expand...
Click to collapse
I have the same issue. I have had LG Watch Urbane 2nd before and there had been Android Pay working well. Now I have to enable it after approx. 1 hour.
I've got the watch one week ago, there was Android 7.1.1. I had to join beta testing, then I got Oreo.
My country is suported by Oreo and also Android Pay is supported (Czech republic)
Has anybody an idea how to fix this? Very annoying.
Android Wear 2.7.0.178645119
Andtoid OS 8.0.0
Services 11.9.51
1st October 2017
Build OWR1.170919.023
I've got the watch one week ago, there was Android 7.1.1. I had to join beta testing, then I got Oreo.
Android Wear Beta did disable Android Pay.
This is why I refused to sign up for the beta program.
But I got final Oreo, not beta.
I live in Spain LG Watch Sport with Oreo, and I have the same issue[emoji852]️
Enviado desde mi SM-G930F mediante Tapatalk
Seems like many people are seeing this, me I will refuse any update until I an sure Android Pay will work.
I purchased the watch because it has NFC and Android Pay support.
I live in Taiwan LG Watch Sport with Oreo, and I have the same issue️.
LG or Google should face & fix this problem.
It's a problem for all devices with Oreo, not only LG Watch Sport
Enviado desde mi SM-G930F mediante Tapatalk
Do you mean all devices or only all wearables? Should I stop upgrading to Oreo on my phone?
libb said:
Do you mean all devices or only all wearables? Should I stop upgrading to Oreo on my phone?
Click to expand...
Click to collapse
All wareables
Enviado desde mi SM-G930F mediante Tapatalk
Lots of good info here.
Having read this and upgraded both my smartphone and my watch to Oreo 8, I tried Pay today. And it did work with both the LG watch sport and my Oneplus 5 (rooted). Suprisingly, the Pay on the smartphone now worked in a shop where I could not pay with smartphone/smartwatch before.
.....
Keep in mind only Non-Americans seem to have issues
How to make a downgrade - Android 7.1.1 Nougat, I really need Android Pay. Does anyone have a factory image?
AstroDigital said:
I can not believe this, it do not want either.'
Any country that supports Android Pay the app should work
Click to expand...
Click to collapse
Android Pay on Android Wear supported only in US and UK
I'm Huawei Watch 2 user also probably soon affected by this. To work around this, I prepared a proxy app that takes only two more taps to enable and launch Android Pay. https://forum.xda-developers.com/android-wear/development/app-pay-enabler-android-pay-oreo-t3750815 Any thoughts/feedback?
Thank you. I appreciate it but we should pust to Google to enable it.
I tried the application and I like it.
One suggestion: is possible to check if Android Pay is enabled and if not, display the page for enabling, if yes, start AP? Then I could set hardware button to your application and it would start what is necessary.
EDIT: I checked source code and you alreadyd did it! Thanks, it works well!
moneytoo said:
I'm Huawei Watch 2 user also probably soon affected by this. To work around this, I prepared a proxy app that takes only two more taps to enable and launch Android Pay. https://forum.xda-developers.com/android-wear/development/app-pay-enabler-android-pay-oreo-t3750815 Any thoughts/feedback?
Click to expand...
Click to collapse
Thank you~
Your app helps us a lot~ :good:
Hey all!
I'll do the long story short: I am stuck on a Korean Note 9 in Europe, which means no Samsung pay for me.
Now, since I can't get Samsung Pay, and I saw I can't instal Google pay either(not sure why the Play store wouldn't let me), I have been contemplating before setting up my Note, to maybe root it, and going stock european ROM.
I have rooted multiple phones in the past, but I am not sure if it's worth it in the present, as the UIs are pretty good and complete.
Now my question is, do I lose anything else by rooting? Could someone Eli~10 what that knox fuse tripping means for future limitations/possibilities? Also, besides my reason to set custom dpi for an app, why else would one root its Note 9 nowadays?
Thanks!
I'm pretty sure you lose Private Folder and maybe Samsung Health if you root. I'd consider rooting only for Viper4Android & the YouTube Background Playback xposed module. But I saw there is xposed for non-rooted phones & Note9 has Dolby Atmos so I think this will be my first android phone that I won't root (don't even need root anymore).
It is personal preference, but all apps that require Knox will cease to work, so almost all payment apps will be of no use. While the first comment said S Health would no longer work, months ago a workaround was found to get it to work. Many apps I like require root, but there are nonroot workarounds for most of them.
Snowby123 said:
It is personal preference, but all apps that require Knox will cease to work, so almost all payment apps will be of no use. While the first comment said S Health would no longer work, months ago a workaround was found to get it to work. Many apps I like require root, but there are nonroot workarounds for most of them.
Click to expand...
Click to collapse
And which are specifically the apps that require Knox to work?
I don't know all of them. The only ones I know are Samsung Pay, Samsung Pass, Secure Folder, and Adhell, but development of Adhell ceased months ago. There are definitely more.
I had the same dilemma when I first bought my Note 9. For a couple of seconds. Then, I rooted it as I do with every Android phone I get since 2009.
Any app, website, or service that demands a non-rooted device goes automatically to my black list.
I've been using an s20 FE 5g. It's a great phone but touch screen issues, of course you can't root the thing and avoid mandatory software updates, news about the glass over the camera breaking, I also just got really tired of not being able to control my own phone. So I bought a used s9 exynos.
I went through a couple of root tutorials online but the one that finally worked was: https://www.thecustomdroid.com/samsung-galaxy-s9-plus-root/
With other methods I kept getting boot loops and couldn't mount the system.
Anyway, this seems to have worked for me, so I'm putting it out there in case anyone needs it. And now some terms in case someone does a google search:
root galaxy s9 android 10 sm-g960f
Have you been able to restore all or some of the functionality that's lost by tripping Knox, such as Secure Folder, Samsung Health, Samsung Pay, Google Pay, iris scanner, logging into secure apps with the fingerprint reader? I've read about MagiskHide but apparently that doesn't work for everything, and I've seen some application-specific instructions, but I'd very much like to hear from someone who knows from experience what lost functionality can be restored and what gotchas you can run into.
kettir said:
I've been using an s20 FE 5g. It's a great phone but touch screen issues, of course you can't root the thing and avoid mandatory software updates, news about the glass over the camera breaking, I also just got really tired of not being able to control my own phone. So I bought a used s9 exynos.
I went through a couple of root tutorials online but the one that finally worked was: https://www.thecustomdroid.com/samsung-galaxy-s9-plus-root/
With other methods I kept getting boot loops and couldn't mount the system.
Anyway, this seems to have worked for me, so I'm putting it out there in case anyone needs it. And now some terms in case someone does a google search:
root galaxy s9 android 10 sm-g960f
Click to expand...
Click to collapse
Thanks! I had the same experience you had trying to root my S9 Plus (SM-G965FD) on Android 10 One UI 2.5. This guide worked for me!
As the title says, even though this phone is not even two years old I am already finding apps that are no longer supported.
As of writing the apps that are currently showing up as no longer compatablie with this device are:
Netflix - preinstalled app asks for an update but never does, says no longer supported.
Final Fantasy XIV Compainion app - Says there was an update but says no longer supported.
Is anyone else able to confirm this happening on there device to, or is there somethign with my phone (I have even did a factory reset to wipe all data)
XQ-AT51
Build Number 58.1.A.5.530
Android 11
Security update 1 December 2021
Google Play System Update 1 January 2022
I find this really werid considering my brother has an Nokia 9 Pureview which both these apps still work on. I am guessing over the coming months more apps will start to not be supported making me start to regret buying this phone.
Netflix works great for me (current Netflix version per Play Store; and Android 12 on my phone).
JamesMiami said:
Netflix works great for me (current Netflix version per Play Store; and Android 12 on my phone).
Click to expand...
Click to collapse
Weird I wonder why google play is telling me the app is no longe supported on my device.
My phone was a XQ-AT52 which I flasehd to a XQ-AT51, but I can't imagine that causing any issues. Hell the only issue it does give me is that Xperia companion app will give me a error if I try to repair the phone.
Normally, the built-in versions are updated when there's a newer version in the Play store. It does on my phone. Maybe the rights management doesn't work anymore because the device is flashed or rooted?
Sorry for bumping this old thread, this may not be the right place to comment but I have the exact same issue on Xiaomi Redmi Note 10 Pro with the same two apps. I previously installed PixelOS on it, but decided to go back to European stock rom, and that's when I noticed the issue.
Edit: Fixed. I just had to lock the bootloader again.
no. just uninstall stock netflix then install from apkmirror if google still say incompatible. sony use spesial netfilx app that in deed no longer supported