Obsolete
Status Update
Comments
sy...@google.com <sy...@google.com> #2
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
ndroid build
Which Android build are you using? (e.g. OPP1.170223.012)
Device used
Which device did you use to reproduce this issue?
Steps to reproduce
What steps are needed to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
What is the expected output?
Current output
What is the current output?
ndroid build
Which Android build are you using? (e.g. OPP1.170223.012)
Device used
Which device did you use to reproduce this issue?
Steps to reproduce
What steps are needed to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
What is the expected output?
Current output
What is the current output?
pi...@gmail.com <pi...@gmail.com> #3
Android build
Which Android build are you using? (e.g. OPP1.170223.012)
- LPBS23.13-56-2
Device used
Which device did you use to reproduce this issue?
- Moto G first Gen(Android 5.1)
Steps to reproduce
What steps are needed to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
- Same happened in attached project after crash
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
- When ever app crash(forcibly or exceptional )
Expected output
What is the expected output?
- It should restart accessibilityService after crash
Current output
What is the current output?
- After app crash AccessibilityService not restarting and not showing as in running service too.
Which Android build are you using? (e.g. OPP1.170223.012)
- LPBS23.13-56-2
Device used
Which device did you use to reproduce this issue?
- Moto G first Gen(Android 5.1)
Steps to reproduce
What steps are needed to reproduce this issue?
Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
- Same happened in attached project after crash
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
- When ever app crash(forcibly or exceptional )
Expected output
What is the expected output?
- It should restart accessibilityService after crash
Current output
What is the current output?
- After app crash AccessibilityService not restarting and not showing as in running service too.
r....@gmail.com <r....@gmail.com> #5
Please mention the reproduction steps to be followed for reproducing the issue with the given sample project.
br...@alignedmedia.com <br...@alignedmedia.com> #6
If you click on crash button that time the label value false after that if you want to start service you should go to setting to make disable and then again enable So it is working fine.
ji...@gmail.com <ji...@gmail.com> #7
I know its duplicate but need solution of this bug or issue... please
ri...@gmail.com <ri...@gmail.com> #8
Agreed, a solution needs to be found
ji...@gmail.com <ji...@gmail.com> #9
do...@gmail.com <do...@gmail.com> #10
Having the same problem with Ticwatch E and Oneplus 5
nk...@gmail.com <nk...@gmail.com> #11
Same here Pixel 2 and Huawei Sport Watch 2.
jt...@gmail.com <jt...@gmail.com> #12
Same issue.
Pixel 2, with Huawei Watch 2 Classic
Pixel 2, with Huawei Watch 2 Classic
sc...@gmail.com <sc...@gmail.com> #13
Pixel 2 XL and huawei watch 2 classic. Contacted google and huawei with no fix
es...@gmail.com <es...@gmail.com> #14
Same issue with Pixel 2XL and Ticwatch S
si...@googlemail.com <si...@googlemail.com> #15
Same here with a Huawei sport watch 2 and Pixel 2 XL. Exactly as described in the initial post.
ra...@gmail.com <ra...@gmail.com> #16
I'd like to add my voice to this. Experiencing the exact same issue.
bo...@gmail.com <bo...@gmail.com> #17
Same here, Huawei watch 2 and Xiaomi MI6.
ig...@gmail.com <ig...@gmail.com> #18
Play phone voice call on watch is disabled, but call notification does not play on watch if it's asleep.
waking watch up plays the notification almost instantly.
Other notifications seem to come through ok.
waking watch up plays the notification almost instantly.
Other notifications seem to come through ok.
br...@gmail.com <br...@gmail.com> #19
Same issue.
Pixel 2, with Huawei Watch 2 Classic
Pixel 2, with Huawei Watch 2 Classic
ro...@gmail.com <ro...@gmail.com> #20
Similar issue - Pixel 2 XL and Samsung Gear S2 watch.
ia...@gmail.com <ia...@gmail.com> #21
Exact same issue Pixel 2 XL and Huawei Watch 2. Core feature of watch is now disabled the call function until a resolution to the issue is available.
se...@gmail.com <se...@gmail.com> #22
Similar issue - Galaxy S8 plus and Fossil Q Explorist.
sy...@google.com <sy...@google.com> #23
Thanks for the reports. Can you please share the below details which will help us to narrow down the root cause?
Build number of connected phone:
Build number of Android Wear device:
Google Play services version:
Android Wear version:
Build number of connected phone:
Build number of Android Wear device:
Google Play services version:
Android Wear version:
su...@gmail.com <su...@gmail.com> #24
Phone build: OPM1.171019.013
Google play services build: 11.9.51 (940-177350961)
Watch build: NWD1.171016.002
Android Wear version: 2.7.0.177669439.gms
Pixel 2 XL and Huawei Watch 1
On Tue, Jan 16, 2018, 2:07 PM <buganizer-system@google.com> wrote:
Google play services build: 11.9.51 (940-177350961)
Watch build: NWD1.171016.002
Android Wear version: 2.7.0.177669439.gms
Pixel 2 XL and Huawei Watch 1
On Tue, Jan 16, 2018, 2:07 PM <buganizer-system@google.com> wrote:
ry...@gmail.com <ry...@gmail.com> #25
For me:
Phone build: 8.1.0 OPM1.171019.013
Google play services build: 11.9.51 (940-177350961)
Watch build: N7176C
Android Wear version: 2.7.0.177669439.gms
Pixel 2 XL and Huawei Watch 2
Phone build: 8.1.0 OPM1.171019.013
Google play services build: 11.9.51 (940-177350961)
Watch build: N7176C
Android Wear version: 2.7.0.177669439.gms
Pixel 2 XL and Huawei Watch 2
aj...@gmail.com <aj...@gmail.com> #26
Same here on my pixel and Huawei Watch 2
aj...@gmail.com <aj...@gmail.com> #27
Apologies
For me:
Phone build: 8.1.0 OPM1.171019.012
Watch Build: N7176C
Android Wear: 2.7.0.178645119
Google play services: 11.9.51 (530-177350961)
For me:
Phone build: 8.1.0 OPM1.171019.012
Watch Build: N7176C
Android Wear: 2.7.0.178645119
Google play services: 11.9.51 (530-177350961)
mr...@gmail.com <mr...@gmail.com> #28
Same with Pixel 2 XL and Huawei Watch 2.
bg...@gmail.com <bg...@gmail.com> #29
Same issue here. Interested in the fix.
bg...@gmail.com <bg...@gmail.com> #30
Build info
Phone build: 8.1.0 OPM1.171019.013
Watch Build: N7176C
Android Wear: 2.7.0.178645119
Google play services: 11.9.51 (530-177350961)
Phone build: 8.1.0 OPM1.171019.013
Watch Build: N7176C
Android Wear: 2.7.0.178645119
Google play services: 11.9.51 (530-177350961)
r....@gmail.com <r....@gmail.com> #31
Phone build number: OPM1.171019.013
Watch build number: OWR1.170919.023
Android Wear version (Watch): 2.8.0.181612071
Android Wear version (Phone): 2.7.0.180439970.gms
Google Play services version (Watch): 11.9.51 (530-177350961)
Google Play services version (Phone): 11.9.51 (940-177350961)
Watch build number: OWR1.170919.023
Android Wear version (Watch): 2.8.0.181612071
Android Wear version (Phone): 2.7.0.180439970.gms
Google Play services version (Watch): 11.9.51 (530-177350961)
Google Play services version (Phone): 11.9.51 (940-177350961)
ri...@gmail.com <ri...@gmail.com> #32
Build number of connected phone:
OPM1.171019.013
Build number of Android Wear device:
N7176C
Google Play services version:
11.9.73 (940-179769395)
Android Wear version:
2.7.0177669439.gms
Watch...
Google Play services version:
11.9.73 (530-179769395)
Android Wear version:
2.7.0.178645119
OPM1.171019.013
Build number of Android Wear device:
N7176C
Google Play services version:
11.9.73 (940-179769395)
Android Wear version:
2.7.0177669439.gms
Watch...
Google Play services version:
11.9.73 (530-179769395)
Android Wear version:
2.7.0.178645119
th...@gmail.com <th...@gmail.com> #33
I have the same issues on my Pixel 2 XL with 8.1 Oreo and 2.7 Android wear on the Huawei watch 2
vo...@gmail.com <vo...@gmail.com> #34
Hi Team,
I am also facing same issue after latest andorid wear upgrade. Waiting for resolution.
Device: Pixel 2XL
Watch: Fossil Q Explorist
PFA attached files for verison information.
I am also facing same issue after latest andorid wear upgrade. Waiting for resolution.
Device: Pixel 2XL
Watch: Fossil Q Explorist
PFA attached files for verison information.
my...@gmail.com <my...@gmail.com> #35
Me too... after latest wear upgrade, real bummer! Experia zx and Huawei 1
la...@gmail.com <la...@gmail.com> #36
Same issue on Huawei Watch and pixel 2xl
id...@gmail.com <id...@gmail.com> #37
Same issue Huawei Watch 2 and Pixel 2 (non XL)
an...@gmail.com <an...@gmail.com> #38
I am having the exact same problem. Worked fine before getting the Pixel 2. Now I have turn off the feature and cannot pick up a call directly on the watch, which is a shame. Please fix this, f
Google!
Cheers
Google!
Cheers
ia...@gmail.com <ia...@gmail.com> #39
Same issue on Huawei Watch 2 and pixel 2xl
an...@gmail.com <an...@gmail.com> #41
I have tried that APK already and it did not solve the issue :(
an...@gmail.com <an...@gmail.com> #42
Unfortunately the issues still persist, even with the release og Google Phone APP 16.0.182967520: when the option to pick up the call directly on my Huawei Watch is turned on and I pick up the call on my smartphone there's like a 13 seconds delay until I and the other person can hear each other. This is definitely not Pixel 2 related since it started happening when my previously Android One project Xiaomi Mi A1 was updated to Android 8.0 Oreo.
GOOGLE PLEASE FIX THIS PROBLEM!
GOOGLE PLEASE FIX THIS PROBLEM!
ad...@gmail.com <ad...@gmail.com> #43
Why is the severity of this issue not higher? It breaks a core function of our devices.
sy...@google.com <sy...@google.com> #44
Thanks for the updates. We are working on this issue and will provide updates as they are available.
as...@gmail.com <as...@gmail.com> #45
Same here :(
sa...@gmail.com <sa...@gmail.com> #46
Same here!!
ja...@gmail.com <ja...@gmail.com> #47
Same issue. Pixel 2 XL and Huawei watch 2. Really frustrating.
an...@gmail.com <an...@gmail.com> #48
Google support team: I just got the update for the Google Phone App, version 16. 0.183307769.
Was this version released to solve this issue?
Cheers
Was this version released to solve this issue?
Cheers
an...@gmail.com <an...@gmail.com> #49
I just checked it. It's still not working. This is is one of the main reasons I've bought an android wear smartwatch, please fix this fast, Google...
r....@gmail.com <r....@gmail.com> #50
Still facing the same issue.
When I pick up an incoming phone call on my Google Pixel 2, the caller's voice cannot be heard, neither on the LG Watch Sport nor the Google Pixel 2 for around 10 seconds. Also, the caller cannot hear my voice either. Most caller's hang up by this time. I end up wasting time in calling them back.
Hack to get this working:
Pick up the call on my watch first, then switch the audio from "Bluetooth" to "Phone". The only problem with this is that for 2-3 seconds, the caller's voice is routed via the watch's speakers, causing everyone around to hear the conversation! :(
Expected behaviour:
When I pick up a call on my watch, the sound should be routed immediately via the watch; when I pick up a call on my phone, the sound should be routed immediately via the phone.
Please fix this issue.
When I pick up an incoming phone call on my Google Pixel 2, the caller's voice cannot be heard, neither on the LG Watch Sport nor the Google Pixel 2 for around 10 seconds. Also, the caller cannot hear my voice either. Most caller's hang up by this time. I end up wasting time in calling them back.
Hack to get this working:
Pick up the call on my watch first, then switch the audio from "Bluetooth" to "Phone". The only problem with this is that for 2-3 seconds, the caller's voice is routed via the watch's speakers, causing everyone around to hear the conversation! :(
Expected behaviour:
When I pick up a call on my watch, the sound should be routed immediately via the watch; when I pick up a call on my phone, the sound should be routed immediately via the phone.
Please fix this issue.
ed...@gmail.com <ed...@gmail.com> #51
Having this issue as well. This is a serious issue should be higher priority.
ni...@gmail.com <ni...@gmail.com> #52
Pixel 2 and Huawei Watch 2 Sport same issue. The issue cannot be reproduced with any other phone I have and tried 3 other phones: Pixel, Nexus 5X and Nexus 5.
The issue only occurs with Pixel 2. My conclusion: the problem is in Pixel 2. Could you please confirm that the problem is indeed in Pixel 2, not the watch? If yes, why is this issue under Android Wear? Should be escalated to Pixel 2 team.
Build number of connected phone: opm1.171019.013
Build number of Android Wear device: N7176C
Google Play services version: 11.0.55 (534-156917137)
Android Wear version: 2.0.0.166801816
I agree with other users, this is a critical issue that needs to be escalated. It breaks core functionality of the watch.
The issue only occurs with Pixel 2. My conclusion: the problem is in Pixel 2. Could you please confirm that the problem is indeed in Pixel 2, not the watch? If yes, why is this issue under Android Wear? Should be escalated to Pixel 2 team.
Build number of connected phone: opm1.171019.013
Build number of Android Wear device: N7176C
Google Play services version: 11.0.55 (534-156917137)
Android Wear version: 2.0.0.166801816
I agree with other users, this is a critical issue that needs to be escalated. It breaks core functionality of the watch.
as...@gmail.com <as...@gmail.com> #53
Same thing happens to me! I have the watch since before I bought Pixel 2, the watch worked fine with Nexus 6P! Will have to return the Pixel 2 and will wait for Pixel 3 :(
pe...@gmail.com <pe...@gmail.com> #54
Having same issue using pixel 2 and fossil q explorist. If I go to watch settings: Bluetooth and turn off play phone voice call on watch. Then it allows me to answer phone call on pixel 2 without a delay. But does not allow me to use the watch for phone calls.
Andriod wear 2.8.0.182823779
Build number OWD4.171214.002
Pixel2 running andriod 8.1.0
Build number OPM1.171019.013
Andriod wear 2.8.0.182823779
Build number OWD4.171214.002
Pixel2 running andriod 8.1.0
Build number OPM1.171019.013
ra...@gmail.com <ra...@gmail.com> #55
Same here - Enabling "Play phone voice call on watch" causes phone apps to lag for 10+ seconds and results in no audio/mic on Pixel 2 XL & Michael Kors Access Grayson. - Please note that disabling "Play phone voice call on watch" is NOT really a workaround -- it is disabling a listed feature used to sell the watch.
This has been a known issue for months. It's ridiculous that this bug hasn't been fixed yet. Please fix this Google.
This has been a known issue for months. It's ridiculous that this bug hasn't been fixed yet. Please fix this Google.
bo...@gmail.com <bo...@gmail.com> #56
Same issue here. Please fix!!
gd...@gmail.com <gd...@gmail.com> #57
Same issue here.
Pixel 2 and Huawei watch 2
Pixel 2 and Huawei watch 2
pi...@gmail.com <pi...@gmail.com> #58
To everyone coming here: Please stop commenting "me too", "same issue here" and star the bug instead (left to the title on top of the page).
You're effectively e-mailing ~40 people every time you add your message and burying useful google devs/support responses.
https://issuetracker.google.com/issues/71010564#comment44 is the last known staff response
Thanks.
You're effectively e-mailing ~40 people every time you add your message and burying useful google devs/support responses.
Thanks.
an...@gmail.com <an...@gmail.com> #59
Me too.
sy...@google.com <sy...@google.com> #60
This bug has a dependency with Pixel 2 & 2XL audio framework. Our Android phone & wear teams working on this issue. Thanks for your patience and will provide updates as they are available.
jo...@gmail.com <jo...@gmail.com> #61
Thanks for the update however i'm not 100% sure this is only Pixel 2 / 2 XL related. When i have Android wear connected to the Samsung Note 8 with call audio enabled on the watch, most it not all VOIP apps (Duo, hangouts etc) will hang (like described above) or have other audio issues when trying to make or receive a call.
It's like these apps try to route the audio to the watch (as it is connected to "phone audio" BT profile) but was not able to because the watch does not act as a true audio Bluetooth, so they freeze.
I have both the Note 8 and the Pixel 2 XL and aside from the native phone dialer issue described here other VOIP apps have the same issue on both phones when wear is connected to the phone with "phone audio" enabled.
It's like these apps try to route the audio to the watch (as it is connected to "phone audio" BT profile) but was not able to because the watch does not act as a true audio Bluetooth, so they freeze.
I have both the Note 8 and the Pixel 2 XL and aside from the native phone dialer issue described here other VOIP apps have the same issue on both phones when wear is connected to the phone with "phone audio" enabled.
an...@gmail.com <an...@gmail.com> #62
Yesterday there was yet another update for the Google Phone App. But, the issue is still unsolved. I don't get it.
sy...@google.com <sy...@google.com> #63
For comment #61 , can you share the bug reports from Samsung Note 8 and Android wear? (after reproducing the issue)
jo...@gmail.com <jo...@gmail.com> #64
I will be happy to send a bug report from the Note 8 showing apps that hang once an android wear watch has call audio enabled but i would prefer not share it publicly.
Can i just email the report without sharing the link on this thread? If so, what email should i use?
Thanks.
Can i just email the report without sharing the link on this thread? If so, what email should i use?
Thanks.
sy...@google.com <sy...@google.com> #65
Please upload the bug reports and screenshots to google drive and share the folder to android-bugreport@google.com, then share the link here.
Note: Give access to "android-bugreport@google.com" which restricts the access to public and provides access to Google team.
Note: Give access to "android-bugreport@google.com" which restricts the access to public and provides access to Google team.
sc...@gmail.com <sc...@gmail.com> #66
February patch had this in the notes. As soon as I get the OTA I will report if this is indeed the fix
A-68874871 Audio Improved routing when switching audio outputs. Pixel 2, Pixel 2 XL.
This might also fix the headphone issues not switching when plugging in
A-68874871 Audio Improved routing when switching audio outputs. Pixel 2, Pixel 2 XL.
This might also fix the headphone issues not switching when plugging in
an...@gmail.com <an...@gmail.com> #67
Dear Google support team, would you be so kind as to answer my question?:
The culprit seems to be the there's been several Google Phone App since this critical bug was reported and identified, how come none of the updates fixed it yet?
The culprit seems to be the there's been several Google Phone App since this critical bug was reported and identified, how come none of the updates fixed it yet?
sy...@google.com <sy...@google.com> #68
For comment #67 , can you please share the bug reports from Android Wear and connected phone if the issue is still reproducible?
an...@gmail.com <an...@gmail.com> #69
@sy...@google.com
Certainly. Can you please tell how do I do that, step by step? Cheers
Certainly. Can you please tell how do I do that, step by step? Cheers
sy...@google.com <sy...@google.com> #70
Please refer to comment #2 for details steps. Thanks
jo...@gmail.com <jo...@gmail.com> #71
@google support: I just tested again with the Note 8 and it seems that the January update fixed the issues with VOIP apps hanging while the watch is connected with call audio. This still happens on the Pixel 2 XL though, even after the February update released today.
What seems to have been fixed is the stock dialer on the Pixel 2 XL, will not be able to answer calls while the watch is connected without hanging for 10-15 seconds. Other VOIP apps such as Duo, still hang.
What seems to have been fixed is the stock dialer on the Pixel 2 XL, will not be able to answer calls while the watch is connected without hanging for 10-15 seconds. Other VOIP apps such as Duo, still hang.
ra...@gmail.com <ra...@gmail.com> #72
@google support' I have tested again with a Pixel 2 XL and an LG Watch Sport after updating to the February security patch - with some interesting results:
Answering calls with the watch connected still results with calls hanging for 10-15 seconds when incoming calls are answered when the screen is already on (not fixed).
It does appear to be fixed (it doesn't hang for 10-15 seconds) when an incoming call is answered from the sleep screen or AOD.
I'm not sure why having answering a call with the screen on or off would matter, but it appears to. I tried multiple test calls to verify this behavior.
Answering calls with the watch connected still results with calls hanging for 10-15 seconds when incoming calls are answered when the screen is already on (not fixed).
It does appear to be fixed (it doesn't hang for 10-15 seconds) when an incoming call is answered from the sleep screen or AOD.
I'm not sure why having answering a call with the screen on or off would matter, but it appears to. I tried multiple test calls to verify this behavior.
ra...@gmail.com <ra...@gmail.com> #73
Further tests indicate the February security patch did not fix this issue - it still hangs for 10-15 seconds arbitrarily. Very disappointing.
de...@gmail.com <de...@gmail.com> #74
I am facing the issue for the past 2 months. Running android 7.11 and android wear 2.8
an...@gmail.com <an...@gmail.com> #75
I just received today YET ANOTHER Google Phone App update (the last was just days ago) but the problem remains... Very disappointing indeed.
wi...@gmail.com <wi...@gmail.com> #76
Pixel 2xl + Huawei watch 2 classic same problem
Seems to happen after I charge my watch
Seems to happen after I charge my watch
th...@gmail.com <th...@gmail.com> #77
Same issue here.
Pixel 2 XL and Huawei Watch 2
Pixel 2 XL and Huawei Watch 2
ad...@gmail.com <ad...@gmail.com> #78
I today manually updated Pixel 2 over ADB hoping to finnaly get working calls on my huawei watch 2. bug still present. tryed to reset phone and watches, no change. Now I cannot set "Call voice over watch" this option in watches disappiered. Really dissapointed.
ro...@gmail.com <ro...@gmail.com> #79
Pixel 2xl and huawei watch(1th gen) same problem. I reported this issue by pixel support in 6th dec 2017. No issue with paired nexus 5x.
as...@gmail.com <as...@gmail.com> #80
I bought my phone in November 2017, Today I went back to the shop with the phone. They were very helpful. They are replacing it with same pixel 2 but different build number. I am to pick up the new phone on Tuesday (13th Feb) do you think it will fix the problem or they have also offered to replace it with different brand. What should I do?
pc...@gmail.com <pc...@gmail.com> #81
Same issue
Pixel 2xl & Asus Zenwatch 3.
Pixel 2xl & Asus Zenwatch 3.
as...@gmail.com <as...@gmail.com> #82
are you all from Australia?
je...@gmail.com <je...@gmail.com> #83
From all described asbove, I also have the same issues. Will send bug reports to Google later on today/tomorrow. Have a Pixel 2 XL and a Huawei Watch Classic and Fossil Q Explorist
sc...@gmail.com <sc...@gmail.com> #84
So is it the Pixel team's fault or Android Wear's fault? I just want this fixed and I am tired of the run around.
as...@gmail.com <as...@gmail.com> #85
This things happens sometimes! It is just a little fault with the phone. Don't let it make you angry! Just get it replaced! Poor Google is already having lots of trouble with pixels. 😒
http://www.patentlyapple.com/patently-apple/2018/02/a-7-count-class-action-has-been-filed-against-google-for-their-faulty-pixel-and-pixel-xl-smartphones.html
ic...@gmail.com <ic...@gmail.com> #86
I have managed to sort it out! You should go to your watch Settings/Personalisation/ and switch off 'Ok Google' detection. That's it! It worked for me, so, now, I am very happy I can use my watch at it's best!
an...@angelo-x.com <an...@angelo-x.com> #87
Recently bought a ticwatch E and was super excited until i recieved my first phone call and tried to answer it on my phone, try to answer it, no audio regardless of switching from phone, bluetooth (watch), or speaker.
If caller waits long enough it will eventually connect but typically the caller will hang up way before, im getting at least a 10-15 delay, in the rare cases the caller waits, my watch THEN starts ringing even when im already connected and speaking with the caller on my phone.
I am using a google pixel 2
If caller waits long enough it will eventually connect but typically the caller will hang up way before, im getting at least a 10-15 delay, in the rare cases the caller waits, my watch THEN starts ringing even when im already connected and speaking with the caller on my phone.
I am using a google pixel 2
ra...@gmail.com <ra...@gmail.com> #88
Switching off "OK Google" detection does not fix the issue. The issue still persists despite this setting.
ic...@gmail.com <ic...@gmail.com> #89
It doesn't work immediately, I switched it off this morning and realized it works only this afternoon
ry...@gmail.com <ry...@gmail.com> #90
I have always had "ok googl"e detection off and bug is still there.
jo...@gmail.com <jo...@gmail.com> #91
Turning off "OK google" detection has nothing to do with this issue and does not solve it.
as...@gmail.com <as...@gmail.com> #92
I have got my phone replaced with another pixel 2 but still the same :(
Apart from the issue with my HW2 I really like the phone! I will just have to wait till google fixes the problem :(
Apart from the issue with my HW2 I really like the phone! I will just have to wait till google fixes the problem :(
sc...@gmail.com <sc...@gmail.com> #93
February security update did not fix the issue. There have been multiple updates to the phone app, huawei watch app and the issue is still not fixed....
[Deleted User] <[Deleted User]> #94
Oreo update on watch has not resolved this - I did not think it would more hopeful anyway just so people know.
rm...@gmail.com <rm...@gmail.com> #95
Would like to chime in. Having this issue on Google Pixel 2 (Verizon) and Huawei Watch 2 running Android Wear 2 (latest Android 8.0).
an...@gmail.com <an...@gmail.com> #96
I don't understand this. Many users with this issue, going on for months now. Multiple updates to the Google Phone App and the issue, a feature we all expect to use on our smartwatchs, a Google refuses to fix this.
Google Support Team, why can't you fix this once for all?
Cheers
Google Support Team, why can't you fix this once for all?
Cheers
mr...@gmail.com <mr...@gmail.com> #97
This is same on original Pixel XL with Huawei Watch 2 Classic. But after reboot of both devices I no longer have option for calls on watch under Bluetooth on phone.
en...@gmail.com <en...@gmail.com> #98
I have tried three watches Huawei watch 2, Fossil Q Explorist, and Gear S2 with my Pixel 2 XL same problem with calls on all of them , new update did not fix.
as...@gmail.com <as...@gmail.com> #99
Did you try with hw2 after orio update
sc...@gmail.com <sc...@gmail.com> #100
I got Oreo on the watch and it still happens. I think it's on the pixel side, not the watch side....
as...@gmail.com <as...@gmail.com> #101
Thank you sc...@gmail.com for the reply! We may just have to wait till we get Android 9😣
Meanwhile what I do is turn off the Bluetooth in my phone. I know I can turn off phone calls through Bluetooth setting but turning off Bluetooth is easy. Turn it on if I want to use my watch!
I can understand is would be very difficult for Google to get it 100% right as there are thousands of combinations out there with so many devices available with Android. Google should come out with pixel watch!
Meanwhile what I do is turn off the Bluetooth in my phone. I know I can turn off phone calls through Bluetooth setting but turning off Bluetooth is easy. Turn it on if I want to use my watch!
I can understand is would be very difficult for Google to get it 100% right as there are thousands of combinations out there with so many devices available with Android. Google should come out with pixel watch!
jo...@gmail.com <jo...@gmail.com> #102
To the google rep from #60, Do you think the fix will be in on March update for the pixels?
The current issue kinda makes Android wear as a phone extension useless on the Pixels. Not to mention bad user experience for people buying the phone, buying Android wear and have no idea why when they answer a call they don't hear anything or having a VOIP app like Duo freeze.
The current issue kinda makes Android wear as a phone extension useless on the Pixels. Not to mention bad user experience for people buying the phone, buying Android wear and have no idea why when they answer a call they don't hear anything or having a VOIP app like Duo freeze.
sy...@google.com <sy...@google.com> #103
This issue is fixed in internal builds of Android wear and the fix is in testing phase. As of now, we don't have a committed release date for this fix since it does have a dependency with Android framework [Pixels code]. We will provide updates when the fix is available to public. Thank you very much for your patience.
an...@gmail.com <an...@gmail.com> #104
Thanks for your answer. Please keep us posted and let us know when it's indeed fixed so we can turn that setting on and use our promised Dick Tracy watches again ;)
Cheers
Cheers
as...@gmail.com <as...@gmail.com> #105
Good things happen to those who wait! 😁
li...@gmail.com <li...@gmail.com> #106
I'm having the same issue. Pixel 2XL with Tic watch E. 10 seconds before I can hear anything on my phone on an incoming call.
sc...@gmail.com <sc...@gmail.com> #107
Oreo on the watch did not correct the issue. C'mon on google, get it together!
jo...@gmail.com <jo...@gmail.com> #108
@ comment #103
https://issuetracker.google.com/issues/71010564#comment103
Great that the issue is fixed internally. Does this mean that the fix would need to come out as an android wear OS update or a Pixel OS update?
If it's on the watch side, this can take long months as i'm sure none of the watches OEMs will actually push a software update any time soon considering they just release Oreo for the watches.
If it's a fix for just the Pixel, this can come as a part of a monthly security update.
Please let us know.
Great that the issue is fixed internally. Does this mean that the fix would need to come out as an android wear OS update or a Pixel OS update?
If it's on the watch side, this can take long months as i'm sure none of the watches OEMs will actually push a software update any time soon considering they just release Oreo for the watches.
If it's a fix for just the Pixel, this can come as a part of a monthly security update.
Please let us know.
th...@gmail.com <th...@gmail.com> #109
same here
fl...@gmail.com <fl...@gmail.com> #110
Ughhhhhh. I got rid of my Gear S3 and switched to Huawei Watch 2 thinking that it should fix the problem. Turns out it's my Pixel 2 XL. Ughhhhhh. Fix this issue please. We are not getting the full potential of the watch!
th...@gmail.com <th...@gmail.com> #111
issue solved by being auto-updated to android wear 2.8
do...@gmail.com <do...@gmail.com> #112
Mine still defaults to Bluetooth output when answering with my phone most
of the time, meaning I have to change to handset mode. Haven't had the 10
second hang anymore though. Can we have it so it defaults to handset mode
if you answer with your handset and to Bluetooth if you answer with your
watch?
On Feb 25, 2018 3:19 AM, <buganizer-system@google.com> wrote:
of the time, meaning I have to change to handset mode. Haven't had the 10
second hang anymore though. Can we have it so it defaults to handset mode
if you answer with your handset and to Bluetooth if you answer with your
watch?
On Feb 25, 2018 3:19 AM, <buganizer-system@google.com> wrote:
fl...@gmail.com <fl...@gmail.com> #113
Is it possible to beta test the internal build?
do...@gmail.com <do...@gmail.com> #114
Definitely NOT working. Just updated to the latest Android Wear app today
2/26 and still takes about 10-13 seconds to get audio on my handset.
On Feb 25, 2018 6:56 PM, <buganizer-system@google.com> wrote:
2/26 and still takes about 10-13 seconds to get audio on my handset.
On Feb 25, 2018 6:56 PM, <buganizer-system@google.com> wrote:
fl...@gmail.com <fl...@gmail.com> #115
Huawei Watch 2 Classic and Pixel 2 XL. Updated to AW 2.9 on both watch and phone. Still the same issue as of 2/27/18. Hoping that we'll see the fix in the upcoming security update. Cheers.
jk...@gmail.com <jk...@gmail.com> #116
Same issue here. Pixel 2 XL and Hawaei sport watch 2. Answer on my phone transfers to the watch. Incredibly annoying.
ne...@gmail.com <ne...@gmail.com> #117
Same here , Pixel 2, Huawei watch sport 4G
an...@gmail.com <an...@gmail.com> #118
Still reproducable on pixel 2xl piared with huawei watch
rm...@gmail.com <rm...@gmail.com> #119
Also the same issue. Pixel 2, Huawei Watch 2
ra...@gmail.com <ra...@gmail.com> #120
Is the fix in the internal Android Wear build near ready for public release? This has been going on for months.
rm...@gmail.com <rm...@gmail.com> #121
It must be nearly ready, as they marked my ticket (very similar to this one) as "Fixed":
https://issuetracker.google.com/issues/73252778
It just says "The development team has fixed the issue that you have reported and it will be available in a future build". Hopefully that means soon.
It just says "The development team has fixed the issue that you have reported and it will be available in a future build". Hopefully that means soon.
fl...@gmail.com <fl...@gmail.com> #122
March security update should start pushing today. Can someone check if they included the fix?
jo...@gmail.com <jo...@gmail.com> #123
The issue of VOIP apps freezing when the watch is connected with "Phone audio" has not been fixed in March update.
ra...@gmail.com <ra...@gmail.com> #124
I believe the fix is in an internal Wear build, not the phone build.
as...@gmail.com <as...@gmail.com> #125
It is already March! Android P should come out soon 😋
Android N and Android O both were released in March! 🤓
Android N and Android O both were released in March! 🤓
ro...@gmail.com <ro...@gmail.com> #126
march update does not fix this issue
pixel2xl + huawei watch
pixel2xl + huawei watch
as...@gmail.com <as...@gmail.com> #127
Has anyone tried Android P?
fl...@gmail.com <fl...@gmail.com> #128
Any update on this? Can someone please keep up posted? I would really hate for this issue to just get pushed in the back burner just because Android P is around the corner. I spent my hard earned money on this watch and phone.
as...@gmail.com <as...@gmail.com> #129
This things can happen! I know it is hassle but you can always give your phone back if you can put up with Samsung galaxy blotware or lg-Nokia-OnePlus no updates 🙄. Google is very generous with refunds. Admit it! Even with a few bugs pixel has no competition out there.
ro...@gmail.com <ro...@gmail.com> #130
It is totaly shame for google that their flagship (especially when you pay extra money for "software with hardware") does not work in this case for 5 months. Whatsmore android wear platform does not have a good period of lifecycle and you cannot use your watches to call what is one of the top features why people buying android wear smartwatches.
First dirty trick from google was that they removed voice typing from android wear to my native language after aw2.0 update and now I cant reply to messages by voice but I can deal with this. But this issue is beyond the imaginary boundary of acceptance.
First dirty trick from google was that they removed voice typing from android wear to my native language after aw2.0 update and now I cant reply to messages by voice but I can deal with this. But this issue is beyond the imaginary boundary of acceptance.
an...@gmail.com <an...@gmail.com> #131
I totally agree with the last post. 5 months to solve this bug is unacceptable.
tm...@gmail.com <tm...@gmail.com> #132
Dear Wear Team,
Please work on this issue!
Please work on this issue!
sc...@gmail.com <sc...@gmail.com> #133
The lack of communication is pretty awful too.
fr...@gmail.com <fr...@gmail.com> #134
Same issue and hardware here
jo...@gmail.com <jo...@gmail.com> #135
I can confirm this is resolved on Android P. Duo and other VOIP apps no longer freeze when the watch is connected with phone audio enabled.
an...@gmail.com <an...@gmail.com> #136
That's great but not a realistic solution. I'm not installing a beta software just to solve this problem and I find it outrageous if I have to do wait for September (when Android P will be released) for a fix!
ru...@russellbryce.com <ru...@russellbryce.com> #137
Same. Pixel 2 XL and Asus ZenWatch 3. Haven't been able to receive calls on my phone without major issues for almost 4 months.
as...@gmail.com <as...@gmail.com> #138
Is Android P usable? When is beta coming out?
as...@gmail.com <as...@gmail.com> #139
Do we have to wait till google I/O 2018 (Mid May?)
mr...@gmail.com <mr...@gmail.com> #140
Yay! Confirmed working Android P DP1, Pixel 2 XL, Huawei Watch 2.
Pe...@weyandt.com <Pe...@weyandt.com> #141
I am having the same issue. Google Pixel XL phone. LG Sport watch. Both are updated to current builds. (phone: 8.1.0 March build / Watch: Wear 2.9.0.185193291)
Is there a work around or a way to turn off phone calls to the watch until this is resolved? It makes calls on my phone very difficult to use. I have not been able to find a workaround other than installing the beta version of Android P.
thanks.
Is there a work around or a way to turn off phone calls to the watch until this is resolved? It makes calls on my phone very difficult to use. I have not been able to find a workaround other than installing the beta version of Android P.
thanks.
an...@gmail.com <an...@gmail.com> #142
You go to the settings on your smartwatch - connectivity - Bluetooth - and turn off the setting of reproducing audio on the smartwatch, this is will turn of the option of earing the calls directly on the watch.
ru...@russellbryce.com <ru...@russellbryce.com> #143
Installed the latest security patch on my Pixel 2 XL this week. Test calls are working great so far this morning. No more 30 second delay of not hearing each other on the phone, weird call waiting beeps, etc. Can take calls on the phone without problems, and can take calls on the watch (Asus ZenWatch 3) no problems. I don't know if Google fixed it, or if I've just been lucky so far. ;)
as...@gmail.com <as...@gmail.com> #144
Installing Android P did not solve the issue for me :(
Pixel 2 - Huawei Watch 2
Pixel 2 - Huawei Watch 2
an...@gmail.com <an...@gmail.com> #145
I have the March update and the issue is still present. Very disappointing :(
ra...@gmail.com <ra...@gmail.com> #146
Please, everyone here scroll up and read post #103. It says "This issue is fixed in internal builds of Android wear and the fix is in testing phase. As of now, we don't have a committed release date...". This issue is addressed in internal WEAR builds. Until a Wear build with the fix is released, this issue will not be resolved. Could someone at Google update us on when this will be released? That post was a month ago.
sy...@google.com <sy...@google.com> #147
Thanks for your patience. This fix is not yet released to public from Wear OS team. However, the Wear OS fix might not solve the issue alone. As we mentioned in comment #103 , it does have dependency with Android Pixel framework code. Our Android Pixel Framework team is working on stable fix for this issue and we will provide updates when the fix is available to public.
as...@gmail.com <as...@gmail.com> #148
Android Wear just turned in to Wear OS! It seems google is not serious about wearable (not just talking about this bug). When talking about market share Wear Os comes distant third, after Apple at 1st & Samsung at 2nd. In other word Wear Os is Microsoft mobile Os of wearable. It should not surprise us if it is discontinued in a year or two just like Microsoft mobiles.
sm...@gmail.com <sm...@gmail.com> #149
Exact same issue here essential ph1 Oreo 8.1 and ticwatch S and wear24 watches both exhibit same behavior. Ticwatch running Android Wear 2.9.0 and Google Play services 12.2 21
ro...@gmail.com <ro...@gmail.com> #150
Interesting. I thought that this is only pixel related problem because my nexus 5x does not facing to this issue.
as...@gmail.com <as...@gmail.com> #151
I understand that pixel phones are not targeted to the retail markets and are targeted towards the tech enthusiasts and issues like this are expected but Wear Os is total mess! Hope things will change soon.
https://www.gizmodo.com.au/2018/03/googles-smartwatch-program-is-a-mess-and-a-name-change-wont-fix-that/
rm...@gmail.com <rm...@gmail.com> #152
Goodbye Android Wear, hello Wear OS! All the same wonderful problems with a shiny new name.
ma...@gmail.com <ma...@gmail.com> #153
I've been refraining from commenting on this because i know everyone gets emailed when a new one shows up but it's getting a bit ridiculous. I bought and android wear watch to use with my pixel 2 XL, just for the fact that i wanted to be able to answer calls on it. That main functionality is broke and it looks like google has all but abandoned android wear/ wearOS, whatever they want to name it. Combine that with the fact that qualcomm has pretty much killed these devices by not making and new chips. I guess maybe time to switch to Tizen... at least Samsung's watches work. Supposedly it's fixed internally. and some have reported Android P allowing it to work but I'm not about to install a beta OS on my daily driver just to fix my watch.
jo...@gmail.com <jo...@gmail.com> #154
I was the one who stated that Android P had this fixed, but I was wrong.
It appeared as if it was fixed but that was because the Bluetooth stack is currently broken in P so this issue does not happen because most VOIP apps I tested with don't seem to be able to connect to any Bluetooth headset on P, hence the freeze problem never happened when the watch was connected.
Can the Google employee from comment #147 clarify if this fix will require an update to BOTH the watch AND the Pixel phones? or just our phones?
If the watches need to be updated, will it require and Android OS update or a WatchOS update? These are two very different updates. I'm pretty sure most OEM's will never push an Android OS update to any of the current aging phones so these watches will be stuck with this bug forever. Can you kindly clarify how this fixed will be rolled out?
It appeared as if it was fixed but that was because the Bluetooth stack is currently broken in P so this issue does not happen because most VOIP apps I tested with don't seem to be able to connect to any Bluetooth headset on P, hence the freeze problem never happened when the watch was connected.
Can the Google employee from
If the watches need to be updated, will it require and Android OS update or a WatchOS update? These are two very different updates. I'm pretty sure most OEM's will never push an Android OS update to any of the current aging phones so these watches will be stuck with this bug forever. Can you kindly clarify how this fixed will be rolled out?
ga...@gmail.com <ga...@gmail.com> #155
Issue happens for me to - Fossil Q Explorist and Pixel 2 both with latest versions
Pixel 2 -
Android version 8.1.0
Build Number OPM1.171019.021
Fossil Q Exploris-
Build Number - OWD4.171214.002
Cant believe a bug like this was not picked up in testing let alone beta testing...
Pixel 2 -
Android version 8.1.0
Build Number OPM1.171019.021
Fossil Q Exploris-
Build Number - OWD4.171214.002
Cant believe a bug like this was not picked up in testing let alone beta testing...
ra...@gmail.com <ra...@gmail.com> #156
This issue is with with Pixel 2 & Pixel 2 XL. Same thing happens when paired with a Samsung Gear S3 - so it's not solely an issue that can be corrected with a new Wear OS build. There has to be something going on with Pixel framework code. Again, if this is happening with Tizen & Wear OS watches, a new Wear build isn't the solution.
fl...@gmail.com <fl...@gmail.com> #157
I have both Gear S3 and Huawei Watch 2. Yes I can also confirm the same behavior with Gear S3.
do...@gmail.com <do...@gmail.com> #158
I had and returned the Gear 3 because I thought this issue was a
compatibility issue between stock Android and Tizen. Then tried the Huawei
and was disappointed, now have the LG sportwatch and am still having the
same issue. So yes, it is on all three watch models and bot platforms.
On Mon, Mar 19, 2018, 9:21 AM <buganizer-system@google.com> wrote:
compatibility issue between stock Android and Tizen. Then tried the Huawei
and was disappointed, now have the LG sportwatch and am still having the
same issue. So yes, it is on all three watch models and bot platforms.
On Mon, Mar 19, 2018, 9:21 AM <buganizer-system@google.com> wrote:
ra...@gmail.com <ra...@gmail.com> #159
This is totally and completely unacceptable. FIVE MONTHS ON A CRITICAL FUNCTION??? I am contacting Google today for a full refund of my Pixel 2 XL, as this is clearly an issue with their flagship phone. This is ridiculous. This phone should never have been released with this Bluetooth issue - much less sold for close to $1000.
ma...@gmail.com <ma...@gmail.com> #160
I would have to second the frustration. For a giant like Google to allow this bug to go unfixed for so long on a flagship phone is unacceptable. And I switched from 10 years of iPhone to get this phone. I love this phone but you are right. That's a core function. And the fact that it's not just isolated to wearos and Samsung's watches have the same issue says a lot. I'm glad I didn't go out and buy a gear. Supposedly they fixed it according to admin. But they have yet to release it to us.
fl...@gmail.com <fl...@gmail.com> #161
Anyone else receive the "Wear OS" update today? Downloading it now. Not sure if it will fix anything though. Will keep everyone posted.
fl...@gmail.com <fl...@gmail.com> #162
I can confirm that updating to Wear OS on both Huawei Watch 2 and Pixel 2XL did not fix the issue. It was probably just a cosmetic update.
ke...@gmail.com <ke...@gmail.com> #163
I installed the update and restarted both the P2XL and Huawei watch 2 and found there was no 10 second delay. Not sure if its a fluke or not but will test more tomorrow.
do...@gmail.com <do...@gmail.com> #164
Wear OS update on the phone did not fix the issue. Was hopeful. I didn't
get any watch updates, just an update to make Android Wear turn into Wear
OS.
🙄
On Mon, Mar 19, 2018, 9:28 PM <buganizer-system@google.com> wrote:
get any watch updates, just an update to make Android Wear turn into Wear
OS.
🙄
On Mon, Mar 19, 2018, 9:28 PM <buganizer-system@google.com> wrote:
ro...@gmail.com <ro...@gmail.com> #165
I can confirm that update did not fix the issue.
Pixel 2xl and huawei watch( 1th gen.)
to comment #163 :
restart of watch and phone makes sometime first incoming call ok but the another ones are muted for 12 secs.
Pixel 2xl and huawei watch( 1th gen.)
to
restart of watch and phone makes sometime first incoming call ok but the another ones are muted for 12 secs.
ro...@gmail.com <ro...@gmail.com> #166
Do you know what is the funny part of this issue?
At the every single Google event managment staff had on the hand android wear watch and in their hands pixel phone. If they really use pixel and android wear they should reveal this issue before us :)
At the every single Google event managment staff had on the hand android wear watch and in their hands pixel phone. If they really use pixel and android wear they should reveal this issue before us :)
sh...@gmail.com <sh...@gmail.com> #167
Same issue for me with Google pixel 2 xl and Fossil Q wander.very disappointed since I just switched over to Android from IOS and I never had these problems.about to take this phone back and get something else or go back to Apple which is depressing because I like a lot of these features but phone calls are a necessity on a phone
bc...@gmail.com <bc...@gmail.com> #168
Same issue with Google Pixel 2 XL and LG Watch Sport. Initially the pairing worked fine, it was only after an update in January that the delay on the phone become an issue.
do...@gmail.com <do...@gmail.com> #169
It goes back before January, I bought my LG watch sport in November and it
was happening then.
On Tue, Mar 20, 2018, 11:40 PM <buganizer-system@google.com> wrote:
was happening then.
On Tue, Mar 20, 2018, 11:40 PM <buganizer-system@google.com> wrote:
ro...@gmail.com <ro...@gmail.com> #170
I have pixel 2xl from december and it was there.
fl...@gmail.com <fl...@gmail.com> #171
Level of severity for this issue should be increased. This is currently on P1. It should be P0 - "An issue that needs to be addressed immediately and with as many resources as is required. Such an issue causes a full outage or makes a critical function of the product to be unavailable for everyone, without any known workaround".
tm...@gmail.com <tm...@gmail.com> #172
It absolutely should!!!
At the very least, seed some of us to beta test the builds that are working. Do something. I returned both my Grayson and TicWatch E because I thought that this problem laid with those devices. I repurchased the Grayson in hopes that this issue would be fixed quickly.
Many more customers will be experiencing this problem. What is Google going to do if it becomes more widely known that it's the Pixel is at fault?
For a company who employs some of the most intelligent technicians and engineers, it's baffling that Google has no idea how to make Bluetooth work properly. It's a technology that's more than a decade old...yet here we are dealing with a most basic function.
At the very least, seed some of us to beta test the builds that are working. Do something. I returned both my Grayson and TicWatch E because I thought that this problem laid with those devices. I repurchased the Grayson in hopes that this issue would be fixed quickly.
Many more customers will be experiencing this problem. What is Google going to do if it becomes more widely known that it's the Pixel is at fault?
For a company who employs some of the most intelligent technicians and engineers, it's baffling that Google has no idea how to make Bluetooth work properly. It's a technology that's more than a decade old...yet here we are dealing with a most basic function.
ri...@gmail.com <ri...@gmail.com> #173
Same issue here, huawei watch 2 and pixel 2
sh...@gmail.com <sh...@gmail.com> #174
Same issue. Call delay of about 5 seconds on Ticwatch S from OnePlus 5!
sc...@gmail.com <sc...@gmail.com> #175
Wear OS update 2.10 on the phone and watch did not fix the issue. GOOGLE PLEASE RESPOND!
sc...@gmail.com <sc...@gmail.com> #176
We shouldn't have to beg.....
br...@gmail.com <br...@gmail.com> #177
How is this STILL an issue? Infuriating.
fl...@gmail.com <fl...@gmail.com> #178
SEVERITY LEVEL MUST BE ADJUSTED TO P0.
st...@gmail.com <st...@gmail.com> #179
Same issue.
Pixel 2, with Huawei Watch 2 Classic
Pixel 2, with Huawei Watch 2 Classic
pr...@gmail.com <pr...@gmail.com> #180
Same issue.
Pixel 2, with Huawei Watch 2 Classic
Pixel 2, with Huawei Watch 2 Classic
ma...@gmail.com <ma...@gmail.com> #181
Same issue. Pixel 2 XL and Huawei Watch 2 Sport
jo...@gmail.com <jo...@gmail.com> #182
Same issue. Pixel 2 XL and Huawei Watch 2 Sport
ha...@gmail.com <ha...@gmail.com> #183
Same issue - Pixel 2XL and Huawei 2 Classic.
rm...@gmail.com <rm...@gmail.com> #184
> For a company who employs some of the most intelligent technicians and engineers, it's baffling that Google has no idea how to make Bluetooth work properly. It's a technology that's more than a decade old...yet here we are dealing with a most basic function.
> We shouldn't have to beg.....
> SEVERITY LEVEL MUST BE ADJUSTED TO P0.
Having switched from iPhone to Pixel 2, I can say that I've never seen an operating system so disorganized, dysfunctional, and neglected: my battery level varies by the end of the day with consistent usage depending on what 'mood' my phone is in after having done the 8.1.0 update, the stock keyboard freezes up frequently, photos aren't downloaded to the phone from the Photos app after a phone restore and only recoverable by zip download, WiFi Calling is consistently unstable (zero issues on iOS), Allo chat still buzzes my phone when I'm in Allo for Web, and the list goes on.
I'm scared to think about the other things that might be swept under the rug that aren't known about yet, let alone this critical issue that just about turned 3 months old with no fix in sight, interfering with the phone service we pay monthly to use and not having it work. Next upgrade simply won't be a Google branded smartphone. There's no reason anybody should have to spend over $600 only to deal with an unstable operating system for a device they generally spend a few hours every day on, the ~$250 that an Android smartwatch costs, and a phone feature that doesn't work when connected to said smartwatch. I feel like we're the guinea pigs being used to test their broken software while other manufacturers slowly push out updates to their users. We are not the consumers, we are the products, and we're literally paying them for that "experience".
> We shouldn't have to beg.....
> SEVERITY LEVEL MUST BE ADJUSTED TO P0.
Having switched from iPhone to Pixel 2, I can say that I've never seen an operating system so disorganized, dysfunctional, and neglected: my battery level varies by the end of the day with consistent usage depending on what 'mood' my phone is in after having done the 8.1.0 update, the stock keyboard freezes up frequently, photos aren't downloaded to the phone from the Photos app after a phone restore and only recoverable by zip download, WiFi Calling is consistently unstable (zero issues on iOS), Allo chat still buzzes my phone when I'm in Allo for Web, and the list goes on.
I'm scared to think about the other things that might be swept under the rug that aren't known about yet, let alone this critical issue that just about turned 3 months old with no fix in sight, interfering with the phone service we pay monthly to use and not having it work. Next upgrade simply won't be a Google branded smartphone. There's no reason anybody should have to spend over $600 only to deal with an unstable operating system for a device they generally spend a few hours every day on, the ~$250 that an Android smartwatch costs, and a phone feature that doesn't work when connected to said smartwatch. I feel like we're the guinea pigs being used to test their broken software while other manufacturers slowly push out updates to their users. We are not the consumers, we are the products, and we're literally paying them for that "experience".
sy...@google.com <sy...@google.com> #185
Thanks for all the updates. As we already informed in comment #103 , #147; this issue is already fixed in our internal builds. We are in the process of releasing the fix to public. We regret for the inconvenience caused to you with this bug and thanks for your patience.
de...@gmail.com <de...@gmail.com> #186
Same issue with a TicWatch 2 up-to-date (3/28). Call on my Pixel will ring and end, and then up to a minute later, my watch will ring as if the call is just coming through.
sc...@gmail.com <sc...@gmail.com> #187
@sy yes but we would like to know which needs to be updated for the fix. Is it the phone app, the wear os build, or april security update?
ni...@gmail.com <ni...@gmail.com> #188
I am having the same issue with my Pixel 2 and my Huawei 2 classic. I will turn the voice call on watch off, however, this is something that needs to be fixed as it's one of the main reasons I bought the watch as well. I see that sy has said (#185 comment) that this is going to be released soon, my question is will it be released with the speed that the other fixes will be released or will we have to wait for our carriers to approve.
rh...@gmail.com <rh...@gmail.com> #189
Same issue is happening with my Mi A1 ( Android One Device) and Asus Zenwatch 2 ( Wear Os version : 2.10.. ). Hoping for a quick fix.
fl...@gmail.com <fl...@gmail.com> #190
Please elaborate "we are in the process of releasing the fix to public" Is that happening now? Any target date? Will it be through an update of Wear OS app? April security patch? Having the "fix" is no use to us, the "public" if we cannot access it. Or at least let us know when we should anticipate it.
ge...@gmail.com <ge...@gmail.com> #191
Same issue. Pixel 2 XL and Huawei Watch 2 Sport.
Just purchased the Watch this weekend, and it was horrible experience. I could not answer any calls, until I turned off the Bluetooth on my phone. I love everything else about the watch but answering calls should not be this frustrating with my Pixel paired to it.
Just purchased the Watch this weekend, and it was horrible experience. I could not answer any calls, until I turned off the Bluetooth on my phone. I love everything else about the watch but answering calls should not be this frustrating with my Pixel paired to it.
sc...@gmail.com <sc...@gmail.com> #192
April security update for Pixel 2 XL did not fix the issue.
jo...@gmail.com <jo...@gmail.com> #193
@sc bummer, looking at the change log it looked promising as there were a lot of fixes to the media framework. How are you testing to confirm it's still broken?
sc...@gmail.com <sc...@gmail.com> #194
@jo Using my work phone to call my pixel 2. Has the same delay when the watch is connected. Therefore, not fixed.
th...@gmail.com <th...@gmail.com> #195
Mine seems to be working correctly now. Updated with April patch. Calls coming into Pixel 2 XL can be answered without the 10 second delay. I will try switching from watch to phone and receive a few more calls. But it hasn't worked this well in ages.
th...@gmail.com <th...@gmail.com> #196
Ok confirmed it's working. I'm able to receive a call, answer it on my watch, while talking, I can use the audio drop down on the Pixel 2 XL's phone app to change the audio from Bluetooth (Huawei Watch 2) to phone's internal speaker, then to external speaker, then back to watch with little delay.
sc...@gmail.com <sc...@gmail.com> #197
@th that has always worked. The bug is answering a call directly on the phone. The first call usually works but subsequent calls do not.
ha...@gmail.com <ha...@gmail.com> #198
Seems to be working for me after the April patch. Less then a sec delay. Have tested answering with watch and phone several times. It defaults to Bluetooth when answering with phone, but switches to phone mic and speaker automatically after a sec approx. Will do some more testing. Pixel 2 and Tichwatch e.
jo...@gmail.com <jo...@gmail.com> #199
Can anyone check using a VOIP app like Google Duo? Those are freezing for at least 10 sec when the watch was connected as phone audio and a call with these VOIP apps were answered.
If anyone here uses Google Duo, please try to place a call while the watch is connected as phone audio, wait for the call to be answered and see if it freezes as it tries to route the call to the watch?
If anyone here uses Google Duo, please try to place a call while the watch is connected as phone audio, wait for the call to be answered and see if it freezes as it tries to route the call to the watch?
tm...@gmail.com <tm...@gmail.com> #200
Can anyone from the Wear OS Team confirm that the April Security patch repaired this issue?
ni...@gmail.com <ni...@gmail.com> #201
This issue is still occurring. I have rebooted my phone and watch 20 times and it worked once. Just once. I wonder if this will be fixed when Wear OS P comes out?
fl...@gmail.com <fl...@gmail.com> #202
So some people are saying it works and some are saying it doesn't. Can you guys confirm the version of Wear OS on your device for those who have it working?
th...@gmail.com <th...@gmail.com> #203
Rebooted both phone and watch and still no delay when answering calls on phone or watch. Wear OS ver 01 and Android OS 8.0.0 on my watch.
an...@gmail.com <an...@gmail.com> #204
I just tried on my Pixel 2 with April update and my original Huawei Watch and it works. Let´s hope it stays that way.
gr...@gmail.com <gr...@gmail.com> #205
Still a problem with my Pixel 2 (latest April update) and my urbane 2 lte (wear os 2.10). I can manually switch inside the phone app and get sound that way, but it needs to happen automatically like it used to.
th...@gmail.com <th...@gmail.com> #206
Same issue. As originally described. It worked for a few calls, but it is definitely back again. Holy very frustrating. Wear is 1 Android version 8.0.0 with Pixel 2 XL and Huawei Watch 2. Issue has not been fixed.
rm...@gmail.com <rm...@gmail.com> #207
Issue is not fixed on Verizon Pixel 2, Android OS 8.1.0 with latest April security update / bug fixes applied.
mr...@gmail.com <mr...@gmail.com> #208
Android P Developer Preview was released for Huawei Watch 2 (selected Bluetooth versions). The Google guys said that this was fixed in internal builds. I don't believe it has been specified whether this is Wear OS, Wear Android OS, Or Phone Android OS.
Has anyone tested with the Android P developer release on the Huawei watch 2?
Has anyone tested with the Android P developer release on the Huawei watch 2?
pj...@gmail.com <pj...@gmail.com> #209
Seems to be working fine for me. Unbranded Pixel 2 (with April security update) and Fossil Q Explorist watch. I've tried a few calls and it worked fine, I hope it will stick.
do...@gmail.com <do...@gmail.com> #210
Tried it earlier today with the April security fix on my Pixel 2 XL. It
worked a few times then switched over to the same old 10+ second delay
issue.. restarted both the watch and phone several times before turning off
the voice to watch feature again. Guess it's not fixed yet..... At some
point the release will become a priority 😑 between the mesh wireless issue
and this, I feel like I'm striking out with this phone 😕
On Tue, Apr 3, 2018, 3:41 AM <buganizer-system@google.com> wrote:
worked a few times then switched over to the same old 10+ second delay
issue.. restarted both the watch and phone several times before turning off
the voice to watch feature again. Guess it's not fixed yet..... At some
point the release will become a priority 😑 between the mesh wireless issue
and this, I feel like I'm striking out with this phone 😕
On Tue, Apr 3, 2018, 3:41 AM <buganizer-system@google.com> wrote:
ro...@gmail.com <ro...@gmail.com> #211
April security patch did not fix this issue. Pixel2xl and huawei watch(1th gen). Same issue perssist, no matter if I restart both devices.
an...@gmail.com <an...@gmail.com> #212
I take back what I've said before. It worked the first time and now it doesn't work anymore!! Very irritating indeed.
PLEASE FIX THIS ONCE FOR ALL, GOOGLE!
PLEASE FIX THIS ONCE FOR ALL, GOOGLE!
jk...@landmarkschool.org <jk...@landmarkschool.org> #213
Patch did not fix for Pixel 2 XL running android 8.1 and Wear24 running 7.1.1. I have tried the restarts also and no luck.
fl...@gmail.com <fl...@gmail.com> #214
After testing for a day, I had the same conclusion as comment #210 . It works sometimes. Currently on April security update, Android Oreo 8.1.0 . Wear version 2.10.0.188560295.gms. I will definitely keep this experience in mind for my next phone purchase.
li...@gmail.com <li...@gmail.com> #215
I was so excited to answer a call on my Pixel 2, but it was short
lived...the next caller hung up because of the 10-12 second delay that is
now consistently happening again. Pixel 2, Huawai watch, Verizon carrier,
frustrated user.
On Mon, Apr 2, 2018, 9:10 PM <buganizer-system@google.com> wrote:
lived...the next caller hung up because of the 10-12 second delay that is
now consistently happening again. Pixel 2, Huawai watch, Verizon carrier,
frustrated user.
On Mon, Apr 2, 2018, 9:10 PM <buganizer-system@google.com> wrote:
ha...@gmail.com <ha...@gmail.com> #216
Patch did very little change. I can answer phone calls on my Huawei 2 Classic, but there is a significant delay when answering phone calls on Pixel 2XL with April patch installed. I had to disable answering call on watch. I feel we're supporting a startup company and allowing the competition to look good!
fl...@gmail.com <fl...@gmail.com> #217
There is just no sense of urgency here. Even with P0 S1 status. There should be more people involved. I won't be surprised if a class action lawsuit gets started.
sc...@gmail.com <sc...@gmail.com> #218
The lack of information from Google sucks. Just saying "we have fixed internally and we will post when released" means nothing if you don't say what needs updating. The wear os build, the google app, the May security update, the phone app? Like...which is it?????
ra...@gmail.com <ra...@gmail.com> #219
This will be my last comment to this thread. I have been following this thread since January and experiencing the issue since I first got the phone about a month after launch. I went through 3 different Pixel 2 XLs and multiple watches trying to correct the issue. Google at first told me my phone was defective - multiple phones used because of that diagnosis to no avail.
I then tried multiple Android Wear / Wear OS watches with no success. I even tried a Tizen Gear S3. Same issue. I waited patiently and tried every update to Wear and to the phone app, security update patches - you name it.
The December patch came - no fix. Then came the January patch came - no fix. Then the February patch came - and no fix.
I waited patiently as a Google rep on this thread first told is there was an internal fix back in February. He said it was fixed in an internal Wear build - but it did have a dependency on the Pixel Audio Framework. This was interesting considering this issue exists when paired with a Tizen watch - so clearly an Android Wear build alone can't solve the issue. If I'm wrong about this, please let me know.
Of course when that was posted in February, he could not tell us any specifics beyond what was vaguely referenced in the post and no time commitment was given other than "soon".
Well, the March security patch came and no fix. No fix in the April patch either. Android Wear was changed to Wear OS and no fix there either.
I reached out to the Google Store and requested a full refund based on this mess. It took over week and several calls - hours of my time. But finally, they agreed to do the right thing and granted my refund request.
I got a Samsung S9+ and a Gear S3 and there is NO ISSUE using the watch as a phone and the phone as a phone. It is so refreshing to use a phone and a watch that work as advertised.
Google will be announcing the Pixel 3 line this September or October. I wonder how many following this thread will consider that phone? I don't know if this issue will be fixed by then.
If you're tired of waiting, I can tell you moving on from this phone is the only thing that solved the issue for me.
I then tried multiple Android Wear / Wear OS watches with no success. I even tried a Tizen Gear S3. Same issue. I waited patiently and tried every update to Wear and to the phone app, security update patches - you name it.
The December patch came - no fix. Then came the January patch came - no fix. Then the February patch came - and no fix.
I waited patiently as a Google rep on this thread first told is there was an internal fix back in February. He said it was fixed in an internal Wear build - but it did have a dependency on the Pixel Audio Framework. This was interesting considering this issue exists when paired with a Tizen watch - so clearly an Android Wear build alone can't solve the issue. If I'm wrong about this, please let me know.
Of course when that was posted in February, he could not tell us any specifics beyond what was vaguely referenced in the post and no time commitment was given other than "soon".
Well, the March security patch came and no fix. No fix in the April patch either. Android Wear was changed to Wear OS and no fix there either.
I reached out to the Google Store and requested a full refund based on this mess. It took over week and several calls - hours of my time. But finally, they agreed to do the right thing and granted my refund request.
I got a Samsung S9+ and a Gear S3 and there is NO ISSUE using the watch as a phone and the phone as a phone. It is so refreshing to use a phone and a watch that work as advertised.
Google will be announcing the Pixel 3 line this September or October. I wonder how many following this thread will consider that phone? I don't know if this issue will be fixed by then.
If you're tired of waiting, I can tell you moving on from this phone is the only thing that solved the issue for me.
fl...@gmail.com <fl...@gmail.com> #220
If I have to wait another month just to get the bluetooth phone function working properly then I too will consider getting a refund.
sc...@gmail.com <sc...@gmail.com> #221
I am not going the nuclear option because of 1 bug. I wish we would get a response but the pros of the Pixel 2 XL outweigh any cons.
sy...@google.com <sy...@google.com> #222
Thank you very much for your patience and support. We regret for the inconvience caused. We pushed the fix to public and the fix should be available to all users. This fix should be available to all Huawei Watch 2, LG Sport devices with rebranding update.
To verify rebranding OTA on Android Wear:
1. You should observe Wear OS by Google boot animation logo when the device is booting
2. Settings -> System -> About -> Versions -> Wear OS by Google -> 1.0
We tested with below devices and public builds to verify the fix and working as expected.
Wear Device: Huawei Watch 2 & Build Number: OWDD.180215.018
Phone: Pixel 2 XL & Build Number: OPM2.171019.029
Links to factory images:
https://developers.google.com/android/ota#taimen
https://developer.android.com/wear/releases/wear-preview-downloads.html
If you have latest OTA on your Wear OS device & Pixel phone and the issue is still reproducible. Please share the below details to investigate further.
1. Bug report from phone & wear device
2. Detailed steps to reproduce the issue
3. Did you reset your Wear device and checked whether the issue is fixed or not?
To verify rebranding OTA on Android Wear:
1. You should observe Wear OS by Google boot animation logo when the device is booting
2. Settings -> System -> About -> Versions -> Wear OS by Google -> 1.0
We tested with below devices and public builds to verify the fix and working as expected.
Wear Device: Huawei Watch 2 & Build Number: OWDD.180215.018
Phone: Pixel 2 XL & Build Number: OPM2.171019.029
Links to factory images:
If you have latest OTA on your Wear OS device & Pixel phone and the issue is still reproducible. Please share the below details to investigate further.
1. Bug report from phone & wear device
2. Detailed steps to reproduce the issue
3. Did you reset your Wear device and checked whether the issue is fixed or not?
gr...@gmail.com <gr...@gmail.com> #223
To be clear on the "the fix should be able to all users" vs "This fix should be available to all Huawei Watch 2, LG Sport devices with rebranding update" .... Will an LG urbane 2 LTE that has the rebranding update get this fix?
sy...@google.com <sy...@google.com> #224
Yes, all the devices which has rebranding OTA should have fix for this issue. Please update us if you didn't get the OTA or didn't fix the issue.
th...@gmail.com <th...@gmail.com> #225
I'm running Wear OS version 1 on Huawei Watch 2 and Pixel 2 XL with 8.1.0 and still having audio delays as originally described.
Thank you
Thank you
fl...@gmail.com <fl...@gmail.com> #226
Do we have to re-pair the watch? A number of people updated to the latest security patch mentioned that it's working "sometimes". In my case, calling out from my phone has no 10 second lag. However, I get the 10 second lag with incomming calls.
bo...@gmail.com <bo...@gmail.com> #227
Still no Rebranding OTA on my LG Watch Sport so I'll have to wait for it
before I can test.
Versions on LG Watch Sport are as follows:
Wear OS 2.10.0.188487362
Google Play Services 12.5.21
Android OS 8.0.0
Android Security Patch Level October 1, 2017
LG Watch Sport Build Number OWR1.170919.018
Thank you if you can help
Kenneth Booth | Pitbull Dad | Medicated for YOUR protection
🔫🗡️☠️ I Support Ritual Killings! ☠️🗡️🔫
On Wed, Apr 4, 2018, 6:40 PM <buganizer-system@google.com> wrote:
before I can test.
Versions on LG Watch Sport are as follows:
Wear OS 2.10.0.188487362
Google Play Services 12.5.21
Android OS 8.0.0
Android Security Patch Level October 1, 2017
LG Watch Sport Build Number OWR1.170919.018
Thank you if you can help
Kenneth Booth | Pitbull Dad | Medicated for YOUR protection
🔫🗡️☠️ I Support Ritual Killings! ☠️🗡️🔫
On Wed, Apr 4, 2018, 6:40 PM <buganizer-system@google.com> wrote:
an...@gmail.com <an...@gmail.com> #228
I own the original Huawei Watch and don't have any OTA update, I just checked. Are you sure I'll get it?
Cheers
Cheers
sy...@google.com <sy...@google.com> #229
If the issue is still reproducible or didn't receive latest OTA, please share the below details to investigate further. We can't investigate further without the bug report. Hence, all our test devices are working with rebranding OTA.
1. Bug report from phone & wear device
2. Detailed steps to reproduce the issue
3. Did you reset your Wear device and checked whether the issue is fixed or not?
Instructions to capture Android Mobile/Tablet bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
Instructions to capture Android Wear bug report:-
1. Make sure your phone is in developer mode, by going to Settings > About phone and tapping 7 times on the build number.
2. Launch the Android Wear app.
3. Open the menu in the top right corner of the app.
4. Tap "Report Wearable Bug".
5. You should feel a confirmation vibration from your watch. If you look at the card stream on the watch you will see a card with the text "Bug report Collecting data..."
6. Once the bug report is complete you will feel two short vibrations on the watch. You will also see a card in the stream that reads "Bug report captured. Swipe left to share your bug". Swipe left on this card. Tap the Open button in the subsequent screen.
7. Return to your phone or tablet and open the shade. You will seen an entry that reads "Wearable bug report finished. Touch to send.". Touch this entry and upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
1. Bug report from phone & wear device
2. Detailed steps to reproduce the issue
3. Did you reset your Wear device and checked whether the issue is fixed or not?
Instructions to capture Android Mobile/Tablet bug report:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
Instructions to capture Android Wear bug report:-
1. Make sure your phone is in developer mode, by going to Settings > About phone and tapping 7 times on the build number.
2. Launch the Android Wear app.
3. Open the menu in the top right corner of the app.
4. Tap "Report Wearable Bug".
5. You should feel a confirmation vibration from your watch. If you look at the card stream on the watch you will see a card with the text "Bug report Collecting data..."
6. Once the bug report is complete you will feel two short vibrations on the watch. You will also see a card in the stream that reads "Bug report captured. Swipe left to share your bug". Swipe left on this card. Tap the Open button in the subsequent screen.
7. Return to your phone or tablet and open the shade. You will seen an entry that reads "Wearable bug report finished. Touch to send.". Touch this entry and upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
gr...@gmail.com <gr...@gmail.com> #230
My urbane 2 LTE with the rebranding update still has a build number of NWD1.171031.001
So I'm still waiting for an update apparently, please correct me if I'm wrong.
So I'm still waiting for an update apparently, please correct me if I'm wrong.
sy...@google.com <sy...@google.com> #231
For #230, if you have a rebranding OTA then you should have a fix for this issue. Each device has different build number. The build number what we specified is only for Huawei Watch 2.
gr...@gmail.com <gr...@gmail.com> #232
Ok thank you, I'll get a bug report asap.
jo...@gmail.com <jo...@gmail.com> #233
@ sy@google.com
The issue in the OP is also discussing the same freeze when using Google Duo and other VOIP apps.
My Pixel 2 XL with the latest April OTA and my Fossil Explorist which was updated via OTA to the rebrand OS still has Google Duo and other VOIP apps freeze for 10+ seconds when answering calls or making calls that are answered on the other side.
Did this fix address only the phone app calling issue? or should it fix also Duo, WhatsApp and other apps that can make VOIP Calls?
They all try to use the watch as a Bluetooth headset and freeze for 10+ seconds.
The issue in the OP is also discussing the same freeze when using Google Duo and other VOIP apps.
My Pixel 2 XL with the latest April OTA and my Fossil Explorist which was updated via OTA to the rebrand OS still has Google Duo and other VOIP apps freeze for 10+ seconds when answering calls or making calls that are answered on the other side.
Did this fix address only the phone app calling issue? or should it fix also Duo, WhatsApp and other apps that can make VOIP Calls?
They all try to use the watch as a Bluetooth headset and freeze for 10+ seconds.
bg...@gmail.com <bg...@gmail.com> #234
Still have the issue with Huawei Watch 2 Sport and pixel 2. Sent email to email address that was provided.
sy...@google.com <sy...@google.com> #235
can you share the link here?
mh...@gmail.com <mh...@gmail.com> #238
rm...@gmail.com <rm...@gmail.com> #239
Wear Device: Huawei Watch 2 & Build Number: OWDD.180215.018
https://drive.google.com/file/d/1f3zNOtIETg3sfOPuvcOCLrvcNuLDkM2c/view?usp=sharing
Phone: Pixel 2 & Build Number: OPM2.171019.029
https://drive.google.com/file/d/1iXpuf5w_H5geWwH8BtseDm5zYO_4IDmC/view?usp=sharing
Issue is not fixed on Verizon Pixel 2, Android OS 8.1.0 with latest April security update / bug fixes applied.
Phone: Pixel 2 & Build Number: OPM2.171019.029
Issue is not fixed on Verizon Pixel 2, Android OS 8.1.0 with latest April security update / bug fixes applied.
do...@gmail.com <do...@gmail.com> #240
Issue not fixed on Pixel 2 XL with LG Sportwatch with latest updates.
On Wed, Apr 4, 2018, 10:27 PM <buganizer-system@google.com> wrote:
On Wed, Apr 4, 2018, 10:27 PM <buganizer-system@google.com> wrote:
sc...@gmail.com <sc...@gmail.com> #241
Have the rebranded build on Huawei watch 2 with pixep 2 xl. Still reproduced the issue.
ha...@gmail.com <ha...@gmail.com> #242
Have the rebranded build on Huawei 2 Classic watch with Pixel 2 XL. Issue still alive and well.
an...@gmail.com <an...@gmail.com> #243
What's the "rebranded build"? Can someone please confirm if the first generation Huawei Watch received any OTA update, has the moderator said? Are ALL the Android Wear watches supposed to receive it or just the last gen ones?
Cheers
Cheers
ro...@gmail.com <ro...@gmail.com> #244
huawei watch 1th gen:
last update of wearos/android wear app by google play: Mar 9, 2018
last system/os update: Oct 5, 2017
android version: 7.1.1
last update of wearos/android wear app by google play: Mar 9, 2018
last system/os update: Oct 5, 2017
android version: 7.1.1
an...@gmail.com <an...@gmail.com> #245
Thanks for your answer. But weren't we all supposed to get a OTA update at the same time? I don't get it...
gd...@gmail.com <gd...@gmail.com> #246
Problems still exists 10-12 second delay in response
Phone: Pixel 2 & Build Number: OPM2.171019.029
Wear: Huawei Watch 2 0027 (classic) Build Number: OWDD. 180215.018
On Thu, 5 Apr 2018, 11:44 am , <buganizer-system@google.com> wrote:
Phone: Pixel 2 & Build Number: OPM2.171019.029
Wear: Huawei Watch 2 0027 (classic) Build Number: OWDD. 180215.018
On Thu, 5 Apr 2018, 11:44 am , <buganizer-system@google.com> wrote:
gd...@gmail.com <gd...@gmail.com> #247
Also for #246
Phone: Android version: 8.1.0 security patch 5 April 2018
Wear: Android version: Wear OS by Google 8.0.0 security patch 1 March 2018
Phone: Android version: 8.1.0 security patch 5 April 2018
Wear: Android version: Wear OS by Google 8.0.0 security patch 1 March 2018
ni...@gmail.com <ni...@gmail.com> #248
Wear Device: Huawei Watch 2 & Build Number: OWDD.180215.018
Phone: Pixel 2 & Build Number: OPM2.171019.029
Bug report captured and sent.
Phone: Pixel 2 & Build Number: OPM2.171019.029
Bug report captured and sent.
fl...@gmail.com <fl...@gmail.com> #249
Mine seems to be working now. Hope it sticks! Not sure if it had anything to do with the recent phone app update. But before the phone app update, I was still experiencing lag when receiving calls.
Wear Device: Huawei Watch 2 & Build Number: OWDD.180215.018
Phone: Pixel 2 & Build Number: OPM2.171019.029
Phone app: 5.9191094625
Good luck to everyone!
Wear Device: Huawei Watch 2 & Build Number: OWDD.180215.018
Phone: Pixel 2 & Build Number: OPM2.171019.029
Phone app: 5.9191094625
Good luck to everyone!
sy...@google.com <sy...@google.com> #250
Updates:-
1. AT&T didn't push the OTA for their LG Sport Watch devices due to some technical reasons. We are following up with them and will provide updates as they are available.
2. This rebranding OTA is released only for Huawei Watch 2, LG Sport Watch 2, Fossil Q Explorist and other newer devices
3. This rebranding OTA is not available for LG Watch Urbane, Huawei Watch 1, Asus Zen gen 2 & 3 and other older devices. These devices has to wait for Pixel 2 & 2XL fixes as we discussed in earlier comments.
4. If the issue is reproducible after upgrading to rebranding OTA, then please capture the bug reports from Android Wear & phone (after reproducing the issue). Refer comment #229 for more details on capturing the bugreports.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here (important).
1. AT&T didn't push the OTA for their LG Sport Watch devices due to some technical reasons. We are following up with them and will provide updates as they are available.
2. This rebranding OTA is released only for Huawei Watch 2, LG Sport Watch 2, Fossil Q Explorist and other newer devices
3. This rebranding OTA is not available for LG Watch Urbane, Huawei Watch 1, Asus Zen gen 2 & 3 and other older devices. These devices has to wait for Pixel 2 & 2XL fixes as we discussed in earlier comments.
4. If the issue is reproducible after upgrading to rebranding OTA, then please capture the bug reports from Android Wear & phone (after reproducing the issue). Refer
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here (important).
gr...@gmail.com <gr...@gmail.com> #251
Can you comment on the LG Urbane 2 LTE (at&t)?
It has the rebranding update already, but since you only mentioned the Urbane (gen 1 I presume), not sure where the urbane 2 stands.
It has the rebranding update already, but since you only mentioned the Urbane (gen 1 I presume), not sure where the urbane 2 stands.
bo...@gmail.com <bo...@gmail.com> #252
Re: #250
I'm on T-Mobile and did not get the update for some reason. What can I do?
I'm on T-Mobile and did not get the update for some reason. What can I do?
sy...@google.com <sy...@google.com> #253
For comment #251 , LG Urbane 2 is not eligible for rebranding OTA and it has to wait for Pixel 2 & Pixel 2XL update. We are not very sure what did you receive. Can you please share the bug report to check what do you have in your device?
For comment #252 , T-mobile with LG Sport Watch should get a rebranding OTA. If you didn't get then share the bug report from your wear device to look into the issue.
For
an...@gmail.com <an...@gmail.com> #254
When will the Pixel 2 update fix the issue? This is a known issue since November. This means that 4 monthly updates were already released and none fixed the problem. How many more will we have to receive until this important feature is once again working properly?!
gr...@gmail.com <gr...@gmail.com> #255
LG Urbane 2 LTE bug report is post #238
What sort of ETA is there for a pixel 2 fix. Pretty bad that I had a perfectly functioning watch for my nexus 6P and since I upgraded to the newest Google "flagship phone" my watch lost one of the biggest features.
What sort of ETA is there for a pixel 2 fix. Pretty bad that I had a perfectly functioning watch for my nexus 6P and since I upgraded to the newest Google "flagship phone" my watch lost one of the biggest features.
sy...@google.com <sy...@google.com> #256
For comment #252 , we looked in to your bug report [OWR1.170919.018 4395587 ] in #237 and this device is from AT&T.
Did you buy from third party or from T-Mobile store?
Can you share us more details on how did you learn this device belongs to T-mobile?
Did you buy from third party or from T-Mobile store?
Can you share us more details on how did you learn this device belongs to T-mobile?
bo...@gmail.com <bo...@gmail.com> #257
Re:256
I purchased from Amazon but is in use on T-Mobile service carrier and has been since activation. Many of us out here have LG Watch Sport on T-Mobile purchased via third party.
I purchased from Amazon but is in use on T-Mobile service carrier and has been since activation. Many of us out here have LG Watch Sport on T-Mobile purchased via third party.
sy...@google.com <sy...@google.com> #259
For #257, thanks for the details. There is a possibility that you could have got the unlocked version of AT&T and which can be compatible with any service provider. We are working with AT&T and will provide updates as they are available.
Thanks for #237 and #258 for sharing the bugreports. We are investigating the reports and will provide updates as they are available.
Thanks for #237 and #258 for sharing the bugreports. We are investigating the reports and will provide updates as they are available.
sy...@google.com <sy...@google.com> #260
Thanks for #239 and #258 for sharing the bugreports. We are investigating the reports and will provide updates as they are available.
bo...@gmail.com <bo...@gmail.com> #261
Re:259
Thank you for all the hard work.
Thank you for all the hard work.
jo...@gmail.com <jo...@gmail.com> #262
Just got the OTA update for the LG sport with the rebrand OS, running Pixel 2 XL with OPM2 April patch. This issue is definitely NOT fixed. Still 10-12 seconds delay when answering a call.
STILL ALL VOIP apps like Google Duo FREEZE for 10-12 seconds when you answer a call and the watch is connected as these apps are trying to use the watch as a Bluetooth headset.
Looks like nothing has been done on this topic.
This does NOT happen with the same watch on my Galaxy note note 8.
STILL ALL VOIP apps like Google Duo FREEZE for 10-12 seconds when you answer a call and the watch is connected as these apps are trying to use the watch as a Bluetooth headset.
Looks like nothing has been done on this topic.
This does NOT happen with the same watch on my Galaxy note note 8.
sy...@google.com <sy...@google.com> #263
For #262, can you also share the bug reports as requested and share the link here?
jo...@gmail.com <jo...@gmail.com> #264
@sy: I will try to take a bug report later but this should be easily replicated by you guys. It's not a sporadic bug, it happens every single time.
I have 3 WearOS watches: LG Sports, HW2, and Fossil Explorist. All of them updated to WearOS 1.0.
All them without exception are having this issue with answering incoming calls and making / answering Google Duo (and other VOIP apps) calls.
With the phone app, when you answer a call there is a 10-12 seconds delay. This happens 8/10 times answering regular calls and 10/10 times when using WiFi calling.
With VOIP apps, they just completely freeze for 10-12 seconds as they try to send the audio to the watch when you answer a call, until some timeout happens and the audio is routed to the phone earpiece.
All of the 3 watches, when paired to the Galaxy note 8 running Oreo 8.0 do NOT have this issue. The Note 8 knows to ignore the watch when using Duo or VOIP apps so they don't freeze while trying to send audio to the watch, and knows how to properly answer a call with the phone app so there is no delay.
This is not a watch issue, this is a Pixel 2 code issue. If this was a watch issue it would also happen with the Note 8.
This is also happening when I pair my Samsung Gear S3 with the Pixel 2 and does NOT happen when the same watch is paired with the Note 8. so again, this is not a watch / WearOS issue. This is a Pixel 2 XL issue .
I have 3 WearOS watches: LG Sports, HW2, and Fossil Explorist. All of them updated to WearOS 1.0.
All them without exception are having this issue with answering incoming calls and making / answering Google Duo (and other VOIP apps) calls.
With the phone app, when you answer a call there is a 10-12 seconds delay. This happens 8/10 times answering regular calls and 10/10 times when using WiFi calling.
With VOIP apps, they just completely freeze for 10-12 seconds as they try to send the audio to the watch when you answer a call, until some timeout happens and the audio is routed to the phone earpiece.
All of the 3 watches, when paired to the Galaxy note 8 running Oreo 8.0 do NOT have this issue. The Note 8 knows to ignore the watch when using Duo or VOIP apps so they don't freeze while trying to send audio to the watch, and knows how to properly answer a call with the phone app so there is no delay.
This is not a watch issue, this is a Pixel 2 code issue. If this was a watch issue it would also happen with the Note 8.
This is also happening when I pair my Samsung Gear S3 with the Pixel 2 and does NOT happen when the same watch is paired with the Note 8. so again, this is not a watch / WearOS issue. This is a Pixel 2 XL issue .
ma...@gmail.com <ma...@gmail.com> #265
This ^ comment 263. This is what most of us have been trying to say. I have a ticwatch E and it behaves the same way. works with other android phones but not the pixel 2. This is definatley a pixel2 issue. How can every other manufacturer get to behave but Google's flagship phone, meant to show off what android is really capable of have this big of a bug. and it's been a known one almost from launch. I mean you shouldn't have to reinvent the wheel here, everyone else has it figured out... It's a shame because i really like the phone but one of the reasons i bought it was so it would play nice with the watch. I'm not one to write off an entire line becasue of one bug but you have to admit, it's a pretty bad one. I'll reiterate this again, I switched from 10 years of iphone use to buy this phone because it was what i was finally looking for in android. Not exactly getting brownie points here. Other bugs are somewhat tolerable (i.e. the color shift on the screen and stuff that people were making mountains out of mole hills) but this is pretty significant.
ma...@gmail.com <ma...@gmail.com> #266
honestly, maybe if this started hitting sites like 9to5google and the likes it might light a bigger fire to get it fixed...
gr...@gmail.com <gr...@gmail.com> #267
Spread it, I sent it to Android police a few days ago
tm...@gmail.com <tm...@gmail.com> #268
I'm beginning to wonder if how Google mucked around with Bluetooth to create the pairing with the Pixel Buds may have had an affect on how it interacts with other Bluetooth devices.
Again, bluetooth has been around far too long to be this big of an issue.
Again, bluetooth has been around far too long to be this big of an issue.
x....@gmail.com <x....@gmail.com> #269
I have same problem with pixel 2 xl and zenwatch 3 , my friend has same problem with pixel 2 xl with gear 3 too.
so...@gmail.com <so...@gmail.com> #270
I have the same problem with the pixel 2 and Huawei watch
di...@gmail.com <di...@gmail.com> #271
Same problem here on pixel 2 paired with Huawei watch
fl...@gmail.com <fl...@gmail.com> #272
Update from comment #249 . THE BUG IS BACK... Then it fixed itself...But for how long?
This is how I reproduced the bug. My devices are currently on the following builds.
Wear Device: Huawei Watch 2 & Build Number: OWDD.180215.018
Phone: Pixel 2 XL & Build Number: OPM2.171019.029
This morning for some reason, I couldn't answer incomming calls with my watch. It forwards the calls to my phone automatically. So I decided to restart my watch. After restarting, the 10 second lag happened again on my phone! It even froze the phone app for a second. After re testing it for about 3 to 4 times (answering call on my phone then answering calls on my watch) It later fixed it seft.. Ughhhhhhhhh.
Bug report links:
https://drive.google.com/file/d/1W3Vhq00ANEuIAjK4t7UexChnKzh-Z91l/view?usp=sharing
https://drive.google.com/open?id=1ANGHEUTPUWzluXPttlbifQn3fJooKScY
This is how I reproduced the bug. My devices are currently on the following builds.
Wear Device: Huawei Watch 2 & Build Number: OWDD.180215.018
Phone: Pixel 2 XL & Build Number: OPM2.171019.029
This morning for some reason, I couldn't answer incomming calls with my watch. It forwards the calls to my phone automatically. So I decided to restart my watch. After restarting, the 10 second lag happened again on my phone! It even froze the phone app for a second. After re testing it for about 3 to 4 times (answering call on my phone then answering calls on my watch) It later fixed it seft.. Ughhhhhhhhh.
Bug report links:
gr...@gmail.com <gr...@gmail.com> #273
I gave up today and went and made the necessary changes to my plan at AT&T to setup NumberSync for my urbane 2. Cut the bluetooth middle man out altogether. The fact that this is a Pixel 2 issue, not an android wear issue, and has lasted this long didn't leave me much hope.
fl...@gmail.com <fl...@gmail.com> #274
Sent it to The Verge. Please share this on your Social Media accounts as well.
We need to have more people working on this issue. I feel like Google's focus is now shifting to the Pixel 3.
We need to have more people working on this issue. I feel like Google's focus is now shifting to the Pixel 3.
do...@gmail.com <do...@gmail.com> #275
In response to #273, did this help? I'm set up with them, but wasn't sure
if this would work. I'm on a LTE LG Sportwatch
On Fri, Apr 6, 2018, 2:32 PM <buganizer-system@google.com> wrote:
if this would work. I'm on a LTE LG Sportwatch
On Fri, Apr 6, 2018, 2:32 PM <buganizer-system@google.com> wrote:
gr...@gmail.com <gr...@gmail.com> #276
@ #275
Yep. Phone starts to ring and within 2-3 seconds watch starts to ring. No issues answering either.
Yep. Phone starts to ring and within 2-3 seconds watch starts to ring. No issues answering either.
do...@gmail.com <do...@gmail.com> #277
Do you turn the Bluetooth voice answering off but keep Bluetooth on for
messaging?
On Fri, Apr 6, 2018, 3:48 PM <buganizer-system@google.com> wrote:
messaging?
On Fri, Apr 6, 2018, 3:48 PM <buganizer-system@google.com> wrote:
gr...@gmail.com <gr...@gmail.com> #278
Bluetooth is on and connected, but "play phone audio on watch" is disabled. Can't completely vouch for messaging as I use the paid version of pulse sms so texts are synced on watch/pc/phone.
sy...@google.com <sy...@google.com> #279
Thank you very much for all the details. We are unable to find the root cause from #239 and #258. Our team is working on the issue and will provide updates as they are available.
sm...@gmail.com <sm...@gmail.com> #280
I have the essential ph1 phone that had the identical problem as the pixel 2 trying to take calls on a wear OS watch. Just installed the April 5th patch and tested the ticwatch S and all seems to work well.
bo...@gmail.com <bo...@gmail.com> #281
For comment #253 I still have not received the Rebranding update. Please see bug report in comment #237 for information. I've switched SIM cards to AT&T as well as removed the sim completely from watch for 8hrs at a time. Still no update to test for calling lag.
sy...@google.com <sy...@google.com> #282
Re:#281, FYI the rebranding OTA push is independent of SIM card. This OTA is only depend on the initial carrier of your Wear OS device which is AT&T (For your device). So, you would be getting rebranding OTA when AT&T pushes to public and it doesn't have dependency on your current network carrier. You can use any network carrier AT&T or T-Mobile or etc.
As we discussed in earlier comments, we are working with AT&T and will provide updates as they are available.
As we discussed in earlier comments, we are working with AT&T and will provide updates as they are available.
an...@gmail.com <an...@gmail.com> #283
What about a fix for the older generation smartwatches, like the Huawei Watch?
ro...@gmail.com <ro...@gmail.com> #284
for #283
As was mentioned in this topic for older devices like huawei watch it should be fixed on the pixel phone side. But still remains question when.
As was mentioned in this topic for older devices like huawei watch it should be fixed on the pixel phone side. But still remains question when.
ha...@gmail.com <ha...@gmail.com> #285
Still having issues with Huawei 2 Classic watch with Pixel 2 XL on Project Fi. Phone rings, a few seconds later, watch rings, answer on phone, which needs about ten seconds to connect. All OTA updates done with no improvements.
sy...@google.com <sy...@google.com> #286
Re:#285, can you share the bug reports from Phone and Wear device as requested in #229?
gd...@gmail.com <gd...@gmail.com> #287
Hi
Just decided to try and do some more bug reports myself. The first time I
tried it worked fine but this always happens after reconnecting the call
answer. Second time it had a 10-12 second delay but then 3rd, 4th, 5th and
6th time worked fine! Never happened to me before through several times of
testing and using different settings. I know others have had it happen to
them, this is a first for me. I will continue testing tomorrow and send my
bug report when ready.
On Mon, 9 Apr 2018, 6:36 pm , <buganizer-system@google.com> wrote:
Just decided to try and do some more bug reports myself. The first time I
tried it worked fine but this always happens after reconnecting the call
answer. Second time it had a 10-12 second delay but then 3rd, 4th, 5th and
6th time worked fine! Never happened to me before through several times of
testing and using different settings. I know others have had it happen to
them, this is a first for me. I will continue testing tomorrow and send my
bug report when ready.
On Mon, 9 Apr 2018, 6:36 pm , <buganizer-system@google.com> wrote:
fl...@gmail.com <fl...@gmail.com> #288
I would like to know exactly how many people are working to solve this issue. P0 S1 should have more than one.
as...@gmail.com <as...@gmail.com> #289
Mine seems to be fixed! It took a few months.
One of the reason why such a big bug went unnoticed was even wearos team reportedly not using wearOs! Anyway Google is a giant, has no competition. They don't worry about little things like this. Some at Google don't even see people like us as customers. We are just commodities and the main business of Google is to harvest data out of us and generate revenues out of those data.
It is all about numbers! How many more Android users they have added last year! That's all matters.
I don't think they even aim to generate any profit out of selling crappy products straight to the consumers. They are happy as long as it is not making loss. It would be interesting to see what more craps they come out with in their self-applauding event next month.
My next phone will be a feature phone with 4g
One of the reason why such a big bug went unnoticed was even wearos team reportedly not using wearOs! Anyway Google is a giant, has no competition. They don't worry about little things like this. Some at Google don't even see people like us as customers. We are just commodities and the main business of Google is to harvest data out of us and generate revenues out of those data.
It is all about numbers! How many more Android users they have added last year! That's all matters.
I don't think they even aim to generate any profit out of selling crappy products straight to the consumers. They are happy as long as it is not making loss. It would be interesting to see what more craps they come out with in their self-applauding event next month.
My next phone will be a feature phone with 4g
gd...@gmail.com <gd...@gmail.com> #290
Hi
Here is the bug report for yesterday and this morning.
https://drive.google.com/folderview?id=16SfUHiiiY44_xGagoM3kQ5MxjqQHEwfZ
As I mentioned yesterday it started to work as normal. This morning it had
mixed results. Tests at 9.13am and 9.20am connected fine. The others didn't
(this is only testing answering on the phone every other scenario seems to
be connecting as expected). I did think it makes a difference if the screen
is active when receiving the call or a sleep. However, these tests don't
clearly show that is always the case.
Hope this helps.
I will try it for a few days and see how it is in the real world. Not
getting my hopes up.
On 10 Apr 2018 6:37 am, <buganizer-system@google.com> wrote:
Replying to this email means your email address will be shared with the
team that works on this product.
https://issuetracker.google.com/issues/71010564
*Changed*
*as...@gmail.com <as...@gmail.com> added comment #289
<https://issuetracker.google.com/issues/71010564#comment289 >:*
Mine seems to be fixed! It took a few months.
One of the reason why such a big bug went unnoticed was even wearos team
reportedly not using wearOs! Anyway Google is a giant, has no competition.
They don't worry about little things like this. Some at Google don't even
see people like us as customers. We are just commodities and the main
business of Google is to harvest data out of us and generate revenues out
of those data.
It is all about numbers! How many more Android users they have added last
year! That's all matters.
I don't think they even aim to generate any profit out of selling crappy
products straight to the consumers. They are happy as long as it is not
making loss. It would be interesting to see what more craps they come out
with in their self-applauding event next month.
My next phone will be a feature phone with 4g
_______________________________
*Reference Info: 71010564 Enabling "Play phone voice call on watch" causes
phone apps to lag for 10+ seconds and results in no audio/mic*
component: Android Public Tracker > Wear
status: Assigned
reporter: pi...@gmail.com
assignee: sy...@google.com
cc: pi...@gmail.com, sy...@google.com
type: Bug P0 S1
blocked by: 71384973 <https://issuetracker.google.com/issues/71384973 >
duplicate issue: 74163619 <https://issuetracker.google.com/issues/74163619 >
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google
IssueTracker issue 71010564
<https://issuetracker.google.com/issues/71010564 > where you have the role:
starred.
Here is the bug report for yesterday and this morning.
As I mentioned yesterday it started to work as normal. This morning it had
mixed results. Tests at 9.13am and 9.20am connected fine. The others didn't
(this is only testing answering on the phone every other scenario seems to
be connecting as expected). I did think it makes a difference if the screen
is active when receiving the call or a sleep. However, these tests don't
clearly show that is always the case.
Hope this helps.
I will try it for a few days and see how it is in the real world. Not
getting my hopes up.
On 10 Apr 2018 6:37 am, <buganizer-system@google.com> wrote:
Replying to this email means your email address will be shared with the
team that works on this product.
*Changed*
*as...@gmail.com <as...@gmail.com> added
<
Mine seems to be fixed! It took a few months.
One of the reason why such a big bug went unnoticed was even wearos team
reportedly not using wearOs! Anyway Google is a giant, has no competition.
They don't worry about little things like this. Some at Google don't even
see people like us as customers. We are just commodities and the main
business of Google is to harvest data out of us and generate revenues out
of those data.
It is all about numbers! How many more Android users they have added last
year! That's all matters.
I don't think they even aim to generate any profit out of selling crappy
products straight to the consumers. They are happy as long as it is not
making loss. It would be interesting to see what more craps they come out
with in their self-applauding event next month.
My next phone will be a feature phone with 4g
_______________________________
*Reference Info: 71010564 Enabling "Play phone voice call on watch" causes
phone apps to lag for 10+ seconds and results in no audio/mic*
component: Android Public Tracker > Wear
status: Assigned
reporter: pi...@gmail.com
assignee: sy...@google.com
cc: pi...@gmail.com, sy...@google.com
type: Bug P0 S1
blocked by: 71384973 <
duplicate issue: 74163619 <
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google
IssueTracker
<
starred.
sy...@google.com <sy...@google.com> #291
Thanks for the updates. We tried several times with different devices and unable to reproduce the issue. We are investigating the issue from the user bug reports.
fl...@gmail.com <fl...@gmail.com> #292
I have the same setup as the original poster which is Pixel 2 XL and Huawei Watch 2. Still have the same issue. As I mentioned in previous post, I thought that the issue was gone until I decided to make a call using my watch. It was forwarding the call to the phone. I restarted and the issue occured again then went away, then came back.
Please restart both the watch and the phone and do the following. I guarantee that you will reproduce the issue.
Call yourself and pick up using the watch.
Call yourself and pick up using the phone.
Make a call with the phone.
Make a call with the watch.
Try all for about 3-4 times.
Bug report links:
https://drive.google.com/file/d/1W3Vhq00ANEuIAjK4t7UexChnKzh-Z91l/view?usp=sharing
https://drive.google.com/open?id=1ANGHEUTPUWzluXPttlbifQn3fJooKScY
Please restart both the watch and the phone and do the following. I guarantee that you will reproduce the issue.
Call yourself and pick up using the watch.
Call yourself and pick up using the phone.
Make a call with the phone.
Make a call with the watch.
Try all for about 3-4 times.
Bug report links:
fl...@gmail.com <fl...@gmail.com> #293
WHY DID THIS GO BACK TO P1 S1 STATUS? NO ONE HERE CAN VOUCH THAT THE FIX ACTUALLY WORKED ON THEIR DEVICE?
an...@gmail.com <an...@gmail.com> #294
I've lost faith in this bug tracker
tm...@gmail.com <tm...@gmail.com> #295
I have to wonder if the changes Google made to BT with the Pixel 2 that allows it to pair with the Pixel Buds is the root of the issue?
Regardless, this issue is far from resolved and has made our Wear devices useless for one of their main functions.
Regardless, this issue is far from resolved and has made our Wear devices useless for one of their main functions.
ma...@gmail.com <ma...@gmail.com> #296
@293. Exactly. What's going to happen is we will be forced to wait for the pixel 3 and maybe just maybe it'll be fixed... After an entire year. October Google, October.... That's how long this has been going on. I have a ticwatch e, which still hasn't bee. Rebranded and who knows when that will ever happen. And sinsce this watch works with other phones I'd say (like the rest of us) the band-aid on the wearos side is just that, a bandaid. This is a pixel 2 issue for sure. I mean. Good grief pick any other Android phone and reverse engeer the Bluetooth stack for crying out loud. It's not like Bluetooth is some groundbreaking piece of tech at this point.
fl...@gmail.com <fl...@gmail.com> #297
REFUND TIME: UPDATE #1
I just started the process of returning the phone. I really wanted this to work but I can't deal with this any longer. I suggest you do the same.
I was able to show the customer support rep the 10 second lag while screen share was on. This was after going through a number or workaround which didn't help at all. Turning off NFC? Come on! The next thing that they want me to try is putting the phone in safe mode and see if the problem still happens. I'll try that as soon as I get home from work. I'll keep everyone posted.
I just started the process of returning the phone. I really wanted this to work but I can't deal with this any longer. I suggest you do the same.
I was able to show the customer support rep the 10 second lag while screen share was on. This was after going through a number or workaround which didn't help at all. Turning off NFC? Come on! The next thing that they want me to try is putting the phone in safe mode and see if the problem still happens. I'll try that as soon as I get home from work. I'll keep everyone posted.
th...@gmail.com <th...@gmail.com> #298
Mine is now working as it is supposed to! After the latest updates it worked, then stopped, but now it's working again. So I'm not saying it's fixed for good, and every time I answer my phone, I'm worried I'll get the 10 second delay of doom. But so far so good.
do...@gmail.com <do...@gmail.com> #299
For 298, do you have an ATT watch or phone?
On Tue, Apr 10, 2018, 9:21 PM <buganizer-system@google.com> wrote:
On Tue, Apr 10, 2018, 9:21 PM <buganizer-system@google.com> wrote:
th...@gmail.com <th...@gmail.com> #300
For #299
I have Pixel 2 XL (on Bell in Canada) and Huawei Watch 2 running Wear OS.
I have Pixel 2 XL (on Bell in Canada) and Huawei Watch 2 running Wear OS.
jk...@landmarkschool.org <jk...@landmarkschool.org> #301
Restarted both devices, had a 12-13 second delay.
Pixel 2 XL Build Number OPM2.171019.029
Wear24 Build number N7G75P
Shared with android-bugreport@google.com
https://drive.google.com/open?id=1rS79lpLem1r0Y_Bs76F6r7XwQ8CKGpGZ
Pixel 2 XL Build Number OPM2.171019.029
Wear24 Build number N7G75P
Shared with android-bugreport@google.com
sh...@gmail.com <sh...@gmail.com> #302
All is working fine now since last update. Huawei 2 Classic, and Pixel 2 XL.
fl...@gmail.com <fl...@gmail.com> #303
In response to comment #219 .
Can you go over the steps that you did to get a full refund?
For comment #300
Can you restart both the phone and the watch and do the following?
Call yourself and pick up using the watch.
Call yourself and pick up using the phone.
Make a call with the phone.
Make a call with the watch.
Try all for about 3-4 times. Let me.know if you're still not getting the 10 delay.
Can you go over the steps that you did to get a full refund?
For
Can you restart both the phone and the watch and do the following?
Call yourself and pick up using the watch.
Call yourself and pick up using the phone.
Make a call with the phone.
Make a call with the watch.
Try all for about 3-4 times. Let me.know if you're still not getting the 10 delay.
fl...@gmail.com <fl...@gmail.com> #304
Same for comment #302 . Please do what I mentioned above and let me know if you're still not getting the 10 second delay.
sh...@gmail.com <sh...@gmail.com> #305
Was working fine, now it's back to the 10 second delay.
fu...@gmail.com <fu...@gmail.com> #306
Was caught out by the same issue. Even when wearing pixel buds the call weren't getting routed to them and no sound on watch.
fl...@gmail.com <fl...@gmail.com> #307
For the Google employee on comment #291
If you're not able to duplicate the issue, then you may not be testing thouroughly. Were you able to try the steps that I mentioned in comment #292 ? Have you checked the bug report that I provided?
I, along with everyone that contributed to this issue tracker are telling you that the "fix" did not actually fix the issue. A core function is not working properly. Hence, the severity SHOULD BE P0, and should stay that way.
If you're not able to duplicate the issue, then you may not be testing thouroughly. Were you able to try the steps that I mentioned in
I, along with everyone that contributed to this issue tracker are telling you that the "fix" did not actually fix the issue. A core function is not working properly. Hence, the severity SHOULD BE P0, and should stay that way.
ra...@gmail.com <ra...@gmail.com> #308
For comment#303 :
I bought my phone directly through the Google Store. I contacted Google by going tostore.google.com and clicking my account icon in the upper right corner, then choosing the circle blue "help" icon with the question mark. Under the "Contact Us" section I chose Phone. I entered my information and phone number and they called me within about one minute. It took several of these calls, and an escalation to a supervisor before they approved the refund. I specifically referenced this bug and this issue tracker number 71010564 as the reason for my return. All told, it took about two weeks of calls and emails, but at least it is resolved. I received my refund and I'm using a Galaxy S9+ with a Gear S3 Classic with no issues. I take calls on my watch when I need to and I take calls on my phone when I need to with no issues. No ten second delay. It just works flawlessly as intended and without hassle.
Obviously, from all of the comments here, this issue still remains, which to me is unfathomable. To the Google employee assigned to this issue: please understand that the issue can't be resolved entirely with a patch to a Wear OS build. I can't stress this enough -- it is not an issue with the watch os alone -- it is an issue with the PHONE. I experienced this issue with a Tizen Gear S3 watch paired with a Pixel 2 XL and a Wear OS watch paired with a Pixel 2 XL. This is an issue with the phone's bluetooth stack. Please address the issue in the Pixel bluetooth audio framework.
You can't release a patch to Wear OS and call this fixed - it can't be done. And you certainly can't downgrade the priority and severity to P1 S1. But look, that's exactly what has happened.
I don't know how many more comments are needed to get Google's attention here. It's a shame. I sincerely hope this gets fixed for all who still have the Pixel 2 phone.
I bought my phone directly through the Google Store. I contacted Google by going to
Obviously, from all of the comments here, this issue still remains, which to me is unfathomable. To the Google employee assigned to this issue: please understand that the issue can't be resolved entirely with a patch to a Wear OS build. I can't stress this enough -- it is not an issue with the watch os alone -- it is an issue with the PHONE. I experienced this issue with a Tizen Gear S3 watch paired with a Pixel 2 XL and a Wear OS watch paired with a Pixel 2 XL. This is an issue with the phone's bluetooth stack. Please address the issue in the Pixel bluetooth audio framework.
You can't release a patch to Wear OS and call this fixed - it can't be done. And you certainly can't downgrade the priority and severity to P1 S1. But look, that's exactly what has happened.
I don't know how many more comments are needed to get Google's attention here. It's a shame. I sincerely hope this gets fixed for all who still have the Pixel 2 phone.
tm...@gmail.com <tm...@gmail.com> #309
It may be about time for me to do the same and return my Pixel 2 XL. As nice the phone is, my Michael Kors Grayson is way to nice to be lacking such a critical function.
ha...@gmail.com <ha...@gmail.com> #310
I called myself from landline to Pixel 2XL and Huawei 2 Classic. About 50% of the time it worked perfectly. The other 50%, I couldn't hear myself on the landline for 10 to 13 seconds.
Here's my bug link.https://drive.google.com/file/d/1h6teqnnfJoVjE06G6r3XzMbyR0uV0Pn_/view?usp=drivesdk
Here's my bug link.
sy...@google.com <sy...@google.com> #311
Thanks for the updates. We are actively working with Pixel 2 & 2XL team for the fix on the issue issue. We followed the directions shared in #303 and no luck. We will keep trying until we figured the proper steps to reproduce the issue.
Re#310, can you share the bug reports from phone and wear device after reproducing the issue?
Re#310, can you share the bug reports from phone and wear device after reproducing the issue?
as...@gmail.com <as...@gmail.com> #312
Mine is fixed. After the updates I factory reset the phone and the paired the watch. Try that is you have liberty to do so.
jo...@gmail.com <jo...@gmail.com> #313
@sy...@google.com:
You can EASILY replicate this issue as I described in my previous comment:
1) Make sure the watch is connected with call audio enabled
2) Open Google Duo, and make a voice call to someone
3) Make sure that other person answers the call.
4) Watch Google DUO freeze for 10+sec while it tries to send the audio to the wacth
This happens 100% of the time with ANY watch connected to the Pixel 2 XL and is directly related to the audio "delay" issue people have been complaining about here when using the phone app.
There is no way you guys at Google can not replicate this bug as this happens 100% of the time with ANY watch connected to the phone when phone audio is enabled on the watch.
This does not happen when those same watches connected to a Samsung Galaxy phone.
Really, saying you guys are not able to reproduce the issue when some many people here complain does not sound credible at all.
You can EASILY replicate this issue as I described in my previous comment:
1) Make sure the watch is connected with call audio enabled
2) Open Google Duo, and make a voice call to someone
3) Make sure that other person answers the call.
4) Watch Google DUO freeze for 10+sec while it tries to send the audio to the wacth
This happens 100% of the time with ANY watch connected to the Pixel 2 XL and is directly related to the audio "delay" issue people have been complaining about here when using the phone app.
There is no way you guys at Google can not replicate this bug as this happens 100% of the time with ANY watch connected to the phone when phone audio is enabled on the watch.
This does not happen when those same watches connected to a Samsung Galaxy phone.
Really, saying you guys are not able to reproduce the issue when some many people here complain does not sound credible at all.
ry...@gmail.com <ry...@gmail.com> #314
It works for me after reboot then it repros again after a few times. When I get a chance I'll try to come up with better repro steps and take some bug reports.
pj...@gmail.com <pj...@gmail.com> #315
For me this works fine when watch shows as connected over bluetooth (Pixel 2, Fossil Q Explorist). However, when I put my watch on my wrist in the morning, it's not showing as connected in phone's bluetooth settings - and if I receive a call on the watch, it tells me I should take it on the phone.
For others does the watch automatically connect over bluetooth, i.e. is it showing as connected in bluetooth settings? I'm trying to figure out if my current issue is related to the 10sec delay issue or not.
For others does the watch automatically connect over bluetooth, i.e. is it showing as connected in bluetooth settings? I'm trying to figure out if my current issue is related to the 10sec delay issue or not.
ta...@gmail.com <ta...@gmail.com> #317
Same issue, hw2 classic + pixel 2
fl...@gmail.com <fl...@gmail.com> #318
Re comment #289 and comment #312 ( which i beleive is the same person?)
Just to clarify, you are not experiencing any type of lag? Can you please try the steps that I mentioned in comment #303 and get back to us? I would also like to see this "fix" in action if possible. Perhaps record a quick video and share it here if you can.
And to anyone else who thinks that their device is fixed. We would like to see it in action if possible. Many thanks.
Just to clarify, you are not experiencing any type of lag? Can you please try the steps that I mentioned in
And to anyone else who thinks that their device is fixed. We would like to see it in action if possible. Many thanks.
sy...@google.com <sy...@google.com> #319
Thanks for the updates.
We followed directions provided in comment #313 , below are our observations.
1. We can reproduce the issue with Pixel 2 [OPM2 build] + LG Sport (rebranding OTA) + Google Duo.
2. We can't reproduce the same issue in our Pixel 2 Preview buid [PPP1.180208.014] + LG Sport (rebranding OTA) + Google Duo. It looks like this issue is fixed in Preview builds.
3. We can't reproduce any of the issues using LG Urbane (no rebranding OTA) with Pixel 2 Preview buid [PPP1.180208.014] using Google Duo and phone app.
4. We can't reproduce the issue with phone app + Pixel 2 preview or Pixel 2 + LG Sport (rebranding OTA)
Can any one update the results with Pixel 2 Preview firmware + any wear device + Phone or Google Duo?
Pixel Preview release notes:https://developer.android.com/preview/release-notes.html
Note: while commenting back, please mention your phone (Pixel 2 or 2XL) + build [Preview or OTA] + Wear device [LG Sport or LG Urbane or Huawei or etc] + application [phone or Google Duo or etc]
We followed directions provided in
1. We can reproduce the issue with Pixel 2 [OPM2 build] + LG Sport (rebranding OTA) + Google Duo.
2. We can't reproduce the same issue in our Pixel 2 Preview buid [PPP1.180208.014] + LG Sport (rebranding OTA) + Google Duo. It looks like this issue is fixed in Preview builds.
3. We can't reproduce any of the issues using LG Urbane (no rebranding OTA) with Pixel 2 Preview buid [PPP1.180208.014] using Google Duo and phone app.
4. We can't reproduce the issue with phone app + Pixel 2 preview or Pixel 2 + LG Sport (rebranding OTA)
Can any one update the results with Pixel 2 Preview firmware + any wear device + Phone or Google Duo?
Pixel Preview release notes:
Note: while commenting back, please mention your phone (Pixel 2 or 2XL) + build [Preview or OTA] + Wear device [LG Sport or LG Urbane or Huawei or etc] + application [phone or Google Duo or etc]
jo...@gmail.com <jo...@gmail.com> #320
@ sy@google.com
The issue does not happen with Google Duo on the P preview because there seems to be a bug with either Duo or the preview where Google Duo will not work with Bluetooth - at all. It's simply not able to send audio over Bluetooth at all.
If you connect a regular Bluetooth headset to the phone and make a Duo call on P, Duo will not send the audio the headset at all (like it is suppose to). This is why you are not able to replicated the issue in the P preview.
I tested this myself when the preview came out and can confirm the above, Duo in P does not see ANY Bluetooth device, not just the watch, hence this is not happening in P.
When I used other VOIP apps in P, they had the same freezing issue as the latest O build when the watch was connected - so this issue is certainly not fixed in P either.
I hope the above explanation clear things up why you are not able to reproduce this in P.
Please have the engineers look at what Samsung is doing on their phones as again, this is not happening with the same watches on the Note 8 or the S9+ with the same watches.
The issue does not happen with Google Duo on the P preview because there seems to be a bug with either Duo or the preview where Google Duo will not work with Bluetooth - at all. It's simply not able to send audio over Bluetooth at all.
If you connect a regular Bluetooth headset to the phone and make a Duo call on P, Duo will not send the audio the headset at all (like it is suppose to). This is why you are not able to replicated the issue in the P preview.
I tested this myself when the preview came out and can confirm the above, Duo in P does not see ANY Bluetooth device, not just the watch, hence this is not happening in P.
When I used other VOIP apps in P, they had the same freezing issue as the latest O build when the watch was connected - so this issue is certainly not fixed in P either.
I hope the above explanation clear things up why you are not able to reproduce this in P.
Please have the engineers look at what Samsung is doing on their phones as again, this is not happening with the same watches on the Note 8 or the S9+ with the same watches.
sy...@google.com <sy...@google.com> #321
Re:#320, Thanks for the details. We will investigate further.
bo...@gmail.com <bo...@gmail.com> #322
Re: comment #282
All LG Watch Sport LG W280A (the version I own) are AT&T branded watches and sold unlocked. What model number LG Watch Sport are you testing with that is running the Rebranded Wear OS firmware? LG W280 is the International version and doesn't support our US frequencies and they never sold the LG Watch Sport LG W280V. I'd really like to know since you are telling me the reason my LG Watch Sport hasn't updated is due to AT&T not having pushed the update yet due to difficulties. If I should have the Rebranding update already, I'd like to know why I don't? I mean, I have the same issue as everyone else with calls not working properly. I also now have the problem of no Rebranding update. If you are testing on an LG W280A with Rebranding then I've got an issue that is compounding the call issue.
All LG Watch Sport LG W280A (the version I own) are AT&T branded watches and sold unlocked. What model number LG Watch Sport are you testing with that is running the Rebranded Wear OS firmware? LG W280 is the International version and doesn't support our US frequencies and they never sold the LG Watch Sport LG W280V. I'd really like to know since you are telling me the reason my LG Watch Sport hasn't updated is due to AT&T not having pushed the update yet due to difficulties. If I should have the Rebranding update already, I'd like to know why I don't? I mean, I have the same issue as everyone else with calls not working properly. I also now have the problem of no Rebranding update. If you are testing on an LG W280A with Rebranding then I've got an issue that is compounding the call issue.
fl...@gmail.com <fl...@gmail.com> #323
Since the same behavior is happening with the Gear S3 line, the engineers should probably focus more on the phone rather than Wear OS.
Well, I now qualify for a refund. If you're thinking of returning your Pixel, make sure to sight this issue tracker and don't settle for a replacement.
Well, I now qualify for a refund. If you're thinking of returning your Pixel, make sure to sight this issue tracker and don't settle for a replacement.
do...@gmail.com <do...@gmail.com> #324
fl...@gmail.com <fl...@gmail.com> #325
Leaning towards S9 plus or Huawei P20 pro.
rm...@gmail.com <rm...@gmail.com> #326
What's the process you have to go through in order to get a refund? I'm a few months in, is it too late?
fl...@gmail.com <fl...@gmail.com> #327
Re: comment #326
Purchased mine back in Oct. Purchased mine through the Google Store. Reached out to customer rep via chat. They'll have you go through a bunch of troubleshooting stuff. Demand to speak with their supervisor and always sight this issue tracker. They will offer to replace your device. Always refuse and demand a refund instead.
Purchased mine back in Oct. Purchased mine through the Google Store. Reached out to customer rep via chat. They'll have you go through a bunch of troubleshooting stuff. Demand to speak with their supervisor and always sight this issue tracker. They will offer to replace your device. Always refuse and demand a refund instead.
mi...@gmail.com <mi...@gmail.com> #328
Same issue pixel 2 XL and Huawei 2 watch
ia...@gmail.com <ia...@gmail.com> #329
Just contacted EE in the UK to see what my options are to change the device - they will not do it as the device Pixel 2XL works on their network. I don't really want to change my device this issue should have been fully resolved by Google by now.
sc...@gmail.com <sc...@gmail.com> #330
I mean, sure it's annoying bug. But all these people willing to trade their phone in for a refund is a bit extreme. I'd rather have stock Android. Please Google fix the issue already. Stop keeping us in the dark. Severity should be p0 with more working on it. Clearly sy does not know what their doing....
sc...@gmail.com <sc...@gmail.com> #331
They're*
fl...@gmail.com <fl...@gmail.com> #332
Of course stock Android is great. What's not great is how they are ruining the experience with the way they are handling this bug. It's their own hardware for geebus sake. Google needs to have more people looking into this. Switch it back to P0 until we actually get a real fix.
ma...@gmail.com <ma...@gmail.com> #333
Yes. Stock Android IS great. But I have to say. I've followed a lot of bogs over the years and over 300 comments on one single big says volumes. And the fact that it's still not fixed....well, that says volumes as well. I think this may be the longest I've seen a bug remain on non beta software remain. I mean this has been an issue since launch. Maybe if it was the actual Linux community working on it it would be fixed. But this is Google we are talking about...
gr...@gmail.com <gr...@gmail.com> #334
Worth noting that the issue, at least for me, only started around mid February. Before this, everything worked correctly.
I have the exact problem as described by others above.
Using;
Pixel 2 XL 8.1.0
Huawei watch 1 version 2.1.0.188xxxx
The only reason I upgraded my Nexus 6P was the constant Bluetooth issues, never had any issues with LG G4,5 and S6.
I have the exact problem as described by others above.
Using;
Pixel 2 XL 8.1.0
Huawei watch 1 version 2.1.0.188xxxx
The only reason I upgraded my Nexus 6P was the constant Bluetooth issues, never had any issues with LG G4,5 and S6.
gr...@gmail.com <gr...@gmail.com> #335
My wife and I both have pixel 2s, I have an LG urbane 2 LTE and her a gen 3 fossil. This has been an issue for us since we got the pixels in December
as...@gmail.com <as...@gmail.com> #336
Mine has come back! It was fixed but now I have noticed that sometimes it does not work. I have to restart my phone or turn off bluetooth of my phone on and off to get it working again.
pi...@gmail.com <pi...@gmail.com> #337
Hi dear Google, OP here (the initial bug reporter)
I'm unhappy to report that the bug seemed fixed on my side at first, I've tested with Phone app and it seemed to work perfectly fine. Then someone called me on Duo and boom, 10s lag again. Today someone called me on the phone and again 10s lag in Phone app (the caller disconnected before the phone unfroze). This isn't fixed at all, Google.
Attaching bug reports from watch and phone done right after the lag happened today:
https://drive.google.com/drive/folders/1UaR-7_bH8JA1EkmsyBzIvM8Xwsbxl_px?usp=sharing
(access given to android-bugreport@google.com)
I'm unhappy to report that the bug seemed fixed on my side at first, I've tested with Phone app and it seemed to work perfectly fine. Then someone called me on Duo and boom, 10s lag again. Today someone called me on the phone and again 10s lag in Phone app (the caller disconnected before the phone unfroze). This isn't fixed at all, Google.
Attaching bug reports from watch and phone done right after the lag happened today:
(access given to android-bugreport@google.com)
dp...@gmail.com <dp...@gmail.com> #338
Same issue with Pixel 2xl (actually my sending one as the first was swapped because of the proximity sensor issue) and Huwaei watch 1. Both running latest releases.
sh...@gmail.com <sh...@gmail.com> #339
Don't understand why this is taking so long to fix. We are talking Google here, not some fly by the seat of your pants company. If I am not mistaken here you wrote the software. It seems to be working fine on other phone's other than the Pixel line. What is the problem taking so long to get it fixed. As many have said this is a core feature of this phone and we can't use it. Huawei 2 Classic and Pixel 2 XL. Thank you.
re...@gmail.com <re...@gmail.com> #340
I'm having the same issue on a Sony Xperia XZ1 Compact in combination with a Ticwatch E. When answering or initiating a call on the phone, there is no sound, even though call sound on the phone has been selected. Only by disabling bluetooth is it possible to actually make a call.
Here is the link to the bug reports (both phone and watch)
https://drive.google.com/drive/folders/18o2aZq7bCRln__Z6j9kbK6SZV5PdsmqV?usp=sharing
Here is the link to the bug reports (both phone and watch)
so...@gmail.com <so...@gmail.com> #341
Have been following this issue for a while, as I've been suffering with it ever since I upgraded from the Nexus 5X to the Pixel 2, with a Huawei Watch 2 4G. With the Nexus 5X it worked flawlessly, but since upgrading to the Pixel 2 in December '17 I get approx 10-20 seconds of silence before call audio is heard by either party. This is so bad to the point I've since disabled "play call audio on watch" and disabled may form of call forwarding.
I shall reenable both to simulate desired normal use and try and capture a few bug reports this evening. Haven't tried with Duo but may attempt with that as well.
I shall reenable both to simulate desired normal use and try and capture a few bug reports this evening. Haven't tried with Duo but may attempt with that as well.
rm...@gmail.com <rm...@gmail.com> #342
I had to call the Fire Department due to a small fire on the side of the highway yesterday and there was no sound coming through on my phone. Called twice before realizing what was happening and then disconnected Bluetooth, and called them back a third time. I could hear the annoyance in their voice.
fl...@gmail.com <fl...@gmail.com> #343
sy...@google.com <sy...@google.com> #344
Thanks for the updates. We regret for the inconvenience caused. We informed comment #342 scenario to our team and increased priority in internal bug too and will provide updates as they are available.
do...@gmail.com <do...@gmail.com> #345
Had a very similar incident in the hospital recently when I just hooked up my watch to Bluetooth. We were trying to communicate about a critically ill patient and I couldn't understand why I wasn't hearing anything from my phone. Then I turned off Bluetooth and my phone audio started working again. Made it so I can't use the watch anymore with Pixel 2XL. Calling for a refund if this can my be fixed in the next few days. I can't put patients at risk for a phone that has features that are not reliable.
ni...@gmail.com <ni...@gmail.com> #346
Not to beat a dead horse, but the bug is a safety issue as well. Even though the phone has the capability to connect to 2 bluetooth devices simultaneously, if you have the phone on, you can't use your car's bluetooth. Trying to dial from the watch while driving is EXTREMELY distracting. Someone can get killed with the 4 steps it takes to dial via watch.
th...@gmail.com <th...@gmail.com> #347
If this a safety issue to you, then please turn off the voice answering feature on your watch's Bluetooth settings until it is fixed. It's one feature that is broken, and it will be fixed at some point with a patch, or eventually when we buy new hardware unfortunately
ma...@gmail.com <ma...@gmail.com> #348
I seriously doubt that if people KNOW this is a safety issue that they are purposely leaving that function on. I'm just speculating but I'm guessing they didn't realize the severity or notice the big at all until these incidents happened. And for what it's worth, I've just been waiting for one of those comments to show up. It was just a matter of time. Wait till someone calls 911 and can't get ahd of an operator because they can't hear the person on the other end.... At some point it will cease to be a bug and become a liability.
do...@gmail.com <do...@gmail.com> #349
Agree with #348. I didn't know that Bluetooth connectivity with my watch was the issue until I received a call from the critical care unit and they hung up on me 3 times because they couldn't get in touch with me. I thought it was a problem with the phone initially, but realized this was a problem with BT connectivity and have had it disabled since. Then I joined this Bug reporting in hopes that it would be solved sooner than later.
an...@gmail.com <an...@gmail.com> #350
It's later since the bug report goes back do December and I Google gives us promises that it's being fixed but it's not.
th...@gmail.com <th...@gmail.com> #351
The last updates have fixed it for me, HW2 Pixel 2 XL
sh...@gmail.com <sh...@gmail.com> #352
I thought so too. Just wait.
rm...@gmail.com <rm...@gmail.com> #353
Yup #352, was fixed for me for a while too. It's back.
jo...@gmail.com <jo...@gmail.com> #354
same issue here with Pixel 2 XL and Huawei Watch 1st gen
sh...@gmail.com <sh...@gmail.com> #355
After resetting both watch, Huawei 2 classic, and phone, Pixel 2 XL, all have latest updates it works on 1st and sometimes 2nd call then rears it's ugly head again. If I disable voice call on watch and then turn back on it will work for 1 or 2 calls then quits working again. PLEASE FIX.
sh...@gmail.com <sh...@gmail.com> #356
I have a similar problem. I can hear the caller, but they can not hear me. And this is not a microphone problem because the google search and other voice commands work. It is just the phone calls so it is a problem with the application.
di...@gmail.com <di...@gmail.com> #357
Same issue for me. Had the q exlporist and pixel 2 xl on the latest security patch and would experience a delay when answering calls on my phone while connected to the explorist watch. Had to return the watch before the return period. I'd purchase the watch again if the issue was fixed.
sh...@gmail.com <sh...@gmail.com> #358
Just received a OS Ware update on my Huawei 2 Classic. Wonder if this will solve the issue.
fl...@gmail.com <fl...@gmail.com> #359
Updating mine as well. Not too promising because the issue is really on the phone side but hopeful nonetheless.
sh...@gmail.com <sh...@gmail.com> #360
OS Ware update did not fix.
em...@gmail.com <em...@gmail.com> #361
I have same problem. Delay when I answer the phone for 15 secs cause the watch is connected. Is there a fix? I thought it was the watch and returned it and bought another but now I know it's not the watch.
Pixel 2 XL
Ticwatch 2e
Pixel 2 XL
Ticwatch 2e
sc...@gmail.com <sc...@gmail.com> #362
Can we get more than one person involved with this?
sc...@gmail.com <sc...@gmail.com> #363
Whelp, gave it a try again Wear OS Home app build 2.10.0.188487362 on Huawei watch 2 and 2.10.0.188560259.gms on the pixel 2 xl and the Phone app version 18.0.187698947. After thorough testing it was working consistently (temporarily) when answering a call directly on the phone with the watch connected. I tried from my dads phone to my Pixel 2 XL, and our house phone to the Pixel 2 XL. It seemed to work about 15 times in a row. Then I waited a few minutes and the issue did come back with the 15 second delay. Again, I cannot stress that seeing this can be an emergency situation people might not know they can turn off the feature and this could cost lives in a bad scenario. It is obviously a Pixel 2 and XL issue as other watches have the same delay (I've read in this thread even samsung watches which don't run Wear OS) I got my watch in December but this issue has probably been happening since day 1 of the Pixel 2 launch (is anyone with a Pixel 1 or nexus having this issue???) I am not willing to go the nuclear option of giving up my phone or watch, but the lack of empathy or a proper apology is trash. You need more people involved at Google on this issue than one guy and we cannot keep waiting patiently for "the fix"
sh...@gmail.com <sh...@gmail.com> #364
With you on this.
sc...@gmail.com <sc...@gmail.com> #365
watch 2 classic*** (also issue tracker should let you edit previous posts.)
ph...@gmail.com <ph...@gmail.com> #366
I read a lot of the comments and don't really understand why there is no fix after half a year. is there anything we can do to help finding a solution? would it help if you get more error reports?
I have the same problem with my pixel 2 xl and a mobvoi ticwatch e. At first I thought my phone was broken, because I forgot that I activated the call feature on my watch. This is really annoying since this is one of the main features of a smart watch.
I think you should at least tell us why you need over 6 month to solve a basic problem like that or if it is even possible to fix it. It is dissapointing to see so many customers ignored for such a long time...
I have the same problem with my pixel 2 xl and a mobvoi ticwatch e. At first I thought my phone was broken, because I forgot that I activated the call feature on my watch. This is really annoying since this is one of the main features of a smart watch.
I think you should at least tell us why you need over 6 month to solve a basic problem like that or if it is even possible to fix it. It is dissapointing to see so many customers ignored for such a long time...
tm...@gmail.com <tm...@gmail.com> #367
I've said it once, and will state it again:
How can a company like Google not understand the baisc of Bluetooth technology?
I guarantee you the issues stem from whatever protocol Google is using to allow it's seamless connect function to the Pixel Buds. By mucking around with the BT stack, it's caused other issues.
When I had my Nexus 6P, I never had this issue occur when paired to Wear devices.
Something so simple is really undermining Google's hardware efforts. Google phones are notorious for BT issues and it's continuing to occur.
How can a company like Google not understand the baisc of Bluetooth technology?
I guarantee you the issues stem from whatever protocol Google is using to allow it's seamless connect function to the Pixel Buds. By mucking around with the BT stack, it's caused other issues.
When I had my Nexus 6P, I never had this issue occur when paired to Wear devices.
Something so simple is really undermining Google's hardware efforts. Google phones are notorious for BT issues and it's continuing to occur.
an...@gmail.com <an...@gmail.com> #368
Google does not want to fix it. They're fooling us around
sh...@gmail.com <sh...@gmail.com> #369
What I don't understand is why someone from Google can't hop on here and respond to us letting us know what is going on on a timely basis. Not asking for much, just a quick response.
ma...@gmail.com <ma...@gmail.com> #370
My guess is they are stalling.... Android P is a few months away at this point. I was tempted to install it were it not for the headache of wiping my phone to do it, then do it again when the final release is out. Some have reported it working in it, but others have reported other apps like Duo not working so is it worth it? who knows. I've just learned to do without it. What i don't get is the lack of attention from other media outlets. If this was in the forfront on bigger sites it may get more traction. I've reported it to numerous sites, none of which seem interested in shedding light on it. I would have to agree with other comments, I'd bet it has to do with how they mucked with BT to get the pixel buds to pair, because that's really the only thing that's different from the other phone makers. Stupid how the media jumped on the color shift with the screen (which all screens have to some degree) but no one will report on this, a much bigger deal than the screen.
fl...@gmail.com <fl...@gmail.com> #371
Google has to be more transparent. There is an obvious issue with their bluetooth technology and it's affecting a wide range of devices including third party devices like the Gear S3 line. In addition, It's also affecting other apps like Google fit and Huawei health. If you look at the number of your steps, I guarantee that they are all different from eachother. I opened another ticket just for that issue. Feel free to chime in. https://issuetracker.google.com/issues/77606997
Google should release some kind of warning to consumers, that way they don't end up buying a device that can't deliver on it's promise. Google can get in a lot of LEGAL trouble for this.
If this continues on even during the Pixel 3 release, we should start considering legal action.
Google should release some kind of warning to consumers, that way they don't end up buying a device that can't deliver on it's promise. Google can get in a lot of LEGAL trouble for this.
If this continues on even during the Pixel 3 release, we should start considering legal action.
ma...@gmail.com <ma...@gmail.com> #372
I agree. Give us SOME transparency. And I won't belabor the point, but my watch does the same thing (ticwatch e) they are never in sync, the phone and watch. But I don't glance at the ohine app that often so it probably doesn't irritate me as much as others. That said, and I've reiterated this in past comments, there are some serious issues with adroid right now (on the Google side) with a raw os that is running as it was meant to be. Makes you wonder how many alterations Samsung and the likes have to make to fix these issues so it seems seamless on their end. It's pretty bad for a Google branded device to have more bugs than the forks of Android have. At least more noticable ones anyway. The only thing that kept me away from the Samsung ecosystem was the bloatware. If it weren't for that or ditch this phone in a heartbeat.
sh...@gmail.com <sh...@gmail.com> #373
The last time we heard anything was comment 344 which was a week ago. Please just stop by at least weekly and give us something.
fl...@gmail.com <fl...@gmail.com> #374
Looks like there is a Wear OS update for the phone today same for Duo. I'll test it out and will get back to you guys.
fl...@gmail.com <fl...@gmail.com> #375
Aaaannnd it's still broken.
sh...@gmail.com <sh...@gmail.com> #376
Same here. Probably going to take a android update to fix.
jo...@gmail.com <jo...@gmail.com> #377
I too am experiencing this issue. I purchased a ZenWatch 3 in December and was using a Samsung phone. Everything worked fine until I switched to the Google Pixel XL. The lag I experience when answering a call by phone (when paired to wearable) is 27 seconds. If the call is answered on the ZenWatch, the call connection is instant. I can then switch the call to "phone" if I don't want others to hear the conversation.
I have tried unpairing the watch and restarting it as well as unpairing and performing a factory reset on the watch and phone at the same time.
Here are the bug reports:
https://drive.google.com/file/d/1XS_VgvN4AFUuuUXi_nsCpYgkd3WqENYm/view?usp=drive_web (wearable-bugreport-NWD1.170623.001-2018-04-26-14-10-07.png)
https://drive.google.com/file/d/1C9xXMwWTV-jtTMYVPKxVaHXkSgTTEyIc/view?usp=drive_web (wearable-bugreport-NWD1.170623.001-2018-04-26-14-10-07.zip)
I have tried unpairing the watch and restarting it as well as unpairing and performing a factory reset on the watch and phone at the same time.
Here are the bug reports:
jo...@gmail.com <jo...@gmail.com> #378
sy...@google.com <sy...@google.com> #379
Re:#378, your phone is Pixel 2 XL[taimen], it is not Pixel XL.
Thanks for the updates. The problem is with Pixel 2 & Pixel 2 XL device code and we are working with appropriate team to get a fix for this issue.
Thanks for the updates. The problem is with Pixel 2 & Pixel 2 XL device code and we are working with appropriate team to get a fix for this issue.
gr...@gmail.com <gr...@gmail.com> #380
Finally an acknowledgment that it is in fact the pixel 2's and not the watches (something everyone has been saying all along)
sh...@gmail.com <sh...@gmail.com> #381
Thank you and we all appreciate it I'm sure. The only question that I think most of us have is it taking so long,
an...@gmail.com <an...@gmail.com> #382
He will never answer that. If you notice all he posts it's that they are working on it and a fix will be released in due time. He's been saying that for 5 months now.
sh...@gmail.com <sh...@gmail.com> #383
Getting ridiculous now. Two weeks without a response from Google. Shoud have never left Apple for Android.
ma...@gmail.com <ma...@gmail.com> #384
Yeah. I'm about at that point too. Issue still persists and I'm pretty well ready to ditch either the phone or buy a smart watch like the amazfit which doesn't take calls anyway since this function is pretty well usieless. Tech that's been around for over a decade and Google manages to screw it up. Stuff like this is why they can't compete with other phones running thoer own system.
ke...@gmail.com <ke...@gmail.com> #385
> I finally gave up and sold my Pixel. I waited 5 months and went through 3 watches trying to get one to work. Went back to Apple and replaced my iPhone 6 with an 8 plus using my watch series 1 and all works perfect. Just like it did 4 years ago.
ni...@gmail.com <ni...@gmail.com> #386
What boggles my mind is that there should be a simple codeset (just to get it fixed) that if you hit the phone feature ON the Pixel/2 it moves the bluetooth state to down/off and when the call ends, wait 2 seconds and turn it back on. There may be a small lag while the bluetooth deactivates, but it would be acceptable (to me that is). Watch will sync to the phone again, problem patched (not looking for permanent resolution here unless they have one and aren't saying). This way they can get it fixed in the next release and all of us watching this will quit being angry.
Please note that I say this not being a real in-depth programmer, but know enough about machines/hardware to know that there's always an easy way to turn things off and on.
Please note that I say this not being a real in-depth programmer, but know enough about machines/hardware to know that there's always an easy way to turn things off and on.
rm...@gmail.com <rm...@gmail.com> #387
> there should be a simple codeset (just to get it fixed) that if you hit the phone feature ON the Pixel/2 it moves the bluetooth state to down/off and when the call ends, wait 2 seconds and turn it back on
It can't work that way, it will disconnect other devices as well. That's a workaround, not a fix. This is a driver level issue for the Pixel 2 / XL. It's likely that higher-ups don't want the engineers working on this bug, which is a high-level driver bug, and want people with that kind of knowledge to instead work on other projects associated with Android P and potentially new hardware. It doesn't excuse Google's inability to solve the problem though, a bug like this would have been fixed and pushed to users in less than a week at Apple I'm sure. Just a few days ago, we hit 4 MONTHS, not weeks or days. Lesson learned: don't buy Google products.
It can't work that way, it will disconnect other devices as well. That's a workaround, not a fix. This is a driver level issue for the Pixel 2 / XL. It's likely that higher-ups don't want the engineers working on this bug, which is a high-level driver bug, and want people with that kind of knowledge to instead work on other projects associated with Android P and potentially new hardware. It doesn't excuse Google's inability to solve the problem though, a bug like this would have been fixed and pushed to users in less than a week at Apple I'm sure. Just a few days ago, we hit 4 MONTHS, not weeks or days. Lesson learned: don't buy Google products.
tm...@gmail.com <tm...@gmail.com> #389
It's high time we start tipping other sites about this issue ahead of Google IO.
an...@gmail.com <an...@gmail.com> #390
Yes, I've done that 2 weeks ago to Android Central, android Authority, Android Police, the Verge. But they didn't reported. But maybe I was the only one, please, everyone, do it also. Tip them the news! This is disgraceful and is taking to consider buying other brands apart from Google.
ma...@gmail.com <ma...@gmail.com> #391
Yeah. That particular site I've had conversation with about this. They at fist reported it but it wasn't accurate. I too have reported it to other sites but that's the only one that has really put some traction on it.
ru...@russellbryce.com <ru...@russellbryce.com> #394
I finally threw in the towel...powered off my Asus ZenWatch3, and chunked in the junk drawer. Then, after 5 frantic minutes of dropped calls with the air conditioning repair man who was trying to get into our gated community, I finally remembered to DELETE the Wear app from my phone...I'm hoping that will finally fix the issue for me. 6 MONTHS of phone call issues is absurd. Going back to my bulletproof $25 Timex Easy Reader, and just carrying around the huge Pixel 2 XL in my hand for 9 hours a day at work, like a ball and chain. ;)
sh...@gmail.com <sh...@gmail.com> #395
New security update just hit the airwaves for the Pixel 2 LX. Heres hoping.
an...@gmail.com <an...@gmail.com> #396
I highly doubt it. Otherwise the Google Team guy would say something about it. But please report back if it does, guys.
Cheers
Cheers
sh...@gmail.com <sh...@gmail.com> #397
Just tried, Worked the first time, them reared it's ugly hear again.. Still waiting Google.
fl...@gmail.com <fl...@gmail.com> #398
Hi Wear OS team;
Please give us detailed update on this issue. The more information, the better.
Please give us detailed update on this issue. The more information, the better.
ma...@gmail.com <ma...@gmail.com> #399
well... I've given up on it. if it isn't fixed by the time P is released (or if it takes that long) i'm getting a refund on this thing. 6 months for a fix? it's beyond and annoyance at this point. this is why google can never compete with the other guys. they just don't give a rip about it's consumers. with any other manufacturer this would have been fixed in a few weeks. absurd. and I know for a fact it has been reported to numerous outlets. fact is, googles phones are so insignificant that no one cares.
fl...@gmail.com <fl...@gmail.com> #400
Re: #399
When you ask for a refund, make sure to always site this issue tracker. Tell them you've tried all the troubleshooting steps. If you're pass the "remorse" period, they will tell you that you're only qualified for an exchange. DON'T AGREE TO IT. Demand a refund instead. Ask for the Supervisor if it gets messy.
When you ask for a refund, make sure to always site this issue tracker. Tell them you've tried all the troubleshooting steps. If you're pass the "remorse" period, they will tell you that you're only qualified for an exchange. DON'T AGREE TO IT. Demand a refund instead. Ask for the Supervisor if it gets messy.
sc...@gmail.com <sc...@gmail.com> #401
Yup, still broken on May security update. WE ARE IN MAY NOW AND STILL NO FIX!
an...@gmail.com <an...@gmail.com> #402
Another missed opportunity. This means that, best chance scenario, we have to wait another month.
Google, you should be ashamed of yourself! We demand an explanation...
Google, you should be ashamed of yourself! We demand an explanation...
so...@gmail.com <so...@gmail.com> #403
This is getting pretty ridiculous now. I've got the 4G version of the Huawei Watch 2 which I'm paying an extra line for, yet I've had to completely disable calling on the watch so as not to kill any calls coming through on my Pixel 2! What a waste of money!
I'm feeling quite pessimistic for a fix prior to the release of Android P. I've sent an email to AndroidPolice.com to see if they'll give the issue some coverage and to try and light a bit of a fire under the issue.
I'm feeling quite pessimistic for a fix prior to the release of Android P. I've sent an email to AndroidPolice.com to see if they'll give the issue some coverage and to try and light a bit of a fire under the issue.
jo...@gmail.com <jo...@gmail.com> #404
I reckon, it might be time to bite the bullet and get an s9 with a gear S3 personally. Gutted...
th...@gmail.com <th...@gmail.com> #405
I just updated to beta Android Phone and am able to receive calls, answer on my phone with no delay. Here are the tests I just performed. With Watch Bluetooth answer called on watch enabled.
1) incoming call answered on phone no delay
2) incoming call answered on phone no delay
3) incoming call answered on watch no delay
4) incoming call answered on watch no delay
5) incoming call answered on watch, transferred to phone no delay.
1) incoming call answered on phone no delay
2) incoming call answered on phone no delay
3) incoming call answered on watch no delay
4) incoming call answered on watch no delay
5) incoming call answered on watch, transferred to phone no delay.
th...@gmail.com <th...@gmail.com> #406
Post #405 should have been Android "P" Beta
an...@gmail.com <an...@gmail.com> #407
Which smartwatch are you using? Does it have a rebranded OS? My original Huawei Watch didn't receive any update, only the last generation watches, so I'm afraid that not even the Android P will fix my issue...
fl...@gmail.com <fl...@gmail.com> #408
Re: comment #405
Try restarting both the watch and the phone. Also in addition to answering incoming calls, make the call using your watch/phone. I can confirm that the bug is happening on Android P beta that just came out.
Try restarting both the watch and the phone. Also in addition to answering incoming calls, make the call using your watch/phone. I can confirm that the bug is happening on Android P beta that just came out.
th...@gmail.com <th...@gmail.com> #409
Ok restarted both Huawei Watch 2 and my Pixel 2 xl running "P Beta". (* Note * No delay means no 10 to 15 second delay, there is still a 1 to 2 second delay but that seems completely acceptable)
1) incoming call answered on phone no delay
2) incoming call answered on watch no delay
3) outgoing call from watch no delay
4) outgoing call from phone, switched to watch no delay
5) outgoing call from watch switched to phone no delay
6) outgoing call switched multiple times between phone and watch no delay.
1) incoming call answered on phone no delay
2) incoming call answered on watch no delay
3) outgoing call from watch no delay
4) outgoing call from phone, switched to watch no delay
5) outgoing call from watch switched to phone no delay
6) outgoing call switched multiple times between phone and watch no delay.
sc...@gmail.com <sc...@gmail.com> #410
Th, Ya it starts working then it will stop like 10 mins later.
ni...@gmail.com <ni...@gmail.com> #411
Methinks it's about time to start a class action suit because this is getting ridiculous. We can't even get a straight answer out of Google telling us that they're not even interested in fixing this or they are interested.
ma...@gmail.com <ma...@gmail.com> #412
I hate to be the buzzkill here but I'm not entirely sure what grounds you'd have. I mean ultimately they will refund the money for the phone. Plus it would likely be stuck in litigation for years. Not only that the lawyers would pocket most of it. The consumer would get very little. It's just frustrating when you shell out over 800 dollars straight out of your pocket. Many of us here did not buy a subsidized phone. I just want my phone to work. The worst way to hit them is to simy quit buying thier phones. Apple got the message with the iPhone x. I was an iPhone user for 10 years. I dumped them when that piece of garbage was released. And many others did too. And it got thier attention. If everyone returned these phones that would send a bigger message id think. Just my thoughts. We'd probably ly will d up with less in a lawsuit then if we just returned the phone.
ni...@gmail.com <ni...@gmail.com> #413
My issue is that I'm still making payments on mine and I got it through Verizon. I doubt that Verizon would let me get my $$ back. So I'm stuck with this.
rm...@gmail.com <rm...@gmail.com> #414
> My issue is that I'm still making payments on mine and I got it through Verizon. I doubt that Verizon would let me get my $$ back. So I'm stuck with this.
This is my issue too. I'm gonna see if they'll let me pay off my phone in full and then get a refund, if that makes sense.
This is my issue too. I'm gonna see if they'll let me pay off my phone in full and then get a refund, if that makes sense.
ma...@yahoo.com <ma...@yahoo.com> #415
I have a Martian Envoy watch and a Pixel 2. I've had this watch for over a year and I used to love using it with my Galaxy S6. The problem I'm having is that I don't want to answer calls on my watch. I just want hands free usage of some apps on my phone and notifications to show up on my watch. When I disable the Bluetooth setting for calls, it kills my mic on my watch and completely kicks me off of Bluetooth altogether, so no hands free access. If I leave calls on, I have to scramble trying to turn it back to phone every time I get a call. It's annoying. My old Galaxy worked flawlessly with this watch. Martian has ignored my emails and now I fear Google has forsaken me. Apparently both are on to bigger and better things and leaving us behind. When this P2 is paid off, I'll be going back to Galaxy. Honestly, I never should've left.
jo...@gmail.com <jo...@gmail.com> #416
The issue has been completely resolved for me on Android P DP2. Both incoming and outgoing calls are now working fine + Google Duo no longer freezes when the watch is connected.
I have been on DP2 since it was released a few days ago and have not experienced this issue once.
I have been on DP2 since it was released a few days ago and have not experienced this issue once.
th...@gmail.com <th...@gmail.com> #417
I am the same as # 416. The issue is completely resolved for me and I couldn't be happier. No issues.
ni...@gmail.com <ni...@gmail.com> #418
#416 and #417, you've rebooted the phone and watch a few times as well and tried placing a call from the watch and things worked seamlessly??
th...@gmail.com <th...@gmail.com> #419
Yes #418 I have. A number of times, and it is still working. I am expecting it to crap out, and I will keep people posted for sure.
ra...@gmail.com <ra...@gmail.com> #420
#416 and #417 what watch and phone are you using - and just to clarify - you're referring to the Wear OS DP2 correct?
jo...@gmail.com <jo...@gmail.com> #421
#420, no, I am referring to the DP2 released for the pixel 2 XL. I installed that a few days ago when it was released.
I am using my phone with the HW2 with the latest stable WearOS (NOT DP2).
Everything has been working as expected and yes, I have rebooted the phone several times since I installed DP2 on my phone.
No issues to report at this time.
The issue was never the watches, it was the Pixel code all along. DP2 seems to have fixed it on the phone side.
I am using my phone with the HW2 with the latest stable WearOS (NOT DP2).
Everything has been working as expected and yes, I have rebooted the phone several times since I installed DP2 on my phone.
No issues to report at this time.
The issue was never the watches, it was the Pixel code all along. DP2 seems to have fixed it on the phone side.
ma...@gmail.com <ma...@gmail.com> #422
That's great that the DP is working but I'm not wiping my phone to install
DP. Push out the update Google.
On Fri, May 11, 2018, 11:53 AM <buganizer-system@google.com> wrote:
DP. Push out the update Google.
On Fri, May 11, 2018, 11:53 AM <buganizer-system@google.com> wrote:
ra...@gmail.com <ra...@gmail.com> #423
Thank you for the clarification #421
rm...@gmail.com <rm...@gmail.com> #424
This issue will be resolved by the time the new rumored Pixel watches come out. Unfortunately, they can't ignore the issue despite their willingness to do so as of currently. It will happen in due time.
rm...@gmail.com <rm...@gmail.com> #425
Ah I hadn't refreshed the page! I'm glad to hear the issue is resolved!! :D
ma...@gmail.com <ma...@gmail.com> #426
Yeah....in October. A year later. If they don't push it out in the next
week I'm returning this phone for an s9. Really, the only perks to this
phone is no bloatware, an ever so slightly better camera and unlimited
photo storage. All of which I could care less about. The bloatware isn't as
much an issue of you buy the phone outright, and my photos are backed up to
my plex server automatically. And the difference in camera quality for what
I use it for doesn't matter. Oh and one more thing... Wireless charging.
On Fri, May 11, 2018, 2:38 PM <buganizer-system@google.com> wrote:
week I'm returning this phone for an s9. Really, the only perks to this
phone is no bloatware, an ever so slightly better camera and unlimited
photo storage. All of which I could care less about. The bloatware isn't as
much an issue of you buy the phone outright, and my photos are backed up to
my plex server automatically. And the difference in camera quality for what
I use it for doesn't matter. Oh and one more thing... Wireless charging.
On Fri, May 11, 2018, 2:38 PM <buganizer-system@google.com> wrote:
sc...@gmail.com <sc...@gmail.com> #427
Ya, running beta software for a fix is not fixing the issue....
ma...@gmail.com <ma...@gmail.com> #428
I just called google, asked for a supervisor, they are supposed to be in contact with me. This phone is going back. I've just had about all a person can take. I was advised that it's a "compatibility issue" and that only LG watches are supported. In other words, it's all the other smart watch manufacturers fault. They won't admit to any blame here. I'm curious, if I remember even the LG watch owners dealing with this same issue in this thread. Waiting a year on a fix is utter crap honestly. I'm not waiting around to see if they decide to push an update out to us at this point. 6 months of this is absurd. core function... broken. Not too mention the paint on the edges begining to peel. I mean this is almost a thousand dollar phone.... Been pretty disappointing.
ma...@gmail.com <ma...@gmail.com> #429
I should add, anyone else that's went through this process, how did you finally get it resolved, they will only let me communicate through email with a supervisor, is that anyone elses experience?
fl...@gmail.com <fl...@gmail.com> #430
I asked for a Supervisor when I was in chat because they were refusing to give me a refund. A supervisor will eventually get in touch with you via e-mail. Insist that the only solution is getting your money back.
sc...@gmail.com <sc...@gmail.com> #431
Still no update lately, hmm?
ma...@gmail.com <ma...@gmail.com> #432
fl...@gmail.com <fl...@gmail.com> #433
Did you ask to speak to a supervisor? I did it during chat. They told me that no supervisor was available yada yada but I said to have the supervisor reach out to me via e-mail.
ke...@gmail.com <ke...@gmail.com> #434
I went through the whole fiasco With emailing a supervisor which consumed over a week's worth of my time going nowhere. I ended up settling for a replacement phone which I sold and purchased an iPhone 10 And went back to my original Apple Watch with no problems
ma...@gmail.com <ma...@gmail.com> #435
I did ask to speak to a supervisor. Multiple times and a they would do is
tell me they had to reach out via email. Google's customer service is
definitely crap compared to Apple that's for sure. Supposedly they will
"reach out to me" I'm half tempted to get the replacement, they said they
would do that, and sell it unopened like the previous post did. But I'll
surley lose money. I won't get the 850 I spent out of it. And I traded in a
perfectly good iPhone at best buy for it too. Talk about buyer's remorse.
tell me they had to reach out via email. Google's customer service is
definitely crap compared to Apple that's for sure. Supposedly they will
"reach out to me" I'm half tempted to get the replacement, they said they
would do that, and sell it unopened like the previous post did. But I'll
surley lose money. I won't get the 850 I spent out of it. And I traded in a
perfectly good iPhone at best buy for it too. Talk about buyer's remorse.
di...@gmail.com <di...@gmail.com> #436
Still the issue remains even after updating to android P beta.
I am using Pixel 2 (Android P beta) along with Huawei watch (Wear OS 2.11.0.193584459, Android OS 7.1.1)
I am using Pixel 2 (Android P beta) along with Huawei watch (Wear OS 2.11.0.193584459, Android OS 7.1.1)
ma...@gmail.com <ma...@gmail.com> #437
I honestly don't think they are paying attention to this thread anymore. I
mean look how long it takes for them to even throw a one sentence response
up there.
mean look how long it takes for them to even throw a one sentence response
up there.
an...@gmail.com <an...@gmail.com> #438
This is outrageous. We demand an explanation and a final solution, Google or our next smartphone and our recommendation to everyone we won't be a Google brand one!
w1...@gmail.com <w1...@gmail.com> #439
Why hasn't this been fixed yet???
ma...@gmail.com <ma...@gmail.com> #440
They don't care. I definitely won't be recommending Google phones to anyone
in the future. The customer service rep I spoke to first actually blamed
all the smart watch manufactures. He said that pixels are only comparable
with lg watches so I immediately combed through this and saw they too were
having this issue. (see comment 335). What's stupid is every smartwatch
running wearos has the same chilset since Qualcomm hasn't released a new
one in over two years. (excluding Samsung and apple of course) so it's
stupid to say it's the manufacturers are to blame. Google screwed up plain
and simple and they won't fess up to it. Hence the brand doesnt matter. The
insides are pretty much the same. That's why they work fine with every
other phone.
in the future. The customer service rep I spoke to first actually blamed
all the smart watch manufactures. He said that pixels are only comparable
with lg watches so I immediately combed through this and saw they too were
having this issue. (see comment 335). What's stupid is every smartwatch
running wearos has the same chilset since Qualcomm hasn't released a new
one in over two years. (excluding Samsung and apple of course) so it's
stupid to say it's the manufacturers are to blame. Google screwed up plain
and simple and they won't fess up to it. Hence the brand doesnt matter. The
insides are pretty much the same. That's why they work fine with every
other phone.
do...@gmail.com <do...@gmail.com> #441
Got the Galaxy S9 Plus, my LG sport watch wasn't working with Pixel 2XL (gonna ask for a refund), but is working great with the S9 Plus.
ma...@gmail.com <ma...@gmail.com> #442
Finally corresponding to a supervisor… I'll keep you updated on what's happening.
ma...@gmail.com <ma...@gmail.com> #443
Directly from a Google supervisor.... they don't give a crap. And of course
there are no direct emails to respond to. How convenient. All emails come
from store-support@google.com
Just because this phone wasn't baught directly from Google and I stead
baught from an authorised reseller doesn't exempt them from everything. I
purchased this phone outright. I don't know how else to get their
attention.
"I'm sorry to hear that you are affected by this bug. Unfortunately, I do
not have a timeframe to quote you for a fix. If your end goal is a refund
for the product, then I would see if the place of purchase can make an
exception for you to return it. I unfortunately cannot refund something
that you didn't purchase from the Google Store.
Thanks,
Jonathan
The Google Support Team"
there are no direct emails to respond to. How convenient. All emails come
from store-support@google.com
Just because this phone wasn't baught directly from Google and I stead
baught from an authorised reseller doesn't exempt them from everything. I
purchased this phone outright. I don't know how else to get their
attention.
"I'm sorry to hear that you are affected by this bug. Unfortunately, I do
not have a timeframe to quote you for a fix. If your end goal is a refund
for the product, then I would see if the place of purchase can make an
exception for you to return it. I unfortunately cannot refund something
that you didn't purchase from the Google Store.
Thanks,
Jonathan
The Google Support Team"
ke...@gmail.com <ke...@gmail.com> #444
I purchased directly from Google and got the same treatment from them.
ma...@gmail.com <ma...@gmail.com> #445
Honestly, I think I'm going to Best buy tomorrow and talk to them. I still
have the packaging and receipt. Maybe if I get pointed with them about this
they will do something. If they will only give me a replacement in the end
fine. I'll just sell the unopened phone and buy an s9. Problem solved. I do
that know how else to push back seeing how the only way they will
communicate is through email. This is the absolute shoddiest costomer
service I've ever dealt with. That alone will make me never go back to a
songle Google product. This is the only one I own and it will be the last.
have the packaging and receipt. Maybe if I get pointed with them about this
they will do something. If they will only give me a replacement in the end
fine. I'll just sell the unopened phone and buy an s9. Problem solved. I do
that know how else to push back seeing how the only way they will
communicate is through email. This is the absolute shoddiest costomer
service I've ever dealt with. That alone will make me never go back to a
songle Google product. This is the only one I own and it will be the last.
ma...@gmail.com <ma...@gmail.com> #446
Course, now they are down to 670 bucks online. The more I deal with this
the more aggrivated I get.
the more aggrivated I get.
fl...@gmail.com <fl...@gmail.com> #447
No excuse for this. At the very least, Google should address it so that people don't end up buying devices that don't work properly with each other. Class Action Lawsuit needs to happen... I would totally join if someone gets it going.
For the time being, please spread the word. I've been trying to reach out to many tech websites but so far I haven't heard anything back. If you're active in social media, please get the word out there. #WearOSisBroken
For the time being, please spread the word. I've been trying to reach out to many tech websites but so far I haven't heard anything back. If you're active in social media, please get the word out there. #WearOSisBroken
ma...@gmail.com <ma...@gmail.com> #448
I still don't think the consumer would benefit much from lawsuit but hey.
If it's worth pursuing maybe THAT will finally get Google's attention. I
mean hey, apple got sued over those stupidly designed butterfly keyboards
and the consumer is at least getting their money back.
If it's worth pursuing maybe THAT will finally get Google's attention. I
mean hey, apple got sued over those stupidly designed butterfly keyboards
and the consumer is at least getting their money back.
ma...@gmail.com <ma...@gmail.com> #449
I just contacted Girard Gibbs, the firm that sued google over the
microphone issues with the pixel 2. Maybe that will get their attention.
microphone issues with the pixel 2. Maybe that will get their attention.
rm...@gmail.com <rm...@gmail.com> #450
> Girard Gibbs
Very good find! The firm's lawsuit is ongoing and taking responses from Pixel 2 users!
ATTENTION all Pixel 2 owners having this issue: do a Google search for "Girard Gibbs Pixel 2" and click the first link for their website. At the top where it says "Own a Pixel? Click Here for a Free Consultation", follow the link and take the SURVEY. Fill out any issues you have been having with your Pixel 2, in addition to checking off "Other" and entering in the details of this bug. If enough users submit these claims, legal action may be taken: if Google does not want to fix this bug, they'll be hit with a fine potentially worth a few million dollars instead.
Very good find! The firm's lawsuit is ongoing and taking responses from Pixel 2 users!
ATTENTION all Pixel 2 owners having this issue: do a Google search for "Girard Gibbs Pixel 2" and click the first link for their website. At the top where it says "Own a Pixel? Click Here for a Free Consultation", follow the link and take the SURVEY. Fill out any issues you have been having with your Pixel 2, in addition to checking off "Other" and entering in the details of this bug. If enough users submit these claims, legal action may be taken: if Google does not want to fix this bug, they'll be hit with a fine potentially worth a few million dollars instead.
va...@gmail.com <va...@gmail.com> #451
No idea what I did right,
But 'voice over Bluetooth ' thing's been working just fine since past few hours.
Pixel 2 & To watch e
But 'voice over Bluetooth ' thing's been working just fine since past few hours.
Pixel 2 & To watch e
ma...@gmail.com <ma...@gmail.com> #452
They pushed out an update last night (I have the same watch, ticwatch e) it
worked one time then went back to doing the same thing. Actually,. It may
be worse. I tried to answer the call on my watch and it locked up. Saying
"answer call on phone" then there was 15 seconds of silence.
worked one time then went back to doing the same thing. Actually,. It may
be worse. I tried to answer the call on my watch and it locked up. Saying
"answer call on phone" then there was 15 seconds of silence.
ma...@gmail.com <ma...@gmail.com> #453
Actually what is odd is that there has always been a significant delay in
the watch as well. When the phone rings sometimes it takes 5-7 seconds
before the watch ever recognizes that the phone is ringing. (Which means
that I'm still pulling the phone out of my pocket to see who is calling) So
the Bluetooth handshake there is a mess all over the board. When I had I
paired to my iPhone it was fine. Watch responded right when the phone rang,
albeit I couldn't answer on my watch because of limitations with iOS but it
always recognized when the phone was ringing. (hense the reason, and thus
the frustration, of buying the pixel 2)
I can't even reiterate enough how bad they screwed up Bluetooth on this
phone.
the watch as well. When the phone rings sometimes it takes 5-7 seconds
before the watch ever recognizes that the phone is ringing. (Which means
that I'm still pulling the phone out of my pocket to see who is calling) So
the Bluetooth handshake there is a mess all over the board. When I had I
paired to my iPhone it was fine. Watch responded right when the phone rang,
albeit I couldn't answer on my watch because of limitations with iOS but it
always recognized when the phone was ringing. (hense the reason, and thus
the frustration, of buying the pixel 2)
I can't even reiterate enough how bad they screwed up Bluetooth on this
phone.
ph...@gmail.com <ph...@gmail.com> #454
Yeah bluetooth is not working correct at all. Today I noticed, that when I play music over bluetooth in my car, it always shows the wrong song information and even the time-bar is completely wrong. Please google just implement bluetooth so its compatible with the standard. It is really frustration when a company says a phone has the newest bluetooth standard, but then it turns out it is not standard at all... I think that this is illegal even since you make wrong clams and misinform your customers.
ma...@gmail.com <ma...@gmail.com> #455
Yep. Their supervisor i had been corresponding with fell off the map when
I mentioned Girard Gibbs... They know this is a huge issue. Eventually it
will force their had one way or another. Haven't heard a peep since. I
think I can safely say we are all frustrated to no end on this. At least 6
months now...
I mentioned Girard Gibbs... They know this is a huge issue. Eventually it
will force their had one way or another. Haven't heard a peep since. I
think I can safely say we are all frustrated to no end on this. At least 6
months now...
fl...@gmail.com <fl...@gmail.com> #456
Wear OS Team;
Can you kindly give us an update on this issue?
Can you kindly give us an update on this issue?
sh...@gmail.com <sh...@gmail.com> #457
Haha. Good luck with that.
ma...@gmail.com <ma...@gmail.com> #458
seriously… what i have started doing is every time an article pops up in my news feed about features of the pixel2 I just start referring to this issue in the comments and referencing the issue-tracker. I just posted one on android authority. I'll say it again, worst. customer. service. ever. I will never buy another google product.
ra...@gmail.com <ra...@gmail.com> #459
Again, as a reminder, THIS IS NOT A WEAR OS issue. It is an issue with the Pixel's Bluetooth stack. The phone simply can't handle Bluetooth properly.
Samsung phones don't have this problem with Wear OS watches.
The Pixel has this same problem with non Wear OS watches (i.e. Tizen powered Gear watches).
Hopefully, Google has been studying how Samsung implements Bluetooth on their Android devices and is able to duplicate Samsung's Bluetooth stack.
With the upcoming Pixel Watch (with a new Qualcomm chipset) and Pixel 3 series rumored to be unveiled this fall, I hope they have something in place by then. There's a lot on the line for Google with this new generation of watches. They better get it right.
Samsung phones don't have this problem with Wear OS watches.
The Pixel has this same problem with non Wear OS watches (i.e. Tizen powered Gear watches).
Hopefully, Google has been studying how Samsung implements Bluetooth on their Android devices and is able to duplicate Samsung's Bluetooth stack.
With the upcoming Pixel Watch (with a new Qualcomm chipset) and Pixel 3 series rumored to be unveiled this fall, I hope they have something in place by then. There's a lot on the line for Google with this new generation of watches. They better get it right.
ma...@gmail.com <ma...@gmail.com> #460
Too late for that with me. I don't care how "great" their next product is, i'm done. And I'd say there are probably more than one in this thread that won't buy another google product again. If their support and service are this crappy why would you want to deal with them? I'd even buy a phone with less options, THAT WORKS correctly than buy another one of these things. I'm an IT guy and I love the latest of what technology has to offer, but this is just unacceptable. a 6 month defect that has yet to be addressed and they won't even update us on the progress (if there is any)? I'm sorry but every other manufacturer practically, has better support than this. I've even seen Chinese knock offs with better support, and that's saying something...
sc...@gmail.com <sc...@gmail.com> #461
We would like an update please.
ta...@gmail.com <ta...@gmail.com> #462
@sc... in our dreams! They're not going to bother with this because it'll be fixed in P. So we're going to wait until August to have a completely separate set of issues.
an...@gmail.com <an...@gmail.com> #463
sy...@Google.com, please answer!
ma...@gmail.com <ma...@gmail.com> #464
It isn't fixed in P though that's the problem. We will just be stuck with a phone thats only functions partially that they will never address. They may address it with the 3. But I'll bet they never touch ours. No matter though, they just lost yet another user to Samsung.
On May 24, 2018, 10:35 AM, at 10:35 AM, buganizer-system@google.com wrote:
On May 24, 2018, 10:35 AM, at 10:35 AM, buganizer-system@google.com wrote:
ke...@gmail.com <ke...@gmail.com> #465
It's all about communication. If communication was there to begin with that would be another story. But without it Google has lost me as a current user and most likely a future user.
jo...@gmail.com <jo...@gmail.com> #466
It is 100% fixed in P for me. Been running the beta since it launched a few weeks ago and no issues so far.
th...@gmail.com <th...@gmail.com> #467
Same here. Running perfect now on Beta P
fl...@gmail.com <fl...@gmail.com> #468
Make sure you guys are testing it thoroughly. My Pixel 2 XL was on DP2 and I was still experiencing the same issue. I even tried it with Wear OS DP2 and still had the same results.
sc...@gmail.com <sc...@gmail.com> #469
I've been submitting this page to various tech outlets to see if they will do a write up but no one wants to touch it (even though they usually foam at the mouth for Pixel 2 bug reports) I just don't understand why this is so hard to address?
2k...@gmail.com <2k...@gmail.com> #470
Exact same issue with my pixel 2 xl and Fossil Q Explorist
sc...@gmail.com <sc...@gmail.com> #471
Priority P0 my a$$
sc...@gmail.com <sc...@gmail.com> #472
Did everyone just give up?
fl...@gmail.com <fl...@gmail.com> #473
Did you mean, did Google* give up on their loyal customers who bought in to this whole "made by Google" crap? Yes, it looks that way.
I'm super upset. This is coming from someone who invested so much on their hardware in the past year. (Pixel buds, a number of Google home devices, Chromebook, Chromecast etc). This whole experience has been a nightmare.
Google doesn't care. They're all just laughing at us.
I'm super upset. This is coming from someone who invested so much on their hardware in the past year. (Pixel buds, a number of Google home devices, Chromebook, Chromecast etc). This whole experience has been a nightmare.
Google doesn't care. They're all just laughing at us.
fl...@gmail.com <fl...@gmail.com> #474
June security update rolling out today. Should we even be hopeful? Google basically abandoned us.
an...@gmail.com <an...@gmail.com> #475
I haven't done the update yet but things are getting worse and worse. Now, even with the setting turned off, the name of the person calling me dosent show on my Huawei Watch :(
sh...@gmail.com <sh...@gmail.com> #476
I can verify, Not fixed on June security update.
sy...@google.com <sy...@google.com> #477
We appreciate your patience and have a fix ready for the issue. Our team is running tests against the fix. We will provide further details as they are available.
sh...@gmail.com <sh...@gmail.com> #478
Do we have to wait for the P update.
an...@gmail.com <an...@gmail.com> #479
Google team guy: are you a bot? Your saying the same thing for months.
sc...@gmail.com <sc...@gmail.com> #480
@sy what is the fix, the phone app, google play services, wear os update. or the June security update on the Pixel. More details would be appreciated.
sy...@google.com <sy...@google.com> #481
The fix is integrated to Pixel 2 & Pixel 2XL audio hardware modules and the fix will be released as part of pixel updates. The fix is still under testing and can't assure any public release dates.
sc...@gmail.com <sc...@gmail.com> #482
So it will be one of the future security updates?
fl...@gmail.com <fl...@gmail.com> #483
Future updates like 5 years from now lmao.
sc...@gmail.com <sc...@gmail.com> #484
...Lol... The line of communication needs to be more frequent and transparent from google.
sc...@gmail.com <sc...@gmail.com> #485
Waiting for updates be like https://i.imgflip.com/11qcpe.jpg
I feel like we should get some compensation like a Google home mini for our troubles.
I feel like we should get some compensation like a Google home mini for our troubles.
fl...@gmail.com <fl...@gmail.com> #486
Nah. More like they should give us our money back and let us have the Pixel 3 XL for free when it comes out.
ta...@gmail.com <ta...@gmail.com> #487
SOMETHING would be nice. This kind of behaviour from a flagship would be an enormous story for samsung or apple, but since it's a pixel...we're beta testers essentially.
ma...@gmail.com <ma...@gmail.com> #488
Shoot, I could care less if they offered an entire suite of Google products to make up for this absurd experience. They burnt that bridge. I still won't buy another Google product. With customer service this poor and the sheer fact it has taken now over 6 months for a fix.... Yeah, I'm not going back. Previous poster is right, if this had been apple or Samsung can you imagine the media back lash? Just shows you how insignificant Google is on the playing field when it comes to hardware. At this point I'd buy less innovative tech for better consumer relations than buy another Google product. So go ahead Google, try to make amends with us, I doubt it will ever happen. Simply because they don't care about the consumer. We are good enough to be beta testers but not not good enough to actually listen to us.
On Jun 5, 2018, 3:38 PM, at 3:38 PM, buganizer-system@google.com wrote:
On Jun 5, 2018, 3:38 PM, at 3:38 PM, buganizer-system@google.com wrote:
ma...@gmail.com <ma...@gmail.com> #489
Seriously.... https://www.droid-life.com/2018/06/05/is-your-pixel-2-xl-slow-to-wake-after-junes-update/
1. They will report on this stupid issue but send them a real story on a core function that's broke and you get zero traction?
2. Google is all over this dumb slightly longer delay but they can't fix their Bluetooth issues in a timely manner?
I can say this, I'm a general contractor and if it took my employees 6 months to remodel a bathroom I'd have canned them. Just saying.
On Jun 5, 2018, 3:38 PM, at 3:38 PM, buganizer-system@google.com wrote:
1. They will report on this stupid issue but send them a real story on a core function that's broke and you get zero traction?
2. Google is all over this dumb slightly longer delay but they can't fix their Bluetooth issues in a timely manner?
I can say this, I'm a general contractor and if it took my employees 6 months to remodel a bathroom I'd have canned them. Just saying.
On Jun 5, 2018, 3:38 PM, at 3:38 PM, buganizer-system@google.com wrote:
sc...@gmail.com <sc...@gmail.com> #490
@ma It's frustrating no news outlet will report on this. I generally believe it could help speed up this process.
ma...@gmail.com <ma...@gmail.com> #491
I've come to the conclusion that it's really because Google's products are so half hearted that people just expect it. That's why apple and Samsung really get run through the ringer when there is a bug. It's because their products are so polished usually. Google is like Microsoft, everybody just expects there to be some stupid thing wrong with everything they make. Think about it, what Google branded product is actually polished before they release something else? Everything they have they rely on the user base to find the bugs. Face it, to Google you are the product, not the other way around.
On Jun 5, 2018, 9:41 PM, at 9:41 PM, buganizer-system@google.com wrote:
On Jun 5, 2018, 9:41 PM, at 9:41 PM, buganizer-system@google.com wrote:
mp...@gmail.com <mp...@gmail.com> #492
Google.... have I missed something ? Are you looking at this? Have you a solution?
di...@gmail.com <di...@gmail.com> #493
I think latest update to android 9.0 DP3 have fixed this issue. Anyone else can confirm ?
so...@gmail.com <so...@gmail.com> #494
Make sure you have tested it thoroughly, people have thought it's been fixed in previous DP releases only to find it's resurfaced after a few days of use. I can't say I'm super optimistic about it being fixed in DP3. Sadly can't test myself as I'm on 8.1 stable.
mr...@gmail.com <mr...@gmail.com> #495
I installed Android 9.0 DP3 yesterday and I think it did happen to me. I'll monitor it closely for few days and report back.
fl...@gmail.com <fl...@gmail.com> #496
Just tested this thoroughly on DP3. I can confirm that the bug is still there. So is this bug https://issuetracker.google.com/issues/77606997
I'm really missing my iPhone and Apple Watch combo right now. Hoping they figure this out before the official release of Android P.
I'm really missing my iPhone and Apple Watch combo right now. Hoping they figure this out before the official release of Android P.
ma...@gmail.com <ma...@gmail.com> #497
In DP3 it seems to me they fixed it. Now, during a call, I can choose between phone , speaker , bluetooth headphones and huawei watch 2. It switches fast and there is no delay, when you answer the call on a phone any more.
an...@gmail.com <an...@gmail.com> #498
Yeah, but that's not a proper fix. I won't be installing beta software, I shouldn't need it for a fix that could be pushed in a monthly security update. And this means we will have to wait for Android 9 which only comes in August or September. Shame on Google!
ma...@gmail.com <ma...@gmail.com> #499
The issue is not being able to switch during a call. That's always been fine. It's answering a call while the watch is connected. I'm just severely dissapointed in this phone. I'm selling or trading it off this week anyway. And besides, it looks as if Google is jumping on the notch bandwagon with the pixel 3. If I wanted that I'd buy apple. At least they have a purpose for it, ugly as it may be. I'm just dumping this phone for an s9. At least they work. It's rediculous that this is still an issue. And unacceptable. I can say this, I'm done with Google's hardware period. Never again.
On Jun 11, 2018, 7:49 AM, at 7:49 AM, buganizer-system@google.com wrote:
On Jun 11, 2018, 7:49 AM, at 7:49 AM, buganizer-system@google.com wrote:
ma...@gmail.com <ma...@gmail.com> #500
Well I finally chucked my pixel 2 xl. Went to bestbuy, where I bought it, and they were already aware of these issues. They swapped it out with a galaxy s9+ no questions asked. And guess what, the watch works fine with it. Zero issues. Never again will I buy a Google product.
null
null
sc...@gmail.com <sc...@gmail.com> #501
Good for you ma. I will not bite that bullet, but I am glad best buy did right by you even if google didn't. Maybe speaking with your wallet will wake them the eff up.
ma...@gmail.com <ma...@gmail.com> #502
Yeah, That BestBuy manager deserves major props. I was fully ready to just eat some of that cost considering i had it since january. I figured I'd have to pay at least some because trade in wouldn't come to the cost of the s9+, but i figured it was worth a shot, but he said because it's within a year not to worry about it. They are just going to send that piece of crap back to google. He was actually surprised the google rep wouldn't refund it because they had their money what difference did it make. I even got some money back because the s9 was a little cheaper.
And google if you actually follow this, I had the manager and another associate saying they would now caution people against buying your junk since you won't fix it. And since best buy is probably one of your major resellers, at least that one store isn't going to be recommending customers buy this crap.
And google if you actually follow this, I had the manager and another associate saying they would now caution people against buying your junk since you won't fix it. And since best buy is probably one of your major resellers, at least that one store isn't going to be recommending customers buy this crap.
an...@gmail.com <an...@gmail.com> #504
Finally someone paying attention to this eternal unsolved bug.
ma...@gmail.com <ma...@gmail.com> #505
My sentiments exactly.
null
null
fl...@gmail.com <fl...@gmail.com> #506
Great. Finally! I sent them a letter about a month ago along with others here. Please retweet, repost, share this article to as many people as you can.
ra...@gmail.com <ra...@gmail.com> #507
This is what happens when you use Java for your framework. The entire Java Framework needs to be ripped out and replaced.
sc...@gmail.com <sc...@gmail.com> #508
I am glad android police finally posted it. I submitted this to them but they rejected it last month. Will this finally get Google's attention????
no...@gmail.com <no...@gmail.com> #509
Can't get any call at all with Pixel 2 + Huawei Watch 2
Google play services build: 12.8.62
Android 8.0
Wear OS: 1.2
Watch build: OWDE.180215.017
Home App: 2.12.0
I can't switch from phone or speakers to Bluetooth either, it switches back to default.
Google play services build: 12.8.62
Android 8.0
Wear OS: 1.2
Watch build: OWDE.180215.017
Home App: 2.12.0
I can't switch from phone or speakers to Bluetooth either, it switches back to default.
fl...@gmail.com <fl...@gmail.com> #510
Pixel 2 XL and Huawei Watch 2 doing the same thing.
2k...@gmail.com <2k...@gmail.com> #511
Any update so far, this should be a priority issue and fixed ASAP.
sc...@gmail.com <sc...@gmail.com> #512
We are almost in July and Google still refuses to fix this.
rm...@gmail.com <rm...@gmail.com> #513
> We are almost in July and Google still refuses to fix this.
I'm hoping we hit December, the 365th day mark will be a new low and will look great for Girard Gibbs.
I'm hoping we hit December, the 365th day mark will be a new low and will look great for Girard Gibbs.
ma...@gmail.com <ma...@gmail.com> #514
Only for this report. This has been an issue since it was released. October will be a year. The fact that they are so lazy as to not even see what others have done to make it work is beyond incompetent. Because if they WERE doing that it would have been fixed. Seeing how everybody else has it working. There were actually a few reports of Samsung's phones doing it early on but they fixed it in a few weeks.
null
null
ni...@gmail.com <ni...@gmail.com> #515
It's nice to see that this is how Google handles a P0 type of Priority. Also one that can affect safety and 911 dialing.
[Deleted User] <[Deleted User]> #516
Pixel 2 and LG Watch Sport. This is horrible behaviour. people keep laughing at me for failing to answer phone calls.... had to disable phone calls on the watch.
Finally realised I'm not the only one who suffers.
Finally realised I'm not the only one who suffers.
sc...@gmail.com <sc...@gmail.com> #517
Can we get someone assigned to this who actually cares?
ta...@gmail.com <ta...@gmail.com> #518
@pi...@gmail.com
@sy...@google.com
Looking at you. It's been over 6 months, this is a priority 0 issue. COME ON. At the VERY least provide a status update - this is asinine. We all spent a decent chunk of money on these devices, we don't appreciate being treated like beta testers.
@sy...@google.com
Looking at you. It's been over 6 months, this is a priority 0 issue. COME ON. At the VERY least provide a status update - this is asinine. We all spent a decent chunk of money on these devices, we don't appreciate being treated like beta testers.
sh...@gmail.com <sh...@gmail.com> #519
Three weeks now without a comment from Google. What's going on with this issue Google?
fl...@gmail.com <fl...@gmail.com> #520
I just sold my Huawei Watch 2 and have been using Fitbit Ionic instead. It's more of a fitness watch, i know, but at least my step count is not all over the place (and actually syncs with their app!) https://issuetracker.google.com/issues/77606997
id...@gmail.com <id...@gmail.com> #521
This will never be fixed. I have been receiving notification emails about this since December of 2017. I'm unsubscribing, y'all have fun :)
sc...@gmail.com <sc...@gmail.com> #522
July security patch does not show this being fixed.
an...@gmail.com <an...@gmail.com> #523
As expected. Google will never fix this. They don't care.
ni...@gmail.com <ni...@gmail.com> #524
With GA now having a hands free driving cell law, there are times when I have to use my watch to answer my phone. It is getting to be a big hassle having to switch on my bluetooth on my watch whenever I have to step into a car that doesn't have BT capabilities and then turn it back off again when I'm done with the drive. Again, Google, this is now not only a safety issue, this is now not only affecting me, but an entire state's population that would use your phone from effectively following a law. Please step this up or let us know that you are abandoning this fix.
so...@gmail.com <so...@gmail.com> #525
Well this doesn't just affect watches, it also affects other Bluetooth devices which have phone call capabilities e.g. headsets, Bluetooth speakers. It means I CAN'T use hands free kits at all in my car, so if I want to take a call I have to either use speakerphone or pull over. It's crazy how crippled my calling experience is thanks to this bug which is now 7 months old!?!? And no further updates or acknowledgements from Google? Wth is even going on anymore?
ma...@gmail.com <ma...@gmail.com> #526
Google isn't going to fix this with the pixel 2. I'll bet once the 3 is released they will abandon the 2 altogether. So all of us that bought one are screwed. Which means if you have an XL you blew over 900 bucks. Thankfully I purchased mine outright and BestBuy took it back no questions asked even after owning it for almost 6 months. If i was on contract with it subsidized I'd be even more ticked off than I was because those people really are screwed. I really do hope some firm picks this up and hits them where it counts, the wallet.
ma...@gmail.com <ma...@gmail.com> #527
Googles own words… "
P1 An issue that needs to be addressed quickly. Such an issue significantly impacts a large percentage of users; if there is a workaround it is partial or overly painful. The impact of the issue is to a core organizational function, or fundamentally impedes another team.
"
What's stupid is that there is no workaround at all. You have to turn the bluetooth off on the connected device for the phone to function properly. This should be P0, not P1. But even at P1, "quickly" hasn't even factored in here.
P1 An issue that needs to be addressed quickly. Such an issue significantly impacts a large percentage of users; if there is a workaround it is partial or overly painful. The impact of the issue is to a core organizational function, or fundamentally impedes another team.
"
What's stupid is that there is no workaround at all. You have to turn the bluetooth off on the connected device for the phone to function properly. This should be P0, not P1. But even at P1, "quickly" hasn't even factored in here.
sc...@gmail.com <sc...@gmail.com> #528
I am really fed up with the lack of communication.
sh...@gmail.com <sh...@gmail.com> #529
Any word if July update fixes this issue.
sh...@gmail.com <sh...@gmail.com> #530
I just answered that myself. It dosen't.
ch...@gmail.com <ch...@gmail.com> #531
Same problem here and reading through this thread I am not sure I made the right decision leaving Apple for the Google phones. Guess I'll be switching back.
ru...@russellbryce.com <ru...@russellbryce.com> #532
Yesterday my Pixel 2 XL updated to Android 8.1.0 (Security Patch Level July 5, 2018), and it did not fix it.
Every week someone compliments my Asus Zenwatch 3, and asks me what it does. Me: "It displays the time AND date. But, unlike a regular watch, this watch requires me to put it on a charger all night." :D
I still like the phone. But damn...that was $200 flushed down the toilet on the watch. I see Google is getting ready to launch their own line of smartwatches. I guess they're hoping we'll just give up and buy those...assuming they work with the Google phones?
Every week someone compliments my Asus Zenwatch 3, and asks me what it does. Me: "It displays the time AND date. But, unlike a regular watch, this watch requires me to put it on a charger all night." :D
I still like the phone. But damn...that was $200 flushed down the toilet on the watch. I see Google is getting ready to launch their own line of smartwatches. I guess they're hoping we'll just give up and buy those...assuming they work with the Google phones?
ar...@gmail.com <ar...@gmail.com> #533
Could it be that it got fixed with the latest WearOS update? I have received it for my TicwatchE and 2 calls in a row got notified...
rm...@gmail.com <rm...@gmail.com> #534
Not working for me, it starts off like that and gets worse. They will never fix this. Even if they were sued for millions in the class-action, I'm sure they still wouldn't fix this. At this point, take your business elsewhere if you are expecting a fix. Google simply does not care about you or the phone they can't fix.
pi...@gmail.com <pi...@gmail.com> #535
OP here. Please READ the description before commenting uselessly. #533 is a great example of not even knowing what this bug is about
ar...@gmail.com <ar...@gmail.com> #536
sorry for confused reply. I still believe this bug is related via calls from watch and notification as well.
to confirm: bug is not fixed
to confirm: bug is not fixed
ro...@gmail.com <ro...@gmail.com> #537
I think that we can forget to fix in oreao lifecycle updates. It seems that for a whole time as a main flagship pixel 2/pixel 2xl will occure this bug. I hope that in android p will be changed whole mechanism how watches communicate with ANDROID phones because there is another annoying things like
- delay of display who is calling on watch sometimes take a long time
When my huawei watches was paired with iphone there was no such a delay. Contact number or name of incoming calls shows immediatli when phone started ringing.
- delay of display who is calling on watch sometimes take a long time
When my huawei watches was paired with iphone there was no such a delay. Contact number or name of incoming calls shows immediatli when phone started ringing.
sh...@gmail.com <sh...@gmail.com> #538
Any update Google team.
an...@gmail.com <an...@gmail.com> #539
OP at least please confirm if Android P will indeed fix this problem for all of us, even who uses older Android smartwatches, ok?
Thanks
Thanks
so...@gmail.com <so...@gmail.com> #540
If P doesn't fix this I will be getting in contact with the Google store and asking for a refund under the Consumer Rights Act 2015, as the phone is no longer fit for purpose.
an...@gmail.com <an...@gmail.com> #541
Not only that but my Pixel 2 as gotten slower and less smooth lately. I'll be asking for a refund as well :(
sc...@gmail.com <sc...@gmail.com> #542
My pixel 2 xl has slowed down a lot too. This is really poor polish.
ch...@gmail.com <ch...@gmail.com> #543
ro...@gmail.com <ro...@gmail.com> #544
it seems to be fixed for me. I tested a several incoming calls with no lags
rm...@gmail.com <rm...@gmail.com> #545
Phone is the most stable it's been in months. The issue may have also cleared up, I was able to take a call from my headphones via USB C adapter without issues, and I reenabled calls from my watch.
li...@gmail.com <li...@gmail.com> #546
My pixel 2 got unbearably slow too. That combined with the ever present
10+ second delay finally got to me. I'm typing this from my new Galaxy S9
that can actually answer calls immediately whether on my phone, watch or
car. Pixel 2 was $700+ down the drain and of course the Galaxy wasn't
cheap either, but at least I can use my phone as a phone again, and now
enjoy my Huawei watch. So long, Google... hello Bixby??
On Mon, Aug 6, 2018, 4:10 PM <buganizer-system@google.com> wrote:
10+ second delay finally got to me. I'm typing this from my new Galaxy S9
that can actually answer calls immediately whether on my phone, watch or
car. Pixel 2 was $700+ down the drain and of course the Galaxy wasn't
cheap either, but at least I can use my phone as a phone again, and now
enjoy my Huawei watch. So long, Google... hello Bixby??
On Mon, Aug 6, 2018, 4:10 PM <buganizer-system@google.com> wrote:
sc...@gmail.com <sc...@gmail.com> #547
Android Pie seems to have fixed the issue. I have been testing for about an hour and no calls had the delay. The phone also seems to be running much faster. We shall see.
ro...@gmail.com <ro...@gmail.com> #548
but i noticed a laggy/delayed writing of this comment. Keyboard on phone is responsible but there is a delay of showing what i wrote to this comment window after pie update. Do you have a same behavour on yours pixels 2?
rm...@gmail.com <rm...@gmail.com> #549
> but i noticed a laggy/delayed writing of this comment. Keyboard on phone is responsible but there is a delay of showing what i wrote to this comment window after pie update. Do you have a same behavour on yours pixels 2?
Yeah, it's because of the amount of comments in this bug report. It's eating all of the memory on mobile Chrome's browser. It's nothing to be concerned about in regards to Android Pie
Yeah, it's because of the amount of comments in this bug report. It's eating all of the memory on mobile Chrome's browser. It's nothing to be concerned about in regards to Android Pie
sh...@gmail.com <sh...@gmail.com> #550
After installing Pie, all seems to be working now. At least 10 calls since update and no 10 second lags.
an...@gmail.com <an...@gmail.com> #551
I also confirm that it's finally working now. I still get some seconds until the smartwatch starts showing the callers name, though. But at least it works.
sh...@gmail.com <sh...@gmail.com> #552
Even though it seems to be working now I still feel that the Google team did a very poor job commuicating with all of us conscerning this matter. All you had to do was drop in once a week and give us an update. You have left a sour taste in our mouths. I wonder how many of us would even consider a Pixel 3 now. I know I won't.
so...@gmail.com <so...@gmail.com> #553
I've only had one call come in so far and it worked fine. Need to have a few more calls come in first before I make a final judgement but all seems positive at the moment.
rm...@gmail.com <rm...@gmail.com> #554
Update: I've taken 3 calls from my watch and have had no issues. The problem is resolved on my end.
ma...@gmail.com <ma...@gmail.com> #555
I find it interesting that all of the sudden everyone is just peachy with it being fixed. Lest we forget that it took them almost a YEAR to fix a simple issue. They didn't even bother rolling out a fix for 8. And effectively just kicked the pixel 2 users to the curb. If apple or samsung had this issue it would have been a media backlash like you've never seen. But I guess everyone just knows Googles products are crap so there is hardly a blip on the radar.
10 months is unacceptable. Good grief.
On Aug 7, 2018, 1:14 PM, at 1:14 PM, buganizer-system@google.com wrote:
10 months is unacceptable. Good grief.
On Aug 7, 2018, 1:14 PM, at 1:14 PM, buganizer-system@google.com wrote:
sh...@gmail.com <sh...@gmail.com> #556
See #552
rm...@gmail.com <rm...@gmail.com> #557
> I find it interesting that all of the sudden everyone is just peachy with it being fixed. Lest we forget that it took them almost a YEAR to fix a simple issue. They didn't even bother rolling out a fix for 8. And effectively just kicked the pixel 2 users to the curb. If apple or samsung had this issue it would have been a media backlash like you've never seen. But I guess everyone just knows Googles products are crap so there is hardly a blip on the radar.
> 10 months is unacceptable. Good grief.
I'm honestly just happy it's fixed, I wasn't ever expecting it to be. What I've learned from all of this is that I will stay away from Google products from here on out because they don't seem to care about their users very much, and their software is constantly in a broken beta stare. Their name is tarnished, I will never buy their hardware again nor recommend it to anybody unless I really, really dislike them. It's nice having the latest version of Android, but it's much nicer to have a working phone, especially when I've paid a very premium price for it.
I'll take my money elsewhere.
> 10 months is unacceptable. Good grief.
I'm honestly just happy it's fixed, I wasn't ever expecting it to be. What I've learned from all of this is that I will stay away from Google products from here on out because they don't seem to care about their users very much, and their software is constantly in a broken beta stare. Their name is tarnished, I will never buy their hardware again nor recommend it to anybody unless I really, really dislike them. It's nice having the latest version of Android, but it's much nicer to have a working phone, especially when I've paid a very premium price for it.
I'll take my money elsewhere.
sc...@gmail.com <sc...@gmail.com> #558
I too am happy its fixed. 10 months is a garbage turn around time. Like Sh says, even checking in once a week would have been nice.
ra...@gmail.com <ra...@gmail.com> #559
Finally - some press coverage and acknowledgement of the issues some 10 months after the fact. I hope this is truly fixed for you all still with this phone:
https://www.androidpolice.com/2018/08/08/android-pie-finally-fixes-wear-os-phone-audio-bug-10-months/
rm...@gmail.com <rm...@gmail.com> #560
I experienced the bug today a few hours ago, hopefully it was just an off thing.
sc...@gmail.com <sc...@gmail.com> #561
Pretty funny this has not been marked closed with no updates.
pr...@gmail.com <pr...@gmail.com> #562
It shouldn't be marked close because I've experienced it several times since the pie update. 5 mins ago was the lastest.
sc...@gmail.com <sc...@gmail.com> #563
Interesting. I have not been able to replicate it since the pie update all month.
ro...@gmail.com <ro...@gmail.com> #564
Last two calls I had a similar problem. There was a call routing problem.The phone app after answering acts like it is routing sound to bluetooth device (watch) but no sound from watch or phone. I had to manualy switch routing to the phone and after that I was able hear a caller. This repeats again than I tried disable Play phone voice call on watch and enable. After that several calls was routed well. This is a little bit frustrating when you has to always face to some kind of problems. The phone app was updated yesterday. I am hoping that it was a one time problem and will not be repeated.
pa...@gmail.com <pa...@gmail.com> #565
So it's fixed only for wear os, samsung s3 (tizen) still have this problem, correct?
P.s. I own xl2 and gear s3 and have this problem
P.s. I own xl2 and gear s3 and have this problem
ch...@gmail.com <ch...@gmail.com> #566
This is Pixel 2/2XL related. Please fix. Ticwatch E. Or even a follow up would be nice.
ch...@gmail.com <ch...@gmail.com> #567
Disable and enabling "Play phone voice call on watch" does appear to help. Pixel 2, Ticwatch E
ch...@gmail.com <ch...@gmail.com> #568
Still delayed. Leaving always on display does seem to work. But I rather have this off to preserve battery life and OLED burn in.
fl...@gmail.com <fl...@gmail.com> #569
You guys still here? Get your refund from Google. Site this bug report and demand to speak with the supervisor. I was here for months waiting for a fix. I think the hardware itself might be flawed. I purchased mine last year and still received a refund. I also got rid of my Huawei Watch. Wear OS still needs a lot of work. Currently on the Essential phone ($250) and Fitbit Ionic setup. So far everything is working as it should. Good luck everyone!
sc...@gmail.com <sc...@gmail.com> #570
No FL, problem was fixed with pie.
rm...@gmail.com <rm...@gmail.com> #571
Problem still comes and goes, albeit infrequently, but the point is that it's actually working now, along with other Bluetooth devices that would bug out. Still not quite satisfied but not unsatisfied either.
fl...@gmail.com <fl...@gmail.com> #572
The questions is, will you guys get the Pixel 3 XL after going through this mess? Lol.
rm...@gmail.com <rm...@gmail.com> #573
Absolutely not. They should be the ones giving them to us so we don't leave their platform.
rm...@gmail.com <rm...@gmail.com> #574
Issue still occurring, can't switch Bluetooth devices with Huawei Watch connected. OS Bluetooth functionality is bugged.
is...@google.com <is...@google.com>
vi...@google.com <vi...@google.com>
vi...@google.com <vi...@google.com>
ta...@gmail.com <ta...@gmail.com> #575
@fl, how did you get a refund? Google is telling me to pound sand
ki...@gmail.com <ki...@gmail.com> #576
why would you transfer the call to phone, when someone is picking the phone on the watch. ? My calls picked on watch randomly shows up on watch or on phone. I have no confidence with the way it works. At times, I pick the phone on the watch to talk on the watch and it goes to phone, and then i have to struggle to find the phone. Why would someone design system like that. Once you have a watch defined to be capable and have bluetooth pairing set, either dont show the call on the watch if outside bluetooth/wifi range. If you show it, please let someone talk on the watch. Thats what is needed. If someone wants to transfer to headset, let him define in the settings to disconnect calls from watch or talk voice on the phone in the settings. This randomness - is not something one expects from this expensive devices.
ta...@gmail.com <ta...@gmail.com> #577
Half the time when I pick up from my watch, it goes to phone and vice-versa, or to another bluetooth device. Bluetooth routing is still broken.
au...@gmail.com <au...@gmail.com> #578
Hi. Just want to add to the nightmare. Holy sh*t. Pixel 2 XL, Huawai Watch 2.
If I answer a call on my phone, it defaults to the watch. When I receive a call I cannot, no matter what I do, (short of turning bluetooth off,) switch to a different type of audio (speaker, handset, other bluetooth) I use the audio drop down in call, and it does absolutely nothing. If I dial out on the phone, I can then switch the audio, but my watch makes a beeping sound every 3 seconds like call waiting or something and it PROGRESSIVELY GETS LOUDER. WTF?
Any progress on this Year+ old bug??
Exact problems as OP described.
Lovely to see the priority is 0. Really boosts confidence.
(Sorry for the sarcastic demeanor, this issue is just driving me up the wall.)
If I answer a call on my phone, it defaults to the watch. When I receive a call I cannot, no matter what I do, (short of turning bluetooth off,) switch to a different type of audio (speaker, handset, other bluetooth) I use the audio drop down in call, and it does absolutely nothing. If I dial out on the phone, I can then switch the audio, but my watch makes a beeping sound every 3 seconds like call waiting or something and it PROGRESSIVELY GETS LOUDER. WTF?
Any progress on this Year+ old bug??
Exact problems as OP described.
Lovely to see the priority is 0. Really boosts confidence.
(Sorry for the sarcastic demeanor, this issue is just driving me up the wall.)
ta...@gmail.com <ta...@gmail.com> #579
@au, same exact behaviour. The beeping used to only happen when navigation is going but now happens all the time (wtf indeed)
I'm on Pixel 3 now and I just don't get ANY sound from the watch. Turning the feature off until they fix this crap.
Google keeps indicating they want to try to make wear legit, but with behaviour like this on their OWN FLAGSHIPS I'm not impressed.
I'm on Pixel 3 now and I just don't get ANY sound from the watch. Turning the feature off until they fix this crap.
Google keeps indicating they want to try to make wear legit, but with behaviour like this on their OWN FLAGSHIPS I'm not impressed.
ra...@gmail.com <ra...@gmail.com> #580
Just be prepared to keep the featured turned off. The problem is with the Pixel line of phones -- not the watch. It was present in the Pixel 2 line and apparently it is present in the Pixel 3 line as well. I can tell you it is not Wear OS. I have tested on Samsung and other phones and the feature works fine and as intended. I am currently using a Ticwatch Pro Wear OS watch paired with a OnePlus 6T and everything works as it should.
Something is wrong with the Pixel Bluetooth stack. This has been discovered months and months ago. Google has done nothing about it, except grant refunds to those who cite this thread and explain the issue in detail.
If you want your Wear OS watch to be able to take calls over bluetooth, you will not be able to with a Pixel phone. It is that simple.
Something is wrong with the Pixel Bluetooth stack. This has been discovered months and months ago. Google has done nothing about it, except grant refunds to those who cite this thread and explain the issue in detail.
If you want your Wear OS watch to be able to take calls over bluetooth, you will not be able to with a Pixel phone. It is that simple.
ra...@gmail.com <ra...@gmail.com> #581
I will also add that pairing a Samsung Watch (which runs Tizen OS) to take calls over bluetooth with a phone from the Pixel line does not work either. Again, this is a Pixel problem, not a watch problem. Specifically, the problem is how the Pixel phone handles switching from one audio source to another.
qu...@gmail.com <qu...@gmail.com> #582
Just got a ticwatch pro. The delay from picking up on phone to being able to use it was 25 seconds
ma...@gmail.com <ma...@gmail.com> #583
Sheesh. I CANNOT BELIEVE this is still ongoing! Simply unbelievable. I'm so glad I ditched that phone.
On Dec 2, 2018, 8:38 PM, at 8:38 PM, buganizer-system@google.com wrote:
On Dec 2, 2018, 8:38 PM, at 8:38 PM, buganizer-system@google.com wrote:
cs...@gmail.com <cs...@gmail.com> #584
Purchased Ticwatch pro and I have same issue. Takes a good 10-15 seconds for watch to ring and its hits or miss on if it answers, biggest issue though is my wrist vibrating and singing and nothing on the screen. HOW is this still an issue? Does Google not care about Wear OS anymore? Did I waste my money?
cs...@gmail.com <cs...@gmail.com> #585
Edit: I am on S8 everything updated, I tried wiping, resetting, clearing adjusting same as others with no results.
mo...@gmail.com <mo...@gmail.com> #586
Hi all.
I have a Huawei P10 Plus phen and a Huawei Watch 2. I am experiencing many issues with calls and SMS not being notified to my phone.
I have lived with it for months, but yesterday I finally got fed up and decided to do something about it.
1) I 100% reset my watch back to factory defaults. Surprise, surprise everything worked again.
2) Overnight my watch did some OS updates, and now I am back to the same issues I had previously.
Note: I did nothing to my mobile - so that takes the Phone out of the equation for the source of the issue.
The biggest visible difference between last night and this morning is that the "Play phone voice call on watch" setting is no longer visible under Connectivity.
So for me, this points be as the root of the issue being the OS update removing this feature.
I also took screenshots of versions, etc just after the reset and again this morning when I noticed the issues. Will attach shortly.
I have a Huawei P10 Plus phen and a Huawei Watch 2. I am experiencing many issues with calls and SMS not being notified to my phone.
I have lived with it for months, but yesterday I finally got fed up and decided to do something about it.
1) I 100% reset my watch back to factory defaults. Surprise, surprise everything worked again.
2) Overnight my watch did some OS updates, and now I am back to the same issues I had previously.
Note: I did nothing to my mobile - so that takes the Phone out of the equation for the source of the issue.
The biggest visible difference between last night and this morning is that the "Play phone voice call on watch" setting is no longer visible under Connectivity.
So for me, this points be as the root of the issue being the OS update removing this feature.
I also took screenshots of versions, etc just after the reset and again this morning when I noticed the issues. Will attach shortly.
mo...@gmail.com <mo...@gmail.com> #587
Screen shots I mentioned attached, in summary
Google Play Services 11.9.11 (534-186244031) - [Factory Reset] WORKS
Google Play Services 14.7.99 (050300-223214910) - Does NOT WORK
All other settings and/or versions are unchanged between working & not working
Google Play Services 11.9.11 (534-186244031) - [Factory Reset] WORKS
Google Play Services 14.7.99 (050300-223214910) - Does NOT WORK
All other settings and/or versions are unchanged between working & not working
rm...@gmail.com <rm...@gmail.com> #588
Both the phone and watch are a factor in this issue, I think. The phones likely have a similar Bluetooth hardware and software (driver) to that found in the Pixel line of phones.
Also, only 10 more days until it's officially one year from the creation of this post. We should give Google a "Participation Award"
Also, only 10 more days until it's officially one year from the creation of this post. We should give Google a "Participation Award"
ss...@gmail.com <ss...@gmail.com> #589
In addition, and not knowing if it's been mentioned, I cannot use speaker phone when play calls on watch is activated. Tic2qtch e on both an original Pixel and now a pixel 3xl.
ss...@gmail.com <ss...@gmail.com> #590
In addition, and not knowing if it's been mentioned, I cannot use speaker phone when play calls on watch is activated. Tic2qtch e on both an original Pixel and now a pixel 3xl.
an...@gmail.com <an...@gmail.com> #591
This is still not working one hundred percent. Half of the times the name of the person does not show de on the my Huawei Watch. Can someone please assist?
Cheers
Cheers
ka...@gmail.com <ka...@gmail.com> #592
I too am having issues with text notifications and hearing the other person when receiving calls. On the other end the person just says that it will ring indefinitely. Have to hang up and call back. Only when the smart watch is on or Google voice is installed. Both together makes for some bad days if missed notifications and calls.
el...@gmail.com <el...@gmail.com> #593
Just installed everything fresh after a factory reset and this issue is effecting my Wear24 updated to android wear version 2.20 and nexus 5 phone. Audio plays from the watch but the mic doesn't pick anything up.
Seems this issue has been unfixed for a year? Please google, i'm considering buying a pixel 3 but this poor support is not doing much to win me over.
Happy new year!
Seems this issue has been unfixed for a year? Please google, i'm considering buying a pixel 3 but this poor support is not doing much to win me over.
Happy new year!
ma...@aim.com <ma...@aim.com> #594
Note 8 with 9.0 Pie, Wear 24 with 2.23.0.238044309 and OS 7.1.1. I have all the Verizon LTE stuff turned off. When making a call from the watch, I can hear the audio (but at a very poor, almost unusable quality) but the microphone does not work. Seems like this issue has been around for over a year now. Just bought this watch expecting to make calls with it, quite upset that doesn't work right now. Really hoping this gets fixed...Happy to provide more info if needed.
ta...@gmail.com <ta...@gmail.com> #595
Still awful bluetooth call handling on the watch, all this time later. Half the time it barely rings before the caller hangs up. Still can't reliably switch between handset/speaker/watch.
er...@gmail.com <er...@gmail.com> #596
I have the exact same problem. Pixel 2 XL and Huawei watch 2.
da...@gmail.com <da...@gmail.com> #597
Was about to finally get a smartwatch! ...And I guess I'll just wait some more year. BTW, I'm using the Mi Band 3 for over a year and calls are received right at the same time. Of course I can not answer but at least I get insta-notification. Just sayin'.
es...@gmail.com <es...@gmail.com> #598
The same for my Ticwatch PRO. Please fix...
er...@gmail.com <er...@gmail.com> #599
#598 I finally bought a Ticwatch PRO and I don't have this problem anymore. Check if your watch has the latest version available.
es...@gmail.com <es...@gmail.com> #600
#599 Very strange, I have the most new firmware. Wear OS 2.8 main app 2.26.0.260128045. Which locale do you use, English?
er...@gmail.com <er...@gmail.com> #601
#600 I have the same versions as you and my phone is set to English as well.
rm...@gmail.com <rm...@gmail.com> #602
Just popping in to say it's been 18 months since I found this thread and the issue is still occurring, I can no longer take calls on my watch :( Not sure if the issue is due to the watch or the OS, but I would try to return your watch within the 30 days if the issue still occurs after attempted fixes. Be careful!
za...@gmail.com <za...@gmail.com> #603
Hi.
I have these devices and I am facing the same problem:
Huawei Watch 2 LEO-DLXX OWDE.180926.001.A1
POCOPHONE F1 9 PKQ1.180729.001
Shouldn't this bug be already fixed?
Why is it taking so long to solve it?
I have these devices and I am facing the same problem:
Huawei Watch 2 LEO-DLXX OWDE.180926.001.A1
POCOPHONE F1 9 PKQ1.180729.001
Shouldn't this bug be already fixed?
Why is it taking so long to solve it?
aa...@gmail.com <aa...@gmail.com> #604
Optional
br...@healthnet.com <br...@healthnet.com> #605
When my watch (Fossil Gen 5) is connected to my Pixel 3a and my Pixel is connected to my car, when I get a phone call no audio comes through my car.
ar...@google.com <ar...@google.com>
fi...@google.com <fi...@google.com>
ab...@gmail.com <ab...@gmail.com> #606
thread started back in 2017 and now 2019.. still same issue persists.. shame on google and its development team.. i am using fossil Q smart watch bought for 300$.. no use of money because of google wear OS..
cc...@google.com <cc...@google.com> #607
Our Engineering team is still working on this issue. We will provide more updates as they become available.
ax...@gmail.com <ax...@gmail.com> #608
I had to finally disable calls on watch ( the main reason I upgraded from a lg g watch) because they are unreliable , slow to appear , and the missed call notification , clear the one on phone . Practically they're a complete disaster , and the fact that google doesn't give a f*ck since 2017 when it first appeared makes me wonder if there's any future for wear os . Actually my lg g watch upgraded via custom rom to 2.0 wear os works exactly the same way as my ticwatch E that I bought for calls on watch
an...@gmail.com <an...@gmail.com> #609
I own a Google Pixel 2 and the original Huawei Watch and most of the times the name of the person calling me does not appear on the watch. I just updated the Android version on the smart phone to android 10 but the issue remains.
vi...@google.com <vi...@google.com> #612
We recommend you to kindly take the latest update available and check the bug. If you still face the issue kindly share the bugreport.
tu...@gmail.com <tu...@gmail.com> #613
2019-10-01 11:13:56.134 9206-9206/com.example.myapplication E/AlarmReceiverDemo**: AlarmReceiverDemo**<<AlarmReceived---->>01-13-2019 11:13:56
2019-10-01 11:13:56.140 9206-9206/com.example.myapplication E/AlarmReceiverDemo**: AlarmReceiverDemo**<<AlarmReceived---->>01-13-2019 11:13:56
2019-10-01 11:13:56.140 9206-9206/com.example.myapplication E/AlarmReceiverDemo**: AlarmReceiverDemo**<<AlarmReceived---->>01-13-2019 11:13:56
tu...@gmail.com <tu...@gmail.com> #614
141812756, 141704937, 141726327, 141732094, 141740550, 141752057, 141752060, 141763650, 141763652, 141787476, 141796871, 141806632, 141812743, 141815359, 141815375, 141825192, 141826026, 141838005, 141838017, 141838115, 141838116, 141846881, 141861586, 141889121, 71010564
tu...@gmail.com <tu...@gmail.com> #615
71010564, 141889121, 141861586, 141846881, 141838116, 141838115, 141838017, 141838005, 141826026, 141825192, 141815375, 141815359, 141812743, 141806632, 141796871, 141787476, 141763652, 141763650, 141752060, 141752057, 141740550, 141732094, 141726327, 141704937, 141812756
Description
I'm having huge issues with "Play phone voice call on watch" on my Pixel 2 XL and Huawei Watch 2 (AW2.7) where apps (Phone, Duo, WhatsApp - anything that uses a BT headset) freeze for 10-15s after making or receiving a call on the phone with the watch connected.
Looks like audio is auto-redirected to the watch when it shouldn't and watch isn't ready resulting in no audio/mic at all
Apps usually unfreeze (or not) after 10-15s and audio is then randomly routed to watch speaker or the handset speaker, but by that time most callers have already disconnected (cause neither mic nor speaker is working and they assume nobody is on the other side of the phone)
On top of that, changing the in-call audio output to speaker doesn't seem to work or persist and Android is trying to route the next call to the watch again - which results in freezes again.
Only solution for now is disabling the feature (which disables the "Phone calls" BT capability on the watch) - but this was one of the crucial features I bought this watch recently for. Could we please try to work this out?
Below is some extra info from a post I made on one of community forums:
---
How I understood it would work:
Calls made/answered on the phone would be heard on the phone (or it would at least remember the last selection)
Calls made/answered on the watch would be heard on the watch
I would be able to transfer the call between my phone/watch (over BT) during the call the same way I do for other BT headsets/speakerphone
How it works for me:
Calls made from the watch work fine and are heard on the watch
Calls made from the phone don't work fine:
The Phone app will lag and freeze for ~5-10s during which nothing is heard on any speaker. When it unfreezes time counter jumps to correct time (e.g. 0:07) which confirms the call was actually underway
OR it won't lag but nothing is heard on the phone /watch speaker anyway, regardless of which was auto-selected by Android
When this happens, switching outputs doesn't work: Watch (BT), Speaker, Phone's headphone - there's only silence on all of them
When this happens, the default device in the Phone can indicate either a BT device or the phone speaker, but both remain silent.
Sound will come back after 10-15s on either watch or phone. If on the phone, there's a "pop" in the earphone right before it comes back
Receiving and making calls in Duo, WhatsApp, Hangouts results in the same - lagginess and no audio at all until I disconnect the watch and make the call again. Apps will also freeze for about 5-15s every time I try to switch to BT audio (no sound at all) and then unfreeze and switch back to phone audio
Android 8.1.0, Pixel 2 XL
Huawei Watch 2 Sport 4G
Android Wear: 2.7.0.178645119
Play Services: 11.9.51
Android: 7.1.1
Security patch: Aug 1, 2017