Database Develop

Urbane 2 on 2.0 can't get Android pay working on watch?

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!

Android Pay on LG Watch Sport W281

Copied from the other thread as I thought I would get more responses in a dedicated one;
I was one of the early adopters of the first Moto 360 (2014 - Gen1) and decided to upgrade to a Wear 2.0 device. Bought the LG Watch Sport LTE W281 Titanium from eGlobal UK (Hong Kong 'region free model') as I wanted one with both Google Assistant and NFC for Android Pay from the wrist. It was a toss-up between this and the Huawei 2, but preferred LG's design as an official Google model ('designed by Google').
Deleted the Moto 360 profile and paired up via the Android Wear app. Everything went smoothly.
Android Pay worked more or less out-of-the-box, it didn't prompt me to re-enter my card details, just copied them off the phone. Had to authenticate on the phone and give permission to copy the details across, but other than that it was automatic. Have used it in McDonalds, Tesco, various coffee spots etc with no issues.
One issue though, I have not been able to get it to work with TfL/London Underground, transit or busses. Every time I get a red light and a 'Card not accepted - seek assistance' message. Tried a few times with no joy. Anyone managed to get this to work? Would having a direct data connection on the watch (SIM) make a difference? As I can use my phone on the underground and it even works offline (i.e. underground, no signal).
I can get my phone to work flawlessly on both and I don't think it needs a 4G signal to make small transactions (I'm sure there's a limit) but the watch won't make transit charges even with signal from the phone.
Contactless bank card works on both retail and transit, Android Pay from the phone works on both retail and transit, Android Pay from the watch will only work at retail. I tried clearing the app cache but no joy. Looking for any advice or tips, things to try. Thanks in advance.

So it seems at least one other UK user on Reddit has tried using this on the underground....successfully. With a Huawei 2.
As it's a different model, which actually got launched over here, I'm assuming this issue is one of three things;
1) Issue with the LG Watch Sport not being an official UK model (unusual as it works as a standalone offline payment method).
2) TFL don't allow more than one device to share the same bank card (cannot find any information to affirm this theory).
3) TFL have some kind of model-specific whitelist to prevent fraud (seems very unlikely as it would have to be constantly updated).

EMUI 10 / Android 10, problem with Google Pay

Anyone else experienced problem with Google Pay after update?
It worked extremely well for me up until the update, then all of the sudden it doesn't work any more.
I checked the settings inside Google Pay, but all seems well. Card is registered and everything.
When holding my phone up to the terminal there is no reaction from the phone at all.
What can I do to fix this?

I have exactly the same, but with my normal banking app. It can also do payments via NFC, but when I hold it up to a terminal nothing happens like you said.
I'm now factory resetting my phone to see if that helps, I'll let you know!

Gfhoihoi72 said:
I have exactly the same, but with my normal banking app. It can also do payments via NFC, but when I hold it up to a terminal nothing happens like you said.
I'm now factory resetting my phone to see if that helps, I'll let you know!
Click to expand...
Click to collapse
Thanks! Looking forward to your feedback if this works or not.

TordFuglstad said:
Thanks! Looking forward to your feedback if this works or not.
Click to expand...
Click to collapse
Nope... Unfortunately not. Maybe I'll just downgrade to Android 9 and wait until a new patch for Android 10 comes out where they fix this.

No problems here, working as before

EnormoDerClown said:
No problems here, working as before
Click to expand...
Click to collapse
What firmware version are you on?
I've downgraded to Android 9.1 and the mobile payment is working perfectly again, so it's definitely an issue with Android 10. So if you really want to use it, you can downgrade for now. Otherwise just wait for the next Android update and hope that it gets fixed.

Same here in France, Google Pay says Phone moved too fast.
Can pay with one other bank's app, but not the other one's. (both Georgian banks)
They did warn in changelog that some banking apps are not working due to their compatibility issues with Android 10, though

