Bug where display always shows tile view screen, not clock

[Spiced]

My Google Nest Hub 2nd Generation has been acting weird for a few weeks now.  I have one in the living room that behaves normally.  

The display on my nightstand, however, constantly displays the hub/control style view with tiles for my alarms, lights, weather and other suggestions, but not the basic clock display.  I have to swipe from the left bezel as though i'm closing an app to get to the clock or weather frog.

Even after swiping away, it returns to this more condensed "Your evening" screen within a few minutes.  I didn't mind when it would switch to this screen if i entered the room briefly, but it is always on now and the clock is tiny on this display.  I have gone through the settings, turned weather frog off and on, changed the photo display settings, and the entire display reset at one point.  I also turned off the ultrasound sensing and cleared the space around the display.

I haven't seen anyone else with this issue or any solutions.  All the "display  wont show clock" reports seem to be about seeing nothing or a broken display.  mine simply goes one step too far at all times.

Anyone else experiencing this behavior? It looks almost like the new pixel home control style screen but this is not a new device, nor have i seen any updates about this...

[stelthy77]

I was experiencing this on most of my hub displays.  A reboot via the app cleared it for me. I know this sounds cliché, but I don't see in your post that you have tried this... Have you rebooted the display?

[Spiced]

Ah I apologize - where I stated "entire display reset" I meant this as a full factory reset.  So more than a normal reboot, though I had also performed several reboots prior to the factory reset.  Problem is still ongoing and unpredictable.  I am thinking there may be a hardware issue with the sensors even with ultrasound sensing off...

Today I am swapping my displays to see if there is an issue with location,  or if this is truly device specific.

Thanks for your reply!

[Alex_S]

Hi everyone,

Thanks for the help here, @stelthy77.
 

@Spiced, I’m sorry to know about what’s happening on your Google Nest Hub 2nd gen. Let’s further look into it. How’s it after swapping their locations? How did you do the factory reset? Kindly provide the software/Fuchsia version of your Google Nest Hub 2nd gen. Swipe up from the bottom of your display > Settings > Device information.

I’ll look forward to your response.
 

Regards,
Alex

[Spiced]

Thanks for your response, Alex!  

The unit was factory reset using the volume buttons on the back of the nest hub.  It was also soft reset/rebooted through power cycles. 

Since swapping my two displays, I have had no issues.  I am assuming it was something with the proximity sensing.  The odd thing is that the behavior continued when I turned off ultrasonic sensing and made sure there were no items near the display.  I checked for damage and can't think of a time it has done anything other than sit stationary on my nightstand.

But as I said - no issues after swapping! The clock/weatherfrog show as a default and I get the new evening/hub view only upon entering the room; unless I tap the display.  The unit that was staying on the hub style screen now also works again. Once moved into the living room, where it sits on a shelf more than 10 feet from any other piece of furniture, it is working fine.  I should note that my nightstand it was set to the back of an 18 inch table, which is 2 inches from my bed, where I sleep on the side opposite (about another 25 inches away). So about 45 inches of space between myself and the hub.

Thanks again for the help, I feel as though my issue is resolved, though I wish I knew why the issue continued after ultrasonic sensing and gestures were turned off...

[Spiced]

I did forget to share the unit was on system firmware version 10.20221207.2.100042. I hope that is the right firmware you were asking for!

[Alex_S]

Hi there,
 

I appreciate the update about your Google Nest Hub 2nd gen device, and I’m glad that everything is working fine. I don't have any information to share why that happened, but I suggest that you send feedback so engineers can review the “crash reports” and prevent it from happening again. 
 

Please let me know if you have other questions or concerns as I will be locking this in 24 hours if I won't hear back from you again. Feel free to start a new thread and we'll be happy to help.

Warmly,
Alex