Related
My phone is a LG G3 T-Mobile, running on 5.0.1 LP OTA updates.
After setting up my zenwatch2 with my phone, the watch pop up the
"Get google play services Android Wear won't run without Google Play services, which are missing from your phone“
On my phone I am running Android Wear ver. 1.3.0.2369832
Google play services ver. 8.3.00
I have done multiple factory reset on the watch but still pop up after synchronising with my phone.
What could be the issue? Watch seems to work fine. Text and notifications shows up fine.
Try to restart the google play services on phone
I've disable it on the phone then it said it will revert to old version. But it didn't. No option under google play for uninstall update. Its greyed out. Once I disable on the phone, well I tried, I reboot and then factory reset zenwatch. Then repeat the entire pairing process all over again. Still nothing. So, I don't know.
When i started the first time, and after I FDR'd I got the message. It went away quickly though.
Nsx93 said:
"Get google play services Android Wear won't run without Google Play services, which are missing from your phone“
Click to expand...
Click to collapse
I've had this message on my SWR50, too, when BT connection to the phone (Edge+) got lost. Android Wear app on phone showed a "connecting" message, while the watch was complaining about missing services. I've rebooted both phone and watch, now it's fine. Hope this does not happen again with the ZW2, which will arrive in 14 days.
I tried everything. It still pop up once in awhile. I am running Blisspop ROM for my lg g3 T-Mobile. Everything is up to date. So, I don't know. Both watch and phone running on lp 5.1.1 ... So, j can't see the conflict there. Both play services updated to current version.
I've had it show up briefly once or twice, but it quickly goes away. Seems like just a minor bug.
Nsx93 said:
My phone is a LG G3 T-Mobile, running on 5.0.1 LP OTA updates.
After setting up my zenwatch2 with my phone, the watch pop up the
"Get google play services Android Wear won't run without Google Play services, which are missing from your phone“
On my phone I am running Android Wear ver. 1.3.0.2369832
Google play services ver. 8.3.00
I have done multiple factory reset on the watch but still pop up after synchronising with my phone.
What could be the issue? Watch seems to work fine. Text and notifications shows up fine.
Click to expand...
Click to collapse
You need Google search to fix the problem.. Make sure Google search is not disable. Clear the cache on Google search in app settings. Then don't open Google search. Because that will be a battery drain.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2
blazinandroid1 said:
You need Google search to fix the problem.. Make sure Google search is not disable. Clear the cache on Google search in app settings. Then don't open Google search. Because that will be a battery drain.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Thanks.
I've updated all the gapps. So far it hasn't pop up on the watch, yet!
Been working fine lately.
It would been nice if the connection range is further. Seem pretty short distance, then it will get disconnected.
Nsx93 said:
Thanks.
I've updated all the gapps. So far it hasn't pop up on the watch, yet!
Been working fine lately.
It would been nice if the connection range is further. Seem pretty short distance, then it will get disconnected.
Click to expand...
Click to collapse
Waiting on the source code. So I can start fxing some of those problems.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2
It would make this watch 10x better if the issues get hammered out.
Look forward to your work.
This is happening on Moto 360 (1st gen) too. Been using the watch fine on my Moto X '13, then today factory reset it paired it with my new phone (moto x pure) and it works fine for a bit, then this notification comes on my watch screen and the watch disconnects. All play services and such are up to date
Every time I factory reset it and re pair it with android wear it will appear once or twice then disappears
It is normal across all Android wear devices. Android Wear requires that Google Search is installed and enabled (not disabled, lol). I have a tendency to disable this feature when I am going through disabling apps on a fresh boot. Just make sure Google Now is able to launch. You don't have to accept to use Google Now, but you should be able to swipe up on home to launch search.
player911 said:
It is normal across all Android wear devices. Android Wear requires that Google Search is installed and enabled (not disabled, lol). I have a tendency to disable this feature when I am going through disabling apps on a fresh boot. Just make sure Google Now is able to launch. You don't have to accept to use Google Now, but you should be able to swipe up on home to launch search.
Click to expand...
Click to collapse
The real reason for that to pop up. Is when the device gets disconnected from the phone. And you are right about Google search.
Anyone got this yet
Sent from my Nexus 6P using XDA-Developers Legacy app
yea just got it. already had assistant but downloaded the updates anyway.
Anyway to force it
Just got a launcher update. But assistant not enabled yet.
Sent from my Nexus 6P using Tapatalk
Does it works with 7.1.1 ?
Sent from my Nexus 6P using XDA-Developers Legacy app
m.t.2012 said:
Does it works with 7.1.1 ?
Click to expand...
Click to collapse
According to this:
https://www.xda-developers.com/google-assistant-now-available-for-all-android-6-0-devices/
Yes, but not worldwide yet...
I just tried updating my play services from 10.2.98 to the newest non beta on apkmirror which is 10.2.99 but assistant is not enabled. I then tried the latest beta which is 10.5.37 but still no assistant. I just got the Google app update to 6.13.x earlier via play store so I figured all I needed was play services but apparently not unless root is causing an issue.
jrg67 said:
I just tried updating my play services from 10.2.98 to the newest non beta on apkmirror which is 10.2.99 but assistant is not enabled. I then tried the latest beta which is 10.5.37 but still no assistant. I just got the Google app update to 6.13.x earlier via play store so I figured all I needed was play services but apparently not unless root is causing an issue.
Click to expand...
Click to collapse
I'm not rooted and updated play services and the Google app and also still have no assistant. So, apparently it is a server side switch that we all just need to wait for. Of course I still don't have the dual tab google app layout, so I'm not holding my breath.
Empty Hand said:
I'm not rooted and updated play services and the Google app and also still have no assistant. So, apparently it is a server side switch that we all just need to wait for. Of course I still don't have the dual tab google app layout, so I'm not holding my breath.
Click to expand...
Click to collapse
That dual tab Google app layout is still a thing? I never got it either and just assumed it was pulled. So for assistant, the Google blog says it's a play services update, naturally that means something else like a server side update too. Silly Google, tricks are for kids.
I have a 6P and 5x both on 7.1.2 beta, no Google Assistant. I have a hunch that apart from having to have the new Google Play Services, that individual accounts have to have the switch thrown on it by Google. Like many of Google's software updates this is liable to take weeks for everyone to see.
I have a 6P, 5X and a 5. Yesterday in an effort to solve another problem, I had clean installed factory 6.0, 7.0, 7.1.1 and 7.1.2(beta) with locked bootloaders and completely stock onto my 6P. None of the phones and none of the factory ROMs had Google Assistant enabled even after updating all stock apps. WTF, Google, after your big announcement that it was available? Aside from the one person in this thread, I haven't heard of anyone having this enabled, even read through over 400 comments in Android Police thread.
Still have not received it. Running stock 7.1.1.
Sent from my Nexus 6P using Tapatalk
It's a server side switch, so we all have to just wait until google flips the switch.
Here's how I did it:
I enrolled with ALL the permissions with the Google (Google Now) app; i.e., News and weather updates.
Then, I downloaded and enrolled with Google Allo. I gave it ALL of the permissions it requested of me. Then I made a few queries with Allo's Google Assistant bot.
It's important that you turn Location and Search histories ON.
I was greeted by Google Assistant shortly thereafter...
Hope this helps!
Janerd said:
It's a server side switch, so we all have to just wait until google flips the switch.
Click to expand...
Click to collapse
honestly it is just matter of adding a single line to build.prob
Code:
ro.opa.eligible_device=true
I am using a LeMax 2 running Lineage OS (14.1-20170503-Unofficial-x2). Everything is working very, very well. (please keep in mind, I'm coming from a Nexus 6, which had bad slowness and battery issues now, and I LOVED this phone!) However, I've run into a problem with "Ok, Google" and Android Auto.
If I update the Google App (I've tried both "normal" and beta) then it breaks the "OK, Google" hotword detection. I downgrade, and it works fine. I have Android Auto set to auto start when it connects to my bluetooth transmitter. If the Google app has been downgraded, Android Auto wants to update it, won't launch without it, and that always updates Google, breaking the hotword again.
I use both Android Auto and "Ok, Google" a lot, so I'd love to find a way to be able to use both. Any suggestions? I've tried downgrading Auto, and every combo I can think of with Google and AA, but I cannot get them to work at the same time.
ETA: I've since updated to the official Lineage OS, (the 05/19 Nightly) and still the same issue
ETA2: I did an uninstall updates. Version 7.1.29.21.arm64 com.google.android.googlequicksearchbox works fine with the hotword detection - until you open Android Auto. Then it stops altogether, even though it hasn't updated. This time, only one time, I got a toast message in Android Auto saying voice commands weren't available right now, but couldn't get it to do it again.
Delete...sorry
Mrs_B said:
I am using a LeMax 2 running Lineage OS (14.1-20170503-Unofficial-x2). Everything is working very, very well. (please keep in mind, I'm coming from a Nexus 6, which had bad slowness and battery issues now, and I LOVED this phone!) However, I've run into a problem with "Ok, Google" and Android Auto.
If I update the Google App (I've tried both "normal" and beta) then it breaks the "OK, Google" hotword detection. I downgrade, and it works fine. I have Android Auto set to auto start when it connects to my bluetooth transmitter. If the Google app has been downgraded, Android Auto wants to update it, won't launch without it, and that always updates Google, breaking the hotword again.
I use both Android Auto and "Ok, Google" a lot, so I'd love to find a way to be able to use both. Any suggestions? I've tried downgrading Auto, and every combo I can think of with Google and AA, but I cannot get them to work at the same time.
ETA: I've since updated to the official Lineage OS, (the 05/19 Nightly) and still the same issue
Click to expand...
Click to collapse
Could you please tell which Google app version do you have exactly? Mine is not working.
Enviado desde mi LEX829 mediante Tapatalk
I've tried several different version from apk mirror and just "un-updating" what I had. I've tried a full factory reset, then installing the official LOS nightly listed above. I've compared the Google app version to the working version (both Android Auto and the Ok, Google hotword) on my Nexus 6, and gotten as close as possible to it, or even newer versions (apk mirror again, then flashing Gapps, arm 64 7.1 Stock from 05/23) I can get one or the other to work, but not both Ok, Google and Android Auto. I've tried turning voice control off, then back on. I've deleted and re-recorded my voice commands. I cannot figure out how to make this work. Until I get it figured out, I'm using my Nexus 6, but it's about to need retiring.
Mrs_B said:
I've tried several different version from apk mirror and just "un-updating" what I had. I've tried a full factory reset, then installing the official LOS nightly listed above. I've compared the Google app version to the working version (both Android Auto and the Ok, Google hotword) on my Nexus 6, and gotten as close as possible to it, or even newer versions (apk mirror again, then flashing Gapps, arm 64 7.1 Stock from 05/23) I can get one or the other to work, but not both Ok, Google and Android Auto. I've tried turning voice control off, then back on. I've deleted and re-recorded my voice commands. I cannot figure out how to make this work. Until I get it figured out, I'm using my Nexus 6, but it's about to need retiring.
Click to expand...
Click to collapse
But which Google app version is working with Ok Google...
Enviado desde mi LEX829 mediante Tapatalk
jufece said:
But which Google app version is working with Ok Google...
Click to expand...
Click to collapse
That's my point. All but the one I'm using now have worked with it...until it insists on an update to the most recent.
All I know is that 7.3.16.21.arm64 com.google.android.googlequicksearchbox doesn't work. I'm sorry, I don't know the version that worked for sure, as I did a full factory reset to try and fix the problem. I promise, I'm not trying to be difficult. I just didn't know it was going to happen or I'd have noted the version numbers.
I've also tried it with the SIM in, and with the SIM out. Not sure why that would have anything to do with it, but worth trying.
I think the problem is to do with google assistant which comes with the newer versions of the Google app (replacing Google Now)
For me it's only working when turning ok Google recognizing off. Turning it on didn't work. Sound curious but it's real. Dunno what's wrong here. Ok Google also only works on main screen when mobile is unlocked. Having another app in foreground it does not trigger.
I don't know if this behavior belongs to me max 2 or to Google app. Anyone else can confirm this problem?
Linage needs to fix this on there end. They need to create a working gapps install.
Sent from my Le Max 2 using XDA Labs
Ever since I upgraded my Moto Z Play to Oreo 8.0 I've had issues with notifications coming in up to an hour late and apps downloading to 100% but not installing. I have to close out the app store and reopen for the downloaded app to install.
Tried cache wipes, app caches wipes, factory resets and it works for a little bit but goes back to not installing apps and notification delays.
The only thing that seems to work is disabling the Google app. Only issue with that is I need the Google app to use Android Auto in my car.
Can't find any answers on what the problem is and the latest Google App update from Aug 20 still doesn't solve the issues.
Anyone else experience this?
Hi everybody,
So yesterday I updated to emui and Android 9. Today I had to discover that the "okay Google" feature doesn't work anymore. If I open the search manually or drag up from bottom screen corners it listens but I can't fire it up with saying "okay Google".
I checked the options in the phone and the ones in the Google app an both were deactivated but not grayed out. The problem is when I try to turn them on they get turned off automatically in less than a second.
I think it has something to do with huaweis assistant wich I don't want to use. Is speech activation now blocked or is it a bug?
BTW I actually own a mate 10 pro but I posted here because I don't know if the problem comes from Android or emui and because the 20 came to my knowledge shipped with the update but the 10 did not.
Please excuse my English I'm not a native speaker and thanks to everybody
I set mine up did the ok Google, hey Google steps. But when I tried to use it, it wasn't detecting my voice. After a bit of fiddling around I managed to get it working. Below is what I did.
Cleared cache and storage
Disabled App
Enabled App
Downloaded update from playstore
Reboot
Setup voice detect
Retrained voice.
Tested it worked several times
Rebooted
Test again still works
Genuine question, why do you all use this feature? What uses does it have? I just pick up my phone to do what I need to do. I'm just curious, might even give me a reason to use it lol
Sent from my [device_name] using XDA-Developers Legacy app
It's a known problem since 6 months by Google on many many many devices
I just started a thread on this... It seems to me like the new Pie permissions are an issue and one of the coders didn't get the memo that now you need to make Google app or Assistant a Trusted Agent to unlock your phone. Been trying things for days to get this working.... Such a piss off. Especially when I'm driving and I need to say Ok Google, take me to the closest Home Depot. Gfs frustrating
Edit: if I get a ticket for holding my phone... I'm gonna blame it on Google