Status Update
Comments
jp...@gmail.com <jp...@gmail.com> #3
jp...@gmail.com <jp...@gmail.com> #4
I can find the "YouTube for Google TV" app on the Google Play Store when searching through the browser on my PC. But on my phone, if I search for it on the Google Play Store it does not come up. I see the "YouTube" app suitable for my phone, which shows as "installed", and I see "Google Play Movies and TV". Same on my tablet.
On my Android TV Nexus Player, I find "YouTube for Android TV" and "Google Play Movies and TV", but not "YouTube for Google TV".
This article
would seem to explain what is going on, as well as the bitterly negative reviews for the March 2015 upgrade of the "YouTube for Google TV" app, here:
The fact that I can't install "YouTube for Google TV" on my Android TV is not surprising -- It seems clear that Google doesn't want Android TV owners to have access to it.
So, back to the original problem: It seems then that the YouTubeAPI for Android is not supported on Android TV (at least currently). So, your original question is still a good one: will Google make the YouTube API library work with the default "YouTube for Android TV" application? Maybe they really don't want the YouTube viewing experience on the living room TV to be customized in third-party apps.
na...@google.com <na...@google.com> #5
Thank you for this post. I am having the same problem with the default pre-installed version of YouTube on my Android TV Nexus Player. When I attempt to "UPDATE YOUTUBE APP" it doesn't actually update it. If I uninstall and re-install YouTube, it simply re-installs the same version (version 1.0.5.4, updated on Mar 26, 2015, 8.62 MB). If I uninstall that, and search on Google Play Store for the com.google.android.youtube.googletv app recommended above, it doesn't find it - it only finds the first app.
You say "But installing of second app is very inconvenient for users." - I agree - it's so inconvenient, I can't figure out even how to do it.
Would you mind telling me how you did it?
Thank you,
Lloyd
mi...@gmail.com <mi...@gmail.com> #6
ja...@gmail.com <ja...@gmail.com> #7
al...@thetechguru.net <al...@thetechguru.net> #8
Nexus Player with android 5.1.1;
com.google.android.youtube.googletv is not installed (and can't be installed) and the youtube player api gives an error and suggests to update the youtube app.
Waiting for updates...
ma...@gmail.com <ma...@gmail.com> #9
sk...@gmail.com <sk...@gmail.com> #11
sn...@gmail.com <sn...@gmail.com> #12
hi...@gmail.com <hi...@gmail.com> #13
I'm using the API for YouTube thumbnails, and am using the onInitializationFailure callback to detect failure. When a user recoverable error happens, the YouTube app linked to from the Dialog is "not available on this device". Very confusing for users, as they can clearly see that it is there.
@Override
public void onInitializationFailure(YouTubeThumbnailView view, YouTubeInitializationResult loader) {
if (loader.isUserRecoverableError()) {
loader.getErrorDialog(activity, code).show();
}
}
to...@gmail.com <to...@gmail.com> #14
So, do you have the new api for android tv?
and there the address for iframe api:
ge...@gmail.com <ge...@gmail.com> #15
ge...@gmail.com <ge...@gmail.com> #16
It provides a YoutubeTvView that embeds a Webview with Youtube iframe with all Javascript API available from this view.
Also, YoutubeTvFragment holds a YoutubeTvView with a media control bar (PlaybackOverlayFragment)
ab...@gmail.com <ab...@gmail.com> #17
Are you folks aware of what's actually occurring out here in the world? This is the future, and can't be difficult to do. Please enable it.
br...@gmail.com <br...@gmail.com> #18
sm...@gmail.com <sm...@gmail.com> #19
mo...@gmail.com <mo...@gmail.com> #20
ew...@gmail.com <ew...@gmail.com> #21
Moto360 3rd gen: 'Ok, Google' detection fails from the moment I first booted the watch out of the box. Reset, update etc... nothing helps. Fix this, Google team. Show Wear OS some love.
ch...@gmail.com <ch...@gmail.com> #22
bo...@gmail.com <bo...@gmail.com> #23
jp...@gmail.com <jp...@gmail.com> #24
kl...@gmail.com <kl...@gmail.com> #25
so...@gmail.com <so...@gmail.com> #26
Please only leave feedback if you have something material to add, thank you.
da...@gmail.com <da...@gmail.com> #27
se...@gmail.com <se...@gmail.com> #28
ch...@gmail.com <ch...@gmail.com> #29
The last version of the WearOS Google App that was working for me was 11.18.11.25.arm, but after I updated to 11.19.13.25.arm around mid of July 2020 it was broken. I uninstalled the update and it was working again so it is most definitely a problem with this version or later.
jf...@gmail.com <jf...@gmail.com> #30
ph...@gmail.com <ph...@gmail.com> #31
am...@gmail.com <am...@gmail.com> #32
Ticwatch Pro 3 GPS
Samsung Galaxy S20+ 5G (Even with forced Google Assistant and disabled Bixby)
Ticwatch Pro 2020
ky...@gmail.com <ky...@gmail.com> #33
ja...@gmail.com <ja...@gmail.com> #34
latest GA updates have made GA less useful.
Google OK - never worked - not know it to work on any watch.
Currently cannot use GA to send a text message or whats app message - just comes up with no phone connection, despite that fact that you can reply to messages without an issue, pointing to the fact that this is a GA issue.
Reminders don't remind.
GA is latest on phone and watch. GA language is English US.
su...@googlemail.com <su...@googlemail.com> #35
re...@gmail.com <re...@gmail.com> #36
I believe this is not a bug and was done deliberately.
I'm surprised the watch manufacturers are not crucifying Google weatos team for this mess.
su...@gmail.com <su...@gmail.com> #37
bu...@gmail.com <bu...@gmail.com> #38
pb...@gmail.com <pb...@gmail.com> #39
ec...@gmail.com <ec...@gmail.com> #40
sp...@gmail.com <sp...@gmail.com> #41
Google app is just broken.
dj...@gmail.com <dj...@gmail.com> #42
am...@gmail.com <am...@gmail.com> #43
mi...@gmail.com <mi...@gmail.com> #44
to...@gmail.com <to...@gmail.com> #45
ar...@gmail.com <ar...@gmail.com> #46
ta...@gmail.com <ta...@gmail.com> #47
with Wear OS 2.23; Home 2.43.0.344410213; GPlay Service 20.45.16(050300-344294571)
"OK Google" detection - not working, tried reboot, re-enable toggle.
Google Assistant on watch only works with manual activation, hold button or tap mic icon on feed page, on phone voice activation works without issue.
ri...@gmail.com <ri...@gmail.com> #48
watch, but assistant is still not working. The error is "impossibile
connettersi al tel." (Impossibile to connect to the phone). If I uninstall
updates of Google app on the phone it works again. Too bad
Il mer 2 dic 2020, 03:46 <buganizer-system@google.com> ha scritto:
ja...@gmail.com <ja...@gmail.com> #49
ku...@gmail.com <ku...@gmail.com> #50
pe...@gmail.com <pe...@gmail.com> #51
hu...@gmail.com <hu...@gmail.com> #52
br...@gmail.com <br...@gmail.com> #53
It is over 1 year.
ph...@gmail.com <ph...@gmail.com> #54
gh...@gmail.com <gh...@gmail.com> #55
zo...@gmail.com <zo...@gmail.com> #56
al...@thetechguru.net <al...@thetechguru.net> #57
da...@gmail.com <da...@gmail.com> #58
by...@gmail.com <by...@gmail.com> #59
to...@gmail.com <to...@gmail.com> #60
in...@gmail.com <in...@gmail.com> #61
Same in my Fossil gen 5
le...@gmail.com <le...@gmail.com> #62
ma...@gmail.com <ma...@gmail.com> #63
ma...@gmail.com <ma...@gmail.com> #64
am...@gmail.com <am...@gmail.com> #65
sl...@googlemail.com <sl...@googlemail.com> #66
Actually the connection between the clock and the smartphone exists.
E.g. When I start navigation using the assistant on the watch, it shows me the suggested routes. if i want to open a route using the watch, the error occurs when the watch tries to operate the smartphone and wants to start navigation.
The messages "can't reach the phone at the moment", "a problem has occurred" appear.
E.g. even if I tell the watch that an app should open on the smartphone, an error also occurs.
I've tried everything. Reseted the smartwatch, uninstalled the assistant or tried an old version, uninstalled the google app or tested an old version on the phone, as well as the app versions on the clock, I swapped, unfortunately without success.
I also gave full access to all apps involved or I tried another language (GER, US).
The "OK Google" command does not work with the watch either.
I bought the newest hardware and it doesn't work - pretty disappointing.
I don't seem to be the only one having this problem either. you can find many posts in other forums. Unfortunately, no tip helped
yc...@googlemail.com <yc...@googlemail.com> #67
Everything else is working, everything is updated
fn...@gmail.com <fn...@gmail.com> #68
On more comment about this topic.
My news smartwatch Fossil gen 5 (Garrett Hr 1254) often doesn’t work with voice recognition. Common error are: G917510 error or an error with Google Connection.
I find a lot of result searching this error code since 2019.
I’m using my Fossil with an IPhone. Yesterday I updated all updatable but the performance are always the same.
I tried to uninstall Google LLC update. I restarted the smartwatch but nothing. It doesn’t work!!!
Here in the tracker I see a lot of messages about this topic but I can’t find a release date where this problem will be fixed.
Please give us a solution.
Regards Fabio
te...@gmail.com <te...@gmail.com> #69
No OK Google on my new Fossil Gen 5. Thanks for Nothing!!!
jo...@gmail.com <jo...@gmail.com> #70
if...@gmail.com <if...@gmail.com> #71
se...@gmail.com <se...@gmail.com> #72
ew...@gmail.com <ew...@gmail.com> #73
xa...@outlook.com <xa...@outlook.com> #74
qu...@gmail.com <qu...@gmail.com> #75
Hasn't ever worked at all to send texts, doesn't recognize my connected phone when trying to set up an appointment or reminder, no OK Google detection. The best I can do, every once in a while, is set a timer or an alarm with it. This is extremely disappointing.
co...@gmail.com <co...@gmail.com> #76
ba...@gmail.com <ba...@gmail.com> #77
Ticwatch 3 pro gps
fr...@gmail.com <fr...@gmail.com> #78
[Deleted User] <[Deleted User]> #79
no...@gmail.com <no...@gmail.com> #80
Esto es un cachondeo
pa...@gmail.com <pa...@gmail.com> #81
th...@gmail.com <th...@gmail.com> #82
be...@gmail.com <be...@gmail.com> #83
se...@gmail.com <se...@gmail.com> #84
fr...@gmail.com <fr...@gmail.com> #85
This is literally one of the main features I wanted out of a smartwatch.. to be able to text\message people without taking my phone out. Please fix!!!
ca...@gmail.com <ca...@gmail.com> #86
ty...@gmail.com <ty...@gmail.com> #87
al...@gmail.com <al...@gmail.com> #88
b0...@gmail.com <b0...@gmail.com> #89
mr...@gmail.com <mr...@gmail.com> #90
- 'ok google' doesn't work
- navigation does not start
- assistant does not send messages - 'unable to connect to the phone'
bu...@gmail.com <bu...@gmail.com> #91
st...@gmail.com <st...@gmail.com> #92
Couldn't connect to your phone". While connected fine.
m....@gmail.com <m....@gmail.com> #93
xi...@gmail.com <xi...@gmail.com> #94
ll...@gmail.com <ll...@gmail.com> #95
fr...@gmail.com <fr...@gmail.com> #96
ko...@gmail.com <ko...@gmail.com> #97
em...@gmail.com <em...@gmail.com> #98
je...@hookt-up.com <je...@hookt-up.com> #99
ry...@gmail.com <ry...@gmail.com> #100
pa...@gmail.com <pa...@gmail.com> #101
br...@gmail.com <br...@gmail.com> #102
ry...@gmail.com <ry...@gmail.com> #103
jm...@gmail.com <jm...@gmail.com> #104
1. No resources should be allocated on this task
2. Fixing this bug would produce more severe issues, so better not fix it.
In both cases, why not just communicate it?
Where is WearOS product management?
ma...@gmail.com <ma...@gmail.com> #105
pa...@gmail.com <pa...@gmail.com> #106
st...@gmail.com <st...@gmail.com> #107
es...@gmail.com <es...@gmail.com> #108
de...@gmail.com <de...@gmail.com> #109
co...@gmail.com <co...@gmail.com> #110
cu...@gmail.com <cu...@gmail.com> #111
mu...@gmail.com <mu...@gmail.com> #112
I'm in Australia and my phone is set to English Australia, if I set it to English US for Google Assistant to work, then I get Fahrenheit - we use Celsius. Please put some effort into making this work - I dont just want google searches, I want to be able to turn my lights on...
j....@gmail.com <j....@gmail.com> #113
And i want to use google assistant in FRENCH whitout any issue.
[Deleted User] <[Deleted User]> #114
Et je veux utiliser l'assistant google en FRANÇAIS sans aucun problème.
rh...@gmail.com <rh...@gmail.com> #115
vr...@gmail.com <vr...@gmail.com> #116
Another user affected by the wizard in wearOS.
Greetings.
be...@gmail.com <be...@gmail.com> #117
Greeting from Turkey. I have Oppo Watch 46mm global version and "OK Google" is not working and all apps are up to date. Please fix this issue because it is very useful to awake watch with the phrase.
aw...@gmail.com <aw...@gmail.com> #118
al...@gmail.com <al...@gmail.com> #119
me...@gmail.com <me...@gmail.com> #120
ra...@gmail.com <ra...@gmail.com> #121
On the new Google Assistant settings app, I am unable to find any options for managing assistant on my WearOS device (Fossil Gen5 or Moto360) anymore. Plus the "OK Google" command just doesn't work.
Also, I can no longer command Google Assistant on the watch to "make a call" or "send a text msg". These functions can still be performed manually using the messenger or phone app on the watch my when I as Google Assistant, I am prompted to enable permission on the phone, which are already enabled and then the watch prompts "Sorry, unable to obtain permission"
I have contact Google & Fossil with not luck or feedback, it's like Google has given up on WearOS, just like the multiple other products on Google graveyard and is only focusing on Fitbit because from what I see Fitbit's Google assistant integration seem to be work fine.
ad...@gmail.com <ad...@gmail.com> #122
Please help.
On Thu, 25 Feb 2021 at 14:18, <buganizer-system@google.com> wrote:
Sent from Gmail Mobile
fu...@gmail.com <fu...@gmail.com> #123
iv...@omelchenko.net <iv...@omelchenko.net> #124
su...@googlemail.com <su...@googlemail.com> #125
I starred this 4 months ago and I'm still having issues.
by...@gmail.com <by...@gmail.com> #126
bl...@gmail.com <bl...@gmail.com> #127
I'm going to refer everyone back to #26.
If you have this bug, please just star the bug. You don't need to reply to the tracker saying "me too" or "+1" or "why hasn't this been fixed" as this sends an email round to everyone who has stared or commented on the issue.
Please only leave feedback if you have something material to add, thank you. It'll likely end up with Google staff locking the issue.
fi...@gmail.com <fi...@gmail.com> #129
ad...@gmail.com <ad...@gmail.com> #130
On Fri., Feb. 26, 2021, 1:51 p.m. , <buganizer-system@google.com> wrote:
as...@gmail.com <as...@gmail.com> #131
er...@gmail.com <er...@gmail.com> #132
ma...@gmail.com <ma...@gmail.com> #133
On Sun, Feb 28, 2021 at 12:12 AM <buganizer-system@google.com> wrote:
ba...@gmail.com <ba...@gmail.com> #134
ra...@humbalang.com <ra...@humbalang.com> #135
ry...@gmail.com <ry...@gmail.com> #136
sh...@gmail.com <sh...@gmail.com> #137
ot...@gmail.com <ot...@gmail.com> #138
appreciate it!!!
On Wed, Mar 10, 2021 at 10:53 PM <buganizer-system@google.com> wrote:
ks...@gmail.com <ks...@gmail.com> #139
be...@gmail.com <be...@gmail.com> #140
sa...@gmail.com <sa...@gmail.com> #141
jo...@googlemail.com <jo...@googlemail.com> #142
se...@gmail.com <se...@gmail.com> #143
de...@gmail.com <de...@gmail.com> #144
iv...@omelchenko.net <iv...@omelchenko.net> #145
de...@gmail.com <de...@gmail.com> #146
fi...@gmail.com <fi...@gmail.com> #147
fi...@gmail.com <fi...@gmail.com> #148
sh...@gmail.com <sh...@gmail.com> #149
I have now updated the Wear OS application on my Fossil Gen 5 to version 2.25. The Google Assistant voice detection is now operational but only when the watch is unlocked and when it has a network connection. I have tested the watch and was unable to get the voice detection to work on the watch's lockscreen not could I get it to work while the watch was in ambient mode. (AOD display which lowers the brightness to reduce battery usage.) The "Okay Google Detection" only seems to work when I press the crown/button on the side of the watch which turns the display on. I am so excited to have it operational on Wear OS! Now it just needs to work on the lockscreen similar to how to android 10 system works. I can get minimal information such as date, time, calendar events, notes, and even call and text from my Android lockscreen. It would be so convenient to be able to do things like that while I am driving so that I do not have to take my eyes off of the road.
lp...@gmail.com <lp...@gmail.com> #150
pe...@gmail.com <pe...@gmail.com> #151
wa...@gmail.com <wa...@gmail.com> #152
em...@googlemail.com <em...@googlemail.com> #153
mr...@gmail.com <mr...@gmail.com> #154
ks...@gmail.com <ks...@gmail.com> #155
da...@gmail.com <da...@gmail.com> #156
em...@googlemail.com <em...@googlemail.com> #157
je...@gmail.com <je...@gmail.com> #158
st...@googlemail.com <st...@googlemail.com> #159
pd...@gmail.com <pd...@gmail.com> #160
em...@googlemail.com <em...@googlemail.com> #161
il...@gmail.com <il...@gmail.com> #162
OK Google not working, calling by contact name returns "sorry, I can't do that any more".
I have seen somebody mention a fix by settings the systemlanguage to english(US), but even though somebody mentioned that worked, it didn't for me.
Kind regards
ca...@gmail.com <ca...@gmail.com> #163
da...@gmail.com <da...@gmail.com> #164
go...@gmail.com <go...@gmail.com> #165
te...@gmail.com <te...@gmail.com> #166
cl...@gmail.com <cl...@gmail.com> #167
lu...@gmail.com <lu...@gmail.com> #168
dr...@gmail.com <dr...@gmail.com> #169
Same problem:
- Does not react on "Hey Google" although feature is switch on (having this problem since ages now)
- "I cant do that anymore" answer when trying to call a contact (new issue since last update)
Please help.
ma...@gmail.com <ma...@gmail.com> #170
Same problem:
- Does not react on "Hey Google" although feature is switch on;
- "I cant do that anymore" answer when trying to call a contact.
Not so good
Not so happy
ty...@gmail.com <ty...@gmail.com> #171
1) when trying to have Google Assistant send a text, "can't connect to phone" error appears but there is no connection issue.
2) when trying to have Assistant start a call from watch "sorry I can't do that anymore" message appears.
ig...@gmail.com <ig...@gmail.com> #172
when trying to have Assistant start a call from watch "sorry I can't do that anymore" message appears.
ig...@gmail.com <ig...@gmail.com> #173
Does not react on "Hey Google" although feature is switch on;
em...@googlemail.com <em...@googlemail.com> #174
Would be nice to be able to use my watches for the purpose I bought them for...eg: hands free messaging and calls.
Many thanks.
mi...@gmail.com <mi...@gmail.com> #175
ju...@gmail.com <ju...@gmail.com> #176
na...@gmail.com <na...@gmail.com> #177
al...@gmail.com <al...@gmail.com> #178
co...@gmail.com <co...@gmail.com> #179
Hey Google keyword won't work + assistant can't make phone calls *sorry I can't do that anymore" error.
Messages works fine.
Reminders are saved but no notification or any reminder appear on my watch (phone works).
sb...@gmail.com <sb...@gmail.com> #180
ch...@gmail.com <ch...@gmail.com> #181
st...@gmail.com <st...@gmail.com> #183
al...@gmail.com <al...@gmail.com> #184
Thanks for your reply
br...@gmail.com <br...@gmail.com> #185
Sent from Nine
________________________________
From: buganizer-system@google.com
Sent: Wednesday, April 21, 2021 18:12
To: b-system+1671992198@google.com
Cc: bricweeks@gmail.com
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
al...@gmail.com added
Very happy to hear that! I'm still waiting for it
Thanks for your reply
_______________________________
Reference Info: 172776291 Wear OS Essential Fuction of Google Assistant does not function
component: Android Public Tracker > Wear
status: Assigned
reporter: jp...@gmail.com
assignee: na...@google.com
cc: jp...@gmail.com, na...@google.com
type: Bug
priority: P2
severity: S2
blocked by: 172994809
duplicate issue: 174336713, 174678810, 185314630
hotlist: [AOSP] assigned
retention: Component default
ReportedBy: User
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.
al...@gmail.com <al...@gmail.com> #186
am...@gmail.com <am...@gmail.com> #187
an...@gmail.com <an...@gmail.com> #188
Another issue is Google Assistant won't show directions. It asks me to touch the place I want to go to and nothing comes up, just a black screen.
al...@gmail.com <al...@gmail.com> #189
ca...@gmail.com <ca...@gmail.com> #190
Je voter pour nko
ca...@gmail.com <ca...@gmail.com> #191
Je voter pour nko
ca...@gmail.com <ca...@gmail.com> #192
Je voter pour nko
br...@gmail.com <br...@gmail.com> #193
th...@gmail.com <th...@gmail.com> #194
nu...@gmail.com <nu...@gmail.com> #195
fi...@gmail.com <fi...@gmail.com> #196
"I can't do it anymore" making calls, sending messages ecc
me...@gmail.com <me...@gmail.com> #197
bi...@gmail.com <bi...@gmail.com> #198
em...@googlemail.com <em...@googlemail.com> #199
wi...@gmail.com <wi...@gmail.com> #200
fi...@gmail.com <fi...@gmail.com> #201
This is ridiculous. Spending money and having a watch that simply doesn't work because there is a huge bug on one of the most important thing that could make every watch "smart". Every single watch that runs wearOS can't make calls and sending messages. Since months. What are you doing google? Waiting the pixel watch that works perfectly so people will buy? C'mon! And please stop asking bug repors. Just buys a google wear watch and try to use assistant. You will get that absurd "I can't do it anymore" message. Any chance to know at least that you are working on it? I spent money
sa...@gmail.com <sa...@gmail.com> #202
me...@gmail.com <me...@gmail.com> #203
me...@gmail.com <me...@gmail.com> #204
is...@hotmail.co.uk <is...@hotmail.co.uk> #205
am...@gmail.com <am...@gmail.com> #206
r4...@gmail.com <r4...@gmail.com> #207
st...@gmail.com <st...@gmail.com> #208
Can't use voice control to dial "Sorry I can't do that anymore"
Navigate just gives a black screen.
Every update seems to be one step forward, two steps back. Are you deliberately driving people over to Apple ?
kw...@gmail.com <kw...@gmail.com> #209
pe...@gmail.com <pe...@gmail.com> #210
care. I guess Apple and Samsung reads this more often than Google. Google
won't care before they launch their first Pixel Watch and they will only
make the Pixel work.
$350 down into the trash. For $100 more I would be happy instead of
disappointed and angry.
Google sux. Google fooled me more than twice. Shame on me.
Den fre 7 maj 2021 17:37 <buganizer-system@google.com> skrev:
es...@gmail.com <es...@gmail.com> #211
ni...@googlemail.com <ni...@googlemail.com> #212
How can you leave it like this.......
Ok google doesn't work
Send whatsapp message doesn't work
Make calls doesn't work
All wear os users are suffering from these issues, I bought the wear os watch for these features specifically
This really is very poor on Google's side
be...@gmail.com <be...@gmail.com> #213
1. Go to Play Store and click on My Apps > Google > Uninstall.
2. Check that now "OK Google" is working, restart if necessary.
3. Go back to Play Store and update Google app, also reboot if necessary.
Make sure that "OK Google detection" is enabled in the Google Assistant settings. This trick does not pose any danger, you will not delete the Google app (it 's a system app), only updates that were applied before March, when the bug was fixed,.
dr...@gmail.com <dr...@gmail.com> #214
Nonetheless I tried as you suggested, by uninstalling Google, resetting, and applying the newest update once again.
OK Google detection works (as before) but still can't do anything for me, for example "Call xyz" -> "I can no longer do that".
TicWatch Pro 2020, Model WF12106, Wear OS 2.27, Google Play Services 21.15.15 (050300-371058782)
Google App Version 12.18.11.25.arm
em...@googlemail.com <em...@googlemail.com> #215
I am an experienced Android / Wear os user, used to flash custom roms etc so know what I am doing.
My ancient old Huwei w1 = assistant does not work.
My brand new Armani Connected 3 = assistant does not work.
Assistant on wear os is broken and Google have acknowledged that fact.
be...@gmail.com <be...@gmail.com> #216
#214 You are confusing issues, this issue was created for bug of invoking google assistant with "OK Google" voice command. "Essential Function" refers to "Ok Google". This bug has been going on for months and was finally fixed by Google officially.
From what I read in your comment I see that you don't have or had the "OK Google" bug, but there are other users who have had it (and currently have it), simply because they have not uninstalled Google updates on the watch.
You are referring to another issue, I link them below and I recommend you to force your comments there. Evidently they are not yet resolved, and those problems have been unresolved for a long time. In fact
em...@googlemail.com <em...@googlemail.com> #217
"Make a call" = I can't do that anymore
"Send a message" = I can't connect to phone right now
"Navigate to" = black screen.
Assistant is broken on wear os for the vast majority of users.
sa...@gmail.com <sa...@gmail.com> #218
I believe one could do that before from what I read from reviews not sure why google decided to just cut support suddenly , it just says I cannot do that anymore!
What's funnier is if you click the 'what can you fo' button right below the assistant icon it says you can make phone calls , texts or navigate to commands!
Pretty frustrating for Google to not do proper beta testing before launching all updates. No wonder apple is way ahead in the game.
lu...@gmail.com <lu...@gmail.com> #219
After update to H MR1 "Ok Google" detection started working, but making calls stoped with "I can't do that anymore".
ni...@googlemail.com <ni...@googlemail.com> #220
.
be...@gmail.com <be...@gmail.com> #221
This issue is ONLY for OK google bug and that it is not activated when you say "ok google", there are dozens of comments in this issue related to the interaction with the Google assistant, but this is not where they should be written if not where there is an open issue about "that does not send SMS", "That does not call", "That does not recognize commands such as play music", etc.. All that is NOT HERE, it is in the following open issues.
They are "bombarding" this issue with comments when they should be bombarding elsewhere, so we are going wrong. If from here they are commenting that it does not work for example to send messages from assistant the engineer who has assigned that problem will not listen to it.
I encourage you to vote by clicking on the star in these three issues and comment intensely there.
re...@robinsonhoover.com <re...@robinsonhoover.com> #222
Wear OS 2.27
System version H MR2
When attempting to make calls using google assistant receive the message that, "sorry, I can't do that anymore"
jo...@gmail.com <jo...@gmail.com> #223
Wear OS 2.27
System Version H MR2
When attempting to make calls using google assistant I receive the message that, "sorry, I can't do that anymore"
Also navigation ist not working, assistant reacts, but then nothing happens, maps just doesn't start.
sh...@gmail.com <sh...@gmail.com> #224
go...@gmail.com <go...@gmail.com> #225
za...@gmail.com <za...@gmail.com> #226
Still can't make calls using contact name with google assistant.
sh...@gmail.com <sh...@gmail.com> #227
st...@gmail.com <st...@gmail.com> #228
lp...@gmail.com <lp...@gmail.com> #229
no...@gmail.com <no...@gmail.com> #230
cb...@gmail.com <cb...@gmail.com> #231
co...@gmail.com <co...@gmail.com> #232
de...@gmail.com <de...@gmail.com> #233
da...@gmail.com <da...@gmail.com> #234
ko...@gmail.com <ko...@gmail.com> #235
ma...@gmail.com <ma...@gmail.com> #236
al...@gmail.com <al...@gmail.com> #237
lo...@gmail.com <lo...@gmail.com> #238
sh...@gmail.com <sh...@gmail.com> #239
So exciting. It doesn't work and apparently Google has known about this for many months and just isn't fixing it?
Bravo.
dj...@gmail.com <dj...@gmail.com> #240
ne...@gmail.com <ne...@gmail.com> #241
ma...@gmail.com <ma...@gmail.com> #242
mi...@gmail.com <mi...@gmail.com> #243
we...@gmail.com <we...@gmail.com> #244
Also will not load content I'm asking for (pictures, navigation on maps etc)
ra...@humbalang.com <ra...@humbalang.com> #245
sm...@gmail.com <sm...@gmail.com> #246
de...@gmail.com <de...@gmail.com> #247
Google, you're costing your partners money.
fu...@gmail.com <fu...@gmail.com> #248
au...@gmail.com <au...@gmail.com> #249
em...@googlemail.com <em...@googlemail.com> #250
wa...@gmail.com <wa...@gmail.com> #251
ni...@googlemail.com <ni...@googlemail.com> #252
vo...@vossi.at <vo...@vossi.at> #253
ma...@gmail.com <ma...@gmail.com> #254
da...@gmail.com <da...@gmail.com> #255
ju...@gmail.com <ju...@gmail.com> #256
m....@gmail.com <m....@gmail.com> #257
da...@gmail.com <da...@gmail.com> #258
pe...@gmail.com <pe...@gmail.com> #259
da...@gmail.com <da...@gmail.com> #260
de...@gmail.com <de...@gmail.com> #261
da...@gmail.com <da...@gmail.com> #262
Still can't make calls using contact name with google assistant.
to...@gmail.com <to...@gmail.com> #263
dr...@gmail.com <dr...@gmail.com> #264
da...@gmail.com <da...@gmail.com> #265
sn...@gmail.com <sn...@gmail.com> #266
We have a ton of hard earned cash in these watches, we need that app working it is SO critical.
Working hands free is such a simple feat for modern man. This app not working Sucks
vi...@gmail.com <vi...@gmail.com> #267
wa...@gmail.com <wa...@gmail.com> #268
im...@gmail.com <im...@gmail.com> #269
ad...@gmail.com <ad...@gmail.com> #270
cb...@gmail.com <cb...@gmail.com> #271
--
Candy Blinson
ka...@gmail.com <ka...@gmail.com> #272
I get to the point where you say/press "send", and it says "can't connect to your phone".
er...@gmail.com <er...@gmail.com> #273
Help pls.
ro...@gmail.com <ro...@gmail.com> #274
*Slow Claps*
mi...@guidaworld.com <mi...@guidaworld.com> #275
da...@gmail.com <da...@gmail.com> #276
me...@gmail.com <me...@gmail.com> #277
broken and you are doing nothing.
Il lun 4 ott 2021, 13:23 <buganizer-system@google.com> ha scritto:
rs...@gmail.com <rs...@gmail.com> #278
What is the status on this issue ?
Please fix it.
gg...@gmail.com <gg...@gmail.com> #279
na...@gmail.com <na...@gmail.com> #280
ta...@gmail.com <ta...@gmail.com> #281
al...@gmail.com <al...@gmail.com> #282
ni...@googlemail.com <ni...@googlemail.com> #283
Seriously google what is going on???
2 years of issues.
ju...@gmail.com <ju...@gmail.com> #284
em...@googlemail.com <em...@googlemail.com> #285
ea...@gmail.com <ea...@gmail.com> #286
ea...@gmail.com <ea...@gmail.com> #287
1 - Open watch and swipe right to see the page just left from the clock face
2 - Scroll all the way down past Google's quote and hit the gear icon (This will open a few hidden Google settings.)
3 - Find the setting here, ***"Ok Google" detection"*** is OFF by default, toggle it on...
4 - Read on how it works for me below:
"Ok Google" only works from the clock face where it has a small icon indicator top center as well. It doesn't work anywhere else, and no one seems to mention this bit maybe it's just this watch.
Note: This is a partial fix because once activated, "Call Dad" for example, says "Sorry I can't do that anymore, but if you dial by the number, for example -- "Call 800 555 1212" -- that works for some reason! Contacts app seems a bit broken, can't be reinstalled? Stuck there.
lo...@gmail.com <lo...@gmail.com> #288
ta...@gmail.com <ta...@gmail.com> #289
mi...@gmail.com <mi...@gmail.com> #290
ti...@gmail.com <ti...@gmail.com> #291
co...@gmail.com <co...@gmail.com> #292
co...@gmail.com <co...@gmail.com> #293
With the solution suggested above of using the phone number instead of the contact I was able to successfully make a call from my fossil.
And also I'm not using "ok Google"..... But was able to make a call either choosing the Google icon on the face, the microphone when you swipe right, or holding down the side button......and saying "call 123-456-7899".....
As ridiculous as it is that I have to use the phone number instead of the contact name at least I can now use that feature which is good.
Has anyone found a way to get text messages out? I tried using the phone number instead of the contact name and it did not work. I continue to get the error message that it cannot connect to my phone.
Would love to know if anyone comes up with a solution for outgoing text messages. I can respond to a message I receive, assuming everybody else is having that experience as well. But I cannot start a message from my watch.
sa...@gmail.com <sa...@gmail.com> #294
da...@gmail.com <da...@gmail.com> #295
do...@gmail.com <do...@gmail.com> #296
Is this going to be repaired ?
js...@gmail.com <js...@gmail.com> #297
Fossil gen 5, hotword ok Google never detected, wear os is at it's higher version.
Of course, feature toggled on.
ar...@gmail.com <ar...@gmail.com> #298
js...@gmail.com <js...@gmail.com> #299
Voice access to the assistant does not work.
Routines don't work.
If I log in manually the assistant cannot call the contacts.
Google app updated, system updated, cache cleared, language changed, I granted all permissions to the google app, assistant ... After 2 nest mini and a nest hub I received this great surprise.
an...@gmail.com <an...@gmail.com> #300
ob...@gmail.com <ob...@gmail.com> #301
My watch is Montblanc summit
How is this little problem taking that much time to fix!
ro...@gmail.com <ro...@gmail.com> #302
th...@gmail.com <th...@gmail.com> #303
da...@gmail.com <da...@gmail.com> #304
da...@gmail.com <da...@gmail.com> #305
ca...@gmail.com <ca...@gmail.com> #306
ca...@gmail.com <ca...@gmail.com> #307
eb...@gmail.com <eb...@gmail.com> #308
he...@gmail.com <he...@gmail.com> #309
da...@gmail.com <da...@gmail.com> #310
ta...@gmail.com <ta...@gmail.com> #311
Hopefully if enough of us reach out, Google will be forced to actually pay attention to the Wear platform again - OEMs like Fossil or Mobvoi have almost no control over what software their devices run.
fa...@wfp.org <fa...@wfp.org> #312
vi...@google.com <vi...@google.com> #313
da...@gmail.com <da...@gmail.com> #314
sc...@noaa.gov <sc...@noaa.gov> #315
dr...@gmail.com <dr...@gmail.com> #316
mu...@gmail.com <mu...@gmail.com> #317
This needs to be fixed!
la...@hotmail.it <la...@hotmail.it> #318
n....@gmail.com <n....@gmail.com> #319
tu...@gmail.com <tu...@gmail.com> #320
cb...@gmail.com <cb...@gmail.com> #321
A link to this page should be posted on every Google capable watch review page!
gi...@gmail.com <gi...@gmail.com> #322
da...@gmail.com <da...@gmail.com> #323
sy...@gmail.com <sy...@gmail.com> #324
���� ��� Outlook for Android<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Thursday, January 20, 2022 8:11:03 PM
To: b-system+-789639249@google.com <b-system+-789639249@google.com>
Cc: sydmwsyly702@gmail.com <sydmwsyly702@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
da...@gmail.com added
Google = virus
_______________________________
Reference Info: 172776291 Wear OS Essential Fuction of Google Assistant does not function
component: Android Public Tracker > Wear<
status: Assigned
reporter: jp...@gmail.com
assignee: na...@google.com
cc: jp...@gmail.com, na...@google.com
type: Bug
priority: P2
severity: S2
blocked by: 172994809<
duplicate issue: 174336713<
hotlist: [AOSP] assigned<
retention: Component default
ReportedBy: User
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
sy...@gmail.com <sy...@gmail.com> #325
���� ��� Outlook for Android<
________________________________
From: �������� ��� <sydmwsyly702@gmail.com>
Sent: Thursday, January 20, 2022 8:59:53 PM
To: buganizer-system+192711+172776291@google.com <buganizer-system+192711+172776291@google.com>; b-system+-789639249@google.com <b-system+-789639249@google.com>
Subject: Re:
����
���� ��� Outlook for Android<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Thursday, January 20, 2022 8:11:03 PM
To: b-system+-789639249@google.com <b-system+-789639249@google.com>
Cc: sydmwsyly702@gmail.com <sydmwsyly702@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
da...@gmail.com added
Google = virus
_______________________________
Reference Info: 172776291 Wear OS Essential Fuction of Google Assistant does not function
component: Android Public Tracker > Wear<
status: Assigned
reporter: jp...@gmail.com
assignee: na...@google.com
cc: jp...@gmail.com, na...@google.com
type: Bug
priority: P2
severity: S2
blocked by: 172994809<
duplicate issue: 174336713<
hotlist: [AOSP] assigned<
retention: Component default
ReportedBy: User
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
al...@gmail.com <al...@gmail.com> #326
The bug has been known for many months and has obviously been reported quite often.
Google knows about the problem, definitely. However, Google ignores all bug reports. So Google doesn't want to fix the problem - no matter how much you complain.
I'm just disappointed that so many people (including me) fell for this scam, because the WearOS watches have so many bugs that they are almost unusable. It's really too bad that Google didn't realize the huge potential of the WearOS watches and is now leaving everyone stranded with a bad and buggy OS.
gi...@gmail.com <gi...@gmail.com> #327
But I think it's a shame that all current wear os 2 watches are simply ignored, except for the galaxy 4, and the assistant doesn't even work properly on it.
In my eyes, that's just a marketing strategy to make their own whatch look great, when it will be released with wear os 3 and a working asisstant.
m....@gmail.com <m....@gmail.com> #328
me...@gmail.com <me...@gmail.com> #329
mi...@gmail.com <mi...@gmail.com> #330
kl...@gmail.com <kl...@gmail.com> #331
ma...@gmail.com <ma...@gmail.com> #332
da...@gmail.com <da...@gmail.com> #333
It's two year that google don't fix that bug, it's very embarrassing.
Device: Carlyle HR 1184
OS: WearOS 2.33 HMR2
vi...@google.com <vi...@google.com> #334
ma...@gmail.com <ma...@gmail.com> #335
H�mta Outlook f�r Android<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Thursday, February 24, 2022 10:30:17 AM
To: b-system+-1003794263@google.com <b-system+-1003794263@google.com>
Cc: magnus.kazen@gmail.com <magnus.kazen@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
vi...@google.com added
Could you please check and confirm whether the bug is reproducible on latest AGSA version (having version 12.8.3 or higher) and kindly share a bugreport if the issue is still present.
_______________________________
Reference Info: 172776291 Wear OS Essential Fuction of Google Assistant does not function
component: Android Public Tracker > Wear<
status: Assigned
reporter: jp...@gmail.com
assignee: na...@google.com
cc: jp...@gmail.com, na...@google.com
type: Bug
priority: P2
severity: S2
blocked by: 172994809<
duplicate issue: 174336713<
hotlist: [AOSP] assigned<
retention: Component default
ReportedBy: User
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
dr...@gmail.com <dr...@gmail.com> #336
12.43.19.25 arm is the latest version available in the play store for Wear OS. The app has not shown any updates since November 9, 2021. There have been updates to the phone version of the app since then, but not for the watch.
da...@gmail.com <da...@gmail.com> #337
ta...@gmail.com <ta...@gmail.com> #338
mu...@gmail.com <mu...@gmail.com> #339
* I cannot control home devices using my watch, it just searches for pictures of lights....
* I can only call people if I read out the number rather than ask it to call a contact by name "Sorry, unable to obtain permissions"
AGSA on phone: 13.7.6.29
AGSA on watch: 12.43.19.25
be...@gmail.com <be...@gmail.com> #340
vi...@google.com <vi...@google.com> #341
ma...@gmail.com <ma...@gmail.com> #342
It is easy to reproduce the problem, it is the same no matter the hardware.
"Ok google" "Call <name of contact>"
Response "Sorry, can't do that any more"
However, "ok google", "call 012345..."
Response "calling......"
And from what i read, this is the same for anybody despite hardware or software version.
You asking for some proof this is not workin implicates You fail to reproduce the problem, if that's the case, Please advice what hardware works. Otherwise you can get all the data from any equipment as it doesn't seem to work for anyone.
I can't remember when it last worked but that was at least 2 years ago and I've switched hw since then with no improvement.
IF you still need rhe reports, Please advice how to obtain them.
H�mta Outlook f�r Android<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Monday, February 28, 2022 9:51:33 AM
To: b-system+-1003794263@google.com <b-system+-1003794263@google.com>
Cc: magnus.kazen@gmail.com <magnus.kazen@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
vi...@google.com added
If the bug is reproducible, please capture a bugreport from Watch & Phone (both) and share with us for further investigation.
_______________________________
Reference Info: 172776291 Wear OS Essential Fuction of Google Assistant does not function
component: Android Public Tracker > Wear<
status: Assigned
reporter: jp...@gmail.com
assignee: na...@google.com
cc: jp...@gmail.com, na...@google.com
type: Bug
priority: P2
severity: S2
blocked by: 172994809<
duplicate issue: 174336713<
hotlist: [AOSP] assigned<
retention: Component default
ReportedBy: User
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
vi...@google.com <vi...@google.com> #343
Android Wear devices connected to Android devices
1. On you Android phone, following the instructions in this doc, under the section `Instructions on your companion phone or tablets (Android)’
2. Launch the ‘Android Wear’ app on your phone or tablet. Tap on the three vertical ellipsis on the top right hand corner of the screen and click on “Report Wearable Bug” to capture a bug report from the watch
3. On the watch, you will observe a notification card with the text “Bug report #X is being generated”. It can take up to 20 minutes for the bug report to be generated and transferred to your phone.
4. Once the bug report is done, the notification card on the watch changes to “Bug report #X captured” and you will receive a notification on the phone that reads “Wearable bug report finished. Tap to send." Tap on this notification and email the bug report to a pre populated email address
Instructions on your companion phone or tablets (Android)
1. On your Android device, go to Settings > About phone or About tablet.
2. At the bottom of the screen, touch 'Build number' seven times in quick succession. You’ll see a message saying you’re now in developer mode.
3. Press Back to go back to the main Settings screen.
4. Touch Developer options.
5. At the top of the screen, make sure 'Developer options' is set to ON.
6. Check the box next to USB debugging.
7. Check the box next to Bug report shortcut.
8. Reproduce the issue or error message on your phone or tablet. It’s important that your device logs at least one occurrence of the problem.
9. Immediately after seeing the issue, press and hold the power button until the power menu appears. Select Take bug report, then select Report in the dialog that follows.
11. After a significant delay -- up to two minutes -- your phone or tablet will vibrate and display a notification saying ‘Bug report captured’. Touch the notification to open Gmail with the report attached.
12. After replying to this message, you can disable developer mode and bug reports by going to Settings > Developer Options and sliding the top toggle to OFF.
vi...@google.com <vi...@google.com> #344 Restricted
ml...@gmail.com <ml...@gmail.com> #345
de...@gmail.com <de...@gmail.com> #346
ta...@gmail.com <ta...@gmail.com> #347
I returned my Fossil Gen 6 because there was no point to having it over a Gen 5 because of this issue.
lu...@gmail.com <lu...@gmail.com> #348
th...@gmail.com <th...@gmail.com> #349
za...@gmail.com <za...@gmail.com> #350
ph...@gmail.com <ph...@gmail.com> #351
da...@gmail.com <da...@gmail.com> #352
jo...@gmail.com <jo...@gmail.com> #353
ma...@gmail.com <ma...@gmail.com> #354
This bug is 2 years old.
There are a few possible explanations to why nothing happen.
1. They simply just don't care.
2. We as Customers have no value to them.
3. Their programmers are incompetent.
4. Their bug tracking system is malfunctioning.
5. The guy responsible for the bug is too embarassed to do anything.
6. They want users to switch to Apple.
7. Probably a few more...
In any case, demanding bugreports and logs from our units is mere bogus. They can test for themselves to get first hand info of the bug if they bothered. So the only reason for "collecting" more data is only to stall the issue instead of solving it.
H�mta Outlook f�r Android<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Friday, March 25, 2022 10:17:16 AM
To: b-system+-1003794263@google.com <b-system+-1003794263@google.com>
Cc: magnus.kazen@gmail.com <magnus.kazen@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
jo...@gmail.com added
What's the point in the watch if I can't use this key feature?!
_______________________________
Reference Info: 172776291 Wear OS Essential Fuction of Google Assistant does not function
component: Android Public Tracker > Wear<
status: Assigned
reporter: jp...@gmail.com
assignee: na...@google.com
cc: jp...@gmail.com, na...@google.com
type: Bug
priority: P2
severity: S2
blocked by: 172994809<
duplicate issue: 174336713<
hotlist: [AOSP] assigned<
retention: Component default
ReportedBy: User
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
de...@gmail.com <de...@gmail.com> #355
ta...@gmail.com <ta...@gmail.com> #356
da...@gmail.com <da...@gmail.com> #357
ph...@gmail.com <ph...@gmail.com> #358
back to fix a big in v2. Even a critical one like this.
On Sat, Mar 26, 2022, 1:51 AM <buganizer-system@google.com> wrote:
d....@gmail.com <d....@gmail.com> #359
How much simpler can it get? How can it be so hard to find a bug in a primary function that NEVER works, anywhere, EVER?
d....@gmail.com <d....@gmail.com> #360
ph...@gmail.com <ph...@gmail.com> #361
you feel better to raise it every day though.
On Sat, Mar 26, 2022, 3:50 PM <buganizer-system@google.com> wrote:
da...@gmail.com <da...@gmail.com> #362
ta...@gmail.com <ta...@gmail.com> #363
d....@gmail.com <d....@gmail.com> #364
ph...@gmail.com <ph...@gmail.com> #365
if media contact them and get a headline about how WearOS team use Apple
Watch then they may get some traction.
On Sun, Mar 27, 2022, 2:27 AM <buganizer-system@google.com> wrote:
ch...@gmail.com <ch...@gmail.com> #366
ta...@gmail.com <ta...@gmail.com> #367
vj...@gmail.com <vj...@gmail.com> #368
ja...@gmail.com <ja...@gmail.com> #369
ph...@datacom.com.au <ph...@datacom.com.au> #370
ph...@datacom.com.au <ph...@datacom.com.au> #371
m....@gmail.com <m....@gmail.com> #372
sl...@gmail.com <sl...@gmail.com> #373
no...@gmail.com <no...@gmail.com> #374
isn't required by law nor was it a advertised feature.
It's a feature I would like to see. And there is a 3rd party app that flips
the screen. But it would be great to have it as a standard feature.
On Thu, Dec 30, 2021, 10:04 PM <buganizer-system@google.com> wrote:
65...@gmail.com <65...@gmail.com> #375
Did you even read the ticket buddy? No-one has mentioned left handed mode. Everyone's problem is with the fact that Google assistant stopped functioning two years ago and Google hasn't been bothered to fix it despite being an extremely important feature.
A very advertised feature, I might add.
ko...@gmail.com <ko...@gmail.com> #376
ma...@gmail.com <ma...@gmail.com> #377
H�mta Outlook for Android<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Monday, July 4, 2022 3:00:41 PM
To: b-system+-1003794263@google.com <b-system+-1003794263@google.com>
Cc: magnus.kazen@gmail.com <magnus.kazen@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
ko...@gmail.com added
Google, this bug is 2 years old, google assistant still don't work on WearOS. FIX IT!!!
_______________________________
Reference Info: 172776291 Wear OS Essential Fuction of Google Assistant does not function
component: Android Public Tracker > Wear<
status: Assigned
reporter: jp...@gmail.com
assignee: na...@google.com
cc: jp...@gmail.com, na...@google.com
type: Bug
priority: P2
severity: S2
blocked by: 172994809<
duplicate issue: 174336713<
hotlist: [AOSP] assigned<
retention: Component default
ReportedBy: User
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
ph...@gmail.com <ph...@gmail.com> #378
critical bug. Best just return the watch and buy something else.
On Tue, Jul 5, 2022, 4:07 PM <buganizer-system@google.com> wrote:
ad...@google.com <ad...@google.com> #379
We would recommend checking if this is reproducible on a more recent version of Google app (12.8.3 or later) on the watch & share a bug report if reproducible.
ta...@gmail.com <ta...@gmail.com> #380
ja...@gmail.com <ja...@gmail.com> #381
ph...@gmail.com <ph...@gmail.com> #382
ga...@gmail.com <ga...@gmail.com> #383
ta...@gmail.com <ta...@gmail.com> #384
ph...@gmail.com <ph...@gmail.com> #385
I feel sorry for FitBit, getting bought out by a company that's going to close them down at this rate.
de...@gmail.com <de...@gmail.com> #387
- OK Google detection does not work from any state. With the watch awake (no lock configured) and my Galaxy S20+ unlocked, the keyword fails to elicit a response from the watch.
- manually activating the assistant with the topmost button on the watch, commands such as "call <contact list name>" take me to an assistant screen with no text at the top that offers me a choice to turn something on on my phone, or exit. The phone is unlocked during this test. Pressing the Turn On option results in an error, "Sorry, unable to obtain permissions".
- I've verified all permissions I'm aware of both on the phone's assistant settings and on the watch. Everything is set to allow.
- I've disabled and re-enabled the option for OK google detection with no impact.
So in a nutshell, the assistant still fails to perform any task hands free, and fails to make use of my contact list.
When manually activated, the Assistant does work better now than it did several months ago. Web search results work - I'm able to get a brief synopsis of the results on my watch, with a link to open the full results on my phone if I wish. Google Maps Directions also work as expected.
ch...@gmail.com <ch...@gmail.com> #388
mi...@gmail.com <mi...@gmail.com> #389
I'd imagine the class is too small for any threat of class action to be meaningful, but I'd definitely sign up if something happened.
de...@gmail.com <de...@gmail.com> #390
Thanks in advance.
da...@gmail.com <da...@gmail.com> #391
va...@gmail.com <va...@gmail.com> #392
They should be legally bound to make this work again.
Stating that they won't put any more effort in this as wear os 3 is the current focus is such BULLSHIT as this problem is already going on so long and they had some weird cooperation with Samsung (wtf was Samsung doing, pants down for a 2 year monopoly for selling devices with wear os 3 ??? Besides that they didn't have any contribution to the os. Much better battery lifetime for example ???)
al...@gmail.com <al...@gmail.com> #393
Because with no reason ticwatch watch started to drain battery, a continuous blinking battery icon on the second display even with charged battery and sensors stopped working. WTF
RETURN THIS WATCH if u are in warranty
ph...@gmail.com <ph...@gmail.com> #394
They're not present as Google have simply removed Assistant entirely. Nice. Good fix Google. Way to go.
ma...@gmail.com <ma...@gmail.com> #395
H�mta Outlook for Android<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Thursday, August 11, 2022 1:31:07 AM
To: b-system+-1003794263@google.com <b-system+-1003794263@google.com>
Cc: magnus.kazen@gmail.com <magnus.kazen@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
ph...@gmail.com added
@va Well the good news is these Assistant issues aren't present in the Wear OS 3 version for non-Samsung devices e.g. the Mont Blanc watch just released.
They're not present as Google have simply removed Assistant entirely. Nice. Good fix Google. Way to go.
_______________________________
Reference Info: 172776291 Wear OS Essential Fuction of Google Assistant does not function
component: Android Public Tracker > Wear<
status: Assigned
reporter: jp...@gmail.com
assignee: na...@google.com
cc: ad...@google.com, na...@google.com, vi...@google.com, and 1 more
type: Bug
priority: P2
severity: S2
blocked by: 172994809<
duplicate issue: 174336713<
hotlist: [AOSP] assigned<
retention: Component default
ReportedBy: User
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
ma...@gmail.com <ma...@gmail.com> #396
ta...@gmail.com <ta...@gmail.com> #397
ph...@gmail.com <ph...@gmail.com> #398
It's classic Google and shouldn't come as a surprise - they just abandon everything. The product head for Wear OS was recently quoted as saying Google were "absolutely committed" to Wear OS. I laughed so hard. Hope he's keeping his LinkedIn up to date as he'll no doubt be needing a new job soon when Wear OS gets canned.
ph...@gmail.com <ph...@gmail.com> #399
If this is the only P2 they've got, how is it taking 2 _years_ with no progress? Unless Google have abandoned Wear OS?
Please just tell us it will never be fixed, or at least some update. Anything really. Just some sort of proof-of-life that this bug list does actually show up somewhere.
Anyway. Back to Amazfit I guess. At least their stuff works.
da...@gmail.com <da...@gmail.com> #400
ph...@gmail.com <ph...@gmail.com> #401
ta...@gmail.com <ta...@gmail.com> #402
vi...@google.com <vi...@google.com> #403
As of August 31, 2023, Assistant is no longer supported on Wear OS versions 2.x and hence we are closing this bug as obsolete.
Assistant is available on Wear OS versions 3.x and later.
de...@gmail.com <de...@gmail.com> #404
mi...@gmail.com <mi...@gmail.com> #405
je...@gmail.com <je...@gmail.com> #406
gotten fired.
On Thu, Sep 7, 2023, 12:03 PM <buganizer-system@google.com> wrote:
ph...@gmail.com <ph...@gmail.com> #407
This is a worse abandonment than when they ditched Reader. I genuinely can't remember a company treating bugs, products and customers with such active disregard. If they are actually serious about playing in the wearable space then they have a very strange way of showing it.
Description