IssueTracker

We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.

danalbert: didn't you already fix this?

i think https://android-review.googlesource.com/c/platform/bionic/+/2670156 (and associated stack) fixed this?

Yep. https://issuetracker.google.com/289419882 turned up a whole bunch of broken things. I wouldn't be surprised if there were more issues, but this one is already fixed.

The application available in playstore has version 2.1.7. Would it be possible to share 2.1.6 apk version of this app.

Also, share the screenrecord of the issue to meet the exact current output.

As per comment#1,

is not build with the jetpack library (using the old support library)

Can you also clarify which support library your app is using ?

Hey,

Sure thing, please find the 2.1.6 release APK attached.

And you'll find all the dependencies here: https://github.com/benoitletondor/PixelMinimalWatchFace/blob/8800fe356bbe161792fd607aa5147e74f35a1257/android/watchface/build.gradle (it's on the commit of the 2.1.6 release)

Hello, I'm also affected, that's a major bug, can you bump its priority, please?

We have looked into the issue and would like to inform that the screen is only turned off when the device is offbody. When the device is offbody, the watch will turn off the screen after a fixed amount of time to save power. Hence this is working as intended.

@comment#13 this is totally wrong. Please reopen this issue and do a proper testing.

The reproduction steps are easy:

• Install & use a watch face using the affected libraries, you have one from me on that issue
• Wait 10 to 15 mins with the watch on your body, normally
• See that screen turned off

@comment#13 I don't believe that you've tried to reproduce the issue by setting a third party watch face NOT made with Samsung's Watch Face Studio but WITH CODE, because I also see the same on my Pixel Watch where only the stock Watch Faces stay on all day long when always on display is on.

One thing: I don't think the delay until unwanted turn-off is always 15 minutes. Sometimes, it seems longer, and possibly less at other times.

To add some context, we were unable to reproduce the issue at the time. Today, two of us tried again with the APK Benoit shared, and only one of us were able to reproduce it.

In future, a bug report would be helpful since it's not always possible to reproduce 100% of the time. Will re-open for the time being while the bug report is analysed - if you do have additional bug reports, those could be helpful too.

Thanks Ataul

You should also be able to reproduce with this watch face app: https://play.google.com/store/apps/details?id=com.ustwo.watchfaces.timer

Oh, I didn't notice that… I hope some folks at Google care about this. It's a major bug for the Pixel Watch, it should probably be P1 or P2 rather than P3.

I hope this issue is assigned to the right person 🙏🙏🙏

Hey folks, we think this issue was caused by unreliable device idle state handling - the result was that sometimes the device would report that it's off-body and begin the ~15 minute countdown.

The reason we haven't been able to reproduce it consistently is because this bug has already been fixed in our internal build, which some of us are currently testing (running on our devices). This should begin rolling out to Pixel Watches in early December. Thanks for your patience.

• Ataul

Hey @comment#26 can you give us some insight about why it would affect only third party watch faces and only old libraries? It does seem a little off

Who gets the 100€ if it's actually fixed on the next update in early December @comment#32?

Thanks for your patience everyone. I'm sorry to say that the issue was not fixed as I stated in #26; it turns out that there were two different issues with similar behavior (the screen turning off) and only that one was fixed.

The other issue (this one) affects Jetpack-based watch faces too, and has also been fixed (I tested it with the APK from #8 myself) however it won't roll out until sometime early next year for Pixel Watches. For Fossil, I don't have visibility on that - please reach out to your technical account manager at Google (I've let them know about this bug).

- Ataul

Thanks for the update and the follow-through Ataul!

Regarding the timeline, I hope the users I'll get in the holiday season won't notice the issue too much until it's deployed to Pixel, Fossil, and other watches running Wear OS 3.

Many thanks for the update Ataul, really appreciate it

Hey,

So I don't have access to the update yet as I'm in Europe but I got this message from one my users:

After the Pixel Watch December update the AOD seems to time out and turn off after about 10 minutes. No issues with it prior to the update.

I had a workaround in place that was working to prevent this but it seems that not only december update didn't fix anything but made things worse?

@at...@google.com @comment#41 it would be great to have some updates on this as this is becoming a serious issue.

but it seems that not only december update didn't fix anything but made things worse?

Benoit, can you add details about your workaround and provide a bug report from the device? It's not expected that the December update would have fixed this issue - as mentioned in comment#41, this is rolling out early next year.

@comment#54 I've been able to get the update, it's installing right now on my Pixel Watch and I'll be able to test and see if there's any kind of regression. I'll keep you posted.

As for the workaround, it's simply using a wakelock every 10 mins to avoid letting the screen turn off. It's ugly and when I opened the bug report almost 3 months I didn't expect to keep it for that long.

@comment#54 I can confirm a regression in December update, my workaround doesn't work anymore (I'll try to see why, didn't investigated yet).

@comment#54 So the regression here seems to be that the screen turns off not after 10 mins like before but after 5 now.

God I want to apply at Google, get hired, yell at the persons responsible for this mess, quit and go back to my life having to deal with WearOS bugs that wouldn't have disappeared just because I yelled at those poor guys.

The inflexibility of the system updates process is a Huge problem.

Apple would take a few days to fix such a noticeable issue, skipping past the normal update schedule.

Hope this makes it to the ears, and brain, of all the right people at Google, before it's too late and people like me who invested months of work just give up and move on past contributing to the Wear OS ecosystem (which Android needs since competition also has watches).

May the readers of this message stress that to the people controlling the system updates traffic lights! 🙏🏼🙏🏼🙏🏼🙏🏼🙏🏼

@comment#54 Can we get a clear update about:

• Is the regression from 10 to 5 minutes explained on Google's side and understood technically?
• Is the fix promised for "early next year" really fixing the issue?

I think it's ok for bugs to happen but please give us a clear status and a concrete timeline here.

Hello folks,

I got a workaround that I've been testing successfully for a few days.

Hopefully, you can apply those to your Watch Faces before your user-base grows in several days amid the Christmas holidays season.

Here's the full gist: https://gist.github.com/LouisCAD/0a4d40278e8572a78d6b90303681e0ba

All the best!

Maybe the dev actually cares? If you don't tell them, you can't know.

This code is only for Watch Face code, but you might be able to make your own always running app that applies a similar approach with a recurring short WakeLock like I did.

Sure, but now, they have a solution.

Well weirdly enough I can also say this bug do affects jetpack watchfaces (I'm testing on mine on a branch where I migrated to the new APIs). Which has 2 consequences:

• It has never been confirmed by Google eng. so far so I have doubts they are actually aware of that ( cc @comment#54 )
• It makes me wonder why stock watch faces aren't affected by this bug. Is there actually any third party watch face not affected?

It would be great to have a clear update from Google, thanks!

There's no new news outside of the information in comment#41.

The other issue (this one) affects Jetpack-based watch faces too, and has also been fixed (I tested it with the APK from #8 myself) however it won't roll out until sometime early next year for Pixel Watches.

Hey Ataul, thanks a lot for making this clearer to me, sorry I missed that part in your message.

Let us know when you have a more precise timeline please, thanks!

Hey, just saw https://support.google.com/googlepixelwatch/thread/196523519/google-pixel-watch-update-january-2023?hl=en

Does this release fixes this issue?

Yeah I will run some tests today too, my expectations are quite low now that I've seen what the December patch has done + we didn't get any message from a Googler recently which isn't a good sign.