How not to handle a user created Issue
issuetracker.google.com
issuetracker.google.com
It took me a while to figure out it was a software issue, I wad helped by the fact that my wife's Pixel has automated updates - and it stopped charging on the wireless charger - while mine I like to manually update - and it stopped charging after the update.
Google Support offered to replace the Pixel - I refused, since being a software issue would not help.
I filed a bug report and created a case. Since [my guess is that] people are being measured on 'touch time' I receive an e-mail every couple of days saying: "Thanks for the feedback, we're working on this" - devoid of any useful information.
I have an issue filed on the Android issue tracker [0], that issue has been marked as duplicate of another issue. I though: "Good! Lets see what this is all about!" - clicked on the issue and found out it's a private issue.
I understand that Google may not want their dirty laundry in the open, but marking a public issue as a "duplicate" of a private one doesn't help any one.
Ideally you'd want to have the public issue 'related to' the private one and have some high level updates - confirmed, this is what's happening, we have a fix, this is our target release and such.
I understand I am not a magic creature identified as a Developer, but a a lowly user that brought in this carcass of a bug into your house as a gift I would expect in exchange a pat on the head and the confidence that I can have some information in exchange.