- Discussions
- You are here
Another day, another Pixel bug — what's wrong this time?
Things that are NOT allowed:
- Off-topic talk - you must stick to the subject of discussion
- Trolling - see a description
- Flame wars
- Offensive, hate speech - if you want to say something, say it politely
- Spam/Advertisements - these posts are deleted
- Multiple accounts - one person can have only one account
- Impersonations and offensive nicknames - these accounts get banned
To help keep our community safe and free from spam, we apply temporary limits to newly created accounts:
- New accounts created within the last 24 hours may experience restrictions on how frequently they can post or comment.
- These limits are in place as a precaution and will automatically lift.
At this point, asking "WTF is it with all of these bugs, Google?!" (or something similiar) has become somewhat of the norm. No OEM seems to have the innate ability to generate as many bugs for their smartphone platform as Google does. I mean, its happening so much that I'm not alone in developing verbiage that relates to it (Forver Beta and Buggy), as even the author has come up with the very witty and likeable term "bug loop" lol. Seriously, get your QC in order, Google. This is beyond ridiculous now.
Folks this is what happens when the phone is smarter than the user.
This girl continues to defend the undefendable. Wise up Lady Bruce.
If you've ever visited Reddit's r/GooglePixel subreddit, you'll be greeted with a slew of posts with user complaints. We've covered quite a few of them over the past year, most recently on July 1, when my colleague Murray detailed a strange pop/click sound affecting some Pixel phones. Now, another glitch is gaining traction, and this time it seems to involve Gemini and headphones. Gemini bugs audio on headphones Over the weekend, several users have noticed how their headphones suddenly blast...
Click here to read the full article