giosal said:
Same here in France, Google Pay says Phone moved too fast.
Can pay with one other bank's app, but not the other one's. (both Georgian banks)
They did warn in changelog that some banking apps are not working due to their compatibility issues with Android 10, though
Click to expand...
Click to collapse
True, that changed the way apps can use your IMEI and this was the way most banking apps verified your phone. But my banking app should be compatible with Android 10 and it is working for some people but not for others.

Gfhoihoi72 said:
What firmware version are you on?
I've downgraded to Android 9.1 and the mobile payment is working perfectly again, so it's definitely an issue with Android 10. So if you really want to use it, you can downgrade for now. Otherwise just wait for the next Android update and hope that it gets fixed.
Click to expand...
Click to collapse
10.0.0.168. "normal" update. Not a member of the beta or anything, just normal OTA. Working exactly as on Android 9. Also tested/used with different cards/institutes in google pay. Working like a charm

Same problem here, Google Pay worked perfectly in 9.1. Now, with 10.0.0.173 there's no response when near terminal. No error messages anywhere. NFC works fine, e.g. ReadID to read the NFC chip in my passport.

The same here, but I have a mate 20 pro. After the update to Android 10 I can no longer pay with Google pay.
From Germany

Updated yesterday and works fine for me in UK

So i better stop an update i am asked to update to 173 and stay on my 168 It is working for sure on 168 for me. Used it quite often

I solved the problem on my P30 Pro. I was using a "twin SIM" card from Ice (service provider). When I switched sim cards to my main SIM, Google pay works as before. The twin SIM worked fine with Android 9. I think the problem is that the twin SIM does not have the real phone number, but some long code that the phone system somehow recognizes, but causes issues in some scenarios e.g. iMessage on iPhone which cannot verify it. That's why I had the twin SIM in my P30 Pro.
EDIT: The iMessage problem is caused by the fact that only the main SIM receives "class 0" or flash SMSs, used for iMessage's verification.

I'm having the issue with my UK region VOG-L29 that's running .173. I rarely use Google pay, so I'm not sure if it was working before the upgrade. Google Pay works fine on my Fossil Wear OS watch that's tethered to the phone. NFC also seems to work fine when connecting my camera to the phone.

Have also the problem of nfc payments (with gpay and postfinance app) not working after updating to Android 10. Full reset didn't help currently on version 10.0. 0.173 and still not working.
Huawei support doesn't know anything about this and said I should wait for app updates and/or emui update.not very helpful...
Uninstalling gpay and deleting the cards linked to it and setup everything from scratch didn't help either. Nfc hardware seems to work as I can trigger my bt connection with my nfc enabled headset.
Hopefully Huawei sorts this out quickly as it is very annoying since I used nfc payment almost every day on emui 9.1

Any solution for this problem? I also used the ohone to pay and the point is that it is a big inconvenience that there is no solution

Waiting for Huawei to fix the damn bug in their next update (hopefully). Downgrading or resetting and so on is a pain when the affected phone is your daily driver.

Been using GPay already multiple times with 10.0.173.
No problems here in germany.
Regards

Same here!
Updated yesterday to EMUI 10 and realized today that I could'nt pay at the terminal. Bad situation without credit cards
Seems like NFC does not work at all. When I try to read my credit cards with NFC Tools, there is no reaction from phone as before.

Android Auto for phone screens is final stopped?

Even the Android Auto for phone screens was retired for Android 12, you can still use it on old Androids 11, 10. A month ago a message appear "Android Auto for phone screens will stop working soon", but still can use it.
Today I tried to start the app and instead appear the Android Auto settings page and no more Android Auto for phone screens. I have Miui 12.5.7 with Android 11 and Android Auto 7.6.621734-release.
Its only me or they kill out AAFPS for good?

For me the same...

Android Auto is now on the scrap heap; in short it will no longer work as a stand-alone.
Google have thrown a kill-switch (2 days ago now) for discrete mode so that now, it can only work in screen-mirroring mode which necessitates a compatible infotainment system/head unit (check the message it opens with).
The official alternative on offer is Driving Mode in the Google Assistant. It's of dubious quality, especially for devices older than Android 10, where it really is just a shortcut to Google Maps.
Alternative apps/launchers are available but they are either expensive or just plain rubbish (and often both).

I'm sorry to hear this is confirmed. So no more Android Auto, I don't have a compatible infotainment system/head unit.
Driving Mode in the Google Assistant is a just simple no-go. Here in Romania we use a lot Waze for police report, traffic jams and bad roads. Also since romanian language is not supported , you can spell some small commands in english, but to convince it to drive you at address or even to call your mom is very difficult.
So now I'm without alternative .

triovi said:
...So no more Android Auto, I don't have a compatible infotainment system/head unit...
...So now I'm without alternative .
Click to expand...
Click to collapse
Indeed - and you are not alone as many reviews on Google Play confirm.
One other option is to roll-back to an older version. If you don't have a backup then APKMirror might be for you:-
Android Auto on APKMirror
FWIW we have an older, 7/Nougat device running ver 7.4.62094-release and it seems to work still.
If you do try this, then be sure and disable auto-update for it in Google Play...

xanda-escuyer said:
FWIW we have an older, 7/Nougat device running ver 7.4.62094-release and it seems to work still.
If you do try this, then be sure and disable auto-update for it in Google Play...
Click to expand...
Click to collapse
I'll give it a try: my Renault Megane is half destroyed and now I have to use (for long time) a Seat Leon without AA enabled!
I've started AA on my old (but still running fine) Motorola Moto G5 and is not working anymore... Problem is that the phone is running Android 8.1 so Drive Assistant is not available (it needs at least Android 9!)

xanda-escuyer said:
FWIW we have an older, 7/Nougat device running ver 7.4.62094-release and it seems to work still.
Click to expand...
Click to collapse
GCalzo said:
I'll give it a try
Click to expand...
Click to collapse
on my pc I had a few backups, I have removed the current build and installed Android Auto_7.2.620123-release and it worked flawlessly!
I'll look for a more recent build on APKmirror!
Addendum: tried with v7.6 but got the advice. For my Android v8.1 the last working is v7.2!

Thank you for this thread!
This has been nagging me more than usual as AA for Phone Screens was something I've used daily. (strong feedback sent to google, not that it will do any good)
Tried with app version 7.3.620544 on Android 11 and I can launch it a few times, all good and functional. But after a few hours an internal update seems to check the installed and Play store versions, preventing me from starting the application without updating. So reinstall APK again. (a hassle)
Tried creating a re-signed version with Android Studio to block auto-updates, but the re-signed APK install itself is blocked due to signature mismatch - even after uninstalling for user 0. I fear this might be only possible with rooting the phone...
I would very much appreciate any other non-root option to get this functioning again. Curse you google for ruining google.

I also tried to modify the apk.
I was not successful. Therefore I gave up...

Google are literally murderers , besides all the people they have stranded or driven of the road or over ravines with their crappy maps app
they have probably killed thousands in traffic accidents with their garbage software
,this new "driving mode" is no exception , I mean AA was an absolute out of control garbage fire just like GA is but this "driving mode" is over the top
even for the complete morons over at Google.
I can not tell you how many accidents I have almost got into since they removed trusted voice unlock and now that this POS driving mode has replaced AA it has gotten MUCH worse, they should be sued for this dangerous crap they have forced on us, I will NOT be buying another pixel EVER.
fist of all this POS continually turns the screen off and locks the device forcing me to unlock the phone continuously while driving,
they are so S all stupid they didn't even bother to make it rotate to landscape mode and my car mount is for landscape only. (only people who hold their guns sideways would want to use their phones in portrait mode as they always seem to do when taking word star videos)
the "driving mode" is pure trash ,there are no audio controls, you can't use it if you just want to listen to music and for phone calls because it's tied to maps and you have be using navigation to use it.
there is NOTHING here of any value I mean who TF wants to read the New York Slimes, ever and especially WHILE DRIVING, yeah great replacement to music apps and music controls.
There is no way in hell I would ever give these evil bastards my biometric data so here I am trying to unlock my phone with a pattern every 30 seconds while it is mounted landscape and the unlock pattern is in portrait mode, I have to tilt my head or try and figure out my lock pattern adjusted for it being tilted 90 degree off while I'm driving every 30 seconds because the screen keeps turning off and locking the device even though I have "smartlock" (DUMBlock) enabled and my cars bluetooth added as a "trusted device" as well as a smart band, but it just seems to ignore the fact both are connected.
how in the actual F do any of these imbecilic A holes still have jobs, every single last one of them should have been kicked the F out on their arses a long time ago. , maybe we need to get Elon over there.

SOFO888 said:
I also tried to modify the apk.
I was not successful. Therefore I gave up...
Click to expand...
Click to collapse
please don't give up and keep trying other wise I am switching back to IOS, I just can't deal with this S
maybe I can throw away my pixel 3a XL and just go back to my old 6p on Nougat
this is not acceptable, what other options are there, I have an echo auto I never set up maybe that will be better.

peetig said:
Thank you for this thread!
This has been nagging me more than usual as AA for Phone Screens was something I've used daily. (strong feedback sent to google, not that it will do any good)
Tried with app version 7.3.620544 on Android 11 and I can launch it a few times, all good and functional. But after a few hours an internal update seems to check the installed and Play store versions, preventing me from starting the application without updating. So reinstall APK again. (a hassle)
Tried creating a re-signed version with Android Studio to block auto-updates, but the re-signed APK install itself is blocked due to signature mismatch - even after uninstalling for user 0. I fear this might be only possible with rooting the phone...
I would very much appreciate any other non-root option to get this functioning again. Curse you google for ruining google.
Click to expand...
Click to collapse
F it, I am just going to throw away my pixel and go back to IOS
I am F ing done , removal of trusted voice unlock was bad enough but this is the last straw.

My idea is to install an alternative launcher as soon as you are connected to your car's Bluetooth system. I mean a launcher made for driving with big icons and so on.
With tasker you could additionally make a task to increase the display timeout to infinite when connected to your car's Bluetooth system.

gdroid666 said:
F it, I am just going to throw away my pixel and go back to IOS
I am F ing done , removal of trusted voice unlock was bad enough but this is the last straw.
Click to expand...
Click to collapse
Goodbye.

gdroid666 said:
how in the actual F do any of these imbecilic A holes still have jobs,
Click to expand...
Click to collapse
Because they have done exactly what The Chocolate Factory wants.
Android Auto was quite good in the past but then they realised a serious problem: It hurts sales.
So the aim then became to make everybody sick of it by degrees, breaking it a piece at a time until expectations reduce to the point the user base ebbs away.
So what's in it for them? Google are betting that Android's 'popularity' will oblige most of us to seek an alternative - but only if works with their device; that means buying a new infotainment system - one that is either Android Auto or stand-alone Android.
Google and OEMs (JVC, Kenwood, Pioneer etc) now have another major market cornered and if they have done their math right, all of us switching over will mean a windfall of revenue in new hardware sales and licence fees.
As for looking for a launcher, well good luck with that. We've tried several but not one has the ability to switch between driving and phone mode.
These two probably represent the best of what's left but again, neither is properly polished even for the paid versions:-
DashDroid on Google Play
AutoMate on Google Play
Failing that, get a TomTom!
gdroid666 said:
maybe we need to get Elon over there.
Click to expand...
Click to collapse
Oh please no - anything but that - no no no no....

