-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Pixel completely died. Doesn't even seem to charge #428
Comments
So "product expert" recommends taking the device to nearest authorized out-of-warranty repair service. Since the operation is limited under covid-19 weather, and recovering this device is by no means high priority, I push this back. |
Google's website let me move on with IMEI, then recommends local repair store: uBreakiFix at 5500 Sunrise Boulevard, Suite 300, Citrus Heights, CA, 95610. On the same there is 'shipping' option that also shows a rough estimate, which was $249 for this particular case. With $249 I can even buy a new Android tablet so I'm not so sure if spending that amount on 3 years old device is reasonable. |
Google offered "Trade In" option while signing-up for Google Fi (https://github.com/130s/30y-130s_life/issues/636#issuecomment-643396814). My Pixel was not acceptable due to power not turning on. When I checked in as "turns on", it was $25.00...Not worth it either. |
Owl inside H-Mart Doraville said he can fix both Google Nexus panel crack and Google Pixel dead battery. Will have him look soon. |
I've seen the store in H-mart in Doraville closed for the past few times after August (Sat or Sundays). Sent an email to ask the status. |
Years passed, I plugged the device to chargers again but no progress, still silent. |
After I switched to Pixel 4 #390, I've been using Pixel as a wifi device. Despite I've seen the device turns off all of sudden while the remaining battery indicates still sufficient, like 40%, it's been working great. However recently I found the device doesn't turn the power on at all. No charging indicator either. Not sure if it's a battery issue (related to #345) or something else.
CoS
The text was updated successfully, but these errors were encountered: