![]() And, our Nexus 5 phone also had similar experience. My friend using Pixel have had similar issues in the past, with Pixel and no support from Google. If this problem is so common now, why google is not doing anything? My OnePlus One, which I took out of my drawer after months, still works like a charm.ītw, my other Pixel 3 also has issues with Power button being flaky and keeps rebooting, another known problem, but Google does nothing about it. Phone was working normally yesterday, and all of a sudden its dead. Only thing changed recently was that major OS update few weeks back. Same thing happened yesterday on my Pixel 3. Almost like this was planned by Google in the first place. Interesting how I was the original owner of my suspect Pixel 3, and that it just so happens that Google's chosen memory chips failed in 3 years - when I'm sure there's phones that have been out there for almost a DECADE without failing and are still going (relatively) strong. I just received the new (refurbished) phone in the mail today.įor any new users coming in here, Google's bug tracker has officially changed this issue to "Won't Fix"/"Infeasible" - their reasoning is that their memory chips have completed their "natural lifecycle" and have failed due to normal consumer use case wear and tear. They said, ok we will replace the phone, this is a one time special blah blah blah. and, and if they didn't fix the phone I would take it up with Australian consume rights. there are no hard numbers and you have make the case.Įven though google only gives you 1 year, I stated that It's fair and reasonable for a phone which was offered by my telco on a 3 year contact, should last for at least 3 years. Australian consume law states the warranty of a product must be fair and reasonable expected period, This is not black and white, it's based on what the item is, the purchase price, how it's used etc. I'm not with that telco anymore, but I went anyways to keep google happy knowing full well they would say no.īack to google. the first told me to go back to my telco and have them sort it out. Hello, my wife pixel 3 died that same death about 2 weeks. ![]() Has Google acknowledged this (likely answer: NOPE), and what are my options to resolve this (likely answer: NONE)? Research online shows that the phone is booting into a super low level Qualcomm firmware recovery mode - so I'm assuming Google pushed out a "security update" or something and the firmware update somehow bricked the phone. There are also at least a couple people reporting this issue in the subreddit within a couple days/weeks (short enough timespan to explain how Google "rolls out" updates slowly) This is 99% due to a firmware update issue with the Pixel, since it notified me it was rebooting overnight to install updates. ![]() I can't identify the device with "adb devices" or whatever the command is, and when I plug the device into my Windows PC, Device manager shows QUSB BULK Power button doesn't work, black screen, no power indication or LEDs when I plug the phone in, not receiving calls, etc. My phone out of the blue decided to stop working overnight while charging. Making a separate thread to hopefully bring more attention to this issue since it seems widespread enough to maybe get Google off their greasy behinds and attend to this issue. I got a new pixel phone as a replacement to the Pixel 3 as I figured it was maybe a bad firmware update on Googles end, but now that it's been identified as hardware failure. What a sad excuse from an advertising company moonlighting as a phone manufacturer. They've closed the bug tracker ticket and are referring people to uBreakiFix for an out of warranty replacement. ![]() Almost like this was planned by Google in the first place to try and get you to buy a new phone. Interesting how Google's chosen memory chips failed in 3 years - when I'm sure there's phones that have been out there for almost a DECADE without failing and are still going (relatively) strong. EDIT: For any new users coming in here, Google's bug tracker entry has officially changed to "Won't Fix"/"Infeasible" - their reasoning is that their memory chips have completed their "natural lifecycle" and have failed due to normal consumer use case wear and tear. ![]()
0 Comments
Leave a Reply. |