xanda-escuyer said:
Because they have done exactly what The Chocolate Factory wants.
Android Auto was quite good in the past but then they realised a serious problem: It hurts sales.
So the aim then became to make everybody sick of it by degrees, breaking it a piece at a time until expectations reduce to the point the user base ebbs away.
So what's in it for them? Google are betting that Android's 'popularity' will oblige most of us to seek an alternative - but only if works with their device; that means buying a new infotainment system - one that is either Android Auto or stand-alone Android.
Google and OEMs (JVC, Kenwood, Pioneer etc) now have another major market cornered and if they have done their math right, all of us switching over will mean a windfall of revenue in new hardware sales and licence fees.
As for looking for a launcher, well good luck with that. We've tried several but not one has the ability to switch between driving and phone mode.
These two probably represent the best of what's left but again, neither is properly polished even for the paid versions:-
DashDroid on Google Play
AutoMate on Google Play
Failing that, get a TomTom!
Oh please no - anything but that - no no no no....
Click to expand...
Click to collapse
Thing is most cars don't have it still
the stand alone android units just suck because they don't have any connection method unless they use your phone as a hotspot , unless they have some with sim cards, but now sim cards are being phased out too, and I would not spend more money a month just to keep my head unit connected to GSM
I would buy a head unit if they made one that had wireless android auto baked in but there are none, at least not what I want, I want one for my BMW E46 that looks pretty close to stock, Android head units like that are a dime a dozen for this thing but none of them have AA or wireless AA
,what they should really make is a tablet that has wireless AA built in
or a fire tablet that acts as an echo show auto but with a screen
that you can mount to your dash ,sucks that all the hardware has been there to this for like a decade but because of theese big cancer monopolies we can't use the hardware to its full potential
I have yet to try reloaded yet but I have feeling it will not be good
but here is no reason this can't run on low end tablet like a fire tablet
maybe I will finally get around to trying out my echo auto that I picked up for $20 that has been sitting here not even unboxed for over a year now
thing is that my grom unit is a PITA to pair to my phone , you need to pull 3 different fuses to erase it and repair a new device and then once you do the feature that send the ID4 tags to the display on the radio might not work then you have to pair it all over agian , I am wondering if echo auto will send the track data to the grom and if it will display on the stock radio display like it does with the phone , then maybe I will just ditch GA altogether
its a horrible trash fire anyways , if Amazon made a fire phone again with hands free Alexa baked in I would buy it in hearbeat, anything to get rid of GA

mike.s said:
Goodbye.
Click to expand...
Click to collapse
Yeah ok ,see ya, I was thinking about buying a 7 pro but not now
F Google , I will NEVER buy another phone from them until they bring back trusted voice unlock and make their phones useable while driving
android is a nothing but a trash fire now, mainly because GA just sucks now
doesn't work while driving , doesn't work with hands free at all not even while using buds, unacceptable trash OS and very dangerous to use while driving people will die in accidents because of Googles moronic decisions and negligence, again F Google I'm out.

gdroid666 said:
Yeah ok ,see ya,..
Click to expand...
Click to collapse
Many of us share your frustration and of course, you are at liberty to try alternatives if you think they are better.
Yet this is primarily a help thread and some would say your 'questions' had been answered before you even posted. So please bear in mind that 'going-off on one' does dilute the thread; making it harder for others to find the help they need as it becomes buried in the noise.
Good luck in your quest...

xanda-escuyer said:
Many of us share your frustration and of course, you are at liberty to try alternatives if you think they are better.
Yet this is primarily a help thread and some would say your 'questions' had been answered before you even posted. So please bear in mind that 'going-off on one' does dilute the thread; making it harder for others to find the help they need as it becomes buried in the noise.
Good luck in your quest...
Click to expand...
Click to collapse
Yes everything Google does frustrates me, these people are absolutely obtuse
ok so do you have any suggestions for alternatives?
maybe there is a 3rd party app?
I have a Grom bluetooth unit and they have an app called dashlinq but I have not tried it yet
not sure how it will work with Google assistant
so are there any other 3rd party apps that do essentially the same thing as AA?
not sure if this dashlinq app uses GA or not or if it has it's own voice recognition.
I am surprised that there is not a way to keep using AA though as there is with Google play music ,which you can stil use if you have the right legacy version installed despite its replacement with YT music.
I am still confident there is a way, and also a bit confused
on weather it is going to work on my phone still since I have not updated past Android 11 , guess I will try installing some older .apk's and see if it is only not working anymore on Android 12.

gdroid666 said:
I'm out.
Click to expand...
Click to collapse
You keep saying that.

