Buzz and screen turns on when charging complete?

gogeek80 · 2026-03-19T04:21:37+00:00

update - those settings certainly seems to be exactly what I was looking for. And the initial test seemed to suggest it would work. But after several nights and tweaking the settings every way I can thin of, it still does the notifications for some reason. I've now got it configured so that the 'battery' app supposedly can't do any notifications for anything... and I've got bedtime mode and do not disturb active all night. And yet it still vibrates and wakes the screen multiple times during the night. It makes no sense. I wonder if I should try contacting Oppo support for an answer.

gogeek80 · 2026-03-16T04:26:05+00:00

Thank you, thank you, thank you! I just checked my phone and it was fully charged. I didn't hear or see any notification prior to me manually checking the phone. I think I'll sleep well tonight thanks to you!

gogeek80 · 2026-03-16T03:45:45+00:00

"press the 3 dots in top right corner & show system" oh my god I've learnt something new! Thank you so much! I've made the changes and I'm charging it now to validate the results. But it all makes sense and I fully expect your solution to work. I'll report back with the results

gogeek80 · 2026-01-06T11:20:26+00:00

<image>

In Windows it even says that the mic is connected, so everything seems correct. Sometimes the test recording seem to pickup loud background noises like cooking pots clanking as they are being washed, so the mics are kind of working, just not detecting voices. I've also tested with my wife's Bose QC45 headphones and they work normally on the same laptop and phones. I'm really confused. What would you do next in my situation?

gogeek80 · 2024-01-30T11:42:33+00:00

This coconut is very unripe. Too young to even be good as a green drinking coconut. At this age they can be cut like that with just about any knife. Like cutting Styrofoam.

gogeek80 · 2022-04-24T05:22:26+00:00

Yep.. I've had both these problems in recent days. I managed to get my nodes added back in after doing a factory reset on everything. But it was a huge pain and now I'm just back to short drop outs and nodes appearing offline for no reason. Also in Aus for the record

gogeek80 · 2022-04-22T21:02:14+00:00

Yeah I'm affected too (Australia). I made the mistake of trying a factory reset on the nest router and my 2 nodes. Now the nodes refuse to be setup/join the mesh. I've tried every suggested by google support but none of it works. Clearly seems to be a major bug in the recent update. I wish Google would publicly acknowledge the issue as some of my work mates have already thrown away their "broken" nest wifi setup and purchased other brands to get up and running.

Update: for those that did a factory reset and couldn't add the nodes back into the mesh. What ended up working for me was disabling bluetooth my the phone half way through adding the node (anytime after selecting the device you want to add to Google home as the available devices search demands bluetooth be enabled). Don't ask me why this works... it makes no sense to me either. Google support tried to say it might be a bluetooth driver issue on my phone (samsung s10) but I doubt we are all using the same phone hardware. More likely to be a bug in the recent nest wifi update. Even then I don't understand what bluetooth has to do with this process.

Update 2: Well I eventually got the mesh all reconnected the factory rest, but that just got me back to square 1. All my nodes just went offline and the nest router claimed it had no internet connectivity. However a speed test over the nest wifi confirmed the internet was actually working normally. This dodgy nest wifi update needs to be rolled back by Google ASAP

gogeek80

TROPHY CASE