WAI
Status Update
No update yet.
Comments
ad...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android bug report (to be captured after reproducing the issue) For steps to capture a bug report from Phone, please refer:
Steps to capture bugreport from the Wear device:
On you Android phone, following the instructions in this doc, under the section ‘Instructions on your companion phone or tablets (Android)’.
Launch the ‘Android Wear’ app on your phone or tablet. Tap on the three vertical ellipsis on the top right hand corner of the screen and click on “Report Wearable Bug” to capture a bug report from the watch.
On the watch, you will observe a notification card with the text “Bug report #X is being generated”. It can take up to 20 minutes for the bug report to be generated and transferred to your phone.
Once the bug report is done, the notification card on the watch changes to “Bug report #X captured” and you will receive a notification on the phone that reads “Wearable bug report finished. Tap to send." Tap on this notification and email the bug report to a pre populated email address.
Note: Please avoid uploading directly to the issue using attachments. Please upload to google drive and share the folder to
ad...@google.com
Steps to reproduce:
1. Install any custom watch face on the pixel watch
2. Set it to be used on watch
3. Set AOD on, without tilt to wake
4. Let the screen go to AOD
5. Cover the screen or let bright light on it
Expected: brightness changes accordingly to the light
Result: screen brightness stays at the level when watch went into AOD
On stock faces this works correctly.
1. Install any custom watch face on the pixel watch
2. Set it to be used on watch
3. Set AOD on, without tilt to wake
4. Let the screen go to AOD
5. Cover the screen or let bright light on it
Expected: brightness changes accordingly to the light
Result: screen brightness stays at the level when watch went into AOD
On stock faces this works correctly.
ca...@gmail.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ke...@kbrd.pw
Hoping for an update sometime in 2024! Can't wait!
he...@gmail.com
This should have an extremely high priority, please fix this soon!
dp...@gmail.com
Checked, This issue is still present on pixel watch January update
mi...@gmail.com
hello?
rn...@gmail.com
Everything is assigned and nothing gets fixed. And you are wondering why the watch is a flop
ga...@gmail.com
Sad to see that this issue isn't being worked on. Rendering useless the 3rd party watch faces. :/
No fix in February update for anything but some sec issues :/
"What’s Included
The February 2023 software update includes the latest security patches for Pixel Watch users."
Nothing else
No fix in February update for anything but some sec issues :/
"What’s Included
The February 2023 software update includes the latest security patches for Pixel Watch users."
Nothing else
gn...@gmail.com
I love google
ma...@gmail.com
Still nothing
ch...@gmail.com
You awake yet? Do like to fix some bugs? No? Ok.
xe...@gmail.com
It's an annoying bug, for me rendering all 3rd party watch faces mostly useless.
Hopefully they fix it soon
Hopefully they fix it soon
ev...@gmail.com
so you added a useless feature (rotating the crown to activate the display.) but still didnt fix THIS bug. wow.
ph...@gmail.com
I still haven't got the march update to validate this, but sounds rather lame if it still isn't fixed. Going to test as soon as this slow roll out gets to my watch
ti...@gmail.com
got the update and its not fixed
sa...@gmail.com
Got the update, still same behavior on the march update.
AOD auto brightness is non existent on custom watch faces
AOD auto brightness is non existent on custom watch faces
he...@gmail.com
Just sold my Pixel watch.
el...@gmail.com
April update, still not fixed. Very annoying
kw...@gmail.com
It's been 4 months. Are you actually serious?
to...@gmail.com
It is really disappointing that great watchfaces have been released but are rendered useless because of this bug in AOD mode.
You see them for a bit and then they turn to dark because they do not adjust.
We are forced to only use the bland stock watchfaces because of this issue.
Please consider addressing this in this century?
4 months - I guess there is plenty of time left.
Thank you for your consideration.
You see them for a bit and then they turn to dark because they do not adjust.
We are forced to only use the bland stock watchfaces because of this issue.
Please consider addressing this in this century?
4 months - I guess there is plenty of time left.
Thank you for your consideration.
ed...@gmail.com
still not fixed. I know you are very busy doing absolutely nothing but the aod update function is broken since last update in fitness training app.
jo...@gmail.com
this also happens with official watch face studio app for windows btw. What is this?
kb...@gmail.com
Very sad that this is still not fixed. Stock faces don't have enough features or customizability, and no 3rd party faces are readable if using always on.
ch...@mnonki.com
maybe with PW2
lb...@gmail.com
Last update says "fixed bugs". Would you mind explaining to your customers exactly WHAT bugs you are pretending to have fixed? It's certainly not those reported directly from your customers MONTHS ago
ya...@gmail.com
Updated, didn't help with this issue. Still present.. Making third party watch faces meaningless still after half a year of reporting the issue.
lb...@gmail.com
Can we get an ETA on the fix please? Thanks. Don't say Pixel Watch 2...
yi...@gmail.com
Any danger of an update on this?
le...@gmail.com
July update, still no fix:/
lo...@gmail.com
Still nothing..maybe with wear os4?
[Deleted User] <[Deleted User]>
> Can we get an ETA on the fix please? Thanks. Don't say Pixel Watch 2...
Ouch...
But, has anyone tried with the PW2?
Ouch...
But, has anyone tried with the PW2?
ga...@gmail.com
Having just bought a PW2, I have also discovered the bug. So nope, not fixed on the PW2.
ch...@gmail.com
It's also there on pixel watch 1 October update, wearos version 4... **Facepalm**
Google this is just plain lame now
Google this is just plain lame now
al...@gmail.com
Pixel watch 2, can confirm this is also an issue. Please fix
wa...@gmail.com
this is a joke lol. Glad I moved away from this watch.
ba...@gmail.com
Same issue (Pixel Watch 2)
ad...@gmail.com
Fixed?
vk...@me.com
No fix
jm...@gmail.com
Yikes this is now a year old and im on the pw2 and still the bug is still a thing hope it gets fixed
ky...@gmail.com
I think that most people don't even notice this problem because there aren't that many users who complain about it. Unfortunately.
da...@gmail.com
Well, it's one of the highest voted open bugs here in the tracker. More likely less people use custom watch faces, and probably many just don't care.
It's Google's lameness and noticeable inability that it's still not fixed.
Google is a software company, it's rather a double facepalm issue on their shame list for Google devs
It's Google's lameness and noticeable inability that it's still not fixed.
Google is a software company, it's rather a double facepalm issue on their shame list for Google devs
lu...@gmail.com
It absolutely, drives me crazy. I want to use a custom watch face but I can't because the screen doesn't auto adjust. Don't say you're going to fix things and then not fix it after a year+
la...@gmail.com
I'd like to request a comment from Google if and when this is going to be fixed.
lb...@gmail.com
Maybe it's simply not possible to fix this problem because the watch faces interfere too deeply with the system's interior. In this condition, the dials are no fun and anyone who has no idea about this topic blames the dial developers, who get bad reviews as a result.
sn...@googlemail.com
Sure it can be fixed. It works just fine in Samsung watches. Google is lame here for over a year now
re...@gmail.com
I need this fixed too.
an...@gmail.com
still not fixed? lmao
pm...@gmail.com
So sad to see another google product not living to it's full potential. ☹️
co...@gmail.com
Please fix this.
an...@gmail.com
Fix pls.
ku...@gmail.com
Please fix...
rt...@gmail.com
Comment has been deleted.
ml...@meta.com
I'm getting this too (PW2, third-party watchface). Sometimes the screen is so dark that it seems to be off. Even large bold white text is rarely readable.
tj...@gmail.com
Issue also applies on Wear OS 5 with PW2 and PW3.
id...@gmail.com
Still the same issue also for GW7.
Please find a way to fix it
Please find a way to fix it
to...@gmail.com
Thank you for reporting this issue. We have a fix rolling out in an upcoming release.
je...@gmail.com
Thanks for handling this so quickly #
jo...@gmail.com
"in an upcoming release"...well not in March anyways. Maybe in three months. I mean it's not that the bug was reported almost 2.5 years (!!!) ago, was it?
ce...@gmail.com
Is there no release yet in March?
Or is it the fix still missing from that?
Or is it the fix still missing from that?
ed...@gmail.com
March release is available, still no fix though...
to...@gmail.com
on Pixel Watch 3, I tried 4 different custom 3rd-party watchfaces, all of them with adaptive brightness, only adjusting brightness every 1 minute.
This issue has been there for 3 years since pixel watch 1......
This issue has been there for 3 years since pixel watch 1......
ha...@gmail.com
Please bring this back! And the calendar when clicking on the date. I used it all the time.
tr...@gmail.com
I'm holding off updating because I heard of this. Sad to see it is true
jd...@gmail.com
*sigh*
ku...@gmail.com
Yep, we want it back. Thanks
sl...@gmail.com
Bring it back
bo...@gmail.com
please bring back the ability to open alarms WITHOUT having to open menus to click on it -
ca...@gmail.com
Please bring it back. Makes no sense to remove such a useful shortcut.
ca...@madeby.cam
Another vote to bring it back. This is literally the only update from Android that has ever reduced OS functionality.
en...@gmail.com
+1
[Deleted User] <[Deleted User]>
Please bring it back. Why has this been marked as "Won't fix (Intended behaviour)"? Why is this intended behaviour? Please explain, or better yet just bring it back.
fo...@gmail.com
Why won't this be brought back... It was a useful feature.... In the new update clicking the time SHOULD open the clock - and the date the calendar. There is no reason for this not to be kept for continuity??
pa...@gmail.com
Hey google guys, wanna hint? Just create a new task with this feature like it is your idea, people happy, you get raise, aight?
vi...@gmail.com
Give me my entire classic UI back. I need to click to many buttons to accomplish what should be 2 clicks.
jo...@gmail.com
Would trade any and all improvements made in this update for this one feature back
pa...@gmail.com
Used this feature daily and today I've reached the point of annoyance to actually bother commenting. Please update with this feature back, no idea why you'd remove something so intuitive for a multiple step approach.
ja...@jackvalentine.org.uk
This may be "by design", but that doesn't stop the design from being terrible. There is no logical reason to remove this function, which worked well and was very convenient. It wasn't in the way of anything else. The only result of removing it is to upset the people who used it and liked it.
So the real question here is: Why do you hate us so?
So the real question here is: Why do you hate us so?
jd...@gmail.com
No point in making an argument. Bullshit apple like move.
sw...@gmail.com
Please reconsider and add this back to android. It is silly not to be able to click on the time and get time related options. Seeing the alarm from the home screen is seriously useful
no...@gmail.com
perhaps replying to this thread every day and starting duplicate threads should also be intended behavior. Sure, you'd rather we didn't do that, but oh well, now you know how your user base feels. :)
tr...@gmail.com
Bring it back.
he...@gmail.com
We can now press on the At A Glance date to go directly to Calendar in S3B1.220218.004. I think that's good enough. :)
[Deleted User] <[Deleted User]>
DISAGREE strongly with previous comment. NOT GOOD ENOUGH
ca...@madeby.cam
I don't even know where to find "At A Glance" date. If it's not as simple as tapping the time in the status bar then it's not good enough.
ca...@gmail.com
Agreed. Please just bring back the original shortcut
zm...@gmail.com
#87 I do not mean to be rude, but how is being able to open the calendar from a widget a substitute for being able to open alarms by tapping the time in the notification panel from anywhere?
he...@gmail.com
@
The At A Glance widget is the default widget that's natively integrated into the Pixel Launcher. It's activated by default as well.
You can tap on the date on the home screen from the At A Glance widget (located at the top of the home screen) to quickly get into the calendar. It's really not that hard and very quick to get there.
I still think the old method was smarter and quicker. But the current method is, in fact, good enough.
The At A Glance widget is the default widget that's natively integrated into the Pixel Launcher. It's activated by default as well.
You can tap on the date on the home screen from the At A Glance widget (located at the top of the home screen) to quickly get into the calendar. It's really not that hard and very quick to get there.
I still think the old method was smarter and quicker. But the current method is, in fact, good enough.
ca...@madeby.cam
Dear "he...@gmail.com", I think you may have the wrong thread.
Nobody here is talking about accessing the calendar.
The shortcut we want back allows us to access the clock and alarms.
The clock and calendar are vastly different things.
Nobody here is talking about accessing the calendar.
The shortcut we want back allows us to access the clock and alarms.
The clock and calendar are vastly different things.
he...@gmail.com
@
li...@gmail.com
terrible design choice
rd...@gmail.com
No it wasn't. Look, don't just say something is changed when nothing was
done. The original answer to the ticket was that removing a feature was
done as intended. I totally forgot about it until now, and now I'm
bothered.
On Thu, Mar 24, 2022, 11:06 PM <buganizer-system@google.com> wrote:
done. The original answer to the ticket was that removing a feature was
done as intended. I totally forgot about it until now, and now I'm
bothered.
On Thu, Mar 24, 2022, 11:06 PM <buganizer-system@google.com> wrote:
da...@gmail.com
Add the shortcut back
we...@gmail.com
Totally agree as a UX Designer that this was not a good move for your user experience. You had something that was used and loved and then you removed it. You have the code and the knowledge to put it back in place.
al...@gmail.com
Very disappointed that you removed the most important function on my phone. It redundant to add a time widget and have the time displayed on the top bar.
Bring this feature back. It's ridiculous that it was removed in the first place.
Bring this feature back. It's ridiculous that it was removed in the first place.
n....@gmail.com
Awful UX choices are all over android 12. Please, bring it back.
il...@adevinta.com
Please bring it back, such a USEFUL feature that I used multiple times daily!
mi...@gmail.com
and it is literally 1 line of code, unbelievable
co...@gmail.com
Why, after almost a year of continual and unique posts requesting reinstating the "button", is this still in Won't Fix status? It's not a Bug - it's a downright liberty that so so reflects so much of Google's lacklustre responsiveness to customers' requests and very reasonable observations.
jo...@gmail.com
PLEASE bring this back, I still haven't gotten used to the 'workaround' a YEAR LATER even with using it every day. The original design was so so so convenient
ge...@gmail.com
Is it really so hard to fix this. Nobody likes this change, just change it back already. It helped nobody at all to have changed this, but hurt so many. Why is Android 12 such garbage?
ge...@gmail.com
I'm still waiting for this issue to be resolved. I should be able to enter the clock app by tapping the clock displayed at the top of the screen in the notification bar.
ge...@gmail.com
I really hope Android 13 fixes this. That should be out in just a couple months, I imagine. Sure hope it brings back this essential feature. I should be able to enter the clock app by tapping the clock displayed at the top of the screen in the notification bar.
th...@gmail.com
I want this feature to exist forever
il...@gmail.com
Bring it back please
Ar...@ascension-external.org
Pls bring it back, its one of the futures I miss with the new Pixel , its really good one used multiple times in a day for me.
rm...@gmail.com
Still a missing feature considered a bug or a failure of UX consideration. Waiting on Android devs to fix something they broke is unlikely to ever bear fruit. Sticking with v11 since it doesn't have this and other UX features broken.
ho...@gmail.com
removing this was stupid and makes me annoyed
an...@gmail.com
This change makes zero sense. It had to be decided by an engineer rather than someone who is responsible or user interface or accessibility. I am temporarily using a Pixel 2 until my new phone arrives and it is so nice having this little shortcut that is missing from the Pixel 4 I was using.
ma...@gmail.com
Another vote to bring back that feature
ti...@gmail.com
For the record I tracked down this thread because I thought I was going crazy...I knew I used to be able to do that! Bring it back please.
wr...@gmail.com
Fixed in A14 beta 3, thx!
co...@gmail.com
Hello Google! Any movement on these requests yet? For general consumption? I'm not playing with 14.3beta.
??
??
v....@gmail.com
confirming, works in v14beta3
ca...@madeby.cam
OMG it's back! Thank you Google for listening to us! ❤️
jo...@gmail.com
Thanks :)
tr...@gmail.com
Holy crap thank you
Description
- Build Number: google/redfin/redfin:12/SPB3.210618.013/7533405:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? Other issue
What steps would let us observe this issue?
1. Pull down notification drawer twice
2. Tap on clock
What did you expect to happen?
Alarms configuration to open
What actually happened?
Nothing
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
Moderate