Question Android Wear OS

Can Wear OS run on the X Fold?
I have TAG connected watch and I read that it does not work with Chinese ROM

I have the TicWatch 3 PRO Ultra and although it was a pain in the ... to make it work, Managed it with both the Chinese and Play versions of the Wear OS app installed together. it is fiddly but eventually, it works. Also, I get all the notifications on the watch (even the ones that will not show up on the phone...

dee163 said:
Thanks for the feedback
Click to expand...
Click to collapse
Can you direct me a tutorial for this ?

dee163 said:
Can you direct me a tutorial for this ?
Click to expand...
Click to collapse
Tutorial unfortunately no as I did not follow any... First tried installing Wear OS from the Play store but it was not finishing the setup. Then I downloaded Wear OS from the Vivo store (the so-called Chinese version. This one does not have any Google Account integration) I gave all possible permissions to both of them (yes, they can be installed at the same time.) Then somehow the Play Store version worked and connected to the watch. I installed also the TicWatch App that is needed (in my case. Guess TAG has one too) and after some more fiddling with notification permissions, it just worked. I get all my notifications and everything seems to sync properly.
I hope that they will really release the phone in India next month, as usually, the Indian releases are Global ROMs with more compatibility with everything. Then we should be able to flash it on our devices...

I have my Galaxy Watch connected.
First loaded the Chinese Wear app, then the Galaxy Wear app.
BUT it won't stay connected. It's OK while the phone is open, but as soon as the phone logs off the Bluetooth disconnects.
I've given the Wear apps every possible permission and power settings but it just won't stay connected.

Just to update from my last post, I've decided to trade in my Galaxy Watch 3 for the new Watch 5. Will be interested to see if that makes any difference. Probably not

I have the same issue - cannot keep my galaxy watch connected (it's the 1st gen)
All is fine and after a while it just disconnects.
The galaxy Buds Live are fine and keep connected.
I'm using the Galaxy wearable app. (as these devices are not Wear OS i think)

Morb81 said:
I have the same issue - cannot keep my galaxy watch connected (it's the 1st gen)
All is fine and after a while it just disconnects.
The galaxy Buds Live are fine and keep connected.
I'm using the Galaxy wearable app. (as these devices are not Wear OS i think)
Click to expand...
Click to collapse
My Watch 5 is due later today. I'll be interested to see if that stays connected.

RR-99 said:
My Watch 5 is due later today. I'll be interested to see if that stays connected.
Click to expand...
Click to collapse
No success with the Watch 5, as I reported in a separate thread. I'll wait for the Pixel Watch.

Got my Galaxy watch (1st gen i guess) successfully paired and it keeps connected. As long as the 2 devices are bound. (once disconnected i have to reconnect via the wear app - no big deal)
Thing is though - battery usage of the watch is through the roof. I hardly get a full day out of it.
Anyone know what might be causing this?

Morb81 said:
Got my Galaxy watch (1st gen i guess) successfully paired and it keeps connected. As long as the 2 devices are bound. (once disconnected i have to reconnect via the wear app - no big deal)
Thing is though - battery usage of the watch is through the roof. I hardly get a full day out of it.
Anyone know what might be causing this?
Click to expand...
Click to collapse
First gen Galaxy Watches did not have a very good battery life to begin with... 1.5 to 2 days at most with good use. Another thing is that the connection between the watch and the phone is not stable for some reason (probably due to the stupid Vivo battery optimizations or some Bluetooth issue)... For instance, my Ticwatch Pro 3 Ultra GPS (names those things) lasted about 3 days with my old Galaxy S21 Ultra but now I struggle to get 2 with the Vivo X Fold...

Which Watch work with X Fold ? It seems no one actually. i have 2/3 Xiaomi, nothing work and it's not Band !!

Samsung Watch 3 works. Samsung Watch 5 does not work.
I now have Huawei GT3 pro and it works perfectly. Does not use Wear. Great battery life, eight days so far !

I agree nt so bad... nothing better than others... But qualitative.
Everything work ?

lesscro said:
Which Watch work with X Fold ? It seems no one actually. i have 2/3 Xiaomi, nothing work and it's not Band !!
Click to expand...
Click to collapse
Huawei models works without problems

maxant69 said:
Huawei models works without problems
Click to expand...
Click to collapse
Good to know !

OrionBG said:
Tutorial unfortunately no as I did not follow any... First tried installing Wear OS from the Play store but it was not finishing the setup. Then I downloaded Wear OS from the Vivo store (the so-called Chinese version. This one does not have any Google Account integration) I gave all possible permissions to both of them (yes, they can be installed at the same time.) Then somehow the Play Store version worked and connected to the watch. I installed also the TicWatch App that is needed (in my case. Guess TAG has one too) and after some more fiddling with notification permissions, it just worked. I get all my notifications and everything seems to sync properly.
I hope that they will really release the phone in India next month, as usually, the Indian releases are Global ROMs with more compatibility with everything. Then we should be able to flash it on our devices...
Click to expand...
Click to collapse
I have a Vivo X Note and also a TicWatch Pro 3 Ultra. Wear OS works well together with the Chinese version. The only and for me the biggest problem is that I cannot pay with a card via Google wallet from watch. When I open the apk and want to add a payment card, it says a connection error with my mobile phone, and on my X Note Wallet does not open through google play services, and I cannot add the card to the watch. I have no problem with paying on my mobile, Wallet works ok there. If I connect the watch to the Lenovo Yoga Tab tablet, Wear OS from the Google Play Store works there without any problems, and I also add all the cards to the Wallet in the watch. I read on the forums that the problem is with the new versions of the Google Play services and that it will help to downgrade the older version lower than 21.26.58. The problem is that when installing, the system gives an error and cannot be installed... So at the moment I have a working watch, but no payment, which is frustrating. Have you tried paying with your watch?

Kucko34 said:
I have a Vivo X Note and also a TicWatch Pro 3 Ultra. Wear OS works well together with the Chinese version. The only and for me the biggest problem is that I cannot pay with a card via Google wallet from watch. When I open the apk and want to add a payment card, it says a connection error with my mobile phone, and on my X Note Wallet does not open through google play services, and I cannot add the card to the watch. I have no problem with paying on my mobile, Wallet works ok there. If I connect the watch to the Lenovo Yoga Tab tablet, Wear OS from the Google Play Store works there without any problems, and I also add all the cards to the Wallet in the watch. I read on the forums that the problem is with the new versions of the Google Play services and that it will help to downgrade the older version lower than 21.26.58. The problem is that when installing, the system gives an error and cannot be installed... So at the moment I have a working watch, but no payment, which is frustrating. Have you tried paying with your watch?
Click to expand...
Click to collapse
I never got google wallet to work on mine too…

Kucko34 said:
I have a Vivo X Note and also a TicWatch Pro 3 Ultra. Wear OS works well together with the Chinese version. The only and for me the biggest problem is that I cannot pay with a card via Google wallet from watch. When I open the apk and want to add a payment card, it says a connection error with my mobile phone, and on my X Note Wallet does not open through google play services, and I cannot add the card to the watch. I have no problem with paying on my mobile, Wallet works ok there. If I connect the watch to the Lenovo Yoga Tab tablet, Wear OS from the Google Play Store works there without any problems, and I also add all the cards to the Wallet in the watch. I read on the forums that the problem is with the new versions of the Google Play services and that it will help to downgrade the older version lower than 21.26.58. The problem is that when installing, the system gives an error and cannot be installed... So at the moment I have a working watch, but no payment, which is frustrating. Have you tried paying with your watch?
Click to expand...
Click to collapse
I will never work, as Android Auto, Google backup, Google Timeline and Ok Google activation.
Vivo doesn't use a full Google Play Service framework as they have Jovi application instead of Google one.

Hello
Does anyone manage to make the Remote Connection work? It's missing in the Galaxy Wear settings.
I'm guessing it's related to the Wear OS China version app.