this post was submitted on 20 Oct 2023
105 points (98.2% liked)
Android
27933 readers
103 users here now
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
!android@lemmy.ml
founded 1 year ago
MODERATORS
It's a really weird issue for sure. I've had nothing but issues with this screen. I've had it for all of 4 months, and had to have the screen replaced for a band across the center horizontally that was not accepting touch. Three screens later, and finally I have one that doesn't have any visual or touch defects, and now I get flashbanged if I fumble unlocking it. Ugh.
If you're consistently having screen issues with your Pixel and it's not due to any accidental damage but straight out the box it could very well be a problem with the motherboard. Various ways to solve this like contacting Google and seeing if they'll do an in-warranty replacement device, or you could see if a Google authorized repair center will do a MOBO replacement. However the suggestion I commented elsewhere in this thread is the better 1st step to take
Yeah, I've had 4 screens replaced. First one, a horizontal band just stopped taking touch input about 3/4 of the way down, and then they replaced it 3 times, each with unique display issues out of the box, and now this lol. This is my first Google phone and, honestly, probably my last.
Edit:just realized you were replying in a chain I had already explained all of that. Oh well!
To be perfectly honest this is why I don't like Pixels. Every manufacturer has issues of course. I'm not saying Pixels are bad, just I wouldn't get them because of personal preference and the design. The Pixel 4s constantly had battery issues because of the quality of the material used for the battery connector. The Pixel 5s were actually pretty good in terms of hardware issues. The Pixel 6s were nightmares. Constantly having battery or screen issues. As for the 7s I can't say as I stopped repairing phones a year ago
This is my first pixel device, and probably the last TBH. Not a good introductory experience.
I will say, my used Pixel 6 (GrapheneOS) has worked beautifully so far, with no hardware defects. If I had to complain, the speakers aren't particularly loud, but I've had no hardware issues with it. I agree with other people, it sounds like it could be a bad motherboard? It would be interesting if you could post a video of the issue
I'll see what I can do about a video. The only thing I really have to record is... Well, my phone lol. I'll borrow one at some point.
Can confirm as well, the speakers kinda blow on the pixel 7 pro, as well lol
I just edited OP with a video.