Related
I have been using android auto for the past 3-4 weeks flawlessly. However in the last day when I plug my phone in I now get the red page stating this device cannot work with android auto on the phone. I have tried everything from reinstalling the android auto app/clearing cache/data and the same for google play services to factory resetting the phone. Has anyone else encountered this? does anyone have any ideas?
Phone: Nexus 6, stock, never rooted, never unlocked
Headunit: Pioneer AVIC8100NEX
Edit: I've been messing around with this, I am starting to suspect the 7.3.29 update to google play services is the culprit. downgrading to 7.0.99 seems to make it work up until the google play service updates itself automatically. I've tried connecting the phone in airplane mode to prevent this but android auto doesn't launch at all when the phone is in airplane mode.
Send a bug report.
ma2885 said:
I have been using android auto for the past 3-4 weeks flawlessly. However in the last day when I plug my phone in I now get the red page stating this device cannot work with android auto on the phone. I have tried everything from reinstalling the android auto app/clearing cache/data and the same for google play services to factory resetting the phone. Has anyone else encountered this? does anyone have any ideas?
Phone: Nexus 6, stock, never rooted, never unlocked
Headunit: Pioneer AVIC8100NEX
Edit: I've been messing around with this, I am starting to suspect the 7.3.29 update to google play services is the culprit. downgrading to 7.0.99 seems to make it work up until the google play service updates itself automatically. I've tried connecting the phone in airplane mode to prevent this but android auto doesn't launch at all when the phone is in airplane mode.
Click to expand...
Click to collapse
Better send a bug report to Google and the Android Auto support team. After I took that update I had some problems with other devices, not sure where but there is a list of devices and applications that have switches to allow/not allow them and all of them were switched to off. Had to turn many of them back on for me to get any information from them. Don't know about the AA application. I have not used it much because there is no Pandora Radio support yet and I have not had to go on any long trips so all I've needed was the voice navigation from Google maps on my phone. Hoping Pandora gets added soon, then it will be all I ever use.
ma2885 said:
Edit: I've been messing around with this, I am starting to suspect the 7.3.29 update to google play services is the culprit. downgrading to 7.0.99 seems to make it work up until the google play service updates itself automatically.
Click to expand...
Click to collapse
7.3.29 is installed on my Nexus6, with the same HU, and I have no problems. Have you updated the avic8100NEX's firmware to 1.0.3?
Yea, I updated to 1.03 the first day I got it installed. There seems to be some people with a similar issue, and others dont experience it at all.
I started a post over at androidcentral http://forums.androidcentral.com/an...y-states-device-cannot-work-android-auto.html
Two others chimed in with the same problem. Started about the same time google play servivce update rolled out. But if that is the problem then I am at a loss why only a few of us are having this problem.
Yeah, I think the update caused issues on some devices. I tested with 6 different phones the other day. HTC One M8 w/ CM12 seems OK, as does MotoG stock or CM12, and I think GS2 w/ 5.1 ROM. GS3 was among the problem devices.
I see a permissions problem in the logcat; Google's own Android Auto app can't get the permissions it needs.
I'm not positive this is all directly related though.
What build of Android?
ma2885 said:
Yea, I updated to 1.03 the first day I got it installed. There seems to be some people with a similar issue, and others dont experience it at all.
I started a post over at androidcentral http://forums.androidcentral.com/an...y-states-device-cannot-work-android-auto.html
Two others chimed in with the same problem. Started about the same time google play servivce update rolled out. But if that is the problem then I am at a loss why only a few of us are having this problem.
Click to expand...
Click to collapse
Could be a combination of things, i.e. build version I,E,M,D,etc.
vvveith said:
Could be a combination of things, i.e. build version I,E,M,D,etc.
Click to expand...
Click to collapse
You nailed the nail on the head...
I think I've figured it out. It definitely is the google play services update 7.3.29 on a N6 running Android 5.0.1. I can out my SIM and block google play through my home firewalls then downgrade to 7.0.99 and it works flawlessly. I then manually updated to Android 5.1.0 with google play services 7.3.29 and it also works flawlessly. So my recommendation is to manually apply the 5.1 update. I just tried to go back to 5.0.1 and once 7.3.29 services come down it no longer works. And went back to 5.1 and it works again. Definitely an issue with 5.0.1 and google play services 7.3.29 combination.
All of this testing was done with factory images, the only non factory application installed was android auto. all partitions on the device were formatted prior to applying system images.
ma2885 said:
You nailed the nail on the head...
I think I've figured it out. It definitely is the google play services update 7.3.29 on a N6 running Android 5.0.1. I can out my SIM and block google play through my home firewalls then downgrade to 7.0.99 and it works flawlessly. I then manually updated to Android 5.1.0 with google play services 7.3.29 and it also works flawlessly. So my recommendation is to manually apply the 5.1 update. I just tried to go back to 5.0.1 and once 7.3.29 services come down it no longer works. And went back to 5.1 and it works again. Definitely an issue with 5.0.1 and google play services 7.3.29 combination.
All of this testing was done with factory images, the only non factory application installed was android auto. all partitions on the device were formatted prior to applying system images.
Click to expand...
Click to collapse
This also worked for me. I was so confused as to why my Nexus 6 all of a sudden didn't work with Android Auto... I was running 5.0.1 with the updated Google Play Services 7.3.29 (auto updated). Switched to a ROM with 5.1 and it works again. Thanks!
I've noticed a problem-bug in my P20 Pro It comes out in only one application so far, I fix it and it only returns if I turn off and on my mobile or reboot it.
I do not know if it's Oreo or P20, but when i open it, it says "Google Services are updating". To do so, I do remove Google Play Services and then update it to the latest version.
Any ideas?
Got the same issue and I think there are more people out there with that issue. I've read about people not being able to see the map in several apps. I have this same issue in telegram for example and it says play services are updating..
Here is a workaround for it.
https://forum.xda-developers.com/huawei-p20-pro/how-to/maps-app-t3788290
It's a pretty serious bug. I use uber a lot, at least I did before I got the P20 Pro.
If it's not fixed in the update I may have to consider selling it. That's if an update ever materialises of course!
Here some people with the same problem -> https://productforums.google.com/forum/#!topic/play/xfLz_9emKs0
would be good if can disable the app from auto-updating so left with a working version
Hey guys,
I posted a thread about this a while back and someone the other day replied with the reason why, at least it confirmed why mine wasn't working.
I opted in for the beta play services, which some of you might have too. The beta is not yet functional with the P20 Pro and we can't expect it to be functional because it's a beta version and stable releases exist.
I suggest leaving the beta and reinstalling the app, that's fixed the issue for me even after multiple reboots.
QuantumNetworks said:
Hey guys,
I posted a thread about this a while back and someone the other day replied with the reason why, at least it confirmed why mine wasn't working.
I opted in for the beta play services, which some of you might have too. The beta is not yet functional with the P20 Pro and we can't expect it to be functional because it's a beta version and stable releases exist.
I suggest leaving the beta and reinstalling the app, that's fixed the issue for me even after multiple reboots.
Click to expand...
Click to collapse
I don't appear to be in the beta program. Which version of Play Services are you running now?
I noticed many reviews of Play Services on the store complains about all kinds of other apps being broken now, no idea if they are all Huawei users or if it's a more general issue with the current version.
MikeMTS said:
I don't appear to be in the beta program. Which version of Play Services are you running now?
I noticed many reviews of Play Services on the store complains about all kinds of other apps being broken now, no idea if they are all Huawei users or if it's a more general issue with the current version.
Click to expand...
Click to collapse
I'm now running version 12.6.73
QuantumNetworks said:
I'm now running version 12.6.73
Click to expand...
Click to collapse
Same version as I mine. I haven't noticed it updating so it's presumably the one that caused me issues until I cleared the data. I haven't tried a reboot since - sounds from some of the other reports that it might trigger the problems again. If so I can try a reinstall of Play Services.
I had the same issue. All I did was clear the cache from settings -- Apps -- Google Play Services -- Clear cache. Worked fine so far, no more issues.
Kostas 741 said:
I've noticed a problem-bug in my P20 Pro It comes out in only one application so far, I fix it and it only returns if I turn off and on my mobile or reboot it.
I do not know if it's Oreo or P20, but when i open it, it says "Google Services are updating". To do so, I do remove Google Play Services and then update it to the latest version.
Any ideas?
Click to expand...
Click to collapse
seems to be a pretty big issue. deleting the app data helps for a few hours, but it comes back. i have an honor 8 and started getting really drastic battery drain and weird wifi issues, along with the google services are updating message. apparently google is working on it. it's 79405933 on issue tracker.
This is getting really infuriating.
Clearing data does sort it, but only temporarily. Also, I have a Wear watch, and clearing data wipes the connection, and it's a PITA to reconnect it without resetting the watch.
Issue is fixed. Please update to New google play services v. 12.6.85.
This is still not working for me , Maps works and is smooth and fine for in car nav etc
But Ingress does not .
I have gone from 12.6.85 to 12.6.88 beta , but that has not fixed the issue.
Ingress lags massively , you cannot really play it
"GPS Test" app show a excellent GPS signal and locked on , yet ingress will take about 30sec -2mins to show up as connected
Then as you move it will be stuck on the last location , tried lots of in game options , nothing seems to help a min later or so it will jump and stick at another location.
Anyone else running Ingress ok ?
Note when I got the phone ingress worked fine, I had to update and reset data to remove that play services updating error in other apps, like TheSchoolApp
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.
Seems like a stupid question, but yes I bought a 2213 EU version, unlocked the bootloader, rooted it the right way, did everything to pass safety net, device is play protect registered, getprop ro.boot.verifiedbootstate returns green, Google Pay works fine after root, DRM Info shows Widevine L1
Netflix won't install (not compatible with device)
HBOMax won't play
Peacock won't install
Hulu won't install
Is this possibly a OnePLus bug on the new NE2213_11_A.15 build, some new rooting thing with Android 12, bad luck, or is there some solution that I need to install?
I may be haded right back to the trusty OnePlus 8 Pro....which has none of these issues and has the Macro Camera which I actually miss....
Thanks in advance for any suggestions....
Also, if anyone in the US needs dual SIM, the EU versions supports all the US bands (and more), is dual SIM, and works flawlessly with T-Mobile...5G, VoWiFi, everything.
Same thing for me, i live in Sweden and we have Cmore & Discovery here that refuse to play after bootloader unlock and root, no magisk hide solution have worked for me. Maybe bootloader unlock with no root works, but cant try because my OP10 is bricked. My old OP9 was working perfect with all the streaming, i now have Xiaomi 12 Pro and was afraid the same thing would happend with this phone, only unlocked bootloader on this phone but no root and everything works 100%, streaming apps, gpay.
It just seems there is something wrong here in the way that OnePlus certified this device. Other Android 12 devices can be rooted without all these issue, right?
Can people US or Chinese / Indian versions get rooted and have access to the Streaming services?
MetroWestMA said:
It just seems there is something wrong here in the way that OnePlus certified this device. Other Android 12 devices can be rooted without all these issue, right?
Can people US or Chinese / Indian versions get rooted and have access to the Streaming services?
Click to expand...
Click to collapse
I have Hulu Disney plus and Netflix working but only play when streamed to my Chromecast. On device play doesn't work and only plays L3 even though device reads L1. Believe it's to deal with bootloader unlock and not root. But others posted that it was a OnePlus issue and was supposed to be resolved but hasn't been.
toolhas4degrees said:
I have Hulu Disney plus and Netflix working but only play when streamed to my Chromecast. On device play doesn't work and only plays L3 even though device reads L1. Believe it's to deal with bootloader unlock and not root. But others posted that it was a OnePlus issue and was supposed to be resolved but hasn't been.
Click to expand...
Click to collapse
It's a issue with this particular Snapdragon chip. The Samsung Galaxy Tab S8 uses the same processor and has the exact same problem.
g96818 said:
It's a issue with this particular Snapdragon chip. The Samsung Galaxy Tab S8 uses the same processor and has the exact same problem.
Click to expand...
Click to collapse
How can it be the chip. It could be the kernel associated didn't have correct commits from snapdragon. But still the drm is in the secure partition on our device that can't be altered also.
toolhas4degrees said:
How can it be the chip. It could be the kernel associated didn't have correct commits from snapdragon. But still the drm is in the secure partition on our device that can't be altered also.
Click to expand...
Click to collapse
Not sure, but that's the only common link between both devices from different manufacturers. They're basically using the same work around we are. I'll be testing it out shortly also since my S8 was just delivered.
It is just fundamentally blocking anything having to do with DRM. You can't even spoof the user agent and watch any streaming service through a browser -- it ask if the browser can play secure content (you say yes) and then gives an error. I am not even that much of a TV / Movie guy, but to be 100% blocked from any streaming just for rooting a device you own????
Pretty F&*^in extreme if you asked me....
The only question is do I wait for someone to hack it (if that's even possible), or do I just go back to my trusty OP 8 Pro and sell this...?
Are there any Android 12 rootable phones that don't have this issue...or is it all Android 12 phones?
MetroWestMA said:
It is just fundamentally blocking anything having to do with DRM. You can't even spoof the user agent and watch any streaming service through a browser -- it ask if the browser can play secure content (you say yes) and then gives an error. I am not even that much of a TV / Movie guy, but to be 100% blocked from any streaming just for rooting a device you own????
Pretty F&*^in extreme if you asked me....
The only question is do I wait for someone to hack it (if that's even possible), or do I just go back to my trusty OP 8 Pro and sell this...?
Are there any Android 12 rootable phones that don't have this issue...or is it all Android 12 phones?
Click to expand...
Click to collapse
i think it's a snapdragon issue rather than software issue.
MetroWestMA said:
Seems like a stupid question, but yes I bought a 2213 EU version, unlocked the bootloader, rooted it the right way, did everything to pass safety net, device is play protect registered, getprop ro.boot.verifiedbootstate returns green, Google Pay works fine after root, DRM Info shows Widevine L1
Netflix won't install (not compatible with device)
HBOMax won't play
Peacock won't install
Hulu won't install
Is this possibly a OnePLus bug on the new NE2213_11_A.15 build, some new rooting thing with Android 12, bad luck, or is there some solution that I need to install?
I may be haded right back to the trusty OnePlus 8 Pro....which has none of these issues and has the Macro Camera which I actually miss....
Thanks in advance for any suggestions....
Also, if anyone in the US needs dual SIM, the EU versions supports all the US bands (and more), is dual SIM, and works flawlessly with T-Mobile...5G, VoWiFi, everything.
Click to expand...
Click to collapse
How did you get widevine L1 after bootloader unlock?
devtherockstar said:
How did you get widevine L1 after bootloader unlock?
Click to expand...
Click to collapse
That's what DRM Info showed.
But for me it's all moot at this point. Yesterday, Google Pay stopped working (some new detection thing I presume), so I attempted to relock the bootloader with
./fastboot flashing lock
at which point the device started going into an infinite power cycle instant reboot no way to get into FASTBOOT, or Recovery or turn off the phone. So I just returning the phone and going back to OnePLus 8 / Android 11 where you can be fully rooted and everything just works.
What a disappointment and waste of time.
Thanks for everyone who offerred suggestions...I'll try back in 6 months or so and see if any of this gets sorted out.
It's not "issues with the chip". Google upped their ante with root detection, which breaks everything from netflix to google pay. See this thread.
I was the OP and had to return my bricked OP10Pro under the 30 day return period.
Anyway, I bought a Google 512GB Pixel 6 Pro used, rooted it, and did the basic stuff I have done since the OP8Pro -- and everything works -- GPay, Netflix, no DRM issues and no hassles.
So maybe it is the chip, but if google had "upped their game" I would think it would be with their own phones especially since the Tensor SOC (co developed with Samsung) has a trusted security module.
As far as the phones go, the Pixel Pro is heavier and the battery charges slower, but you get dual SIM and it works on all USA/Worldside 5G networks and bands. And the cameras are top notch. So kind of a tossup I guess.
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.